XTI 4002 - Stereo Mode: Ch 2 Signal Meter Shows Activity with No Input or Output Connectedxti-4002 xti 2 series 4002 xti 1002 xti 2002 xti 6002
Posted 26 July 2012 - 06:15 PM
In stereo mode, when I connect a signal to just the channel 1 input and the corresponding channel 1 output is connected to an 8 ohm speaker – not only does the channel 1 signal meter on the front of the amp show activity – but the channel 2 signal meter (with gain level off) also illuminates – with no channel 2 input or output connections. The amount of signal activity on the channel 2 meter seems to match the channel 1 meter. This happens on both new amps.
Then, I made the same connections on channel 2.
I turned the gain down on channel 1 and just using the channel 2 input and output – only the channel 2 meter illuminates and shows activity – the channel 1 meter did not show any signal activity.
In stereo mode, with the channel 2 gain level off, why would the channel 2 signal meter show the same signal activity as channel 1, with no channel 2 input or output connections?
Let me know if you need more information.
Posted 02 August 2012 - 03:49 PM
I have found the same behavior with my units: When signal is input to Ch1, Ch2 shows activity! Only the Signal led is lit though on Ch2.
Do you have more than the Signal led lit?
I have advised Crown and am waiting for a reply to this behavior.
Posted 04 August 2012 - 11:05 PM
Only the Channel 2 signal indicator on the amp is lit. I checked both System Architect and Band Manager - the software is accurate - only the channel 1 signal appears in both software programs.
Maybe it's an issue within the amps (hardware) only. Since it occurs on my two new 4002 amps and yours as well, it will be interesting to hear what Crown has to say about this.
Let me know when you hear from Crown.
Thanks for input.
Posted 07 August 2012 - 07:28 AM
Posted 22 August 2012 - 10:42 AM
Crown just notified me that there is a firmware bug that causes the channel 2 meter to show activity with no input or output connections.
The issue will be fixed in an upcoming firmware update.