fofosfederation
Member
General
I'm a student at a college theater, and we have an incredibly annoying problem where a random number of our intelligent lights will power up as soon as our lighting board turns off.
Our Setup
The addresses of the lyntech panel are patched into the board as non-dims, those channels are selectively added to a group (whichever lights need power for the show have their power channel added to the group), and we have a macro that parks that group at full (run manually).
There is an automatic shutdown macro that unparks the group. It runs immediately before the board shuts down. As soon as it's done the eos turns off. I've noticed a problem in the most recent Eos update where shutdown macros fire incorrectly; they won't wait for submacros (the unpark macro is called by the actual shutdown macro), to finish, and instead immediately move on to the next thing while the submacro is still working. However we were experiencing this problem before that, and the issue persists even when the shutdown macro runs correctly from a manual firing before shutting down the board.
When the board finishes powering off (all black screens, no lights on board) the lyntec panel will sometimes fire and switch on a random number of random intelligent lights. The lyntec panel does not indicate that they are on (from the green lights). Restarting the board and parking the suspect power channel at 0 does not fix the problem. The power channel must be brought to 100 (now shows up on lyntec), and then brought to 0. That powers off the lights, and the eos and lyntec agree that it is in fact off. But then shutting down the board after fixing it causes the issue again..
I've attached a showfile in case that might help anyone.
Help
Does anyone have any idea what our problem is? Have you experienced anything similar? I'm usually very good with complex technology, and I'm kind of at a loss for what's going on. The technical director keeps calling me in to fix it on my time. I need a permanent solution to this nonsense; so if anyone can provide anything useful that would be great!
-TCJ
I'm a student at a college theater, and we have an incredibly annoying problem where a random number of our intelligent lights will power up as soon as our lighting board turns off.
Our Setup
- ETC Eos Lighting Board
- Connects to an ETC Net3 Show Control Gateway
- Ancient ETC Dimmer Rack (pre-unison, I don't have the model)
- A couple of ETC Net3 DMX Two Port Gateways distributing data to the intelligent fixtures
- A Lyntec Motorized Circuit Breaker, controlling power to all the intelligent lights
- 30~ Elation Design Spots & Washes
- 12 ETC Selador LEDs
- DMX Universes:
- 1: Conventionals, connects to the dimmer rack
- 2/3: Intelligents, connects to all the intelligent lights
- 4: Lyntech, connects to the lyntec panel
The addresses of the lyntech panel are patched into the board as non-dims, those channels are selectively added to a group (whichever lights need power for the show have their power channel added to the group), and we have a macro that parks that group at full (run manually).
There is an automatic shutdown macro that unparks the group. It runs immediately before the board shuts down. As soon as it's done the eos turns off. I've noticed a problem in the most recent Eos update where shutdown macros fire incorrectly; they won't wait for submacros (the unpark macro is called by the actual shutdown macro), to finish, and instead immediately move on to the next thing while the submacro is still working. However we were experiencing this problem before that, and the issue persists even when the shutdown macro runs correctly from a manual firing before shutting down the board.
When the board finishes powering off (all black screens, no lights on board) the lyntec panel will sometimes fire and switch on a random number of random intelligent lights. The lyntec panel does not indicate that they are on (from the green lights). Restarting the board and parking the suspect power channel at 0 does not fix the problem. The power channel must be brought to 100 (now shows up on lyntec), and then brought to 0. That powers off the lights, and the eos and lyntec agree that it is in fact off. But then shutting down the board after fixing it causes the issue again..
I've attached a showfile in case that might help anyone.
Help
Does anyone have any idea what our problem is? Have you experienced anything similar? I'm usually very good with complex technology, and I'm kind of at a loss for what's going on. The technical director keeps calling me in to fix it on my time. I need a permanent solution to this nonsense; so if anyone can provide anything useful that would be great!
-TCJ