Module specification
Use a reusable specification for triggering, result validity, timeouts, recipes and restoration. Define the evidence needed to reproduce the vision function on the next machine.
A working prototype is not yet a repeatable machine module. The next build needs the same inspection conditions, a defined controller interface and a tested restoration procedure. This specification excerpt can be completed for a machine family. It supports the delivery approach described for machine builders.
Assign a configuration owner and revision before approving the first build. Separate required behaviour from implementation details so a replacement component can be evaluated against the same requirement.
| Field | What to specify |
|---|---|
| Inspection decision | Feature or measurement, allowed product variants and expected machine action. |
| Imaging limits | Field width and height, smallest relevant detail, position/height range, exposure and lighting conditions. |
| Hardware revision | Camera, lens, light, controller, mounts, cables and power supplies by exact reference. |
| Software baseline | Firmware, driver, inspection software, operating environment and licence requirements. |
| Trigger | Source, electrical or protocol interface, minimum interval and acceptance condition. |
| Ready and busy | When the machine may request an image and what happens to a request during processing. |
| Result | Data format, units, coordinate frame if relevant, validity flag and association with the trigger. |
| Timeout | Maximum permitted wait and the machine action if a result is missing or late. |
| Acknowledgement/reset | How a result is consumed, when flags clear and how a new cycle starts. |
| Recipe change | Recipe identifier, load confirmation, permitted change moment and handling of an invalid recipe. |
| Restoration | Backup location, included files, licence recovery, hardware replacement steps and reference test. |
| Release control | Approved revision, test evidence, authoriser and rollback procedure. |
Fill these fields with measured or agreed values. Do not use an example camera's frame rate as the machine's permitted result time. The latter includes acquisition, processing and communication and must meet the actual machine deadline.
For example, the controller issues a trigger only when the subsystem reports ready. The vision subsystem accepts it and returns a new result associated with that cycle. The controller consumes the result and acknowledges it using the supported protocol. A missing result reaches the defined timeout and cannot silently reuse the previous result.
This is a behaviour specification, not a universal wiring diagram. Some interfaces use discrete signals, others use messages or counters. Confirm the sequence and electrical levels for the selected devices. Define restart behaviour when only one device loses power.
Use identified good parts, known defects and borderline cases. Retain an independent validation set. Agree separate limits for missed defects, false rejects and result time, then test across the supported product positions and speeds.
Include a trigger during processing, missing image, late result, disconnected data cable, invalid recipe and restart. Check that each condition produces the specified machine action. Confirm that image logging or other required production functions are active during timing tests.
For a repeated build, verify mounting dimensions and reproduce the reference images before running the acceptance set. A matching part number alone does not prove matching focus, light angle or configuration.
Have a maintainer restore the configuration on the intended replacement device in a controlled test. Include software and licence recovery where required. Repeat the relevant image, interface and decision tests and record the elapsed time and missing instructions.
Set the permitted restoration time from the machine's service requirements. Retaining a backup file does not establish that the machine can be restored within that time. Confirm responsibility for keeping spares, backups and tested software versions available.
Separate first-module design and validation from per-machine assembly, configuration and acceptance. Calculate each activity as hours multiplied by the applicable rate. Add hardware, licences, spare stock and expected maintenance of the approved configuration.
Track the actual time required on later builds. Reuse may release engineering capacity, but a new surface, smaller feature or different interface can require requalification. Include that work rather than assuming the first design applies without limits.
Start by completing the interface and restoration fields for one current machine module. Review them with the PLC engineer and service team, then use the agreed excerpt to define the next acceptance test.

Discuss interfaces, software management and expected machine life early in the design. We can help align the hardware and integration choices.