Care-tech 2500 Not Alarming

[Deltaseven]

We have a site with 2 Castle Care-tech 2500 panels linked through the RS485 bus. Reasonable sized site, 3 PSUs, 3 Keypads, 50 zones (mixture of PIR, PA and M.Cs). The site is split into areas A and B. Area B is a sensitive area inside of area A.

The system sets fine (A and B or independently), but when any zone is triggered, there is no reaction from the panel. Entry door does not start a delay, walk-through or intruder do not cause an alarm. Even a zone set as PA in area A (or B ) will not cause an alarm condition. The log shows the closing and opening.

All the PA's set-up as in Areas ABCD, and they do cause an alarm condition.

This system has been working fine, and it is only after moving a few PAs that this fault has come up - whether it is related or not, I am not sure - the customer does not know exactly when the problem started.

Whilst fault-finding, I found that 2 of the PSUs were providing low voltage (12.2V and 12.4V), but since they are only feeding PIRs and 1 keypad, I don't think this is the fault (but they will be replaced anyway).

Castle Tech-support have not come across this fault before, and suggested I power down and up again, but this made no difference.

Any thoughts?

[BUSTER]

I presume the end stations are connected using the gateway module and are addressed A and B

The comms unit must be plugged onto end station A

Recommend 'clear logs'

From diagnostics can you view the id point condition for zones on each end station?

Is it digi or Redcare?

Is the alarm response for areas A and B set to 'Full Alarm'

Are the digi/stu outputs programmed for area alarms?

[Deltaseven]

I presume the end stations are connected using the gateway module and are addressed A and B

The comms unit must be plugged onto end station A

Recommend 'clear logs'

From diagnostics can you view the id point condition for zones on each end station?

Is it digi or Redcare?

Is the alarm response for areas A and B set to 'Full Alarm'

Are the digi/stu outputs programmed for area alarms?

22601[/snapback]

Units are addresed A and B and connected using gateway module.

Id point condition shows zones opening and closing on both panels

Unit is on Redcare

A B C and D are all set for full alarm

The STU outputs are programmed for any areas - but I don't think the STU programming is the problem, as we don't even get a local (bells) alarm - but I am ready to try anything at this stage!!

Thanks,

D7

[Guest Peter James]

How are you setting it did you try a force set using the engineer code?

Is there a bell delay progged?

Castle tech support is very good and this one sounds like you should call them from site so they can talk you through it.

Pete

[Deltaseven]

How are you setting it did you try a force set using the engineer code?

Is there a bell delay progged?

Castle tech support is very good and this one sounds like you should call them from site so they can talk you through it.

Pete

22616[/snapback]

Hi there,

I have armed using Engineer Force Arm and customer code - same result both times.

Bell delay is set to 0. (Even if it wasn't the entry timer should still start on violation of the entry door, and the log should record the activation)

Castle tech-support are stumped on this one - they have not heard of it before. We went through most of the programming options, which they confirmed were fine. I powered down (and left it down for a good 15 minutes) and powered up in case there was some induced voltage lurking somewhere, but no joy.

Will be going back tomorrow with 2 replacement PSUs, and another engineer to see if a fresh pair of eyes spots something obvious.

I guess the final option is to clean start and reprogram, which I really don't want to do if I can avoid it as the whole system is a bit complicated!!

Thanks for all advice,

D7

[BUSTER]

Can't see the psu causing the problem as long as you've got sufficient volts at the detector end. Have you tried re-starting the gateway module?

[Deltaseven]

Can't see the psu causing the problem as long as you've got sufficient volts at the detector end. Have you tried re-starting the gateway module?

22630[/snapback]

I guess the gateway would restart when it is powered down (at the same time as both panels and all 3 PSUs)

[BUSTER]

After everything has been powered up short the R and S pins on the Gateway module to ensure that all components are initiallised

I think the best way forward would be to do a full factory reset and re-programme, it sounds like a software glitch

[Deltaseven]

After everything has been powered up short the R and S pins on the Gateway module to ensure that all components are initiallised

I think the best way forward would be to do a full factory reset and re-programme, it sounds like a software glitch

22650[/snapback]

Yeah - I have a feeling you are right there Buster! But I really, really don't want to!!! Still, if there is no choice, there is no choice.

Thanks,

D7

[Deltaseven]

WAY-HAY!!! We got there in the end! Without re-programming too.

It turns out that somehow the programming had changed so in "PROGRAM VALID ENDSTATIONS" Valid stations were CD - (AB had been turned off!!)

We obvoiusly don't know for sure, but I suspect someone may have been playing on the keypad while the panel was in Engineering for me to move the PAs - as I KNOW I didn't go into that submenu.

Anyway - one I will store to memory!! Thanks all for advice given,

D7