PulseCBusLevel

[Titsonabull]

Hi I've installed C-Bus Firmware for LSS5500SHAC Automation Controller V1.15.0 (V1.15.0) and since then all my PulseCBusLevel commands are giving multiple triggers and seem to be turning off groups before turning them back on. 

Any advice

[DarrenMullighan]

Hi there, the 1.15.0 firmware addressed some issues around the PulseCBusLevel command. Funnily enough to actually prevent the issuing of multiple commands. Out of interest, what firmware did you upgrade from? and does this affect any new scripts which use this function? Regards, Darren

[Titsonabull]

Hi Darren. Thank you for your reply.

I’ve updated from V1.6 I think and updated to V1.15.

I had several simple event  based scripts to pulse groups on and return them to off after a period of time. The script was activated by a group on a schedule. This group was also turned on by a toggle switch on a visualization page. This allowed the script to run when the toggle switch was turned on or the schedule ran.  Within the script the group for the activation of the script was also pulsed for the same time length.

By turning off the toggle switch it used to cancel the pulse command and off each group that was being pulsed including the toggle switch that activated the script. This allowed me to see on the visualization page if the  groups being pulsed where on or off. Code shown below

if (GetCBusLevel(0, 49, 4) >= 1)  -- toggle switch for activation of script which is also activated from             schedule

 then

 PulseCBusLevel(0, 56, 43, 255, 0, 5, 0) -- Light to be pulsed on for 5 seconds and then turned off

PulseCBusLevel(0, 49, 4, 255, 0, 5, 0) 

 end

With the new firmware when I toggle the switch it pules the groups on and off in a loop. It’s like the pulse command is being reactivated by the pulse command of the group being pulsed within the script and turning off the toggle switch does not cancel the pulse command.

Any help would be much appreciated. Regards, Colin

[Mr_C]

Hi  

1.15.0  Release notes  statements 
Fixed an issue related to the PulseCBusLevel() function, which appeared to send multiple first
stage commands.
• Fixed an issue related to the "Execute during ramping" option for an Event-based script, which
was not functioning.

Out of interest does the event script action the group that creates the event,   if so , Please check to make sure your Execute during ramping is not set. 

An issue with PulseCBusLevel was fixed in 1.15.0  but t might be the execute when ramping fix could possible causing the difference you currently see. 

[MarkHenry · Accepted solution]

Haven't seen multiple commands but the issue still exists where the expiry function is not cancelled when a command has been sent during the expiry time.

e.g.

Send Pulse Group1 to 255 and after 20 sec set to 0

During the 20 sec expiry time send a command to Group1 to any level, for this example say 50%

Group1 turns off 20sec after the initial command.

Expect that the expiry timer would be cancelled when a command is received without a pulse as it did previously in any PICED devices. Have not used pulse in NAC at all due to this.

[Titsonabull]

Hi All, 

thanks for the reply's. Got it working all be it over a couple of event scripts. Not sure how it worked previously but with the new upgrade it works differently and requires a bit more thought going into the scripting when using the pulse command as pulse is no longer canceled with the deactivation of the pule trigger. Learned a lot while trying to figure it out and really appreciate those who took the time to reply. 

Regards 

Colin