PC_GIM message data

Hi,

Is there any way to get the message data from the measurement application ($E4) to send information to the PC interface? Or can anyone explain to me how to set up a way to request an update using the control trigger application?

Thanks,
Simon

 

You need to configure a trigger group in the Global configuration tab in toolkit for the general input unit. Once you've got that then you can send a message via the PCI with the trigger group and the appropriate action selector for the channel you want immediately broadcast.

 

Hi Tsman,

Thanks very much for the reply. I've somehow got the strings being received from the PC_GIM modules. I connected to the C-Bus system via the pc interface and scanned the network and also checked the application log. I then disconnected after not changing any settings and then reconnected the crestron system I have controlling the clipsal system and suddenly I noticed all the strings coming back from the PC_GIM modules. Sadly some of the readings are not correct but I think that is down to faulty temp sensors.

Thanks again,
Simon

 

You can confirm what the readings actually are by looking at the general input unit configuration window in Toolkit. There should be a checkbox to display the current reading. The diagnostic utility will also decode the messages on the bus. You can cross reference the readings with what values you're decoding from the measurement application messages.

The mystery messages appearing now may be caused by your Crestron system communicating with the PCI in a different mode than what is used with C-Bus Toolkit. The PCI can be also set to only pass certain applications through as well. Toolkit will setup the PCI to pass all messages and to do so in the extended format.

 

Hi Tsman,

How do I check in toolkit what messages are being sent through the pc interface? I have also (worryingly) noticed that the lighting strings I previously was sending from the crestron to the pc interface are not being acknowledged (ie. bounced back) which they were before and much of my lighting code relies on this.

Thanks,
Simon

 

The Application Log is all you can see in Toolkit since the C-Gate service handles it all behind the scenes. You may be able to enable debugging in C-Gate for more information but I've never had the need to do that so somebody else will have to chip in for that.

I've generally used two PCIs for cases like this. One PCI for the actual interfacing and another temporary PCI to monitor the bus to see what is going on.

I suspect that you are hitting the problem with the different modes since the messages you send/receive aren't quite the same. I assume you've downloaded the protocol documentation already from http://training.clipsal.com/downloads/OpenCBus/OpenCBusProtocol.html . Look at the one called "Serial Interface User Guide" and it'll list the different formats in there.

 

Hi Tsman,

Thanks so much for the help, I've managed to put the interface back into basic mode which echo's the commands.

I'm annoyingly left in a situation that I will have to change my code as to get the temp feedback from cbus it needs to be in smart mode which disables the echo. At least that's what I understand from the serial interface guide.

Thanks,
Simon

 

Hi Tsman,

Do you think from your knowledge on the pc interface and cbus that there might be a way to have it in basic mode but be able to monitor the measurement values coming back from the PC_GIMs? I have read through the document and I don't understand some of the terminology used. I was thinking of enabling "monitor" and "exstat" but even the format of the string I'm struggling with and don't want to break anything!

Thanks,
Simon

 

You may be able to do it using the CONNECT option without the long form messages and SMART mode but I've not tested it. The temperature sensors will be broadcasting Point to Multi-Point messages in the measurement application and CONNECT will instruct the PCI to send those to you.

 

Hi Tsman,

That's great, I'll test when I'm next onsite.

Thanks,
Simon