Supported receiver types
Every receiver line names the receiver it is talking to by number — the TYPE= value in its concport configuration. That number selects the decoder, and it is the same number on both generations of the Concentrator: a line that ran as TYPE=52 against SBNConcentrator.exe runs as TYPE=52 against sbn-concentrator.
Sixty-one receiver types are supported — every receiver type the previous generation supported.
The table
| TYPE= | Receiver | Notes |
|---|---|---|
| 10 | ITI | Polls the receiver once a minute |
| 11 | FBI | Polled |
| 12 | Ademco, older receiver | Superseded by type 13; still supported for existing lines |
| 13 | Ademco 685 | Carries Contact ID inside the 685's own framing |
| 14 | Radionics 6000 / 6500 / 6600 | |
| 15 | Silent Knight 9000 | Handshakes: sends a heartbeat to the receiver and carries a counter between messages |
| 16 | DataVision | |
| 17 | Aritec TAC-90 | |
| 18 | Robofon, original | |
| 20 | Franklin | Up to 26 records in one message |
| 21 | McCulloh II | Sends a line-open handshake |
| 22 | HSL | Session protocol — the line negotiates a session before signals are accepted |
| 23 | DMP / SCS1 | |
| 24 | Veritech V300 / Moose | The panel repeats each record; a matching pair is required |
| 26 | SESCOA 3000 | |
| 27 | Seaboard RF | |
| 28 | SPC-5000 | Polled |
| 29 | IEI E6800 (Australia) | Sends no acknowledgement |
| 30 | Care-net | |
| 31 | Securitel — Honeywell Australia STU/ATU | Carries state between messages |
| 32 | Scancom | |
| 33 | HSL text reader | Sends no acknowledgement until a pattern matches |
| 34 | SIA | |
| 35 | Derived Channel 1 | |
| 36 | Pro-Com Extended | |
| 37 | Sensus SafeCom | |
| 38 | SurGard CPM2 | Multi-format: SurGard, SIA and Ademco on one line |
| 39 | TAR-200 (Audiolite) | |
| 40 | Debug receiver | Decodes nothing — logs what arrives, for commissioning a new line |
| 41 | Robofon RBM-600 | |
| 42 | Morse | Polled |
| 43 | RC-4000 printer | A CFGFILE= rules file is tried first, then the built-in decode |
| 44 | InfraNet | Session protocol; sends no acknowledgement |
| 45 | Audiolite on a parallel port | No framing; sends no acknowledgement |
| 46 | DomiTech DM8 | |
| 48 | Receiver test | Dials out and sends; decodes nothing |
| 50 | Keltron | |
| 51 | Multicom | |
| 52 and 63 | SurGard MLR2 | One decoder under two type numbers; the wire format is the same |
| 53 | Vigilante fire panel | Reassembles messages across reads |
| 54 | IBS GSM | |
| 55 | Osborne-Hoffman | Several message formats on one line |
| 56 | SECOM CTIP | Reassembles messages across reads |
| 57 | TFS F1 | Handshakes: polls, answers each message with an acknowledgement built from that message, and resets the connection after three unanswered polls |
| 58 | SDN SMS gateway | Reads messages from the file named by IFILENAME= |
| 59 | AlarmNet — Danish national alarm transport | Session protocol with its own link layer; sends no plain acknowledgement |
| 61 | Alarm Force | |
| 62 | SDS | |
| 64 | Emerson / Emergency 24 | Session protocol; sends no acknowledgement |
| 65 | Cellularm | |
| 66 | OzVision | Sends no acknowledgement |
| 67 | Computech | Polls every six seconds |
| 68 | Atlas | |
| 70 | Stealth | |
| 71 | BT Redcare gateway | Sends no acknowledgement by default; carries state between messages |
| 72 | Dualcomm | |
| 74 | Risco Cloud | |
| 75 | SIA DC-09 over IP | Encrypted payloads are decrypted with the keys in SIADC09AesKeys.ini |
| 76 | Rules-driven receiver | The receiver is defined by the file CFGFILE= points at, not by the type number |
| 77 | RSM-02 | Field mapping comes from the file CFGFILE= points at |
| 900 | Contact ID | Bare Contact ID on a data line. There is no equivalent number on the Delphi Concentrator |
What the notes mean
Session protocol. The line is not a plain stream of messages. The receiver and the Concentrator exchange control frames first, and signals only count once the session is up. Types 22, 44, 59 and 64 work this way. Types 15 and 57 handshake in a smaller way — they carry state between messages and answer with something computed from what arrived, rather than with a fixed byte. A line of one of these types can be connected and quiet for a while after it opens — that is the session coming up, not a fault.
Polled. The Concentrator sends to the receiver on a timer instead of only answering it. Nothing extra needs configuring; the cadence belongs to the receiver type.
Sends no acknowledgement. Some receivers expect nothing back, so the Concentrator answers with nothing. A quiet outbound side on those lines is correct.
Rules-driven. Types 43, 76 and 77 read their behaviour from a file, so adding or changing a format is a configuration change rather than a new release. Point CFGFILE= at the file. Type 76 accepts either the JSON rules format or the older text grammar; a missing file stops the line from opening.
Contact ID (900). Contact ID reaches most sites inside a receiver's own framing — through type 13, type 38, or types 52 and 63 — and those lines stay as they are. Type 900 exists for the case where bare Contact ID arrives on the line on its own.