CNI- C-Bus network problems

The problem Dan was having is unrecoverable, so it would not be intermittent for a while and get worse, it just stops the CNI talking to C-Bus altogether.

When you say the CNI netmask sets itself to nothing, do you mean you do a scan with the IP Utility and it shows up blank? Does it reappear if you re-scan it later?

 

Yep that's right Tim in the ip utility. This happened to the other wiser I had on site as well the cni just stopped connecting. But all the other fields are correct!

 

and yes sometimes it does reappear after a rescan or a power down and power up of the wiser. But when it does re-appear it still doesn't connect to C-bus.

 

Hi Josh,

If you use a browser and connect to the IP of the CNI, what does it show. For example, here's what I get from mine, http://192.168.2.2/

C-Bus status: Client connected from 192.168.2.1
since > 24 hours ago
Network voltage: 28.9V, measured > 24 hours ago
IP Address: 192.168.2.2
Netmask: 255.255.255.0
Gateway: 192.168.2.1
TCP Port: 10001
Unit Address: 26
MAC Address: 00:17D:00:00:xx
Serial Number: xxxxxxxxxx
C-Bus Firmware: 5.2.24
Ethernet Firmware: 0.1.4
Hardware variant: Inline

Are your Wiser and your CNI connected together on a busbar or connected separately?

 

it is on a busbar

I will be going back on site at a later date, can't sign in on it remotely. The wiser and cni pages on the browser wouldn't load last time I was up there. CNI showed up a device on the toolkit. If i restarted the wiser sometimes it would connect but not longer than 5minutes and then offline sometimes complete offline and I couldnt even open the wiser ip address or the cni ip address to view the details you are asking for. But it always found it using the ip utility. Hope that didnt confuse it further.

 

Couple of things I would check because I've seen this before.
1. Verify that there are no conflicting IPs. I normally use arping for detecting this. I've seen setups where someone had another CNI configured for the same IP as the Wiser's CNI. That resulted in their switch getting confused so when the laptop tried to go to the CNI's IP, some packets would go to the first one, some to other with the end result making it look like something was hung.
2. When I see a Wiser not connecting, here are the things I check:
- can I ping the Wiser's IP
- if no, then check the switch/etc in between the host PC and the Wiser. I also check if firewall/antivirus sw has flagged the IP for some reason.
- if yes, can I connect to the Wiser's web server, eg: http://192.168.2.1/ and get the Adobe Flash UI
- if yes for the UI, do I then see it show the normal widgets or do I see it show unable to connect to Wiser
- if it shows unable to connect to Wiser, then I check if remote projector is enabled in the PICED project that I used
- if it shows the normal widgets, but shows no C-Bus connection (the C-Bus icon with a strikethrough), then I go to the browser and do http://192.168.2.2/ to check the CNI status

 

will check these when I head back out there and report back to you with findings, its out of Adelaide unfortunately.

 

Josh, this means that the IP Utility is having difficulty communicating with the CNI, not that the CNI is losing those settings. You may have some kind of network problem on your LAN as Jaya has suggested.

It also sounds like your CNI is bricked, if you can never connect to C-Bus and it is displaying the same flash pattern as described earlier in the thread. One way to check is to visit the CNI's IP address in a browser and see what C-Bus status it reports.

Do you have any idea when the CNI was last able to connect to C-Bus and whether it coincides with any particular event, e.g. you being on site, or did it just happen?

 

The cni connects on the ip utility with no dramas always finds it. It sometimes doesn't load on the browser, and the cni connects cbus when it wants to. On site or not.

Heading back up this week so I will check what is mentioned here.

 

If you are sometimes able to connect to C-Bus then you do not have the same issue as was originally being discussed in this thread, which causes permanent failure of the CNI. It sounds to me like your Ethernet network may be unreliable.

 

Hi.......

Just a little share...
There only 1 application can run with CNI,
So make sure.. That you have already closed another program and closed the grup properly (cbus toolkit , then closed grup)

Then try again connect to wiser..
Please remind, that only 1 program running through CNI

Thanks,

Rgds
Vincent

 

Hi

Maybe you can try to connect CNI directly to your local LAN or computer, setting your cbus toolkit to call cbus through your CNI IP address....
If running well,so The CNI just great.

Thanks

Rgds
Vincent