Two zones now as one.

[Ingo]

Hi,

I recently suspected a cable problem on two of my zones. When I trigger zone 21, both 21 and 22 activate. Just before I climbed into the ceiling to investigate I removed the wires from my slave unit and shorted zone 21. When I did this both 21 and 22 activated. Shorting zone 22 didn\'t produce any results. I finally had to move zone 22 to another input.

Can someone tell me if zone circuitry work in pairs and if there is something wrong with 21 and 22 that there may be a common piece of hardware that could be responsible? Also, is it fixable or should I just leave it be?

Thanks,
Ingo

[admin]

The circuit for slave zones 5 and 6 does not work in pairs. Each has its own circuit., other than the fact that they are next to each other. Perhaps there is a short on the board between Z 21 and Z 22, but I would expect that shorting zone 22 would also trigger zone 21
Are the 2 zones programmed the same zone type? with EOL resistors?

If you can, measure the voltage on zone 22 when you short zone 21

[Ingo]

The two zones are programmed for PIRNightAway but only the one triggers both zones. In my case IP15 triggers an IP15 and IP16. If I short IP16 then nothing happens.

I measured the open-circuit voltage of both and they are both around 1.1V give or take a couple of millivolts.

I don\'t use EOL resistors on them, they are either open or closed circuit.

The following are voltages measured:

IP15 (with IP16 shorted) = 1.1V
IP16 (with IP15 shorted) = 1.1V

Can you please send me a portion of the diagram showing the circuit information of these zones so I can try and trace which component could be at fault - depending how long the warranty on these panels are obviously :-)

Ingo

[admin]

I have sent an email with some help

[Ingo]

Thanks Chiu,

When I have lots of time to take that slave out of service I will search for the fault. In the meantime I just moved it to another zone.

Ingo

[Ingo]

Thanks to the technical information provided by Cytech I traced the fault to a faulty MPU01-SEM itself. Something internal to the MPU seems to be causing the condition. The workaround was just to move the zone to a spare one.

Regards,
Ingo