7/5/2009 1:44 PM | |
Posts: 767 Rating: (69) |
AttachmentComms_Fault.pdf (624 Downloads) |
This contribution was helpful to2 thankful Users |
7/5/2009 3:05 PM | |
Joined: 10/7/2005 Last visit: 1/17/2025 Posts: 3030 Rating: (1058) |
Hello Shahiiee Unfortunately I can't offer youa "smoking gun" solution, instead I propose that you add some simple capture logic to your PLCto store the SFB's 12/13 STATUS word when the ERROR bit goes high. This will help you in narrowing the problem down and you can of cause post the captured values here too. I also have a question for you: You said that "I am using 1 BSend and 1 Brecv (SFB12 & 13) on each side for the send and receive ofdata. The standalone AS side is not generating any errors." Can you please clarify this a bit further (i.e. SFB12&13 call in H system AND SFB12&13 call in standalone AS) Reason for asking is that just in case this is a "oneway"data exchange (i.e. the H system only SFB12 sends and the standalone ASonly SFB13 receives)? If this is the case you canhavea H systems SFB12 BSEND "failure" (as reported by PCS7), but you won't get a fault on the standaloneAS since the SFB13 BRECVdoesn'tknow that new data was meant arrive and as such can't report a problem. This in turn could have such simple causes as bad network connection somwhere or interference etc. Anyway, I hope this helps a little bit and let us know when more info comes to hand. |
Cheers |
|
Follow us on