Sign in to follow this  
Followers 0
bishop

RS 5000 ethernet module issue

3 posts in this topic

Hi we're using the RS loginx 5000 on a clients site, and about 3 weeks ago the PLC went into stop mode - but nobody noticed because the ethernet module kept transmitting the last data it received and so the SCADA showed that all was well. Is this normal?

Share this post


Link to post
Share on other sites
Is it a case of the ethernet module not keeping on transmitting but wherever the data is being recieved it is just not recieving any new data?, I have come acrzoss similar scenarios in the past, regardless of communication method used, where a PLC has failed and the last data recieved is what is seen, Idealy some kind of active watchdog handshaking would be used to monitor the link, so that failures would be noticed earlier

Share this post


Link to post
Share on other sites
When an Input module connection fails, the Input tag values remain at whatever values they were before the connection failure. The usual method for detecting a failed connection is to use a GSV instruction to examine the Module object's EntryStatus value. See the Help file "GSV/SSV Objects" topic and multiple threads on this Forum and other Forums. ControlLogix controllers have RUN, Remote RUN, Remote PROG, PROG, Recoverable Major Fault, and Unrecoverable Major Fault modes. "STOP" sounds like "PROG" mode or "Fault" mode.... which one was it ? The controller cannot go to "PROG" mode without being commanded to do so, but it can go to "FAULT" mode in the event of a program fault.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0