Difference between revisions of "Airzone"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
{| class="wikitable" | {| class="wikitable" | ||
| '''Baud rate''' | | '''Baud rate''' | ||
− | | | + | | 19200 |
|- | |- | ||
| '''Data bits''' | | '''Data bits''' | ||
Line 19: | Line 19: | ||
|- | |- | ||
| '''Parity''' | | '''Parity''' | ||
− | | | + | | even |
|- | |- | ||
| '''Flow control''' | | '''Flow control''' |
Revision as of 11:34, 7 January 2014
Airzone is a control framework for ducted air conditioning systems which allows for the control of several zones independently. This I/O server provides support for this Airzone systems: INNOBUS, FLEXA, ANTREE and CEN.
Communication
Airzone communicates with HSYCO through a modbus connection employing a RS-485 gateway.
RS-485 parameters:
Baud rate | 19200 |
Data bits | 8 |
Stop bit | 1 |
Parity | even |
Flow control | none |
HSYCO Configuration
Options
ID | Default | Values | Description |
---|---|---|---|
pin | <code> | 4 or 6-digits code. Use the specified PIN code to perform operations that require user authentication. If this option is not specified it will be required to manually insert the pin every time such operations are performed | |
gui | true | true | enable support for the UI object, UISET actions and USER commands |
false | disable UI support | ||
startupevents | false | true | generate IO events also during the driver’s start-up phase |
false | start generating events only after HSYCO is aligned with the current status of the system | ||
pollinterval | 3 | n > 0 | the data acquisition interval, in seconds |
logsize | 20 | n ≥ 0 | the number of log lines to display in the UI object |