Hi I have being using 1.11 succesffully but cannot get 1.12 to work Extract from 1.11 and 1.12 logs plus attachements. I am using usb to serial as pc has no serial ports. Any timing settings I can adjust? 1.12 20120611-131836 755 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 InterfaceState=opening 20120611-131836 757 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 State=new Previous=(unchanged) Reason=Interface Opening 20120611-131836 766 cmd3 - Response: [157] 120-initializing 20120611-131837 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial attempt at baud 9600 20120611-131837 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Tx: ~~~~~~~~~ 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ~ 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ~ 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ? 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ? 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ~ 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ~ 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: 5 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Tx: ****** 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: * 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: * 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: * 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: * 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: % 20120611-131838 799 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 Serial Rx: ? 20120611-131838 757 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 State=new Previous=(unchanged) Reason=starting threads 20120611-131838 790 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 rx thread init 20120611-131838 899 sys Debug: New Command Context: cc003 = Network 254 pci reset 20120611-131838 735 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 cc003 sent cmd: || 20120611-131838 734 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 response: || processed by network. 20120611-131838 766 cmd3 - Response: [157] 120-opening port 20120611-131838 766 cmd3 - Response: [157] 120-starting network threads 20120611-131838 735 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 cc003 sent cmd: @1A2001 20120611-131840 757 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 command timed out: @1A2001 after 2000ms, retry limit of 0 reached 20120611-131840 757 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 command-fail-count=1 unit=-1 reason=no response (@1A2001) 20120611-131840 735 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 cc003 sent cmd: ~~~ *** 20120611-131840 734 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 response: ~~~ *** processed by network. 20120611-131840 824 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 unknown response: ~~~ *** 20120611-131840 735 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 cc003 sent cmd: 1A2001 20120611-131840 734 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 response: 80?EC?~?5**??1A?? processed by network. 20120611-131840 824 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 unknown response: 80?EC?~?5**??1A?? 20120611-131846 757 //CORSTOWN/254 6d9cc820-95ed-102f-86e4-d0241371ca92 command timed out: 1A2001 after 6000ms, retry limit of 0 reached 1.11 20120611-130315 757 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a State=new Previous=(unchanged) Reason=Interface Opening 20120611-130315 766 cmd3 - Response: [152] 120-initializing 20120611-130316 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial attempt at baud 9600 20120611-130316 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Tx: ~~~~~~~~~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: ~ 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Tx: ****** 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: * 20120611-130317 799 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a Serial Rx: 20120611-130317 757 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a State=new Previous=(unchanged) Reason=starting threads 20120611-130317 790 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a rx thread init 20120611-130317 999 sys RegistrationQueue : added syncer for network 254 20120611-130317 735 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a sent cmd: || 20120611-130317 766 cmd3 - Response: [152] 120-opening port 20120611-130317 766 cmd3 - Response: [152] 120-starting network threads 20120611-130317 999 sys RegistrationQueue : found syncer for network 254 20120611-130317 999 sys RegistrationQueue : requeued syncer for network 254 20120611-130318 735 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a sent cmd: @1A2001 20120611-130318 734 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a response: 8220005E 20120611-130318 735 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a sent cmd (fastpci): \4600002101g 20120611-130318 766 cmd3 - Response: [152] 120-pci reset 20120611-130318 765 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a got packet confirm: g. 20120611-130318 734 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a response: 890150434C4F43414C3444 20120611-130318 755 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a InterfaceState=running 20120611-130318 999 sys RegistrationQueue : found syncer for network 254 20120611-130318 999 sys RegistrationQueue : found syncer for network 254 20120611-130318 999 sys RegistrationQueue : requeued syncer for network 254 20120611-130318 754 //CORSTOWN/254 543714f0-95eb-102f-8ed8-c7d350d92b4a State=sync Previous=new Reason=Interface Opened 20120611-130318 766 cmd3 - Response: [152] 120-checking connection 20120611-130318 766 cmd3 - Response: [152] 120-reconnecting to bridged networks 20120611-130318 766 cmd3 - Response: [152] 120-open complete 20120611-130318 766 cmd3 - Response: [152] 200 OK: //CORSTOWN/254
more info ok ran diagnostic - I take it this is not healthy??? I have 3 clocks and 1 hardwrae burden on network Calculator says power is balanced and recommends 1 burden, PAC is generating most of the messages
ok so Diagnostic error is non issue with Pac disconnected error rate is zero which I think is expected with PAC
cbus diag with pac disconnected Any suggestions appreciated. If CBUS diag can successfully connect - what would the difference be with cgate?
Sorry to keep posting to my own thread but hoping to get help on this. In order to reduce the liklehood that this is config error I done the following: I copied cgate.jar from a v1.11 install and copied the v1.11 project file to the v1.12 directory and cgate loads fine with the rest of the v1.12 files so this issue is specific to v1.12 jar and/or my upgraded project file.
You can see error spikes like that when the PAC is trying to talk to devices that either aren't there or it can't connect to. I suggest you reconnect the PAC to your C-Bus network and download a new blank project to it. Then check the error rate and report back here.
Hi towbar, I'm surprised by the garbled responses: response: 80?EC?~?5**??1A?? processed by network. This suggests a problem with the units on the network or the usb to serial adapter. I'm also afraid that copying the c-gate jar from one version to another has placed your system in an further unknown state that will be difficult to diagnose. I also note with concern your previous posts regarding electrical modification of your PAC: http://www.cbusforums.com/forums/showpost.php?p=38287&postcount=4 NickD advised you at the time "At best, this will just reduce the reliability of your C-Bus network. At worst, it could be a safety concern." I can only suggest at this point that you simplify your network as much as possible - remove any and all "modified" units. Also remove any chatty units such as sensors, thermostats, touchscreens and PACs. Use a regular PCI as the interface. Back up all your Toolkit and PICED project files. Uninstall Java 7 and all Clipsal software. Ensure the C:\Clipsal directory is empty. Do a fresh install of C-Bus Toolkit, selecting the option to re-install the USB drivers. If you still have problems at that point please use the Help | Report a Problem menu option in Toolkit to send some logs, and in that report please include a description of your usb-serial adapter and any other information that may be useful.
Daniel, As mentioned I disconnected PAC and it cleared up the error messages -I'll have a look to see what it is trying to connect to but clearly its not the problem as the problem still occurs with it disconnected. I cant see how copying cgate.jar and the associated project creates an unstability when I confirmed it worked and when I restored the original 1.12 it didn't but I understand you have to flag it, I was simply trying to present as much info as possible to help rule things out. I tried uninstalling reinstall including forcing cbus driver which made no difference. I dont know what model the usb serial is but if I can get another will try it and post results. It must be a timing or buffer issue and clearly something that has changed from 1.11 to 1.12 - I'll do a bit more investigation - if I find anything will post back. For now I'll stick with 1.11. Thanks.
I may be off on the wrong track here but I noticed something using a port diagnostic utility that might point towards the problem. In v1.11 015960: I/O Request (DOWN), 13.06.2012 16:01:10.727 +0.0 IOCTL_SERIAL_SET_LINE_CONTROL: Set line control WordLength=8 StopBits=1 stop bit Parity=No parity in v1.12 000138: I/O Request (DOWN), 13.06.2012 16:10:10.315 +0.0 IOCTL_SERIAL_SET_LINE_CONTROL: Set line control WordLength=8 StopBits=2 stop bits Parity=No parity I doubt if the protocol has changed and if it was setting the wrong number of stop bits surely nobody would get version 1.12 working - totally confused now but it might explain the garbelled data. My machine is windows 7 x64 - if anyone else has cgate 2.9 running on this os please let me know
Hi towbar, Thanks for the additional diagnostics, I have reported this for further investigation (#23649). The reason why just copying the cgate.jar isn't recommended is because the supporting files are different between the two versions - those for one C-Gate aren't intended to be used with the other C-Gate. This includes the serial library which has changed in 1.12.0. I'll PM you some further debugging you can try. EDIT (November 2013): We have been able to confirm this adapter uses a Prolific chipset which is now known to have issues with Toolkit 1.12.0 and later. See http://www.cbusforums.com/forums/showthread.php?t=11574 for more info.
