shoelesscraig
Member
Okay, I've got a NET ENI hooked to a SLC 5/03. Its been that way for years, works great.
Recently, I have had a problem however. When I go into Linx, the node has started coming up with a red X over it. But, I can still ping the IP address. And...and here's the kicker...the SLC is still communicating with our main controller (a Controllogix) with no problems. The SLC also uses the ENI to talk to the CLX and this still works great...messages in the CLX are showing "done" and info is being transferred.
So, I know that the ENI is working to a degree, but it will not show up in Linx so that I can online with the SLC. First time I've seen this problem. Usually it just quits working altogether. The only thing that I know that has been changed in the recent past was that the firmware was updated to OS302. The ENI is the newer "series D" I believe it is called. So I can't really see how upgrading the firware when coupled to a newer model ENI would be a problem.
Any ideas of what I should try?
Recently, I have had a problem however. When I go into Linx, the node has started coming up with a red X over it. But, I can still ping the IP address. And...and here's the kicker...the SLC is still communicating with our main controller (a Controllogix) with no problems. The SLC also uses the ENI to talk to the CLX and this still works great...messages in the CLX are showing "done" and info is being transferred.
So, I know that the ENI is working to a degree, but it will not show up in Linx so that I can online with the SLC. First time I've seen this problem. Usually it just quits working altogether. The only thing that I know that has been changed in the recent past was that the firmware was updated to OS302. The ENI is the newer "series D" I believe it is called. So I can't really see how upgrading the firware when coupled to a newer model ENI would be a problem.
Any ideas of what I should try?