Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Persistent Error A083 with PCS7 Chart

Created by: Thanasis Tsiakmakis at: 11/12/2012 6:34 PM (5 Replies)

Rating (0)

Thanks 0

6 Entries

11/12/2012 6:34 PM	Rate (0)
Thanasis Tsiakmakis Posts: 6 Rating: (1)	Hello! I am experiencing a quite peculiar problem in an installation. We have various communications via Profibus and Modbus and a redundant CPU417-4H and CP443-1. The problem in question is that in one Chart we have two Modbus modules. The connection Id is different and they are triggered separately. But the problem is that only the second one is functioning correctly. The first one is continually giving the stated error. I have even disabled the second one but to no avail. The modules are reading/writing in different DB, the same data. Finally I have restarted the PLCs, but due to the impossibility of a full stop I have downloaded the hardware in Run Mode. This has the effect of restarting each PLC separately, thous passing through OB100 and reconfiguring if need be the Modbus module. Cheers, Thanasis Tsiakmakis
Thanasis Tsiakmakis Posts: 6 Rating: (1)
Suggestion To thank Quote Answer

11/12/2012 9:05 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi, did you a restart of the PLCs after you inserted the modbus instances? A083 means that you set ENQ to TRUE before the current modbus telegram was finished. You must wait until ERROR or DONE is set, after this you can start a new telegram. Please check it. Could you attach the chart here? Wüstenräuber

Suggestion To thank Quote Answer

11/13/2012 8:55 AM	Rate (0)
Thanasis Tsiakmakis Posts: 6 Rating: (1)	Dear Wüstenräuber, I have restarted the PLCs by tricking them into downloading the hardware again, so that the installation won´t stop. I have observed that whenever I make a petition to read/write I get directly an error in the module and no busy or done is ever activated, they are always 0. I attach the chart. It is the one giving me the problem. Attachment UOperate.pdf (393 Downloads)
Thanasis Tsiakmakis Posts: 6 Rating: (1)
Suggestion To thank Quote Answer

11/13/2012 10:07 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Thanasis, which Modbus block and version do you use? Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

11/13/2012 10:35 AM	Rate (0)
Thanasis Tsiakmakis Posts: 6 Rating: (1)	Hello! It's Open Modbus/TCP Redundant Communication. MB_REDCL Version 2.0. FB909 by default. Cheers, Thanasis
Thanasis Tsiakmakis Posts: 6 Rating: (1)
Suggestion To thank Quote Answer

11/13/2012 11:01 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Thanasis, there is a hotfix available regarding the communication lock up after restart. You can order it at it4.industry@siemens.com by telling them the license number of the Modbus library. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on