Changes between Version 21 and Version 22 of WikiStart


Ignore:
Timestamp:
2012-02-23 01:03:17 (13 years ago)
Author:
strangely
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v21 v22  
    33= Introduction = 
    44 
    5 The DSC Alarm plug-in is a [http://wiki.micasaverde.com/index.php/Luup_Plugins Luup component] that connects Vera to a DSC !PowerSeries alarm panel such as the !PowerSeries 1616, 1832 and 1864 panels, via the IT-100 RS232 Keybus module. 
     5The DSC Alarm plug-in is a [http://wiki.micasaverde.com/index.php/Luup_Plugins Luup component] that connects Vera to a DSC !PowerSeries alarm panel such as the !PowerSeries 1616, 1832 and 1864 panels, via an IT-100 or *Envisalink IP170/2DS Keybus module. 
    66Through this interface, events occurring within the Alarm Panel are exposed to Vera including the status of any attached Doors, Windows, Motion Sensors.   
    7  
     7*Currently the Envisalink 170/2DS is considered as Beta and can only be used if the 170/2DS has beta firmware with the TPI functions. 
    88Each of these is exposed as a ''Motion Sensor'' to Vera, so that standard [http://wiki.micasaverde.com/index.php/Scenes Scenes] (Lights, Notifications, etc) can be established in Vera based upon events occurring within the Alarm Panel. 
    99 
    1010Additionally, the interface exposes the current Armed State, Stay Armed State and whether the Alarm is in Breach.  These are also exposed in a ''Scene-aware'' manner so that Vera can respond to them. 
    1111 
    12 '''WARNING: This plug-in ''will probably not'' work with the "UI3" (versions 1.1.x) of Vera's firmware. 
     12'''WARNINGS:  
     13* This plug-in ''will probably not'' work with the "UI3" (versions 1.1.x) of Vera's firmware. 
     14* If the Plugin is updated from the files contained here >0.35, or if it automatically updates from an app store based version, then it will change the device ID's of any sensors that are set up as "D\doorZones" 
     15  The above will only be a problem if these doorZone sensors have been set up at all as triggers for scenes, and these will have to reset after updating 
     16  To avoid the above scenario the following changes should be made prior to updating: 
     17   
     18  If you currently have a setup with the following initialization parameters 
     19   
     20      doorZones=1,2 
     21      motionZones=3,4,5 
     22   
     23  Then they must be changed prior to the update being made as follows,  
     24   
     25      doorZones= 
     26      motionZones=1,2,3,4,5 
     27   
     28  They must all be set up under the motionZones parameter (the front, ordering is important) 
     29  Once the above is saved, then it will be safe to proceed with updating the plugin. 
    1330 
    1431 
    … …  
    1633 
    1734 
     35The DSC Alarm Panel uses a proprietary interface bus, called Keybus, to talk to the devices connected to it.  The IT100 Serial module and IP170/2DS Ethernet Modules are Keybus devices that acts as a bridge between the Alarm Panel. 
    1836 
    19 The DSC Alarm Panel uses a proprietary interface bus, called Keybus, to talk to the devices connected to it.  The IT100 Serial module is a Keybus device that acts as a bridge between the Alarm Panel. 
     37 
     38The IT100 interface or IP170/2DS sits on the Keybus interface where other devices such as Keypads are normally wired, it is able to interact with Alarm Panel messages in order to interface with a Home Automation controller such as Vera. Similarly, these messages can be sent from the Home Automation device back to the DSC Alarm Panel to perform various actions. 
    2039 
    2140[[Image(IT100.jpg, align=center)]] 
    2241 
    23 The IT100 interface sits on the Keybus interface where other devices such as Keypads are normally wired, it is able to interact with Alarm Panel messages in order to interface with a Home Automation controller such as Vera. Similarly, these messages can be sent from the Home Automation device back to the DSC Alarm Panel to perform various actions. 
    24  
    25 To connect the IT100 to Vera, a user will have to decide the best method to interface with Vera. This can be accomplished with any of the following options: 
     42If the IT100 is to be used with Vera, the user will have to decide the best method to interface It. This can be accomplished with any of the following options: 
    2643 
    2744* Direct Connection to a USB to RS232 serial adapter thats supported by Vera such as [http://www.futureelectronics.com/en/Technologies/Product.aspx?ProductID=UC232R10FUTURETECHNOLOGYDEVICES2297802 this ] one. 
    2845* Wired Ethernet Connection via an IP to RS232 serial adapter such as WIZnet device like [http://www.sparkfun.com/commerce/product_info.php?products_id=9476 this] one. 
    29 * !WiFi to RS232 serial adapter such as [http://www.mouser.com/ProductDetail/Roving-Networks/RN-134/?qs=sGAEpiMZZMvdqMP%2faZ%252bGClQs06owUsC0 this] one. 
     46* WiFi to RS232 serial adapter such as [http://www.mouser.com/ProductDetail/Roving-Networks/RN-134/?qs=sGAEpiMZZMvdqMP%2faZ%252bGClQs06owUsC0 this] one. 
    3047 
     48[[Image(2DS.png, align=center)]] 
     49 
     50The Envisalink IP170/2DS does not need a serial adapter, and only needs to be connected via Ethernet. 
    3151 
    3252== Terminology == 
    … …  
    3656  a collection of Zones.  Typically there is a single Area in a house.  Larger houses are often split into separate Areas (Upstairs vs Downstairs). External buildings such as Garages and Guest houses are also candidates for additional Areas. 
    3757Keybus:: 
    38   DSC Security proprietary protocol. This protocol is used for communications between DSC System components, such as the IT100, T-Link IP modules, Zone Expanders, and the System Keypads. 
     58  DSC Security proprietary protocol. This protocol is used for communications between DSC System components, such as the IT100, T-Link IP modules, Zone Expanders, Envisalink IP170/2DS, and the System Keypads. 
    3959Remote control:: 
    4060  a Key chain remote control device, used to Arm (Lock), Disarm (Unlock) or set a Panic Alarm 
    … …  
    84104  === Event processing === 
    85105 
    86 After startup, the system is set running. It receives events and, for those of interest, it translates them into !MotionSensor values to set upon it's Child Devices, in addition to setting Variables directly on the Alarm Area device 
     106After startup, the system is set running. It receives events and, for those of interest, it translates them into MotionSensor values to set upon it's Child Devices, in addition to setting Variables directly on the Alarm Area device 
    87107 
    88108 
    … …  
    103123  * ''Police Panic'' - Submit a request to trigger the Alarm Partition's Police Panic - UI4 and above only 
    104124 
    105 NOTE: The Alarm plugin code disables these Actions by default.  They must be enabled prior to using them in a Scene definition.  Since MiOS stores these scene definitions, including any Parameters supplied (eg PINCode) use of these features may constitute a security risk - use at your own risk. 
     125NOTE: The Alarm plugin code disables these Actions by default. They must be enabled prior to using them in a Scene definition.  Since MiOS stores these scene definitions, including any Parameters supplied (eg PINCode) use of these features may constitute a security risk - use at your own risk. 
    106126 
    107127==== Alarm Area Variables ==== 
    108 This Alarm Panel implements a !DeviceType that gives it the following Variables (through it's !ServiceStateTable).  These can be used for Luup scripting: 
     128This Alarm Panel implements a DeviceType that gives it the following Variables (through it's ServiceStateTable).  These can be used for Luup scripting: 
    109129   
    110     * ''Disarmed'' - Set whenever the Alarm Area is Disarmed (not Armed and not !StayArmed) 
     130    * ''Disarmed'' - Set whenever the Alarm Area is Disarmed (not Armed and not StayArmed) 
    111131    * ''Armed'' - Set when the user requests the Alarm Area to Arm, Force Arm, Stay Arm or Instant Arm the Area 
    112     * ''!StayArmed'' - Set when the user request the Alarm Area to Stay Arm or Instant Arm the Area 
     132    * ''StayArmed'' - Set when the user request the Alarm Area to Stay Arm or Instant Arm the Area 
    113133    * ''Breach'' - set when the Alarm Area is in Breach (Siren, Silent etc) 
    114134 
    … …  
    127147  For three partitions enter '''1,2,3''' etc etc... 
    128148 
    129 Under the different Zone fields, enter the zone numbers in the same type of sequence. By default it will display '''1,2,3,4,5,6''' in ''!DoorZones''.  
     149Under the different Zone fields, enter the zone numbers in the same type of sequence. By default it will display '''1,2,3,4,5,6''' in ''DoorZones''.  
    130150 Note you will need to know which Zones are set up which on your panel. They may not be in sequence (per the above), and can be entered depending on their type in any of the three Zone variables. 
    131151 
    132 If remote Arming and Disarming is not required from Vera, then exit and save; however if this is required then stay in this screen and enter one of the following into the ''!EnableRemoteArm'' variable: 
     152If remote Arming and Disarming is not required from Vera, then exit and save; however if this is required then stay in this screen and enter one of the following into the ''EnableRemoteArm'' variable: 
    133153 
    134154* '''disarm''' (Least secure as all functions are available including disarm) 
    … …  
    148168 
    149169* If labels have previously been programmed in a keypad, then attempt a label broadcast from the keypad they were originally programmed from by entering *8[Installer code]*998* 
    150 * If labels were never programmed then they can be programmed them from an alpha numeric keypad and a subsequent a label broadcast 
     170* If labels were never programmed then they can be programmed them from an alpha numeric keypad and a subsequent label broadcast 
    151171* Program the labels to the panel using DSC DLS software 
    152172 
    153  
    154 = Discussion = 
     173= Troubleshooting IT100 issues= 
     174   
     175If after setting everything up the plugin does not seem to work, then its recommended to try some of the following: 
     176 * If using a USB to serial adapter, check that its a supported type. 
     177 * Check that the cabling is correct, or replace the serial cable (if used); note that the IT100 does not need a Null modem cable and the pins of the DB9 should be wired 2>2, 3>3 and 9>9 
     178 * If the plugin was downloaded from the UI4 apps section, then delete it and reinstall the plugin from the files linked here. 
     179 * If using a WIZnet adapter make sure its setup correctly as per [http://forum.micasaverde.com/index.php/topic,5154.msg34061.html#msg34061 this post:] and especially that its "Operation Mode" is set up as Server. 
     180  
     181  
     182 = Discussions = 
    155183 
    156184  * [http://forum.micasaverde.com/index.php?topic=5154.0 Main thread] 
    157185  * [http://forum.micasaverde.com/index.php?topic=5794.0 Serial adapter discussion] 
    158   * [http://forum.micasaverde.com/index.php?topic=3713.0 Standardization effort] 
     186  * [http://forum.micasaverde.com/index.php?topic=3713.0 Standardization effort]   
     187  * [http://forum.micasaverde.com/index.php/topic,5154.msg60596.html#msg60596 Building a DLS programming cable]   
    159188 
    160189 
    161 = References = 
     190= References and Links = 
    162191 
    163   * [http://cms.dsc.com/download.php?t=1&id=10910 IT100 developer guide]   
     192  * [http://cms.dsc.com/download.php?t=1&id=10910 IT100 developer guide] 
     193  * [http://www.homesecuritystore.com/p-548-kit32-219-dsc-power-1832-wireless-ready-security-kit.aspx A good base system] 
    164194  * [http://www.lua.org/manual/5.1 Lua 5.1 Reference Manual] 
    165195  * [http://lua-users.org/wiki/LuaTutorial Lua-users Lua Tutorial]