So how do you tie the following together? turning on non-dim set lights. Sending power to DMX controlled lights that can go in to “disco mode”. Controlling a few cues on a light console. Then Of Course….. make it easy for anyone to start and stop the system?
The answer is Automation.
This Blog Post will be touching on how I solved this problem off a “simple on/off switch” for this complex system.
Part One: What was the scope of this sub-project?
This system Must, make it where the end user can Start Up and Shutdown(safe) the lighting system. this control system shall be accessible from any network. To allow any device to start or safe it via a Website.
The website Must be secured. The only options shall, use two links. “OFF and ON”.
Part Two: Old Implementation
Back when I started work on this to be controlled by my PBX, with the 6602 extension. The end user would call the 6602 extension and press a option. then the following would happen. (when turning it on)
Hard coded DMX values being sent via OLA daemon over network to a DMXking eDMX4 to get the DMX to the lights to set the color.
The main issue I had with this setup, I could not dynamically control the system. Also you had to be on my PBX, or white listed to be redirected when you dial in to my home phone line.
Part Three: Current Implementation
With those known limitations, I decided to do something about it Implement the scope of work in Part on
Webserver to Austin VMs.
I have a hub and spoke VPN infrastructure all ready in place. Lets look at the Hub.
This Pfsense vm links using OpenVPN to a few sites. but most importantly it links to my apartment.
With that link I can remotely call commands over SSH to turn on and off the system, from the web server. then It is just a matter of calling a shell command to kick off a Shell script on the Austin utility VM.
Above is the PHP code for turning on the system. the off code is 99% the same. Its secured with a username and password. Looking at the aus-netbox host, the system is running a bunch of different Expect scripts.
Turn on outlets on the PDUs
Tell LightFactory to go to a standby cue. over its telnet connection.
Let us look at the integration via expect and and LightFactory
First we say log all output to the shell
the “set timeout 20” is Very Important. as it helps keep the telnet session from hanging. all it means is this, “If I don’t get input from the I//O stream bail out”
spawn says what we are running and redirecting I/O from.
Then its expect “foo” and send “bar”. its pretty simple
To touch on the Light Factory commands. sc31 is a shortcut macro (I created) to release all channels. and cue line calls the cue from the cue list serah #8888 .
Then it exits. Now Serah can then control the system via the LightFactory Myinterface app. As long as she is on the right WiFi Network.
Hi, I have been working on a setup for my Friend/roommate streamer. Serah
This post is going to touch base on automation, and ease of control using COTS and some scripting. The goal of this project was to make it where she could click one thing and start the lighting look. Adjust it while it is live. Then turn it off, via another click.
The system uses DMX control. Switched outlets (via a few network PDUs).
The lighting console software is LightFactory. It sending sACN to Open Lighting Architecture running on a Linux VM. which then sends it to Art-Net, to output two worlds of DMX. This setup allows me to control the system with out the console if need be, Via OLA.
Scripting. I am using Expect to control the PDUs to turn on and off the outlets for different lights. Also I am using it, to send the commands to the lighting console over telnet. I use bash to script turning on and off everything.
I am using a protected web page to allow her to click a “on” or “off” link. that calls via a system exec in php to run the bash script. I do not need to reinvent the scripts when I can just call it.
When the show is running. it can be controlled by Lightfactoy’s mobile interface control.
I created a simple setup for it via the mobile interface builder. seen below.
With that, She is able to control some of the attributes of the show.
A view showing the DC to AC converter, with the test setup. (Bottom to Top of image) Fluke Scopemeter 115, Fluke 87 V, PEAK POWER 800W DC to AC supply. Plugged in to it is a “Extech AC Line Spitter”
I was looking in to my old 800W 120VAC DC to AC supply, to see just how bad the square wave is.
The test in my view was not complete. I did not load test the supply. To see how the wave forms was effected. Due to missing Nut assembly for the Positive lead. I felt it would be unsafe due to insecure connection that could heat up due to possible arcing issues.
With the unit unloaded I proceeded to do a preliminary look at it with the 87 V, a digital meter. The 87, read that it was 120.2VAC and 61.12Hz.
Fluke 87 V, showing 120.2 on the display
Fluke 87 V, showing 61.12Hz
With that I was curious what was going on with the waveform.
I hooked up the Scopemeter in to the mix. AC Neutral to Ground reference for the probe. The probe hooked in to the AC Hot on the line Splitter.
with that, I set the A input channel to 10:1 and took a look.
in mixed scope and meter view on the scopemeter
with that we see that it is going from +120V to 0 then -120V in reference to Neutral.