Every JM Automated Solutions vision system runs on the same HMI platform. Operators see the live image, a clear pass/fail result and false-reject counts. Recipes change over from the plant's MES via EtherNet/IP or TCP/IP. Failed parts are removed by an encoder-tracked pneumatic reject. Because it is one platform, operators who learn it on one line can run it on the next.
What does the operator see?
- Live image. What the camera sees right now, with the inspection result drawn on it.
- Pass/fail display. A clear result for every part, plus the saved images of recent fails.
- False-reject counts. How many good parts are being rejected, so a system that is too strict shows up on the screen, not in a pile of scrapped product.
- Reports. Reject counts by reason and by time period, with timestamped logs for traceability.
How do recipes change over?
From the plant's own system. When the line changes product, the MES or production system sends the new recipe to the vision system over EtherNet/IP[1] or TCP/IP. The recipe carries everything that changes with the product: the expected code, the tolerances, the inspection settings. Nobody re-teaches the camera at changeover, and the HMI shows which recipe is running.
How are failed parts removed?
With an encoder-tracked pneumatic reject. An encoder on the conveyor tracks how far each part has moved since the camera saw it. When a failed part reaches the reject, a PLC output fires a short blast of air and removes that exact part, even if the line speeds up or slows down.
What runs underneath?
A typical strobed exposure of about 60 microseconds[2], so moving parts are imaged sharply. The lighting, camera and settings are chosen per task. Code reading uses the same deep learning OCR on every system. The hardware is built for washdown areas.
Which systems use it?
Nearly all of them:
Want to see it with your product?
Tell us what your line runs and what goes wrong. We'll show you what the HMI would show for your inspection. Book a call or send JM Automated Solutions a message.