Forum Home › Forums › Communicating with Devices › Modbus › Error data fire system
- This topic has 3 replies, 3 voices, and was last updated 4 years, 8 months ago by
jeeslo.
-
AuthorPosts
-
January 8, 2019 at 6:07 pm #4819
jeeslo
ParticipantHello
I have a problem with the Modbus communication of a fire system, I use the Modbus Poll software for previous tests and everything works excellent.
MODBUS-POLL
000-Tx:00 25 00 00 00 06 01 03 00 00 00 0A
001-Rx:00 25 00 00 00 17 01 03 14 00 00 01 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09
002-Tx:00 25 00 00 00 06 01 03 00 00 00 0A
003-Rx:00 25 00 00 00 17 01 03 14 00 00 01 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09When I configure the scada-communication I have an error, checking the communication line log the data of TX there is a data F6 of hex I can not find a way to change to 01
SCADA-COMMUNICATION
2019-01-08 12:02:04 Establish a TCP connection with 172.16.0.41:502
2019-01-08 12:02:05 Communication session with the Device 12 “Incendios”, type: ScadaCommCommon, address: 502, call number: 172.16.0.41
Request element group “Test 1”
Send (12): 00 00 00 00 00 06 F6 03 00 00 00 05
Receive (0/7):
Communication error!
Request element group “Test 1”
Send (12): 00 00 00 00 00 06 F6 03 00 00 00 05
Receive (0/7):
Communication error!
Request element group “Test 1”
Send (12): 00 00 00 00 00 06 F6 03 00 00 00 05
Receive (0/7):
Communication error!2019-01-08 12:02:10 Disconnect from 172.16.0.41
Greetings and waiting for your help thank you very much
January 9, 2019 at 8:43 am #4822manjey73
ParticipantTry this library. If your device does not respond due to zero ID, it should work. In the future, Mikhail promised to add an identifier change in the release version of the library.
If so, this is the second device that does not accept a null request ID.
Still you have the difference
00 25 00 00 00 06 01 03 00 00 00 0A
00 00 00 00 00 06 F6 03 00 00 00 05January 9, 2019 at 1:15 pm #4833Mikhail
ModeratorHola
00 00 00 00 00 06 F6 03 00 00 00 05
F6 is a unit ID, in terms of Rapid SCADA this is a device address defined in Administrator.
While another software uses Unit ID = 1.
You can check it by http://modbus.rapidscada.net/First of all, change the device address to 1.
January 9, 2019 at 3:06 pm #4836jeeslo
ParticipantHello friends
Following its recommendations, solve it in the following way:
1. In Administrator the address enter the server port number 502
2. In the Communicator the Address set the number of the slave ID 01It worked correctly
Thank you very much for your valuable support
-
AuthorPosts
- You must be logged in to reply to this topic.