BACnetNG driver send InvokeIDs beginning with 0 when readPropertyMultiple

BACnetNG driver send InvokeIDs beginning with 0 when readPropertyMultiple

Summary

Some BACnet devices have problems with InvokeIDs 0. They only accept from 1 upwards even if in standard it is clearly allowed from 0 to 255.

Description

Some BACnet devices have problems with InvokeIDs 0. They only accept from 1 upwards even if in standard it is clearly allowed from 0 to 255.

Solution

The BACnet driver now begins with InvokeID 1. The InvokeID 0 is used if the full range possible (256) of concurrent requests is configured in the driver.

Issue Number: 36592
Fixed on Date: 10.6.2016
Versions: 7.50 0 BUILD 28986

    • Related Articles

    • The BACnetNG driver should support TrendLog variables.

      Summary TrendLog variables should be supported by the BACnetNG driver. DescriptionTrendLog variables should be supported by the BACnetNG driver. Solution The BACnetNG driver now supports TrendLog variables. Issue Number: 36601 Fixed on Date: ...

    • Driver configuration cannot be opened and also no new driver can be created.

      If a Service Engine is started as a windows service also zenDrvOpsManager is running as a service. Thus zenDrvOpsManager cannot open a user interface for driver configuration and the Engineering Studio seems frozen. Running a Service Engine as a ...

    • IEC870_103 driver does not send GI command

      Description The IEC870_103 driver did not send the General Interrogation (GI) command in certain conditions. The issue has been addressed and the IEC870_103 driver behavior is now as expected. To benefit from this fix: Update your zenon Software ...

    • Driver ALLENDF1 does not send all recipe values to PLC

      Summary It is not possible to send all recipe values to PLC  using ALLENDF1 driver. PLC type in this specific case MicroLogix Allen-Bradley  Standard recipe / Recipe Group Manager:　 When send action ('write all values' screen specific functions) is ...

    • 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 ...