User Manual

Corrections and improvements in MP2.31
4 Corrections and improvements in MP2.31
This chapter provides a detailed report on the issues resolved as well as on detailed
improvements in MP2.31.
Be aware that the most severe issues in MP2.30 have been already addressed by spe-
cific service releases (fixes #2.30-01 and #2.30--02), which are now fully integrated into
MP2.31 software. However, MP2.31 includes further enhancements and therefore,
whenever any of those can be somehow beneficial, we recommend you to plan for up-
dating existing installations
On top of remarkable achievements in the areas of product reliability and performance,
the functions addressed by specific corrections and improvements are the following:
 Installation
 User interface
 NS8210 driver for NK822x
 CS11 AlgoRex EP7
 CC60
 CS6 Guarto
 Event treatment
 Graphics
 History browser
 Printed output: journaling and alarm printout
 Import procedures for CS4, CZ10, and CS11 AlgoRex
 Tool environment
 License
The table below illustrates the most important corrections and improvements. Note that
the list does not cover the entire set of modifications included in the software.
# Function Error (as it was before MP2.31) or improvement description Notes
3740 Installation If the computer name was longer 15 characters, previous MM8000
software used not to work properly.
 The computer name is also used as local domain name for MM8000
Stand-Alone stations. Note that in Composer, and namely in the M8000
security settings, the domain name should be anyway cut to 15 charac-
ters, e.g.: the computer name “My_MM8000_station” (in Composer 
MM8000 station name) should be indicated as “My_MM8000_stati”
domain (in Composer  MM8000 domain name).
3380 User interface
(Event filters)
One of the event filter options, related to “Unprocessed events”, did not
work properly
4063 User interface
(Plant browser)
If a CZ10 zone had no affiliated elements, Plant Browser used to report
the zone’s “Disconnect” property as faulty (greyed text).
4300 User interface
(Dual monitor)
If configured, the 2nd monitor must necessarily be used for the history
browser, which could no more start on the 1st monitor.
4320 User interface
(Dual monitor)
After the use of “Empty_DB” procedure, the 2nd monitor was disabled.
18
Fire & Security Products 008091_a_en MM8000 MP2.31 Release Notes.doc
Siemens Building Technologies Group 02.2004