Difference between revisions of "Troubleshoot DigiGate Systems"

From PTI Security Systems
Jump to: navigation, search
(Created page with " == RS-485 Network Troubleshooting ==")
 
 
(29 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
<div class="linkshow" id="HTDJ3Rlinkshow">
 +
<div class="linkhide" id="HTDJ3Rlinkhide">
 +
<div>[[#HTDJ3Rlinkshow|How do I do a J3 reset of the Syscon?]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#HTDJ3Rlinkhide|Hide]]</div>
 +
<br \>
 +
A J3 reset of the [[Syscon]] may be needed in certain situations to re-establish communications from the Syscon to the PC that runs the [[DigiWin]] program.  Generally, this is only done if a simple reset does not solve the issue.
  
== [[RS-485 Network Troubleshooting]] ==
+
'''''This procedure will erase any codes currently stored in the Syscons memory.  You should check first that any communication errors are not the result of bad connections, incorrect setups, or problems with the PCs com port.'''''
 +
 
 +
#Locate the power supply input to the System Controller box. It appears like a miniature microphone cord connection near the bottom right outside corner of the box.<br \>
 +
#Disconnect the power supply from the System Controller box by unscrewing the connector and unplugging it.<br \>
 +
#At the System Controller box, open the cover and locate the “J3” jumper . It is located to the left of the red power light on the back “System Controller” board.<br \>
 +
#Pull the “J3” jumper off the circuit board pins (be careful not to lose it).<br \>
 +
#Wait 10 seconds.<br \>
 +
#Replace the “J3” jumper.<br \>
 +
#Reconnect the power supply to the System Controller box.<br \>
 +
#Reset the System Controller by pressing the “RESET” button to the left of the J3 Jumper. *If no “RESET” button is found, jump connections 1 & 3 of the P1 connector on the same board with a wire or paperclip.<br \>
 +
#Repeat Step 2 above.  The software setups and codes will now need to be reloaded from the Digiwin program on the PC to the Syscon. To do this, continue with Steps 10 through 22 below.<br \>
 +
#At the DigiGate software, click on the “Utility” menu.<br \>
 +
#In the “Utility” menu, click “Clear SysCon.”<br \>
 +
#"Confirm - Clear System Controller?” dialogue box appears.<br \>
 +
#In the “Confirm - Clear System Controller?” dialogue box, click “Yes.”<br \>
 +
#A “Cold Start” message may appear on the Activity Log.<br \>
 +
#In the “Utility” menu, click “Set Controller.”<br \>
 +
#“Set System Controller” dialogue box appears.<br \>
 +
#In the “Set System Controller” dialogue box, click “OK.”<br \>
 +
#The Set Controller process initiates, and then finishes.<br \>
 +
#In the “Utility” menu, click “Download All.”<br \>
 +
#“Download All Units” dialogue box appears.<br \>
 +
#In the “Download All Units” dialogue box, click “OK.”<br \>
 +
#The Download All process initiates, and then finishes.<br \>
 +
<div style="float: right;">[[#HTDJ3Rlinkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
<div class="linkshow" id="BPFWDlinkshow">
 +
<div class="linkhide" id="BPFWDlinkhide">
 +
<div>[[#BPFWDlinkshow|I'm seeing a lot of Bad Password messages from devices that have Weigand card readers.  How do I fix this?]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#BPFWDlinkhide|Hide]]</div>
 +
<br \>
 +
Occasionally an RS485 keypad with a Weigand device, such as a proximity card reader, attached to it can cause “Bad Password” messages to appear in the activity log when no activity is taking place at the reader.  This is caused due to noise on the data wires from the reader being interpreted as a card read.
 +
 
 +
This noise, and the resulting bad passwords, can be greatly reduced by adding two capacitors to the connections on plug P4 where the Weigand device is connected to the circuit board.
 +
 
 +
Parts Needed:
 +
 
 +
*Two .01uf ( micro-farad ) non-polarized Capacitors.<br \>
 +
 
 +
'''Connection Instructions:'''
 +
 
 +
#On plug P4, loosen the terminal screws for terminals 3, 4 and 6.<br \>
 +
#Trim the leads on the capacitors to about .5” ( 15mm ) long.<br \>
 +
#Place one capacitor in terminals 4 and 6, as shown below.[[File: Weigand_Cap-1.png|none]]<br \>
 +
#Place the other capacitor in terminals 3 and 6, as shown below.[[File: Weigand_Cap-2.png|none]]<br \>
 +
#Tighten the terminals, making sure that the wires from the Weigand device, and the capacitors, are held securely.
 +
 
 +
<div style="float: right;">[[#BPFWDlinkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
<div class="linkshow" id="TSDAlinkshow">
 +
<div class="linkhide" id="TSDAlinkhide">
 +
<div>[[#TSDAlinkshow|I replaced some old Matrix door muxes but I'm still having false alarms.  How do I troubleshoot this?]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#TSDAlinkhide|Hide]]</div>
 +
<br \>
 +
When replacing old Matrix style multiplexers, there may be a need to troubleshoot existing problems with the system. These problems are broken down into two groups. Door problems and RS485 communication problems.<br \>
 +
 
 +
Just the act of replacing the old Matrix mux with a Uni-Mux should solve any RS485 problems that you may have had that were cause by the old board, or by ground loops in the electrical system. The Unimux has a optically isolated network, rated up to 500 volts AC. This eliminates ground loop problems. If you continue to have RS485 problems after replacing the board you can use [[Troubleshoot_DigiGate_Systems#RS485TSDlinkshow|these]] instructions to troubleshoot, or you can contact [https://support.ptisecurity.com PTI Technical Support].<br \>
 +
 
 +
Door alarm problems are usually caused by one or more of the following situations.
 +
#Door switch alignment. The magnet and switch do not align correctly with each other.<br \>
 +
#Loose connections. The connection of the switch to the trunk wire, or the trunk wire to the MUX board is faulty.<br \>
 +
#Shorted wires. The trunk cables have short circuits between wires in the trunk cable, or from the wires to the metal frame ( ground ) of the building.
 +
 
 +
'''Door Switch Alignment and Loose Connections:'''
 +
 
 +
False alarms due to door switch alignment problems usually manifest themselves as a single unit alarming intermittently, or a single unit constantly showing an open condition on the LCD screen of the Unimux. This type of failure can also be caused by a loose connection or damaged wire from the switch to the trunk wires, or in rare instances a bad switch. If you have these symptoms, it will be necessary to obtain access to the interior of the unit to check the switch for proper alignment to the magnet, the integrity of the switch wire, and its connections.
 +
 
 +
'''Shorted Wires:'''
 +
 
 +
When wires in the trunk cable short together, or short to the metal frame / walls of the building, then the symptoms will be multiple units alarming at the same time. Shorted wires in the trunk cable are usually caused by poor workmanship in installing the cable, resulting in damage to the cable when it was being pulled through the building.
 +
 
 +
Depending on which wires are shorted, the LCD screen on the Unimux will display a “block” of units in an open status.
 +
 
 +
Note: The screens shown below assume that all 20 doors on a trunk cable are connected and are closed.
 +
 
 +
#If a wire connected to an odd numbered terminal on the plug is shorted to ground, a block of four units will show as open.[[File: DATroubleshooting-1.png|none]]<br \>
 +
#If a wire connected to any even numbered terminal is shorted to ground, then all 20 doors on that daughterboard will show open.<br \>
 +
#If two odd numbered terminal wires are shorted together, eight doors will show open.
 +
 
 +
Tracking down trunk cable wires that are shorted to ground in a building that has been rentedout is difficult. The Unimux does give some advantage in that only the doors on the particular trunk that is shorted will show an alarm condition. (With the older matrix mux, a shorted wire could cause all 80 doors on the mux to alarm at the same time).
 +
 
 +
If you know which trunk cable is shorted, then the possibilities are narrowed down. Armed with a mux / slot report and a diagram showing the cable routing, units can be opened to track down the location of the short circuit.
 +
 
 +
'''Note that in many cases, these short circuits are intermittent. And may only last for a few seconds at a time.'''
 +
 
 +
Places to look for cable damage include:
 +
 
 +
#Penetrations through walls, where conduit or protective bushings were not used.[[File: DATroubleshooting-2.png|none]]<br \>
 +
#Where cables run over the tops of unit walls and past sharp or pointed edges.[[File: DATroubleshooting-3.png|none]]<br \>
 +
#Wires getting pinched between two surfaces.[[File: DATroubleshooting-4.png|none]]<br \>
 +
#Ends of the trunk cable not insulated correctly.[[File: DATroubleshooting-5.png|none]]<br \>
 +
#Wire not stripped correctly, wires were nicked, and the cable then touches metal.[[File: DATroubleshooting-6.png|none]]
 +
 
 +
<div style="float: right;">[[#TSDAlinkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
<div class="linkshow" id="RS485TSDlinkshow">
 +
<div class="linkhide" id="RS485TSDlinkhide">
 +
<div>[[#RS485TSDlinkshow|RS-485 Network Troubleshooting for DigiGate systems.]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#RS485TSDlinkhide|Hide]]</div>
 +
<br \>
 +
Note:  These troubleshooting steps assume that the network has been wired in accordance with [[PTI Security Systems specifications for Digitech RS-485 systems]].
 +
 
 +
*'''Troubleshooting a new site that is just being installed'''
 +
 
 +
The following troubleshooting steps are for a '''new site''' that has not been up and running before.
 +
 
 +
Symptom: No boards come online. (When a “[[General_questions_for_DigiGate_systems#HDISTSlinkshow|Set Controller]]"<ref>Setting the controller is done in the [[DigiWin]] program, under the Utilities Menu.</ref> is performed, none of the boards on the RS-485 network show an on-line status report.  This includes the [[DigiGraphics]])
 +
 
 +
# Inside the [[Syscon]], check the status of the two RS-485 LED’s on the lower board (Some Syscons may only have one board installed). [[File: RS485Troubleshooting1.png|none]]<br />
 +
# The Normal condition for the RS485 lights is for both of them to be constantly flashing.<br />
 +
# If the RCV light is on solid, then goes off for a split second as the XMT light comes on, and repeats this every two seconds, then there is a short circuit between the positive and the negative lead of the RSX-485 bus.  This short could be at any point in the RS-485 network.  See the next section in this answer for instructions on locating a short circuit.<br />
 +
# If the RCV or the XMT lights do not light up at all, or if the RCV light is on solid and the XMT light does not flash, then the [[Syscon]] is not polling the network.  Check the programming of the [[DigiWin]] software and make sure that the RS-485 network boards are defined correctly in the software setups.<ref>To check the system settings, in the [[DigiWin]] program select the "Report" Menu, then select "Misc. Reports", then "Setup Info".</ref><br />
 +
# If the XMT light flashes once every two seconds, and the RCV light does not come on, then there is a wiring problem in the RS-485 bus ( Open circuit or miswired connection ), or a problem with the MUX boards.  See page 4 for instructions on troubleshooting these problems.
 +
 
 +
 
 +
----
 +
*'''Troubleshooting a Short Circuit'''
 +
 
 +
#Disconnect the RS485 line that goes from the [[Syscon]] to the [[DigiGraphics]].  Check to see if the RS485 lights have returned to normal operation.  If they have,<br />
 +
#*Inspect the line that runs to the [[DigiGraphics]] for shorts.<br />
 +
#*Check the wires at the [[RS-485 converter]] ( Connected to the back of the [[DigiGraphics]] ) and make sure they are connected correctly.<br />
 +
#*Replace the RS485 converter at the [[DigiGraphics]].<br />
 +
#If your system has a single branch of the RS-485 network that is connected to the controller (As shown in the example below), then start at the far end of the network and disconnect the last device from the RS-485 network.  If your system has two branches, then you should disconnect one branch from the system controller at a time, to determine which branch the short circuit is in.  Once you have determined which branch it is in, then start troubleshooting that single branch. (The system should not have more than 2 branches, and it can only branch at the system controller.).  [[File: RS485Troubleshooting2.png|none]]<br />
 +
#Work your way back from the last device on the line towards the [[Syscon]], disconnecting each board from the RS-485 network.  Each time you disconnect a board, check the status lights inside the system controller to see if the short has been removed (The RCV light will no longer be on solid).  Once you disconnect a board and the lights change, then you will find that the short is either in the last box you disconnected, or in the line running to the next box in the chain.  This shows an example of how the lines were disconnected. [[File: RS485Troubleshooting3.png|none]].<br />Note:  When you are disconnecting the RS-485 wires from the boards, check all of the wire connections for correct polarity and for any short circuits as you are doing this.<br />
 +
#Check each of the following areas for the short circuit after you have determined which box is at fault.<br />
 +
#*Check the outgoing wire to the next RS485 device first (If applicable).  Disconnect it from the boards and read it with a ohmmeter.  Should read an open circuit.<br />
 +
#*The circuit board itself can be at fault.  This requires replacement of the board.
 +
 
 +
 
 +
----
 +
*'''Other wiring problems with the RS485 Network'''
 +
 
 +
If the RS-485 XMIT light flashes by itself for a few seconds, then both lights flash for a few seconds, then the system is polling for a board and is not getting a response from it.  Look for the following:
 +
 
 +
#Incorrect polarity of the wires when connected to the board.<br />
 +
#On connector P2 of the [[Digitech Multiplexers|UniMux]] board or keypad board, check that the connector is not crimped down on the insulation of the wire instead of the wire itself.<br />
 +
#Check the continuity of the wires in the system.<br />
 +
#Check [[DigiWin]] software programming, to make sure the software is only polling boards that are on the system.<br />
 +
#Check the address settings of the various MUX boards to see if the correct MUX addresses are present and that you do not have any duplicate addresses set.
 +
 
 +
 
 +
It can be useful to also check the status of each MUX boxes RS-485 lights.  You should see the RCV light almost constantly flashing, with the XMIT light flashing at a slower rate.  The rate the XMIT flashes depends on the total number of devices on the system.  The more RS-485 devices the system has, the slower a board's XMIT light will flash.
 +
 
 +
 
 +
----
 +
*'''Troubleshooting a site that was previously working'''
 +
 
 +
Use the following steps to troubleshoot a RS-485 network that was working when installed, but has failed at some point in time after the initial installation.
 +
 
 +
Again, these troubleshooting steps are only valid for systems that are [[PTI Security Systems specifications for Digitech RS-485 systems|installed as per Digitech specifications.]]  '''''It is possible for a system that is not installed to specification to work for a time, and then fail or operate intermittently.'''''
 +
 
 +
The three different failure modes for these systems are:
 +
 
 +
#Component failure.  This is when one of the boards on the system fails.  This may or may not be the direct result of a surge.  This type of problem usually manifests itself in one of two ways:<br />
 +
#*One board on the system goes “offline” and remains offline.<br />
 +
#*More than one or all RS-485 boards go offline, and may stay offline or switch back and forth over a period of time.<br />
 +
#External Damage:  This is damage to the wires in the RS-485 system.  This can be cause by wires that are unprotected and are damaged by a person.  Or it can also be a result of poor installation that allows the wires to be damaged while being installed, and the problem manifests itself later in the life of the system.<br />
 +
#Surge Damage:  This is caused by an electrical surge (lightning) that can damage the components on the MUX boards.  These problems can also show up as boards cycling on and offline.<br />
 +
 
 +
 
 +
The most efficient check that can be made at this point is to observe the status LEDs of the [[Syscon]] and the RS-485 devices.
 +
 
 +
#Check to make sure that the Digitech software has not been altered, and that all MUX boards are defined in the setups for the system.<br />
 +
#Check the system for shorted RS-485 lines.  Use the instructions at the beginning of this answer to look for short circuits.  A common occurrence is for a RS-485 line to have been “nicked” when it was pulled into conduit, and the moisture in the conduit shorts out the line.  Also RS-485 lines can become “pinched” or damaged inside of a building, causing a short to each other or to electrical ground.<br />
 +
#Isolate the system from the [[DigiGraphics]] converter.<br />
 +
#Use the “Divide & Conquer” method to isolate the system.  Start from the [[Syscon]] and connect one part of the system at a time to see if they work.  Use the [[DigiCom]] software tool to “poll” the RS-485 devices as you connect them one by one.  Once you connect the faulty device, the system will stop operating.<br />
 +
#Watch out for systems that appear to only malfunction at certain times of day.  For example, if a system works fine during the day and then starts to have offline problems at night, this is an indication that an electrical wiring problem may exist in the buildings the MUX boxes are attached to.  Typically this would be something in the lighting control circuit or its electrical panel.<br />
 +
 
 +
 
 +
==Notes==
 +
<references />
 +
<div style="float: right;">[[#RS485TSDlinkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
<div class="linkshow" id="TSS700Klinkshow">
 +
<div class="linkhide" id="TSS700Klinkhide">
 +
<div>[[#TSS700Klinkshow|Troubleshooting Standard 700 Keypads.]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#TSS700Klinkhide|Hide]]</div>
 +
<br \>
 +
This procedure will determine the origin of the keypad problem; which could be the keypad itself, the Keypad I/O Board, or the wiring between the two. This is a generalized method that can be used for several problems when you are just trying to narrow down the problem to the keypad, wiring harness or IO board.<br \>
 +
 
 +
'''Note:''' When a keypad has a whole row or column of numbers that does not work, the problem can be either the keypad or the Keypad Interface Board.  If a keypad has just a single number that does not work, it's usually the keypad itself that is the problem.
 +
 
 +
*Swap the Keypad with one known to work. (If you only have one standard keypad, jump to the next section.)<br \>
 +
*#Remove the 4 Keypad Mounting screws on the problem keypad.<br \>
 +
*#Gently remove the keypad from its housing.<br \>
 +
*#Remove the Keypad plug from the back of the keypad.[[File:DigiGate_Standard_Keypad_Back.png|none]]<br \>
 +
*#Take the keypad to a location that has a working keypad.<br \>
 +
*#Repeat the 3 steps above on the working keypad.<br \>
 +
*#Reverse the first 3 steps, installing the problem keypad where the working keypad was located. (You can only use one mounting screw to temporarily hold the keypad in place. Just don't lose them.)<br \>
 +
*#Take the good keypad to the location where you removed the problem keypad. Again reverse the first 3 steps, installing the working keypad where the problem keypad was located.<br \>
 +
*#Try both keypads and note the result.<br \>
 +
<br \>
 +
*If the problem moved with the keypad, the keypad is the cause and should be replaced or repaired. If the problem stayed at the gooseneck that originally had the problem, Continue with the next test.<br \>
 +
<br \>
 +
*Checking the Keypad I/O Board and the Wiring.<br \>
 +
*#On the Keypad I/O Board, remove the keypad plugs for the problem keypad and a working keypad. Mark each plug so that they are not confused.[[File:DigiGate IO Board Example.png|none]]<br \>
 +
*#Plug the keypad plug of the problem keypad into the socket where the working keypad plug was removed. (If you only have one keypad, it's probably plugged into the lower port of plug P3.  Move it to the top port.)<br \>
 +
*#Plug the keypad plug of the working keypad into the socket where the problem keypad plug was removed.<br \>
 +
*#Try both keypads and note the result.<br \>
 +
*If the problem is at the same keypad as before, the problem is in the eleven conductor keypad wire going to that keypad. This wire will have to be replaced. If the problem switched to the other keypad, the problem is in the Keypad I/O board, which must be replaced.<br \>
 +
 
 +
'''Note:''' You may occasionally run into a problem where a bad keypad or harness affects the other Digigate 700 keypads plugged into the same Keypad Interface Board. In those cases, you may need to try the individual keypads  without having the other harnesses plugged in. For instance a row of numbers is not working on three 700 kps.  Use the method described above, but only plug in one keypad or harness at the time. The keypad or harness causing the problem will exhibit the symptoms individually and the others will not.
 +
 
 +
<div style="float: right;">[[#TSS700Klinkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
 
 +
<!--
 +
Template for adding in a new question / answer.
 +
Where **** is displayed, substitute a shorthand tag for the question.
 +
For example, if the question is "How Do I Reset the Syscon?" it would be HDIRTSlinkshow &
 +
HDIRTSlinkhide.
 +
Do not edit the class=link attributes!
 +
Do not remove the # marks!
 +
Make sure you use a unique (for this page) shorthand tag.
 +
 
 +
<div class="linkshow" id="****linkshow">
 +
<div class="linkhide" id="****linkhide">
 +
<div>[[#****linkshow|Question text here]]</div>
 +
<div class="answer">
 +
<div style="float: right;">[[#****linkhide|Hide]]</div>
 +
<br \>
 +
*******answer text here********
 +
<div style="float: right;">[[#****linkhide|Hide]]</div>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
-->

Latest revision as of 09:40, 19 August 2015


A J3 reset of the Syscon may be needed in certain situations to re-establish communications from the Syscon to the PC that runs the DigiWin program. Generally, this is only done if a simple reset does not solve the issue.

This procedure will erase any codes currently stored in the Syscons memory. You should check first that any communication errors are not the result of bad connections, incorrect setups, or problems with the PCs com port.

  1. Locate the power supply input to the System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. box. It appears like a miniature microphone cord connection near the bottom right outside corner of the box.
  2. Disconnect the power supply from the System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. box by unscrewing the connector and unplugging it.
  3. At the System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. box, open the cover and locate the “J3” jumper . It is located to the left of the red power light on the back “System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices.” board.
  4. Pull the “J3” jumper off the circuit board pins (be careful not to lose it).
  5. Wait 10 seconds.
  6. Replace the “J3” jumper.
  7. Reconnect the power supply to the System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. box.
  8. Reset the System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. by pressing the “RESET” button to the left of the J3 Jumper. *If no “RESET” button is found, jump connections 1 & 3 of the P1 connector on the same board with a wire or paperclip.
  9. Repeat Step 2 above. The software setups and codes will now need to be reloaded from the Digiwin program on the PC to the Syscon. To do this, continue with Steps 10 through 22 below.
  10. At the DigiGate software, click on the “Utility” menu.
  11. In the “Utility” menu, click “Clear SysCon.”
  12. "Confirm - Clear System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices.?” dialogue box appears.
  13. In the “Confirm - Clear System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices.?” dialogue box, click “Yes.”
  14. A “Cold Start” message may appear on the Activity LogThe display window in the DigiGate program that shows the activities that occur at the system. For example: Code entries, bad passwords, alarms, doors opened and closed. etc. Can also refer to the program's database file that stores this information..
  15. In the “Utility” menu, click “Set ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices..”
  16. “Set System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices.” dialogue box appears.
  17. In the “Set System ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices.” dialogue box, click “OK.”
  18. The Set ControllerTerm for the Falcon XT, Falcon Base Unit, or Master Security computer that ‘controls’ AI Devices. process initiates, and then finishes.
  19. In the “Utility” menu, click “DownloadTo copy information from a main source or computer into a peripheral, for example copying a file from the internet into your local computer. All.”
  20. DownloadTo copy information from a main source or computer into a peripheral, for example copying a file from the internet into your local computer. All Units” dialogue box appears.
  21. In the “DownloadTo copy information from a main source or computer into a peripheral, for example copying a file from the internet into your local computer. All Units” dialogue box, click “OK.”
  22. The DownloadTo copy information from a main source or computer into a peripheral, for example copying a file from the internet into your local computer. All process initiates, and then finishes.


Occasionally an RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. keypad with a Weigand device, such as a proximity card reader, attached to it can cause “Bad PasswordA secret series of numbers or letters up to fifteen characters that allows an operator to access the StorLogix program.” messages to appear in the activity log when no activity is taking place at the reader. This is caused due to noise on the data wires from the reader being interpreted as a card read.

This noise, and the resulting bad passwords, can be greatly reduced by adding two capacitors to the connections on plug P4 where the Weigand device is connected to the circuit board.

Parts Needed:

  • Two .01uf ( micro-farad ) non-polarized Capacitors.
    Connection Instructions:
  1. On plug P4, loosen the terminal screws for terminals 3, 4 and 6.
  2. Trim the leads on the capacitors to about .5” ( 15mm ) long.
  3. Place one capacitor in terminals 4 and 6, as shown below.
    Weigand Cap-1.png

  4. Place the other capacitor in terminals 3 and 6, as shown below.
    Weigand Cap-2.png

  5. Tighten the terminals, making sure that the wires from the Weigand device, and the capacitors, are held securely.


When replacing old Matrix style multiplexers, there may be a need to troubleshoot existing problems with the system. These problems are broken down into two groups. Door problems and RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. communication problems.

Just the act of replacing the old Matrix mux with a Uni-MuxDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. should solve any RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. problems that you may have had that were cause by the old board, or by ground loops in the electrical system. The Unimux has a optically isolated network, rated up to 500 volts AC. This eliminates ground loop problems. If you continue to have RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. problems after replacing the board you can use these instructions to troubleshoot, or you can contact PTI Technical Support.

Door alarm problems are usually caused by one or more of the following situations.

  1. Door switch alignment. The magnet and switch do not align correctly with each other.
  2. Loose connections. The connection of the switch to the trunk wire, or the trunk wire to the MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. board is faulty.
  3. Shorted wires. The trunk cables have short circuits between wires in the trunk cable, or from the wires to the metal frame ( ground ) of the building.

Door Switch Alignment and Loose Connections:

False alarms due to door switch alignment problems usually manifest themselves as a single unit alarming intermittently, or a single unit constantly showing an open condition on the LCD screen of the Unimux. This type of failure can also be caused by a loose connection or damaged wire from the switch to the trunk wires, or in rare instances a bad switch. If you have these symptoms, it will be necessary to obtain access to the interior of the unit to check the switch for proper alignment to the magnet, the integrity of the switch wire, and its connections.

Shorted Wires:

When wires in the trunk cable short together, or short to the metal frame / walls of the building, then the symptoms will be multiple units alarming at the same time. Shorted wires in the trunk cable are usually caused by poor workmanship in installing the cable, resulting in damage to the cable when it was being pulled through the building.

Depending on which wires are shorted, the LCD screen on the Unimux will display a “block” of units in an open status.

Note: The screens shown below assume that all 20 doors on a trunk cable are connected and are closed.

  1. If a wire connected to an odd numbered terminal on the plug is shorted to ground, a block of four units will show as open.
    DATroubleshooting-1.png

  2. If a wire connected to any even numbered terminal is shorted to ground, then all 20 doors on that daughterboardModules that are installed in a Digitech Unimux. There are 3 different types of daughterboards, each with a different function. will show open.
  3. If two odd numbered terminal wires are shorted together, eight doors will show open.

Tracking down trunk cable wires that are shorted to ground in a building that has been rentedout is difficult. The Unimux does give some advantage in that only the doors on the particular trunk that is shorted will show an alarm condition. (With the older matrix mux, a shorted wire could cause all 80 doors on the mux to alarm at the same time).

If you know which trunk cable is shorted, then the possibilities are narrowed down. Armed with a mux / slot report and a diagram showing the cable routing, units can be opened to track down the location of the short circuit.

Note that in many cases, these short circuits are intermittent. And may only last for a few seconds at a time.

Places to look for cable damage include:

  1. Penetrations through walls, where conduit or protective bushings were not used.
    DATroubleshooting-2.png

  2. Where cables run over the tops of unit walls and past sharp or pointed edges.
    DATroubleshooting-3.png

  3. Wires getting pinched between two surfaces.
    DATroubleshooting-4.png

  4. Ends of the trunk cable not insulated correctly.
    DATroubleshooting-5.png

  5. Wire not stripped correctly, wires were nicked, and the cable then touches metal.
    DATroubleshooting-6.png


Note: These troubleshooting steps assume that the network has been wired in accordance with PTI Security Systems specifications for Digitech RS-485 systems.

  • Troubleshooting a new site that is just being installed

The following troubleshooting steps are for a new site that has not been up and running before.

Symptom: No boards come online. (When a “Set Controller"[1] is performed, none of the boards on the RS-485 network show an on-line status report. This includes the DigiGraphics)

  1. Inside the Syscon, check the status of the two RS-485 LED’s on the lower board (Some Syscons may only have one board installed).
    RS485Troubleshooting1.png

  2. The Normal condition for the RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. lights is for both of them to be constantly flashing.
  3. If the RCV light is on solid, then goes off for a split second as the XMT light comes on, and repeats this every two seconds, then there is a short circuit between the positive and the negative lead of the RSX-485 bus. This short could be at any point in the RS-485 network. See the next section in this answer for instructions on locating a short circuit.
  4. If the RCV or the XMT lights do not light up at all, or if the RCV light is on solid and the XMT light does not flash, then the Syscon is not polling the network. Check the programming of the DigiWin software and make sure that the RS-485 network boards are defined correctly in the software setups.[2]
  5. If the XMT light flashes once every two seconds, and the RCV light does not come on, then there is a wiring problem in the RS-485 bus ( Open circuit or miswired connection ), or a problem with the MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boards. See page 4 for instructions on troubleshooting these problems.



  • Troubleshooting a Short Circuit
  1. Disconnect the RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. line that goes from the Syscon to the DigiGraphics. Check to see if the RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. lights have returned to normal operation. If they have,
    • Inspect the line that runs to the DigiGraphics for shorts.
    • Check the wires at the RS-485 converter ( Connected to the back of the DigiGraphics ) and make sure they are connected correctly.
    • Replace the RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. converter at the DigiGraphics.
  2. If your system has a single branch of the RS-485 network that is connected to the controller (As shown in the example below), then start at the far end of the network and disconnect the last device from the RS-485 network. If your system has two branches, then you should disconnect one branch from the system controller at a time, to determine which branch the short circuit is in. Once you have determined which branch it is in, then start troubleshooting that single branch. (The system should not have more than 2 branches, and it can only branch at the system controller.).
    RS485Troubleshooting2.png

  3. Work your way back from the last device on the line towards the Syscon, disconnecting each board from the RS-485 network. Each time you disconnect a board, check the status lights inside the system controller to see if the short has been removed (The RCV light will no longer be on solid). Once you disconnect a board and the lights change, then you will find that the short is either in the last box you disconnected, or in the line running to the next box in the chain. This shows an example of how the lines were disconnected.
    RS485Troubleshooting3.png
    .
    Note: When you are disconnecting the RS-485 wires from the boards, check all of the wire connections for correct polarity and for any short circuits as you are doing this.
  4. Check each of the following areas for the short circuit after you have determined which box is at fault.
    • Check the outgoing wire to the next RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. device first (If applicable). Disconnect it from the boards and read it with a ohmmeter. Should read an open circuit.
    • The circuit board itself can be at fault. This requires replacement of the board.



  • Other wiring problems with the RS485A type of communications used for electronic devices. Generally, limited to four thousand total feet of wire length. Used for connecting the Falcon XT to AI Devices. Network

If the RS-485 XMIT light flashes by itself for a few seconds, then both lights flash for a few seconds, then the system is polling for a board and is not getting a response from it. Look for the following:

  1. Incorrect polarity of the wires when connected to the board.
  2. On connector P2 of the UniMux board or keypad board, check that the connector is not crimped down on the insulation of the wire instead of the wire itself.
  3. Check the continuity of the wires in the system.
  4. Check DigiWin software programming, to make sure the software is only polling boards that are on the system.
  5. Check the address settings of the various MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boards to see if the correct MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. addresses are present and that you do not have any duplicate addresses set.


It can be useful to also check the status of each MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boxes RS-485 lights. You should see the RCV light almost constantly flashing, with the XMIT light flashing at a slower rate. The rate the XMIT flashes depends on the total number of devices on the system. The more RS-485 devices the system has, the slower a board's XMIT light will flash.



  • Troubleshooting a site that was previously working

Use the following steps to troubleshoot a RS-485 network that was working when installed, but has failed at some point in time after the initial installation.

Again, these troubleshooting steps are only valid for systems that are installed as per Digitech specifications. It is possible for a system that is not installed to specification to work for a time, and then fail or operate intermittently.

The three different failure modes for these systems are:

  1. Component failure. This is when one of the boards on the system fails. This may or may not be the direct result of a surge. This type of problem usually manifests itself in one of two ways:
    • One board on the system goes “offline” and remains offline.
    • More than one or all RS-485 boards go offline, and may stay offline or switch back and forth over a period of time.
  2. External Damage: This is damage to the wires in the RS-485 system. This can be cause by wires that are unprotected and are damaged by a person. Or it can also be a result of poor installation that allows the wires to be damaged while being installed, and the problem manifests itself later in the life of the system.
  3. Surge Damage: This is caused by an electrical surge (lightning) that can damage the components on the MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boards. These problems can also show up as boards cycling on and offline.


The most efficient check that can be made at this point is to observe the status LEDs of the Syscon and the RS-485 devices.

  1. Check to make sure that the Digitech software has not been altered, and that all MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boards are defined in the setups for the system.
  2. Check the system for shorted RS-485 lines. Use the instructions at the beginning of this answer to look for short circuits. A common occurrence is for a RS-485 line to have been “nicked” when it was pulled into conduit, and the moisture in the conduit shorts out the line. Also RS-485 lines can become “pinched” or damaged inside of a building, causing a short to each other or to electrical ground.
  3. Isolate the system from the DigiGraphics converter.
  4. Use the “Divide & Conquer” method to isolate the system. Start from the Syscon and connect one part of the system at a time to see if they work. Use the DigiCom software tool to “poll” the RS-485 devices as you connect them one by one. Once you connect the faulty device, the system will stop operating.
  5. Watch out for systems that appear to only malfunction at certain times of day. For example, if a system works fine during the day and then starts to have offline problems at night, this is an indication that an electrical wiring problem may exist in the buildings the MUXDoor Alarm Multiplexers take multiple inputs from individual door contacts and convert them to a single output back to the controller. Camera Multiplexers are similar in that they take multiple inputs from different cameras and create a single output back to the recorder. boxes are attached to. Typically this would be something in the lighting control circuit or its electrical panel.

    Notes

  1. Setting the controller is done in the DigiWin program, under the Utilities MenuA list of commands or options that the user can choose from..
  2. To check the system settings, in the DigiWin program select the "ReportA presentation of data in the system, formatted to be printed on paper from a printer." MenuA list of commands or options that the user can choose from., then select "Misc. Reports", then "Setup Info".


This procedure will determine the origin of the keypad problem; which could be the keypad itself, the Keypad I/O Board, or the wiring between the two. This is a generalized method that can be used for several problems when you are just trying to narrow down the problem to the keypad, wiring harness or IO board.
Note: When a keypad has a whole row or column of numbers that does not work, the problem can be either the keypad or the Keypad Interface BoardA circuit board used in a Syscon. (Can be optional, but the majority of systems have them installed.) Provides inputs for up to 4 Standard 700 Keypads, and 6 Control Point outputs.. If a keypad has just a single number that does not work, it's usually the keypad itself that is the problem.

  • Swap the Keypad with one known to work. (If you only have one standard keypad, jump to the next section.)
    1. Remove the 4 Keypad Mounting screws on the problem keypad.
    2. Gently remove the keypad from its housing.
    3. Remove the Keypad plug from the back of the keypad.
      DigiGate Standard Keypad Back.png

    4. Take the keypad to a location that has a working keypad.
    5. Repeat the 3 steps above on the working keypad.
    6. Reverse the first 3 steps, installing the problem keypad where the working keypad was located. (You can only use one mounting screw to temporarily hold the keypad in place. Just don't lose them.)
    7. Take the good keypad to the location where you removed the problem keypad. Again reverse the first 3 steps, installing the working keypad where the problem keypad was located.
    8. Try both keypads and note the result.

  • If the problem moved with the keypad, the keypad is the cause and should be replaced or repaired. If the problem stayed at the gooseneck that originally had the problem, Continue with the next test.

  • Checking the Keypad I/O Board and the Wiring.
    1. On the Keypad I/O Board, remove the keypad plugs for the problem keypad and a working keypad. Mark each plug so that they are not confused.
      DigiGate IO Board Example.png

    2. Plug the keypad plug of the problem keypad into the socket where the working keypad plug was removed. (If you only have one keypad, it's probably plugged into the lower port of plug P3. Move it to the top port.)
    3. Plug the keypad plug of the working keypad into the socket where the problem keypad plug was removed.
    4. Try both keypads and note the result.
  • If the problem is at the same keypad as before, the problem is in the eleven conductor keypad wire going to that keypad. This wire will have to be replaced. If the problem switched to the other keypad, the problem is in the Keypad I/O board, which must be replaced.
    Note: You may occasionally run into a problem where a bad keypad or harness affects the other Digigate 700 keypads plugged into the same Keypad Interface BoardA circuit board used in a Syscon. (Can be optional, but the majority of systems have them installed.) Provides inputs for up to 4 Standard 700 Keypads, and 6 Control Point outputs.. In those cases, you may need to try the individual keypads without having the other harnesses plugged in. For instance a row of numbers is not working on three 700 kps. Use the method described above, but only plug in one keypad or harness at the time. The keypad or harness causing the problem will exhibit the symptoms individually and the others will not.