SLC5753PEIRL programming guide

Is there a comprehensive programming guide for the SLC5753PEIRL, also for the SLC5750WPL? I want to activate a scene upon motion, and activate a different scene after timer run. Also, is there a way to activate a scene on "lack of motion" i.o.w. If Scene A (the same one activated by motion) is activated by a schedule (from PACA) there will be no timer running to switch to the second "off" scene. So how do you get a scene to activate if there is no occupancy after a schedule switches an area ON?

 

Hi there.. I am not aware of a comprehensive programming guide like what you are asking for..

However its pretty simple, provided you have sound CBUS understanding..

You need to set up you scenes in a touchscreen, pac or wiser.. One scene for 'on' snd one scene for 'off'..

In the scene configuration gui, you set a triger group, ie 'movement sensor trigger' and then set the action selector to on for the 'on' scene, and off on the 'off' scene..

Then in your sensor set its motion group address to the trigger group address, set you time and away it should go.

As for the second part of your question, why bother having a schedule turn on the scene if it can be controlled via the sensor? However if this is something u must have u would most likely need to write some logic code and have a third scene..

Cheers..

 

Thanx Roosta

Easy enough setting the Trigger Group and the Action Selector, I'll do that. The challenge comes that the "Unoccupied" Scene isn't the reverse of the "ON" Scene. So how do I get the Timer to expire to a different Action Selector. It's a large Community Center, so, if there are occupants in a particular hall/ area, we want the ON scene to switch on all that area lights, but, after a period of no occupancy we want most of the lights to go out but to leave pathway and cove lights on (Scene 2)... So that that part of the building isn't completely black. After-hours a scheduled OFF would switch them all off.
The second part, if the schedule, or keypad button scene select switched that area on, no lack of occupancy would time out to scene 2. So the lights would remain on permanently (until the next schedule change). It's quite a large complex, broken into sections, each with occ sensors and multiple lighting loads.

 

The default settings execute an ON Key (i.e. group address=255) when movement is detected and OFF Key (i.e. group address=0) when the timer expires. So just create the on scene with an action selector of 255 and an off scene with an action selector of 0. You can also change the ON Key to recall1 and timer expiry to Recall 2 to set any action selector you want.

Setting the scene from a switch or schedule won't stop the sensor from operating, it might just put it into Movement In Light mode if the lights are bright enough.

If you want to set a scene at a particular time for a fixed duration, but have it overridden by the sensor, create a scene to pulse the action selector for the appropriate scene and set the final (timer expiry) level to the action selector for the expiry scene. If any movement is detected, this will change the action selector, set the sensor scene, cancel the schedule timer and set the sensor timer.

 

Thanx Ashley

It's tough to believe there is no advance programming manual for this product. We have designed 20/30 projects, some of them very large, but haven't used PERIL's for Occupancy until now, only for Light Level Maintenance. It's not a real simple unit. You can create a Scene within the device, that's the only way you seem to get the option to select a scene trigger, but then the virtual key group becomes a Scene and NOT a motion activated timer??? Is there any way of varying that 255/ 0 value because you obviously need multiple scenes associated with various areas, they can't all have action selector 255 and 0. Where do you change the ON key to be recall 1? How do you set Recall 1 and Recall 2's action selector? I just need a Day Move selecting PICED Scene 1 and timing out to Scene 2, and a Night Move selecting PICED Scene 3 and timing out to Scene 2. All the scenes are created in PICED and their action triggers show up in Toolkit.

 

Ok so you will actually need 4 scenes in what you are describing above..

Depending on how you have setup your scene triggers you may need to set the application address of the unit to the 'Trigger' application..

Day motion ON scene 1, OFF scene 2.. Night motion ON scene 3, and OFF scene 4.. Scene 2 & 4 would effectively be the doing the same thing but with different trigger groups.. Scene 1 & 2 would use the same trigger group (ie 'area 1 day move') with 255/0 action selectors.. Scene 3 & 4 would use the same trigger group but different to your day move scenes (ie 'area 1 night move') with 255/0 action selectors.. Then in the GUI of the sensor set day move to activate the trigger group 'area 1 day move', and set the night move to activate the trigger group to 'area 1 night move'.. As standard it will trigger the appropriate group to 255 on motion and 0 after timer expiry..

As for advanced function such as recall setting etc, thats is generally done in the blocks and key function tabs of the GUI.. Although I cant see that you will need this in this case..

 

Oops. I just realised you are using a multi-sensor. For some reason, known only to the developers, you can't trigger scenes in a multi sensor from occupancy or light level events. They can only be triggered locally from ir commands or remotely using their trigger group and action selector. The other problem is for some reason the multi sensor won't let you select Trigger Control as its application so you can't generate scene triggers from movement either (you can using the 5753L sensor!). The only option you have is to use the sensor to set a virtual group address to specific levels then use logic in some other device to detect the change in the group address and set the appropriate scenes.

 

Really Ashley? Thats bloody interesting and frustrating..

Alternatively, set up your trigger groups on the lighting application.. Not recommended but I have done so plenty of time no problem..

 

Unfortunately the Multi Sensor (or NEO or Saturn) switches won't let you set the trigger group application. You can only do that in Piced supported devices.