PWR LED error codes

[XetAutomation]

Hello,

I have been using a ENET to RS-232 device for communication to an inverter undergoing lightning tests.  A recent failure of the inverter during this test appears to have damaged the port 1 interface on the NI 232.

LED for Port 1 is always on.

Just following this test, the other ports were verified and checked out fine.  Now, several weeks later after power cycling the NI 232 device I see an error indication on the PWR/RDY LED.  The code looks to be 25.  Is there any listing of these codes available through the web?  What is code 25?  The NI trouble shooting wizard seems to talk to this device and indicate all com ports have failed, but I don't trust this because I can't ping the device or discover it on the network.

Thanks

-xetautomation

[Wayne.C]

XA,

I far as I know only NI knows what the flash codes mean.  I suggest you call NI directly.

As far as the ENET-232 device goes, it has most likely been damaged and the symptoms will probably continue to get worse as damaged silicon fails completely.  There is also the potential for damage to other ENET devices connected to the network.   If you aren't already, I suggest using an optical  isolator when using 232 or 485 to communicate with inverters.  Especially where surge or lightning testing is concerned.

[Scott-M]

Hi,

Error 25 would indicate that your device is failing a loopback test while starting up. If this behavior is repeatable and is affecting the function of your device you can call us at 1-866-ASK-MYNI and we can look into getting it fixed for you.

Thanks

Scott M.

[JasonSmith]

The power-on loopback test can fail if a connected device is transmitting data to the box while it is powering on. Try disconnecting any cables then power-cycling the box. If that doesn't work, it sounds like it probably needs to be repaired.

-Jason S.

[AtteqAutomation]

A follow up for those interested in the solution:

The damage was first suspected to be just in the RS-232 device, so I replaced this Intersil part.  As luck would have it, this was not the only problem and the reported loopback error would not clear.  Replacing the Exar XR16C864 part was going to be a bit harder.  The only evidence that this might be successful was that the unit was responding to test requests, and the part was getting a bit hot to the touch.  Real scientific... sigh.  But, without additional troubleshooting tools it was the only method available.  Well, it worked.  With these two parts replaced the unit came up and is running fine.  I don't recommend this approach unless you are willing to spend some time doing this, and don't mind the risk that it might be a project in the waste basket.

Thanks for the responses.  And Jason, thanks for that pointer about the serial traffic during boot.  This one got me after the unit was running and I thought it was yet another problem until I decided to disconnect the serial port.  Your post confirmed the issue.

-xetautomation