BACnetNG driver does not properly write schedule objects

Summary

An scedule in BACnet can have the objects:

Device_0030de091099.SCHEDULE_0.effective-period

Device_0030de091099.SCHEDULE_0.exception-schedule

Device_0030de091099.SCHEDULE_0.weekly-schedule

when trying to write the exception schedule the diagviewer/wireshark reports an error:

'Device_0030de091099' Error writing value to object '04400000' property '00000026' array index '4294967295' failed with error class '2', error code '9'

To reproduce for example take the string from the exception schedule

{<0> {<1> {[10] 255.255.01.255},{[10] 255.255.02.255}}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> {[11] 00:00:00:000},{[0]},{[11] 00:00:00:000},{[0]}},{(3) 1}

and change it to

{<0> {<1> {[10] 255.255.01.255},{[10] 255.255.

03.255}}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> {[11] 00:00:00:000},{[0]},{[11] 00:00:00:000},{[0]}},{(3) 1}

which still should be valid.

The weekly schedule also can't be written.

E.g. a string like this:

{<0> {[11] 08:00:00:000},{[2] 3},{[11] 18:00:00:000},{[2] 2}}

The effective period can be written

Description

An scedule in BACnet can have the objects:

Device_0030de091099.SCHEDULE_0.effective-period

Device_0030de091099.SCHEDULE_0.exception-schedule

Device_0030de091099.SCHEDULE_0.weekly-schedule

when trying to write the exception schedule the diagviewer/wireshark reports an error:

'Device_0030de091099' Error writing value to object '04400000' property '00000026' array index '4294967295' failed with error class '2', error code '9'

To reproduce for example take the string from the exception schedule

and change it to

{<0> {<1> {[10] 255.255.01.255},{[10] 255.255.

03.255}}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> },{(3) 1},{<0> {(0) 255.255.255.255}},{<2> {[11] 00:00:00:000},{[0]},{[11] 00:00:00:000},{[0]}},{(3) 1}

which still should be valid.

The weekly schedule also can't be written.

E.g. a string like this:

{<0> {[11] 08:00:00:000},{[2] 3},{[11] 18:00:00:000},{[2] 2}}

The effective period can be written

Solution

The problem was addressed in the parsing of nested constructed types.

Issue Number: 34768
Fixed on Date: 7.7.2015
Versions: 7.20 0 BUILD 21629

Related Articles
FAQ: When I activate the option "write synchronously" for the Recipegroup manager recipe, and I write the recipe, the recipe does not seem to be written properly and also the Service Engine does not close properly. Why is that?
When the option "write synchronously" is active at a recipe, when writing a recipe (sending values to the PLC) for each recipe variable a writing confirmation is requested to the driver. On a successfull write, the driver sends a writing confirmation ...
OPCUA Client Driver: Extension Objects "Switching Time" in "Schedule" do not work properly
Description In the OPCUA client driver, setting a value other than 0 for "Switching Time" in "Schedule" leads to an error. All variables become invalid. These variables can be set to 0 again with another OPCUA client. They are then spontaneous again. ...
FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?
When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...
Checklist: Driver(s) cannot establish a reliable communication
Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...
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: ...

BACnetNG driver does not properly write schedule objects

BACnetNG driver does not properly write schedule objects

Summary

Description

Solution

Related Articles

FAQ: When I activate the option "write synchronously" for the Recipegroup manager recipe, and I write the recipe, the recipe does not seem to be written properly and also the Service Engine does not close properly. Why is that?

OPCUA Client Driver: Extension Objects "Switching Time" in "Schedule" do not work properly

FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?

Checklist: Driver(s) cannot establish a reliable communication

The BACnetNG driver should support TrendLog variables.