Commands and state
Separate JSON-RPC request/response from RTDE state; a live RTDE connection does not prove job completion.
TRUSTED FACTORYFLOW
Pick/place, machine tending and work cells. SDK / JSON-RPC / RTDE / Script.
Controller owns motion; check mode/alarms before restart; no arbitrary scripts.
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 | SDK / JSON-RPC / RTDE / Script |
| Related modules | Robot Cell / Device Adapter |
| Work mapping | recipe/version → program; state, I/O and job result |
| Catalogue status | Integration is confirmed by Mobile-ID. Models, firmware, options and adapter builds belong in project acceptance records. |
Separate JSON-RPC request/response from RTDE state; a live RTDE connection does not prove job completion.
Bind approved program/script to recipe hash and check I/O state before handover.
After reconnect, inspect mode and alarms and reconcile the previous 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.