At the Liberty Memorial Museum in Kansas City we have a hog3pc running a theatrical presentation and an ETC Unison/Emphasis running the rest of the museum. Three universes from the hog go out to an ETCNet 4 port gateway configured for 3 DMX inputs. The hog and the Unison share universe #1 for our 3x96 ETC dimmer racks. Universe #2 feeds all DMX raceways (via another 4 port gateway acting as a DMX distro) that are terminated via several DL-1s, Studio Spots, and strobes. There is a 2 port ETCNet node on the same universe (#2) that feeds The groundrow Selador LED strips at the upstage wall. Universe #3 feeds to a 2 port ETCNet node via the ETCNetwork that runs a long stretch of ColorBlaze 72 in 12ch mode (400+ channels just for the strips!) at one exhibit on the other side of the museum. The 4th Universe is for 3x Catalysts at the AV rack. It all works pretty well, we are essentially using the ETCNet system as a big, configurable, DMX splitter/merger/distribution rig. The Unison mostly does all lighting control for the rest of the museum and does tap into Universe 2 to activate shutdown channels on the DL-1s and Spots when someone hits the "End Of Day" button. All in all it works pretty well.
I do wish there were more of an open standard for networked control systems. I'd really like to be able to http into the entire system remotely to check on dimmer loads (for burnouts) and VPN into the hog3 and Catalyst servers to make sure everything is on the up and up. At present you have to be the equivalent of an IT Guru to be able to make things like this happen. The rest of the remotely controlled computer world has featuresets like this and I believe this type of activity will increase as more networked lighting control systems become more prevalent in the industry. The Rosco/ET Horizon control system implemented http in a good way and I had hoped that would begin some kind of trend, but I have yet to seet it happen. It's too bad.
At the Liberty Memorial Museum in Kansas City we have a hog3pc running a theatrical presentation and an ETC Unison/Emphasis running the rest of the museum. Three universes from the hog go out to an ETCNet 4 port gateway configured for 3 DMX inputs. The hog and the Unison share universe #1 for our 3x96 ETC dimmer racks. Universe #2 feeds all DMX raceways (via another 4 port gateway acting as a DMX distro) that are terminated via several DL-1s, Studio Spots, and strobes. There is a 2 port ETCNet node on the same universe (#2) that feeds The groundrow Selador LED strips at the upstage wall. Universe #3 feeds to a 2 port ETCNet node via the ETCNetwork that runs a long stretch of ColorBlaze 72 in 12ch mode (400+ channels just for the strips!) at one exhibit on the other side of the museum. The 4th Universe is for 3x Catalysts at the AV rack. It all works pretty well, we are essentially using the ETCNet system as a big, configurable, DMX splitter/merger/distribution rig. The Unison mostly does all lighting control for the rest of the museum and does tap into Universe 2 to activate shutdown channels on the DL-1s and Spots when someone hits the "End Of Day" button. All in all it works pretty well.
I do wish there were more of an open standard for networked control systems. I'd really like to be able to http into the entire system remotely to check on dimmer loads (for burnouts) and VPN into the hog3 and Catalyst servers to make sure everything is on the up and up. At present you have to be the equivalent of an IT Guru to be able to make things like this happen. The rest of the remotely controlled computer world has featuresets like this and I believe this type of activity will increase as more networked lighting control systems become more prevalent in the industry. The Rosco/ET Horizon control system implemented http in a good way and I had hoped that would begin some kind of trend, but I have yet to seet it happen. It's too bad.
