What voltage and current is the phone line monitor measuring to sense trouble on the phone line on the D7212B/D9112B panels?
The phone line monitor senses trouble when the voltage on the line falls below 4.5 to 7.5 VDC, or in the off-hook condition when the current is 8 to 13mA.
How is the history reset after an event overflow message?
Receive the panel's history, choose the set pointer option to have panel start history from that point forward on newer just receiver Current.
Part numbers D7212B, D9112B, D7212B1, D9112B1, D7212, D7412, D9112, D9124, D9412, D7212G, D7412G, D7412G, D9124G, D9412G, D7212GV2, D7412GV2, D7412GV2, D9124GV2, D9412GV2, D7212GV3, D7412GV3,D7412GV3, D9412GV3, D7212GV4, D7412GV4, D7412GV4, D9412GV4, B8512G, B9512G
Points are faulted but the panel does not react.
Points must be faulted for 500 milliseconds minimum.
*When using self resetting devices, some do not latch the contact in the faulted position but do show a fault trip via a latched LED.
How does the FIRE TEST COMMAND 58 feature function?
• Use this function to test fire points and other 24-hour points to be certain they function properly. You can review both the tested and untested points at your command center to help pinpoint any problems.
• Upon initiation, the fire test will test the fire bell pattern on the bell output and ring the command center fire bell for 2 seconds. The AC will be disabled for 4 minutes in order to test the system’s battery power. If the battery cannot maintain the system for the 4 minute period, the command center will appear to go dead. If this happens, contact your security company. At the end of the 4 minute period, AC is returned to the system and the panel restores. A message will be sent to your security company upon initiation and completion of the Fire Test. During the Fire Test, no 24-hour alarms will be sent to your security company.
• If there is no activity on the system for 20 minutes, the system will automatically exit from the Fire Test.
Using COMMAND 58:
1. Ensure your command center is at disarmed idle text.
2. Press the COMMAND bar. The display shows SYSTEM COMMAND.
3. Press the 5 key, then press the 8 key.
Note: If you prefer, you may use the Command Menu in place of steps 2 and 3 to initiate this function. Press the MENU key to enter the Command Menu, then press NEXT repeatedly until you reach the FIRE TEST ? prompt. Press ENT.
4. The display shows ## PTS TO TEST.
5. One-at-a-time, activate the detection devices to fault each point.
6. As you fault each point, your command center will display the point text for 60 seconds and ring the fire sounders for 2 seconds. This verifies that the detection device is working properly. Your system automatically resets smoke detectors.
• When a resettable point (such as a smoke detector) is faulted, the display shows SENSOR RESETTING for 5 seconds. During this time power is removed from smoke power relays.
• Faulting a point more than once does not increment the test count. However, the command center emits a brief tone and displays the point text each time you fault the point allowing you to test multiple devices assigned to one point.
7. When all 24-hour points have been tested, 0 PTS TO TEST is displayed. Press ESC. The display momentarily shows ALL PTS TESTED before returning to idle text.
8. During the Fire Test you may want to see the points that remain untested. When point text is displayed, press ESC. The display shows ## PTS TO TEST. Press the ESC key. VIEW UNTESTED ? is displayed. Press ENT. ## PTS UNTESTED is displayed. Press NEXT to see a list of the points that have not yet been tested. Move through this list by pressing the NEXT key. To resume the Fire Test, press ESC. ## PTS UNTESTED is displayed. Press ESC. ## PTS TO TEST is displayed. Resume testing points. To end the Fire Test, press ESC twice.
When using 4 wire smoke detectors on the D6112, where do the detectors power connections need to be landed on the panel to provide reset capabilities with Command 47?
The power connections need to be landed on terminal 15(+) and 14(-) for the reset to occur when a CMD 47 is entered at the keypad.
The D8112 panel is not sending signals when modem format is selected to the Central Station.
Only the D8112G2 can send signals in Modem II format with a CS setting of 7.
The D8112E, D8112E1, D8112G, D8112G1 and D8112A must have CS set to either Blank or a selection between 1 and 6 but not 7.
Only Modem Format can report a 4 digit account number to the Central Station all others only report a 3 digit account number.
Can not connect to a panel using a DX4020 and RPS?
There are a lot of things to check for when having connectivity issues between RPS and 7000/9000 series panels through a DX4020. Perform the following in order. A technician with a laptop and RPS installed on the laptop should be on site.
1.) Check for Bus Status LEDs (Red LEDs). If they are flashing, go to step 2. If they are not flashing, make sure that dip switches 1, 2, and 3 are closed (down) and dip switches 4 and 7 are open (up) (dip switches 5, 6, and 8 do not matter) and make sure that there is not a DX4010 on this panel addressed as 88 (you can only have 1 SDI address 80 and 1 SDI address 88 on the panel). If you still do not have Bus LEDs, latch down the reset pin. If they come on after this, change Enable SDI RPS to YES in the AUX / SDI RPS Parameters. If they still do not come on check wiring to the SDI bus, that the EEPROM chip on the DX4020 did not come loose, that the EEPROM on the panel is 6.0 or higher, for grounds on the panel, ensure DC voltage is ~12vDC between terminals R (power) and B (common), and disconnect all other SDI devices from the panel to eliminate the keypads and keypad wiring as issues. If after completing all of this, you still do not have bus LED status lights, replace the DX4020.
2.) Once you get the Bus Status LEDs, do a network test. This is the same thing as doing a ping from the command prompt. If they do not come back successful, go to step 3. If they do come back successful, go to step 4.
3.) If you are not successful with a network test on the panel, connect directly to the DX4020 with a crossover cable (pin 1 will be crossed with pin 3 and pin 2 will be crossed with pin 6) and try again. If you are still unsuccessful, check to ensure that your computer is on the same network as the DX4020. If it is, arp in the IP address of that card (arp –s IPaddress MACaddress). If you are running Vista, you MUST be in administrator mode to do this (go to cmd under programs – accessories, right click, and select run as administrator). Next, establish a telnet connection with the DX4020 (telnet enter, open IPaddress 1, wait for it to fail, then, enter open IPaddress 9999). If you are running Vista, telnet is not installed by default but the setup files are copied. You must add the telnet client component in Programs and Features. It is helpful with multiple LAN components to arp in the DX4020’s IP address while binding it to the specific connector which the DX4020 is attached. A main example of this would be if you have a wireless NIC and Ethernet Port. In this case put in arp –s IP_address_of_4020 MACaddress IPaddressofyoursystem. Once you are in, go to server configurations and verify the IP address, default gateway, and subnet mask. Remember that it is looking for the number of bits in the host portion of the subnet mask.
4.) Now that we have Bus connectivity (red LEDs) and can do a successful network test, try to connect to the panel and watch the SER RX and SER TX (green LEDs) on the DX4020. If the green SER RX LED comes on but not the green SER TX, go to step 5. If neither of these come on, then the data packets are not making it through the DX4020 to the serial bus for the panel to process. This can be due to the port being blocked (default port is 7700), non matching encryption keys, or a malfunctioning DX4020. While connected with a crossover cable, make sure the D6200 software is not running or use a different port than 7700. Turn off all firewalls and anti-virus software. Check to see if the receiver is running encryption and if they are, make sure the same key is in the DX4020 and in RPS. If you can now get in, but still can’t across a network, then the panel is setup correctly but a network device is down or the port or IP address is being blocked between their workstation and the panel.
5.) If you get the green SER RX but no SER TX, then the information is going through the DX4020 but the panel is not responding to the data. Telnet into the DX4020, scroll to the top line which should have the firmware version of 1.5D or higher (This must be Bosch released firmware, such as version 18.104.22.168 for a Xport-01 or version 22.214.171.124 for a Xport-03, to support Datagram type 02). The second line should have AES firmware version. If the card does not meet those requirements, download and update the firmware to the latest revision. If it does, verify the correct datagram type in channel 1 configurations. If the panel firmware revision is a G panel 7.0 or GV2 panel 7.06 or higher, you must use datagram type 02. Otherwise use datagram type 00. If you are using datagram type 02, you must use RPS version 5.5 or higher. If the green ser RX LED stays on, check that the baud rate and other settings are set to 9600, no parity with 1 stop bit, and force RTS and DTR are forced on in the AUX portion of the panel, and verify correct datagram is being used in the DX4020. The panel will not reply to invalid RAM pass codes over the SDI bus, thus will never reply with an invalid RAM pass code. Check the RAM pass code with another system that CAN get in, or with a D5200 programmer and use that in place of the ****** when connecting to the panel.
6.) If you continue to have issues after checking these things, contact Bosch Technical Support for further assistance.
Notes: If you can connect locally but not remotely, then the problem is not with the panel or DX4020. If at the remote location, they can connect to the same type of panel with the same firmware locally, then the problem lies in the network. It is important to note that the port used by RPS is UDP and must be open to inbound and outbound traffic on all routers and firewalls. This includes your own computer. Windows, Symantec, Norton, AVG, Trend Micro, MaCafee, and numerous other Operating Systems and Anti-Virus software come with some form of firewall built into them. For this reason, disable all these types of applications for the initial connection to verify that we can connect. After we know that we can connect, then build exceptions for the UDP port (default is 7700) in your applications.
The FA113 will not arm the panel if it was disarmed from the keypad and will not disarm if panel was armed from the keypad
Used as an arm/disarm device, the FA113 is configured to panel zone 74 or 194. Pressing the FA113 Off button sends an OPEN signal to the control panel and pressing the On button sends a NORMAL signal to the control panel.
The area should be both Armed and Disarmed by the FA113 for it to function correctly. When the arming state is changed by the FA113, then by another means, the FA113 becomes unable to detect the current armed state of the area and will not respond to the keys pressed.
Correct settings for FA113:
The transition of the state of point 74 is what causes the area to arm or disarm. • Mode in the D8125INV is set to 4. • Keyswitch Maintained point (Point Type 4) with Point Response 2, is required for the FA113. • Area will arm with a transition from open to normal on point 74. • Area will disarm with a transition from normal to open on point 74. The FA113 is also used for panic on point 75 (7412G) and point 195 (9412G).
Overview: In order to comply with SIA CP-01 standards, GV2 revision 7.06 and higher panels have modified the method that points programmed for Swinger Bypass are bypassed. GV2 panel revisions 7.05 and earlier will automatically bypass points and report Swinger Bypass P### when these points erroneously report four trouble or alarm events within one hour of the first event. RPS revision 5.5 and higher provides a field called Swinger Bypass Count to be used in GV2 panels revision 7.06 and higher. This setting, between 1 and 4, selects the number of times that a point will automatically bypass after going into trouble or alarm, the selected number of times, within 1 hour of the first event. The Swinger Bypass Count setting is defaulted to 1 and if left unchanged Swinger Bypass points will Bypass after one alarm or trouble event. Further, new GV2 panels revision 7.06 and higher come with a default Swinger Bypass Count setting of 1. If programming with RPS revision 5.4 or earlier, the Swinger Bypass Count field will not be available to change and the setting will remain at 1. Likewise, if programming with the D5200 programmer using GV2Aux revision 1.01 or 1.00 the same problem will occur. RPS 5.5 or GV2Aux revision 1.02 or higher is required for programming.
Why do points bypass after one trouble or alarm event?
The point that generated 1 trouble or alarm and Bypassed uses a Point Index with Swinger Bypass set to Yes and the Swinger Bypass Count is set to 1. This setting is modified in GV2Aux>Misc>Swinger Bypass count in RPS rev 5.5 or higher. Using a D5200 programmer, GV2Aux revision 1.02 must be used. Swinger Count can be modified by entering group on Miscellaneous and then Swinger Count.