Tablet vs Sensor vs Controller Machine Monitoring — Which Fits Your Shop?

Short answer

Operator tablets work on any machine, need no wiring and are the only source that knows rejects, reasons, jobs and operators. Sensor boxes automate the piece count and run state on any machine with a cycle signal. Controller connections (Fanuc, Haas, Mitsubishi…) add alarms with codes, true cycle times and program data — on machines whose controls support it. Most shops should start with tablets everywhere and add the other two machine by machine.

Side by side

Operator tablet vs sensor box vs controller connection
	Operator tablet	Sensor / auto-count box	Controller connection
Works on	Any machine, any age	Any machine with a cycle-complete or stack-light signal	Fanuc (FOCAS), Haas (MTConnect), Mitsubishi (SLMP), others by protocol
Hardware per machine	Basic Android tablet	Small box wired in the panel	None — one gateway PC per floor
Time to go live	One afternoon for the floor	Panel wiring per machine	Option licensing + network per machine
Piece count	Operator taps	Automatic (pulse per cycle)	Automatic (control's counter)
Running / idle	From operator actions	Automatic	Automatic
Rejects & reasons	Yes	No	No
Job card & operator	Yes	No	No (program number only)
Alarms with codes	Operator reports	No	Yes
Cycle time, program, feed, spindle	Derived / no	Cycle time from pulse gap	Yes, from the control
When it fails	Operator forgets or batches taps	Wrong signal tapped; Wi-Fi down (buffers)	Option not licensed; IP changed; counter reset (should self-heal)
Best for	Every machine, day one	Busy machines where counts must be hands-free	Modern CNCs where alarms and true cycle times matter

Operator tablet: the only source that knows why

A tablet at the machine turns the operator into the sensor — and the operator is the only sensor that knows a piece was scrapped for a burr, that the stop was waiting for material, and which job card is running. Big buttons, PIN login, three taps per entry. It works on a 1998 lathe and a new five-axis alike, and a whole floor goes live in an afternoon.

Its weakness is honest: it depends on the operator tapping at the moment, not at the end of the shift. Good tablet systems make the tap cheaper than not tapping, and show the gap when a shift under-logs.

Sensor box: hands-free counting on any machine

A small box wired to the machine's cycle-complete or stack-light signal emits one pulse per cycle. From pulses you get piece count, running vs idle and an approximate cycle time — on any machine with such a signal, regardless of control brand or age. It needs a panel wiring job per machine and a Wi-Fi connection, and it should buffer when the network drops.

It cannot know rejects, reasons, jobs or operators, and a wrongly tapped signal counts the wrong thing — so commissioning matters. Use it where the operator is too busy to tap counts reliably and the machine is worth automating.

Controller connection: the richest data, on the machines that allow it

Modern controls expose their state over the network: Fanuc through FOCAS, Haas through MTConnect, Mitsubishi through SLMP, Siemens through its own interfaces. A gateway on the plant LAN polls them and gets the part counter, run state, alarms with codes and text, the active program, feed and spindle — the control's own measurements, not inferences.

The catches: the option must be licensed and enabled on the control, the machine needs an IP on your network, and the software must handle counter resets and offline gaps without inventing parts. Insist on read-only, outbound-only integration — no write path to the control, no inbound port into the factory. And it still does not know rejects or reasons, so the tablet stays.

What each costs, roughly

Cost shape

Tablet: A basic Android tablet per machine from a local shop, plus a mount; no vendor hardware
Sensor box: Small hardware cost per machine plus a wiring visit; nothing on machines you don't automate
Controller gateway: One small PC per floor, amortised across every connected machine; option licensing on the control if not already enabled
Software: Usually per machine per month; check whether the vendor also charges per user or per gateway

Numbers and Indian market ranges are in the guide to machine monitoring software cost in India.

How to decide, floor by floor

Mixed floor, 5–30 machines, mostly older

Tablets everywhere. Add a sensor box on the two or three machines where counting by hand is the bottleneck.

High-volume turning, many machines, few supervisors

Tablets for rejects and reasons; sensor boxes on the machines that run unattended cycles all day.

Newer VMCs with Fanuc / Haas / Mitsubishi

Tablets for context; controller links for alarms, true cycle times and hands-free counts. Skip the sensor box on those machines.

Tablets this week; sensors and controllers when they pay.

A 20-minute demo, on-site in Rajkot and across Gujarat or over a call anywhere in India. Free 15-day trial, no hardware to buy from us.

Book a demo WhatsApp us

Questions shop owners ask

Which is more accurate — a sensor, the controller, or the operator?

For the piece count and run state, the controller, then the sensor, then the operator. For rejects, reasons, job and operator identity, only the operator — no sensor or control knows why a machine stopped or that a piece was scrapped. Accurate monitoring uses both: a machine source for counts, a human source for context.

Can I monitor an old machine with no Ethernet port?

Yes, two ways. An operator tablet works on anything. An auto-count sensor box works on any machine that has a cycle-complete or stack-light signal to tap into — which includes most CNCs from the last twenty years, and many older machines with a simple relay added.

What do I need to connect a Fanuc controller?

A Fanuc control with Ethernet and the FOCAS option enabled, an IP address on your plant network, and a small gateway PC on the same network that polls it read-only. No inbound port, no VPN. Haas uses MTConnect; Mitsubishi uses SLMP; the gateway handles all three.

Is it safe to connect software to my CNC controller?

If the connection is read-only and outbound-only, yes. Ask the vendor two questions: can the software ever write a parameter to the control, and does it need an inbound port or VPN into the factory? The answers should be no and no.

Do I have to pick one approach for the whole shop?

No, and you shouldn't. Tablets on every machine, sensors on the busiest, controller links on the CNCs that support it — all feeding one dashboard. Start with the cheapest that works everywhere and upgrade machine by machine.

Which approach gets me live fastest?

Tablets — a whole floor in one afternoon with no wiring. A sensor box is a panel-wiring job per machine; a controller link needs the option licensed and the network set up. Both are worth doing on the machines where hands-free counts matter, after the floor is already live.

Tablet vs sensor vs controller machine monitoring — which fits your shop?