Using MachineMotionV2 Communication Protocols With MachineLogic
MachineLogic › External Communication › MachineMotion V2
MachineMotion Controller Use the topics below when the application should react to an event internal to the MachineMotion controller such as an Estop event for example. Topic Payload Description estop/status true false aux_safety_power/+/status 24V 0V 24V (0V) corresponds to unlocked (locked) aux_safety_power/+/request 24V/0V aux_safety_power/+/stored_request 24V/0V used internally to track desired brake state on reboot/transition drive/+/energized true/false drive/+/motor_size None small medium large nema_17_stepper overheat drive/+/error [{code: 0x4821, description: "over current"},{code: 0x5432 ..},{...}] drive/+/motionComplete 0 1 drive/+/sensor/A 0 1 drive/+/sensor/B 0 1 drive/+/end 0 1 sensor convention can be swapped drive/+/home 0 1 sensor convention can be swapped drive/+/temperature float drive/+/parameters {"axisType": "enclosed_timing_belt", "tuningProfile": "default", "motorCurrent": 10, "motorSize": "Large Servo", "brake": "present", "parent": 4, "direction": "positive", "gearRatio": 1.0 …