12v trigger on at boot- a 6.86 bug?

[starford]

After updating to 6.86 formware on my C1, I observe the following:

At boot up (hard power reset, or after power failure), the C1 will turn on the 12v triggers, and I think one stays on. I have a pair of A23s attached to a 12v trigger on the C1 that will stay on indefinatly. This is a new behavior compared to before.

This creates a pair of unattended, unobserved room heaters. Powering on, then off again, the C1 via front panel corrects this state.

Anyone else seen this behavior?

[Peter Nielsen]

Yes. I see this problem too with v6.80. It is repeatable. I have my T3 connected to the second programmable output, which is set to activate on AUDIO1.

Test scenario:

I set the C2 to VIDEO1. The T3 is not triggered, and is in standby state. I switch off the C2 (to standby). I unplug the C2 from the wall. When I plug the C2 into the wall again, it is still in standby as it should, BUT the T3 is now powered on!!! =C2 SOFTWARE BUG!!!

In order to correct this, I have to power on the C2, switch to AUDIO1 and then back to another input. That finally switches off the T3....

So, yeah, the software is flakey. Every time there is a blackout I see this problem over and over again...

Peter

P.S. I have my first programmable output to trigger on "power on" with a 2 second delay. Interestingly enough, this always seems to work correctly! The first output does not come on by itself after a power outage.... Strange, huh?! I guess the problem is only occuring when setting the output to trig for a specific input like AUDIO1 or something like that...

[starford]

I'd guess that we're seeing something more related to a rapid trigger signal than something caused by associating a trigger with an input. My theory is that the C1/2 sends the 12v trigger outputs high (on) very briefly when the system boots up. I think the 12v triggers then go low (off) immediately after that, but some equipment isn't fast enough, or a built-in heuristic doesn't allow it, to follow the rapid high-low trigger signal. Thus, we end up with gear sitting idle & consuming power.

Your observation that a 2 sec delay seems to work better would tend to support my theory of a rapid high-low trigger signal causing our issue. The 2 sec delay may buffer the outputs such that the high and low are spaced out.

Funny we're both seeing this with Parasound Halo gear. My other 12v trigger off the C1 goes to a external AC switcher that has no such trouble.

So, in short, I think the 12v trigger gets sent high on boot, but goes low so quickly that the gear doesn't respond (or is designed not to respond) to it. Resolution requires repeating the trigger event manually by either powering up/down or by selecting/deselecting the associated trigger event.

[Peter Nielsen]

No. I don't think this is the case. I'm pretty sure the output STAYS high.

I will check this with a scope and report back...

Peter

[Peter Nielsen]

Yes, this is definitely a bug. Here's how to repeat it:

Set P1 as a power-on trig with 2 sec delay
Set P2 as an AUDIO 1 trig, no delay
Set the C2 input to VIDEO1 (unless it already is that)

Switch off the C2, and unplug it from the wall. Wait a few seconds and plug it back in again.

Now the P2 output will be on, and it STAYS on. Power on the C2. Power off the C2. P2 STAYS ON!!!

The ONLY way to get P2 to turn off is to switch the C2 to AUDIO1 and then back to another source. That finally takes care of it and all is well until the next power outage...

I hope that Parasound reads this and can repeat this problem.

Peter

[Peter Nielsen]

Well... Today I decided to pull the (trigger) plug. With the frequent temporary outages after Ophelia, I seem to find my T3 on every time I walk by the media room.

I guess I'll have to manually turn on the T3 until Parasound releases a fix for the bug in the C2 software...

Peter

[Chris D]

Well, good that y'all are posting this here for Parasound to read. Peter, I'd suggest sending an E-mail to the tech department summarizing the bug or directing them to this thread.