User manual

2-26 Troubleshooting Technobeam
®
User Manual
2. Is more than one device affected? If so, and the devices are addressed
sequentially on the link, check to make sure addressing was done
properly on all affected devices. In particular, if you are using fixture
numbering, review the DMX channel boundaries for all affected
fixtures.
Table A-5 on page A-16 shows fixture number to DMX channel
boundaries for Technobeam.
3. Make sure the last device on the link is terminated.
4. Are the gears and motors moving at all? If not, check for a loose cable
connection or a cable break somewhere on the link. If possible, verify
cable integrity or replace questionable cable with known good cable.
5. Make sure the controller is generating output. Consult the
documentation provided with the controller for more information.
6. Verify the DMX data for other fixtures on the link (see “Viewing DMX
Status and Construct Values (FIXT)” on page 3-24 or “Viewing DMX Data
for Another Device (DATA)” on page 3-26).
Menu Error Messages
This section lists the possible error messages that can appear on the
fixture’s LED display, as well as suggested actions. If the suggested
action does not solve the problem or if you have additional questions,
contact High End Systems Customer Service in one of the ways shown
in the section titled “Contacting High End Systems” on page Intro-4.
Addr Lost
The fixture’s software was unable to retrieve the fixture number or
DMX start channel from non-volatile storage. Try unplugging the
fixture, waiting a short time, then plugging it back in. If this error
message reoccurs, contact High End Systems Customer Service in one
of the ways shown in the section titled “Contacting High End Systems”
on page Intro-4.
Boot Diff
(Boot difference error.) This message may occur after a software
upload or crossload if new boot software has been included in the
upload. Selecting BOOT from the Test menu will copy the new boot to
the boot software storage area, and correct the cause of this error
message.
EMEM Ack
This error may occur during data storage when an attempted write has
taken too long. Attempt the operation again. If this message reoccurs,
contact High End Systems Customer Service in one of the ways shown
in the section titled
“Contacting High End Systems” on page Intro-4.