Compile Error on C-Touch Unit.

[Dave Byron]

Needed to replace a unit that did not survive last nights storm with a new unit.

When download the project to the C-touch unit get a "Compile logic error 14097"

This project has not been changed for a long time so when first saved get the expected message about made with old version of Piced.

Using Piced version 4.3.0.0

In Piced compiles OK
Error report show nothing – just the usual warnings

But when downloaded the C-Touch shows the error / warning – the help file not sure if it a warning or error.

Now the question is how do u fix when Pice says no errors.
dave

[AliG]

check the group description names. I had a similar problem and the software compiled ok but the screen didnt like it.

Found that some of the tags had change from lower to upper case or vice versa.

changed them to match toolkit and all was ok

[Dave Byron]

You maybe on to something.
Problem is I do not have a spare C-Touch unit to test with.

In Piced logic there is
if getTriggerLevel("Xtrig Page no") >0 then

But the logic report shows
Group Address 19 (Xtrig Page No) is controlled by :

Which is the same as in Toolkit.

Are the Piced and Homegate compilers not 100% compatible ??.

dave

[ashleigh]

Should be compatible.

[Dave Byron]

ashleigh,
But are they.
Be nice if the C-Touch Homegate gave a line number or something to track.
A clue were to look would be nice.

Be even nicer if good compile in Piced worked in a C-Touch unit.

PS
Sent all the files to Tech services for someone to have a look at.

dave

[Matt]

I am getting this problem too i downloaded using the latest piced (4.3.0)

is it possible that the group addresses are to long.... and that they are being shortend when they are downloaded and therefor are not matching up ???

or is there somthing else at play here

thanks

[ICS-GS]

Dave / Matt,

This happened to me a while ago. I posted info about it here:

http://www.cbusforums.com/forums/showthread.php?t=3818

Maybe it still lingers on!!

Good luck

Grant

[Matt]

i have found the problem it seems that it was just a extra space at the end of the tag name that was doing it

i had

(GetLightingState ("Master Bedroom Light ") = OFF

where as it should of been...

(GetLightingState ("Master Bedroom Light") = OFF

Strange that it would piced would let this through and let it compile

oh well now i know to watch for that

[Dave Byron]

It would be nice if the Clipsal TS section was not just a dead end email address, despite what we were assured in the last Adelaide meet.

I sent an email to them on the 27/3/08 and as yet;

no acknowledge that the email received,
no report number
nothing says they working on it.



Just dead silence
dave

[[IL]NewGen]

i have found the problem it seems that it was just a extra space at the end of the tag name that was doing it

i had

(GetLightingState ("Master Bedroom Light ") = OFF

where as it should of been...

(GetLightingState ("Master Bedroom Light") = OFF

Strange that it would piced would let this through and let it compile

oh well now i know to watch for that

hehehe, just a simple space can cause mismatch within the logic engine:D

an alternate solution u can replace the tag description with the corrisonding group address; for example:
Your:

(GetLightingState ("Master Bedroom Light") = OFF)

can also be written as:

{Keep your descriptions there but comment them out to eliminate confusion or errors during your programming}
(GetLightingState (130 {"Master Bedroom Light "}) = OFF)