Roboguide Virtual Robot Controller as Modbus Slave

    Hello,

    Trying to connect controller R-30iB and PC with Modbus. But my controller is not available now, so I use roboguide as virtual controller.
    After reading Modbus TCP Interface Operator's manual, I still have lots of questions.

    What's the slave ID (device ID) of controller? Can I modify it?
    What's the address with function "Read Holding Registers" for master polling?
    Currently the Modbus IO of controller is DO[129-192], DI[129-192], as what I read from manual, the address is supposed to be 10008 but the polling is failed.

    Other information:
    The connection is successfully built.
    Running roboguide and Modbus master at same PC.
    Tested on two PCs that are Windows 10 and Windows 7.
    Use Modbus Master Tool from Witte Software for testing.
    Use roboguide version 9.

    Found another topic about similar question of mine.
    https://www.robot-forum.com/robotforum/fan…cp-c-libmodbus/

    Slave ID should be 1. Also confirmed variable $MODBUSTCP.PORT is 502. Connected to wrong port before.
    Function code could be any. For example to read DI[129] the code is 01-Read Coils Address 128, when $MODBUSTCP.BASEZERO is true.

    But it's unable to connect port 502. Maybe I have to turn on something to run server first?

    Edited once, last by zbc (July 10, 2018 at 4:03 AM).

    I test on real robot controller and the Modbus connection is success. Maybe there are some settings I missed in RoboGuide?

    To read DO[129], poll address is 10000 when $MODBUSTCP.OUTPUTBASE is 10000.
    But fail to write any DI. I don't know if address is wrong or the controller disables permission for written.

    Edited once, last by zbc (July 18, 2018 at 4:34 AM).

    I know this is old, but I'm posting this in case anyone faces the same issue.

    To enable Modbus I/O control on Roboguide, you need to set system variable $MODB_ENABLIO to 1, then restart the controller. Same goes for Ethernet/IP ($EIP_ENBL_IO).

    MENU--NEXT--SYSTEM--Variables--$MODB_ENABLIO

    Hi,
    I test this also today, with RG V9 and ModBus Poll V. 9.6.0

    I get always "Read error" and "Write error" at ModBus Poll.

    Maybe someone can support screenshots of settings at ModBus Poll and also ModBus Screen at iPendant?

    When the connection is running, is the "Slave status" Running or Idle at ModBus TCP Screen at RG?

    Many thanks.

    I haven't tried Roboguide with Modbus but I have done Ethernet/IP and OPCUA in Roboguide.

    1. I found wireshark to be a helpful tool. I was able to find some error message in one of the Ethernet packets that helped me figure out my problem.

    2. In Windows you can open a Command Prompt as Administrator. Run the command: netstat -ab

    It will list all of the ports. This will help you to see what ports Roboguide has opened. For example, I have FRVIRT~1.exe (roboguide) listening on Port 4880 which is used for OPCUA. If port 502 is not opened by Roboguide then you won't be able to connect.

Advertising from our partners