Problems with toolkit

Hi All

I have a network up and running and i have wanted to make a few minor changes and i am getting messages saying cannot save to network. there is some other info from the command line prompt, below and you point me in the right direction.....

I should add the cbus side is working fine, its just making a few alterations

coppy from command line

Clipsal C-Gate(TM) v2.6.0 (build 2213)
Hardware key: Key initialize failed (DRIVER NOT INSTALLED)
License file found:
Customer Name: PUBLIC
Location: PUBLIC
License type: PUBLIC
Network licenses: 2
Expiry: 31 December 2099
Total network licenses: 2
20070313-190300 803 cmd3 - Host:/127.0.0.1 opened command interface from port: 3
784
20070313-190303 751 //SPRING - Tag information changed at tag address: //SPRING/
Installation oldtag: null newtag: null
20070313-190303 742 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Network cr
eated type=CNI address=192.168.204.6:10001
20070313-190309 751 //SPRING - Tag information changed at tag address: //SPRING/
!3b089f30-14af-1029-aa0a-d526d34dcc75 oldtag: Springfield newtag: Springfield
20070313-190329 751 //SPRING - Tag information changed at tag address: //SPRING/
!3b089f30-14af-1029-aa0a-d526d34dcc75 oldtag: Springfield newtag: Springfield
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 9 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 10 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 11 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 12 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 14 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 15 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 17 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 18 (suggests unit address conflict)
20070313-190331 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 19 (suggests unit address conflict)
20070313-190332 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 23 (suggests unit address conflict)
20070313-190332 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 27 (suggests unit address conflict)
20070313-190353 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 1 (suggests unit address conflict)
20070313-190353 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 1 (suggests unit address conflict)
20070313-190353 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 1 (suggests unit address conflict)
20070313-190354 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 3 (suggests unit address conflict)
20070313-190354 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 3 (suggests unit address conflict)
20070313-190354 840 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 Orphaned c
ommand reply for unit 3 (suggests unit address conflict)

 

Very often the Network will appear to be working fine.. you can switch loads off an on, sensors work etc.. then you connect Toolkit and have problems, cant save units, cant scan etc and its usually a Network problem..

The switching of loads from Input Units etc is a really really short message on the bus that also has an inbuilt correction method.. when Toolkit hooks up to a Network huge volumes of traffic are generated and problems on the Network become more apparent..

I'd still be checking the Network for all the usual culprits, low unit voltages, lack of burden, cable length, number of units etc..

 

Thanks Duncan

No Burden !!! i had my CNI with burden enabled and removed to work on another network, cairfully switching the burden off on it for the new network and enabling another burden..... compleatly forgot to do the same on my own network !!!!

Now i can alter the network, i am still getting some errors in the java app

20070314-062947 824 //SPRING/254 3b089f30-14af-1029-aa0a-d526d34dcc75 unknown cbus response: 0510CA0021

But will look at other sections of the network and see if i can spot a problem

Thanks again

 

As I read through Duncan's post which is very informative, I found myself making a mental bet (about $100 worth) that the culprit would be burden. In line with this, the plug in burden is the way to go. You can see it even bite it between your teeth. There is no guessing if there is a burden on the network like your situation. I also believe the components on the plug in burden are electronically superior to the equiv connected to the network via an output unit (surface mount).

By the way, I win a $100 in the imaginary world and that Duncan chap seems very handy for someone who is "Banned"

 

Is the "error" you're seeing in the Java Window (CGate) actually causing issues in any Toolkit operations or is Toolkit working fine now?

 

Congrats on the win, I briefly imagined sending you the $100 so everyone is square now

 

Ahh yes.. there's a capacitor in there which can discharge across your tongue if you have the pluggy end in your mouth

 

Ahhhh the old charged capacitor trick.

Gee I had some fun with that in electronics first and second year.