Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Modbus TCP with S7-1500 - Error Status= 80A3 after a while

Created by: Rafael Fernandes at: 12/4/2014 7:50 PM (4 Replies)

Rating (1)

Thanks 4

5 Entries

12/4/2014 7:50 PM	Rate (0)
Rafael Fernandes Experienced Member Joined: 2/19/2014 Last visit: 10/15/2024 Posts: 8 Rating: (0)	Hello, We are comissioning a system with a S7-1500 [CPU 1516-3 PN/DP] Firmware 1.6 (TIA V13 upd 6) , the Siemens PLC uses the block MB_SERVER to communication with a Modbus Master (a ControlLogix using the Prosoft Modbus Module MVI56E-MNETR). The Modbus Server ConnectionId is = 1, and the Interface Id is 64 (X1 Interface), the block runs in the OB1 cycle. During the comissioning I noticed some weird status errors : 16#80C4, 16#80C5 . I didn't know exacly the errors meaning, but I assume that they are internal status (like connect, disconnect, timeout, etc...) , but the communication works fine. After some time the communication stops working and the block call MB_SERVER in the Siemens PLC remains with Error=True and Status= 80A3. Could you please help us ? Do you have some idea what can be wrong ? I have also a Profinet IO Controller, a HMI in the X1 Interface, and the Simatic NET communication in the X2 Interface (corporate network), do you think they can affect the Modbus comms ? ------------ new subject after Splitting from Sample Program: Modbus TCP with S7-1500
	Last edited by: CS Moderator at: 12/8/2014 12:37 PM splitting Industrial Automation / IT Systems Analyst
Suggestion To thank Quote Answer

12/10/2014 3:47 PM	Rate (1)
Fafner Silver Member Joined: 3/20/2013 Last visit: 4/3/2024 Posts: 676 Rating: (44)	use the online help function of the TIA portal (it is F1 as a shortcut)! "With the "MB_SERVER" instruction, in addition to the errors listed in the tables, errors caused by the communication instructions ("TCON", "TDISCON", "TSEND", "TRCV", "T_DIAG" and "T_RESET") used by the instruction can occur." E.g. the 80A3 is with TCON the following: 80A3 ID is used by a connection created by the user program, which uses the same connection description at the CONNECT parameter. 1 80C4 Temporary communication error: The connection cannot be established to the partner at this time. The interface is receiving new parameter settings or the connection is being established. 1 80C5 Connection terminated by the communication partner.
	Best Regards, Fafner
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users NPlayer Prasanna_Prasanna

12/11/2014 9:03 AM	Rate (0)
Pittiplatsch Posts: 1368 Rating: (126)	So...in summary...I would suggest you to change the Connection ID to another, unused value!
Pittiplatsch Posts: 1368 Rating: (126)
Suggestion To thank Quote Answer

2/23/2015 2:50 PM	Rate (0)
Rafael Fernandes Experienced Member Joined: 2/19/2014 Last visit: 10/15/2024 Posts: 8 Rating: (0)	Hello guys, Thanks for your help, we found that the problem was in the Prosoft communication card, it connected to the Siemens PLC, requested the Holding Register data and then disconnected, after that it connected again requested the Holding Register data and then disconnected, and so on. This seemed to stress the Modbus communication in the Siemens CPU, so the Prosoft sent us the correct firmware and the communication is working fine now. Item solved !
	Industrial Automation / IT Systems Analyst
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users Fafner Min_Moderator

5/12/2015 3:25 PM	Rate (0)
Min_Moderator Platinum Member Joined: 9/3/2014 Last visit: 3/13/2019 Posts: 4766 Rating: (122)	New question published by AutoGen_1065444 is split to a separate thread with the subject Modbus client error. Best regards Min_Moderator

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on