Referring to my previous post, it looks like probably
all the X10 \'All On\' and \'All Off\' codes are swapped. I have changed my X10 light from house-code A4 to C3 and changed all the response codes accordingly. However, I still need to use the C \'All On\' response to turn the lights off!
I realise that X10 isn\'t flavour of the month, but where it exists, it can still be useful as I am proving. Can this anomaly be investigated, please? I would assume it could be corrected in a future firmware update?
Thanks for confirmation. I\'ll look forward to the firmware update.
I thik it would be a good addition to Comfigurator the possibility of using Do While or For /Next constructs.
They are a basic feature that can be found in any programing language.
I would certainly make use of them.
Well, of course, I entirely agree with you! I find it amazing that a \'programmable\' system that has the \'microcode\' ability to support this construct doesn\'t have it at the \'higher language\' level. Let\'s hope we get some more support from others to get this adopted.
Meanwhile, I have worked out a way to do this using 3 responses. In my specific case, I want to flash some lights three times. I have three responses which we will call Response1; Response2 and Response3.
Response1:
If NightTime <> 0 Then If Counter Counter013 <> 0 Then !CBus Grp 13 Set Counter051 = 3 Do Response2 End If End If
Response2:
Cbus2 UCM02 13 25 121 Wait 3 Seconds Using Timer25 Cbus2 UCM02 13 25 1 Wait 3 Seconds Using Timer25 Decrement Counter051 Do Response3
Response3:
If Counter Counter051 <> 0 Then Do Response2 End If
It works - but it is \"messy\" and we shouldn\'t have to go to this level!