Commands and state
Keep CR, MG400 and M1 Pro profiles separate; the vendor name does not define a command set.
TRUSTED FACTORYFLOW
Compact pick/place, tending and sorting. TCP/IP SDK — model-specific.
No default shared CR/MG400/M1 Pro profile. Agree controller/SDK before command mapping or fault reset.
FactoryFlow links business work to the vendor system through a selected adapter/profile. Vendor interfaces below are technical references; deployment scope is configuration-specific, not implied by the brand name.
| Component | Scope |
|---|---|
| Referenced interface | TCP/IP SDK — model-specific |
| Related modules | Robot Cell / Program Control / Adapter |
| Work mapping | cell job → approved program; state/error → recovery |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Keep CR, MG400 and M1 Pro profiles separate; the vendor name does not define a command set.
Bind cell jobs to programs and native errors for the selected controller; ACK is not done.
Fault reset is model/mode-specific; SAT checks reconnect during an active job before restart.
The configuration record identifies model/controller, firmware, options, authentication, adapter build and state mapping. Test the target equipment, including disconnects and unresolved outcomes.
| Test | Evidence to reconcile |
|---|---|
| Command acceptance | Task/execution links to a vendor ID; ACK and completion remain distinct. |
| Redelivery and reconnect | Query existing work before recreation; retain identities and exception decisions. |
| Handover / completion | Verify scans/handshakes and outcomes at the owning system, not robot state alone. |
Interface documentation does not establish FactoryFlow acceptance of every model or option.
Bring equipment records and the use case to discovery to agree profiles and tests.