...
| Kotva | ||||
|---|---|---|---|---|
|
...
The BACnet communication protocol (Building Automation and Control Networks) implements ANSI/ASHRAE 135-2001 standard.
This implementation was tested with the following devices:
...
Note: If the Application tag is not configured properly (for the binary value it is Enum), the Desigo station returns an error 'invalid-data-type' when attempting to write:
...
When writing the value, the WriteProperty-Request message is used. As Subscribe/read is checked, the value is read after it's written. If I/O tag would be configured with Request type WriteProperty, its behavior would differ only by an absence of periodic value reading (when starting the KOM process and during its running, the period is configured on the station, in Time parameters tab).
...
D2000 supports the reading and writing of schedulers. A scheduler contains BACnet attributes weekly-schedule(123) and exception-schedule(38).
Weekly-schedule is the field an array of 7 items (one item for each day in of week). Each item represents a sequence of time-value pairs that defines define the value changes of the scheduler in a given time. When reading and writing, you can configure also an Array index which enables to access to the items in an array and access individual items of a weekly-schedule(123) array. The array index is 1-7 for single individual days (1=Monday), the index 0 contains a size of the array (value 7 for the attribute the weekly-schedule(123) )attribute, value 0 up to N for the exception-schedule(38) attribute).
Exception-schedule is intended for the holidays that require a different regime mode as is configured for common days. Exception-schedule is the sequence of 0 up to N items. One An item always contains a date (or range of dates), several time-value pairs (as regards in a weekly-schedule), and a priority (1= top, 16= the lowest). The priority defines which of the items will be used if they overlap.
Reading of scheduler (the
...
weekly-schedule attribute)
- Value after -by-value: a dynamic change of complex address (1.1, 1.2, 1.3, etc.) in a script enables us to read all values and times similarly as for other properties.
- All times and values for one day at the same time:
- Value type: a text input (reading of scheduler) or text output (read/write)
- Request type: ReadProperty (reading of scheduler), ReadWriteScheduler (read/write)
- Subscribe/read: Y
- Object type: schedule(17)
- Instance: an instance number (e.g. 6) which is found in a Desigo configuration or with the help of the WhoIs request.
- Property type: Complex
- Property identifier: weekly-schedule(123)
- Array index: 1 up to 7, it depends on the day being read
- Application tag: if it is not defined, Unsigned is will be used (it is necessary used only when for writing the value)
- Complex address: 1 (address of a sequence)
The times and values separated by a semicolon are read into the text value (see Note).
When writing the value to a scheduler you should realize that the value can be sent with various application tags (Unsigned, Signed), however, the device expects a particular tag (the easiest way to find it, is by reading of the value value while line logging is active on the line). The application tag of value is defined by the item Application tag item in the configuration. The valid value of Application tag can be Boolean, Unsigned, Signed, Real, and Double. If any other type is set, the Unsigned value is automatically sent. A value type can be changed dynamically - if the first character of a text value is B, U, S, R or D, it stands for (B)oolean, (U)nsigned, (S)igned, (R)eal or (D)ouble.
...
You must configure Request type=ReadWriteScheduler and assign the a sequence of time-value pairs separated by semicolon into I/O tag of text output (type, e.g. "0:0:0; 1; 2:30:40.5; 2; 5:00:00;1".
The text string with the length=0 is ignored so that the "empty sequence" will not be recorded written to the scheduler after saving the D2000 configuration or starting when the KOM process is started. For this reason, if the time plan of the scheduler must be deleted for the a particular day, the string of nonzero length (it contains neither time nor value: " ") must be assign written to the I/O tag.
Note: Another possibility to write weekly-schedule, besides the special ReadWriteScheduler request ReadWriteScheduler, to write weekly-schedule is recording writing of an ASN sequence, e.g. the sequence "{ T0:0:0 u1; T2:30:40.5 u2; T5:0:0 u1 }" corresponds to the value "0:0:0; 1; 2:30:40.5; 2; 5:00:00;1". The I/O tag configuration differs only in Request type=ReadProperty. You can also write the time frame schedule for the whole week, if Array index is not set and the value contains 7 sequences for the individual days, e.g. "{ T0:10:0 u3 T1:3:0 u1; } {T2:0:0.0 u2 T5:30:10.0; u3; } { T6:0:0.0 u2 T7:0:0.0 u3} { T20:0:0.33; u1} { T21:0:0.0; u1} { T22:0:0.0; u2} { T0:0:0.0; u3; T1:2:0.0; u1; T2:0:0.0; u2; T5:30:10.0; u3}".Kotva note_schedulersiemens note_schedulersiemens
...
Writing to the scheduler (the exception-schedule attribute)
The recording of writing to the exception-schedule is supported over via the recording writing of the an ASN sequence.
Example: I/O tag configuration:
...
Application tag: not defined (write the whole ASN sequence)
With Using the help of this string "0{ 0D2.10.2005 } 2{ T1:0:0; u1; T12:0:0; u3 } 3u10" you can write the time frame schedule for the day October 2, 2005. The scheduler has the value 1 from since 1:0:0, the value 3 from since 12:00:00. The priority of the exception-schedule is 10. When rereading of reading a value after writing (Subscribe/Read was configured) with the activated debug on the line, you can see the following log:
...
To set the exception-schedule for the range of dates, write the value "0{ 1{ D5.10.2005; D8.10.2005}} 2{ T1:0:0; u1; T7:0:0; u3; } 3u15". This value for the range of dates 5.10.2005-8.10.2005 sets the scheduler from 1:00:00 to the value 1 and from 7:00:00 to the value 3. The priority of the exception-schedule is 15. When rereading of value When reading a value after writing (Subscribe/Read was configured) with the activated debug on the line, you can see the following log:
...
Several items of above mentioned types can be written to the the exception-schedule by the using a string which contains jointed joined sequences, e.g. "0{ 0D2.10.2005 } 2{ T1:0:0; u1; T12:0:0; u3 } 3u10 0{ 0D3.10.2005 } 2{ T0:0:0; u2; T5:0:0; u3; T14:0:0; u1 } 3u11 0{ 1{ D5.10.2005; D8.10.2005}} 2{ T1:0:0; u1; T7:0:0; u3; } 3u15 "
...