Difference between revisions of "Tecnoalarm"
Jump to navigation
Jump to search
(Created page with "TECNOALARM TP16-256, TP8-64BUS, TP8-96VIDEO, TP8-96GSM and TP16-512GSM are advanced, multi-area security systems integrated with a variety of wired and wireless sensors. The T...") |
|||
| Line 1: | Line 1: | ||
| − | + | == Options == | |
| − | + | ||
| − | + | {| class="wikitable" | |
| + | !ID | ||
| + | !Default | ||
| + | !Values | ||
| + | !Description | ||
| + | |- | ||
| + | |||
| + | |rowspan="2"|gui | ||
| + | |rowspan="2"|true | ||
| + | |true | ||
| + | |enable automatic support of Web GUI objects to show the system status and intercept control buttons | ||
| + | |- | ||
| + | |false | ||
| + | |disable support for the Web GUI | ||
| + | |||
| + | |- | ||
| + | |||
| + | |rowspan="2"|startupevents | ||
| + | |rowspan="2"|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 | ||
| + | |||
| + | |- | ||
| + | |||
| + | |rowspan="2"|discovery | ||
| + | |rowspan="2"|true | ||
| + | |true | ||
| + | |automatically creates the list of all detected datapoints with type DPT 1 and the defined virtual datapoints in the systemtopo.txt file | ||
| + | |- | ||
| + | |false | ||
| + | |auto-detect for devices is disabled | ||
| + | |||
| + | |- | ||
| + | |||
| + | |rowspan="2"|fromevents | ||
| + | |rowspan="2"|false | ||
| + | |true | ||
| + | |generates events for commands sent on the KNX BUS reporting the source address and the value of the command | ||
| + | |- | ||
| + | |false | ||
| + | |disable command events | ||
| + | |||
| + | |- | ||
| + | |||
| + | |rowspan="2"|readaftercommand | ||
| + | |rowspan="2"|false | ||
| + | |true | ||
| + | |forces the driver to read the value of a datapoint after a command is sent to it | ||
| + | |- | ||
| + | |false | ||
| + | |the driver will assume that commands detected on the BUS are always successful, thus no re-reading is performed to set the value of a datapoint | ||
| + | |||
| + | |- | ||
| + | |||
| + | |localport | ||
| + | | | ||
| + | |<port_number> | ||
| + | |specifies the port used locally by HSYCO to communicate with the KNXnet/IP gateway. This option might be necessary when employing network address translation (NAT) | ||
| + | |||
| + | |} | ||
Revision as of 15:34, 16 December 2013
Options
| ID | Default | Values | Description |
|---|---|---|---|
| gui | true | true | enable automatic support of Web GUI objects to show the system status and intercept control buttons |
| false | disable support for the Web GUI | ||
| 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 | ||
| discovery | true | true | automatically creates the list of all detected datapoints with type DPT 1 and the defined virtual datapoints in the systemtopo.txt file |
| false | auto-detect for devices is disabled | ||
| fromevents | false | true | generates events for commands sent on the KNX BUS reporting the source address and the value of the command |
| false | disable command events | ||
| readaftercommand | false | true | forces the driver to read the value of a datapoint after a command is sent to it |
| false | the driver will assume that commands detected on the BUS are always successful, thus no re-reading is performed to set the value of a datapoint | ||
| localport | <port_number> | specifies the port used locally by HSYCO to communicate with the KNXnet/IP gateway. This option might be necessary when employing network address translation (NAT) |
