CNI Issue

I have a CNI that has been working perfectly for nearly 2 years.

This morning I couldn't connect to the C-Bus network using the CNI (via toolkit or the diagnostic utility) or the CNI itself via a browser. It shows on the IP utility scan with the correct IP, Mask, Gateway and Port. Telnet will not connect either.

I can connect with the IP utility but when I leave the IP Utility rescan on it shows the status as Recovered then Online then Offline then Recovered etc.

The C-Bus LED is orange and the Network light flashes Orange/Green, indicating things should be ok.

I have powered off the entire C-Bus network and the CNI power and restarted the switch the CNI is connected to (all other network connections are fine anyway).

Any ideas? Has the CNI just given up on me?

Edit: Interestingly, when connecting to the network using the diagnostic utility and the 5500PC via a serial connection it tells me the PC Interface Details are unknown and no use a version 4.0 or later PCI. The one I have is Firmware 4.5. C-Gate is giving a message about no specification for the unit so using bas CBusUnit.

 

If you cannot connect telnet into the CNI then either the CNI itself has carked it or your ethernet network/firewall configuration has changed.

Has anything recently changed on your network?
Do you have an IP Address conflict with another device on your network?
Do you have a firewall/antivirus running?

 

Hi Newman

Nothing has changed since yesterday.

I have managed to connect via telnet now. The CNI appears to keep restarting itself going from Offline to recover to online and cycling so when it is in the online state I can connect, but it only stays like this for 5-10 secs.

I have also managed to connect with the Diagnostic Utility but again, it disconnected after about 10 secs.

I can change the CNI settings (IP etc) via the IP utility but only by 'retrying' so effectively it is managing to do this during the 10 secs or so it is online.

Sounds sick.

Other the other issue - PCI serial connection I don't understand why the Diagnostic thinks it is < version 4 when the firmware is 4.5?

 

Definitely sounds sick to me. It's probably worth grabbing a multimeter and checking the plug-pack to make sure that's working properly before getting too excited.

On the second issue, some USB to Serial adapters can cause this sort of problem, or more specifically the drivers for these things can do this.
If it's connected to your PC using a native serial port (with no long cables or anything "creative") then it suggests that there's a communication issue with your network. Can you scan successfully in Toolkit? Does everything else work OK?

 

Definitely 12v at the CNI. Will persevere.

For the PCI I am using a Dontronics USB to serial converter. The Dontronics serial end doesn't fit into the PCI (too bulky) so there is a male/female serial cable in between. I have also tried the RJ45-serial cable into the dontronics from the RJ45 serial connection on the PCI. Both connect, but both bring up the version error.

Everything else works fine. Scans etc.

 

I reflashed my CNI using the last published firmware and COB file from Lantronix. It had been out of warranty so I put the latest firmware.

I would also check the lan cable.

 

Hi Tobex

I am running 5.2 firmware. Any chance you can pm the firmware/cob file? I I can get mine stable enough I might be able to upgrade the firmware.

I can't locate the firmware on the Lantronix web site. They've pulled the firmware from the UDS-10 link.

It appears the UDS-10 (which the CNI is based on) is no longer supported. Raises the question - what's are current CNI's made with?

Thanks

Andrew.

 

Thanks Ashleigh.

A closer look shows the firmware appears the same for both (although USD-10) isn't available via the discontinued link on their web site. Reason for thinking it was a UDS-10 is that their device installer shows the following as USD-10/Cobox 5.X


Unfortunately I can't get the CNI to stay online long enough to do anything. Scans ok, c-bus voltage ok, 12v supply ok, both lights orange on unit but can't reliably ping,telnet etc.

Real pain. Think it is time to replace.

 

I have several of the Cobox modules in stock. If you wish to send me one of these broken CNI modules I can determine if I can refresh the function by replacing the COBOX module.

I never thought I would have a use for these !

 

Thanks Tobex. The wonderful folks at CIS are replacing the unit under warranty.