Toolkit DLT

When in toolkit if I goto the edit languages and remove english and chinese and leave just australian the next time I come back those two languages show up again - is this correct ??

dave

 

Dlt

If you hit the edit languages button then return then hit the default button i get this everytime

dave

 

DLT house keeping

when i set the default language to australian toolkit does not remove the other language text

dave

 

DLT Languages

Dave,

This behaviour is correct. DLTs can do 8 languages, two of which are enforced as English and Chinese.

Toolkit continues to show labells for non selected languages as these labells still exist in the DLTs memory, they just aren't being displayed.

Remember each key MUST be labelled in English before being labelled in other languages on v1.x.x units. V2.x.x units can be labelled any any language first.

Cheers,
Mark.

 

Dlt

Mark
In manual with switchs (page 5) says labels can be changed dynamically by other cbus devices.
Which other devices and were do i find more info


dave

 

DLT Text

Is it possible to get more info in this message, like which group or what it doent like ???

dave

 

DLT Text

The 14 chars is dependant on pixel width - have a look at what I have given to Mark much smarter - i think

dave

 

Hi Dave,

There are 2 seperate issues here. The problem being experienced is related to the actual DLT protocol on C-Bus being limited to 14 characters, and the correct solution is to limit the length of messages to 14 characters.

The issue regarding pixel sizes is a DLT Key input unit is design limitation. The size of the physical display limits thenumber of possible characters to display based the font and characters being used.

These are 2 entirely different things. To limit the labeling of a group address to less than 14 characters based on current DLT key input unit screen limitations would reduce all future DLT enabled products to match this limitation.

Now what would be cool is some magic in Toolkit that looks at where a DLT label is going to be used (based on looking at unit programming) and warn you if a specific label may not display correctly on that unit (by using your pixel/character counting suggestion).

I hope this makes sense.

So in summary, although directly applying your idea to this dialog is not a good idea, using the principle you descibe in a smart analysis of the unit programming would be a very worthwhile addition to Toolkit.

 

DLT Text

Richo

No way was i suggesting less than 14 char thats just the max.

if you try using say "W" you get 9 chars, what i wanted was some way other than loading into a switch to see if the text will fit hence suming the pixel sizes.

i have it working now so i can tell which ones fit before loading, given the code to Mark so maybe can be added to toolkit later.


dave