Tibv31 4

TIB 1211
TECHNICAL INFORMATION BULLETIN
MZX Firmware and Consys

Version 31.4
1 General Note
The main features in Version 31.4 are:
• Firmware compatibility with update CPU801 and PFI800 boards.
• Improved to sounder processing
• Compatibility with Connected Services Gateway (CSG800)
• Consys links to datasheets
• Improved callpoint processing on noisy loops.
The main features in Version 31.2 are:

• Correction to Greek template
• Romanian template available
• Loop driver improvements for multiple devices with the same address and single point polling.
The main feature in Version 31.1 was:

• Version 31.1 Consys was updated to provide compatibility with the ‘Zettler Digital Enrollment mobile
application’ device programming app. Data is exchanged between Consys and the app via new Import and
Export menu items in the File menu.
The main features in Version 31.0 were:

• Ability to connect a PFI80x panel to the network via COM3 (Also in Version 30.95 which was a limited
release)
• Multi-Tone support in the Italian template
• Support for 855 and 835 series of detectors.
• Support for the P82AVB open class addressable sounder beacon base
• Improved simulation options
NOTE:
Page 1 of 45
Registered Company: Tyco Fire & Security GmbH Registered Office: Victor von Bruns-Strasse 21, 8212 Neuhausen am Rheinfall Switzerland
TIB 1211
At the time of Version 31.4 release there is not a release of TXG that is fully compatible.
Version 31.x will be the last major version that supports the CPU800.
There was no Zettler Version 31.3 release.
Version 3.4 GUI was a limited release, sites using that version are advised to upgrade to Version 3.5.
Version 30.95 was a limited release to provide new network options to Profile Slot Card panels. The options available
in Version 30.95 are also available in Version 31.
For compatibility with other products refer to the table at the end of this TIB.
MZXConsys Version 31.x will upgrade the format of previous templates or projects.
MZXConsys Version 31.x has been tested on Windows 10.
By default Version 31 uses MXSpeak network protocol revision 6.0. It is possible to downgrade to previous revisions
of MXSpeak, see Consys help for details.
2 Upgrading to Version 31
Projects started with previous versions do not get the latest template changes; the configuration is preserved. The
changes outlined below will only be available for projects started with Version 31 templates. Instructions on how to
upgrade existing projects are provided below.
Note: The internal format is different between Version 31.x and previous versions. The upgrade of format is a one-
way operation and is handled by MZX Consys. It is good practice to keep a copy before upgrading.
2.1 Automatic Upgrade

Automatic Upgrade does not change the cause & effect (groups and actions) in the project.
When a project which was created using an older version of MX / ZX / MZX Consys is opened in Version 31.x
Consys, it will be automatically upgraded. This involves no effort or input from the user. The automatically upgraded
project can be downloaded into a panel running Version 31.x firmware.
A project which is upgraded automatically will get many of the firmware-only changes listed in section 4 Firmware
Changes’. Each item in this section indicates if it will be available in an automatically upgraded project or not.
A project which is upgraded automatically will not get the template changes listed in section 3, ‘Changes made to the
Templates since Version 30.2’. It will also not get any template changes introduced since the version in which the
project was originally created.
For example, if a project was originally created in Version 16.0, then automatically upgraded into Version 30.0, the
cause & effect will work the same as they did in Version 16.0.
Page 2 of 45
TIB 1211
Where a template changes introduced in Version 31.x can be manually added by the user the details of how to do it
are included in the section about that change.
2.2 Manual Upgrade

If a site needs the changes listed in section 3 ‘Changes made to the Templates since Version 30.2’, or any template
changes made since the version with which the project was originally created, then the project must be upgraded
manually.
For example, if a project was originally created in Version 16.0, then you should review section 3 ‘Changes made to
the Templates since Version 30.2’, and also the corresponding sections in the TIBs of the releases between these
versions. If your site requires any of these changes, then a manual upgrade will be necessary.
Manual Upgrade is a three stage process:
2.2.1 Stage 1 – Automatic Upgrade
Open the old project in Version 31 Consys. It will be automatically upgraded.
2.2.2 Stage 2 – Create new project from Version 31 Template
Create a new project from the appropriate Version 31 template. This should be the same type of template as the
original project was based on.
For example, if a project was created using Version 16.0 Consys using the Marine template, then the new project
should be created using the Marine template supplied with Version 31.
2.2.3 Stage 3 – Copy & Paste
Open both the old, automatically upgraded project, and the new project based on the Version 31 template, at the same
time.
Copy and paste all the site-specific data from the old project to the new one. Please note that the order in which data
is copied is important. Detailed instructions for how to do this operation, and what order the data should be copied in,
can be found in the Consys Help File.
The new project will now have all the data specific to this site and it will now include the template changes listed in
section 3, Changes made to the Templates since Version . It will also include any template changes made since the
version in which it was originally created.
3 Changes made to the Templates since Version 30.2
Projects started with previous versions do not get the latest template changes; the configuration is preserved. The
changes outlined below will only be available for projects started with Version 31 templates. Instructions on how to
upgrade existing projects are provided later in this document.
Page 3 of 45
TIB 1211
3.1 All Templates
3.1.1 GUI Pseudo Points 1 and 2 have been updated so their functionality is fixed
All GUI Pseudo points should have fixed functionality, i.e. they are either disabled or they are enabled and their
associated functionality fixed to line up with the text as displayed by the GUI.
Prior to Version 30.0 it was possible to change the configuration for GUI Pseudo Point 1 or 2 in a way which was
incompatible with the GUI text, i.e. it was possible to enable the point and assign functionality that conflicted with the
text as displayed by the GUI.
This incorrect flexibility has been removed in Version 31.0 of the templates (projects created with templates older
than Version 31.0 will not be corrected on upgrade).
[Corrected in Version 31.0]
3.1.2 Group 0018 names have been updated

In Version 30.0 the name of group 0018 was inadvertently changed for a number of languages, e.g. Germany where
'#2-Mld.abh / aut.Rückst.' was changed to 'Detektoralarm - Zeitg ZDK', these have now been reverted to their original
names.
3.1.3 Aux Mains fault to Aux PSU Fault

The Aux Mains fault groups have been renamed to Aux PSU fault groups.
The event logged by the group is now PSU FAILURE, was MAINS FAULT.
This group structure is used by remote GUI units to report power problems.
[Changed in Version 31.0]
3.1.4 Updates for Connected Services Gateway.

The Version 31.4 templates have additions to provide compatibility with the Connected Services Gateway card (CSG)
for use as a fire signalling unit. See more details with the Consys entry in this TIB.
[Added in Version 31.4]
3.2 German Templates

3.2.1 Corrected Fire Reset from Fire Brigade Panel
The group used for Fire Reset on the Fire Brigade Panel is 240. This group was missing an action to activate group
986 to reset VESDA units.
This action has been added in the templates released with Version 31.
It can be added manually for projects based on older templates.
Page 4 of 45
TIB 1211
3.3 Swiss Template

3.3.1 Alarm Acknowledgement with GUI
If the project is based on a Swiss Version 31 template and used with Version 3.3 GUI (or later) then the Alarm
Acknowledge button will displayed on the GUI after log-in.
The feature is not available on upgraded projects.
3.4 Austria Template

3.4.1 PR1D2 RBus Repeater is now available in the Austria Template
Prior to Version 31.0 the PR1D2 RBus Repeater was not available for the Austria template.
This omission has been addressed in Version 31.0 of the Austria template (upgraded projects will still not have the
PR1D2 available).
Page 5 of 45
TIB 1211
3.5 All Dual Language Templates

3.5.1 Changed default language settings on dual language templates
The default was changed for dual language templates so that "Fix language" is not checked by default. This will
enable the language UI selectable in Consys.
[Updated in Version 31.2]
3.6 Greek Template

The code page setting in the Greek template issued with Version 31.2 has been corrected.
3.7 Romanian template.

The installer now includes a template for Romania.
4 Firmware Changes
The following changes have been made to the panel firmware since Version 30.2:
When Version 31.4 was released, Version 30.2 was the most recent full release of Version 30.x
This section covers the changes in Versions 31.0 to Version 31.4
4.1 New Features

All of the items in this section are available on upgraded projects unless specified.
4.1.1 Added new Open Class sounder/beacon P82AVB

Version 31 offers support for the P82AVB open class sounder beacon.
This device is a replacement for the LPSB3000.
4.1.2 Support for 855 and 835 detectors

Version 31 supports the 855 and 835 detector ranges. They are compatible replacements for previous generation
devices.
Page 6 of 45
TIB 1211
For example if an 830PH failed, it could be replaced with a suitably addressed 835PH without the need to update the
configuration.
They do not offer IR communication.
More details are given in the Consys Devices section of this TIB, section 5.5.1
The devices are available on upgraded projects. Upgraded projects will not have the Device Uses, so will not support
autoconfiguration of these devices. Projects started with Version 31 templates will support autoconfiguration of these
devices.
If using 835 or 855 with a TXG system refer to section 9.7.2 of this TIB.
4.1.3 Support for Connected Services Gateway

Panel firmware Version 31.4 has additions to support the CSG if configured as specified in the Consys section of this
TIB.
4.2 Improvements and Corrections

4.2.1 Loop selection in Walk test dialog (OCM/CUI)
The walk test screen has been improved; it now only offers available loops on the selected panel.
4.2.2 Improvement when working with USB start-up configuration

Prior to Version 31.0 if the USB Start Up configuration was used to set up the panel, within a short period of time a
System Fault would be raised.
This was due to there being no communications from the panel to the FIM/PFI processor.
From Version 31.0 the panel now runs a basic communication service with the FIM/PFI processor, thus preventing it
from forcing a System Fault.
4.2.3 Loop limit for dual language projects has been removed
Prior to Version 31.0 it was not possible to add more than 16 loops to a panel when using a dual language project.
From Version 31.0 this limit has been removed.
Any GUIs on such a project need to be Version 3.3 or later.
Page 7 of 45
TIB 1211
4.2.4 Improved OCM/CUI menus on single panel networks

Prior to Version 31.0 any project which consisted of a single panel on the network with only non-panels, then some
OCM/CUI menus, e.g. ‘Autoconfigure’ and ‘Loop Point Counters’, would always fail with a ‘No Response’ error
message.
4.2.5 Improvements Simulating FBI800

Prior to Version 31.0, when a project configured with an FBI800 is simulated in Checker the panel will still raise a
comms fault if the configured FBI800 is not present. This should not happen as the panel is simulating the device.
This problem has been corrected in Version 31.0 of the panel firmware and works with all projects, including those
upgraded from earlier versions.
4.2.6 Supervised Inputs on a PFI/FIM, when inverted, raise spurious faults
Prior to Version 31.0, when a Supervised Input on a PFI or FIM was configured to be inverted the panel could raise
spurious, and unwanted, faults on that input.
This problem has been corrected in Version 31.0 of the Panel firmware and works with all projects, including those
upgraded from earlier versions.
4.2.7 VID/VAD Sounders Checksum Test

Prior to Version 31.0 a daily check was made on the VID/VAD Sounders. It has subsequently been found that this is
unnecessary and may cause spurious faults – CHECKSUM FAULT.
From Version 31.0 and later this check is no longer invoked by the Panel.
This will also apply to projects upgraded into Version 31.
[Update in Version 31.0]
4.2.8 Protection Fault LED now turns off when all Protection Faults are cleared
Prior to Version 31.0 there could be occasions when, although all Protection Faults have cleared, the Protection Fault
LED remains active (this problem first appeared in Version 25.0). The issue occurred mostly when the panel was busy
dealing with a burst of Events.
This problem has now been corrected.
4.2.9 Panel no longer fails with ‘Loop Polling Error’ for ‘Multiple Devices’
The panel firmware Version 30 for the Profile Flexible Panel introduced a potential problem when two or more loop
devices on the same loop were programmed with the same address.
Page 8 of 45
TIB 1211
The problem meant that a loop polling error could be triggered which eventually results in the panel restarting,
whereupon the whole cycle repeats.
This problem has been corrected in Version 31.2 of the panel firmware and will apply to upgraded projects.
Multiple devices detection is run on panel power up (panel reboot).
During panel initialisation the loops are scanned for multiple devices. If more than one device on a loop address is
found, a Multiple Devices fault is triggered. Once triggered, the fault can be cleared only by system reset (panel
reboot).
If there are more than two devices on a single address, the panel may trigger No Response fault from affected address
rather than the Multiple Devices fault.
When the panel is running and another device (or more) is added on the loop with an incorrectly programmed address
conflicting with a device already present on the loop, the panel will report No Response fault. As soon as the
conflicting device(s) is removed, No Response fault should be cleared.
4.2.10 ‘Single Address Polling’ no longer raises ‘unconfigured device’

In Version 31.0 of the Panel firmware an issue was introduced such that if ‘Single Address Polling’ is run when ‘Poll
Addr 255’ is enabled, a ‘phantom’ unconfigured device fault is incorrectly raised on the Loop.
This problem has been corrected in Version 31.2 of the Panel firmware and applies to both new and upgraded projects.
4.2.11 Simulation of FBI (Germany) no longer raises an ‘INITIALISE ERROR’ Fault

The simulation of an FBI unit from within Consys was never implemented correctly which meant an ‘INITIALISE
ERROR’ was always raised at the start of simulation.
This problem has been corrected in Version 31.2 of the PC Panel Simulator (which comes with Consys) and will also
work with upgraded projects.
4.2.12 CUI/OCM users can now select a specific Loop for Walk Test
In Version 31.0 of the Panel firmware an issue was introduced that meant it was not possible for a user to select a
specific Loop for Walk Test if the Panel was not part of a network of Panels (the Loop selection was stuck on ‘All’).
This problem has been corrected in Version 31.2 of the Panel firmware and applies to both new and upgraded projects.
Page 9 of 45
TIB 1211
4.2.13 Added support for a new NAND flash

There is a new device on the miniCPU board (used on the CPU801 and PFI800) that is not compatible with previous
releases of panel software. The lower level bootrom on the new boards correctly prevents the existing, incompatible,
software being installed on the newer boards.
For an overview of panel releases to support the new hardware see TIB 2013.
The new hardware units can be identified with the sticker as below.
PHOTO
Build Date of MiniCPU

The mini-CPU board that has the changed components is located on the CPU801 and PFI800 boards.
It is a slightly raised board with solder connections on all 4 edges.
All units have a sticker on this board with hardware build information, next to a QRCode.
The text on the sticker contains build date information, plus some stickers have board revision details.
In 2020 the date format changed from 8 to 9 digits.
Older method, 8 digits

ywwd (and then 4 digit of serial number)
y = last digit of the year
ww = number of week
d = number of day in week (1= Monday, 2 = Tuesday,… ,7= Sunday)
Newer method, 9 digits

yywwd (and then 4 digit of serial number)
yy = 2 last digits of the year
ww = number of week
d = number of day in week (1= Monday, 2 = Tuesday,… ,7= Sunday)
[Change added in Version 31.4]
4.2.14 Outputs of Sounders / Beacons now driven correctly after a device power up
Since Version 30.0 there are two scenarios where the output of Sounder / Beacons may not be put into the correct state
on a power up of the device.
1. A ‘Panel Restart’ where the Sounder / Beacon has been immediately activated at the beginning of the restart.
Page 10 of 45
TIB 1211
2. A ‘Loop Restart’ after the loop had been shut down (affects single address Sounder/Beacons only).
The issue which caused the above problems has now been corrected in Version 31.4
Burning Issue: ISS-2022-02128
4.2.15 Tones of Sounders now configured correctly after a device power up

An issue was introduced in Version 31.0 whereby a busy loop would occasionally prevent one or more random tonal
sounder devices being configured correctly, resulting in the wrong tone being used when activated. This can occur on
Panel start up, but is especially true where a loop containing tonal sounders is shutdown and restarted.
The issue which caused the above problem has now been corrected in Version 31.4
Burning Issue: ISS-2023-02345.
4.2.16 Improved Handling of Callpoints on Noisy Loops

On particularly noisy loops callpoint activation could be delayed. This has been corrected.
The panel’s susceptibility to noise delaying callpoints was introduced in Version 31.0 and corrected in Version 31.4.
[Improvement in Version 31.4]
4.2.17 The user can no longer shut down a loop whilst it is initialising
In all versions of the panel, up to and including Version 31.2, it was possible for the user to invoke a loop shut down
even though the loop was still in the process of initialising itself. Whilst this is not an issue on single panel project, as
it is not possible for a user to log on to a User Interface during the first 2 minutes of the Panel powering up, on a
network project it is feasible for one of the panels to be restarted when the user is already logged on to another panel
on the network.
The panel has now been updated such that it will not accept requests to shut down one of its loops whilst that loop is
running its initialisation, instead it will decline the request and respond with busy.
This new behaviour has been added in Version 31.4
Page 11 of 45
TIB 1211
5 Consys
5.1 New Features
5.1.1 Addressing Loop Devices with App – Digital Enrollment
From version 31.1 Consys provides compatibility with the ‘Zettler Digital Enrollment mobile application’ device
programming app. Data is exchanged between Consys and the app via new Import and Export menu items in the File
menu.
When used with the app, Consys now offers a new approach in assigning addresses to loop devices.
The Consys help file has been updated with suggested work flows for addressing devices with the app.
The Consys help file covers the interaction between Consys and the app and the panel. Device addressing at the panel
user interface is covered in the appropriate panel guide.
The smart phone app is available for iOS and Android phones.
The training videos are available via the App.
5.1.2 Profile slot card panels can connect to the network via COM3
The ability to use PFI800 COM3 as a network port was added in Version 30.95 (which was a limited release).
Support is now offered for the TLI800EN network cards with PROFILE slot card panels. The card connects to panel
COM3. It is possible to mix TLI800EN and PNI800 cards on the same network.
It is possible to have a network of two nodes without network cards. This is possible if the system is two panels and
the panels are close-coupled, or a single panel plus a head-end system. The nodes will communicate via the COM3
link used for TLI800EN cards. A NULL modem cable will be required. The TLI800EN cards will need to be in the
configuration.
A new SKU has been added - 557.202.808 N-EXP, Network Expansion Kit
Please check availability of the kit.
The kit includes

• Instructions on how to mount the TLI800EN inside a CUI panel
• Cable to connect panel COM3 to the TLI800EN card
Page 12 of 45
TIB 1211
• COM3 to COM3 cable to connect two panels of the same type (PFI to PFI, or CPU80x to CPU80x)
• The required power cable assembly for the TLI800EN
• Support plate
• Necessary screws and fixings
Description of cables
Panel COM3 to panel COM3 of the same panel 557.202.808 N-EXP

family without network cards
Network Expansion Kit
(PFI to PFI, or FIM to FIM)
Panel COM3 to panel COM3 without network Contact Product Support

cards
(PFI to FIM)
FIM based panel using COM3 connected Cable supplied with TLI800EN
TLI800EN
PFI based panel using COM3 to TLI800EN 557.202.808 N-EXP

Network Expansion Kit
FIM based panel directly connected to non-panel Standard download lead with a null
node such as a head-end system, without network modem adapter
cards.
Configured as COM3 TLI800EN networking
PFI based panel directly connected to non-panel Standard download lead, no null
node such as a head-end system, without network modem adapter needed
cards.
Configured as COM3 TLI800EN networking
5.1.3 Multi-Tone
Projects based on the Italian Version 31 templates offer an alarm multi-tone feature.
The feature is also an option if the project is based on most Version 31.2 templates.
The option is selected from the new ‘Multi-Tone’ tab on the System Overview dialog.
If selected, it allows different alarm levels to use different tones. The device mode will be shown as ‘Using Multi-
Tone Sounders’ on the Points dialog.
Page 13 of 45
TIB 1211
The feature works by mapping the requested point state (on/pulsing) to a tone. For example, if the configuration
requests a compatible sounder is set to pulse, this is mapped to tone A, if set on, to tone B.
Due to the time needed to switch the tones within the devices, at the time of version 31 release, the maximum
recommended multi-tone devices per loop is 40.
[Multi-tone added at Version 31.0 for the Italian template, available most templates Version 31.2]
5.1.4 Support for the Connected Services Gateway Card (CSG)

Version 31.4 Consys when used with a Version 31.4 template offers support for the Connected Services
Gateway cards as signalling units. Version 31.4 panel firmware is required to support the unit.
The card connects to the panel on the LNet (Ethernet). It provides panel state information to remote
services including the SafeLinc web interface and app.
Details on how to configure the card are covered in the help file with Consys Version 31.4.
If Version 31.4 is used with an upgraded project or a project based on an earlier Version 31.x template the
CSG options will not be available.
If the base template is not Version 31.4 it is possible to use a CSG as interface to the Safelinc products
without signalling.
[Supported added in Version 31.4]
5.1.5 Links to Datasheets

Many menus and dialogs have been extended to offer links to product information documents held on the
Zettler website.
An account on the website is required to access some of the documents.
[Feature added Version 31.4]
5.1.6 Auto Renumber User Groups

The context menu on the group edit screen now offers ‘auto renumber’. This feature renumbers user groups to the
higher group numbers. This process can be useful in the process of moving the functionality of an upgraded project to
the latest template.
Page 14 of 45
TIB 1211
5.2 Changed features

5.2.1 Template Events Increased – User Events Moved
User events are now from 501 to 599, previously they were from 401 to 499. User events are moved to the new
number range and the actions adjusted as part of the upgrade process.
Prior to Change After Change
Event Type Range Range
Template 1 - 400 1 - 500
User 401 - 499 501 - 599
5.2.2 Panel Point Information

The Panel Point Information scan available from the Transfer menu has been updated to allow the user to scan an
individual loop.
[Added Version 31.0]
5.2.3 CUI panels can work on a network where panels have more than 16 loops
The restriction stopping panels with a Colour User Interface (CUI) being configured on a network where any panel
had more than 16 loops has been removed.
[Restriction removed in Version 31.0]
5.2.4 Project Compare ignores ‘Designer Pro’ only properties

When loop points are being compared all the properties that are for ‘Designer Pro’ only, are ignored. For example, if
the points have different SKUs (one for the Red variant of the device and one for the White variant) then Project
Compare will not display this property which is meaningless to the panel.
5.2.5 Slot Card Availability

The Pro415S Lite, Pro415D Lite and Pro415 CH Lite panels can now support a single PLX800 card. The panel can
support two stacked cards, plus an optional fuse board. See panel documentation for fitting instructions.
5.2.6 Improvements in Simulation

Network simulation
Page 15 of 45
TIB 1211
Consys now allows the simulation of up-to 4 panels from a network configuration.
The first panel selected is assigned an instance of checker.
The other panels share the other instance of Checker.
Simulation of up to two GUIs

It is now possible to run a simulation of two panels both having a GUI on LNet1.
Simulations using PC GUI with Consys Version 31 requires PC GUI version 3.2 or later.
Fixes
The following problems in simulation have been fixed:
- network simulation did not work after a ‘Download and Simulate’ had been performed on any
single panel
- simulation of a single panel did not work for PFI800 based panels when the project had more than
one panel
These items have been fixed.
As with real hardware, if the project uses User Events, then Version 3.5 is required.
[Changes in Version 31.0]
5.2.7 Download Mods Improvements

The logic for ‘download mods’ has been improved. This gives a quicker transfer after most configuration updates.
[Improvement added in Version 31.4]
5.3 Corrections
5.3.1 Point Regions ‘RBus Emergency Mode Display’ no longer offered for CPU801
Prior to Version 31.0 the Point Regions ‘RBus Emergency Mode Display’ setting was incorrectly offered for Panels
based on the CPU801, but this facility is unavailable on this hardware.
This has now been corrected in Version 31.0 so that only when the Panel is PFI based will the option be offered when
configuring GUIs on the LNet.
5.3.2 Point Overview Dialog – point selection bugs fixed

The problems with keyboard navigation on the Point Overview dialog have been corrected.
Page 16 of 45
TIB 1211
This includes use of Shift+PageUp, Shift+Arrow-Up, Shift+PageDown and Shift+Arrow-Down
5.3.3 Correction on ‘Network Overview’

A problem existed in the ‘Network Overview’ dialog if a panel was converted to a non-panel node, but the
change was cancelled.
[This has been fixed in Version 31.0]
5.3.4 ‘Replace Devices’ Corrections

An assortment of problems with the ‘Replace Device’ feature have been fixed:
• In some situations, ‘Replace Device’ on the second loop of a pair of shared power loops did not offer full
functionality.
• It was possible to corrupt the point data if the (X) option or the Cancel button was used.
• If the 801PC was selected, the Replace Device option gave invalid entries for new device types.
5.3.5 Panel Point Information handling disabled channels

After a Scan, split devices with disabled channels are shown. However, the panel does not provide any information
about the disabled channels. So, Update cannot work with these devices. The Report tells users ‘Split device with
disabled channels not processed’.
5.3.6 Sounder Beacon splitting loses Class Change

Previously when a VID/VAD was split over two points, the day mode on the primary channel was corrupted. This has
been fixed.
Note, when a VID/VAD gets split the Class Change gets set to the night setting.
5.3.7 Changes made to ‘Bell Map Control’ Group Actions are now saved
Since Version 17.0, any change made to the ‘Priority’ setting of a ‘Bell Map Control’ Group Action was missed by
the Group Dialog and thus was not saved to the Project. This meant when the configuration was downloaded the Panel
would not behave fully as expected.
This problem has been corrected in Version 31.2 of Consys and will work in upgraded projects.
5.3.8 TLI Network Simulation of a Profile Flexible panel is now possible
Version 30.95 was created to allow the use of TLI (COM3) for Network configurations on Profile Flexible panels
(panels using the PFI800).
Page 17 of 45
TIB 1211
Consys simulation support for this set up was not fully updated to match, thus simulated Panels would not
communicate with each other.
This problem has been corrected in Version 31.2 of the PC Panel Simulator (which comes with Consys) and also
works with upgraded projects.
5.3.9 Simulation of a single panel from a networked configuration stops functioning

An issue was introduced into v30.0 of the PC Panel Simulator whereby the simulation of a single panel from a
network project eventually stopped working correctly (this occurred in some templates more quickly than it did in
others).
This problem has been corrected in Version 31.2 of the PC Panel Simulator (which comes with Consys) and also
works with upgraded projects.
5.3.10 Corrections to Point Scan

Adding points from a Point Scan did not work correctly for dual language projects, the second language label was not
completed.
The scan is offered per loop, in Versions 31.0 and 31.1, loop 32 was not available. This has been corrected.
5.3.11 ‘Full Upload’ Bug with PFI80x panels that use COM3 for the network
There was a bug that caused PFI80x panels which were configured to use COM3 as the network port, to be ‘fully
uploaded’ with a printer on COM3.
5.3.12 ‘Logical Address’ displayed in project with no Logical Addressing

In projects based on templates which did not allow Logical Addressing…On the second loop on a set of paired loops
(shared power loops panel) the ‘Point Overview’ dialog was displaying a ‘Logical Address’ column.
5.3.13 Point Overview – Group setting screen corruption

The problems only existed:
• When the Restricted Group List was being used.
• When jumping between input and out device types.
Page 18 of 45
TIB 1211
When up and down arrowing between points of selecting points with mouse click the points Group setting displayed
incorrectly on Point Overview.
5.3.14 Fix for settings when changing the set of devices for Device Uses
When editing Device Uses it is possible to select a set of data to ‘use as default for device’. Previously this selection
could be lost if other edits were made to Device Uses.
This has been corrected.
5.4 Device Changes
5.4.1 Support for 855 and 835 devices

Version 31 supports the 855 and 835 devices. These are drop-in replacements for the 850 and 830 series devices.
The 855 and 835 devices do not have the IR interface.
Detector SKU Detector SKU
855PH 516.855.051 835PH 516.835.051
855P 516.855.052 835P 516.835.052
855H 516.855.053 835H 516.835.053
855PC 516.855.504 835PC 516.835.054

5.4.2 Support for P82AVB
The P82AVB open class VAD sounder beacon base, 576.080.015, is supported by Version 31.
5.5 Patches
Page 19 of 45
TIB 1211
5.5.1 Patch for Emergency alarm processing

A patch has been added to correct a previous template problem in the processing of alarms in Emergency Mode.
When the alarm was processed, depending on the alarm point, it could have been reported twice.
5.6 Project Checks

5.6.1 Insecure passcodes
The logic for project check 2151 has been improved. It is now reported at the correct level, site wide or per panel.
5.6.2 Check for Minerva Bridge configuration.

W2136 : The configuration has a Minerva Bridge but none of the panels has a text based user interface. Minerva VFP
is not available on GUIs.
The text for the project check has been updated. The check logic remains the same.
5.6.3 Check on Evacuate Level Bellmap settings

W2159: (Panel <panel>) The Bellmap settings for Zone <zone number> does not target evacuate sounders in the
same zone with ‘Switch On’. This can lead to unexpected results, see help file.
This is a new project check.

Some templates use special processing to ensure the sounders in the zone of origin are switched on quickly for
evacuate level fires. The check is raised if the special processing is enabled, but the bellmap would switch the same
sounders to a different state. A more detailed explanation is in the Consys help file.
5.6.4 Network Checks

Two new network related checks were added.
E1141 : (Panel <panel>) is a networked Profile Flexible panel but has both PNI800 and a TLI800 configured.
I3027: There are issues to consider when a PFI80x panel uses COM3 as a ‘network port’ – refer to the Help
5.6.5 Check on zonal LED board configuration

New project checks:
W2160 : (Panel <Panel Number>) The zonal display on <unit> has a mixture of groups assigned
W2160 : (Panel <Panel Number>) The panel uses different types of fault display cards.
Page 20 of 45
TIB 1211
Different zonal display configurations are available. These project checks highlight unexpected mixtures of board
types or mixtures of groups on a board.
5.6.6 Open Loop Polling

The open loop polling disabled reminder was only displayed if there were points on the loop, now it is always
reported.
5.6.7 Incompatible use of non-addressable bases.

New project checks:
E1147 : Device Use <Use Number> for device <device type> is configured with a sounder or relay base.
E1147 : (Panel <number>) Loop <Loop ID>, Address <address> the device <device type> is configured with a
sounder or relay base.
These two new error level checks test for the presence of a non-addressable sounder or relay base on an 850 or 855
sensor. This combination will not work correctly as the base conflicts with the internal isolator circuit.
TIB 1053 was issued informing users this combination should not be used. If the use of a non-addressable base is
required, then the equivalent 830 / 835 series device should be used.
At version 31 these checks were changed to error level, previously the information was given as Warning 2095.
5.6.8 Multi-Tone
W2164 : (Panel <Panel Number>) Loop <Loop id> has <number> Multi-Tone devices. The maximum recommended
is <max>.
The Multi-Tone sounder functionality was added in Version 31 on the Italian template. This warning indicates if the
number of devices on the loop may lead to reduced response time.
5.7 Help System

The Consys Help system has been updated to match the features provided with Version 31.4. A brief overview with
links is provided in the ‘New for Version 31.4’ section.
6 Digital Enrollment
Version 31.1 provided compatibility with the ‘Zettler Digital Enrollment mobile application’ device programming app.
Data is exchanged between Consys and the app via new Import and Export menu items in the File menu.
Page 21 of 45
TIB 1211
When used with the app, Consys now offers a new approach in assigning addresses to loop devices.
The Consys help file has been updated with suggested workflows for addressing devices with the app.
The Consys help file covers the interaction between Consys and the app and the panel. Device addressing at the panel
user interface is covered in the appropriate panel guide.
7 Profile GUI
PROFILE GUI Version 2.0 is required for use with the PROFILE Flexible panels.
PROFILE GUI Version 2.1 is required to support dual language projects that use the MINERVA Bridge.
PROFILE GUI Version 2.2 is required to support EN54-13 Loop functionality
PROFILE GUI Version 2.3 added standby emergency mode operation and provides limited Display Repeater
functionality.
PROFILE GUI Version 2.4 was released for French market only.
PROFILE GUI Version 2.5 added full Display Repeater functionality, VID/VAD support and input test information.
PROFILE GUI Version 2.6 was a Danish Market specific release.
PROFILE GUI Version 2.7 added support for new Emergency Mode features and several general fixes.
PROFILE GUI Version 3.0 general update with improvements.
PROFILE GUI Version 3.1 added Hebrew display texts and several general fixes. TIB 1079
PROFILE GUI Version 3.2 Fixes Zone Maps for network configurations. TIB 1095
PROFILE GUI Version 3.3 walk test improvements and deferred disablements. TIB 1158
PROFILE GUI Version 3.4 user event description and other general fixes. TIB 1183 – Limited Release
PROFILE GUI Version 3.5 compatibility with new hardware and general fixes TIB 1191
Version 3.2 of the GUI does not support the ‘Disablement during an alarm’ facility, this is supported from Version 3.3.
If using zone maps on the GUI in a network configuration, GUI Version 3.2 or later is required.
Version 31 handles event descriptions in a different way. If user event text is used GUI Version 3.5 is required.
At the time Version 31.2 was released it is recommended to use Version 3.5 GUI.
Version 3.4 was a limited release, sites using Version 3.4 are advised to upgrade to Version 3.5
Page 22 of 45
TIB 1211
8 Installation Program
8.1 Templates
The templates available with Version 31 are listed below.
Korean support which was available in older versions, is not available in this release.
The template for France is not included with Version 31 and although the CO_FR template provides standard EN54
functionality in French, it is not for use in France.
Market Template Name Notes
Austia AU<version>.PJT Based on VdS functionality
AU_EN_<version>.PJT Dual language, Austrian and English
Beigium BE<version>_LOG_F.PJT In French with logical addressing
BE<version>LOG_FL.PJT In Flemish with logical addressing
BE<version>_PHY_F.PJT In French with physical addressing
BE<version>PHY_FL.PJT In Flemish with physical addressing
BE<version>_PHY_E.PJT In English with physical addressing
BE_FL_F<version>L.PJT Dual Language –

French and Flemish – logical addressing
BE_FL_F<version>P.PJT Dual Language –

French and Flemish – physical addressing
BE_FL_E<version>P.PJT Dual Language –

Flemish and English – physical addressing
Chinese CI<version>_big5.pjt Chinese (Tradition Big5 encoding) requires

PROFILE GUI.
CI_EN_<version>.PJT Dual language
EX<version>_CI.PJT Export template, in English, set to Chinese

code page.
Page 23 of 45
TIB 1211
Core EN54 functionality with French text

Core EN54 CO<version>_FR.PJT
CR<version>.PJT
Croatian Based on the EN54 Core template.
CZ<version>.PJT
Czech Based on the German template with
modifications
DM<version>.PJT
Danish based on the EN54 Core template with minor
modifications.
DM_EN_<version>.PJT Danish-English dual language

NL<version>.PJT
Dutch Based on the EN54 Core template with minor
modifications
EX<version>.PJT
Export based on the EN54 Core template with
American codepage
Based on the EN54 Core template with
Finnish FI<version>_LOG.PJT
modifications
logical addressing
FI<version>.PJT physical addressing
German GE<version>.PJT Functionality required by VdS

Single language
GE<version>_ENG.PJT German-English: functionality as required by

VdS with text in English
GE_D_E_<version>.PJT Dual language – German and English
GE_D_F_<version>.PJT Dual language – German and French

GR<version>_ENG.PJT
Greek Functionally the same as the EN54 Core
template.
This template is in English but runs on a
Greek PC
HE<version>.PJT
Hebrew based on the EN54 core functionality with
minor
HU<version>.PJT
Hungarian based on the EN54 Core template with minor
Page 24 of 45
TIB 1211
Italian IT<version>_LOG.PJT Functionally based on EN54 Core template.

Offers Multi-Tone feature
Logical addressing
IT<version>_PHY.PJT As above, with physical addressing

NO<version>.PJT
Norwegian Functionally the same as the EN54 Core
template
PO<version>.PJT
Polish functionally the same as the EN54 Core
template
Portuguese PG<version>_LOG.PJT Functionally the same as the German template

with logical addressing
PG<version>_PHY.PJT Functionally based on EN54 with minor

modifications and physical addressing
Romania RO<version>.PJT Functionally is similar to the EN54 Core

template
Russian RU<version>.PJT Functionally the same as the EN54 Core

template
Based on the EN54 Core template with
Swedish SE<version>_LOG.PJT
modifications.
Logical addressing
SE<version>.PJT As above with physical addressing.

SL<version>.PJT
Slovakian Functionally the same as the Czech template
SP<version>.PJT)
Spanish Functionally the same as the EN54 Core
template with minor modifications
Swiss CH<version>_F.PJT Functionally similar to the German template.

Needs GUI 3.3 or later for Alarm
Acknowledgement.
Swiss French
CH<version>_D.PJT As above - Swiss German
CH<version>_I.PJT As above - Swiss Italian
Page 25 of 45
TIB 1211
CH_D_E_<version>.PJT Dual Language –

German and English
CH_F_E_<version>.PJT Dual Language –

French and English
CH_I_E_<version>.PJT Dual Language –

Italian and English
CH_E_D_<version>.PJT Dual Language –

English and German
TR<version>.PJT
Turkish Based on the EN54 Core template.
TR_EN_<version>.PJT Dual language - Turkish and English
UK UK<version>.PJT EN54 template for land use
Although the panel is available in all of the above languages this does not mean that all support software is also
available, for example MZXChecker and TXG. Contact Product Management for the current status.
8.2 MZXConsys Languages

Consys is available in the following languages
• English
• German
• Spanish
• Italian
• Chinese
• French
• Danish (this is a part translation. All dialogs are in English but the default names given when points are
added are in Danish)
• Finnish (this is a part translation. All dialogs are in English but the default names given when points are
added are in Finnish)
Others
• The dongle interface is provided in English, German, Spanish, Italian and French.
Page 26 of 45
TIB 1211
• MXExport is included in the installation set. It is a configuration conversion program used when configuring
AV300 systems. The export format is now available directly from MXConsys.
• Sample.csv, this file is used to show the required formatting to use when preparing data to be ‘imported’ into
MXConsys. The process is described in more detail in the Help system.
9 Compatibility Between Version 31 And Previous Versions
The file format used in the previous versions has been changed for the Version 31. If an older project is loaded into
MZX Consys Version 31 the user is asked if an upgrade is required. If required, the underlying format is updated to
match that used in Version 31. The content and functionality of the project is not changed.
The process of upgrading is detailed in the Help system.
9.1 FIM and CPU80x Based panels
Product Preferred Stock code Other Versions Comments

Version that will work
Bootrom V1.2 136.112.181 V1.1 V1.1 does not offer self-checksum which is
required for full EN54 compliance.
(CPU800) 557.202.110
Local I/O V1.0 125.112.822 N/A For FIM based panels, not panels in the
PROFILE Flexible range.
Loop Driver For upgrade contact Product Support.

(AVR)
V6.0 136.112.369 V5.8 An overview of the changes between earlier
versions of the firmware is now provided in
the MZXConsys Help File.
The Loop Driver firmware can be upgraded
using the Tyco MZX AVR Programmer,
516.800.941
Page 27 of 45
TIB 1211

TLI800EN V1.6 557.202.080 V1.4, V1.3, V1.2 Previous versions are available to download
from www.zettlerfire.com
V1.5 will work with V1.4, V1.3 or V1.2
when using MXSpeak 5.2 or below.
Each TLI800EN has the hardware option to
add two FOM800 (557.202.081) for use on
a fibre optic MZX Network
V1.6 is required for MXSpeak revision 6
(see TIB 1011)
If used in a Profile slot card panel the
expansion kit may be required.
557.202.808 N-EXP, Network Expansion
Kit
Character Set V4.0 125.112.917 V3.0, V2.0, V1.1, Version 4.0 added Greek
V1.0
557.202.108 Version 3.0 added Hebrew and corrections
for Russian
Version 2.0 added Central European and
Russian
Version 1.1 or 1.0 can be used provided the
character set required is code page 850.
The device is only required in an MPM if
used as an OCM
Page 28 of 45
TIB 1211

OCM/MPM V3.2 136.112.286 V3.0,V2.0, V1.1, Version 2.0 or above is required in OCM
V1.0 units if more than 3 are to be used on the
same panel.
Version 3.0 or above is required for
MPM800 issue 5 or above. For MPM800s
below this revision, issue 2.0 should be
used.
Version 3.1 is required for MPM800 issue 7
or above to get the functionality of real
point 22. This is required when using the
Marine IRU.
Version 3.2, Only added the French text
when the OCM/DCM has communication
fault with panel because of approvals, there
is no real requirement to upgrade to V3.2 if
you are running V3.1.
Version 3.0, 3.1 & 3.2 can be used with any
OCM revision but all new units will be
fitted with V3.2.
ZETFAS / 1.0.1 1.0 Version 1.0 processed sensor values

STI Loop card correctly but did not make the values for the
multi, optical or ion sensor available to the
Point Values screen.
In Version 1.0 in the input of the LAV was
in fault the output channel was also reported
as faulty.
Version 1.0.1 corrects both of the problems
reported above.
NOTE: The panel firmware only reports the
most significant 2 digits in the software
Versions screen. The full 3 part number is
given in the report.
Page 29 of 45
TIB 1211
9.2 PFI800 based panels

PROFILE 3.5 N/A From Consys Version 3.4 provides compatibility with
GUI Version 31, PC Event Message display, see TIB 1183 -
GUI 3.2 or later is Limited release
required for
Version 3.5 general fixes and compatibility
simulations.
with new hardware, see TIB1191.
Not all panel versions and GUI versions are
Versions before fully compatible. For details see section 7of
3.5 are not this document and GUI 3.5 TIB 1191.)
recommended.
PLX800 1.12 557.202.842 1.11 PROFILE Flexible loop Expansion card

Version 1.3 includes the EN54-13 support
for the Loop.
Versions 1.3 and 1.4 are compatible with
panel firmware V27.0 onwards, but not
Version 26.x
Version 1.8 bug fixes for emergency mode.
More information in PFI/PLX1.8 TIB 1038.
Version 1.9 supports VADs in emergency
mode. More information in PFI/PLX1.9
TIB 1048
Version 1.11 fix for start-up problems with
noisy loops. TIB 1060
Version 1.12 for improved performance
during a loop wire to Ground fault.
Page 30 of 45
TIB 1211

PNI800 1.8 557.202.844 PROFILE Flexible network card

Each PNI800 has the hardware option to add
two FOM800 (557.202.081) for use on a
fibre optic MZX Network
V1.6 is the first full release of the software.
(see TIB 1010)
V1.7 adds compatibility with the FBI800
card.
Version 1.7 is required if the panel has an
FBI800 in the configuration.
Version 1.8 offers star topology. See
TIB1062.
PCH800 1.0 PROFILE Flexible charger card
PFI800 1.12 1.9 Version 1.3 includes the EN54-13 support

for the Loop.
Local I/O
Versions 1.3 and 1.4 are compatible with
panel firmware V27.0 onwards but not with
Versions 26.x
Version 1.8 bug fixes for emergency mode.
More information in PFI/PLX1.8 TIB 1038.
Version 1.9 supports VADs in emergency
mode. More information in PFI/PLX1.9 TIB
1048
Version 1.11 fix for start-up problems with
noisy loops. TIB 1060
Version 1.12 for improved performance
during a loop wire to Ground fault.
Page 31 of 45
TIB 1211

Display 3.5 125-685-108 2.3, 2.7, Version 2.3 was the first version of the GUI
Repeater to offer the Display Repeater option. It has a
3.0, 3.1, 3.2
shared software with the GUI.
PR1D2
3.3
See TIB 1032 for details
It is
Version 2.5 remaps the points which are
recommended to
then compatible with Version 28.x
use Version 3.5
templates.
See TIB 1040 for details.
Version 2.7 provides general bug fixes. TIB
1058
Version 3.0 General update with
improvements. See TIB 1066
Version 3.1 Hebrew support and general
update with improvements. See TIB 1079
Version 3.2 provides support for Logical
Zones, for full list see TIB 1095
Version 3.3 improved internal zonal
displays, see TIB 1158
Version 3.4. TIB 1183 – Limited release
Version 3.5 TIB 1191
FBI800 2.0 1.1 The FBI800 is a slot card for PROFILE

Flexible panels.
It requires the use of template Version 28.1
or later. If used on a network, PNI800
Version 1.7 or higher is required.
If used with the Czech or Slovak template
version 28.6 or later required.
Version 2.0 see TIB 1160
PR1DF 2.4 The PR1DF is a variant of the GUI that

offers a log repeater option for the French
Market.
Version 2.4 firmware is required.
Page 32 of 45
TIB 1211
9.3 Networks

TXG 7.16F7 7.16A Version 7.16A only supports MX Speak 5.2

and earlier
And later
Version 7.16B was never launched
7.16F7
does not Version 7.16C adds the support for MX
support the Speak 6.0 and PROFILE Flexible Panels
835 or 855
Version 7.16D support for Windows 10 and
devices.
Windows Server 2016. See TIB1056
Version 7.16F6 support for VID/VAD
devices. See TIB1109
Version 7.16F7 See TIB 1133
7.16F7 does not support the new devices
added in Version 31.
BACnet 3.0 2.02, 2.03, 2.05 For further information, see the TIB of
Interface MZX BACnet Interface version 2.03
Version 2.04 moved the system to new
hardware. This version should not be used,
upgrade to 2.05.
Version 2.05 addresses a number of known
issues found in 2.04. TIB 1025
Version 3.0 adds support for MX Speak 6.0
and PROFILE Flexible Panels. TIB 1065
CCU3/C- V5.05 557.202.046 V3.08, V3.10, MZX to ModBus interface.

MXMB V4.0, V4.20
Version 4.20 will only work with MX Speak
Version 3.0.
Version 5.05 adds support, up to MX Speak
6.0 and PROFILE Flexible Panels.
Page 33 of 45
TIB 1211

CCU3/C- V4.05 557.202.120 3.01, V4.4 This is a kit with 2 part numbers used to
MXBRIDGE identify either a deep or shallow battery
(17A/H)
housing.
557.202.121
It is used on a shared network with
(38A/H) MINERVA panels.
Both these Versions of the MX Minerva
Bridge will only work with MX Speak
Version 3.0
MX Graph N/A N/A None MXGraph is no longer supported.

TXG is the preferred head-end system.
ZX Bridge N/A N/A None ZX Bridge is no longer supported.
Page 34 of 45
TIB 1211
9.4 Other

Designer Pro 31.4 31.0 The product design and ordering system
compatible with Version 31 is Designer Pro.
Version 31.0 TIB 1155
Version 31.4 TIB xxxx
MZX 11.2 Version 11.2 adds support for FV421i, and

Designer ™ Chinese template devices added in Consys
See Note
Version 28.6. TIB 1080.
NOTE:
Version 11.2 is the final release of
MZXDesigner. All new functionality added
by Version 30.0 and later is now only
supported by ‘Designer Pro’.
MZXChecker 5.0 All previous The Consys Help File describes the features
releases. added in each MZXChecker release
See note
Version 3.1 is required to support network
simulation from MZXConsys.
Version 4.0 added multiple panel support,
capture panel log and highlight zones.
Version 4.2 added improvements to
scripting and panel log capture
Version 5.0 adds support for MX Speak 6.0
and PROFILE Flexible Panels.
Page 35 of 45
TIB 1211

MZX Data 4.0 NOTE:

Logger
See note At the time of Version 31.0 release there is
no version of MZX Data Logger that
supports the MXSpeak 6 protocol which is
required for larger PROFILE Flexible panel
projects
Check for future MZX Data Logger TIBs.
Data Logger Version 4.0 – TIB 956
LCD Repeater 557.200.024 N/A Works with MX Version 2 firmware and

onwards, it requires the project to be based
LCD800 Code for
upon the UK template. The printer output
complete
should be set to 80 characters and 4800
LCD Repeater
baud.
Documentation 17A-02-LCD
LCD800 V2.1 557.200.028 The updated LCD800 firmware requires the

unit to be configured as an ‘LCD Repeater’.
MK II Code for
complete The Version relates to the firmware in the
LCD Repeater LCD800 device.
LCD800 V2.1 557.200.030 None This device has the same firmware as the
Code for item above but is fitted with a different LCD
MK II WE
complete driver module to enable handling of
LCD Repeater extended characters.
It will work on the UK and other European
templates using codepage 850.
LCD820 3.24 557.200.302 None Repeater for France
MX Remote V2.0 V1.0 Note: Version 1.0 has the bitmap images
with the LEDs in pre-Version 14.0 locations
See note.
(without Protection Equipment Monitoring).
Version 2.0 MXRemote offers the ability to
select between sets of LEDs allocations.
NOTE: MXRemote cannot be used with
MXSpeak revision 6 which is required for
some PROFILE Flexible configurations.
Page 36 of 45
TIB 1211

Austrian Fire 1.2 N/A N/A This item is under the control of an external
Brigade Panel company from Germany called Schraner.
On the FBP LCD at start-up it should report
“TEEXPE1B”.
850EMT 1.8 All previous* Version 1.1 provides support for split
devices and functional bases.
V1.2 minor fixes
V1.3 and V1.4 language releases.
V1.5 adds support for the new range of
sounder, and sounder beacon devices.
V1.6 added Italian and Spanish as user
languages and a few minor fixes.
V1.7.1 various updates.
V1.7.4 adds support for Autocall devices.
V1.8 added improved Autocall support,
corrections for type identification and
updates for P80AVR and P85AVR devices,
and fixes to device type identification
*The commissioning mode is not
compatible with the panel loop numbering
method, 1 to 32, and is only compatible with
the panel loop letters, A to H.
9.5 Associated TIBs

The table below lists the latest revision from each major release and the associated TIB.
This table was checked at the release of Version 31.0
Version Associated TIBs

(UK TIB number / German TIB Number)
1.7 V1.0 (423), V1.2 (445), V1.3 (456), V1.6 (518/D-0307), V1.7 (550/D-0312)
V1.7 supersedes and replaces all previous Version 1 firmware, see Correcting Action Bulletin 138
Issue 2.
Page 37 of 45
TIB 1211

2.7 V2.1 (486), V2.2 (501),V2.3 (505), V2.7 (551/D-0313)

V2.7 supersedes and replaces all previous Version 2 firmware, see Correcting Action Bulletin 138
Issue 2
3.2 V3.0 (511/D-0303),V3.1(520), V3.2(552/D-0314),

V3.2. supersedes and replaces all previous Version 2 firmware, see Correcting Action Bulletin 138
Issue 2
V3.3 was a limited release for Korea.
4.1 V4.1(591)
5.1 V5.0 (645/D-0404),V5.1(666/D-0408)
6.5 V6.0 (726/D-0412), V6.1(754) Russian Templates, V6.1(763) Hebrew templates,

V6.2 (788/D-0503),
Versions 6.3, 6.7, 6.8 and 6.9 were special for individual sites.
V6.5 (811/D-0510),
V6.6 – Firmware only, limited release.
7.0 V7.0 (809/D-0509) – Limited release to support the Zetfas loop card.
8.2 V8.0 (812), V8.1(817/D-0603),

V8.2 (874) firmware only release, correction for SAM800 and SAB800 devices.
9.0 V9.0 – limited release for France and Austria.
10.1 V10.0 (841/D-0712), V10.1(851/D-0724)
11.0 V11.0 (850/D-0719)
12.1 V12.0 (856/D-0801), V12.1(862/D-0807)
13.0 V13.0 (859) – limited release for the French market.
14.0 V14.0 (866/D-0812)
15.0 V15.0 (869/D-0815),

V15.1 – Limited release to fix site network problems.
Page 38 of 45
TIB 1211

16.0 V16.0 (876)
17.0 V17.0 (882/D-0915), V17.1(896/ 896-D)
18.0 V18.0 (890) – limited release, Hong Kong Airport and France.
19.2 V19.0 (900/ 900-D)

V19.1 – Limited release with corrections for the Czech and Slovakian templates.
V19.2 (906/ 906D)
V19.3 – Limited release to correct a site problem with RIM800 devices.
V19.4 – Limited release to provide updated device LED operation.
20.5 V20.0 (909/ 909D), V20.1(919/ 919D), V20.2(926/926D)

V20.3 – Limited Release to correct RMRS functionality
V20.4 – Limited Release to correct 856 device calibration problems.
V20.5 (948/948D)
V20.6 - Limited release for Marine, printer with VDR correction
21.0 There was not an MZX release of Version 21
22.2 V22.0 (934/ 934D), V22.1 – Not released, V22.2(949/949D)

V22.5 (1215/1215D) (*)
23.2 V23.0 (943/ 943D), V23.1- A limited release, V23.2(958)
24.5 V24.0 – not released, V24.1 (954/954D), V24.2 (910), 24.3 – Not released.
V24.4 (973/973DEU)
25.9 V25.0 (991/991DEU)

V25.7 (1017/1017DEU)
V25.8 (1030/1030DEU)
V25.9 (1200/1200D) (*)
26.2 V26.0 (1001) – limited release

V26.1 (1008) – limited release
V26.2 (1018) – limited release
Page 39 of 45
TIB 1211

Version 26 supported English and Turkish only.
27.2 V27.0 (1023/1023DEU) – Limited release

V27.1 (1029/1029DEU) – Limited release
Version 27 supports a limited set of templates.
28.8 V28.0 (1034/1034DEU) – Limited release

V28.1 (1041/1041DEU)
V28.2 (1046/1046DEU)
V28.3 (1052/1052DEU)
V28.6 (1088/1088DEU)
V28.8 (1201/1201D) (*)
30.4 V30.0 (1125/1125DEU)

V30.1 (1127/1127DEU)
V30.2 (1142/1142DEU)
V30.4 (1203/1203D) (*)
30.9x V30.95 (1146/ 1146DEU) – Limited release

V30.96 (1204/1204D) (*) Limited release
31.4 V31.0 (1157/1157DEU)

V31.1 (1174/1174DEU)
V31.2 (1186/1186)
V31.4 (1211/1211D) (*) – This TIB
(*) These releases provide panel firmware compatible with the updated CPU801 and PFI80x boards.
9.6 LCD820
9.6.1 Known Issue - Filtering of Un-Configured Points
Problem description
Page 40 of 45
TIB 1211
When an LCD820 repeater is configured to filter out panel/ zonal information and it receives an "UNCONFIGURED
DEVICE" event from a panel/zone it should be filtering out, these events are displayed.
This problem is seen as minor and will typically only be seen during installation/commissioning.
9.7 MXSpeak Protocol

9.7.1 Overview
The fire panels communicate using a packet based system. The definitions of some of the packets used are made
available to other companies to allow them to connect their equipment to an MX network.
The default protocol revision used with Version 31 is revision 6.0.
Revision 6.0 is required for larger PROFILE Flexible configurations.
It is possible from the Network Overview dialog in Consys to request that the panels revert back to a previous
protocol revision.
It is important to check which revision of the protocol any external equipment uses.
NOTE :
At the time of Version 31 release, not all support programs support MXSpeak 6.
For example, MXRemote and MX Data logger.
9.7.2 TXG
TXG Version 7.16A or above is required with protocol revision 5 to get the full benefits of network changes.
TXG Version 7.16C or above is required with protocol revision 6 to get the full benefits of PROFILE Flexible panels.
To improve network performance, it is recommended the baud rate between TXG and the local network card is
increased from the default 9,600. The setting is RS232 Baud rate, PTP Parameters, for more details see TXG
documentation.
TXG Version 7.16D or above is required with to support Windows Server 2016.
At the time of Version 31.2 release there is not a release version of TXG fully compatible with the new devices. A
new release is expected shortly.
When using 835 or 855 series devices with current TXG V7.16G, an error will be displayed on the imported device
instance list because these devices do not currently exist in the device type table. This can be dealt with by using an
existing device type (e.g., 830 or 850 equivalent) to overwrite the device type. This procedure will edit the following
details: command set, device icon and event icons.
9.8 Sentinel Dongle Driver

The recommended driver for MZXConsys on Windows 10 PCs is Version 7.6.0
The driver can be found on the following web site, https://www.safenet-inc.com/support-downloads/sentinel-drivers
Page 41 of 45
TIB 1211
9.8.1 Dongle problems : MZX Consys and TSW + 410ES Programmer software on the same PC
There are reports of MZX Consys reporting ‘dongle not found’ problems when attempting to load it on a machine that
is already running TSW + 410ES Programmer software.
The solution to this is to install the latest “Sentinel Protection Installer” software. Currently this is V7.6.6 and is
available from the SafeNET Web Site at
https://supportportal.gemalto.com/csm?id=kb_article_view&sys_kb_id=e88691ba37edcb08cc47261953990e80&sysp
arm_article=KB0016514
9.8.2 Dongle recognition problems

Some users have reported problems where Consys does not recognise the presence of a dongle. If such problems are
encountered, please refer to CAB 188 – Consys Dongle Driver Installation.
CAB 188 replaces CAB 181 which also covered Dongle issues, CAB 181 has been withdrawn.
10 Other Resources
The smart phone app is available for iOS and Android phones and is available, from ITunes and Play Store.
The training videos are available from the App.
11 Known Issues
11.1 TXG Compatibility
When Version 31.4 was released, there was not a fully compatible version of TXG available.
If Version 7.16F7 TXG is used and the configuration includes one of the new devices, (855 or 835 series detectors)
then see Section 9.7.2
11.2 GUI Compatibility

If the project uses User Events then Version 3.5 GUI is required. If previous versions of the GUI are used, no event
text will be displayed if user events are used.
This restriction is only for GUIs on the LNET used as main displays or fully functional repeaters, PR1D2 devices do
not require Version 3.5.
Version 3.4 GUI was a limited release.
Page 42 of 45
TIB 1211
11.3 Group 0018 ‘Alert I/P (Z coinc timed)’ does not broadcast Alarm Warnings
Group 0018 ‘Alert I/P (Z coinc timed)’ raises a Warning for the first alarm in a Zone and an Alert for the second and
subsequent alarms in that Zone.
It should be noted that since Version 24.0, when this Group went from being global to zonal, on network systems the
Alarm Warning event is not sent to other panels. Thus, unless a Log to Log client is set up only the local Panel will
display the Alarm Warning.
11.4 Class Change
11.4.1 Overview
The system offers Class Change functionality where suitably configured sounders can be activated for a short time
using an alternative tone to indicate a non-alarm event, such as change of class in a school.
Timings of a Class Change are controlled by three delay groups:
• Group 0988 - Class Change I/P, provides the delay required to reprogram all relevant sounders for the Class
Change tone.
• Group 0992 - Class Change Timer, provides the delay required to activate all sounders that are taking part in
the Class Change plus keeping them active for the desired time.
• Group 0993 - Class Change Deactivator, provides the delay required to deactivate all sounders that have
taken part in the Class Change (once this delay has expired the command to reprogram the sounders back to
their Alarm tones is sent).
11.4.2 Limitations
Due to the amount of time required by the panel to change the tone of a sounder plus the timings applied by a Class
Change, there is a limit to the number of sounders which can reliably take part in a Class Change.
The limit needs to be applied on a per loop basis (either per high powered loop or per pair of split loops).
If there are too many sounders on a given loop, or loops, some of the sounders on those loops can misbehave in the
following ways whilst running a Class Change:
• They may raise a SOUNDER FAULT event (Group 0988 delay insufficient).
• They may not be activated (Group 0992 delay insufficient).
• They may change to Alarm Tone before the Class Change ends (Group 0993 delay insufficient).
For the default template timings for Class Change in Version 31.0-31.2 the limit is 35 Sounders.
If more than 35 sounders are required, up to 80, then the delays of the relevant Groups should be increased to the
following recommended values:
• Group 0988 = 8 seconds.
Page 43 of 45
TIB 1211
It is not recommended to increase the number of sounders on a loop, or loop pair, above 80.
11.4.3 Project checks

A new project check has been added in Version 31.2 which estimates the time required to successfully run a Class
Change for each of the configured loops. If any of these loops exceed the timings configured for the current template
then a warning is issued for each loop failing the check.
For each loop, or loop pair, the following three timings are assessed:
• D1, the time required to reprogram all sounders to the Class Change tone (Group 0988).
• D2, the time required to activate all sounders (Group 0992).
• D3, the time required to deactivate all sounders (Group 0993).
The user can attempt to eliminate the warnings by:
• Increasing the delay of the appropriate Group.
• Decreasing the number of Sounders on the offending Loop(s).
• Reconfiguring single address Sounder / Beacons to use split addressing so only the time needed to activate
the Sounder is required.
The following formulas are used to calculate the required group delays:
• Group 0988 (D1) = Number of Sounders x 100mS.
• Group 0992 (D2) = (Sounder-Beacon Count x 80mS) + (Sounder Count [1] x 42mS).
• Group 0993 (D3) = (Sounder-Beacon Count x 80mS) + (Sounder Count [1] x 42mS).
[1]
Sounder Count includes Sounder-Beacon device types which have split addressing.
11.4.4 Fire Alarm during Class Change

If a Fire Alarm is raised whilst a Class Change is running there are two issues to consider:
• All sounders actively playing the Class Change tone can remain active but switch to playing the Alarm tone,
regardless of how the cause and effect is programmed for the Alarm Zone in question.
• If the alarm is from a callpoint then the sounders in the callpoint Zone may not be play the Alarm tone within
3 seconds of the callpoint activation.
11.5 Multi-Tone
Currently multi-tone is offered with most templates released with Version 31.2.
For reasons similar to the Class Change restrictions (see section 11.4) there is a limit on the number of sounders if the
multi-tone feature is used.
Page 44 of 45
TIB 1211
The limit is 40 sounders per high powered loop or split across a pair of shared powered loops.
11.6 Multiple Devices

Since Version 31.0, depending on the loop configuration, it is possible that when 2 or more devices are assigned to the
same address no faults will be raised by the Panel.
12 Technical Support
• For Europe, please send technical support issues to: [email protected]

• For Middle East please send technical support issues to: [email protected]
• For APAC please send technical support issues to: [email protected]
Page 45 of 45

Tibv31 4

Uploaded by

Copyright:

Available Formats

Tibv31 4

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

Tibv31 4

Uploaded by

Copyright:

Available Formats

TIB 1211

TECHNICAL INFORMATION BULLETIN

MZX Firmware and Consys

The main features in Version 31.2 are:

The main feature in Version 31.1 was:

The main features in Version 31.0 were:

TECHNICAL INFORMATION BULLETIN

2.1 Automatic Upgrade

TECHNICAL INFORMATION BULLETIN

2.2 Manual Upgrade

3 Changes made to the Templates since Version 30.2

TECHNICAL INFORMATION BULLETIN

3.1 All Templates

3.1.2 Group 0018 names have been updated

3.1.3 Aux Mains fault to Aux PSU Fault

3.1.4 Updates for Connected Services Gateway.

3.2 German Templates

TECHNICAL INFORMATION BULLETIN

[Changed in Version 31.0]

3.3 Swiss Template

3.4 Austria Template

TECHNICAL INFORMATION BULLETIN

3.5 All Dual Language Templates

3.6 Greek Template

3.7 Romanian template.

4.1 New Features

4.1.1 Added new Open Class sounder/beacon P82AVB

4.1.2 Support for 855 and 835 detectors

TECHNICAL INFORMATION BULLETIN

4.1.3 Support for Connected Services Gateway

4.2 Improvements and Corrections

4.2.2 Improvement when working with USB start-up configuration

TECHNICAL INFORMATION BULLETIN

4.2.4 Improved OCM/CUI menus on single panel networks

4.2.5 Improvements Simulating FBI800

4.2.7 VID/VAD Sounders Checksum Test

TECHNICAL INFORMATION BULLETIN

4.2.10 ‘Single Address Polling’ no longer raises ‘unconfigured device’

4.2.11 Simulation of FBI (Germany) no longer raises an ‘INITIALISE ERROR’ Fault

TECHNICAL INFORMATION BULLETIN

4.2.13 Added support for a new NAND flash

Build Date of MiniCPU

Older method, 8 digits

Newer method, 9 digits

[Change added in Version 31.4]

TECHNICAL INFORMATION BULLETIN

4.2.15 Tones of Sounders now configured correctly after a device power up

4.2.16 Improved Handling of Callpoints on Noisy Loops

TECHNICAL INFORMATION BULLETIN

The kit includes

TECHNICAL INFORMATION BULLETIN

Panel COM3 to panel COM3 of the same panel 557.202.808 N-EXP

Panel COM3 to panel COM3 without network Contact Product Support

PFI based panel using COM3 to TLI800EN 557.202.808 N-EXP

TECHNICAL INFORMATION BULLETIN

5.1.4 Support for the Connected Services Gateway Card (CSG)

5.1.5 Links to Datasheets

5.1.6 Auto Renumber User Groups

TECHNICAL INFORMATION BULLETIN