Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

AG_LSEND Status 8181H though Partner CPU is in STOP mode

Created by: ARC at: 2/17/2009 4:42 PM (5 Replies)

Rating (0)

Thanks 0

6 Entries

2/17/2009 4:42 PM	Rate (0)
ARC Posts: 5 Rating: (0)	Dear all, I have5 S7 400 Stations in one Ethernet Network of 100MBPS via CP 443-1. ISO on TCP connectionis configured. Keep Alive is set to Default 30 AG_LSEND/AG_LRECV is being called every 100ms. AG_Lsend is being triggerd only when done or error with error status other than 7000H is reported. AG_LSEND/AG_LRECV not called for 2 Sec if Error Status 8304H = No Connection is Reported The System is working fine as long all 5 Stations are working fine. The problem is when any one CPU say CPU Agoes to stop and the CP A remains in Run Mode. The status in the partner Station ie CPU B,C.D & E in AG_LSENDfor CPU A remains 8181H. This causes High Bus Load and the communication becomes very slow. Where as if the CP Agoes to Stop CPU B,C.D & E in AG_LSEND instantly reports 8304H. This Cause instant rejection of task and thus bus speed remains normal. Why does it not report error 8304H or any other statewhen the CPU goes to Stop? What should be the setting of Keep Alive in CP Configuration? What Should I do when Status 8181H is for long? Cansomeone please help me resolve the issue. Thanks and regards ARC
ARC Posts: 5 Rating: (0)	Last edited by: ARC at: 2/17/2009 5:03 PM Last edited by: ARC at: 2/17/2009 4:46 PM Last edited by: ARC at: 2/17/2009 4:45 PM
Suggestion To thank Quote Answer

2/18/2009 3:38 PM	Rate (0)
J_Bell Posts: 5822 Rating: (411)	Dear ARC, well, this may get a pretty long subject but first of all I would like to know what version of the CP 443-1 you use, to get to know this I need to know the Order number and the exact Firmware revision running on the CP. Best regards J_Bell
J_Bell Posts: 5822 Rating: (411)
Suggestion To thank Quote Answer

2/18/2009 4:55 PM	Rate (0)
ARC Posts: 5 Rating: (0)	Hello Bell The Order No. of the CP is 6GK7 443-1EX11 0XE0. Firmware version running in the CP is Ver 2.6. Order no. of the CPU is 6ES7 414-2XK05 0AB0. Firmware version running in the CPU is Ver. 5.1. Thanks and regards ARC
ARC Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

2/19/2009 11:41 AM	Rate (0)
J_Bell Posts: 5822 Rating: (411)	Dear ARC, well... I think one thing could be tried first of all. The Firmware you use with the CP 443-1 EX 11 is not the latest one. As far as I know some issues got solved with the latest version which might be found at: CP 443-1 Firmware Update V2.7 and Unrestricted Use on Every Hardware Release (6GK7443-1EX10-0XE0 and 6GK7443-1EX11-0XE0) Maybe this already fixes your issues. Best regards J_Bell
J_Bell Posts: 5822 Rating: (411)
Suggestion To thank Quote Answer

3/2/2009 6:46 AM	Rate (0)
ARC Posts: 5 Rating: (0)	Hello J_Bell Thanks for the information. Itried withversion 2.7 but the result was same. FC 50 AG_LSEND does not report any error when the parner CPU goes to stop. It Keeps on reporting 8181H thus occuping the resource . This in turn reduces the Bus speed considerably. Can I stop the CP if the CPU goes to stop? or Can I reset/break the connection when it is busy for long and thus force it to report 8304H? Regards ARC
ARC Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

3/17/2009 2:01 PM	Rate (0)
J_Bell Posts: 5822 Rating: (411)	Dear ARC, well... I was thinking about this situation together with a colleague of mine and we came to the conclusion that a slow down of the communication, especially a rise of the telegrams may not happen. The point is, if the CPU is in Stop mode the CP may store some data within its cue but as soon as the cue is filled the Window size must be 0. So if the TCP Window is 0 the emitter is not allowed to send anything only the receiver would indicate the change of the Window and than the emitter may send something again. Well, the result would be, in my mind, that you may not finish your send order and you have to wait until the CPU has finished the receive, as soon as it is back in run. In this situation you may not send another thing on this connection but the communication with the other nodes should not be interfered at all... If you still think you have too much traffic to the PLC which is in Stop please take a Ethernet monitoring tool to monitor the traffic and post this file here. Best regards J_Bell
J_Bell Posts: 5822 Rating: (411)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on