TycoCCU3-MXMB 420

Rev: 4.
20 17 September 2012
CCU3/C-MXMB
Installation and Configuration Manual

Rev: 4.20 17 September 2012
TABLE OF CONTENTS
1. GENERAL..............................................................................................................................................5
1.1. INTRODUCTION ..................................................................................................................................5
1.2. ORDERING CONFIGURATIONS:............................................................................................................6
1.3. SYSTEM REQUIREMENTS FOR CCU3/C-MXMB PROGRAMMER ........................................................7
2. INSTALLATION...................................................................................................................................8
2.1. PARTS SUPPLIED ................................................................................................................................8
2.2. YOU WILL NEED .................................................................................................................................8
2.3. POWER REQUIREMENTS .....................................................................................................................8
2.4. BOARD LAYOUT ................................................................................................................................8
2.5. CONNECTING THE CCU3/C-MXMB ..................................................................................................9
2.6. MX NETWORK CONFIGURATION......................................................................................................11
2.6.1. CCU3/C-MXMB to TLI800 / TLI800EN Connection ..............................................................11
2.6.2. TLI800 Configuration..............................................................................................................12
2.6.3. TLI800EN Configuration.........................................................................................................13
2.6.4. TLI800 and TLI800EN Consys Setup ......................................................................................16
2.7. SINGLE PANEL CONFIGURATION ......................................................................................................18
2.7.1. Connecting the CCU3/C-MXMB to FIM COM3 .....................................................................18
2.7.2. Consys Setup for COM3 of the MX FIM..................................................................................18
2.8. SERIAL PORT MODBUS CONNECTIONS ..........................................................................................19
2.9. PROFIBUS CONNECTION ...............................................................................................................20
2.10. HOST PC CONNECTION ..................................................................................................................21
2.11. CCU3/C-MXMB POWER CONNECTION ........................................................................................22
2.12. NORMAL AND FAULT CONDITION INDICATORS ..............................................................................23
2.12.1. Operation of LEDs.................................................................................................................23
2.12.2. Supervision Relay ..................................................................................................................23
2.12.3. CCU3/PB PROFIBUS Card LEDs ........................................................................................23
3. MXMB OPERATION.........................................................................................................................24
3.1. MODBUS TCP ...............................................................................................................................24
3.2. PROFIBUS AND PROFISAFE........................................................................................................24
3.3. AUTRONICA MODE. .....................................................................................................................25
3.4. MIPLOC MODE. .............................................................................................................................25
3.5. MX DOOR / DAMPERS.....................................................................................................................25
3.6. MODBUS MAP OPTIONS ................................................................................................................26
4. STANDARD MODE MODBUS MAP ...............................................................................................27
4.1. MAP OVERVIEW...............................................................................................................................27
4.2. MODBUS MAP REGISTER AND BIT DETAILS ..................................................................................28
4.2.1. Submap Registers ....................................................................................................................28
4.2.2. CCUioNET Register Block ......................................................................................................28
4.2.3. MXNet Address Map Register Block........................................................................................29
4.2.4. MXNet Sector Status Map Register Block ...............................................................................29
4.2.5. Time and Date Registers..........................................................................................................30
4.2.6. MXMB Global Register Block .................................................................................................30
4.2.7. MX Panel Register Blocks – Example Panel Number 1, 2…...................................................31
4.2.8. Panel Status Registers .............................................................................................................31
4.2.9. Command Acknowledge Register (CAR) .................................................................................32
4.2.10. Loop Information...................................................................................................................33
4.2.11. Zone Status Information ........................................................................................................33
4.2.12. Point Status Information........................................................................................................34
4.2.13. Point Isolate / De-isolate Reply Registers .............................................................................34
4.2.14. Point Information Reply Registers.........................................................................................35
4.2.15. Panel Control Register ..........................................................................................................37
4.2.16. Point Isolate / De-isolate Request Registers..........................................................................38
4.2.17. Point Information Request Registers .....................................................................................38
5. CCU2 COMPATIBILITY MODE MAP ...........................................................................................40
5.1. MAP OVERVIEW...............................................................................................................................40
 Copyright base2, 2012 2 of 93
All Rights Reserved
5.2. MODBUS MAP REGISTER AND BIT DETAILS ..................................................................................41

5.2.1. Submap Registers ....................................................................................................................41
5.2.2. CCUioNET Register Block ......................................................................................................41
5.2.3. MXMB Global Register Block .................................................................................................41
5.2.4. MXNet Address Map Register Block........................................................................................42
5.2.5. MXNet Sector Status Map Register Block ...............................................................................42
5.2.6. Time and Date Registers..........................................................................................................43
5.2.7. MX Panel Register Blocks – Example Panel Number 1, 2…...................................................43
5.2.8. Command Acknowledge Register (CAR) .................................................................................44
5.2.9. Panel Status Registers .............................................................................................................44
5.2.10. Panel Control Register ..........................................................................................................45
5.2.11. Loop Information...................................................................................................................45
5.2.12. Zone Status Information ........................................................................................................46
5.2.13. Point Status Information........................................................................................................46
5.2.14. Point Information Request Registers .....................................................................................46
5.2.15. Point Information Reply Registers.........................................................................................47
5.2.16. Point Isolate / De-isolate Area ..............................................................................................49
6. MIPLOC MODE. ................................................................................................................................52
6.1. RESERVED REGISTERS .....................................................................................................................52
6.2. MIPLOC STATUS WORD .................................................................................................................52
6.3. WATCHDOG HEARTBEAT .................................................................................................................52
6.4. NEW EVENT BIT ..............................................................................................................................52
6.5. PLC STATUS WORD ........................................................................................................................53
6.6. COMMAND TRANSFER FROM PLC TO MX.......................................................................................53
6.7. UNIMPLEMENTED MIPLOC FEATURES ...........................................................................................54
6.8. FURTHER INFORMATION ..................................................................................................................54
7. CONFIGURING THE MODBUS MAP ............................................................................................55
7.1. INSTALLING THE CCU3-MXMB SETUP PROGRAM .........................................................................55
7.2. THE CCU3-MXMB SETUP PROGRAM .............................................................................................55
7.2.1. Opening, Saving and Restoring CCU3/C-MXMB Configurations ..........................................55
7.2.2. The MX Panel Setup Page .......................................................................................................56
7.2.3. The Sector Map Setup Page.....................................................................................................56
7.2.3.1. Adding and Removing Sector Mappings...........................................................................................57
7.2.4. The Expansion Cards Page .....................................................................................................58
7.2.4.1. Adding and Removing CCU/IO Nodes .............................................................................................58
7.2.4.2. Configuring CCU3 IO Devices .........................................................................................................58
7.2.4.3. Configuring CCU3/E.........................................................................................................................58
7.2.5. The Submap Setup Page ..........................................................................................................59
7.2.6. The PTP Interface Setup Page.................................................................................................60
7.2.7. The Modbus Interface Setup Page...........................................................................................61
7.2.8. The Other Options Setup Page ................................................................................................62
7.3. PROGRAMMING THE CCU3/C-MXMB ............................................................................................64
8. COMMUNICATION ..........................................................................................................................65
8.1. MODBUS COMMUNICATION PARAMETERS ....................................................................................65
8.2. MODBUS COMMANDS ...................................................................................................................65
8.2.1. Read Coil Status (01)...............................................................................................................66
8.2.2. Read Input Status (02) .............................................................................................................67
8.2.3. Read Input Registers (04) ........................................................................................................69
8.2.4. Force Multiple Coils (15) ........................................................................................................70
8.2.5. Preset Multiple Registers (16) .................................................................................................72
8.2.6. Error Responses.......................................................................................................................74
8.2.7. Calculating CRC16..................................................................................................................74
8.3. POINT INFORMATION REQUEST ........................................................................................................75
8.4. ISOLATE DE-ISOLATE REQUEST .......................................................................................................75
8.5. CCU TIMEKEEPING..........................................................................................................................75
9. EXAMPLE CCU3/C-MXMB SETUP ...............................................................................................77
9.1. ADD THE MX PANELS .....................................................................................................................78
9.2. ADD THE CCU/IO NODES................................................................................................................78
9.3. SET UP THE SUBMAP ........................................................................................................................78
9.3.1. Adding the MX Zone Alarms to the Submap............................................................................78

All Rights Reserved
9.3.2. Adding the Blank Addresses to the Submap.............................................................................80

9.3.3. Adding the CCU/IO Active Bits to the Submap .......................................................................81
9.4. SETUP THE PTP INTERFACE .............................................................................................................82
9.5. SETUP THE MODBUS INTERFACE ...................................................................................................82
9.6. SETUP THE OTHER OPTIONS.............................................................................................................82
9.7. SAVE THE PROJECT AND PROGRAM THE CCU3/C-MXMB ..............................................................83
9.7.1. Saving ......................................................................................................................................83
9.7.2. Programming...........................................................................................................................83
10. TESTING THE CONFIGURATION...............................................................................................84
APPENDIX A CCU3 SERIAL PORTS .................................................................................................89

RS232 OPERATION .................................................................................................................................89
RS485 OPERATION .................................................................................................................................89
RS422 OPERATION .................................................................................................................................89
APPENDIX B MX SPEAK 1 POINT INFORMATION REQUEST/REPLY...................................91

All Rights Reserved
1. General
1.1. Introduction
The CCU3/C-MXMB provides a third party interface to a number of MX panels on an MXNet.
The CCU3/C-MXMB connects to the MXNet via a TLI-800 (TPI) interface card using RS232. For a single MX
panel installation, the CCU3/C-MXMB can be connected directly to COM3 of the MX panel FIM (Field Interface
Module) board and the TLI-800 card not used.
Two serial MODBUS interfaces are available on the CCU3/C-MXMB. They can be configured for RS232, RS485
or RS422 operation.
Expansion cards can be added to the CCU3/C-MXMB to provide extra functionality.
• CCU3/E - Supports MODBUS TCP. Up to 4 simultaneous TCP connections are supported.
• CCU3/PB – Supports PROFIBUS and PROFISAFE. In PROFIBUS mode the first 76 bytes (608 bits) of
the submap data is mapped as cyclic input data. The first word of the cyclic output data is mapped as a
command register. Transitions from 0 to 1 in this register trigger global commands broadcast to all the
panels in the network. In PROFISAFE mode the first 71 bytes (568 bits) of submap data is mapped as
F-Input data. The first word of the F-Output data is mapped as a command register. Transitions from 0
to 1 in this register trigger global commands broadcast to all the panels in the network.
• CCU3/IO – Provides general-purpose I/O devices. The CCU3/IO has 4 relays that are controlled via
WRITE commands to the MODBUS map. The relay contacts can be used as inputs to an MX panel or
external equipment. There are also 10 supervised inputs whose status can be read from the MODBUS
map.
The MODBUS map of the CCU3/C-MXMB is configured using the CCU3/C-MXMB Programmer. There are 2
types of MODBUS map available.
• Global Map – The bits for every MX loop point and zone are present in the map at a fixed location.
• Submap – A custom map of bits can be configured by the user to reference addresses in the Global
Map. This allows the user to build a custom map consisting only of the data they require. The submap is
also used as the active map for AUTRONICA, PROFIBUS and PROFISAFE operation. The number of
bits in the submap is constant however the number that can be transferred varies depending on the
protocol.
Protocol Effective Submap Size

Serial MODBUS 5120 bits
MODBUS TCP 5120 bits
AUTRONICA 5120 words
PROFIBUS 608 bits
PROFISAFE 568 bits

All Rights Reserved
1.2. Ordering Configurations:

Part Number: CCU3/C-MXMB. Base version with 2 serial MODBUS interfaces. Each can be independently
configured for RS232, RS485 or RS422 operation.
Figure 1:CCU3/C-MXMB
Part Number: CCU3/E-MXMB. This configuration has a CCU3/E expansion card fitted to provide an Ethernet
connection for MODBUS TCP.
Figure 2:CCU3/E-MXMB
Part Number: CCU3/C232PB-MXPB. This configuration has a CCU3/PB expansion card fitted to support
PROFIBUS and PROFISAFE.

All Rights Reserved
1.3. System Requirements for CCU3/C-MXMB Programmer

The minimum requirements for the computer system are:
• 100 Mb of disk space for installation.
• 256MB Ram
• SVGA Monitor
• Windows® 95, 98, 2000, XP, NT or Windows® 7 operating system
• Microsoft® Windows compatible pointing device (such as a mouse)
• A communications port for reprogramming the CCU3/C-MXMB.

All Rights Reserved
2. Installation
2.1. Parts Supplied

1 x CCU3/C board with firmware for MXMB
1 x CCU3/E plug in board if CCU3/E-MXMB is ordered
1 x CCU3/PB plug in board if CCU3/C232PB-MXPB is ordered
4 x 6G x 1/4inch Self-tapping screws for the installation mounting
1 x 5.08 x 3 way Power connector for CCU3/C
2 x 3.5 x 3 way connector for CCU3/C
2 x 3.5 x 6 way connector
1 x Interface cable TLI-800 from TLI-800 card to CCU3/C (CCU3-TLI800)
1 x CCU3 Programming cable (CCU3/PROG)
1 x CD with MXMB software and manual
2.2. You will need

1 x 24V DC plug pack or Power Source
1 x Interface cable for MODBUS communication
2.3. Power Requirements

Typical: 200mA at 24VDC Voltage Input: 11.5V-16 VDC or 18V to 30V
2.4. Board Layout

There are 4 DIP switches next to the relay port. They should all be in the UP position.

All Rights Reserved
2.5. Connecting the CCU3/C-MXMB

COM1 connects to the MX panels, either directly or using a TLI800 network card.
COM2 connects to a PC for reprogramming and debugging.
COM3 and COM4 connect to the MODBUS system.
MODBUS
Master MX Net with TLI-800
Com 3
TLI-800
Com 4 Com 1
CCU3/C-MXMB
Com 2 Configuration and

Reprogramming PC
For a networked MX installation COM1 on the CCU3/C-MXMB connects using an additional TLI-800 network
card. This card should be installed in the same enclosure as the CCU3/C-MXMB.
Earth 0V 24V
TLI-800 Card
PC
Modbus
Figure 3: Multiple Panel Configuration

All Rights Reserved
For a single MX panel installation, the CCU3/C-MXMB can be connected to COM3 of the MX panel FIM (Field
Interface Module) board. A TLI-800 card is not required.
Earth 0V 24V
Single MX Panel
FIM Com3
PC
Modbus
Figure 4: Single Panel Configuration

All Rights Reserved
2.6. MX Network Configuration

Connection to both TLI800 and TLI800EN cards is supported.
2.6.1. CCU3/C-MXMB to TLI800 / TLI800EN Connection
Connect COM1 of the CCU3/C-MXMB to socket PL2 of the TLI800 or TLI800EN card using the
provided cable. (Order Code: CCU3-TLI800-B)
Figure 5: RJ12 Plug for Connection to TLI800 PL2
Pinout for TLI 800-B Cable Connection from the CCU3/C-MXMB to the TLI800
Network Interface Board on MX Panel
RJ12 Pin Number CCU3 Com 1 Pin Number
Orange 6pin (3.5 pitch) Weidmuller plug
6 NC
5 NC
4 NC
3 6
2 3
1 4
Table 1 CCU3-TLI800-B Cable
CCU3 6 Pin Port 1 Signal Common

RXD
6
CTS 2 Data IN
5
0V 3 Data OUT
4
TXD 4 RTS to TLI800
3
RTS 5 CTS from TLI800
2
SHIELD/GND 6 Not Used
1
Figure 6: CCU3-TLI800-B Cable

All Rights Reserved
2.6.2. TLI800 Configuration
The TLI-800 Interface module is configured using 2 sets of DIP switches SW1 and SW2.
SW1 Switch Application Assembly SW1 Switch Network SW1 Network

Position Position BAUD Rate Position Topology
1 2 3 4 5 6 7 8
ON ON ON TFXnet TLI-530 ON ON ON 1200 ON ON Bus
Gateway
ON ON OFF TFXnet Hub TLI-530 OFF ON ON 2400 ON OFF Star
ON OFF ON TFXnet Bridge TLI-530 ON OFF ON 9600 OFF ON Ring
ON OFF OFF Not Used N/A OFF OFF ON 19200 OFF OFF Redundant
Star
OFF ON ON TFX-to-XA TLX-530 ON ON OFF 38400
Normal
Operation
OFF ON OFF TFX-to-XA TLI-530 OFF ON OFF Reserved
Config. Program TLX-530
OFF OFF ON Reserved N/A ON OFF OFF Reserved
OFF OFF OFF Reserved N/A OFF OFF OFF Reserved
ON ON ON Third Party TLT-530
Interface
Table 2 Switch SW1 Functions
SW2 Value SW2 Function

Position 1-7 (OFF) Position 8
1 1 ON TFX TTL Port
2 2 OFF RS232
3 4
4 8
5 16
6 32
7 64
Table 3 Switch SW2 Functions
• Set SW1-1, 1-2 and 1-3 to “Gateway” for the MXMB.

• Set SW1-4, 1-5, 1-6, 1-7, 1-8 to the settings chosen for your network. A network baudrate
of 19200 is recommended for TLI800.
• Set SW2-1 to SW2-6 to the network address that the MXMB will be using. This address
must be configured in MX Consys as a non-panel node.
• Set SW2-8 to RS232 for the MXMB.

All Rights Reserved
2.6.3. TLI800EN Configuration
The TLI-800EN Interface module is configured using 3 sets of DIP switches SW1, SW2 and SW3.
Switch 1 position Application

1-1 1-2
OFF OFF Gateway/BMX
OFF ON BMI
ON OFF Bridge
ON ON Reserved
Table 4 TLI800EN - Application Setting
Switch 1 position Network Baud Rate

1-3 1-4 1-5
ON ON ON 9600
OFF ON ON 19200
ON OFF ON 38400
OFF OFF ON 57600
ON ON OFF 76800
OFF ON OFF 115200
ON OFF OFF Reserved
OFF OFF OFF Reserved
Table 5 TLI800EN – Network Baud Rate
Switch 1 position Network Topology

1-6
OFF Bus
ON Ring
Table 6 TLI800EN – Network Topology

All Rights Reserved
Switch 1 position Firmware upgrade of M MCU

1-8
ON Download mode after RESET
OFF Run
Table 7 TLI800EN – Master MCU Downloading Setup
Switch 2 position Host Interface

2-1
ON Bus RS485
OFF RS232
Table 8 TLI800EN – Host Interface Setup
Switch 2 position Emergency Display

2-2
ON Enabled
OFF Disabled
Table 9 TLI800EN – Emergency Display Setup
Switch 2 position Host Interface Baud Rate

2-3 2-4 2-5
ON ON ON 4800
OFF ON ON 9600
ON OFF ON 19200
OFF OFF ON 38400
ON ON OFF 57600
OFF ON OFF 76800
ON OFF OFF 115200
OFF OFF OFF Reserved
Table 10 TLI800EN – Host Interface Baud Rate

All Rights Reserved
Switch 2 position M MCU Watchdog

2-6
ON Enabled
OFF Disabled
Table 11 TLI800EN – M MCU Watchdog Setup
Switch 2 position E MCU Watchdog

2-7
ON Enabled
OFF Disabled
Table 12 TLI800EN – E MCU Watchdog Setup
Switch 2 position Firmware upgrade of E MCU

2-8
ON Download mode after RESET
OFF Run
Table 13 TLI800EN – Emergency MCU Downloading Setup
Switch 3 position Node

3-1 3-2 3-3 3-4 3-5 3-6 3-7 Address
3-1 = LSB Binary coded node
3-7 = MSB address
(OFF=0, ON=1)
Table 14 TLI800EN – Node Address
Switch 3 position Node Address or Test Option

3-8
ON Switch 3 is reserved for test option
OFF Switch 3 = node address
Table 15 TLI800EN – Node Address Setting
• Set SW1-1 and 1-2 to “Gateway/BMX” for the MXMB.

• Set SW1-3, 1-4, 1-5, 1-6 to the settings chosen for your network. A network baudrate of
115200 is recommended.
• Set SW1-8 to “Ru”n for the MXMB.
• Set SW2-1 to “RS232” and SW2-2 to “Enabled”.
• Set SW2-3, 2-2, 2-3 to the desired host interface baudrate.
• Set SW2-8 to “Run” for the MXMB.
• Set SW3-1 to SW3-7 to the network address that the MXMB will be using. This address
must be configured in MX Consys as a non-panel node.
• Set SW3-8 to “Use Address” for the MXMB.

All Rights Reserved
2.6.4. TLI800 and TLI800EN Consys Setup
In the “General | Network Overview” section select an unused network address and add a MZX
Node for the CCU3-MXMB. The network address DIP switches on the TLI800 card need to be set
to this value.
Figure 7: Consys Network Overview
In the “General | Log Settings” section set the MZX node for the CCU3-MXMB as a Log Client. Set
ALL event priorities to be logged to the Client. Select “Skip No Response Data” if you are using
the “No Response” pointmap feature of Consys.
Figure 8: Consys Log Settings

All Rights Reserved
If you are using either the “No Response” or the “Door/Damper” pointmaps feature of Consys then
enable the broadcast of the respective message. If “Fast No Response Data” is selected ensure
that “Skip No Response Data” has also been selected in the Log Settings for the project.
Figure 9: Consys MX Panel Network Options

All Rights Reserved
2.7. Single Panel Configuration
2.7.1. Connecting the CCU3/C-MXMB to FIM COM3

The cable to connect to COM3 of the MX FIM is shown below. Note that this cable is NOT the same as the cable
to connect to PL2 of a TLI800. This cable is not supplied with the CCU3/C-MXMB.
Pinout for Direct Connection from the CCU3/C-MXMB to FIM Board Com3 on MX
Panel
RJ12 Pin Number CCU3 Com 1 Pin Number
Orange 6pin (3.5 pitch) Weidmuller plug
6 NC
5 NC
4 NC
3 3
2 6
1 4
Table 16
2.7.2. Consys Setup for COM3 of the MX FIM

The Consys setup for the MX COM3 is the same as for the TLI800 connection. It is necessary to add a MZX
node for the CCU3/C-MXMB and to set it as a logging client.

All Rights Reserved
2.8. Serial Port MODBUS Connections

The CCU3/C-MXMB supports RS232, RS422 and RS485 MODBUS connections on its serial ports. The
interface type and the MODBUS address are set through the CCU3/C-MXMB Programmer.
Pinout for Cable Connection from the CCU3/C-MXMB to a MODBUS RS422

Network
RS422 Wiring CCU3 Com 4 Pin Number
NC 1
TX+ 2
TX- 3
NC 4
RX+ 5
RX- 6
Table 17 RS422
Pinout for Cable Connection from the CCU3/C-MXMB to a MODBUS RS232 Port
RS232 Wiring (DTE) CCU3 Com 4 Pin Number
Shield 1
RTS 2
TX 3
0V 4
CTS 5
RX 6
Table 18 RS232
Pinout for Cable Connection from the CCU3/C-MXMB to a MODBUS RS485 Port
RS485 Wiring CCU3 Com 4 Pin Number
NC 1
+ 2
- 3
0V 4
NC 5
NC 6
Table 19 RS485

All Rights Reserved
2.9. PROFIBUS Connection

The CCU3 PROFIBUS Interface is implemented using a module that provides the correct levels
for PROFIBUS. The interface includes the following features.
• Galvanic isolation of the bus electronics

• Automatic baud rate detection
• Set slave address support
# Item
1 Mode Indication LED
2 Status Indication LED
3 PROFIBUS Connector
Table 20 PROFIBUS Module Front View
Pin Signal Description

1 - -
2 - -
3 B Line Positive RxD/TxD, RS485 level
4 RTS Request to send
5 GND Bus Ground (Isolated)
6 +5V Bus Output +5V Termination power (Isolated)
7 - -
8 A Line Negative RxD/TxD, RS485 level
9 - -
Housing Cable Shield Internally connected to the module
protective earth via cable shield filters
according to the PROFIBUS standard.
Table 21 PROFIBUS Connector (DB9F)
Two LEDs built in to the module provide information on the state of the PROFIBUS module.
State Indication
Off Not online / No power
Green Online, data exchange
Flashing Green Online, clear
Flashing Red (1 flash) Parametrization error
Flashing Red (2 flashes) PROFIBUS Configuration error
Table 22 Operation Indication (LED1)
State Indication
Off Not online / No power
Green Online, data exchange
Flashing Green Online, Clear
Red Parametrization error
Table 23 Status Indication (LED2)

All Rights Reserved
2.10. Host PC Connection

A cable is provided to connect COM2 of the CCU3/C-MXMB to a PC COM Port for configuration,
reprogramming and diagnostics.
Pinout for Cable Connection from the CCU3/C-MXMB to the PC COM Port
PC COM Port DB9 Pin Number CCU3 Com 2 Pin Number
NC 1
6 2
2 3
5 4
4 5
3 6
Table 24 CCU3/PROG Cable
Figure 10: Pinout for Cable Connection between CCU3/C-MXMB and PC COM Port.

All Rights Reserved
2.11. CCU3/C-MXMB Power Connection

Connect the 24V DC power source to the supplied connector. The pin connections are written on the top of the
unit.
Pin number Function

V+ 24V
V- COM
Earth
Table 25 Power Connections
For correct installation and protection of the CCU3/C device the CCU3 must
be mounted on an earthed metal plate. This is important for correctly
dissipating any static discharge on the communication lines (as caused by an
electrical storm) and thereby preventing damage to this unit.

All Rights Reserved
2.12. Normal and Fault Condition Indicators
2.12.1. Operation of LEDs

Each serial port has a Green and a Yellow LED. The green led flashes when data is transmitted on the port.
The yellow LED glows when there has been supervision failure on the port or it is unable to make a
connection. If a port has been disabled in the software then neither LED will indicate.
Com 1 (Connection to MXNet):

• Green LED flashes to indicate Data Transmission.
• Yellow LED indicates Supervision failure.
Com 2 (Host PC connection):

• Yellow LED is not used.
Com 3 (MODBUS connection):

Com 4 (MODBUS connection):

2.12.2. Supervision Relay

The supervision relay on the CCU3/C-MXMB main board is used to indicate a problem with a configured
interface. This can optionally be connected to an input on the MX for annunciation of the interface fault.
If a PROFIBUS/PROFISAFE interface has been configured then the relay will energise when the PROFIBUS
connection is not online and exchanging data.
If no PROFIBUS/PROFISAFE interface has been configured then the relay will energise in the event of a
supervision failure of a MODBUS interface.
2.12.3. CCU3/PB PROFIBUS Card LEDs

Two LEDs provide information on the state of the PROFIBUS interface.
• Green LED flashing - The interface is configured but not yet connected.
• Green LED on - The connection is online and in the data exchange state
• Yellow LED flashing – The CCU3/C-MXMB is halted due to a PROFISAFE error condition.
• Yellow LED on – The PROFIBUS module is not responding to the CCU3.

All Rights Reserved
3. MXMB Operation
The CCU3/C-MXMB provides a third party interface to a number of MX panels on an MXNet.
The currently supported protocols are serial MODBUS, MODBUS TCP, PROFIBUS and PROFISAFE.
Serial MODBUS is always available on the CCU3/C-MXMB. The other protocols are automatically enabled when
the appropriate expansion card is configured. Addition of a CCU3/E enables MODBUS TCP; addition of a
CCU3/PB enables PROFIBUS and PROFISAFE.
3.1. MODBUS TCP

Addition of a CCU3/E expansion card enables MODBUS TCP. You will need to configure the IP Address, Subnet
Mask, and Gateway for the Ethernet interface.
There is also an option to change the word order in the MODBUS TCP packets.
The CCU3/E card also supports timekeeping. The CCU3/E-MXMB is able to update its time from a network
SNTP Server. If it has been set as a timekeeper this time will be broadcast to the MX Network.
3.2. PROFIBUS and PROFISAFE

Addition of a CCU3/PB expansion card enables PROFIBUS or PROFISAFE operation.
All PROFIBUS/PROFISAFE data is mapped through the submap. While the other areas of the memory map are
still present in the MXMB, they are not accessible to the PROFIBUS/PROFISAFE protocols. The required
PROFIBUS/PROFISAFE map must be manually configured into the submap. The size of the data that can be
mapped is limited by the protocol selected. The Standard memory map should be selected in the MXMB.
In PROFIBUS mode the submap data is mapped as cyclic input data. The data is limited to 76 bytes (608 bits).
The first word of the cyclic output data is mapped as a command register. Transitions from 0 to 1 in this register
trigger global commands broadcast to all the panels in the network.
Bit Number Command

0 Silence Buzzer
1 Silence Panel
2 Panel Resound
3 Day Mode
4 Night Mode
5 Function 1
6 Function 2
7 Reset
Table 26 PROFIBUS and PROFISAFE Command Bits
In PROFISAFE mode the submap data is mapped as F-Input data. The data is limited to 71 bytes (568 bits). The
first word of the F-Output data is mapped as a command register. Transitions from 0 to 1 in this register trigger
global commands broadcast to all the panels in the network. The bit definitions are the same as PROFIBUS.

All Rights Reserved
3.3. AUTRONICA Mode.

In this mode the operation of the CCU3 changes to a mode compatible with AUTRONICA panels. The submap
is organised as 5120 registers. Each register stores an integer value representing the current device state of one
point.
Value Device State

1 Normal
3 Alarm/Fire
5 Pre Alarm
7 Trouble
8 Isolate
Table 27 AUTRONICA Device States
The global map is not accessible in this mode.
3.4. MIPLOC Mode.

In this mode the CCU emulates a Minerva MIPLOC interface. This allows a Minerva / MIPLOC site to be
upgraded to MX / CCU3 without requiring reprogramming of the PLC. In MIPLOC mode the CCU operates as a
MODBUS master updating the registers in the PLC using the defined submap. Use of the submap allows any
differences between the MX and Minerva loops to be catered for. The MIPLOC had some reserved registers for
doing panel commands, MIPLOC status, panel time/date, etc. These are carried across in the CCU submap,
though only some are implemented. The reserved registers cannot be removed from the submap. See the
MIPLOC chapter of this document for more information.
3.5. MX Door / Dampers.

If the MX panel has been programmed in Consys to broadcast its Door/Damper status then the Alarm bit for a
loop point will be set when the Door/Damper is activated. The MX panel Door/Damper status will not be used to
set the panel and global common register Alarm bit.

All Rights Reserved
3.6. MODBUS Map Options

The MODBUS map consists of two sections. The global map is a fixed map containing a block of registers for
each MX panel configured in the system. The configurable submap mirrors bits from the global map. This allows
the user to define a map containing only the bits required by the MODBUS master. This will improve the
response of the system and may also simplify the programming of the MODBUS master.
The MXMB Map Type options change the structure and functioning of the global map and the submap.
• Standard Mode – Operates as a standard CCU3/C-MXMB. The submap is a simple collection of bits
mapped from the fixed map. Each bit in the submap represents the state of one device event. For
example, bit 10 is the alarm state of a point 01-A005. The CCU operates as a MODBUS slave.
• CCU2 Compatibility Mode – In this mode the CCU3/C-MXMB has the same submap and global map
format as the CCU2/C-MXMB, allowing the CCU3 to be a drop-in replacement for a CCU2. When
swapping from “Standard mode” to this option, the program automatically recalculates all of the memory
map positions and bit numbers for the global map and submap, without clearing the submap. The CCU
operates as a MODBUS slave.
• AUTRONICA Mode – Changes the submap to a mode compatible with AUTRONICA panels. The
submap is organised as one word register for each point, each register stores an integer value
representing the current device state. The global map is not accessible in this mode. The CCU operates
as a MODBUS slave.
• MIPLOC Mode – In MIPLOC mode the CCU operates as a MODBUS master updating the registers in
the PLC using the defined submap. The MIPLOC reserved registers are carried across in the CCU
submap, though only some are implemented. These reserved registers cannot be removed from the
submap.
If PROFIBUS or PROFISAFE operation is selected then the Standard map should be used.

All Rights Reserved
4. Standard Mode MODBUS Map
4.1. Map Overview

The fixed map contains a block of 1024 registers (16384 bits) for each MX panel configured in the system. The
CCU3/C-MXMB is limited to 32 panels.
The submap contains 320 registers (5120 bits). The submap is configurable. Each bit in the submap can mirror
any bit in the global map.
The MODBUS functions Read Coil Status (1), Read Input Status (2) and Force Multiple Coils (15) address the
memory as individual bits. The maximum address is 65535 so the master can only directly address the map for
2 MX panels. The submap can be used to work around this restriction.
The MODBUS functions Read Input Registers (4) and Set Multiple Registers (16) address the memory as word
registers so the master will be able to directly address the map for all 32 panels.
CCUioNET devices (CCU/I or CCU/IOs) can be connected to the CCU3/C-MXMB to provide supervised inputs
and relay outputs.
Register Number Bit Number Registers Usage

0 – 319 0 – 5120 Submap
375 – 412 6000 – 6607 CCUioNET
420 – 427 6720 – 6847 MXNet Map
428 – 488 6848 – 7823 Sector Map
489 – 491 7824 – 7871 Time and Date
500 – 511 8000 – 8191 MXMB Global
512 – 1229 8192 – 24575 MX Panel 1
1536 – 2559 24576 – 40959 MX Panel 2
2560 – 3583 40960 – 57343 MX Panel 3
3584 – 4607 57344 – 73727 MX Panel 4
4608 – 5631 73728 – 90111 MX Panel 5
5632 – 6655 90112 – 106495 MX Panel 6
6656 – 7679 106496 – 122879 MX Panel 7
7680 – 8703 122880 – 139263 MX Panel 8
8704 – 9727 139264 – 155647 MX Panel 9
9728 – 10751 155648 – 172031 MX Panel 10
10752 – 11775 172032 - 188415 MX Panel 11
11776 – 12799 188416 - 204799 MX Panel 12
12800 – 13823 204800 - 221183 MX Panel 13
13824 – 14847 221134 - 237567 MX Panel 14
14848 – 15871 237568 - 253951 MX Panel 15
15872 – 16895 253952 - 270335 MX Panel 16
16896 – 17919 270336 - 286719 MX Panel 17
17920 – 18943 286720 - 303103 MX Panel 18
18944 – 19967 303104 - 319487 MX Panel 19
19968 – 20991 319488 - 335871 MX Panel 20

All Rights Reserved
20992 – 22015 335872 - 352255 MX Panel 21

22016 – 23039 352256 - 368639 MX Panel 22
23040 – 24063 368640 - 385023 MX Panel 23
24064 – 25087 385024 - 401407 MX Panel 24
25088 – 26111 401408 - 417791 MX Panel 25
26112 – 27135 417792 - 434175 MX Panel 26
27136 – 28159 434176 - 450559 MX Panel 27
28160 – 29183 450560 - 466943 MX Panel 28
29184 – 30207 466944 - 483327 MX Panel 29
30208 – 31231 483328 - 499711 MX Panel 30
31232 – 32255 499712 - 516095 MX Panel 31
32256 - 33279 516096 - 532479 MX Panel 32
Table 28: MODBUS Map Registers
4.2. MODBUS Map Register and Bit Details
4.2.1. Submap Registers
Register Number Bit Number Bit Usage

0 - 319 0000 - 5119 Bits mirrored from the global maps
Table 29: Submap Registers
4.2.2. CCUioNET Register Block

375 - 376 6000 – 6031 CCUioNET Node offline
377 - 392 6032 – 6287 64 inputs with 4 state bits for each input
Bit 0 – active, Bit 1- supervision fault, Bit 2 –
reserved, Bit 3 – reserved
393 – 394 6288 – 6591 32 outputs (relay energise control bits)
Table 30: CCUioNET Registers

All Rights Reserved
4.2.3. MXNet Address Map Register Block

420 6720 - 6735 Valid MXNet address (MXNet Address 1 to 15)
422 6752 - 6767 Valid MXNet address (MXNet address 32 to 47)
427 6832 - 6847 Spare
Table 31: MXNet Address Map Registers
Reg Bit Bit Bit Bit Bit Bit Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
No 15 14 13 12 11 10
420 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 -
421 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
422 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
423 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
424 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
425 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
426 - - - - - - - - - - - - 99 98 97 96
Table 32: MXNet Node Register Bits
These are read-only registers. The MXMB is programmed with information about valid MXNet addresses. This
register block provides MXNet address information to the PLC.
If no panels are configured bit 0 of register 420 will be set to one.
4.2.4. MXNet Sector Status Map Register Block

428 - 488 6848 - 7808 Sectors 1 to 240 with 4 bits each
Bit 0 – Alarm, Bit 1 – Fault,
Bit 2 – Isolated, Bit 3 - Reserved
Table 33: Sectormap Registers
These are read-only registers. This map provides the PLC with indications of the total network sector alarm
status. If any device in any of the 240 available sectors is in the alarm, fault or isolated status a bit will be set in
this map.

All Rights Reserved
4.2.5. Time and Date Registers

Typically, one node of the MX network is set as the timekeeper. This node periodically broadcasts time and date
information via a special packet. The MXMB can also be set as a timekeeper.
Registers 489 and 490 contain the current time value. The time and date is stored as the number of seconds
after 00:00:00 01 Jan 1992. This is the same format used in the MX Time and Date Update packet. These are
read-write registers.
Bit15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit 0
timestamp byte 1 timestamp byte 0 (lsb)

Register 489
Bit15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit 0
timestamp byte 3 (msb) timestamp byte 2

Register 490
4.2.6. MXMB Global Register Block

These are read-only registers.
The watchdog bit toggles state every 20 seconds.

500 8000 - 8015 Bit 0 – Common Alarm
Bit 1 – Common Fault
Bit 2 – Common Isolate
Bit 8 – Watchdog bit
Bit 9 – PTP Trouble
Bit 10 – MODBUS0 Trouble
Bit 11 – MODBUS1 Trouble
501 8016 - 8031
504 8064 - 8079 Bit 0 – Common Fault
- v4.07 or later Bit 1 – Network Left Port Fault
Bit 2 – Network Right Port Fault
Bit 3 – Network Ground Fault
Bit 4 – Data Transfer Fault
Bit 5 – Ring Continuity Fault
Bit 6 – Network Communications Failure
Bit 7 – Set in addition to bit 4 to indicate fault is
caused by a gap in the broadcast sequence
numbers
508 8128 - 8143 Global Commands Register – These commands are
- v4.07 or later broadcast to all the panels in the network.
Bit 0 – Silence Buzzer
Bit 1 – Silence Panel
Bit 2 – Panel Resound
Bit 3 – Day Mode
Bit 4 – Night Mode
Bit 5 – Function 1
Bit 6 – Function 2
Bit 7 – Reset
Bit 8 – Fire Alarm/Evacuate
Table 34: MXMB Global Registers

All Rights Reserved
4.2.7. MX Panel Register Blocks – Example Panel Number 1, 2…

Panel MODBUS bits are spaced 16Kb apart.
Start Register Bit Number Bit Usage

Number
Panel 1
Example
512 8192 – 8223 Panel Status Registers
514 8224 – 8255 Command Acknowledge Register
516 8256 – 8415 Loop Information Registers
526 8416 – 9439 Zone Status Information
590 9440 – 19679 Detector Information Registers
1230 19680 – 19807 Isolate / Deisolate Reply Registers
1238 19808 – 20703 Point Information Reply Registers
1294 20704 – 20719 Panel Control Register
1295 20720 – 20815 Isolate / Deisolate Request Registers
1301 20816 - 24575 Point Information Request Registers
Start Register Bit Number Bit Usage
Number
Panel 2
Example
1536 24576 - 24607 Panel Status Registers
1538 24608 - 24639 Command Acknowledge Register
… … …
Table 35: MX Panel Register Allocation
4.2.8. Panel Status Registers

These two registers contain information relating to MX panel status. They are read-only registers.
Register Offset 0 Command

Bit 0 MX Common Alarm
Bit 1 MX Common Fault
Bit 2 MX Common Isolate
Bit 3 MX Panel Not Responding
Bit 4 MX Panel Resetting
Bit 5 MX Panel Evacuate Activated
Bit 6 Reserved
Bit 7 Reserved
Bit 8 Sounder Circuit 1 fault
Bit 10 Mains supply fault
Bit 11 Battery fault
Bit 12 Earth fault
Bit 13 Remote Bus fault
Bit 14 Signalling device fault
Bit 15 Charger fault
Table 36: Panel Status (Register 1)

The Panel Resetting bit is active for 20 seconds after the panel is reset.

All Rights Reserved
The second register contains information about system faults/isolations:
Register Offset 2 Meaning when set

Bit 0 Sounder circuit 1 isolated
Bit 2 Fire alarm contact isolated
Bit 3 Signalling device isolated
Bits 4 to 7 Reserved
Bit 8 Main PCB failure
Bit 9 Customer EPROM checksum error
4.2.9. Command Acknowledge Register (CAR)

This register contains control bits that are required so that the PLC can initiate point data requests and also
perform device isolations.

Bit 0 Point data request done
Bit 1-7 Global bits not used
Bit 8 Isolate request done
Bit 9 - 15 Reserved
Table 38: Command Acknowledge Register Bits
Communication between PLC, MX CCU and MX panel is as follows:-

1/ The PLC checks the CAR request done bit in the MX CCU and waits until it is cleared.
2/ The PLC sends its point data or isolate request to the registers of the MX CCU.
3/ The MX CCU checks if it is a valid request and then sends the request to the MX panel.
4/ The MX panel processes the request and replies to the MX CCU.
5/ The MX CCU stores the reply in the reply register, then sets the CAR request done bit.
6/ The PLC then reads the reply to its request.
7/ The PLC then sends a “Null” command to instruct the MX CCU to clear the command done bit.
8/ The MX CCU process the “Null” command and clears the command done bit.
The isolate/de-isolate reply packet confirms that the panel has carried out the request. PLCs can check the
isolate status by reading the appropriate isolate bit.
The reply to the point data request will contain all the relevant information required by the PLC for the
appropriate point.

All Rights Reserved
4.2.10. Loop Information

Stored in ascending order, each 16 bit register contains information about a particular loop in the system. The
format is as follows:
Register Offset Bit Number Bit Usage
4 64 – 79 Loop A Information
5 80 – 95 Loop B Information
6 96 – 111 Loop C Information
7 112 – 127 Loop D Information
8 128 – 143 Loop E Information
9 144 – 159 Loop F Information
10 160 – 175 Loop G Information
11 176 – 191 Loop H Information
12 192 – 207 Loop I Information
13 208 – 223 Loop J Information
Table 39: Loop Information Registers
Bit Meaning when set

Bit 0 Loop Shutdown
Bit 1 Loop Communication Fault
Bit 2 Loop High Current Consumption
Bit 3 Loop Open circuit
Bit 4 Loop Short Circuit
Bit 5 Loop card fault
Bits 6-15 Reserved
Table 40: Loop Information Register Contents
4.2.11. Zone Status Information

The zone status information registers provide an overview of the local MX panel detection zones. Each panel
can have up to 240 fire detection zones configured.

14 - 77 224 - 1247 Zones 0 to 240 with 4 bits each
Bit 2 – Isolated, Bit 3 – Prealarm
Table 41: Zone Status Information Register

All Rights Reserved
4.2.12. Point Status Information

Bit 2 refers to the isolation of the addressable device. If the device address has either an input or an output
isolated, or both, then this bit is set.
Register Offset Bit Number Bit Usage Address Range Applicability

78 – 141 1248 – 2271 Loop A, Points 0 to 254, Addresses >125 are applicable on
with 4 bits each 4 & 6 Loop Controllers only
Bit 2 – Isolated, Bit 3 –
Prealarm
142 – 205 2272 – 3295 Loop B, Points 0 to 254, Addresses >125 are applicable on
with 4 bits each 4 & 6 Loop Controllers only
206 – 269 3296 – 4319 Loop C, Points 0 to 254, Addresses > 125 are applicable on
with 4 bits each 4 Loop Controllers only
270 – 333 4320 – 5343 Loop D, Points 0 to 254, Addresses > 125 are applicable on
with 4 bits each 4 Loop Controllers only
334 – 397 5344 – 6367 Loop E, Points 0 to 254, Addresses > 125 are NOT
with 4 bits each applicable
398 – 461 6368 – 7391 Loop F, Points 0 to 254, Addresses > 125 are NOT
462 – 525 7392 – 8415 Loop G, Points 0 to 254, Addresses > 125 are NOT
526 – 589 8416 – 9439 Loop H, Points 0 to 254, Addresses > 125 are NOT
590 – 653 9440 – 10463 Loop J, Points 0 to 254,
with 4 bits each
654 – 717 10464 – Loop K, Points 0 to 254,
11483 with 4 bits each
Table 42: Detector Information Registers
4.2.13. Point Isolate / De-isolate Reply Registers

A point isolate/deisolate data area is located within each of the pre-designated panel global map areas. These
registers contain MX Speak Point Status Update Request (135) packets with the headers stripped off. A
MODBUS Write to the first address in this area will trigger the sending of the Point Status Update Request
packet on the MX network.
Register Offset Byte Usage Value Comment

718 10 Number of 0-65535 Number of Points that matched the
11 Matches Request
719 12 Number of 0-65535 How many Isolate/De-isolate CHANGES
13 Successes were effected (e.g. Isolating a Point
already Isolated is NOT a success)
720 14 Isolate/De- 0-5 0 = Isolate Both Input and Output
isolate Sub- 1 = Isolate Input
command 2 = Isolate Output
3 = De-isolate Both Input and Output
4 = De-isolate Input
5 = De-isolate Output
15 Target 0-8 0 = Any Point
Category 1 = Points with Input
2 = Points with Output
3 = Detectors
4 = Callpoints
5 = Sounders
6 = Plant Controls
7 = Extinguishing Controls
8 = Signalling Devices (Tele-
communications transmitters)

All Rights Reserved
721 16 Target Type 0-2 0 = Point

1 = Zone
2 = Sector
If Target Type
= Point
17 Channel 0-5
722 18 Channel 0-15
19 Point Category 0-6
723 20 Physical Point 0-255
Number
21 Logical Point 0-250 Logical Point Address (optional).
Number
724 22 Logical Point 0-240, 254
Zone
If Target Type
= Zone or
Sector
17 Area Number 0-240, 254
Table 43: Point Isolate / De-isolate Reply
4.2.14. Point Information Reply Registers

A point information data area is located within each of the pre-designated panel global map areas. These
registers contain MX Speak Point Information Request (148) packets with the headers stripped off. A MODBUS
Write to the first address in this area will trigger the sending of the Point Information Request packet on the MX
network.
The tables below list the data as it appears in this area for MX Speak V2,3,4 and 5. The message format is
slightly different to that for MX Speak 1 (Appendix B). Bytes 21 and 22 have been changed to reserved and byte
55 has been introduced for the device type.

726 10 Reply Status 0-1 0 = Success, i.e. Point(s) found,
1 = Fail – no Point(s) found that match
the criteria
11 Flags 0-31 Bit0 = Input Forced
Bit1 = Point Untested or Failed (Walk
Test)
Bit2 = Input Isolated
Bit3 = Output Isolated
Bit4 = Out of Compensation
Bit5 = Non-Loop Point (0 = Loop Point)
727 12 Node 1-99 Point Address
13 Channel 0-6
728 14 Channel 0-15
Address
Number
Number
730 18 Logical Point 0-240, 254
Zone
19 Device Type 0-254 As configured (See separate list of
Device Types)

All Rights Reserved
731 20 I/O Detail 0-3 0 = Nil

1 = Supports Input
2 = Supports Output
3 = Supports Both Input and Output
732 21 Group 1-65535 Group
22
733 23 Area Type 0-1 Area
24 Area Number 0-255
734 25 Sector ID 0-255 = 254 if Zone not in Sector
26 Loop Type 0-2 0 = Thorn
1 = MX Digital
2 = Not Loop (i.e. Local or Remote Digital
Points)
735 27 Raw Identity 0-255 Identity code/value returned by the
device
28 Actual Device 0-254 Device Type that corresponds to the Raw
Type Identity
736 29 Mode & 0-255 As configured
Sensitivity
30 Raw Analogue 0-255 Value 1 as provided by the device,
Value 1 without conversion
737 31 Raw Analogue 0-255 Value 2 as provided by the device,
738 33 LTA Flags 0-1 0 = Not available (some devices don’t
have it)
1 = LTA available
34 Raw LTA 0-255 LTA of main Raw Value
739 35 % Dirtiness 0-255
36 Unit of 0-9 0 = Invalid
Measure 1 1 = Degrees C
2 = Degrees F
3 = ppm (parts per million)
4 = %/ft Obscuration
5 = %/m Obscuration
6 = Y Value
7 = 1/10 Amp
8 = 1/10 V
9 = Not Installed
740 37 Unit of 0-9
Measure 2
38 Unit of 0-9
Measure 3
741 39 Converted 0-255 Value 1 in Units of Measure 1 (e.g. in
Value 1 %/m obscuration)
40 Converted 0-255 Value 2 in Units of Measure 2 (e.g. in °C)
Value 2
742 41 Converted 0-255 Value 3 in Units of Measure 3
Value 3
42 Instantaneous 0-1 Instant single reading from driver
Active State 0 = Normal
1 = Active
743 43 Instantaneous 0-254 (See separate list of Fault States)
Fault State
44 Confirmed 0-1 Confirmed by driver – true physical state
Active State of the Point
0 = Normal
1 = Active
744 45 Confirmed 0-254 (See separate list of Fault States)
Fault State

All Rights Reserved
46 Acknowledged 0-1 Acknowledged input state. (State

Active State actually used by MX – the Point is
assumed to be in this state. Typically is
the same as the Confirmed state, but it
may not be, e.g. when the input is
Forced.)
745 47 Acknowledged 0-254 (See separate list of Fault States)
Fault State
48 Output Forced 0-1 0 = Unforced
Mode 1 = Forced
746 49 Output 0-4 0 = OFF
Unforced 1 = ON
State 2 = Pulse 1 (pulsing in mode 1)
3 = Pulse 2 (pulsing in mode 2)
4 = Point with no Output
50 Output Forced 0-4 0 = OFF
State 1 = ON
747 51 Client ID 0-65535 Provided by the Server
52
Table 44: Point Information Reply
4.2.15. Panel Control Register

This register is used to pass commands to the individual MX panel. Please note these are individual panel
commands, not Global commands.
The commands available are as follows:

Bit 0 Silence Buzzer
Bit 1 Silence Panel
Bit 2 Panel resound
Bit 3 Day mode
Bit 4 Night mode
Bit 5 Function 1
Bit 6 Function 2
Bit 7 Reset
Bit 8 Fire Alarm/Evacuate
Table 45: Panel Control Register (register 782)

All Rights Reserved
4.2.16. Point Isolate / De-isolate Request Registers

3 = Detectors
4 = Callpoints
5 = Sounders
6 = Plant Controls
1 = Zone
2 = Sector
If Target Type
= Point
13 Channel 0-5
785 14 Channel 0-15
Number
Number
787 18 Logical Point 0-240, 254
Zone
If Target Type
= Zone or
Sector
Table 46: Point Isolate / De-isolate Request
4.2.17. Point Information Request Registers
Register Offset Byte Usage Value Comments

11 Channel 0-6
790 12 Channel 0-15
Address
Number
15 Logical Point 0-250
Number
792 16 Logical Point 0-240, 254
Zone

All Rights Reserved
17 Device 0-11 0 = All

Category 1 = Inputs
2 = Outputs
3 = Callpoints
4 = Detectors
5 = Smoke Detectors
6 = Heat Detectors
7 = Flame Detectors
8 = CO Detectors
9 = Digital Visual Outputs
10 = Detector or Callpoint
11 = Supervised Output
793 18 Group 1-65535 Interested in Points from this Group
19
794 20 Output Point 3 Always = 3 (= All Stores)
State Store
21 Reserved 0
795 22 Reserved 0
23 Multi-Area 0-1, 3 Multi-Area Bitmap Type
Type
796 24 Areas 000-007 0-255 Lsb = Area 0
25 Areas 008-015 0-255 Lsb = Area 8
. . . . .
. . . . .
55 Device Type 0-255 Device Type (e.g. Heat Detector)
attached to the Point
812 56 Request Type 0-1 0 = First Point only
1 = All Points, one by one
57 Search Type 0-10 0 = Points with Input Isolated
1 = Points with Output Isolated
2 = Points with Both Input and Output
Isolated
3 = Points with Either Input or Output
Isolated
4 = Points with Input Forced
5 = Points with Output Forced
Forced
Forced
8 = Points Untested
9 = Points out of Compensation
10 = All Points
Table 47: MX Speak 2, 3 and 4. Point Information Request

All Rights Reserved
5. CCU2 Compatibility Mode Map
5.1. Map Overview

The fixed map contains a block of 512 registers (8192 bits) for each MX panel configured in the system. The
CCU3/C-MXMB is limited to 32 panels.
The submap contains 320 registers (5120 bits). The submap is configurable. Each bit in the submap can mirror
any bit in the global map.
The MODBUS functions Read Coil Status (1), Read Input Status (2) and Force Multiple Coils (15) address the
memory as individual bits. The maximum address is 65535 so the master can only directly address the map for
6 MX panels. The submap can be used to work around this restriction.
The MODBUS functions Read Input Registers (4) and Set Multiple Registers (16) address the memory as word
registers so the master will be able to directly address the map for all 32 panels.
CCUioNET devices (CCU/I or CCU/IOs) can be connected to the CCU3/C-MXMB to provide supervised inputs
and relay outputs.
Register Number Bit Number Registers Usage

0 – 319 0 – 5120 Submap
375 – 417 6000 – 6687 CCUioNET
418 – 419 6688 – 6719 MXMB Global
420 – 427 6720 – 6847 MXNet Map
428 – 488 6848 – 7823 Sector Map
489 – 491 7824 – 7871 Time and Date
512 – 1023 8192 – 16383 MX Panel 1
1024 – 1535 16384 – 24575 MX Panel 2
1536 – 2047 24576 – 32767 MX Panel 3
2048 – 2559 32768 – 40959 MX Panel 4
2560 – 3071 40960 – 49151 MX Panel 5
3072 – 3583 49152 – 57343 MX Panel 6
3584 – 4095 57344 – 65535 MX Panel 7
4096 – 4607 65536 – 73727 MX Panel 8
4608 – 5119 73728 – 81919 MX Panel 9
5120 – 5631 81920 – 90111 MX Panel 10
5632 – 6143 90112 – 98303 MX Panel 11
6144 – 6655 98304 – 106495 MX Panel 12
6656 – 7167 106496 – 114687 MX Panel 13
7168 – 7679 114688 – 122879 MX Panel 14
7680 – 8191 122880 – 131071 MX Panel 15
8192 – 8703 131072 – 139263 MX Panel 16
8704 – 9215 139264 – 147455 MX Panel 17
9216 – 9727 147456 – 155647 MX Panel 18
9728 – 10239 155648 – 163839 MX Panel 19
10240 – 10751 163840 – 172031 MX Panel 20

All Rights Reserved
10752 – 11263 172032 – 180223 MX Panel 21

11264 – 11775 180224 – 188415 MX Panel 22
11776 – 12287 188416 – 196607 MX Panel 23
12288 – 12799 196608 –2047991 MX Panel 24
12800 – 13311 204800 – 212991 MX Panel 25
13312 – 13823 212992 – 221183 MX Panel 26
13824 – 14335 221184 – 229375 MX Panel 27
14336 – 14847 229376 – 237567 MX Panel 28
14848 – 15359 237568 – 245759 MX Panel 29
15360 – 15871 245760 – 253951 MX Panel 30
15872 – 16383 253952 – 262143 MX Panel 31
16384 – 16895 262144 – 270335 MX Panel 32
Table 48: MODBUS Map Registers
5.2. MODBUS Map Register and Bit Details
5.2.1. Submap Registers

0 - 319 0000 - 5119 Bits mirrored from the global maps
Table 49: Submap Registers
5.2.2. CCUioNET Register Block

375 6000 - 6015 CCUioNET Node offline
376 – 407 6016 - 6527 128 inputs with 4 state bits for each input
Bit 0 – active, Bit 1- supervision fault, Bit 2 –
reserved, Bit 3 – reserved
408 – 412 6528 - 6591 64 outputs (relay energise control bits)
Table 50: CCUioNET Registers
5.2.3. MXMB Global Register Block

418 6688 - 6703 Bit 0 – Watchdog bit
419 6704 – 6719 Reserved
Table 51: MXMB Global Registers
These are read-only registers.

The watchdog bit toggles state every 20 seconds.

All Rights Reserved
5.2.4. MXNet Address Map Register Block

427 6832 - 6847 Spare
Table 52: MXNet Address Map Registers
Reg Bit Bit Bit Bit Bit Bit Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
No 15 14 13 12 11 10
420 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 -
421 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
422 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
423 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
424 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
425 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
426 - - - - - - - - - - - - 99 98 97 96
Table 53: MXNet Node Register Bits
These are read-only registers. The MXMB is programmed with information about valid MXNet addresses. This
register block provides MXNet address information to the PLC.
If no panels are configured bit 0 of register 420 will be set to one.
5.2.5. MXNet Sector Status Map Register Block

428 - 488 6848 - 7808 Sectors 1 to 240 with 4 bits each
Bit 2 – Isolated, Bit 3 - Reserved
Table 54: Sectormap Registers
These are read-only registers. This map provides the PLC with indications of the total network sector alarm
status. If any device in any of the 240 available sectors is in the alarm, fault or isolated status a bit will be set in
this map.

All Rights Reserved
5.2.6. Time and Date Registers

Typically, one node of the MX network is set as the timekeeper. This node periodically broadcasts time and date
information via a special packet. The MXMB can also be set as a timekeeper.
Date Register
If the TLI800 node is set as the time and date keeper then this register shall hold the date, to be transmitted to
the MXNet.
Register 489 is used for network date information; the value for each bit is as below:
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit 0
64 32 16 8 4 2 1 8 4 2 1 16 8 4 2 1
Year Month Day
Register 489
Time Register
If the TLI800 node is set as the time and date keeper then this register shall hold the time, to be transmitted to
the MXNet.
Register 490 and 491 are used for network time information, the value for each bit is as below:
Bit15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit 0
- - - - 32 16 8 4 2 1 32 16 8 4 2 1
Not Used Minutes Seconds
Register 490
Bit15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Bit 0
- - - - - - - - - - - 16 8 4 2 1
Hours
Register 491
5.2.7. MX Panel Register Blocks – Example Panel Number 1, 2…

Panel MODBUS bits are spaced 8kB apart.

Panel 1

513 - 514 8208 – 8239 Panel Status Registers
515 8240 – 8255 Panel Control Register
516 – 519 8256 – 8319 Loop Information Registers
520 – 579 8320 – 9279 Zone Status Information
580 – 835 9280 – 13375 Detector Information Registers
836 – 860 13376 – 13775 Point Information Request Registers
861 – 882 13776 – 14127 Point Information Response Registers
883 – 887 14128 – 14207 Isolate / Deisolate Request Registers
888 - 894 14208 – 14319 Isolate / Deisolate Response Registers
Panel 2

All Rights Reserved
1536 – 1537 16400 – 16431 Panel Status Registers

… … …
Table 55: MX Panel Register Allocation
5.2.8. Command Acknowledge Register (CAR)

This register contains control bits that are required so that the PLC can initiate point data requests and also
perform device isolations.

Bit 0 Point data request done
Bit 1-7 Global bits not used
Bit 8 Isolate request done
Bit 9 - 15 Reserved
Table 56: Command Acknowledge Register Bits
Communication between PLC, MX CCU and MX panel is as follows:-

1/ The PLC checks the CAR request done bit in the MX CCU and waits until it is cleared.
2/ The PLC sends its point data or isolate request to the registers of the MX CCU.
3/ The MX CCU checks if it is a valid request and then sends the request to the MX panel.
4/ The MX panel processes the request and replies to the MX CCU.
5/ The MX CCU stores the reply in the reply register, then sets the CAR request done bit.
6/ The PLC then reads the reply to its request.
7/ The PLC then sends a “Null” command to instruct the MX CCU to clear the command done bit.
8/ The MX CCU process the “Null” command and clears the command done bit.
The isolate/de-isolate reply packet confirms that the panel has carried out the request. PLCs can check the
isolate status by reading the appropriate isolate bit.
The reply to the point data request will contain all the relevant information required by the PLC for the
appropriate point.
5.2.9. Panel Status Registers

These two registers contain information relating to MX panel status. They are read-only registers.

Bit 0 MX Panel Resetting
Bit 1 Reserved
Bit 2 MX Panel Not Responding
Bit 3 MX Common Alarm
Bit 4 MX Common Isolate
Bit 5 MX Common Fault
Bit 6 Main PCB failure
Bit 7 Customer EPROM checksum error
Bit 10 Mains supply fault
Bit 11 Battery fault
Bit 12 Earth fault
Bit 13 Remote Bus fault
Bit 14 Signalling device fault
Bit 15 Charger fault

All Rights Reserved
The Panel Resetting bit is active for 20 seconds after the panel is reset.
The second register contains information about system faults/isolations:

Bit 2 Fire alarm contact isolated
Bit 3 Signalling device isolated
5.2.10. Panel Control Register

This register is used to pass commands to the MX control panel. The commands available are as follows:
Register Contents Command

Bit 0 Silence Buzzer
Bit 1 Silence Panel
Bit 2 Panel resound
Bit 3 Day mode
Bit 4 Night mode
Bit 5 Function 1
Bit 6 Function 2
Bit 7 Reset
Bit 8 Fire Alarm/Evacuate
5.2.11. Loop Information

Each 16 bit register contains information about a particular loop in the system.

4 64 – 79 Loop A Information
5 80 – 95 Loop B Information
6 96 – 111 Loop C Information
7 112 – 127 Loop D Information
Table 59: Loop Information Registers
Bit Meaning when set

Bit 0 Loop Shutdown
Bit 1 Loop Communication Fault
Bit 2 Loop High Current Consumption
Bit 3 Loop Open circuit
Bit 4 Loop Short Circuit
Bit 5 Loop card fault
Bits 6-15 Reserved
Table 60: Loop Information Register Contents

All Rights Reserved
5.2.12. Zone Status Information

The zone status information registers provide an overview of the local control panel detection zones. Each panel
can have up to 240 fire detection zones configured.

8 - 67 128 – 1072 Zones 1 to 240 with 4 bits each
Table 61: Zone Status Information Register
5.2.13. Point Status Information

Bit 2 refers to the isolation of the addressable device. If the device address has either an input or an output
isolated, or both, then this bit is set.

68 - 131 1088 - 3096 Loop A, Points 1 to 250, with 4 bits each
132 - 195 2112 - 3120 Loop B, Points 1 to 250, with 4 bits each
196 - 259 3136 - 4144 Loop C, Points 1 to 250, with 4 bits each
260 - 323 4160 - 5168 Loop D, Points 1 to 250, with 4 bits each
Table 62: Point Status Registers
5.2.14. Point Information Request Registers

A point information data area is located within each of the pre-designated panel global map areas. These
registers contain MX Speak Point Information Request (148) packets with the headers stripped off. A MODBUS
Write to the first address in this area will trigger the sending of the Point Information Request packet on the MX
network.
The tables below list the data as it appears in this area for MX Speak V2,3,4 and 5. The message format is
slightly different to that for MX Speak 1 (Appendix B). Bytes 21 and 22 have been changed to reserved and byte
55 has been introduced for the device type.

11 Channel 0-6
325 12 Channel 0-15
Address
Number
Number
327 16 Logical Point 0-240, 254
Zone

All Rights Reserved

Category 1 = Inputs
2 = Outputs
3 = Callpoints
4 = Detectors
5 = Smoke Detectors
6 = Heat Detectors
7 = Flame Detectors
8 = CO Detectors
10 = Detector or Callpoint
11 = Supervised Output
19
State Store
21 Reserved 0
330 22 Reserved 0
Type
331 24 Areas 000-007 0-255 Lsb = Area 0
25 Areas 008-015 0-255 Lsb = Area 8
. . . . .
. . . . .
55 Device Type 0-255 Device Type (e.g. Heat Detector)
attached to the Point
347 56 Request Type 0-1 0 = First Point only
57 Search Type 0-10 0 = Points with Input Isolated
Isolated
Isolated
Forced
Forced
8 = Points Untested
10 = All Points
Table 63: MX Speak 2, 3 and 4. Point Information Request
5.2.15. Point Information Reply Registers

349 10 Reply Status 0-1 0 = Success, i.e. Point(s) found,
1 = Fail – no Point(s) found that match
the criteria
11 Flags 0-31 Bit0 = Input Forced
Bit1 = Point Untested or Failed (Walk
Test)
Bit2 = Input Isolated
Bit3 = Output Isolated
Bit4 = Out of Compensation
Bit5 = Non-Loop Point (0 = Loop Point)
13 Channel 0-6

All Rights Reserved
351 14 Channel 0-15

Address
Number
Number
353 18 Logical Point 0-240, 254
Zone
19 Device Type 0-254 As configured (See separate list of
Device Types)
354 20 I/O Detail 0-3 0 = Nil
1 = Supports Input
2 = Supports Output
3 = Supports Both Input and Output
355 21 Group 1-65535 Group
22
356 23 Area Type 0-1 Area
24 Area Number 0-255
357 25 Sector ID 0-255 = 254 if Zone not in Sector
26 Loop Type 0-2 0 = Thorn
1 = MX Digital
2 = Not Loop (i.e. Local or Remote Digital
Points)
358 27 Raw Identity 0-255 Identity code/value returned by the
device
28 Actual Device 0-254 Device Type that corresponds to the Raw
Type Identity
359 29 Mode & 0-255 As configured
Sensitivity
360 31 Raw Analogue 0-255 Value 2 as provided by the device,
361 33 LTA Flags 0-1 0 = Not available (some devices don’t
have it)
1 = LTA available
34 Raw LTA 0-255 LTA of main Raw Value
362 35 % Dirtiness 0-255
36 Unit of 0-9 0 = Invalid
Measure 1 1 = Degrees C
2 = Degrees F
3 = ppm (parts per million)
4 = %/ft Obscuration
5 = %/m Obscuration
6 = Y Value
7 = 1/10 Amp
8 = 1/10 V
9 = Not Installed
363 37 Unit of 0-9
Measure 2
38 Unit of 0-9
Measure 3
364 39 Converted 0-255 Value 1 in Units of Measure 1 (e.g. in
Value 1 %/m obscuration)
40 Converted 0-255 Value 2 in Units of Measure 2 (e.g. in °C)
Value 2
365 41 Converted 0-255 Value 3 in Units of Measure 3
Value 3

All Rights Reserved
42 Instantaneous 0-1 Instant single reading from driver

Active State 0 = Normal
1 = Active
366 43 Instantaneous 0-254 (See separate list of Fault States)
Fault State
44 Confirmed 0-1 Confirmed by driver – true physical state
Active State of the Point
0 = Normal
1 = Active
367 45 Confirmed 0-254 (See separate list of Fault States)
Fault State
46 Acknowledged 0-1 Acknowledged input state. (State
Active State actually used by MX – the Point is
assumed to be in this state. Typically is
the same as the Confirmed state, but it
may not be, e.g. when the input is
Forced.)
368 47 Acknowledged 0-254 (See separate list of Fault States)
Fault State
48 Output Forced 0-1 0 = Unforced
Mode 1 = Forced
369 49 Output 0-4 0 = OFF
Unforced 1 = ON
State 2 = Pulse 1 (pulsing in mode 1)
50 Output Forced 0-4 0 = OFF
State 1 = ON
370 51 Client ID 0-65535 Provided by the Server
52
Table 64: Point Information Reply
5.2.16. Point Isolate / De-isolate Area

A point isolate/deisolate data area is located within each of the pre-designated panel global map areas. These
registers contain MX Speak Point Status Update Request (135) packets with the headers stripped off. A
MODBUS Write to the first address in this area will trigger the sending of the Point Status Update Request
packet on the MX network.

3 = Detectors
4 = Callpoints
5 = Sounders
6 = Plant Controls

All Rights Reserved

1 = Zone
2 = Sector
If Target Type
= Point
13 Channel 0-5
373 14 Channel 0-15
Number
Number
375 18 Logical Point 0-240, 254
Zone
If Target Type
= Zone or
Sector
Table 65: Point Isolate / De-isolate Request

376 10 Number of 0-65535 Number of Points that matched the
11 Matches Request
377 12 Number of 0-65535 How many Isolate/De-isolate CHANGES
13 Successes were effected (e.g. Isolating a Point
already Isolated is NOT a success)
3 = Detectors
4 = Callpoints
5 = Sounders
6 = Plant Controls
1 = Zone
2 = Sector
If Target Type
= Point
17 Channel 0-5
380 18 Channel 0-15
Number
Number

All Rights Reserved
382 22 Logical Point 0-240, 254

Zone
If Target Type
= Zone or
Sector
Table 66: Point Isolate / De-isolate Reply

All Rights Reserved
6. MIPLOC Mode.
6.1. Reserved Registers

The shaded entries indicate MIPLOC registers that have not been implemented in the MXMB.
Register Register Usage

000 MIPLOC Status
001 PLC Status
002 Loop Faults
003 Walk Test Zone
004 Time - Hours
005 Time - Minutes
006 Time - Seconds
007 Time - Day
008 Time - Month
009 Time – Year
6.2. MIPLOC Status Word

The shaded entries indicate MIPLOC status bits that have not been implemented in the MXMB.
Bit Num
0 WDog Watchdog toggling every 20 seconds
1 MFlt MX OFF-line is set on a PTP Interface Error
2 SysFlt System Fault is not implemented
3 ComDne Set after a command has completed
4 IldIns Illegal Instruction is not implemented
5 KypMde Keypad Mode is not implemented
6 NewEvt Set after a bit has changed in the MIPLOC map (MXMB submap)
7 Unused Unused
8 ConErr The MXMB configuration checksum is invalid

9 PrcErr Internal Process Fault is not implemented
10 RamErr Ram Test Error is not implemented
11 WlkTst Walk Test Mode is not implemented
12 Buzzer Buzzer is not implemented
13 Isolate Common Isolate
14 Fault Common Fault
15 Fire Common Alarm
6.3. Watchdog Heartbeat

This feature enables the PLC to monitor the health of the MXMB and the link to it. The PLC should examine the
Watchdog bit in the MIPLOC Status word that is toggled by MXMB every 20 seconds. If after 20 seconds the
Watchdog bit in the MIPLOC Status word has been left in the same condition, either the MXMB has stopped
functioning or the serial link is faulty.
6.4. New Event Bit

This bit is set by the MXMB when a point bit in the MIPLOC map changes. The bit is set after the changed
registers in the PLC have been written. This bit is not set when a point configured as a door/damper changes
however.
This bit is cleared by the Reset New Event Bit command from the PLC. After this command has completed the
PLC should check the New Event bit again. This is to cover the situation where another event has occurred
immediately after the new event bit was cleared.

All Rights Reserved
6.5. PLC Status Word

The shaded entries indicate PLC status bits that have not been implemented in the MXMB.
Bit Num
0 Cmd0
1 Cmd1
2 Cmd2
3 Cmd3
4 Reserved Reserved
5 Reserved Reserved
6 Reserved Reserved
7 Reserved Reserved
8 Spare Spare
9 Spare Spare
10 Spare Spare
11 Spare Spare
12 Spare Spare
13 Spare Spare
14 ComReq Command Request Valid
15 EnbKpad Enable Minerva Keypad
6.6. Command Transfer From PLC to MX

The valid values for the Cmd field of the PLC status word are:
Cmd Command
1 Panel Reset
2 Panel Silence
3 Reset New Event Bit
4 Reset Illegal Instruction
5 Reset System Fault
6 Not defined
7 Fire Alarm
To initiate a command the PLC should:
1. The PLC will examine the ComDne bit in the MIPLOC Status word and wait until it is cleared by
MIPLOC.
2. PLC Sets ComCde in PLC Status word to the desired command code.
3. The PLC set the ComReq bit in the PLC Status word to initiate the processing command.
4. MIPLOC polls the PLC by reading the PLC Status word.
5. MIPLOC will detect that the ComReq bit is set and will read and action the command code in ComCde.
6. When complete MIPLOC will set ComDne in its status word and this will be transferred to the PLC.
7. The PLC will detect that the ComDne bit has been set showing that the command has been completed.
8. The PLC will clear the ComReq bit in the status word.
9. MIPLOC will detect the change in ComReq and clear the ComDne bit.

All Rights Reserved
6.7. Unimplemented MIPLOC Features

The following MIPLOC features have not been implemented in the MXMB due to technical design differences
between MX and MINERVA panels.
• Report Minerva Isolation as an illegal instruction.

• Enable alternative use of Pre-Alarm registers for the Advanced Flame Detector S251+ Range Warning
state.
• Enable Minerva Logging of Serial Link to PLC faults.
• Digital I/O Alarm, Fault and Isolate Registers
• System Alarm, Fault and Isolate Registers
• Walk Test Zone Register
• Enable Manual mode for acceptance of Unaccepted events and Minerva clock settings at the Minerva
when the MIPLOC/PLC are online.
• Minerva Keypad Enable
6.8. Further Information

Document: 07A-05-D1 MINERVA PROGRAMMABLE LOGIC INTERFACE CONTROLLER (MIPLOC)
PRODUCT APPLICATION AND DESIGN INFORMATION, Issue No 3

All Rights Reserved
7. Configuring the MODBUS Map

The MODBUS map must be configured using the CCU3/C-MXMB Programmer. The program allows the user to
add MX panels and CCU3 IO devices into the Global Map.
A useful feature is the ability to make a submap of up to 5120 bits from the bits in the global map. This allows the
user to mirror bits from the global map in the submap. For instance, bit 8345 in the global map may be mapped
to bit 0 in the submap. This gives the user flexibility in the layout of the MODBUS map.
7.1. Installing The CCU3-MXMB Setup Program

Running the Setup.exe application will install the MXMB Setup program to Program Files\TEPG\CCU3-MXMB. A
shortcut is added into the Start menu under Programs | Tyco | MXMB Programmer.
7.2. The CCU3-MXMB Setup Program
7.2.1. Opening, Saving and Restoring CCU3/C-MXMB Configurations

The user may clear the current configuration and start a new configuration by selecting File | New from the Main
Menu. A configuration can be saved by selecting File | Save from the Main Menu. All saved files are given the
extension .MXMB by default. A configuration can be loaded by selecting File | Open from the Main Menu.

All Rights Reserved
7.2.2. The MX Panel Setup Page

The MX panel page specifies which MX panels will be in the memory map of the CCU3/C-MXMB. These panels
must be configured using MX Consys to send logging events to the CCU3/C-MXMB.
Figure 11: MX Panel Setup Page

To add more MX panels to the configuration click the Add Panel button on the Fire Panels page. When the
New Panel screen appears fill in the MXNet address, which is the address of the MX panel on the MXNET. Add
a brief description for easy identification.
To remove a panel select the panel in the MX Network then press the Remove Panel button.
MX Speak Version: Select which MX Speak you are using.

Reset Panels on Startup: If ticked, send Reset command to the panels when the CCU starts up.
Timekeeper – Send time to Network: CCU is the timekeeper of the MX panel network. Modbus Mater should
write a timestamp to CCU3 Time and Date registers.
Always reply to Supervision Requests: If ticked, the CCU replies to Supervision requests sent from any panels
that are not in the Fire Panel list.
7.2.3. The Sector Map Setup Page

The sector map is used to calculate the status of the system sectors in the CCU3/C-MXMB. A sector is a
collection of zones, which may be from multiple panels. The MXMB updates its sectormap independently using
the zone-sector mappings configured here. The do not have to be the same as the MX sectors.

All Rights Reserved
Figure 12: Sector Map Setup Page
7.2.3.1. Adding and Removing Sector Mappings

To add another zone mapping to the Sector Map select the sector in the Sector Map then the required panel
zone in the Fire Panel Zones. Click the AddToSectormap button to add the new mapping.
To remove a zone mapping select the zone mapping in the Sector Map then press the
RemoveFromSectormap button.

All Rights Reserved
7.2.4. The Expansion Cards Page

Up to 4 expansion cards (IO or Ethernet cards) can be connected to the CCU3/C-MXMB. If you have an
Ethernet card, it needs to be added first. Only one Ethernet card can be added to the CCU3/C-MXMB.
7.2.4.1. Adding and Removing CCU/IO Nodes

To add a CCU3 Ethernet or CCU3 IO card click the Add Card button on the Expansion Cards page.
To remove a card select the one you want to remove then press the Remove Card button.
7.2.4.2. Configuring CCU3 IO Devices

Each CCU3/IO expansion card has 10 inputs and 4 relays.
Each input can be set to either disabled or supervised Input. Each relay can be set either disabled or relay.
The sense of all CCU3/IO inputs and outputs is configurable, to operate in either normal or reversed mode. In
normal mode, the relay outputs read set when the relays are energised; in reversed mode, they would read
cleared for this case. In normal mode the ‘active’ bit is set for a normal input, in reversed mode the ‘active’ bit is
cleared for a normal input. The ‘input fault’ bit is not affected by the normal or reverse modes.
7.2.4.3. Configuring CCU3/E

Click on CCU3/Eth card from the Expansion Cards, you’ll see IP Address, Subnet Mask, and Gateway. Please
contact IT system administrator to get these details.

All Rights Reserved
7.2.5. The Submap Setup Page

The submap is a custom map which is configured by the user to reference addresses in the Global Map. This
allows the user to build a custom map consisting only of the data they require. The submap is also used as the
active map for AUTRONICA, PROFIBUS and PROFISAFE operation. The number of bits in the submap is
constant however the number that can be transferred varies depending on the protocol.
The user selects which bits to add to the submap from the global map and the order in which they are arranged.
The submap may include any bits from the global map including CCU3/IO bits.
To add bits to a submap go to the Submap page, by clicking on the Submap tab at the top of the window (see
figure 30). To add a bit to a submap find the bit that you wish to add in the Global map on the left hand side of
the screen. Remember you can expand and collapse branches by clicking the ‘+’ and ‘-‘ signs. Select the bit then
the click Add button. The bit should appear in the submap on the right-hand side of the screen. If the Add button
is ‘greyed out’ then a valid bit has not been selected.
Blank bits or unused addresses may be added to the submap by adding the Unused Entry in the Global Map
Tree to the submap or clicking the Unused button.
To remove a bit from the submap select the bit from the submap on the right-hand side of the screen and then
press the Remove button. The bit should disappear from the submap.
It is possible to add the same bit to the submap more than once. Change the position of entries in the submap
by dragging them to the desired location.
Figure 13: Submap Setup Page

All Rights Reserved
7.2.6. The PTP Interface Setup Page

These settings are used for the communication between the MX panel and the CCU3/C-MXMB. The Network
Address must be set to the jumper address of the TLI-800 and the rest of the settings set to match the network.
For further information and help with these settings refer to publication number 19700344 Network Interface
Module and to MXSpeak Reference Guide for Advanced Third Party Interface Applications.
It is recommended that the default settings displayed when the program is first run should be used. These are
the default settings used in MXConsys.
ATTN: These parameters must be identical for all nodes on the MXNet. Also the Network Peer Limit value
must be set to equal or exceed the number of nodes on the network.
Figure 14: PTP Interface Setup Page

All Rights Reserved
7.2.7. The Modbus Interface Setup Page

The CCU3/C-MXMB is connected to the MODBUS as a slave device and therefore requires a MODBUS
address.
The reply delay is the time between the master’s MODBUS request and the answer from the CCU3/C-
MXMBMB. This delay gives the master time to turn off its transmitter when RS485 is being used.
The baud rate and parity of the MODBUS communications is also specified here.
MODBUS Interface 0
Is the configuration page for CCU3 Comport 4.
MODBUS Interface 1
Is the configuration page for CCU3 Comport 3. You can disable this port if you wish.
Figure 15: Modbus Interface Setup Page

All Rights Reserved
7.2.8. The Other Options Setup Page
Figure 16: Other Options Setup Page
SNTP – A CCU3/E-MXMB is able to update its time from a network SNTP Server. A CCU3/E plug-in board and
an Ethernet connection are required. If the CCU3/E-MXMB has been set as a timekeeper this time will be
broadcast to the MX Network.
MODBUS TCP – Sets the word order in MODBUS packets sent over TCP when an Ethernet connection is used.
MXMB Options: Map Type – This option changes the structure and functioning of the submap. Changing this
option causes a short delay while the map is rebuilt.
• Standard Mode – Operates as a standard CCU3/C-MXMB. The submap is a simple collection of bits
mapped from the fixed map. Each bit in the submap represents the state of one device event. For
example, bit 10 is the alarm state of a point 01-A005.
• AUTRONICA Mode – Changes the submap to a mode compatible with AUTRONICA panels. The
submap is organised as one word register for each point, each register stores an integer value
representing the current device state.
Value Device State

1 Normal
3 Alarm/Fire
5 Pre Alarm
7 Trouble
8 Isolate
• MIPLOC Mode – The CCU emulates a Minerva MIPLOC interface. This allows for a Minerva / MIPLOC
site to be upgraded to MX / CCU3 without requiring reprogramming of the PLC. In MIPLOC mode the
CCU operates as a MODBUS master updating the registers in the PLC using the defined submap. Use
of the submap will allow any differences between the MX and Minerva loops to be catered for. The
MIPLOC had some reserved registers for doing panel commands, MIPLOC status, panel time/date,etc.
These are carried across in the CCU submap, though only some are implemented. The reserved

All Rights Reserved
registers cannot be removed from the submap. See the MIPLOC chapter of this document for more
information.
• CCU2 Compatibility Mode - Setting this option changes the CCU3/C-MXMB to have a similar submap
and global map format to the CCU2/C-MXMB, allowing the CCU3 to be a drop-in replacement for a
CCU2. When swapping from “Standard mode” to this option, the program automatically recalculates all
of the memory map positions and bit numbers for the global map and submap, without clearing the
submap.
MXMB Options: Latch Points in Alarm – Select this option to latch point alarms into the CCU3/C-MXMB. The
alarm bit will only clear when the panel is reset, not when the point clears.
MXMB Options: Pointmap Status Bit Use – This defines the use of the status bit in the MX panel pointmap. The
options are:
• Pre-Alarms – The status bit indicates point prealarms.

• Door/Damper - The status bit indicates Door/Damper status. When this option is NOT selected
Door/Damper status is indicated with the active (alarm) bit. Note that for Door/Damper states to be
available Door/Damper pointmap broadcast must be enabled in Consys.
• Window Fault - When enabled WINDOW FAULT (233) event messages set the point status bit in
addition to the point fault bit. This setting is mainly for compatibility with MIPLOC systems that used this
setting.
MXMB Options: Zonemap Status Bit Use – This defines the use of the status bit in the MX panel zonemap. The
options are:
• Pre-Alarms – The status bit indicates zone prealarms.

• Gas Alerts – The status bit reflects the values from the MX panel zone status message.
MIPLOC Options – These settings only apply when the CCU is in MIPLOC mode.
• PLC Base Register Address - the address in the PLC where the MIPLOC table starts.
• TCP Connection to PLC - Check to use a TCP connection to the PLC from the CCU. Edit boxes appear
when this box is checked to allow entry of the IP addresses of up to four PLC hosts.
• MIPLOC Map Type - There are 4 default MIPLOC submap formats and a fifth option of “Custom” for a
user defined map. Note that these options require a MX fire panel to be added before they can generate
the submap. If multiple MX panels have been added, the default MIPLOC submaps all use the first MX
panel. Changing this option causes a delay while the map is rebuilt.

All Rights Reserved
7.3. Programming the CCU3/C-MXMB

When the configuring process is complete the user should save the work and then program the CCU3/C-MXMB.
To plug the computer into the CCU3/C-MXMB, please use the CCU3-PROG cable provided. ( refer to the
section 2.8.4 listing the pinout descriptions if you need to make a cable ). Connect this cable from the desired
COM port of the computer to Com 2 on the CCU3/C-MXMB.
Before programming is commenced the PC’s comport must be set in the CCU3/C-MXMB Programmer to the
port that the CCU3/C-MXMB is connected to. To do this select Update | Programming Options from the Main
Menu.
To program:
The CCU is powered and working before programming.
Press the Update | Firmware and Data or select Update | Data only from the Main Menu. Programming should
commence and a success message will be displayed when finished.

All Rights Reserved
8. Communication
8.1. MODBUS Communication Parameters

19200 baud, no parity, 8 data bits,1 stop bit.
8.2. MODBUS Commands

The CCU3/C-MXMB connects to a MX MODBUS as a slave. The MODBUS master may use any of the
following 4 MODBUS commands:
Code Description
1 Read Coil Status
2 Read Input Status
4 Read Input Registers
15 Force Multiple Coils
16 Preset Multiple Registers

All Rights Reserved
8.2.1. Read Coil Status (01)

Read Coil Status reads the ON/OFF status of discrete output from the MODBUS map.
An example of Read Coil Status command:
Field Example
MODBUS Address 5
MODBUS Function 1
Starting Address Hi 0
Starting Address Low 18
Number of Points Hi 0
Number of Points Low 37
CRC16 (Low) ???
CRC16 (High) ???
This command is to request to read coils 18 to 55 from the MODBUS 5.

The ‘Starting MODBUS bit address’ is always rounded down to its byte boundary and so the number of bytes
returned will encompass the number of bits requested. Hence the bits are returned on their byte boundary (i.e.
bit positions within the bytes are as their appear in the MODBUS map).
An example of reply message for Read Coil Status command is shown below. 1 indicates ON, 0 indicates OFF.
Field Example
MODBUS Address 5
MODBUS Function 1
Number of bytes returned 5
Data (Coils 23-16) CD 1100 1101
Data (Coils 31-24) 6B 0110 1011
Data (Coils 39-32) B2 1011 0010
Data (Coils 47-40) 1E 0001 1110
Data (Coils 52-48) 1B 0001 1011
CRC16 (Low) ???
CRC16 (High) ???
If returned coils are not a multiple of 8, the remaining bits are padded with zeros. The status of coils 23 to 16 is
1100 1101, which means Coil 16 is ON, Coil 17 is OFF, … Coil 23 is ON.
Coil 53, 54 and 55 are not requested but zero padded to fill 8 bit data.

All Rights Reserved
8.2.2. Read Input Status (02)

Read Input Status reads a range of bits from the MODBUS map. This command can read up to 65535 bits
starting at any address range from 0 to 65535 in the MODBUS map. This command is used to read from the
Global MODBUS on the CCU3/C-MXMB.
The byte fields of this command type are as follows:
Request:
1. MODBUS Address
2. MODBUS Function
3. Starting bit address (High byte)
4. Starting bit address (Low byte)
5. Number of bits (High byte)
6. Number of bits (Low byte)
7. CRC16 (Low byte)
8. CRC16 (High byte)
Reply:
1. MODBUS Address
2. MODBUS Function
3. Number of bytes returned
4. Data (number of data bytes is ‘number of bytes returned’)
5. CRC16 (Low byte)
returned will encompass the number of bits requested. Hence the bits are returned on their byte boundary (i.e.
bit positions within the bytes are as their appear in the MODBUS map).
The status of the returned bits is indicated as: 1 = ON; 0 = OFF.
Note: If the number of bits returned does not divide evenly into eight then the remaining bits, front and back
padding, will reflect the status of those bits with the same remaining valid addresses in the Global MODBUS
map.
Example
Request:
Field Example
MODBUS Address 5
MODBUS Function 2
Starting Bit Address (High) 1
Starting Bit Address (Low) BF
Number of Bits (High) 0
Number of Bits (Low) 12
CRC16 (Low) ???
CRC16 (High) ???
NB. CRC16 must be calculated using the appropriate formula by the MODBUS master and added in
the last word position (it takes up 2 bytes).
This command will read 0012hex (18 decimal) bits from MODBUS device 5 starting at MODBUS address
01BFhex (447 decimal).
The CCU3/C-MXMB will return the bits from address 01BFhex to 01D1hex. Address 01BF is eighth bit in the
56th byte hence the starting byte returned is the 56th byte therefore the address of the first bit returned is
01B8hex. The bits are packed into bytes in the reply message. The first data byte of the reply contains the bits of
the lowest 8 addresses, with the lowest or first address being represented by the LSB (Least Significant Bit).

All Rights Reserved
Reply:
Notice the start address in this example is rounded down to the byte boundary and the number of bytes returned
is rounded to include the top bit address.
Field Example
MODBUS Address 5
MODBUS Function 2
Number of Bytes Returned 4
Data (Address 01B8 – 01BF) E5
Data (Address 01C0 – 01C7) 4D
Data (Address 01C8 – 01CF) 02
Data (Address 01D0 – 01D7) 78
CRC16 (Low) ???
CRC16 (High) ???
NB. CRC16 is calculated by the CCU3/C-MXMB and takes up 2 bytes.

All Rights Reserved
8.2.3. Read Input Registers (04)

The Read Input Registers command allows the MODBUS master to read from the Global MODBUS map using
the register address of the bits to be read. This command returns word wide bytes from the MODBUS map.
Request:
1. MODBUS Address
2. MODBUS Function
3. Starting register/word address (High byte)
4. Starting register/word address (Low byte)
5. Number of registers/words (High byte)
6. Number of registers/words (Low byte)
7. CRC16 (Low byte)
Reply:
1. MODBUS Address
2. MODBUS Function
3. Number of bytes returned
4. Data (number of data bytes is ‘number of bytes returned’, low byte followed by high byte)
5. CRC16 (Low byte)
The status of the returned bits is indicated as: 1 = ON; 0 = OFF.

The first data byte of the reply contains the low byte of the first register/word to be returned.
Example
Request:
Field Example
MODBUS Address 5
MODBUS Function 4
Starting Register (High) 0
Starting Register (Low) 2
Number of Registers (High) 0
Number of Registers (Low) 1
CRC16 (Low) ???
CRC16 (High) ???
the last word position ( it takes up 2 bytes ).
This command will read register 0002hex from MODBUS device 5. This register is part of the SUBMAP. The
number of registers to be returned is 0001hex. The CCU3/C-MXMB will return 16 bits from the SUBMAP.
Reply:
Field Example
MODBUS Address 5
MODBUS Function 4
Number of Bytes Returned 2
Data (Register 2 (Low)) C0
Data (Register 2 (High)) 4E
CRC16 (Low) ???
CRC16 (High) ???

All Rights Reserved
8.2.4. Force Multiple Coils (15)

Force Multiple Coils sets a range of bits in the MODBUS map. This command can set up to 65535 bits starting
at any address range from 0 to 65535 in the MODBUS map. This command is used to set bits in the Global map
of the CCU3/C-MXMB. The value of this bit will be reported back until the bit is rewritten by another device or by
the CCU.
Request:
1. MODBUS Address
2. MODBUS Function
7. Number of bytes
8. Data (number of bytes needed to write the appropriate data)
9. CRC16 (Low byte)
Reply:
1. MODBUS Address
2. MODBUS Function
7. CRC16 (Low byte)
returned will encompass the number of bits requested. Hence the bits are written on their byte boundary (i.e. bit
positions within the bytes are as their appear in the MODBUS Global map).
The status of the written bits is expected as: 1 = ON; 0 = OFF.
Note: If the number of bits to be written does not divide evenly into eight then the remaining bits, front and back
padding bits, will reflect the status of those bits with the same remaining valid addresses in the Global MODBUS
map.
Example
Request:
Field Example
MODBUS Address 5
MODBUS Function 0F
Starting MODBUS Address (High) 1
Starting MODBUS Address (Low) 51
Number of Bytes 02
Data (Address 0150 – 0157) C2
Data (Address 0158 – 015F) 01
CRC16 (Low) ???
CRC16 (High) ???
The data to be written is expected as byte-aligned bits as they would be read in the Global MODBUS map.
The first data byte contains the bits of the lowest 8 addresses, with the lowest or first address being represented
by the LSB (Least Significant Bit). Bits of no interest should reflect the status that they should appear in the
Global MODBUS map.
The CCU3/C-MXMB returns the start address and the number of coils successfully set.

All Rights Reserved
Reply:
Field Example
MODBUS Address 5
MODBUS Function 0F
Starting Bit Address (High) 1
Starting Bit Address (Low) 51
CRC16 (Low) ???
CRC16 (High) ???

All Rights Reserved
8.2.5. Preset Multiple Registers (16)

The Preset Multiple Registers command allows the MODBUS master to write to the MODBUS map using the
register address of the bits to be set.
Request:
1. MODBUS Address
2. MODBUS Function
3. Starting register address (High byte)
4. Starting register address (Low byte)
7. Number of bytes
8. Data (number of bytes needed to write the appropriate data)
9. CRC16 (Low byte)
Reply:
1. MODBUS Address
2. MODBUS Function
3. Starting register address (High byte)
4. Starting register address (Low byte)
7. CRC16 (Low byte)
Note: Data to be written is expected as low byte – high byte order.
Example
Request:
Field Example
MODBUS Address 5
MODBUS Function 10(hex)
Starting register (High) 0
Starting register (Low) 3
Number of Registers (High) 0
Number of Registers (Low) 2
Byte Count 2
Data (Register 3 (High)) 1D
Data (Register 3 (Low) F0
Data (Register 4 (High)) 12
Data (Register 4 (Low)) 69
CRC16 (Low) ???
CRC16 (High) ???

All Rights Reserved
This command will write register 3 and register 4 on MODBUS device 5.

The CCU3/C-MXMB returns the start address and the number of registers successfully written.
Reply:
Field Example
MODBUS Address 5
Starting register (High) 0
Starting register (Low) 3
Number of registers (High) 0
Number of registers (Low) 2
CRC16 (Low) ???
CRC16 (High) ???

All Rights Reserved
8.2.6. Error Responses

When the CCU3/C-MXMB detects an error in the query message, it cancels the process and sends master a
response message with an exception code referring to the error. The function code used is the function code in
the query message with 80hex added.
The byte fields of the error response are as follows:
Error Response:
1. MODBUS Address
2. MODBUS Function
3. Error Code
4. CRC16 (Low Byte)
The defined error codes are:

Error Code Meaning
1 The Function Code received in the Query is not an
allowable action for the CCU3/C-MXMB.
2 The Address received in the Query DATA field is not
allowable address for the CCU3/C-MXMB.
3 A Value contained in the Query DATA field is not an
allowable value for the CCU3/C-MXMB.
For example the reply to the invalid MODBUS function 7 would be:
Field Example
MODBUS Address 5
Error Code 1
CRC16 (Low) ???
CRC16 (High) ???
8.2.7. Calculating CRC16

Step 1 - Start with a 16-bit register set to FFFF hex. Call this the CRC16 register.
Step 2 - Exclusive OR the first eight-bit byte of the message with the low byte of the CRC16 register, putting the
result in the CRC16 register.
Step 3 - Shift the CRC16 register one bit to the right, shifting in a zero for the MSB.
Step 4 - If the LSB in the CRC16 register is 0, repeat Step 3. If the LSB is 1, Exclusive OR the CRC16 register
with A001 hex (1010 0000 0000 0001).
Step 5 - Repeat Steps 3 and 4 until eight shifts have been performed. When this is done, a complete eight-bit
byte will have been processed.
Step 6 - Repeat Steps 2 ... 5 for the every byte in the message.
Step 7 – Place the CRC16 value in the message.

All Rights Reserved
8.3. Point Information Request

The ‘Point Information Request’ registers in the CCU are located at the address positions as specified in the
section 4.2.14. Error! Reference source not found.. That is, at offset address 789 in each of the panel bits the
’Point Information Request’ bits start.
NOTE: When performing a write to the MODBUS the data sent to the CCU must be in Lo-Hi byte format. Hence
when writing to the ‘Point Information Request’ addresses be sure to send the data to be written as it would
appear in the registers (from register 789 to register 812, Lo-Hi).
8.4. Isolate De-isolate Request

As with the ‘Point Information Request’ the ‘Isolate De-isolate Request’ is written to the CCU in the same
fashion, Lo-Hi byte. However, the starting address of the ‘Isolate De-isolate Request’ data is at 783.
8.5. CCU Timekeeping

There are two ways to configure the MXNet timekeeping with reference to the CCU3/C-MXMB. The first is to
configure one of the panels on the MXNet to be timekeeper. Once the time has been set correctly on this panel it
will broadcast the time and date to the MXNet and all nodes on the net will use its time to keep time (including
the CCU). The second way is to enable the CCU as timekeeper. On power up the CCU has a default time and
date that will be used if configured as the timekeeper. In order to set the correct time and date set the
appropriate bits in the time and date registers, in the MODBUS map, and the CCU will set its own time to this
and use this time to perform timekeeping on the MXNet. Please see section 4.2.5. of this document for date and
time format.

All Rights Reserved

All Rights Reserved
9. Example CCU3/C-MXMB Setup

This section will step through an example configuration. The example configuration will map five devices
(labelled ‘A’, ‘B’, ‘C’, ‘D’ and ‘E’):
• 3 x MX panels connected to the MXNET (‘A’, ‘B’ and ‘C’).
• 2 x CCU/IO boards on the CCUioNET (‘D’ and ‘E’)
The MODBUS map that we will require for this example project will list all of the zone alarms (excluding zone 0,
the system zone) of the three MX panels in the start of the address map. Leave some blank addresses and then
have all of the active bits from CCU/IO ‘D’. Next we will have 8 more blank addresses then active bits from
CCU/IO from CCU/IO ‘E’.
Address
0
Panel ‘A’ Zone Alarms 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
16
Panel ‘B’ Zone Alarms 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
32
Panel ‘C’ Zone Alarms 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
112
BLANK
128
CCU/IO ‘D’ Active bits BLANK
1 2 3 4 5 6 7 8
134
CCU/IO ‘E’ Active bits BLANK
1 2 3 4 5 6 7 8
Figure 17: The desired MODBUS Map

All Rights Reserved
9.1. Add the MX Panels

Our example system has three MX panels, ‘A’, ‘B’ and ‘C’. To add a panel press the Add button or select
Edit | Add from the Main Menu. The MXNet Address box must be filled in with the address of the MX panel
on the MXNet. Press OK. If you have already entered a panel with this address an error message will be
displayed, otherwise the new MX should be listed in the MX Panel Tree on the left hand side of the screen.
You may need to expand the tree to see the node, to do this press the ‘+’ next to ‘Global Map’. To add a
description to this panel double-click on the panel in the MX Panel Tree.
Add MX panel ‘B’ and ‘C’ in a similar way.
9.2. Add the CCU/IO Nodes

Our example system has two CCU/IO nodes- the CCU/IO-485 boards ‘D’ and ‘E’. To add a node press the
Add button or select Edit | Add from the Main Menu. The new CCU/IO node should be listed in the CCU/IO
Devices Tree on the left hand side of the screen. You may need to expand the tree to see the node, to do
this press the ‘+’ next to ‘CCU devices’. To add a description to this node so it is not confused with other
nodes double-click on the node in the CCU/IO Devices Tree. The node number in the CCU/IO Devices
Tree should match the address on the CCU/IO board. So CCU/IO board ‘D’ has address 1 on the
CCUioNET.
Add CCU/IO board ‘E’ in a similar way.
9.3. Set up the Submap

At this stage, the Global Map is completely set up. Now all that is left is to create a submap of points that are
useful to us from the global map.
9.3.1. Adding the MX Zone Alarms to the Submap

The appropriate bits from the Global Map must be added to the submap in the desired order. For us, this means
that Panel ‘A’ Zone Alarm 1 should be added first. To do this open the Submap page and expand the MX Panel
Devices Tree to be able to see the Zone Alarm 1. It should come under Global Map – MX ( Device ‘A’ ) – Zones
– Zone 1. Select Alarm Zone 1 by clicking on it. The Add button should change so it is no longer ‘greyed out’.
Click the Add button, the bit should appear in the submap on the right-hand side of the screen. Repeat this for
all of the Zone Alarms on all three MX panels, making sure that they stay in order in the submap.

All Rights Reserved
Figure 18: Adding the Zone Alarm bits to the submap

All Rights Reserved
9.3.2. Adding the Blank Addresses to the Submap

In the course of laying out a submap often there are addresses that are not needed or used and so are left
blank. To do this select Unused Entry from the MX Panel Devices Tree and press Add to add it to the submap.
As many unused addresses as are required may be added to the submap. However, unused bits still take up
space in the submap.
Add the desired 16 unused bits to the example project.

All Rights Reserved
9.3.3. Adding the CCU/IO Active Bits to the Submap

The CCU/IOs have two bits for every input on the board. One indicates a supervision fault on the input and the
other indicates that the input has been set to its active state. For the example project the eight Active bits of
CCU/IO ‘D’ and ‘E’ are added to the submap with eight blank spaces between them.
To add the Active bits to the example project expand the Global Map Tree to be able to see the Input Active
Node 1 Device. It should come under Global Map – CCUioNET Nodes – Node 1 (Device ‘D’) – Node 1 Device 1
– Input Active Node 1 Device. Select Input Active Node 1 Device by clicking on it. The Add button should
change so it is no longer ‘greyed out’. Click the Add button, the bit should appear in the submap on the right-
hand side of the screen. Repeat this for all of the Active bits on the CCU/IO, making sure that they stay in order
in the submap.
Add eight unused (blank) bits.
Add the eight Active bits for CCU/IO ‘E’.
Figure 19: Adding the Input Active Bits to the Submap

All Rights Reserved
9.4. Setup the PTP Interface

Set the Network Address to match the jumper address of the TLI-800 and the rest of the settings to match the
settings you used in your MXConsys setup.
It is recommended that the default settings displayed when the program is first run should be used. These are
the default settings used in MXConsys.
For further information and help with these settings refer to publication number 19700344 Network Interface
Module and to MXSpeak Reference Guide for Advanced Third Party Interface Applications.
9.5. Setup the MODBUS Interface

Set your MODBUS address and baud rate.
9.6. Setup the Other Options

Select which network protocol you are using.

All Rights Reserved
9.7. Save the Project and Program the CCU3/C-MXMB

Now both the global map and the submap are totally set up. Before programming the CCU3/C-MXMB it is a
good idea to save your work, so that it can be used again at a later date, or for reference purposes.
9.7.1. Saving
To save all of the information that has been entered so far press the Save button or select File | Save from the
Main Menu. To restore it at a later date press the Load button or select File | Load from the Main Menu.
9.7.2. Programming
Connect the CCU3/C-MXMB to the computer using a CCU3 Prog cable provided from the desired com port of
the computer to Port 1 on the CCU3/C-MXMB.
Before programming is commenced the comport must be set in the CCU3-MXMB Programmer program to the
port that the CCU3/C-MXMB is connected to. To do this select Update | Programming Options from the Main
Menu.
Select Update | Data only from the Main Menu. Programming should commence and once all of the lines have
been sent a success message should be displayed.

All Rights Reserved
10.Testing the Configuration

Once the configuration has been downloaded to the CCU it can be tested using the supplied test application modbus.exe. To use this program the CCU and
panels must be on the MXNet with all of the relevant cabling installed.
The File | Open menu allows the MXMB file that was saved in the CCU3-MXMB Programmer program to be opened. Locate the MXMB file and open it.
Go to Settings | Communications to setup the comport you are using.
When the communication is set, press Enable. Then you can go to Communications page to see packets transmitting and receiving. Each of the tab sheets
display the bits in the map that are being polled at present.
The different sections of the map have been separated into different pages in the window. To identify a bit which is activated in the map move your mouse over the
bit and the name will be displayed in the status bar on the bottom of the window. This will work with all of the bits in each of the tab windows.

All Rights Reserved
To send commands to the panel, select the function to be sent to the panel by clicking on the radio buttons in the ‘Commands’ tab in Fire Panels page. Then click
the ‘Send Panel Command’ button.

All Rights Reserved
To send a Point
Information
Request use the
Point Info Request
tab to enter in the
packet data to be
sent to the panel.
Enter the values in
the text edit boxes
on the left of the
window and click
the Send Point
Information
Request button.
This will write those
values to the
appropriate area in
the MODBUS map
and send the
packet to the panel.
The reply will be
updated
automatically.

All Rights Reserved
To send an MX
panel an
Isolate/Deisolate
Request refer to the
previous description
of how to send a
Point Information
Request and use
the same process
for the
Isolate/Deisolate
Reply.

All Rights Reserved
To set the time and

date in the CCU
enter the values in
the text edit boxes
on the left hand
side click the Send
Time and Date
button. NOTE:
Enter in the real
year (eg. 2001),
however the actual
value written to the
CCU is years from
1900.
Time and Date
information is
updated
automatically.

All Rights Reserved
Appendix A CCU3 Serial Ports

Each Port on the CCU3 can be software selected for RS232, RS485 or RS422 operation. The following
sections will denote the port pin settings for each of these modes of communication
RS232 Operation
Pin Number Function

6 RXD
5 DSR/CTS
4 0V
3 TXD
2 DTR/RTS
1 SHIELD/GND
Table 67
Figure 20: RS232 Connection
RS485 Operation
Pin Number Function
6 Not Connected
5 Not Connected
4 0V
3 -VE
2 +VE
1 SHIELD/GND
Table 68
RS422 Operation
All Rights Reserved
Pin Number Function

6 RX-
5 RX+
4 0V
3 TX-
2 TX+
1 SHIELD/GND
Table 69

All Rights Reserved
Appendix B MX Speak 1 Point Information Request/Reply

MX Speak 1 Point Information Request

11 Channel 0-6
719 12 Channel 0-15
Address
Number
Number
721 16 Logical Point 0-240, 254
Zone
Category 1 = Inputs
2 = Outputs
3 = Callpoints
4 = Detectors
5 = Smoke Detectors
6 = Heat Detectors
7 = Flame Detectors
8 = CO Detectors
19
State Store
21 Area Type 0-1, 3
724 22 Area Number 0-255
Type
725 24 Areas 000-007 0-255 Lsb = Area 0
25 Areas 008-015 0-255 Lsb = Area 8
726 26 Areas 016-023 0-255 Lsb = Area 16
27 Areas 024-031 0-255 Lsb = Area 24
727 28 Areas 032-039 0-255 Lsb = Area 32
29 Areas 040-047 0-255 Lsb = Area 40
728 30 Areas 048-055 0-255 Lsb = Area 48
31 Areas 056-063 0-255 Lsb = Area 56
729 32 Areas 064-071 0-255 Lsb = Area 64
33 Areas 072-079 0-255 Lsb = Area 72
730 34 Areas 080-087 0-255 Lsb = Area 80
35 Areas 088-095 0-255 Lsb = Area 88
731 36 Areas 096-103 0-255 Lsb = Area 96
37 Areas 104-111 0-255 Lsb = Area 104
732 38 Areas 112-119 0-255 Lsb = Area 112
39 Areas 120-127 0-255 Lsb = Area 120
733 40 Areas 128-135 0-255 Lsb = Area 128
41 Areas 136-143 0-255 Lsb = Area 136
734 42 Areas 144-151 0-255 Lsb = Area 144
43 Areas 152-159 0-255 Lsb = Area 152
735 44 Areas 160-167 0-255 Lsb = Area 160
45 Areas 168-175 0-255 Lsb = Area 168
736 46 Areas 176-183 0-255 Lsb = Area 176
47 Areas 184-191 0-255 Lsb = Area 184
737 48 Areas 192-199 0-255 Lsb = Area 192
49 Areas 200-207 0-255 Lsb = Area 200
738 50 Areas 208-215 0-255 Lsb = Area 208
51 Areas 216-223 0-255 Lsb = Area 216

All Rights Reserved
739 52 Areas 224-231 0-255 Lsb = Area 224

53 Areas 232-239 0-255 Lsb = Area 232
740 54 Area 240 0-1 Lsb = Area 240
55 Request Type 0-1 0 = First Point only
741 56 Search Type 0-10 0 = Points with Input Isolated
Isolated
Isolated
Forced
Forced
8 = Points Untested
10 = All Points

All Rights Reserved

All Rights Reserved

TycoCCU3-MXMB 420

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TycoCCU3-MXMB 420

Uploaded by

Copyright:

Available Formats

Rev: 4.

Installation and Configuration Manual

5.2. MODBUS MAP REGISTER AND BIT DETAILS ..................................................................................41

 Copyright base2, 2012 3 of 93

9.3.2. Adding the Blank Addresses to the Submap.............................................................................80

APPENDIX A CCU3 SERIAL PORTS .................................................................................................89

 Copyright base2, 2012 4 of 93

Expansion cards can be added to the CCU3/C-MXMB to provide extra functionality.

• CCU3/E - Supports MODBUS TCP. Up to 4 simultaneous TCP connections are supported.

Protocol Effective Submap Size

 Copyright base2, 2012 5 of 93

1.2. Ordering Configurations:

 Copyright base2, 2012 6 of 93

1.3. System Requirements for CCU3/C-MXMB Programmer

• 100 Mb of disk space for installation.

• Windows® 95, 98, 2000, XP, NT or Windows® 7 operating system

• Microsoft® Windows compatible pointing device (such as a mouse)

• A communications port for reprogramming the CCU3/C-MXMB.

 Copyright base2, 2012 7 of 93

2.1. Parts Supplied

2.2. You will need

2.3. Power Requirements

2.4. Board Layout

 Copyright base2, 2012 8 of 93

2.5. Connecting the CCU3/C-MXMB

Com 2 Configuration and

Figure 3: Multiple Panel Configuration

 Copyright base2, 2012 9 of 93

Figure 4: Single Panel Configuration

 Copyright base2, 2012 10 of 93

2.6. MX Network Configuration

2.6.1. CCU3/C-MXMB to TLI800 / TLI800EN Connection

Figure 5: RJ12 Plug for Connection to TLI800 PL2

CCU3 6 Pin Port 1 Signal Common

Figure 6: CCU3-TLI800-B Cable

 Copyright base2, 2012 11 of 93

2.6.2. TLI800 Configuration

SW1 Switch Application Assembly SW1 Switch Network SW1 Network

Table 2 Switch SW1 Functions

SW2 Value SW2 Function

Table 3 Switch SW2 Functions

• Set SW1-1, 1-2 and 1-3 to “Gateway” for the MXMB.

 Copyright base2, 2012 12 of 93

2.6.3. TLI800EN Configuration

Switch 1 position Application

Switch 1 position Network Baud Rate

Switch 1 position Network Topology

 Copyright base2, 2012 13 of 93

Switch 1 position Firmware upgrade of M MCU

Switch 2 position Host Interface

Switch 2 position Emergency Display

Switch 2 position Host Interface Baud Rate

 Copyright base2, 2012 14 of 93

Switch 2 position M MCU Watchdog

Switch 2 position E MCU Watchdog

Switch 2 position Firmware upgrade of E MCU

Switch 3 position Node

Switch 3 position Node Address or Test Option

• Set SW1-1 and 1-2 to “Gateway/BMX” for the MXMB.

 Copyright base2, 2012 15 of 93

2.6.4. TLI800 and TLI800EN Consys Setup

Figure 7: Consys Network Overview

Figure 8: Consys Log Settings