PI Release 3.1SR2
PI Release 3.1SR2
PI Release 3.1SR2
Product information
Information produit
englisch (GB) - e / Doc No.: D100037715 Doc. created on: 08.04.2010
novaPro Open Version 3.1 SR 2 is available on the Extranet. This is a full version, i.e. the DVD
contains novaPro Open V3.1 and Service Release 2
Contents
2. Notes
Please note:
This is a service release of novaPro Open. It can be downloaded from the extranet or ordered as a
DVD (YZP420F999).
All other preceding service releases from version 3.1 are included in this version, and will therefore
be removed from the extranet. novaPro Open V3.1 SR 2 is therefore the latest version of novaPro
Open.
3. Installation prerequisites
A back-up of the existing installation must be made prior to installation.
4. Installation instructions
1. Close all novaPro Open applications.
2. Close all other applications and disable any anti-virus programs.
3. If an existing application is upgraded, read carefully the upgrade document.
4. Unzip the downloaded zip file into a new folder (with folder structure) and run the installation
program at "newfolder\Programs\setup.exe"
or run "\Programs\setup.exe" straight from the DVD.
5. Follow the instructions.
5.1 UCVT_Converter
The UCVT converter 3.1.2.0 delivered in this release fixes the following entries:
- When an alarm is modified, it is saved a second time and erases another one.
- Added English xml syntax for S2400 plan
- Bad driver ID for the project with different type of drivers
Blink, Fill color, and Line color have to propose new settings for this new event.
The new event “End acked”, is added to these dialogs to be able to setup representation of the new
alarm state.
This feature is also concerning the web image (for display part).
Acknowledgment trigger proposes to user to acknowledge start and/or end of the alarm depending
on alarms acknowledgement requirement.
This concerns the “Action On Alarm” feature. When defining the alarm properties for a BACnet alarm
rule or event filter the operator needs to specify the image and zone to switch to the correct window
when he clicks on an alarm in the event summary. This process is time consuming and error prone.
When the user selects “Go to zone” in event summary an image selector will popup. The image
selection is limited to the images containing a corresponding alarm object. If only one image is
possible, the selection is skipped. The same process of selection is done for the zone inside the
image.
As it is possible in Object Generator to build alarm rules, the use of %Macro% will be introduced in
the following properties of BACnet event filter definitions:
- Alarm text
- Alarm family
%DevInst%, %DevName%,
%ObjType%, %ObjTypeName%,
%ObjInst%, %ObjName%, %Description%,
DB-ID: 524338 Rev.: 01 / Vers.: 01 5/9
DoNr.: D100037715
%EventTypeName%, %EventStateName%, %EventText%, %NotifyType%
If the “<auto>” value is set in the help file name in the alarm definition, the help file name will be
automatically built by interpreting a string with macro fields.
The field "automatic alarm help file" associates to a BACnet alarm one help file whose name is
composed from the macro defined in this field. The macro %ObjName% is the most relevant.
It is advisable to use the file in HTML format. They will be available in the PDM application and in the
Web application.
To do this: create your html files and copy the files in the directory AHP (see paths in the options of
studio) and in the DOCS directory.
More than 8 characters can now be used.
This option "automatic alarm help file" is valid only for BACnet alarms routed by the driver with alarm
rules (or default event filters).
Previous version of BACnet event filter definition allows only priority and object name criteria.
- Event type:
Empty for all or one among:
"CHANGE_OF_BITSTRING", "CHANGE_OF_STATE", "CHANGE_OF_VALUE",
"COMMAND_FAILURE", "FLOATING_LIMIT", "OUT_OF_RANGE", "COMPLEX_EVENT_TYPE",
"BUFFER_READY", "CHANGE_OF_LIFE_SAFETY",
"EXTENDED", "BUFFER_READY_2", "UNSIGNED_RANGE"
- Event state:
Empty for all or one among:
"FAULT", "OFF_NORMAL", "HIGH_LIMIT", "LOW_LIMIT", "LIFE_SAFETY_ALARM", "NORMAL"
- Object type:
Empty for all or one type number (standard or proprietary).
- Notification class:
Empty for all or one instance number.
- Notify type:
Empty for all or one among:
"EVENT", "ALARM"
Note:
Up to now, the only events that were treated were of “notify-type” “Alarm”, with these modifications
the “Event” type will also be handled and routed to novaPro Open.
6. Coming next
A new version from nPO is in work, it will be the version 4.0. The main new features are the
compatibility with windows server 2008 and windows 7. A new trend module will replace and improve
the existing one.