Diagnosing network issues

Can anyone suggest some possible causes of the following?

Code:

14:52:02 WRITE NET close 52 NET open 52 NET flush 52 NET sync 52 
14:52:02 [ 0] 200 OK: //ALL/52 
14:52:03 [ 1] 120-initializing 
14:52:03 [ 0] 120-opening port 
14:52:06 [ 3] 120-starting network threads 
14:52:06 [ 0] 120-pci reset 
14:52:15 [ 9] 120-checking connection 
14:52:15 [ 0] 120-reconnecting to bridged networks 14:52:15 [ 0] 120-open complete 14:52:15 [ 0] 200 OK: //ALL/52 
14:52:15 [ 0] 200 OK. 
14:52:15 [ 0] 120-Net Sync: started 
14:52:15 [ 0] 120-Net Sync: synchronising PCIs 
14:52:22 [ 7] 120-Net Sync: starting network discovery 
14:52:24 [ 2] 120-Net Sync: Unit count: 19 
14:52:24 [ 0] 120-Net Sync: Unit error count: 0 
14:52:24 [ 0] 120-Net Sync: Units at: 50, 51, 52, 53, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 250, 251 
14:52:24 [ 0] 120-Net Sync: Unit errors at: 
14:52:30 [ 6] 120-Net Sync: address=50 type=KEY1 version=1.2.67 serial=100067.2270 catalog=5031N 
14:52:33 [ 3] 120-Net Sync: address=51 type=KEY1 version=1.2.67 serial=100073.767 catalog=5031N 
14:52:48 [ 15] 120-Net Sync: address=52 type=KEY1 version=1.2.67 serial=100073.727 catalog=5031N 
14:53:21 [ 33] 120-Net Sync: address=53 type=KEY1 version=1.2.67 serial={none} catalog=5031N 
14:53:21 [ 0] 120-Net Sync: address=100 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=101 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=102 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=103 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=104 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=105 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=106 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=107 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=108 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=109 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=110 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=111 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=112 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=250 error reading type and version 
14:53:21 [ 0] 120-Net Sync: address=251 error reading type and version 
14:53:24 [ 3] 200 OK

Unfortunately I have nobody on site to investigate from the software end but there are people who can check voltages etc.

Suggestions?

 

Run the C-Bus Diagnostic Software to see if you have any communications problems. If so, then check:

• burdens
• C-Bus voltage
• electrical interference
• number of C-Bus units
• short circuits
• etc

 

A bit more info:

The end user has reported that occasionally they lose communications to the network from the (Citect) head end, and that rebooting the PC and restarting the CNI tends to fix it. The network has worked fine for several years so we're looking for what might have failed or changed to cause the problem.

There's nobody on site that can do much (and I'm on holiday at the moment so can't even make an emergency visit to site). It happens that I wrote a web interface that allows them to flush/sync a network and they were able to copy+paste the results via email to me, which I posted here (which was hard work on a phone!).

They're able to control things via the pushbuttons on the units but it's a large public building and they have an event on at the weekend where having to control everything manually like that would be a problem. I might try to talk them through creating a cable to short out the "remote on" pair as a temporary workaround (since events usually needs "all on"). But ideally I am hoping that someone will see the above and say "I saw that once, the cause was XXX".

 

OK, I've now had the opportunity to go to site to test.

A resync (as per first post to this thread) threw up no problems whatsoever. I connected to the network via a PCI and ran the C-Bus Diagnostic reliability test on it, and everything came back perfect. So, as is the way of these things, when the doctor arrived the patient no longer had any symptoms.

This either means that the problem is intermittent or has now fixed itself; any suggestions as to what else to try to make it fail during testing if there's still a fault?

 

I sometimes associate intermittent with water leaks.

 

Interesting thought and entirely possible with this site, thanks!

I'll get site to investigate further.