RiZone Release Notes

Version: 3.11.9.0
Operating system: Windows Server 2012R2 Standard
Windows Server 2016 Standard
Windows Server 2019 Standard
Platform: OVF, installer
Date: May 2021

The RiZone Release Notes describe the functional restrictions as

well as the known errors in the listed version.

The performance range and the implemented functions are

described in the RiZone Operating Instructions at:

http://www.rittal.com/de_de/rimatrix-downloads/

dotNet Framework
To install RiZone 3.10.x or newer dotNet Version 3.5 and 4.8.x is required.

RAM
We recommend that the RAM for existing RiZone installations is increased to 8 GB.
The RAM must be increased to 8 GB when DRC is used in RiZone.

Database
The database for installations commissioned with a RiZone version prior to 2.5.x
must be adapted by executing an SQL script.
The script and a HowTo file are available at the Rittal Service Team.

Using the SQL Express Database Server, the name field will not evaluated.

RiZone 3.11.x supports Microsoft SQL 2017 and Microsoft SQL 2019.

RiZone Release Note 1 of 6 PM RiMatrix / May 2021

Update to RiZone version higher 3.8.x
After update to RiZone version 3.8.x please download the project to the GUI and
immediately upload it again to the server. This will provide any necessary technical
changes to the project file.

Update to RiZone Version 3.10.9 from Version 3.10.6

Before an update can take place, all drivers of the existing RiZone installation must
be deleted in the following folders.

%appdata%Rittal\RiZone\Data\MetaData\DeviceDrivers
C:\Program Files (x86)\Rittal\RiZone\drv\devices\concrete
C:\Program Files (x86)\Rittal\RiZone\ Core\DeviceDrivers

Supported devices
RiZone supports all components of the CMC-TC product family, including CMC III.
The following are excluded in version 3.8.xxx.1 and following versions:

 CRAC product family

 CMC Fan Alarm System 7320.811

PDU metered/switched/managed with slave PDUs

The PDUs provide via SNMP a large number of different variables.
If further slave PDUs are attached to a PDU, the number of variables increases
further. To ensure the fault-free transfer of all variable values via SNMP, the use of
slave PDUs is restricted as follows:

1. A maximum of two slave PDUs may be connected to a master PDU.

2. A maximum of two slave PDUs may be connected to a CMC III Processing
Unit per CAN bus output. Namely, maximum 2 x 2 slave PDUs.

LCP
Bei dem Einsatz der LCP Produktfamilie wird bei einer Änderung der Einheit der
Durchflussmenge von Liter/Minute auf Gallonen/ Minute das LCP nicht in den
Wartungsmodus gesetzt. Es erfolgt eine falsche Darstellung der Einheit in RiZone.
Bei der Umstellung von l/m auf g/m muss das LCP neu entdeckt werden und im
Projektbaum erneuert werden.

LCP VX
When using "Virtual Devices", care must be taken to ensure that the "Virtual Devices"
are configured in the LCP or CMCIII before they are detected by RiZone. If the
configuration is subsequently changed, a display error occurs in RiZone. If the
"Virtual Device" is configured in the CMC after discovery in RiZone, the "Virtual
Devices" must be rediscovered and replaced in the RiZone project.

RiZone Release Note 2 of 6 PM RiMatrix / May 2021

In the graphical representation of a LCP VX, only the status of the main node is
shown. If the status information of subordinate nodes changes, this change is not
inherited by the main node and is not displayed graphically.

Known errors
GUI:
1 The GUI is installed with the “Execute as administrator” function.

2 An appropriate message will be issued if users with expired password or

deactivated account attempt to login. Local server users can reset their password
if it has expired. Domain users cannot change their password via RiZone. Note:
Users are notified seven days prior to expiration of their password already during
the login.

3 Simultaneous start of two GUIs on a PC

If two GUIs are started in quick succession on a PC, it is possible that only red
“X”s, instead of the device icons, are displayed in the tree structure for a GUI.
This GUI must be closed and restarted.

Server:
The Server is installed with the “Execute as administrator” function.

Device support:
1 To use the CMC III PU firmware update function, the PU must have firmware
version 3.13.xx or later. A remote update is not possible for older firmware
versions.

2 If two access systems, each with their own PU III, are installed in an enclosure,
the behaviour of the one-time PIN in this constellation must be considered. If the
one-time PIN is set on the higher-level infrastructure component (enclosure), both
access systems can be opened with the one-time PIN. If, for example, the front
enclosure door is opened with the one-time PIN, the rear door can also be
opened subsequently with the same one-time PIN.
For a configuration with only one PU III, the one-time PIN allows only the front or
the rear door to be opened.

3 If a device in the project is replaced with an identical device (Discover > ALT-
drag-and-drop to the old device), it must be guaranteed that the same SNMP
connection settings (e.g. the Read- and Write-Community for v1/2c) are set.

RiZone Release Note 3 of 6 PM RiMatrix / May 2021

4 When replacing devices in the project (Discover > ALT-drag-and-drop to the old
device), it is not possible that RiZone transfers all values of the old variable list
(Setpoints, Description Name, etc.) automatically from the old device to the new
device. The automatic insertion of the new device in existing views, charts,
workflows, etc., still functions.

5 RiZone 3.9.xx and newer supports PDU Firmware Version 5.15.xx or newer.

6 When creating a third-party device driver, the created default chart must be saved
via the menu. If you close the window with the "x", the changes are discarded.

Communications modules:
1 In additional to the network ports described in Section 29.3 of the RiZone manual,
as of RiZone version 3.6.xx.5, port 22221 is also used for the communication
between the RiZone GUI and the server.

2 As of version 3.8.xx.1, RiZone can write status information in the event log of the
Windows Server operating system.
Meaning of the possible log entries:
Start (1100)
Connection to core (1101)
Project loaded (1102)
Stop (1110)
Error (1120)
Lost connection to core (1121)

Offline configuring:
1 The offline configuring must be performed from top to bottom in the device tree.
Example: For RiMatrix S, the RiMatrix S node must be moved in before fans in
the location tree.

RiZone Release Note 4 of 6 PM RiMatrix / May 2021

RiZone server key

1 The server key is given triple DES encryption and saved on the server. The key is
encrypted with the processor ID and the processor revision. The key is stored on
the server in the folder:

%ProgramData%\Rittal\RiZone\ServerKey.enc

2 If the processor type in the virtualization environment change or the Encryption

procedure by an update of the operating system, you must generate a new
RiZone Server key. The program for creating a new key is located in the folder:

C:\rizone_install\RittalSSLCfg.exe

RZGuiUser
The encryption of the password of the RZGuiUser is done by the CPU ID. If the CPU
ID or the encryption method changes due to an update of the operating system, the
password must be reset in the Windows user administration and in the RiZone GUI
installer.

RiZone Master/Slave operation

In the master/slave operation of RiZone the slave RiZone server must be integrated
into the master server via the SNMP - device drivers.

Variable ElectricalWorkMonthly
When calculating the variable "ElectricalWorkMonthly", the value before the first
calculation is specified with "-100". The value does not get the status "Quality Bad".

RiZone Release Note 5 of 6 PM RiMatrix / May 2021

Corrected Errors
Version 3.8.40.1
1 The one-time PIN and the emergency PIN now have maximum two successive
identical digits.
2 During the PIN generation, the GUI can crash in rare cases.
3 Improved behaviour when uploading Access files to the CMC III PU.

Version 3.8.41.1
One-time PIN and the emergency PIN status information will be displayed only inside
the executed GUI (Multiuser operating)

Version 3.9.2x
Sending traps from a workflow is not possible. The Rizone.Messaging service
crashes.

RiZone Release Note 6 of 6 PM RiMatrix / May 2021