DSC Wireless Smoke Reporting incorrectly

1. You do not have it set to send auto-Contact ID
2. You have your fire zone programmed as a burg
3. You don't really have a 632 but instead have an AT&T 8000

Actually I do. All other signals are sent correctly.

Zone type 88 is 24hr wireless smoke. The panel reports it correctly on Keypads, but the Contact ID sent is interpreted as Burg with the correct zone info.

Guess the DSC logos should be ignored... :-p

This might be the reason...

Section 381-7 should be off (auto report codes enabled) Section 360 should be 03 in both locations Something other than 00 is programmed as the report code.

Doug

It is, thats why all the other signals are correct...

It is.

FF

To me it seems like the Auto CID is not right for zone type 88 or 87.

I'm just guessing but do you have problems getting anyone to help you or even talk to you for more than five minutes?.

What signal does the central station actually receive, they may be misinterpreting it.

Doug

No Just you...

The gal that is there has to wait for the technician on Monday. (she can't see codes, just the interpretations?) So he is supposed to call me back... Thought I would throw it out to the experts...

If they still use tape he needs another c/s

Its definately sending a 3A.... Looks like I will have to turn off auto CID and put in all the reporting codes...

Strange that DSC requires 87 or 88 for the zone type, have it report correctly locally, but auto CID a general burg...

they should be able to redefine that zone at the central station

They could, but I would rather have it report correctly, in case someone does not look at the zone and only at the code type...

(seem to recall a post about someone programming a waterbug to report a

Also, by redefining it, it is a) not standard, and b) opens an avenue of error (i.e. cs system drops zone info, now its a burg instead of fire. Is that likely to happen? Prolly not, but why open another path for error?)

If I am going to have a monitored alarm system, why would I want to micky mouse it because DSC isn't reporting correctly?

Do it right and you will have less problems and less finger pointing, I would think...

Jose wrote:

Ugh.

Just talked to DSC... A few versions of the 1555 had this problem. Lucky me, I have one.

Only solution is to manually enter all the codes...

They don't really see it as a problem because you *can* manually program it. I wonder how many systems are out there reporting 3A's for wireless smokes because the installer didn't bother to fix it...

I can test mine tomorrow but I doubt anything is wrong with the panel

It depends on the version. I called DSC and they verified that it is a problem on some versions of the 1555.

Mark Leuck wrote:

Did they say how to tell which are affected? As far as I know there is only two versions of the 632

Nope, just that they have heard of it and the only fix is manual reporting...

Mark Leuck wrote: