Feature Request - Custom Fixtures - Lamp Control - Time/Hold/*Release*

uhm i don't have a way of trying that right now, but i would think that if instead of "Hold" you put a number of seconds there it would be released after the that time runs out. you might need to assert the cue after lamp ccontrol has done it's job and should go away

Yes, you are right but time is not an option in this case. I can't predict if the cannel should stay on for about 3h or 16h

And if one is Hold an one is time - hold is always stronger and time has also no effect any more. Would be nice to tell the cannel to get to 0 for x seconds and than release it. but it doesn't even turn to 0 if it was on hold = 255.

Usually a lamp control command you just send for a number of seconds to tell the lamp to power up. Once you've done that it stays on regardless, so you should t need to do the infinite hold.

If you want complete control just change that DMX parameter to a normal one rather than a lamp control and you can then drive it normally and just have a couple of beam pallets that set the value to turn it on or off as required or whatever you are actually doing with this channel

Thanks Mike but that's not the situation here.

I use the lamp control to switch devices on before a show and to switch them off afterwards.

When they are off, it should be possible to switch them on/off by show values instead. This is needed for our rehearsal light, which is controlled by a sub.

Our RPU is running 24/7 so every switch once controlled by lamp control isn't controllable my manual values unless I exit into eos shell and return to the show. Only If I do this, all lamp control commands are forgotten.

This exit/re-enter is our workaround so far. But it's not always possible if our system is fully up and running.

(There is also a bug in the software only visible in this case: if a value is on Hold by lamp control for a long time it gets "stuck" in the system but thankfully not in the output. if it is switched from 255 to 0 by lamp control after some hours, output on hardware will be 0 but sometimes the value shows up in "actual values" with 255 and a MS is also showing it on 255. This also resolves by leaving the show and re-entering it. )

-----

RPU3 2.6.3, 3xTi, 1xGio, 1xPuck, 70x2-Port 7.0.1.9.0.17, 18x4-Port, 15xCEM3 1.6.1.9.0.41

I understand that you use the lamp controls before and after the show and you dont know how long you will need the lamp on for.

For background "Lamp controls allow you to execute control functions of selected fixtures such as calibrate, douse lamp, strike lamp, and reset."

What I am trying to explain is that normally a lamp expects the command to strike the lamp to be a particular level on a particular channel for a certain amount of time. ie 12 seconds and then thats it (look at the lamp control setup for say the Martin Mac 2000 Profile 16B and you will see the ON command for that is dmx 1 at 232 for 12 seconds, and the OFF command for that lamp is dmx 1 at 251 for 6 seconds).

So what you have done with setting it to hold the value indefinitely is somewhat strange.

Maybe you are not trying to operate the control functions a "normal" sort of lamp and are using it to directly control power breakers feeding a dimmer rack or something. Or maybe you are thinking they are intended for setting the output level of a lamp.

If you are genuinely trying to control something that really needs to have a continuous dmx value send to it, then you probably shouldn't be using lamp controls at all for this and just use normal cue levels or a sub or any of the other normal ways you'd set a level. You mention a rehearsal light, that is definitely something that should be controlled in the normal way - loads of options there park, independant subs, macros, home values.