Electronic Alarms and Home Security Devices - Light [4] General System Tamper: Tamper has been detected in a module

Hi, when my wife and I bought our current house back in 2003 we had an ADT installer put in a DSC Power 632 system for us. It has 2 door zones, 2 motion detectors, fire and carbon monoxide detection, and wireless key fob capability. After we fulfilled our contract with ADT we opted to discontinue their monitoring service. I eventually powered the entire system down because of the above trouble code and left it like that for almost 2 years.

I recently gained an interest in the system and powered it back up. My ultimate goal is to send alerts to my mobile phone when any zone breaches occur and perhaps even interface the security system with my home computer network. I may be reaching out to everyone on here again when I get ready to cross those bridges, but my most urgent goal at this point is to address the above trouble code. For starters, figuring out a way to subdue the audible chirping so it doesn't disturb us in the middle of the night would be helpful, although ideally I want to identify the source of the problem and fix it once and for all. I read on another forum where a zone expander was causing problems with the tamper circuitry, thoughts?

Just to make sure: Is the 4 showing _all the time_ or just when you press *2?

I press [2] which lights up a 1, then I press 1 again and it shows a 4.

Look at the wireless receiver board. There should be a Tam (tamper terminal). There should be a wire going from that terminal to any common terminal. If there isn't, add one.

If that doesn't clear the tamper, try turning off the RF jam detection feature. It's a frequent source of this issue.

MrRon,

There is only a single system board and a battery inside the "box". Is the wireless receiver board usually integrated on the main board or is it co-located outside the box? I ask because I do not see anything labeled TAM on the main board, though there are a few common terminals as well as some other ones; AC, +Aux-, +Bell-, Yel, Grn, 1 PGM 2, and Z1-Z6.

Also, I checked and the audible RF jam trouble beep is not enabled and the RF jam event log is turned off.

Something else that is curious, and I don't know if it's related or not. There was a jumper terminal just laying inside the main box. The only spot on the main board for this is labeled Q16 but when I tried jumping it the system went nuts and started throwing a zone fault. I didn't catch which zone it was complaining about though. Do you know off hand if this jumper should be on there or not and what it's for?

That means that you don't have the regular wireless receiver board, one of your keypads must be a RF model.

No, there's no tamper terminal on the main board. If you have no expansion boards, you should not have this particular trouble. The only other thing to check is some versions of the LCD 5501z32-433 keypad had a tamper switch option on the mounting plate.

Just for fun, try running the supervision routine (*8 [installer code] 902).

It's possible that way back when, a module was removed from the system, but whoever did it never reset the supervision.

No such luck MrRonFL. I ran the routine to reset supervision and I am still having the same problem. You mentioned a tamper switch on the mounting plate of the keypad. I haven't pulled this out yet to look but I assume you mean behind the keypad?

Also, did you see my comments a few posts ago about that jumper I found? Any thoughts about that?

Thanks!

That jumper has nothing to do with module supervision.

If you refer to your installer manual, it tells you that that jumper is to be removed if the PGM 2 is set for either 2-wire smokes, or for a 24 hour panic input.

That said, what is connected to your PGM inputs?

There are configurations intended for connected the Links 1000 cell dialer that, if it were removed without resetting the PGMs to different settings might do this.

If there is nothing connected to your PGM outputs, try go to program, then enter 009 19 10 then exit programming.

If someone had that PGM set as an input zone, _then_ you might need to put the jumper back.