Difference between revisions of "Trouble Shooting"

 
(7 intermediate revisions by one user not shown)
Line 2: Line 2:
 
[[Category:FAQ]]
 
[[Category:FAQ]]
 
[[Category:Documentation]]
 
[[Category:Documentation]]
[[Category:Specifications]]
+
[[Category:HowTo Video]]
[[Category:Features]]
+
{{PageHeading|
'''First make sure you have watched the videos about configuring your system for the AlarmDecoder'''
+
'''Make sure that you have read the Quick Start guide and watched the installation videos found in the [[Getting_Started|Getting Started]] section.'''
 
+
}}
<center><video type="youtube">K7BOHLq8tGg</video></center>
+
<center>This video discusses panel configuration as well as physical connection to the alarm system</center>
+
----
+
 
+
<center><video type="youtube">MaHrJYkQDhY</video></center>
+
<center>This video discusses connecting your AlarmDecoder to a PC</center>
+
----
+
 
+
<center><video type="youtube">G3qxiiBBJxg</video></center>
+
<center>This video discusses connecting your AlarmDecoder to a Mac</center>
+
----
+
  
  
 
==Troubleshooting Steps==
 
==Troubleshooting Steps==
# does the AD2* have power?
+
# Does the AlarmDecoder have power?
#* make sure the LED on the AD2* device is flashing about 1 cycle a second
+
#* Make sure the LED on the AlarmDecoder is flashing about once per second.
#* check your power connections if you do not see LED flashing
+
#* Check your power connections if you do not see the LED flashing.
# does the connected computer show an attached device.
+
# Does the connected computer show an attached device?
#* For windows look in device manager
+
#* Windows: Confirm the device is present in the Device Manager.
#** On some installs of windows it is necessary to enable the VCP option for the driver
+
#** On some installs of windows it is necessary to enable the VCP option for the driver.
#* for OSX and Linux look in /dev
+
#* OSX/Linux: Check your syslog and look in ''/dev''.
 +
# Can you communicate with the device with a terminal program?
 +
## Open the device with your favorite terminal program.  We suggest one of the following:
 +
##* Windows: [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY]
 +
##*# Select the ''Serial'' option.
 +
##*# Enter the COM port number.  You can look this up in Device Manager.
 +
##*# Enter the speed.
 +
##*#* AD2USB & AD2Pi: 115200
 +
##*#* AD2Serial: 19200
 +
##*# Click ''Open''
 +
##* OSX/Linux: screen
 +
##*# Open a terminal
 +
##*# Locate your device by checking syslog or your ''/dev'' directory
 +
##*# Execute ''screen [device] [baudrate]''
 +
##*#* Baudrate:
 +
##*#** AD2USB & AD2Pi: 115200
 +
##*#** AD2Serial: 19200
 +
## Confirm that you can reboot your Alarm Decoder by typing: '''='''
 +
## Make sure you cleanly exit your terminal program.
 +
##* PuTTY: Click the '''X'''
 +
##* screen: Ctrl + A + K
 +
# Are you seeing messages from your panel?
 +
## Confirm that the AlarmDecoder is wired correctly to your panel.  See the videos above or the quickstart document.
 +
## Confirm that you (or your alarm company) have added a keypad to your panel for the AlarmDecoder.
 +
## Confirm the correct keypad address is configured on the device by typing '''!''' and going through the prompts.
 +
# Can you send key presses to the panel?
 +
## Type '''*''' (asterisk) You should see ''Sending.done'' and the panel should respond with the current status.
 +
##* There may be up to five periods between 'Sending' and 'done'.  If there are five the keypress has timed out and you should confirm your wiring.

Latest revision as of 23:34, 21 December 2013

Make sure that you have read the Quick Start guide and watched the installation videos found in the Getting Started section.


Troubleshooting Steps

  1. Does the AlarmDecoder have power?
    • Make sure the LED on the AlarmDecoder is flashing about once per second.
    • Check your power connections if you do not see the LED flashing.
  2. Does the connected computer show an attached device?
    • Windows: Confirm the device is present in the Device Manager.
      • On some installs of windows it is necessary to enable the VCP option for the driver.
    • OSX/Linux: Check your syslog and look in /dev.
  3. Can you communicate with the device with a terminal program?
    1. Open the device with your favorite terminal program. We suggest one of the following:
      • Windows: PuTTY
        1. Select the Serial option.
        2. Enter the COM port number. You can look this up in Device Manager.
        3. Enter the speed.
          • AD2USB & AD2Pi: 115200
          • AD2Serial: 19200
        4. Click Open
      • OSX/Linux: screen
        1. Open a terminal
        2. Locate your device by checking syslog or your /dev directory
        3. Execute screen [device] [baudrate]
          • Baudrate:
            • AD2USB & AD2Pi: 115200
            • AD2Serial: 19200
    2. Confirm that you can reboot your Alarm Decoder by typing: =
    3. Make sure you cleanly exit your terminal program.
      • PuTTY: Click the X
      • screen: Ctrl + A + K
  4. Are you seeing messages from your panel?
    1. Confirm that the AlarmDecoder is wired correctly to your panel. See the videos above or the quickstart document.
    2. Confirm that you (or your alarm company) have added a keypad to your panel for the AlarmDecoder.
    3. Confirm the correct keypad address is configured on the device by typing ! and going through the prompts.
  5. Can you send key presses to the panel?
    1. Type * (asterisk) You should see Sending.done and the panel should respond with the current status.
      • There may be up to five periods between 'Sending' and 'done'. If there are five the keypress has timed out and you should confirm your wiring.