TTDMâNMM and - California Detection Systems

More documents

Recommendations

Info

TTDM-NMM Data Structure for Modbus Access The following paragraphs describe the data structure used by the TTDM-NMM to serve its purpose of leak detection and location. This information is provided to assist those configuring the Modbus master (host system) to communicate with the TTDM-NMM and provide effective monitoring of the leak detection system. These next paragraphs highlight areas important for leak detection, and are followed by a detailed technical reference. Note: The host application software may use either the register address or the hexadecimal address to construct the Modbus message frame; this manual shows the decimal address only for reference. System Status To obtain summary information for the entire NMM/SIM system (as described in “System Status” on page 17), use the Modbus 4 function to read the registers noted below. Input Address Address Name/description of 16-bit value Register (decimal) (hexadecimal) (4 hexadecimal characters) 30001 0 0000 Product ID (0–255) 30002 1 0001 UI Version — Major Version number/minor version number: MV =0–99/ mv = 0–99 30003 2 0002 UI Version letter (1 ASCII character) 30007 6 0006 SIM Network: Number of active nodes 30008 7 0007 Number of Leak Alarms 30009 8 0008 Number of Service Req’d Alarms 30010 9 0009 Number of Cable Breaks 30011 10 000A Number of Loop Imbalances 30012 11 000B Number of YB Breaks 30013 12 000C Number of RG Breaks 30014 13 000D Number of SI Comm Errors 30015 14 000E Number of SI H/W Errors Events Events are stored in a circular buffer containing multiple event records. The capacity of the list (maximum number of events: 256) is stored in Input Register 30018. The number of events that have been recorded is stored in Input Register 30017; this value can be used by the host system to determine if any events have occurred since the TTDM-NMM was last polled. Input Address Address Name/description of 16-bit value Register (decimal) (hexadecimal) (4 hexadecimal characters) 30017 16 0010 Number of events recorded (1–32767) 30018 17 0011 Capacity of event list (256) Note: If the number of events recorded exceeds the capacity of the list (register 30017 > register 30018) the events list is full. When this occurs, the list “wraps around”: when a new event occurs the TTDM-NMM overwrites the earliest event, and the list then stores the 256 most recent events. To allow a host system to access various event records without extensive register mapping, the TTDM-NMM incorporates a sevenregister overlay that holds a single event record. Holding Register 40001 determines the event number for which the overlay stores data. Holding Address Address Name/description of 16-bit value register (decimal) (hex) (4 hexadecimal characters) 40001 0 0000 Number of event record stored in Input Register overlay 36
To access an event record using the overlay: • Use Modbus function 06 to write the desired event number in Holding Register 40001. • Use Modbus function 04 to read the overlay registers, as tabulated below. Input Address Address Name/description of 16-bit value Register (decimal) (hexadecimal) (4 hexadecimal characters) 30021 20 0014 Event Type (numeric code; see table below) 30022 21 0015 SIM Module Address (channel number) 30023 22 0016 Module Subaddress (not used) 30024 23 0017 Event Time Stamp (high byte: hours; low byte: minutes) 30025 24 0018 Event Date Stamp (high byte: month; low byte: day) 30026 25 0019 Event Date Stamp (low byte-year) 30027 26 001A Event Data (i.e., location) Note: Event Data (leak location, in Input Register 30027) uses the unit of measure selected for the system, as defined in Holding Register 40007. The TTDM-NMM communicates the event type (Input Register 30021) with a numeric code, as defined in the table below (See “Appendix 2 - Events Glossary” for further detail). Code Event type 001 Leak 002 New Leak 003 Re-Alarm 004 Service Req’d 005 Cable Break 006 YB Loop Break 007 RG Loop Break 008 Loop Imbalance 009 SI H/W Error 010 SI Comm Error 011 System Restart 012 System Power Down 013 Leak relay Reset 015 Leak Cleared 016 Service Cleared 017 Cable Restored 018 SI H/W Recovered 019 SI Comm Recovered 020 SIM Normal 021 System Normal 022 Memory Cleared 023 RTC/RAM Error 024 Re-Alarm 8 Hours 025 Re-Alarm 12 Hours 026 Re-Alarm 24 Hours 027 Alarm Silenced Hint: An event record can also be accessed with a single read function. Page 43 in the “Modbus Technical Reference” section provides a register map so the host system can be programmed to access events records directly. 37
Page 1 and 2: R TraceTek TTDM-NMM and TTDM-SIM Le
Page 3: Contents Overview Identifying TTDM-
Page 6 and 7: Description of TraceTek Leak Detect
Page 8 and 9: Connection of TraceTek TTDM-NMM Sys
Page 10 and 11: Current Event/Status Display (Norma
Page 12 and 13: Leak Detection and Location Events
Page 14 and 15: Fault Events Introduction Several c
Page 16 and 17: Should the leak continue to spread,
Page 18 and 19: Status of Individual SIM Channels T
Page 20 and 21: Events History Log One extremely us
Page 22 and 23: General Setup Access the General Se
Page 24 and 25: SIM Network Access the SIM Network
Page 26 and 27: Self-Test The Self-Test menu provid
Page 28 and 29: Appendix 2 - Events Glossary Type o
Page 30 and 31: Appendix 4 - Maintenance Cleaning t
Page 32 and 33: Assigning a SIM Address When a TTDM
Page 34 and 35: 4-20 mA Output Signals The TTDM-NMM
Page 36 and 37: Configuration and Testing of Serial
Page 38 and 39: Selecting RS-485 vs. RS-232 Communi
Page 42 and 43: SIM Channel Status The TTDM-NMM off
Page 44 and 45: Digital Inputs — Alarm Relay/LED
Page 46 and 47: Input Registers — SIM Status Data
Page 48 and 49: Holding Registers — Module Setup
Page 50 and 51: R R Appendix 8 - TTDM-NMM Network M
Page 52: www.raychem.com cheminfo@raychem.co

TTDMâNMM and - California Detection Systems

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

TTDMâNMM and - California Detection Systems