Helix DSP.3s Conductor Question

I have an issue with the helix conductor. When I first start the vehicle, about half the time the conductor will light up red and there will be no sound. When I double click it, it starts working normally. I was thinking maybe it was because of a low input signal to DSP, but it does it half the time no matter what the volume is at vehicle startup. Volume could be at 1 or 15 and it still does it. Anyone have this experience and if so, is there a way to resolve this?

 

That's one of the error codes in the DSP. When is the last time you updated software in the DSP and the conductor?

The only other thing i could think of is, is your DSP not powering up properly.

It's more of a pain, but if disable the conductor, will the DSP fire up with no issues?

 

Hmm. Yeah I did all my tuning with the conductor disconnected and it never had a problem powering up. I thought I had all the latest software/firmware, but I will check again and make sure.

 

The other piece of that now could there be an issue with your conductor cable. Did it get pinched or whatever?

 

I don't think so, but anything is possible. It feels like it might be a firmware update. Because when it does happen, I just have to double press the conductor and it always starts working perfectly normal.

 

what are you using to trigger the helix to turn on?

 

Remote wire from PacAmp

 

definitely check the firmware/software stuff first.

but if it keeps up, i would get a volt meter on that remote trigger wire and monitor it during startup.

not audio-related, but i've had some issues with hydraulic control systems hard-rebooting during startup. they get the initial 'kick on' key signal from going to start the truck, then the voltage drops out/low during starting, and then they get the stable key-on signal. depending on the stability of the system, sometimes that double-key signal can interrupt the boot process enough that the systems need to be re-set again to correctly and fully boot up.

 

Ended up being firmware. When I did the update I was already at the latest level, but I ran the update again anyway and reflashed it. Hasn't had that error since.