Update Notes - Version 3.20

Notes to consider when updating older projects to Version 3.20.

Note: Consider the Incompatibilities introduced in 3.20 when upgrading.

User Interface

Compatibility - Graphical Display Qt5

When upgrading a project from versions older than 3.20, the config entry [ui] compatLegacyPainting is set. This config entry allows the display to remain largely compatible with the earlier versions. This influences the behavior when rounding up/down to the next full pixel. If you want to deactivate the compatibility behavior, the config entry must be set to 0:

[ui] 
compatLegacyPainting = 0

Driver

SNMP in Redundant Systems

When upgrading a project with SNMP Drivers in redundant systems, a new datapoint "<DP>_2" is automatically created for the redundant connection.

SNMP Datapoints

When upgrading a project to version 3.20, the obsolete data points _SNMPAgent and _SNMPV3Entity are deleted if they have no active connections. The data point type itself remains available.

Notes for Upgrading the BACnet AddOn

You can upgrade a BACnet AddOn project from an older version to the new BACnet AddOn version 3.20.

Upgrade Requirements

The upgrade will only work if the stdlib and BACnet AddOns directories in the configuration file are updated to the current version (3.20). You must do this manually in the project. Make sure to complete this step BEFORE starting the project for the first time, but AFTER it has been upgraded to the current version.

BACnet Object Naming

When creating new datapoints for a BACnet object with the new AddOn, you must be careful. The naming convention for datapoints and the configuration of the datapoint element address are different from the old AddOn's conventions. The new naming convention for datapoints in the style of the new AddOn is as follows:

<device Id>_<object type name><instance>

If you need the old behavior for existing projects, you can configure it using the internal datapoint element _BACnetEng.DpNaming.. The default value "0" enables the new behavior. Setting the value to "1" enables the legacy behavior, which uses <Object name>. However, using this legacy behavior is not recommended because the <Object name> might not be unique and could contain special characters. These issues can cause problems when creating datapoints.

Important: The datapoint element _BACnetEng.DpNaming. is only created when you import the datapoint list of the BACnet AddOn for the first time.

CAUTION: Switching to the old behavior should be considered a permanent change for this project and can only be done in the PARA.

JSON Format

In the upgraded project, the JSON format is now used for displaying and modifying BACnet complex properties.