Sending Text to a DLT with Serial Commands

I've scanned through the Serial docs - I can see there is scope for sending bitmap information to a DLT.

In the future, is there likely to be a published command set so as to send text information to DLTs ? And also, dynamically altering what a button does ?

The killer application here I see is with Comfort, and allowing Comfort to send alarm information, sensor information, and altering the layout depending on the mode (ie Night Mode).

Thanks

 

The C-Bus protocol already contains the details of the message to label a DLT group or action selector.

Labelling a button does not change what it does.

 

does it??

sweet.
Any chance you can point me in the right direction to find it? I've searched all the public docs but was unable to find the info.

 

Can we also issue commands to program a DLT button for example to a different group that already exists ?



Thnx

 

That's trying to program it on the fly. Might be better off looking at using logic to change what each button does by monitoring the GA's assigned.

 

OK, I've re-read the docs - I'm not seeing it.

Humour me if you will given the following scenarios

1. Group Address 12 - labelled 'Alarm' on one of the DLT's. Not connected to any load (virtual group)

Can we send a command to the DLT to say "Away Mode" or "Sec Off" programmatically ? And if so, what would a command structure look like for this ?

2. On a DLT or Saturn, button #1 is mapped to Group 30. Can we programmtically tell that button to be re-assigned to Group 55 ?

Thanks

 

Regarding labels, the Lighting Application protocol docs section 2.4.2 lists the languages, 2.5 covers the commands, 2.5.2 specifically being the label command, 2.6.5 describes the various command attributes in more detail.

Issuing labelling commands is part of the public protocol information. Re-programming the functionality of units is not.

There are many factors that need to be considered when reprogramming units and it is very easy to wind up in a situation where the unit does not do what is expected. Whilst changing a group address may seem like a trivial operation there are many aspects of a unit's behaviour that can be impacted. Toolkit does all the hard work for you.

 

No, you can't do this. What you could do is as follows:
1. Program the button to use a group address which is not used anywhere else (a "virtual" or "phantom" group)
2. When the use for that button changes, send a label to the group
3. Write some logic (in C-Touch, PAC or Wiser) which responds to changes in that group address according to the changing needs.

No, you can't do this. What you could do is as follows:
1. Program the button to use a group address which is not used anywhere else
2. When the use for that button changes, send a label to the group
3. Write some logic (in C-Touch, PAC or Wiser) which maps that group address to group 30 or 55 as required. See the logic TrackGroup procedure in the help file for details on how to do this.

 

Thanks for that Ashleigh.

These docs must have been added a day or so after the first few.
Time to relax with a good tech manual and nice glass of red

 

I tried that forum before posting here - no access to post.

 

I've just installed my first DLT and I'm ploughing my way through the training docs on dynamic labelling. I have a few questions:

1. It seems that only a blue LED is available on the Saturn DLT, unlike the Saturn which has blue and amber?
2. How do I get the LED to blink depending on group address state (like when running a timer on a KIU)?

By way of background my application is for the DLT to display an electric door strike state, whether the door is
a: "closed and locked" (DLT button LED off, label displaying PUSHTOEXIT), or
b: "unlocked" (DLT button LED on, label displaying CLEARTOEXIT), or
c: "closed and unlocked" (DLT button LED blinking, label showing DOORUNSAFE).

The function of the associated button on the DLT is to toggle the relay that sends the release command to the door controller.

The electric door strike signals it's state to CBUS via an AUXINPUT unit through 2 dry contact relays built into the strike, 1 contact senses whether the latch is NO or NC (i.e. whether the barrel in the door is pushing in the latch), and the other contact senses whether the strike is NO or NC (i.e. whether the strike is locked or not). The problem can arise where the door is closed but the strike fails to engage, I want to signal this condition by a flashing LED on the DLT.

So in operation it will work like this:

a: Normal. The door is closed and the strike is locked (as sensed by the AUXINPUT). DLT displays "PUSHTOEXIT" with LED off.

b: Exiting. Push the DLT button and that action toggles a relay which commands the door controller to release the strike for a preset period (30 secs). AUXINPUT senses the strike changing state from NC to NO, triggers DLT to display "CLEARTOEXIT" and steady LED.

c: Door unsafe condition. If after 30 seconds the AUXINPUT senses latch NO (meaning the door is closed) AND the strike is NO means the door strike is unlocked, triggers the DLT to display "DOORUNSAFE" and flashing LED.

Or am I in logic territory here better suited to my C-Touch Colour, and then get CTC to trigger the appropriate responses on the DLT? What's the best way to go here to achieve the function I'm after??

 

So if I'm to understand this correctly.

1. I need to set up the appropriate logic in the CTC.

2. The DLT can always show the appropriate door state labels depending on what the AUXINPUT senses.

3. The LED on the DLT will never be able to blink because the AUXINPUT is the unit sensing the unsafe state of the door strike (i.e. it's not dependent on anything actioned in the DLT).

4. But I might be able to get the AUXINPUT to get the DLT to trigger a long timer when the logic senses door unsafe???

This is the important bit, because I need an obvious visual warning, i.e. blinking LED, if the door appears to be locked but it isn't (this happens whenever the door is closed whilst the strike is unlocked, the strike can't lock unless the door is open).

FINAL QUESTION: Can I get the CTC to trigger an aural warning when the unsafe door logic is met?