Error whilst trying to Scan... any ideas?

I seem to be getting this error all of a sudden when trying to scan the network. This is from the Java window.

Any clues as to what the cause could be?

20111015-131101 824 //SALTFORD/254 a7b6b760-d954-102e-ab19-d872e31563e7 unknown
response: ~~~ ***
20111015-131137 824 //SALTFORD/254/172 a80a2e90-d954-102e-ad3c-d872e31563e7 bad
SAL response: 36011D4101810036010208FF0000F8C5
20111015-131137 824 //SALTFORD/254/172 a80a2e90-d954-102e-ad3c-d872e31563e7 unkn
own cbus response: 36011D4101810036010208FF0000F8C5
20111015-131151 824 //SALTFORD/254/56 a7b70580-d954-102e-ab1b-d872e31563e7 unkno
wn SAL command: 0174017601770175016D016F0BC5
20111015-131151 824 //SALTFORD/254/56 a7b70580-d954-102e-ab1b-d872e31563e7 unkno
wn cbus response: 0174017601770175016D016F0BC5
Exception in thread "CBusReceiver" java.lang.StringIndexOutOfBoundsException: St
ring index out of range: 4
at java.lang.String.substring(Unknown Source)
at en.a(ProGuard:83)
at en.a(ProGuard:52)
at com.clipsal.cgate.cbus.app.aircon.CBusAirConditioningApplication.a(Pr
oGuard:295)
at gI.b(ProGuard:193)
at cG.a(ProGuard:3787)
at cG.a(ProGuard:3509)
at iJ.a(ProGuard:121)
at iJ.run(ProGuard:77)
at java.lang.Thread.run(Unknown Source)​

Any help would be very much appriciated.

 

Are you using a USB PCI? There have been some problems with the old USB driver. Updating to the last ToolKit fixes the driver.

 

No it's an Ethernet CNI. Interestingly I also have a Wiser and I get the same error connecting via the CNI on the Wiser.

One thing I thought it might me. I recently installed theSkyNet.org Java software. I stopped it and deinstalled but wonder if that might have messed up Java somehow. I have tried removing and reinstalling Java so I would guess not but wondered if that might be a factor.

Cheers


Jon

 

Our Java expert is away for a few days. Hopefully he can suggest something when he gets back.

 

tried diconnecting the CNI from cbus and power cycling and it seemd to start scanning then same error. I will try the tool kit on a fresh machine and see how that goes.

Cheers


Jon

 

I've not tried the fresh Java install but here's some text which might give your guy a clue...

Clipsal C-Gate(TM) v2.8.0 (build 2316)
Logging to file: event.log
20111017-211647 803 cmd3 - Host:127.0.0.1/127.0.0.1 opened command interface fro
m port: 49309
20111017-211655 751 //SALTFORD - Tag information changed at tag address: //SALTF
ORD/Installation oldtag: null newtag: null
20111017-211655 742 //SALTFORD/254 e2052eb0-db2a-102e-bc2c-d9810d1f6e5c Network
created type=CNI address=192.168.1.9:10001
20111017-211700 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn SAL command: 0174797679777975796D9BC5
20111017-211700 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn cbus response: 0174797679777975796D9BC5
20111017-211700 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 05011D010E0005010201000014C5
20111017-211700 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 05011D010E0005010201000014C5
20111017-211700 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn SAL command: 796FDBC5
20111017-211700 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn cbus response: 796FDBC5
20111017-211700 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 36011D41017F0036010208FF0000FAC5
20111017-211700 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 36011D41017F0036010208FF0000FAC5
Exception in thread "CBusReceiver" java.lang.StringIndexOutOfBoundsException: St
ring index out of range: 4
at java.lang.String.substring(Unknown Source)
at en.a(ProGuard:83)
at en.a(ProGuard:52)
at com.clipsal.cgate.cbus.app.aircon.CBusAirConditioningApplication.a(Pr
oGuard:295)
at gI.b(ProGuard:193)
at cG.a(ProGuard:3787)
at cG.a(ProGuard:3509)
at iJ.a(ProGuard:121)
at iJ.run(ProGuard:77)
at java.lang.Thread.run(Unknown Source)
20111017-211705 824 //SALTFORD/254 e2052eb0-db2a-102e-bc2c-d9810d1f6e5c unknown
response: ~~~ ***
20111017-211744 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 15011F13EA001DC5
20111017-211744 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 15011F13EA001DC5
20111017-211757 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn SAL command: 0174797679777975796D9BC5
20111017-211757 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn cbus response: 0174797679777975796D9BC5
20111017-211757 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 05011D010E0005010201000014C5
20111017-211757 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 05011D010E0005010201000014C5
20111017-211758 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn SAL command: 796FDBC5
20111017-211758 824 //SALTFORD/254/56 e2057cd0-db2a-102e-bc2e-d9810d1f6e5c unkno
wn cbus response: 796FDBC5
Exception in thread "CBusReceiver" java.lang.StringIndexOutOfBoundsException: St
ring index out of range: 4
at java.lang.String.substring(Unknown Source)
at en.a(ProGuard:83)
at en.a(ProGuard:52)
at com.clipsal.cgate.cbus.app.aircon.CBusAirConditioningApplication.a(Pr
oGuard:295)
at gI.b(ProGuard:193)
at cG.a(ProGuard:3787)
at cG.a(ProGuard:3509)
at iJ.a(ProGuard:121)
at iJ.run(ProGuard:77)
at java.lang.Thread.run(Unknown Source)
20111017-211820 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own SAL command: 79012F011D610116000010C5
20111017-211820 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 79012F011D610116000010C5
20111017-211821 824 //SALTFORD/254/203 e2445a90-db2a-102e-bdca-d9810d1f6e5c unkn
own SAL command: 02021D0FC5
20111017-211821 824 //SALTFORD/254/203 e2445a90-db2a-102e-bdca-d9810d1f6e5c unkn
own cbus response: 02021D0FC5
20111017-211821 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 2F010260FF000000BEC5
20111017-211821 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 2F010260FF000000BEC5
Exception in thread "CBusReceiver" java.lang.StringIndexOutOfBoundsException: St
ring index out of range: 12
at java.lang.String.substring(Unknown Source)
at com.clipsal.cgate.cbus.app.enablecontrol.CBusEnableControlApplication
.a(ProGuard:475)
at gI.b(ProGuard:193)
at cG.a(ProGuard:3787)
at cG.a(ProGuard:3509)
at iJ.a(ProGuard:121)
at iJ.run(ProGuard:77)
at java.lang.Thread.run(Unknown Source)
20111017-211928 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own SAL command: 79012F011D610116000010C5
20111017-211928 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 79012F011D610116000010C5
20111017-211928 824 //SALTFORD/254/203 e2445a90-db2a-102e-bdca-d9810d1f6e5c unkn
own SAL command: 02021D0FC5
20111017-211928 824 //SALTFORD/254/203 e2445a90-db2a-102e-bdca-d9810d1f6e5c unkn
own cbus response: 02021D0FC5
20111017-211928 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c bad
SAL response: 2F010260FF000000BEC5
20111017-211928 824 //SALTFORD/254/172 e2186890-db2a-102e-be4f-d9810d1f6e5c unkn
own cbus response: 2F010260FF000000BEC5
Exception in thread "CBusReceiver" java.lang.StringIndexOutOfBoundsException: St
ring index out of range: 12
at java.lang.String.substring(Unknown Source)
at com.clipsal.cgate.cbus.app.enablecontrol.CBusEnableControlApplication
.a(ProGuard:475)
at gI.b(ProGuard:193)
at cG.a(ProGuard:3787)
at cG.a(ProGuard:3509)
at iJ.a(ProGuard:121)
at iJ.run(ProGuard:77)
at java.lang.Thread.run(Unknown Source)
20111017-211934 824 //SALTFORD/254 e2052eb0-db2a-102e-bc2c-d9810d1f6e5c unknown
response: ~~~ ***
20111017-212151 804 cmd3 - Host:127.0.0.1/127.0.0.1 closed command interface from port: 49309

 

For info; I get the same error with a clean install and tried older toolkit versions.

 

There is a clear pattern of the front part of C-Bus messages being lost. I have not seen this before, except with USB PCIs with the old driver.

To get to the bottom of this, we are probably going to need to see the network traffic between the CNI and C-Gate to see where the missing information is going. What we need is a log of the TCP/IP traffic on your computer for the same period as when this fault occurs. We can then compare the C-Gate log with the Wireshark log to see if we can work out what is going on. It would also help to have C-Gate logging at event level 9.

The best tool for this is Wireshark which is a free download from here.

I would suggest sending these logs to Tech Support and ask them to forward them to myself and Daniel. Refer to this post in your e-mail.

 

The Sky Net Applet

Hi, Darren, I think I have this solved. To fix this I set up a "clean" network but had the restart the CNI and the router on the network.

I believe the problem is running a Java grogramme anywhere on the same network from www.theskynet.org project. This project uses spare computing power to process radio telescope data and their application uses Java. I've been running it on a number of machines. It's the only change to the network I can think of and might explain the missing c-bus data.

I will do some more work to hunt this down but it seems the probable cause.

Thanks for your help. If you still want me to log the data I will if you think it might help others.

Cheers


Jon

 

It would be interesting to know, but probably not worth your time. Thanks for reporting back to us.

 

I will give it a go as I'm still having some problems... I'll get back to you.

Cheers


Jon

 

Hi,

Finally fixed this for good by powering down the whole c-bus supply and restarting. Not sure if it was or it wasn't the skynet app. The network was working fine functionally it was just the Toolkit which was failing. I did start the logging but there is so much going on on that machine with CCTV, Audio and C-Bus it was tricky.

Anyway; restart seems to have fixed it. I'll let you know if it happens again and thanks for your help.

Cheers


Jon