When I create a Channel Summary report, the Messages window pops up listing an "error at address" for each of the dimmers I designated in the Dimmer field for each fixture.
Someone please guide me to the correct Help screen so that I can figure out how to correct these errors. I've been searching in LXBeams Help for "patch", "error", "duplication", and combinations of those to no avail.
--
Ralph M
Patch errors in LXBeams Report
-
rmessnerjr
- Posts: 5
- Joined: Fri Oct 07, 2011 1:43 am
Patch errors in LXBeams Report
Ralph Messner, Worship Technologies Director
Tempe Nazarene Church, Tempe, AZ
Tempe Nazarene Church, Tempe, AZ
-
rmessnerjr
- Posts: 5
- Joined: Fri Oct 07, 2011 1:43 am
LXSeries applications primarily consider the "Dimmer" field to be a DMX address. In particular, the Channel Summary report has a patch column that represents the channel patched to an address.
In the Channel Summary, M-Channel List and M-Dimmer List, devices and moving lights can be patched by providing only the base address (which is expanded based on the device info table).
LXSeries applications allow some flexibility in the format of address numbers. With the exception of the above reports, they will recognize a dimmer of the form 1a, 1b, 1c as distinct. This notation might be used to denote manual replugging of a single physical dimmer.
LXSeries applications also allow the specification of addresses in universe.dimmer format. For example an dimmer might be specified as 2.1. When this appears in a channel summary it appears as 513.
Patch errors are displayed when more than one channel is set to control a single dimmer or address (which is not possible). In your example, there is no distinction between NSI1 and NSI2 (because the characters are not recognized) and that produces an error message.
---------
In the case where you want to document the dimmer number in a rack differently than its DMX address, you might make use of the circuit field.
For example, you could have a circuit of "Rack1#1" with an Dimmer address of 1. And have a circuit of "Rack2#1" (the first dimmer in rack 2) and that might actually have the Dimmer address of 13. This tells you where to look for the physical dimmer as well as the address needed to patch your console.
In LXSeries applications, the circuit field is recognized as a number or a number followed by a single letter, just like a dimmer or channel. But, if you don't need to generate a Circuit List report, then this won't be a problem.
In the Channel Summary, M-Channel List and M-Dimmer List, devices and moving lights can be patched by providing only the base address (which is expanded based on the device info table).
LXSeries applications allow some flexibility in the format of address numbers. With the exception of the above reports, they will recognize a dimmer of the form 1a, 1b, 1c as distinct. This notation might be used to denote manual replugging of a single physical dimmer.
LXSeries applications also allow the specification of addresses in universe.dimmer format. For example an dimmer might be specified as 2.1. When this appears in a channel summary it appears as 513.
Patch errors are displayed when more than one channel is set to control a single dimmer or address (which is not possible). In your example, there is no distinction between NSI1 and NSI2 (because the characters are not recognized) and that produces an error message.
---------
In the case where you want to document the dimmer number in a rack differently than its DMX address, you might make use of the circuit field.
For example, you could have a circuit of "Rack1#1" with an Dimmer address of 1. And have a circuit of "Rack2#1" (the first dimmer in rack 2) and that might actually have the Dimmer address of 13. This tells you where to look for the physical dimmer as well as the address needed to patch your console.
In LXSeries applications, the circuit field is recognized as a number or a number followed by a single letter, just like a dimmer or channel. But, if you don't need to generate a Circuit List report, then this won't be a problem.