TheAlarmTech.com

I know this is old but it's a system sensor loop you're looking at. I don't remember the values but the irc3 sensitivity reports had the numbers for the specific device types listed as a range of ok, somewhat dirty and real dirty

Any serial printer or even your pc can be used to capture data from the port. (Provided you've enabled the card in the SDU)

You realize if you're not certified to work on EST systems you shouldn't touch it, right? LOL. It's typical after testing or just cleaning and re-installation of smoke detectors. You need to read in the map and check mapping errors, 90% of the time there are none. frequently you can just commit all ...

plan a : read in the map. use 'alt printscn' to capture a picture of it. open the picture in paint. arrange the configure window and the paint picture side by side and add the devices to the database or just write them down. then use actual/expected form to commit the devices. plan b: get a barcode ...

Chaos, that's where you screwed up. You should have ran a sensitivity report to get the model number.

That's defeating the whole purpose of the companies that earn the right to train their employees and get keys. Your company should not have taken on those systems.

You need to make up a special cable with jumpered pins to download.
You also may need the patched version.
Finally you might need a windows 95 pc.

I know they made: CM1 CM1NX CMIN CMIN-SG CM2N CM2N-SG We're working on a networked irc-3 system that is randomly locking up. the stiickers are missing from the main cpu card. The main panel has only a ZB0-8 card while the cm-2n nodes are populated with zas-2 cards. Versions of firmware aside (3.3/4/...