Skip to content
English
Sign in
Go to Robotiq.com
  • There are no suggestions because the search field is empty.

Why Does the Gripper Work on RUI but Not on a TM/Omron Robot?

Check Modbus settings and COM port configuration when using Robotiq grippers with TM/Omron

Context
Sometimes a gripper works correctly when tested on the Robotiq User Interface (RUI) but fails to communicate with a TM/Omron robot. This article explains the most common cause and how to resolve it.

Information

Main Cause

  • The RUI can control a gripper with any slave ID and baud rate.

  • The TM/Omron robot, by default, can only communicate with a gripper that has slave ID = 9.

How to Fix the Issue

  1. Check Modbus RTU Settings in RUI

    • Verify the slave ID of the gripper.

    • If it is not set to 9, update it to match the TM/Omron requirement.

    • Confirm that other communication settings (baud rate, parity, etc.) are at their default values

  2. Check COM Port Settings

    • Ensure the physical COM port used for the connection matches the COM port defined in the SET node on the TM/Omron robot.

    1.

    2.

    If the Problem Persists

    Other causes and solutions may be possible. If the issue is not resolved after checking Modbus settings and COM ports:
    Contact : support@robotiq.com