Photoeyes: presence, registration, and the rule you never break

The photoeye is the workhorse of the sensing layer. A beam of light crosses the conveyor to a receiver. Break the beam and the sensor changes state. Simple part, and it does two different jobs that people constantly blur together.

The first job is presence. Is there a package here, yes or no. That's the transducer you met back in Lesson 12: a photoeye plugged into an accumulation zone, reporting to the zone controller so the zone knows whether to hold product or release it. Presence is a steady-state question, and the eye answers it for as long as the package sits in front of it. Presence has its own mounting trap, though: set the beam height and angle to catch the shortest, flattest carton in the mix, not the tall one you're picturing, because a beam that rides over a three-inch pad reads an empty zone that isn't. And watch reflective, shiny surfaces, shrink-wrap, foil, a glossy tote, since they can bounce the beam back and false-trigger on a package that isn't there or read the wrong one.

The second job is registration. Not whether a package is present, but exactly when its leading edge crosses one fixed point. Registration is an event, a single instant, and that instant is what starts things: a scan, a tracking clock, a timed divert. Every timed action in a section hangs off a registration read.

Those two jobs put different demands on how you mount the eye, and that's where the one rule in this lesson lives, the one you don't get to break. A photoeye used for registration has to be mounted square to the direction of travel. Square, the leading edge breaks the beam at the same repeatable point on every carton, no matter where the carton rides across the belt. A narrow box hugging the left rail and a wide box centered on the belt both trip the beam at the same line across the conveyor, because the beam is that line.

Angle the eye and you lose that. Now the point where the leading edge breaks the beam depends on how wide the carton is and where it sits across the belt. Two cartons cross the same physical line and trip the eye at two different instants. The registration point drifts, and every timing that hangs off it drifts right along with it. An angled eye can look like it catches more of the box, more coverage, but for registration that's exactly backwards. It trades a repeatable trigger for a variable one.

One more thing that same presence photoeye does, so you recognize it in the field. A photoeye that should clear within a set window and doesn't is reporting a jam. A lane-entry photoeye that stays blocked is reporting a full lane. Same sensor, different question. What the system does about a jam or a full lane, the recovery logic and the response it triggers, is its own subject and it's Lesson 23. Here, name the job the eye is doing and keep moving.

Encoders: knowing where the carton is after the read

A read happens at one fixed point. The divert happens somewhere downstream, a good distance later. In between, nothing is watching that specific carton. So how does the system know, at the instant the carton reaches the divert, that this is the one it scanned well upstream, and that now is the moment to fire?

The encoder. On a sorter, an encoder measures belt travel in precise increments, and the PLC uses that measurement to know exactly where every item is at any given moment. The carton stops being a thing the system has to keep an eye on and becomes a number: a position, counted forward from the point where it was inducted. The belt has moved exactly this far since the read, so this carton is exactly here now. When here lines up with the divert, the PLC fires, and it fires on time even though the read happened well upstream. The encoder is the mechanism that closes the loop between the identification event and the divert event.

This isn't a conveyor trick. It's the same position-tracking principle a CNC machine or an industrial robot runs on. The item gets treated as a virtual object moving through a coordinate system, and the machine knows the coordinate at all times. A sorter tracking a carton by belt-travel distance from induction and a robot tracking its tool through a work envelope are doing the same thing: holding a moving object as a number and trusting the number.

Here's the dependency worth saying out loud. The encoder can only trust the read if the read was repeatable. If registration drifted because somebody angled the eye, the encoder faithfully tracks a carton whose starting position was already wrong, and it diverts precisely to the wrong place. Tracking doesn't fix a bad read. It commits to it. And when the encoder loses a carton, when track drops, that carton has a destination waiting for it, the hospital lane. Naming that path is enough for now. Turning encoder counts and belt speed into the actual distance you need between the read and the divert is the latency budget, and that math is Lesson 22.

Identifying and measuring: the read is a family, not a device

Up to now I've said the read like it's one thing. It isn't. The read is a family of devices, and you pick from it by what you actually need to know at that point.

• A fixed barcode scanner reads a barcode presented in a known orientation at a known point. It's the default when you can control how the label faces the reader: fast, reliable, inexpensive, as long as that orientation holds.
• A scan tunnel is an array of scanners arranged to read a barcode on any of several faces at once. You spec a tunnel when you can't guarantee which way the label faces, because the product arrives however it arrives. The tunnel buys you orientation independence, and it costs more and takes more room than a single head.
• A camera, or vision system, reads what a laser scanner can't. A damaged label, an unoriented one, the printed characters themselves through OCR, or the condition of the package. When the barcode alone won't carry the job, the camera picks it up.
• An inline scale weighs the package while it's moving, without stopping the line, for any decision that turns on weight: a routing call, or a reject when the weight comes back outside the expected range.
• A dimensioner measures length, width, and height in motion. You use it for cubing, or to confirm a package sits inside the design envelope you built the system around before it reaches equipment that assumes it does.

Now the part that separates a real design from a hopeful one. No identification system reads everything. Some share of barcodes come back unreadable: torn labels, bad print, shrink-wrap glare, a carton that landed with the label face-down. That share is the no-read rate, and it's a number, not a hope. You design for it. A read that fails has to have somewhere to go. Give it a destination, the hospital lane, and a no-read becomes a routine event the system absorbs without breaking stride. Leave it without one and the first failed read of the shift is a carton stopped at a decision point with nowhere to go, waiting for a routing answer that will never come, and the line backs up behind it. What that destination has to be sized to hold, and how the routing around it gets built, is Lesson 23. That it has to exist gets settled right here.