The native communication protocol of Robotiq product is Modbus RTU.
For 2F, Hand-E, EPick, and AirPick it is possible to control with a different communication protocol using a "Universal controller".
- [UNI-CTR-001-CANO] External controller for Robotiq Device -- CANopen
- [UNI-CTR-001-DNET] External controller for Robotiq Device -- DeviceNet
- [UNI-CTR-001-ECAT] External controller for Robotiq Device -- EtherCAT
- [UNI-CTR-001-ENIP] External controller for Robotiq Device -- Ethernet/IP
- [UNI-CTR-001-MTCP] External controller for Robotiq Device -- Modbus TCP
- [UNI-CTR-001-PNET] External controller for Robotiq Device -- ProfiNET
CAUTION: A master controller is needed to control Robotiq product. Sometimes, the robot controller can only act as a slave.
For the FT300 the Universal Controller cannot be used. The client should be oriented to https://www.anybus.com/ which can provide some generic communication protocol converters.
If the client wants to integrate our product on a Robot for which we do not provide a software integration, he will have to control the gripper at a low level by reading and writing registers. This control process is described in the manual section 4.2 - Serial Registers Mapping.
0 Comments