About David

1.  Verify FPE-1000-SLC cards are at version 1.25 or greater. 2.  Download the Offline Tool and FPA-1000 version 2 software from the Bosch website. a.  Access https://commerce.boschsecurity.com/us/en/Product-Segments/c/1 and select Product Catalog > Fire Alarm Systems > Analog Products, and locate FPA-1000 Analog Addressable Fire Panels. b.  Select Downloads and Software, download the below zip files and extract into a folder. i.  Software (Offline Tool) ii.  Software (Panel Software) 3.  Using a crossover Ethernet cable and the Firefox browser, connect to the panel and save a copy of the FPA-1000 version 1 panel (see figure 1). Figure 1 Download a copy of the existing panel  4.  Note that the downloaded configuration is an XML file and may appear as programmer’s data. This is the panel program which should be saved (see figure 2).   Figure 2 Downloaded panel program as XML file 5.  Select File >Save Page As… to save a copy of the current configuration. Be sure to save the file using the default option; Web Page, Complete (*.xml) (see figure3).   Figure 3  Save the downloaded panel program a.  Save 2 copies of the file. One as a back-up of the original program and the second to be promoted to version 2. i.  MyFPA1000program-V1 ii.MyFPA1000program -V2 6.  Open the folder containing the Software (Offline Tool) and double-click on startpage.hta to open the FPA-1000 Offline Configuration Tool (see figure 4). Figure 4 FPA-1000 Offline Configuration Tool a.  In the area which reads Convert Configuration (UL -> V2), browse to the location of the saved configuration file and select Convert Selected. The file is now converted to version 2 and ready to load into the FPA-1000 once the upgrade is complete. Use the following steps to upgrade the panel to version 2.  7.  Default the FPA-1000 Version 1 panel. a.  Access programming from the panel keypad. b.  Press 6 [Programming]. c.  Press 9 [Auto Learn]. d.  Press 9 [Return To Default]. 8.  Connect to the panel, select Maintenance > Testing and select SW Update from the tabs at the top of the page (see figure 5). Figure 5 Select SW Update under Maintenance and Testing 9.  Browse to the location of the new firmware; [uImage] and select Upload Software to panel. 10.  From the FPA-1000 browser Start Page where it reads; Upload configuration (PC -> FPA-1000), browse to the location of the configuration which was upgraded to version 2 [MyFPA1000program -V2]. Send the panel configuration to the panel by pressing Upload (see figure 6). Figure 6 Upload Version 2 software to panel 11.  The FPA-1000 is now upgraded to version 2 and ready to test. ... View more

What are Output Profiles? Output Profiles are an enhancement in output programming which provide additional options for configuring outputs. Each output profile contains a set of conditions which, when satisfied, will generate an output pattern (steady, pulsed, temporal, etc.) for an assigned output relay to follow. What is required for using Output Profiles? Output Profiles become available in B8512G, B9512G and B-Series panels using firmware version 3.10. Programming must be performed with RPS 6.10 or higher. Why are Output Profiles needed? Occasionally multiple conditions are required to activate an output. One solution is to use multiple physical relays with each one programmed for a separate event. Relays are then interconnected with wiring to obtain an output only when both the first and second relays turn on.  Output profiles perform the same operation except by using programming. Each profile follows panel events configured as ‘triggers’ and an output is generated when the triggers occur. What is a ‘Trigger’? Triggers can be panel events, arming states or activation of selected points or outputs. Triggers may even be the activation of a SKED or Custom Function. The trigger is selected from a drop-down list with additional parameters for selecting a scope (area/panel wide/etc.) and filter (designated area/point/output/etc.). How are Output Profiles configured and what happens when the Triggers occur? Each output profile is configured to follow either one or two panel generated triggers. When one or both triggers (depending on configuration) occur, a steady or pulsed output pattern is generated. The output profile is assigned to a panel output, and that output follows the selected output pattern. Should Output Profiles be used in place of Area Wide or Panel Wide Outputs? Output Profiles are not intended to replace area wide or panel wide outputs. Some additional panel generated events are included in output profiles which were previously not available.  Output Profiles are preferred when using one of the newly added events or when multiple conditions are required to obtain an output. Most applications will continue to use panel or area wide outputs for general output programming as in previous panel versions. Note when configuring panel outputs: An output can only be configured in one area of the program. For example if Output 2 was selected for Summary Fire in Panel Wide Outputs it will not be available for use with an output profile. Take care to not configure an output from multiple areas of the program to avoid unexpected operation. Options for Delay or Duration: Delay: This setting may be used to delay the output pattern from occurring from between 5 seconds and 2 hours after the trigger events occurred. Note that some triggers such as Watch Active do not allow a delay. Duration: This setting determines how long the associated output(s) will remain active; Until Off - persists until the silence function is initiated. Timed - persists from 5 seconds up to 2 hours. Until Cleared - persists until the alarm and fault event are cleared (when an alarm and/or fault events are followed). This selection cannot be silenced. Follows Trigger - persists until the Trigger event is cleared. This selection cannot be silenced. Use case example for an Output Profile: The following example uses an Output Profile to generate a supervisory trouble if the Garage Man-Door is left open for 5 minutes between 22:45 and 23:30. 1.  Point 2 supervises the Garage Man-Door. Point 9 will be discussed later. Figure 1 Point Assignments  2.  Output 4 follows a schedule to turn on at 22:45 and turn off at 23:30. Figure 2  Skeds 1 and 2 turn Output #6 On and Off 3.   Output Profile 1 is configured to monitor Trigger 1 and Trigger 2. A steady pattern is generated when Trigger 1 and Trigger 2 occur. Figure 3 Output Profile1 combines Point 2 and Output 4 a.   Trigger 1: Point Active. A point is monitored and the trigger is satisfied when the point is active (off normal).  Point 2 is selected as the point which Trigger 1 will monitor. b.   Trigger 2: Output Active. An output is monitored and the trigger is satisfied when the output is active (turns on). Output 4 is selected as the output which Trigger 2 will monitor. 4.  Output Profile 1 is assigned to an Output 9. Figure 4 Output Assignments  5.  Output 9 follows the pattern generated by Output Profile 1 (On Steady). 6.  Input 9 is assigned Point Source= Output and Profile 23; Non-Fire Supervisory (see figure 1 Point Assignments). 7.  Point Profile 23 is configured as Non-Fire Supervisory. 8.  Input 9 follows Output 9 and a supervisory alarm is generated when both triggers in output profile 1 occur (Point 2 faulted while Output 4 is active). ... View more

Verify the DX4010V2 is connected and addressed correctly: D7212/D7412/D9412, G-GV4 series: Connect the DX4010V2 to the SDI bus of the panel and not the Program port. Legacy panel types do not include the 4-pin molex connector.  Use a 4-conductor wire and connect to SDI bus terminals 29-32. Set dip-switches 1, 2 & 3 Up/On and 4-8 Down/Off for SDI address 250, required for connecting to RPS. FPD-7024: Connect the DX4010V2 to the option bus located on the lower right corner of the panel. Note the option bus connections (R/B/G/Y) are different than DX4010V2 (R/Y/G/B). Incorrect wiring may damage the DX4010V2. Set all dip-switches 1 - 8 Up/On for option bus address 250, required for connecting to RPS. B8512G, B9512G and B-Panels: The DX4010V2 is not intended for B8512G, B9512G or B-Panels. Use the B99 USB-A to A cable and connect via USB instead. After-market cables must be ‘computer to peripheral’ type and not ‘computer to computer’ type. Port in use by Other Device error display: Figure 1 Port in use' error display The computer assigns a COM Port to the DX4010V2. The error displays when an incorrect COM Port has been selected in the Panel Communication dialogue. Use Device Manager to determine the correct Com Port assigned to the DX4010V2 (see figure 2). Right click on the Windows Icon and select Device Manager. Locate ‘Silicon Labs CP210x USB to UART Bridge (COMx)’ under Ports (Comm & LPT). Enter this Com Port in the Panel Communication dialogue (see figure 3). Figure 2 Access Device Manager Figure 3 DX4010V2 Determine selected Comm Port When ‘Silicon Labs CP210x USB to UART Bridge (COMx)’ is not listed under Ports (Comm & LPT): The driver is normally installed during the installation of RPS. When not listed it may be downloaded from https://commerce.boschsecurity.com/ by searching the DX4010V2 and downloads. Check for a correct RPS Passcode used for the RPS connection: The RPS passcodes in the panel and in the RPS panel account must match in order for a successful connection. In most cases the error below; 5025: Connection Terminated Retry Count Exceeded is caused by a mismatch in the RPS passcode. Figure 4  Connection Terminated Retry Count Exceeded The default RPS Passcode for GV4 and earlier panel types is 999999. Use keypad programming (when available) or another means must be used to determine the RPS Passcode stored in the panel.  RPS connections to the panel will not be possible without the correct passcode and when unrecoverable panel replacement is required to resume RPS connections. Enter the correct RPS passcode in the panel communication dialogue. Note the [****] in the panel communication dialogue is populated with the RPS Passcode located in the RPS account under Panel Wide Parameters > RPS Passcode. Figure 5 Verify Correct RPS Passcode Address conflict or Interference on the SDI Bus: Check that only one device using SDI 88 is connected to the SDI bus while using the DX4010V2. Devices such as the B426, B420 or DX4020 will conflict with the DX4010V2 and block the RPS connection if addressed as SDI 88. Isolate any possible noise/interference by removing all other wiring from the SDI bus except for the DX4010V2. GV3 and GV4 panel types: Ensure the panel account was created for the correct panel firmware version. Press [Command] + [59] on a panel keypad and note the firmware revision. Right-Click on the panel account in RPS and select Open Panel Data-View. Verify a correct Panel Version selection (see figure 4 below). Figure 6  Panel Version selection in the panel account GV3 and Subscript out of Range: A “Subscript out of Range” message may display when connection is attempted with a GV3 type using an invalid RPS passcode. Verify the correct RPS passcode is used.  DX4010V2 compatibility with legacy D7212/D7412/D9412 G and Non-G types: Panel firmware must be version 6.0 or higher for compatibility. Press [Command] + [59] to verify panel firmware. EEprom chips are no longer available for upgrading firmware in these types. Damage caused by power loss in legacy D7212/D7412/D9412 G and Non-G types: A 3V lithium battery was used to retain the panel firmware and all programming upon power loss in these legacy panel types. When this battery drops below ~2.9V, and both AC input power and the panel backup battery are lost, the panel will fail and must be replaced.  This problem may apparent when the reset pin is open and all keypads read ‘Call for Service’. The following procedure may be used to verify adequate voltage exists in the lithium battery. Make sure a working D1640 AC transformer connected to terminals 1 & 2 and a working 12V backup battery connected to terminals 4 & 5. Remove the heat shield from the front of the panel and carefully remove the lithium battery. Check the lithium battery for at least 3V. If the voltage reads less than 3Vdc, the panel should be replaced. Panels using the Cloud ID: Only B8512G/B9512G and B-Series types use the panel Cloud ID as the RPS passcode. These panels are not compatible with the DX4010V2 and RPS connections should use other means. Use the B99 USB-A to A cable and connection via USB is recommended. After-market cables must be ‘computer to peripheral’ type and not ‘computer to computer’ type. Cloud ID: B8512G/B9512G and B-Series types comply with the California Security of Connected Devices Act (see below) and therefore use the Cloud ID for the initial connection to RPS. Locate the Cloud ID sticker (see below) and use this in place of the default 999999. Figure 7   Cloud ID sticker California Security of Connected Devices Act In order to comply with the California Security of Connected Devices Act (TITLE 1.81.26. Security of Connected Devices) this product uses a unique connection password. The “RPS Passcode” for the initial connection to this product must match the unique Cloud ID of the product. Ensure your RPS Operator uses the unique Cloud ID that is labeled on the product and included on the card in the box of the product. ... View more

When Remote Programming Software opens, a secure connection is made to the database which is located in an instance of SQL. If the connection to SQL is not successful or the database is not accessible, the Database connection failed error will display (see figure 1). Figure 1  Database connection failed error This article discusses some possible causes for the database connection to fail, select Details for more information. Some common causes for the database connection to fail are; failure to connect to the SQL Server, failure to open the database or failure to authenticate the user (see figure 2). Figure 2  Three common causes for the database connection failure Review the information displayed in details, then select OK to open the Database Settings Page (see figure 3). This page may also be accessed by selecting Config and System from the front page of RPS. Note the following settings which are applied during a basic installation of RPS; SQL Server Name: The Computer Name followed by back-slash [\] and the name of the SQL instance where the database is located, e.g. [computer-name\SQL Instance Name]. The default SQL instance name is BOSCHSQL. SQL Database Name: The name of the database used by RPS. The default database name is RPSDB. Authentication: The method for authenticating the database connection. The default entry is SQL Server Authentication. User Name: The user authenticated to allow  connecting to the SQL database. The default entry is 'sa' (system administrator). SQL Authentication Password: The password used to authenticate the SQL database connection.  The default password used in the default installation is;  RPS version 6.10 and newer: B@SCHRPSsql12345 RPS versions 6.09 and earlier: RPSsql12345. Instructions for correcting an unknown sa password are included later in this article.  Figure 3  System Configuration Page 1.   Failure to connect to the SQL Server. Details displays: “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. (Provider: SQL Network Interfaces, error: 26 – Error Locating Server\Instance Specified).” In this case the connection to the SQL Server has failed causing the database connection to fail. Press OK and return to the Database Settings page. Troubleshoot using the following steps; Check for a correct SQL Server name entry with the following format; [computer-name\SQL Instance Name]. Be sure that a backslash [\] is used between items. [Computer-name] represents the name of the computer with SQL installed. [SQL Instance Name] represents the name of the SQL Instance where the RPS database is located. Note that there may be more than one instance of SQL on the PC. The correct instance name must be entered here. Open Computer Services using the steps below to verify; 1) SQL is installed, 2) the correct instance name is entered in Database Settings, and 3) the related service is running. Right-click on This PC or Computer and then select Manage and Computer Management opens. Select Services and Applications and then select Services to open Computer Services (see figure 4). Figure 4  How to access Services and Applications A list of computer services displays as in figure 5. Identify the SQL Server service with the RPS database, e.g.  SQL Server (instance-name) from the list. Verify this instance name was entered correctly in the Database Settings page under System Configuration (see figure 3).  If the service is not listed, then the instance is not installed on this PC.    Figure 5  Locate the SQL Service Note the Status and Startup Type for the Service. If status does not display Running, right-click on the service and select Start. If the Startup Type does not show Automatic it must be changed from the properties page. Access the properties page by double-clicking on the SQL Server service. Select Automatic from the drop-down list in the properties page as displayed in figure 6. Figure 6 Verify the Service is running and Startup is Automatic Verify Microsoft SQL Server Native Client is installed on the PC running RPS. Microsoft SQL Server Native Client can be downloaded from the link: https://www.microsoft.com/en-us/download/details.aspx?id=50402 Beginning with version 6.07, RPS makes an encrypted connection to SQL, therefore TLS 1.2 must be supported on the computer. The following links may be used to verify encryption is supported; https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15 https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server Note that encryption must be supported on both the Client and Server PCs when SQL is located on a remote computer. Verify a functional network connection between the Client computers to the Server computer when SQL is located on a remote computer. 2.   Failure to open the database. Details will display; “Cannot open database “[database name]” requested by the login. The login failed. Login failed for user ‘sa’”.  In this case the database failed to open after the connection was made to SQL. Press OK and return to the Database Settings page.  Troubleshoot using the following steps; Verify the Database Name entry is correct. Navigate to the following path and note the name in brackets and verify it was entered correctly in Database Settings; C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.BOSCHSQL\DATA\[database name] Press Upgrade Database. This updates the database tables as well as verifies correct ability to ‘write’ data to the database. Verify the RPS installation was executed by right-clicking on the installation file and selecting ‘run as administrator’ (see figure 7 ). This permits the system to make required changes to the registry as well as grant read/write permissions to files & folders where needed. Figure 7 Install with Administrator Privileges Attempt to create a new database.  As a possible last resort, this will validate that the login method had the ability to create a new database and has write permissions to update tables. 3.   Failure to authenticate the user: Details will display; “Login failed for user sa”. The user “sa” is used when the database connection is made using SQL Server Authentication. There are two likely causes for the SQL Server user sa to fail. The sa password may either be incorrect or fails to meet domain requirements for complex passwords (if required). It may also be occur if the SQL installation was not configured for Mixed Mode. Press OK to return to the Database Settings page. Troubleshoot using the following steps; Manually enter the default user name and password loaded with a basic install of RPS; RPS version 6.10 and newer using SQL Server 2017: B@SCHRPSsql12345. RPS versions 6.09 and earlier using SQL Server 2012: RPSsql12345. Change Authentication from SQL Server Authentication to Windows Authentication in Database Settings. Use Microsoft SQL Server Management Studio to verify a correct password is used, or to create a new password which satisfies the domain requirements for complex passwords. Examples are; Minimum number of characters. Upper case characters. Lower case characters. Numbers between 0-9. Non-alphabetic (special) characters (for example, !, $, #, %)  Download and install Microsoft SQL Server Management Studio (SSMS). Go to the SSMS installation page in a browser with the following link: https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15  Figure 8  Download SSMS  Click the Download SQL Server Management Studio link. Right-click the downloaded SSMS setup file and select Run as Administrator. Follow the on-screen prompts to install SSMS.  Figure 9  Welcome to install screen  Select Install. Figure 10  Select Restart  Select Restart to complete the installation(see figure 10). Figure 11  Open Management Studio  Open SQL Server Management Studio (see figure 11). Figure 12  Log in using Windows Authentication The Connect to Server dialog opens. Select Windows Authentication and then select Connect to log into the server's dashboard (see figure 12). Figure 13 Object Explorer  SQL Server opens to the Object Explorer page with configuration options (see figure 13). Figure 14  Object Explorer Security expanded Double-click on Security or click on [+]to expand the folder (see figure 14). Figure 15  Object Explorer Logins Expanded Double-click on Logins or click on [+]to expand the folder and then double-click on the user; sa (system administrator) to open the Login Properties page (see figure 15). Figure 16  Login Properties sa password The login properties for user: sa opens to the General page. Enter the default password in Password and enter again in Confirm Password. The default password is recommended to assist Bosch Technical Support when needed. For SQL 2012 enter: RPSsql12345. For SQL 2017 enter: B@SCHRPSsql12345. Select OK at the bottom of the page. Test the new sa user password by logging out of the Object Explorer and then logging back in with SQL Authentication Mode and the new sa password.  Press File > Disconnect Object Explorer, and then File > Connect Object Explorer.  Figure 17 Connect to server with SQL Server Authentication Enter the new password and press Connect. If the error “Login failed for user sa” still displays, the problem may be occurring because the SQL installation was not configured for Mixed Mode. Use the following steps to configure SQL for Mixed Mode. Change Authentication from SQL Server Authentication to Windows Authentication and press Connect (see figure 12). Right click on the instance name ([computer name\BOSCHSQL]) or ([computer name\BOSCHSQL2017]) and select properties (see figure 18). Figure 18 Access Properties for the SQL instance Select SQL Server and Windows Authentication mode (see figure 19). Figure 19 Select SQL Server and Windows Authentication Mode Note that the overall settings in Microsoft SQL go beyond the scope of this article. The assistance of a qualified SQL administrator may be needed when the steps in this article have not resolved the "Database Connection Failed" error. ... View more

Opening Remote Programming Software initiates a connection with the database it uses, located in SQL. This connection is normally authenticated using SQL Server Authentication, and with the user name [sa] and default password [RPSsql12345]. If this password needs to be changed, for example to meet a domain’s requirements for a more complex password, SQL Server Management Studio is used to make the change. The following steps may be used to change the System Administrator (sa) password in SQL. 1.   Download and install Microsoft SQL Server Management Studio (SSMS). https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15 Go to the SSMS installation page in a browser. Click on Download SSMS (SQL Server Management Studio). Right-click the downloaded SSMS setup file and select Run as Administrator. Follow the on-screen prompts to install SSMS. 3.   Open SQL Server Management Studio. 4.   The Connect to Server dialog opens. Select Windows Authentication and select Connect to log into the server dashboard. 5.   The Object Explorer opens. The SQL Server Instance name opens and several options should expand below it. If the list doesn’t expand, click on the [+] icon to expand it. 6.   Click on the [+] beside Security to expand the folder. 7.   Click on the [+] beside Logins to expand the folder. 8.   Double-click on the user login; [sa].  The properties window for the login [sa] opens. 9.   Enter the new password and enter again to confirm. Note that the default password used in the original install is [RPSsql12345]. 10.  Press OK. ... View more