Device defaults

Plant automation

Start program after a full load

Activates the function in the Programming editor. This is only valid for newly created devices. The default entry is cleared.

Programming editor > Settings

Enable engineering data on device

Activate to load the engineering data into the device. The Load > Engineering data menu becomes visible.
Note: Within a region, the settings should be the same to avoid confusion if engineering data on the device exists or not. To have this menu available, the tool manager must enable this function in the ABT Site installer.

Pre-configuration definition

Displays project specific pre-configuration definition files which is applicable to the primary application from the standard library.

Pre-configuration file

Object structure on BACnet

Indicates whether the BACnet object hierarchy is visible in the online system.

Does not create the structure view object (object-type 29) in the reports. Use this functionality for KBOB projects.

Creates the structure view object (object-type 29) in the reports.

Notification class template

Notification classes will be used for new devices created in ABT Pro and ABT Site. The default notification class is Desigo.

The notification classes can be changed at a later state in ABT Site for Desigo PXC4/5/7 devices in ABT Pro and room programming. In the Log tab, a message will be displayed.

AMEV, Desigo and KBOB are visible and delivered by headquarter. If there are additional regional headquarters templates, the list will show those as well. Regional headquarters templates must be stored under:
C:\ProgramData\Siemens\Desigo\ABT\Libraries\RC\NotificationClasses.

Note: In ABT Pro if device is added from Add device dialog, then notification class selected in ABT Site is taken as default. The devices which are added through libraries take the notification classes defined in the library (currently it shows Desigo’s contents).
Replace a notification class template of a device

Import template

A new notification class template can be imported into the project and automatically selected as a new default in the combo box.

APDU retries

Specifies the number of retries when an APDU (Application Protocol Data Unit) transmission fails.
Default is 3.

APDU segment timeout (ms)

Specifies the timeout value in milliseconds from 1000 to 10000, when the APDU is sent in multiple segments.
Default is 2000.

APDU timeout (ms)

Specifies the timeout value in milliseconds from 1000 to 10000, when the APDU can be sent in one transmission.
Default is 3000.

APDU retries

Specifies the number of retries when an APDU (Application Protocol Data Unit) transmission fails.
Default is 3.

APDU segment timeout (ms)

Specifies the timeout value in milliseconds from 1000 to 10000, when the APDU is sent in multiple segments.
Default is 10000.

APDU timeout (ms)

Specifies the timeout value in milliseconds from 1000 to 10000, when the APDU can be sent in one transmission.
Default is 10000.

Mains frequency

50 Hz and 60 Hz. Default is 50 Hz.

Table with preferred TX I/O module for each data type

Binary input. Default is TXM1.8D.

Multistate input. Default is TXM1.8D.

Analog input. Default is TXM1.8U.

Analog output. Default is TXM1.8U.

Binary output. Default is TXM1.6R.

Multistate output. Default is TXM1.6R.

Accumulator. Default is TXM1.8D.

Power supply. Default is TXS12F10

Show all object types

When selected additional, advanced data points are displayed in the Add data point dialog in Engineering > Modbus.

Note
This option must be enabled in order to be able to create bulk reader objects manually.
Optimizing the network traffic