Other robots
      Back to home
      1. Help Center Home
      2. Other robots

      How to control Robotiq Product on non supported robot?

      When you make an integration on a robot not supported by Robotiq you have to check the following points.

      Mechanical connection

      Check robot tool flange drawings in robot documentation and gather the following information:

      • PCD: (ex: 31.5mm)
      • Screw size and number: (ex: 7M5)

      Example of flange drawing:

      Then we will check if we can find a coupling that may correspond to  your robot. 

      If there are no coupling that can fit, we can propose using a blank coupling. On this coupling the client can machine holes where he wants to use screws.

      Check that the CAD of the coupling that can be downloaded on Robotiq support page fits the robot flange. Sometimes, even if PCD and screws match the design of the flange, they may prevent the use of the coupling.

      It is client's responsibility to make sure the mechanical coupling is fit for his robot.

       

      Communication protocol

      By default the communication protocol of the Robotiq products is Modbus RTU.

      For the gripper 2F85, 2F140, Hand-E, Hand-E C10 and E-Pick, if the controller of the robot can handle this communication protocol you don't need to use a universal controller.

      However, if the robot cannot use Modbus RTU, then you can use a universal controller to communicate with one of the following protocols:

      • [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

      A master controller is needed to control Robotiq product. Sometimes, the robot controller can only act as a slave.

      It is client's responsibility to choose the appropriate communication protocol.

       

      For the FT300 the Universal Controller cannot be used. The client should be oriented to Anybus which can provide some generic communication protocol converters.

       

      Software

      Our products can be controlled by reading and writing memory registers.

      Details are available in our manuals : https://robotiq.com/support

      It is client's responsibility to make the software to control the gripper.