OnRobot, a company known for its “one interface fits all” approach to end-of-arm tooling (EoAT), has taken a significant step toward solving this. Their adoption of —specifically Modbus RTU over RS-485 and Modbus TCP over Ethernet—is quietly turning their grippers, sensors, and vacuum tools from simple accessories into fully addressable, intelligent edge devices. Why Modbus, and Why Now? Modbus is not new. Developed by Modicon in 1979, it is the automation industry’s lingua franca —simple, open, and robust. Unlike Ethernet/IP or Profinet, which require costly licenses and complex configuration, Modbus offers a flat, predictable register map.
And in a world of locked-in ecosystems and proprietary fieldbuses, that is genuinely collaborative. Need a specific register map or troubleshooting guide for an OnRobot tool? Let me know the model (e.g., RG6, VG10, HEX-H) and I can drill deeper. onrobot modbus
For OnRobot, the choice was strategic. Their tools already support multiple major robot brands (Universal Robots, Fanuc, Doosan, Mitsubishi, etc.) via their and One System Solution . But many advanced users don’t want to control a gripper only from the teach pendant. They want to trigger it from a vision system, a safety PLC, or a custom .NET application. OnRobot, a company known for its “one interface
For years, the promise of collaborative robotics has been simplicity. Yet, anyone who has wired a complex gripper or a force-torque sensor into a third-party PLC knows the reality: different protocols, proprietary boxes, and a tangle of cables. Modbus is not new