Cloud CLSS Receiver and TXID

For some panels, Manitou interprets the TXID as the number with a dash and a number. This can be confusing if a customer was not expecting the dash and number,

The panel the customer has was reporting like a Silent Knight IFP 2000 panel. A Silent Knight IFP 2000 panel is an industrial panel for large buildings/high rises where it can report from multiple panels (sub transmitter IDs) and modules.

This panel sends a signal like this:

// S08342[#1651|NFT01230018/FT01220019/FT01330020/FT01440021/FT01550022/FA02660024]
// Silent Knight IFP 2000 panel - address field is PPMMZZZZ where PP is panel number (sub-txid), MM is module number and ZZZZ is the actual zone number

Explanation from the signal above:

S = SIA signal

08342 = DNIS 08342

[ = segment separator

# = account number identifier

1651 = Transmitter ID 1651

N = new block

FT01230018 - FT from panel number 01, module number 23, zone 0018 - TXID = 1651-1, area = M23, zone 18

/ = start of new segment

FT01220019 - FT from panel number 01, module number 22, zone 0019 - TXID = 1651-1, area = M22, zone 19

/ = start of new segment

FT01330020 - FT from panel number 01, module number 33, zone 0020 - TXID = 1651-1, area = M33, zone 20

/ = start of new segment

FT01440021 - FT from panel number 01, module number 44, zone 0021 - TXID = 1651-1, area = M44, zone 21

/ = start of new segment

FT01550022 - FT from panel number 01, module number 55, zone 0022 - TXID = 1651-1, area = M55, zone 22

/ = start of new segment

FA02660024 -  FA from panel number 02, module number 66, zone 0024 - TXID = 1651-2, area = M66, zone 24

] = segment end

When we create the signal, we take the transmitter ID, add a "-", and then add the panel number. If we also got an area, we create the area as the module, add a "-", and then the area. If we did not get an area, we create the area as "M" and then add the module.

We discussed creating an option at the driver or FEP level, that would stop putting the panel number with the transmitter ID and stop putting the module in the area. It would basically treat that whole signal like it was coming from one transmitter ID/account. If the panel is set up that way, then this would work. The problem is that it would be an all-or-nothing flag. All signals of this type would be treated this way and perhaps not all panels would be set up this way.

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.