The responsibilities of an automated lighting programmer are similar to that of an airplane pilot in several ways. We have to control expensive equipment, ensure a successful production (flight), and we must be masters of our crafts. Before beginning a flight, an airplane pilot always checks the airplane from top to bottom, inside and out. In the same manner, it is important for a lighting programmer to confirm "all systems are GO" prior to starting a programming session. With any size lighting rig, there are certain procedures and tests that should be performed before a single cue is written. Failure to accurately test the rig can result in long delays or inaccurate values being recorded.
Getting in the Cockpit
First and foremost, the lighting console must be checked to guarantee it is working properly. As early as possible, you should confirm that the console will boot up and that the peripherals you need are functioning as expected. Ensure that connected monitors are functioning, network expansions are communicating and wing devices are found. Furthermore, check that any mice, keyboards or other accessories operate in the proper manner. Additionally, you should confirm the version of software in the console is the most current (or the version you want to use). Once the console and peripherals are confirmed to be in good order, then you should do the same checks with the backup console. During this time, I also like to test that the UPS actually holds a charge and that the consoles can properly load and save show files.
Examining the Aircraft
Once the console is operational and you have entered your patch information, you can connect it to the lighting rig and begin to validate several key things. First, you will know right away if your console is outputting DMX or not. If the fixtures are non-responsive to the console then there is likely a problem with the DMX output, data lines and distribution, or Ethernet-to-DMX nodes. If your fixtures begin flashing and moving erratically, then you probably have the patch incorrect or your data lines are plugged into the wrong outputs. Work with your lighting crew to resolve these problems quickly so that you can move on to the next phase of testing.
Checking the Flaps and Rudder
With the console communicating with the fixtures, you are now ready to test all your fixtures. The first thing I do is check to see that they all come on; this way I can rule out power and data line runs. Typically, I perform these tests by fixture type or by location, depending upon the show. I will bring all fixtures of a particular type to full intensity and confirm that they all turn on in open white. By breaking down the rig into smaller parts, it is easy to quickly determine if a fixture is not functioning. I will make a note in my notepad of any fixtures that do not turn on. I then send a strike or home command to the troubled fixtures and see if they turn on. At the same time I test to see if the fixtures turn on, I typically pan and tilt them as a group. This enables me to quickly see which fixtures still have their pan and/or tilt locks enabled. Also, by moving them as a group, I can easily determine if a certain fixture has a different speed mode enabled, has pan/tilt inverts on, or is hung the opposite direction from the others. Again, I will make a note of any fixtures that are not perfect. At the end of my testing I can provide the crew with a list of things to fix. If I have any digital fixtures or media servers, I confirm that I have control of the various layers and that they are outputting to the proper display devices.
Looking at Each Fuel Tank
Next comes one of the most important tests. It is imperative to confirm that each fixture is addressed as expected. This requires an individual test of one fixture at a time. Without this test, you may never know until it is too late that you have two fixtures responding to the same fixture number. I like to use the console's Highlight (or ID) function to assist with this test. The Highlight function found on most consoles will set intensity at full with an open beam for the currently-selected fixture (see your console manual for full details). I will activate the Highlight function and then select the first fixture in my rig. Then I turn the tilt encoder and just keep rotating it around and around without stopping. Now I can just press the NEXT key on my desk to cycle from fixture to fixture until I have seen them each move. By continually adjusting the tilt encoder, each fixture will tilt up towards me as I press the Next key. If I see more than one fixture come on and move at the same time, then I know that one of them has the wrong address. Likewise, I will also find times when no fixture turns on because they are misaddressed. Again, I will notate the fixture and what its address should be so that the crew can make corrections after I finish my testing.
Kicking the Tires
After confirming the controller and fixtures are correctly configured, I inspect the capabilities of the fixtures. I will perform these tests by selecting all fixtures of each type and placing them in a position where I can see the output of each. Then I run through the various parameters to ensure that everything is functioning. First, I run through the color mixing, fixed colors, and CTO filters. Next, I run the zoom, iris, frost, shutters, strobe, and other functions. I also focus on each gobo wheel and ensure that all gobos match and that they are properly installed. By adjusting all fixtures of the same type simultaneously, it is very apparent when one behaves different than the others. With digital fixtures or media servers, I will ensure that any custom content is loaded and plays back correctly. When I am satisfied that all fixtures are functioning correctly, then I am ready for takeoff and to begin programming.
Have a Great Flight
This pre-flight checklist will undoubtedly save important programming time by identifying problems before you begin programming. Depending on your gig, you may or may not need to perform such in-depth examinations. For example, when working on a permanent or semi-permanent installation, you probably do not need to check the DMX addressing, the functions of the fixtures or pan/tilt locks on a daily basis. However, if you are touring, you will want to confirm the pan/tilt locks are disabled every single day. In addition, some of these tests can occur while the lighting rig is still on the ground. If, by testing early, you can reduce the need for the crew to climb in the truss or lower the rig, then you will not only save time, but you will also gain kudos from your crew. As with an airplane pilot, it is essential for an automated lighting programmer to be familiar with the lighting rig and to confirm the entire system is working as planned. If trouble is found, it should be documented and reported to the crew for quick resolution. By ensuring that all is working well on the ground prior to take-off, you can rest assured that your production and programming will fly high and please your audiences.
