Senpill

I have just installed my first cbus network in my new house. i have about 55 units including about 8 SENPILL units. I would like to know how to program these. most of what i have played with works fine (NEO switches everywhere) but these senpill units seem to only want to on/off on movement (day or night)
i tried to select a scene but it then decided to nothing. I also don't understand the occupancy area. Is there supposed to be a help file for the cbus toolkit ? I have 1.1.8 and the help menu is strangly greyed out. Can anyone point to a help file i can install ? I have installed the PICED and TICA toolkits (but havent programmed the units properly yet)

Any help would be appreciated

Regards
Kevin

 

Yes there is meant to be a Help File. Needless to say, I'm deservedly getting a LOT of grief over this..

I'll leave the SENPILL Guru's (Newman, Daniel) to answer your other questions.

 

What exactly do you want to do with your SENPILLs?

Note that you can't trigger an internal Scene in response to motion, the only way to do this is to trigger a Scene stored in another unit. The only way to trigger a Scene in a SENPILL is over C-Bus or from the Infrared remote.

Have you got the regular PIR functions (i.e. motion detection) up and running OK?

Occupancy Tab: Sequence of control goes something like this....

• Movement (Light and Dark) and Light Sensor (Sunset) functions are all fed into the Occupancy Tab.
• The tick boxes on the Occupancy Tab apply those PIR events to a Virtual Key. If you have the Light + Movement checkboxes ticked for keys 1 - 4 then those Virtual Keys will be "pressed" whenever the Light + Movement events happen. The Group listing is just there so that it's obvious which groups you will be controlling under what light conditions.
• The Key Functions (PIR Day Move, Bell Press, etc) determine what happens to the Group Address when the key is "pressed". So, PIR Day Move is just saying that any active timer will be re-triggered whenever movement is detected (see key microfunctions on the blocks tab to see which key functions are happening).
• There is a UI bug that fails to remove the Scene options from the list of available Functions for key that are assigned to things on the Occupancy Tab

A little help on setting up multisensors here: http://www.cbusforums.com/forums/showthread.php?t=661

 

Thanks for that, ill play with the system tonight and see what i can solve. I have a c-touch (BW) and would like to do things like.

At night, on movement, set lights to 20% for 10 mins, during the day, do nothing. etc.

What are the 'short press/long press/short release/long release' setup for the PIR ? i presume its always a short press/short release on pir sense and not sense ?

Thanks.

 

You can think of it like this:
Whenever movement is detected then the Virtual Key is pressed. When the movement stops the Virtual Key is released.

So, if there's a brief flutter of movement you will get the SP and SR events. If it's a long continuous detection of movement you will get SP, LP and finally LR events. The reality is that motion in the field of view, with it's random nature, tends to be pressing and releasing the Virtual Key quite a bit.

 

I have some progress.

I setup the occupancy sensor so that dark + movement triggers key 1, then i put 2 blocks on key 1. I have Front Entry lights and Stairwell lights.
short press - retrigger timer
short release - ramp recall 1
long press - retrigger timer
long release - ramp recall 1

ive set the block recall 1 level to 50% and it does what i want. at the end of the timer, it ramps off.

Now, i want to be able to tell this senpill that if the group is already on, don't do anything at all. ie don't start timers and don't ramp to anything. is there any way to do this ? i have a c-touch and have ordered a PAC but the PAC hasn't arrived yet.

thanks again for all your help. im getting closer to having the system setup in quite a friendly way.

Regards
Kevin

 

Kevin

You may be better off changing your key functions to:
short press - ramp recall 1
short release - retrigger timer
long press - retrigger timer
long release - retrigger timer or idle

This is essentially the same as the regular PIR Night Move functions, except that it uses Ramp Recall 1 in lieu of the On command so that you get your 50% level. Making the above changes will guarantee that the timer gets re-triggered. With what you have suggested if it's only a brief flutter of movement then you'll only get the SP and SR commands. Given that the ramp recall 1 comes subsequent to the retrigger timer in your example you may find that every now and then the light gets stuck on and doesn't time out.

I gather that you don't want the unit to set the group level to 50% if the group was turned on via some other devce, e.g. switch, C-Touch or similar? Can do this a few ways:

• You can simply set the Light Level threshold so that when the group is turned on then the measured light level is above the threshold. The Multisensor will then start doing the Light + Movement functions instead of the Dark + Movement functions. Hook that up so that the L+M functions are assigned to another key, set that key to the same 2 blocks and select PIR Day Move. That will keep the same 2 groups in the On state for as long as there is occupancy detected.
• Another way would be to use MAX logic in the output unit so that the output channel takes the greater value of the level set by the switch and the level set by the Multisensor. If the level set by the switch is greater than that set by the Multisensor (50%) then the load will be at the brigher level. This doesn't help for when you've used the switch to dim down below the 50% point however.
• Program up a PAC to do it.