Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Library still fails when the standby connection is lost

Created by: amuz2805 at: 12/20/2018 4:53 AM (4 Replies)

Rating (0)

Thanks 0

5 Entries

12/20/2018 4:53 AM	Rate (0)
amuz2805 Experienced Member Joined: 5/26/2016 Last visit: 10/13/2024 Posts: 3 Rating: (0)	Kaulquappe Hello Zen-Zen, did you use this library? Redundant Modbus/TCP blocks for CPUs 1200 and 1500 available If yes, which errors are reported at STATUS? Regards, Kaulquappe yes, I use that library but it still fails when the standby connection is lost. error statement 16 # 80C4 the library block uses the example 1500_Server_Dev Single ------------------------------------------------------------------------------------------ Split from S7-1500 Redundant Modbus TCP With Honeywell C300 (PCDI). Attachment ERROR_MODBUS.PNG (232 Downloads)
	Last edited by: Jen_Moderator at: 12/20/2018 2:00:16 PM New subject after splitting
Suggestion To thank Quote Answer

12/21/2018 1:41 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello, your screen shot shows error 80C5. This means that the client terminated the connection. As the Modbus server is the passive communication partner, it is up to the client to establish the connection again. The S7 can nothing do than wait. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

12/29/2018 2:40 PM	Rate (0)
amuz2805 Experienced Member Joined: 5/26/2016 Last visit: 10/13/2024 Posts: 3 Rating: (0)	First I want to explain the My Redundant Modbus Configuration I use PLC 1511-1PN and CM 1543-1 Connection 0A to DCS Server A C300 PCDI IP Address = 192.169.12.225 ID = 1 Local Port = 502 Connection 0B to DCS Server B C300 PCDI IP Address = 192.168.12.226 ID = 2 Local Port = 502 Case 1 If connection 0A and connection 0B is connected, on DCS the active connection is connection 0A. Then connection 0A is disturbed, the connection 0B automatically backs up and redundant modbus works without errors Case 2 If connection 0A and connection 0B is connected, on DCS the active connection is connection 0B. Then connection 0B is disturbed, the connection 0A automatically backs up and redundant modbus works without errors Case 3 If connection 0A and connection 0B is connected and on DCS the active connection is connection 0A. Then the connection 0B is disturbed so connection 0A is disturbed too. DCS reads the two connections failed, after 3-5s the connection 0A is normal error code16#80C5 Case 4 If connection 0A and connection 0B is connected and on DCS the active connection is connection 0B. Then the connection 0A is disturbed so connection 0B is disturbed too. DCS reads the two connections failed, after 3-5s the connection 0B is normal error code16#80C5 Case 1 and Case 2, redundant works Case 3 and Case 4, connections that have been disrupted will interfere with normal connections, error code 16#80C5 is there a solution to improve hardware and software and dcs and plc sides? maybe your explanation and solution can solve my case thank you

Suggestion To thank Quote Answer

1/2/2019 9:47 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello, you still did not answer my first question. Do you use the redundant Modbus blocks from TIA or did you program your own redundancy? Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

1/4/2019 12:36 PM	Rate (0)
amuz2805 Experienced Member Joined: 5/26/2016 Last visit: 10/13/2024 Posts: 3 Rating: (0)	Yes, I use modbus block redundant

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on