Forum Home › Forums › Communicating with Devices › Modbus › Slave Device Failure
- This topic has 8 replies, 2 voices, and was last updated 4 years, 3 months ago by kirjono mudiarto.
-
AuthorPosts
-
December 19, 2019 at 8:58 am #6218kirjono mudiartoParticipant
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
kirjonoDecember 19, 2019 at 12:52 pm #6219MikhailModeratorHi Kirjono,
Please provide screenshots of the Communicator settings and copy a part of log file here.
December 20, 2019 at 1:34 am #6222kirjono mudiartoParticipant
https://ibb.co/ZMcGyz8
https://ibb.co/cC5DD88
https://ibb.co/H218Bqm
https://ibb.co/mG7RRJ8
https://ibb.co/T2DMmS5- This reply was modified 4 years, 4 months ago by kirjono mudiarto.
- This reply was modified 4 years, 4 months ago by kirjono mudiarto.
- This reply was modified 4 years, 4 months ago by kirjono mudiarto.
- This reply was modified 4 years, 4 months ago by kirjono mudiarto.
December 20, 2019 at 1:42 am #6227kirjono mudiartoParticipant2019-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 established2019-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
December 20, 2019 at 2:08 pm #6228MikhailModeratorYou 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!May be the device can’t get data from sensors?
December 20, 2019 at 2:09 pm #6229MikhailModeratorThe register address looks strange. Try address 5-6 instead.
January 3, 2020 at 3:28 am #6302kirjono mudiartoParticipantHi 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.January 3, 2020 at 7:14 am #6304MikhailModeratorI’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.
January 20, 2020 at 4:37 am #6427kirjono mudiartoParticipantThank you very much Mikhail
-
AuthorPosts
- You must be logged in to reply to this topic.