Cbus - "unknown response: ~~~ ***"

Hi there,
I'm using CBUS toolkit 1.11.4 and PICED 4.9.2.

Whereas PICED can talk quite happily to the USB interface of CBUS, CBUS
can't, and gives me several lines of "unknown response:" errors before
failing to connect. looks a lot like a baud rate problem in communication.

CGate version is 2.8.0

Prior to this I was running an earlier version of the CBUS toolkit which did
talk to the USB interface properly, so I'm a bit stumped as to how PICED
can talk happily but the toolkit not?

Bueller?

 

What Operating System are you running on the PC you are using?

 

XP SP3. Pretty standard.

But like I said, all was well with CBUS toolkit till I installed PICED.

I ran PICED, then realised it required a later toolkit, installed it, after which point
PICED works but the toolkit doesnt.

Toolikit DOES connect however, because sees the device and you can
see a connection in the Java console - but then it gets bad characters

 

Where are you seeing the message "unknown response: ~~~ ***" ?

 

The message comes up in the Java text window/console.
The toolbox application itself just times out.

 

So just tried it again. Toolkit won't communicate.

In the Java C-Gate window it says:

Clipsal C-Gate(TM) v2.8.0 (build 2310)
20110401-144840 800 cgate - C-Gate started.
20110401-144853 803 cmd3 - Host:localhost/127.0.0.1 opened command interface from port: 1036
20110401-144952 751 //TOPOLOGY1 - Tag information changed at tag address: //TOPOLOGY1/Installation oldtag: null newtag: null
20110401-144952 742 //TOPOLOGY1/NET0 - Network created type=serial address=COM4
20110401-145012 824 //TOPOLOGY1/NET0 - Unknown response: ~~~ ***
20110401-145013 852 //TOPOLOGY1/NET0 - C-Bus Network Powerup Detected
20110401-145013 824 //TOPOLOGY1/NET0 - unknown response: {graphic chars}


And that's all she wrote. If I probe all serial ports it still sees COM4, but no talky.

If I fire up PICED, no problems, it'll download the config.

 

It isn't quite clear what you are saying that PICED will do.

Are you able to connect to C-Bus from PICED and monitor and control C-Bus from PICED? Or are you just opening the C-Bus project and using the tags?

What do you mean by this?

 

Ah right.

I'm connecting to CBUS and downloading the project.
I'm not controlling anything at this stage because I'm trying to import
a project and find out which bits are which as it seems that every
daylight savings time the lights go on the fritz - so if I can get a
full picture of the lights and the code, I'll rename the various parts
to something other than POINT1 so that it's easier to diagnose in
6 month's time...

 

So what I did over the weekend was to install the toolkit (and cgate) along with PICED on a completely different laptop and this appears to work, so
I'm wondering whether upgrading the software didn't replace some component
which was incompatible or whether leaving it for a couple of days has
done something.

The only thing I note is many many tag errors in the java window, which
I'll look into shortly.

I'll test the other machine again in the next day or two to see if it's still
not talking properly?

 

I have a similar problem but I'm not currently using PICED. I'm accessing the network via a PAC using a USB connection. It then worked OK for a while and now I can't open the network. I've only got one network, I don't have a dongle. Do I need a dongle for a single network?

I get similar messages whenever I click on my project:
Tag information changed at tag address: //MALTON/Installation oldtag: null newtag: null

After that I get "unknown response: ~~~ ***", and it keeps repeating.

The same thing happens when I try using c-gate commands directly.

This looks like a java programming bug.

 

My problem fixed itself after powering cycling my c-bus.

 

Thanks for letting us know. The USB drivers occasionally seem to get themselves into a funny state too, so something else to try next time is disconnecting the USB cable and re-booting your PC.