Forum Home › Forums › Runtime Bugs › Communicator Bugs › Communication stops on device timeout
- This topic has 8 replies, 2 voices, and was last updated 4 years, 7 months ago by
Mikhail.
-
AuthorPosts
-
April 12, 2021 at 12:31 pm #8709
Jure
ParticipantI have two devices on communication line, both of them modbus. Everything works OK if both are working, but If i turn off one communication with it times out and whole communication line stops:
Should i change settings to prevent this, or what would be solution?
http://imgur.com/a/BP6llmoApril 12, 2021 at 1:34 pm #8712
MikhailModeratorOn the screenshot the line seems working.
Also please provide a screenshot of your communication channel properties.April 12, 2021 at 1:43 pm #8714Jure
ParticipantIf you look at last line it says:”Establish a TCP connection with 192.168.95.112:502″ it is waiting there for few seconds without communicating with other device which is still turned ON.
With turning off the device i mean turning off the simulator on some PC. Other device that is PLC is still working.With communication channel you mean this?
http://imgur.com/a/motJS49April 13, 2021 at 3:34 pm #8725
MikhailModeratorLine Parameters – Main Parameters, then Communication Channel group box and the Properties button.
it is waiting there for few seconds without communicating with other device which is still turned ON
What date and time on your screenshot?
April 14, 2021 at 6:09 am #8730Jure
ParticipantSettings:
https://imgur.com/Oz20xiYCommunication log:
https://imgur.com/TeDtNY0As you can see it takes 25 seconds between two reads. But it should read every second. So if I send command in this 25 second window it won’t be sent. Should every device be on it’s own line?
-
This reply was modified 4 years, 7 months ago by
Jure.
April 14, 2021 at 6:18 am #8732Jure
ParticipantSorry second screenshot was wrong:
https://imgur.com/a/XnMcZ6SApril 14, 2021 at 2:01 pm #8749
MikhailModeratorIt takes time for waiting 192.168.95.112 at 08:07:43.
I don’t see the 1st screenshot that may be contains communication channel properties. Could you post it again?April 15, 2021 at 6:13 am #8752Jure
ParticipantCorrect, it waits because 192.168.95.112 is offline. But because of that 192.168.95.10 is unresponsive.
I hope that properties work now:
http://imgur.com/a/mV5s7a3April 15, 2021 at 11:36 am #8760
MikhailModeratorYou could increase the Reconnect parameter to 30 or 60, for example, to reduce latency when a device is offline.
Also it can be a good idea to split polling into several communication lines that work in parallel. -
This reply was modified 4 years, 7 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.