all off via scenes

I have followed this forum for a few years now and have seen many time people recomend that an all off should be done via a scene instead of the application.

While I have always used the aoolication method, I find myself needing to use a scene as I need one of the loads to remain on. I created a scene, but it only allows for 10 groups to be included. In my case there are a few more than 10 groups that I want to turn off.

How can I do this - I dont have a PAC or a touchscreen to use logic either.

Mick

 

Have you tried using the output logic option???

 

You could "join" scenes between Neo/Saturn/Reflection plates together to achieve more than 10 groups..

By assigning the same Trigger Group to the plates and the same Action Selectors to the scenes you could have a group of Input Units collaborate to execute a very large scene..

The drawback is that each part of the scene on each plate would need to be assigned to a key in order to get its Action Selector assigned.

 

Get your self a Minder, it's dead easy using one of those.

Cheers

Rohan

 

It depends a little on the vintage of the units you are using. More recent Neo and Saturn style units (firmware version 1.6.00+) support up to 40 groups in a single scene, and Toolkit should regognise these and allow you to program it. All DLT units support 40 groups on a scene as well. If you have a C-Touch on the network of course it is dead easy..

 

Thanks Guys

no more output logic available - all four are used

Isn't joining scenes going to waste a button on a key input? Trying to avoid that as spare inputs are very limited if non existent.

Yes a minder will do it, but I don't think the people concerned will want to spend the money on some outdated hardware (no offense Rohan - I know you like your minder).

The best way to resolve my problem is for a single channel DIN rail relay - but alas they are not available (a standard single channel will not "fit" the installation).

Mick

 

Outdated!! how rude, you can still buy them you know

Overpriced and badly supported I think is a better description.

You could also write a macro in CQC if they are using that.

Cheers

Rohan