Interrogating Groups

Hi,
I'm after some information on the best way to get the group names from CBus, or are these only stored within Cbus toolkit. I'd like to enumerate them in much the same way as done by Piced for example.

Cheers,
Paul

 

Group names are not downloaded to the units - they reside in toolkit only. If you go to a new existing installation you can download the configuration of the system, but there will be no group names (other than the default Group 001 etc) .

Mick

 

What is the actual problem?

a) Have you inherited a CBus system with no toolkit (tag) files? If so, then unless you have a Colour Touchscreen you will have to recreate the tag names from scratch as they are not stored in the units. If you are lucky enough to have a colour touchscreen on the system you can download the tag file from it and restore it to the cgate/tag directory.

b) If you just want to access group names from a Pc for some third party application, just process the xml tag file under cgate/tag.

c) If you want to access group names from logic this can only be done on a colour touchscreen (not sure about Wiser 2 actually).

 

Thanks Ashley, I'm working on a third party app and wanted to access the group names for the fluffy factor.

I assume the correct path can be found through the registry key under HKLM\Software


Thanks for the pointers,

Cheers,
Paul

 

If you use the default installation path it is C:\Clipsal\C-Gate2\tag

Extracting the tag names is just a case of scanning down the Application nodes until you get to the one you want. They are in no particular order.

 

Hi Ashley,

Actually the best way is to grab the path from registry then process from there. All good, works like a charm once the XML is parsed in.

One other question in regards to the messaging timing. If we are looking at a general input unit or CMU for example, we have an option to transmit periodically which if fine. There is also an option to transmit on change. Do these two operate totally independently or is there some interaction where if one message is already placed on the network the other message won't be sent.

Or if the time is right, message gets sent AND when the input change is enough to trigger this message will also be sent regardless of what fact that a message has already been sent based on time.

Hope that makes sense.


Cheers,
Paul