supported_hardware:ad2usb
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| supported_hardware:ad2usb [2014/09/28 15:17] – external edit 127.0.0.1 | supported_hardware:ad2usb [2023/02/13 14:52] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 19: | Line 19: | ||
| All zones setup in the system can also be configured to XTension units. These are receive only and the units in XTension cannot be used to trigger a zone in the alarm panel. Create a unit in XTension addressed starting with “ZONE” and then the 3 digit zone number. For example, an XTension unit with the address “ZONE003” will correspond to Zone 3 in the alarm panel. | All zones setup in the system can also be configured to XTension units. These are receive only and the units in XTension cannot be used to trigger a zone in the alarm panel. Create a unit in XTension addressed starting with “ZONE” and then the 3 digit zone number. For example, an XTension unit with the address “ZONE003” will correspond to Zone 3 in the alarm panel. | ||
| + | Prior to XTension version 9.4 only zones actually reported as faulted would send commands to XTension. Other zone messages were ignored. This means that if you had created a non-fault zone for some other kind of sensor that zone would not have updated in XTension. In version 9.4 I changed the zone handling so that non-fault zones that send an alarm message will also update their XTension units when they are alarmed. | ||
| ===Individual special units=== | ===Individual special units=== | ||
| * address: “ARMEDAWAY” currently read only, is the panel armed away | * address: “ARMEDAWAY” currently read only, is the panel armed away | ||
| Line 43: | Line 44: | ||
| ===still to complete=== | ===still to complete=== | ||
| At this moment there is no communication from XTension INTO the panel except the function keys and the virtual zones. Otherwise we can monitor things quite well. Future versions will bring more abilities for control. There remain questions about the clearing of the zones, they may read alarmed after the zone has cleared if other zones are still faulted, or they may clear immediately after faulting. This software doesn’t currently support the idea of “partitions” with separate pin codes. If your setup is configured into partitions this may or may not be useful for you yet. | At this moment there is no communication from XTension INTO the panel except the function keys and the virtual zones. Otherwise we can monitor things quite well. Future versions will bring more abilities for control. There remain questions about the clearing of the zones, they may read alarmed after the zone has cleared if other zones are still faulted, or they may clear immediately after faulting. This software doesn’t currently support the idea of “partitions” with separate pin codes. If your setup is configured into partitions this may or may not be useful for you yet. | ||
| + | |||
| + | ===Notes: | ||
| + | Added in XTension version 9.4 the AD2USB interface will now send a reboot message to the device if you use the [[dictionary: | ||
| + | |||
| - | ===this is still alpha=== | ||
| - | This software is hardly tested yet and not feature complete. There is a known issue with the data from the AD2USB being garbled if there is a comm error on the panel. I have added code to filter this out as best as possible, but if the panel is in a comm error state there may be incorrect triggers of the XTension units. | ||
supported_hardware/ad2usb.1411917431.txt.gz · Last modified: 2023/02/13 14:51 (external edit)