Last Updated: Aug 04
Version 5.0 Imagescans require 3032 Controller software version 2.03. Internal and DMX programs should remain unaffected by the upgrade.
New Features in Version 5.0
- Lamp off via DMX: To switch the lamp off via DMX, set channel 0 to 253-255 and set channels 1-6 to 255. These levels must be held for at least 5 seconds. (See DMX protocol in user manual).
- Gobo indexing now uses the scene time: This makes it possible to keep an image straight up while panning slowly. This feature is implemented only by Martin protocol and internal memory programs.
- Focus positioning now uses the scene time: This makes it possible to keep the image in focus while panning. This feature is only implemented for Martin protocol and internal memory programs.
Shutter speed has been increased: it is recommended that the shutter be replaced with the new, lighter shutter.
With previous software versions, synchronization could be problematic if several fixtures were running programs from memory in the same setup. Even with the most precisely timed programming, the fixtures would fall out of sync sooner or later due to small variations in the electronic components in each fixture.
Synchronization can be achieved by linking fixtures and setting one to act as "host" and the rest as "clients."
Normal host/client operation, where the clients just mimic the host, is not useful in the Imagescan. Each fixture must be independently programmable. For this reason, 3 different synchronization modes have been implemented. The client settings are identical for each mode, only the host fixture settings change.
Mode 1: Synchronized Sequence Start
Set host DIP switches 10,3,1 on; client DIP switches 10,3 on.
In mode 1, the host sends out a sync pulse every time it executes scene 1. The client fixtures respond by snapping to scene 1 and restarting the sequence. They execute their programs using their own scene time. If a client fixture completes its program before the host, it will not loop to scene 1 but will hold and wait for the next scene 1 sync pulse.
Mode 2: Synchronized Scene Time
Set host DIP switches 10,3,2 on; client DIP switches 10,3 on.
In mode 2, each time the host executes a scene, it transmits the scene time. The clients use the host´s scene time for their own scenes. Clients execute all scenes in their program sequence and then loop to the first scene. Thus, if fixtures have different numbers of scenes, sequence start is not synchronized.
Mode 3: Synchronized Sequence Start and Scene Timing
Set host DIP switches 10,3,2,1 on; client DIP switches 10,3 on.
In mode 3, the host transmits the scene 1 sync pulse, as in mode 1, and the scene time as in mode 2. All fixtures execute the same scene number with the same scene timing. If a client is programmed with fewer scenes than the host, it will not wait at the end of its sequence, but will loop back to the start. If a client has more scenes than the host, it will never execute them because it will snap to scene 1 when it receives the scene 1 sync pulse.
Link the fixtures normally but do NOT terminate the link. (Terminating the link causes unnecessary drain on the battery of the remote.)
DIP switches MUST be set prior to powering up the fixture - changing DIP switch settings after power-on may not work.
Which mode should be used depends on the setup. If the scanners need to project at a certain location at the same time, then mode 1 or 3 should probably be used. If all that is needed is a more synchronized look, mode 2 is probably the best option. In any case, good results will require a bit of planning before programming the fixtures. Experimentation suggests that the best results are obtained when the scene times on the host are 1 second or longer.
Any fixture, regardless of position in the link or mode in which it was programmed, may act as host. There should be only one host - having several hosts will cause unpredictable behavior.
When the host fixture is powered on, it sends a standby signal to synchronize the start of scene 1 . This startup synchronization will only work if all fixtures are powered up at the same time, or if the host fixture is the last to be powered up. This is only important if mode 2 is used and consistent execution is needed.
Fixtures may still be programmed normally with the remote control, even when setup as host fixtures.
It is still possible to connect the remote control to the link with a fixture acting as host. However, any programming with the remote control will affect all fixtures - it is probably only useful when programming fixtures with the same scene contents.
Also - when using the view function on the remote - there is a slight chance for a transmission collision between the host´s sync pulses and the remote´s ´voltage level´ transmission to the fixtures. Therefore, when using the view function to check the programs, it is best to switch off the remote while the fixtures are running their programs. While a transmission collision will not damage the remote or the fixtures, the results are unpredictable and in the worst case could cause the internal programming to be erased. The most likely consequence is that the host will stop transmitting the sync signals or that the clients will stop receiving them. If this happens, stop playback by pressing any button except t view: the fixtures should recover after 15-20 seconds. The most reliable way to use the view function is to press and hold the view button and then to switch off the remote while still holding the view button down.
Finally, the indication of problems with gobo indexing has changed slightly. During reset - power on or serial - if the sensor fails or the gobo holder micro-switch is not closed, the shutter will open and the mirror will move between extreme left and center twice. If the switch is closed, the gobo will rotate fast; if the switch is open, the gobo will be static. If an error is detected the software will time-out the indexing procedure after approximately 30 seconds. Then it should be possible to continue normally, except that it is not possible to open the shutter if the micro-switch has not been closed.
The calculated gobo indexing time does not compensate for gobo acceleration/deceleration before starting the movement to the indexed position. This means that if the gobo was rotating in the scene before, the calculated indexing time will not match the selected time. This problem can be avoided by programming a short scene with no gobo rotation before a scene with indexed gobo position.
For short movements over a long time, the built-in ´speed calculator´ does not have sufficient resolution to match the exact timing. The result can be seen as one of the effects continuing its movement for a short time after the rest of the effects have stopped. If neither of the positions are critical, the problem may often be fixed by adjusting the positions in either the current scene or the previous scene, or by changing the movement time slightly.
The speed of the gobo rotation has been significantly slowed to reduce problems with noisy bearings and gobos missing indexed positions.
The shutter speed has been increased. The increased shutter speed may lead to problems, especially when using the blackout feature. A new shutter using a lighter material is now in production and is recommended as an upgrade with version 5.0. A part number for the shutter assembly will be available soon.
The following bugs have been reported but not yet verified:
- Mode 1: Client(s) sometimes gets stuck on a single scene.
- All modes: Removing the gobo module while the fixture is running in client mode makes the shutter behave unpredictably.