Summary
This article explains how to generate CFX protocol data that will be readily interoperable with ArchFX. Customers can use it when updating their factory data sources to publish data in CFX format for use by ArchFX and other applications. This document will document all few possible CFX use cases, not all of them.
Generate compliant CFX data
One common source of CFX interoperability problems is when software generates CFX data that doesn't comply with the IPC-CFX specification. Developers should carefully review the latest PC-CFX specification to make sure your software is generating data that is compliant with the specification.
Guidance for all machines and stations
All machines and stations must:
- produce a Heartbeat message every 1-5 minutes
All machines and stations should:
- report faults using FaultOccurred and FaultCleared
Back End Assembly Station
Back End Assembly Stations (BEAS) must:
- send a WorkStarted and WorkCompleted message so that ArchFX can determine the cycle time
- send a UnitsProcessed message
- Use the internal dynamic structure placeholder to report measurements and traceability data.
- produce a Heartbeat message every 1-5 minutes
Back End Inspection Machine
Back End Inspection Machines (BEIM) must:
- send a UnitsTested message when the inspection cycle is complete
- Use the internal dynamic structure placeholder to report measurements and defects.
- produce a Heartbeat message every 1-5 minutes
The BEIM may also send a WorkStarted and WorkCompleted message so that ArchFX can determine the cycle time.
The BEIM should report faults using FaultOccurred and FaultCleared.
Notes
- UnitsTested is for units tested by automated means; UnitsInspected is for units inspected by technicians visually.
Comments
0 comments
Please sign in to leave a comment.