rob5029

Changing a faulty GuardLogix devicenet node

1 post in this topic

We have a Smartguard 600 with devicenet slave nodes running a safety system, so all nodes are safety locked. one of the I/O Nodes has developed a fault and needs changing, so I got the replacement node from the spares cupboard, and configured it with RSNetworx for Devicenet. when I downloaded the settings to the new module from our saved configuration file it told me that there was a version mismatch. the old module was version 1.002 and the new module is version 1.003 I clicked ok to continue and downloaded the configuration, including the safety network number, and re-locked the node. it now sits on the network with the NS light flashing green, which the manual states is waiting for communication from master node. But the master node will not pick up the new node, and still says that there is a system fault. is this because of the change in hardware version? If I have to unlock the SmartGuard 600 master node, our safety procedure states that the entire system will require retesting, which is not an easy thing to do and not desirable in the middle of a run. any ideas of a way round this? I've been unable to obtain an older module with the matching version, and I don't think I can downgrade the new one. many thanks Rob.

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