Slave Device Failure

Forum Home Forums Communicating with Devices Modbus Slave Device Failure

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #6218
    Avatarkirjono mudiarto
    Participant

    Hi,

    I am trying to use Rapid SCADA to communicate with Modbus TCP device. It seems that communications is established but an error is being generated. Looking at the log in communicator shows ‘Slave Device Failure’, even though communication using simply modbus was successful (device responds the data as expected).

    Can someone point me in the right direction as to how I can deal with this please?

    Thanks
    kirjono

    #6219
    MikhailMikhail
    Moderator

    Hi Kirjono,

    Please provide screenshots of the Communicator settings and copy a part of log file here.

    #6222
    Avatarkirjono mudiarto
    Participant





    https://ibb.co/ZMcGyz8
    https://ibb.co/cC5DD88
    https://ibb.co/H218Bqm
    https://ibb.co/mG7RRJ8
    https://ibb.co/T2DMmS5

    #6227
    Avatarkirjono mudiarto
    Participant

    2019-12-20 08:04:18 Communication session with the Device 1 “Test device”, type: KpModbus, address: 1, call number: 192.168.0.152
    Request element group “gateway”
    Error writing data: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
    Receive (0/7):
    Communication error!
    Unable to request because connection is not established
    Unable to request because connection is not established

    2019-12-20 08:04:20 Establish a TCP connection with 192.168.0.152:502

    2019-12-20 08:04:20 Communication session with the Device 1 “Test device”, type: KpModbus, address: 1, call number: 192.168.0.152
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!
    Request element group “gateway”
    Send (12): 00 00 00 00 00 06 01 04 75 34 00 02
    Receive (7/7): 00 00 00 00 00 03 01
    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!

    2019-12-20 08:04:21 Disconnect from 192.168.0.152

    #6228
    MikhailMikhail
    Moderator

    You can successfully connect to the device. The device “understands” your requests and replies according the Modbus specification:

    Receive (2/2): 84 04
    Device error: [04] SLAVE DEVICE FAILURE!

    Modbus Exception

    May be the device can’t get data from sensors?

    #6229
    MikhailMikhail
    Moderator

    The register address looks strange. Try address 5-6 instead.

    #6302
    Avatarkirjono mudiarto
    Participant

    Hi Mikhail,

    thank you for the replies, now it works.
    I have changed the address to 30006-30007.
    I’ve realized that the address must be added by 1 since rapidscada address starting from 1 and device address starting from 0.

    #6304
    MikhailMikhail
    Moderator

    I’ve realized that the address must be added by 1 since rapidscada address starting from 1 and device address starting from 0.

    You can change the starting address in the template settings.

    #6427
    Avatarkirjono mudiarto
    Participant

    Thank you very much Mikhail

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.