About David

When looking at the history log on a D6412 or D4412, the history log displays user 255 key-switch, and the key-switch zone has not been enabled.  The keypad displays as described below: This will occur when a passcode is not required for arming.  Because there is no user number associated with the arming command, User 255 will be logged.     ... View more

After emailing the certificate to the device the error message "Certificate Not Valid" continues to appear. The certificate has a start and end date built into it. If the date is not correct in the panel or has not been set in the panel, you will get this error. By default the panel date is set to 7/1/2010 and the Certificate start date is set to the computers date that the certificate is created on. ... View more

D6200 shows Communication Failed by Error when connecting to the receiver. Why does the D6200 software show "Communication Failed by Error" when trying to send files to a D6100 or D6600 receiver? This error will occur if the D6200 is set for the wrong environment option.  In the D6200 software, browse to Administration | Environment Option and select the correct Mode.  The options are D6600 or D6100.  Click OK to save the change. ... View more

How to connect to RPS using: ‘Connect Via: IP Direct’: B-Series or GV4 panels can use IP Direct as a means to connect to Remote Programming Software locally.  IP Direct uses an Ethernet cable connected directly between the computer and IP Communicator.  Provided both the control panel and IP Communicator are configured for DHCP, IP Direct completes the connection to RPS.  Ensure both the control panel and IP Communicator are configured for DHCP. If no program changes have been made to either, then both are configured for DHCP. How it works: The computer and IP Communicator are both set to DHCP and therefore both request an IP address from a server.  With the Ethernet cable connected directly between computer and IP Communicator and no DHCP server is available, the PC fails to obtain an IP address and falls back to the APIPA (Automatic Private IP Address) of 169.254.xxx.xxx (where xxx= a random number between 0-255).  The IP Communicator, also configured to DHCP, will fall back to its Automatic IP Address of 169.254.1.1.  When configured in this way connecting via ‘IP Direct’ will work because both the computer and IP communicator fall within the same subnet by design. Note: The IP Communicator does not require additional configuration when: Currently contains default settings (unused card) DHCP is available on the network AES encryption is not required UDP on Port 7700 (default B426 port setting) is available on the network. Configure the IP Communicator and computer to connect Via: IP Direct: Set the address switch to either 1 or 2. Ensure different addresses are used on each IP communicator connected to SDI2 (B420, B426 or B450).  Connect to the SDI2 bus with either a 4-pin molex connector or 4-conductor cable to terminals 33-36 (never use both at the same time). Set the PC to obtain an IP address automatically and the IP communicator to: DHCP/AutoIP Enable=Yes (default setting) Connect an Ethernet cable direct from the PC to the IP communicator and wait 60 sec. With DHCP enabled on the computer, a 169.254.xxx.xxx address should now be assigned and the IP Communicator should fall back to its default address of 169.254.1.1. The conditions for IP Direct have now been satisfied. Select Connect Via IP Direct. How to connect to RPS using ‘Connect Via:  Network’: Use ‘Connect Via:  Network’ for making local or remote connections with RPS using standard networking rules.  The IP communicator can use either DHCP or a static IP address depending site requirements.  Port forwarding rules may be required when connecting from outside of the host network.  Note: IP address 169.254.1.1 can be used for ‘Connect via Network’ when an Ethernet cable is connected directly between the IP communicator and computer and both are configured to use DHCP. ... View more

Verify that the reset pin is NOT latched on the control panel. Verify that the user has "view area status" authority in the panel. ... View more