...
This protocol supports data reading from/writing to Johnson Controls devices , - DX9100 unitseries units, that are equipped by with a serial port for N2 Bus. The implementation currently does not support the N2 Open standard.
| Kotva | ||||
|---|---|---|---|---|
|
...
Note: on TCP-IP/TCP line, multiple host names hostnames or IP addresses separated by comma/semicolon can be defined , to connect to multiple devices in a round-robin fashion.
| Kotva | ||||
|---|---|---|---|---|
|
...
- Communication protocol: Johnson Controls N2-Bus.
- Address The address of the station on N2 Bus is the number in the range of 1 to 255, the address 0 is reserved.
- Reading values of objects object values on the station is executed periodically according to time parameters "Polling parameters".
- The synchronization of real-time can be activated - check the Enable parameter in the "Synchronization period" section and set the period, which defines a period of recording writing a real-time.
| Kotva | ||||
|---|---|---|---|---|
|
...
The configuration dialog box - Parameters tab.
The parameters influence some optional parameters of the protocol. There can be defined the following parameters of station protocol:
...
| Parameter | Meaning | Unit | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Delay The delay between reading the responses until it is completed. | millisecms100 millisec | 100 ms | ||||||
| The first waiting for a response after sending a callrequest. | millisecms200 millisec | 200 ms | ||||||
| Delay between retry calls The delay between request retries if a communication error occurs. | millisecms500 millisec | 500 ms | ||||||
| Number of retry response reading until The number of readings of a response until it is completed. | - | 10 | ||||||
| Number of retry calls when The number of request retries when an error in communication occurs. | 1 .. 32 | 2 | ||||||
| Maximum The maximum number of consecutive errors in one station reading cycle after which the next I/O tags are no longer read. A value of 0 causes all I/O tags to be read. The parameter is implemented to prevent one non-communicating station from causing an excessive reading delay for other stations on the line. | - | 0 | ||||||
| Enables the detailed debug information about the values of I/O tags that were obtained by polling. | YES/NO | NO |
...
Used I/O tags: Ai, Ao, Ci, Co, Di, Dout.
The address of the I/O tag can define be defined in two formats:
1. Predefined items of DX9100 has have format:Kotva preddef_itemy preddef_itemy
Modul.Tag
Where Modul is a the name of the module and Tag is the name of the tag within a module. List The list of items is based on the documentation DX-9100 Configuration Guide, Appendix B. Since this is a large list of the static items, there is prepared an "Object Browser" dialog window is prepared, where you may find the particular object. In the "Item Address" section click the button next to the "Item" field.
...
The following window opens:
The left part of the window contains the list of modules. After clicking the particular module, the list of tags that belong to this module are is displayed in the right part of the window.
Parameters of items:
Tag: Name of the tag.
Description: Short description of the item.
Access: Access level (R - read-only, R/W - read and write, CNF - read and write, the configuration parameter is recorded stored into EEPROM).
Type: Value type of item (see also here).
Address: Physical address of item that is used for reading/writing. It is calculated from the starting address of the module and offset tag (in hexadecimal format). The bit number (1 up to 32) of the addresses of binary items is placed after the dot.
After double-click the particular clicking a selected tag, the dialog window is closed and the name of the item occurs is copied in the "Item" field in the "Item Address" section.
...
| Value type | Range, value interpretation |
|---|---|
| U8 | 8 bits unsigned (JC tagging 1 Byte) |
| U16 | 16 bits unsigned (JC tagging 2 Byte) |
| U32 | 32 bits unsigned (JC tagging 4 Bytes) |
| I8 | 8 bits signed (JC tagging 1 Byte Int) |
| I16 | 16 bits signed (JC tagging 2 Byte Int) |
| FP16 alebo or N | 16 bits floating point in Johnson Controls format (JC tagging Number) |
| CONN | Connection - interpreted as 16 bits unsigned |
| DST | Destination - interpreted as 16 bits unsigned |
Address is the address of the item in decimal format.
Bit is a bit number. Optional An optional parameter, it is important relevant only for binary items, when the particular bit is extracted form from the value of the whole item (for U8, U16, or U32 items).
Examples:
N.1232
U8.765.1
U32.4078
...
Starting with D2000 version 10.1.37 (patches from 12.4.2016 and newer) it is possible to configure Time Schedules. In "Object Browser" new modules TS1cfg, TS2cfg .. TS8cfg have been added, each of them repesents represents a configuration of one Time Schedule.
Every time schedule has several general parameters and a set of eight begin times (BETIME1..8), end times (EETIME1..8), and days when a time schedule is active (EEDAYS1..8).
A time interval is configured by writing values to begin time and end time. Writing is supported for relative time (e.g. 01:05:00) and for Ao/Co (value in seconds, i.e. 01:05:00 equals to 3 900). Times are sent to the device as hours:minutes (i.e. seconds are ignored). Invalidation of time is possible by writing an invalid value or value 24:00:00 or greater (86400 seconds or more).
By writing a value to days (EEDAYS1..8) it is possible to specify during which days a time schedule is active. Value is a number (0-255) interpreted as a bit maskbitmask:
- 1.bit - Monday
- 2.bit - Tuesday
- 3.bit - Wednesday
- 4.bit - Thursday
- 5.bit - Friday
- 6.bit - Saturday
- 7.bit - Sunday
- 8.bit - Holidays
...