Differences to version V2.12

Version V2.20 has been fundamentally extended and improved in relation to version V2.12. The entire functional range of room automation is covered by the new functions. In addition to the extensions, however, the existing performance features have been revised. So that projects created with V2.12 can continue to be maintained, versions V2.12 and V2.20 can be installed and used in parallel on the same computer. The project files can easily be distinguished by the file extension. Due to some extensions, however, old projects cannot be directly read into version V2.20. In future there may be a migration tool that will transfer as much information as possible from an old project to a new one. The following table contains a summary of the most important extensions and changes:

Requirements

V2.12

V2.20

Improvement

File extension of the project file is *.bam.

File extension of the project file is *.bamx.

The individual project files can be assigned to the individual versions by the file extension alone.

TwinCAT V2.10 is required.

TwinCAT V2.11 is required.

The CX5000 can thus be supported.

Supports EnOcean via KL6021-0023.

Supports EnOcean via KL6021-0023 and via KL6581.

Several EnOcean receivers can be connected to one terminal.

Only signal groups can call scenes.

Signals and signal groups can call scenes.

In the case of a signal, a group does not always have to be created in order to call a scene.

There are 2 versions for the lighting.

There are 6 versions for the lighting.

Lightings for staircase lighting, twilight switch, emergency lighting or the like are now also available.

-

Objects for timer switch channels, composite modules and weather stations have been added.

Important performance features are thus available with the new version.

The commands are transmitted by ADS/TCP.

The commands are transmitted via TwinCAT network variables.

Network variables can be integrated more easily into the system. It is not necessary to register all devices in the TwinCAT router of the controller. The transmission by TwinCAT network variables is considerably more efficient, since the same command can be sent to several devices with one telegram.

Access to the objects in the PLC takes place via global variables.

Function blocks are available in the PLC for each type of object. Each object can be addressed via these function blocks.

The extension of the PLC program with the user’s own PLC functions has become simpler, in particular for the graphic display types.

-

Copy, pasting, importing and exporting are supported by the TwinCAT Building Automation Manager.

Project creation is very much simplified. Once parameterised, elements can be duplicated as often as required.

-

Searching for I/O devices and fieldbus terminals is supported.

This can accelerate the registration of the I/O devices.

The sensors are assigned to the functional units via an event/action assignment on the sensor.

All sensors and all actuators are assigned on the functional unit.

The overview is significantly improved. It is easier to see which sensors and actuators are affecting the functional unit.