The BACnetNG driver should support TrendLog variables.

• Related Articles

• BACnetNG: Driver does not finish reading trendlog object before starting to read another trendlog with maxconcurrentrequest=1

  Description The BACnetNG driver did not finish reading the reading the first trendlog file when the setting for the maximum concurrent requests is set to 1. With specific configurations this can lead to multiple trendlog files being read by the ...

• Variable xml export/import does not consider parameters BACnetPropertyID and BACnetWritePriority for variables created on BACnetNG driver

  Summary BACnetNG driver: the variable xml export/import in the editor does not consider the parameters BACnetPropertyID and BACnetWritePriority Description BACnetNG driver: the variable xml export/import in the editor does not consider the parameters ...

• BacnetNG driver should not suggest a hashmark (#) as Property Separator

  Summary "#" is not an allowed character in zenon variablenames. It shouldn't appear as a suggestion for a property separator within the BacnetNG driverconfiguration. Side effect: If a hash is used, these variables cant be used in a extendet trend ...

• KUKA32 Driver. Variables of driver object type 'KUKA System Variable' do not support dynamic communication names.

  Summary The usage of dynamic communication names with variables of Driver object type KUKA System Variable of the KUKA32 Driver does not work correct. Instead of the correct values chinese like characters are shown. DescriptionThe usage of dynamic ...

• PHOENIX32 Driver should support variable addressing via symbolic address

  Summary PHOENIX32 Driver should Support variable addressing via symbolic address in addition to addressing via variable name. DescriptionPHOENIX32 Driver should Support variable addressing via symbolic address in addition to addressing via variable ...