MSA MultiGard 5000 - Factory Configured Parameters

4.0 Guidelines For Accessing Data Table Addresses
Remember the following key items about the MultiGard 5000 System when using these tables to
decide what is applicable:
 All Modbus data is read-only (holding register, 4X, or read input, 1X) except for
the acknowledge items listed in Table 6 (force single coil, 0X).
 Model: 8 point, 16 point, dual 8 point, 24 point, 32 point, or dual 16 point
 Single or Dual: Single sequencer MultiGard 5000 Systems can have 4 sensors (#1
- #4) installed. Dual sequencer MultiGard 5000 Systems can have 2 sensors (#1,
#2) on Sequencer A and 2 sensors (#3, #4) on Sequencer B. Note that in the
following tables reference to Single Sequencer is identical to Dual Sequencer A.
In the tables this is represented as “Sequencer (A)”.
 Options: The User Configured Outputs (UCO) can be supplied as UCO #1 only
or both UCO #1 & UCO #2 together.
 Additional information necessary to properly decode the data is supplied under
each table if applicable.
 All analog data will automatically be in engineering units based on the MultiGard
5000 System factory configuration. No additional scaling is required.
 It may be desirable to read blocks of words out of the gateway instead of only the
specific addresses listed in the tables. This depends on the interfacing
requirements and the software capabilities of the third party product. If this is
done, be sure to only use the addresses listed in this document for presentation
purposes.
 CAUTION
Use only data table addresses defined in this manual. The use of
undefined addresses will produce an incorrect presentation. Data
table addresses not defined are reserved for MSA use only.
 Customers who use bi-directional communications with the controller must avoid
writing into addresses not referenced in this document.
 WARNING
Do not write into undefined addresses. Doing so may prevent the
system from detecting gas. Data table addresses not defined are
reserved for MSA use only.
Failure to follow this warning can result in serious personal
injury or death.
 The end user must verify all data transfers following the system integration effort.
 See Table 1 below, and its associated warning, for important information about