BOSCH B426-M Alarm Panel Series Security Systems User Guide

: June 13, 2024
: Bosch

Table of Contents

BOSCH B426-M Alarm Panel Series Security Systems
Product Information
Product Usage Instructions
Overview
Features
Frequently Asked Questions
Setup
Troubleshooting
Licensing
Creating a Project on Driver Central
Purchasing a Driver Licence
Install the driverCentral cloud driver
Install Control4 driver
Change Log
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

BOSCH B426-M Alarm Panel Series Security Systems

Product Information

The Bosch Solution Installation and Usage Guide provides information on the installation and usage of the Bosch Solution 2000/3000 driver. This driver is compatible with both Solution 2000 and Solution 3000 panels when used with the optional B426-M Ethernet Module. It offers end user alarm interface features and installer features.

Features

Compatible with Solution 2000 and Solution 3000 panels
Requires optional B426-M Ethernet Module
End User Alarm Interface Features
Installer Features

Product Usage Instructions

Setup

Ensure Control4 is running OS 3.3.0 or later. Previous versions may operate, but are unsupported.
Upgrade the Bosch Solution 2000/3000 panel to Firmware 2.1.0.2 or later.
Enable Alarm Reset On Disarm on the panel. This can be configured in two different ways:
Via Alink: Go to System, System Option, Alarm Memory Reset On Disarm, and set it to Enable.
Via the panel keypad: Use Keypad Menu, Installer Menu, System (3), System Option 1 (6), Alarm Memory Reset On Disarm (3), and set it to Enabled.
Ensure IP Adapter is connected to the Solution Panel and set a Static IP. Refer to Bosch documentation for configuration details.
Set A-Link/RSC Password as required. The default password is: 0000000000.
Add a Dedicated Default User Code for Control4 with full privileges in A-Link using Access, User.
Bind each output to the device required in Connections.
For two-way control, set the Output Remote Control Binding property to the Remote Control Event allocated in A-Link.
(Optional) To show Panel logs to clients, add the custom BoschSolution Interface driver to the project and connect it to the alarm panel driver in Connections. Rename the driver and add it to appropriate navigator categories and areas.
Reload navigators.

Overview

The Solution 2000 & 3000 alarm panel series from Bosch Security Systems offers you the perfect solution. They’ve created a security system that has all the technology it needs to identify intruders to your home or small business, without being hard to use. It helps you protect the things you love, providing you with reliable security at your fingertips. Supporting up to 8 fully programmable zones on the Solution 2000 and 16 fully programmable zones on the Solution 3000, these intrusion alarm panels are suitable for any home, and even small commercial premises. With support for up to 4 keypads on both panels and the ability to split into two separate areas, you have the flexibility of one security system that can act as two. Both the house and garage, granny flat, shop, office or warehouse can be covered by the one system at one cost. Each area can even report separately if desired – the perfect arrangement for shared premises such as duplex houses or commercial properties, where more than one business occupies the unit space.

Features

The VERSA Solution 2000/3000 driver is compatible with both Solution 2000 and Solution 3000 panels (requires optional B426-M Ethernet Module)

End User Alarm Interface Features

Full support for Areas 1 and 2
Supports Disarm, Arming, Stay 1, and Stay 2
Both detailed and simple Zone feedback options, with zone list
Visual feedback of Warnings and Trouble in Alarm UI
Output Control and Feedback for all outputs (requires configuration by Installer)
Instantaneous panel feedback for alarms and states
Custom Alarm Log Interface

Installer Features

Events for Trouble Start, Trouble Clear, alarm and arming stages
Access to Variables for advanced programming
Programming Commands to arm and disarm panel.
Display Full Panel History
Display Panel Protocol Versions
Automatically show maximum capacities of panel.
Output Support
Advanced Programming for via Event Variables

Frequently Asked Questions

What are the requirements to use this driver

A network module must be setup and operational with A-Link for the panel. The recommended IP module for this panel is Bosch’s B426-M module. This panel does not support serial control.
The Bosch Panel must be setup with a static IP
Firmware 2.1.0.2 or later is required. An installer is required to install the firmware.
Panel must be configured and operational before C4 driver installation. Refer to the panel documentation for details.
Control4 OS 3.3.0 or later is required. Earlier versions may operate but remain untested and unsupported.
Please refer to the Setup section of this document for Control4 Setup.

Where can I purchase a Bosch panel?

https://www.boschsecurity.com/au/en/where-to-buy/where-to-buy-au.html

I want to try this driver out before buying it?

All VERSA drivers for Control4 come with a 90-day trial to test

Setup

Ensure Control4 is running OS 3.3.0 or later. Previous versions may operate but are unsupported.
Ensure Bosch Solution 2000/3000 panel is upgraded to Firmware 2.1.0.2 or later.
Alarm Reset On Disarm” must be enabled on the panel. This can be configured in 2 different ways:
1. Via Alink. This option is available under System, System Option, Alarm Memory Reset On Disarm: Set To Enable
Via the panel keypad. Using Keypad Menu: Installer Menu, System (3), System Option 1 (6), Alarm Memory Reset On Disarm (3). Set to Enabled
Ensure IP Adapter on Solution Panel and set Static IP. Refer to Bosch documentation for configuration.
Set A-Link/RSC Password as required. The default is: “0000000000”
Add Dedicated Default User Code for Control4 with full privileges in A-Link using “Access, User Code” and “Access, User Code, User X – X Property”. Alternatively, you can use Keypad for configuration.
Ensure all output channels which require two-way control are allocated a Remote Control Event Code in A-Link
DriverCentral Cloud Driver must be installed and operating correctly:
https://drivercentral.io/platforms/control4-drivers/utility/drivercentral- cloud-driver/
Add VERSA Bosch Solution 2000/3000 driver to the Control4 project
Under Connections, set driver to IP address of panel.
The driver will connect to the panel and perform the configuration sequence
For Outputs:
Bind each output to the device required in Connections.
For two way control, set the Output Remote Control Binding property to the Remote Control Event allocated in A-Link.
(Optional) To show Panel logs to clients. We provide a custom Bosch Solution Interface driver
Add Bosch Solution Interface driver to project
In Connections, connect BOSCH_PANEL_UI to alarm panel driver
Rename driver and add to appropriate navigator categories and areas
Reload navigators

Troubleshooting

When clearing an alarm, panel disarms, however, Control4 continues to show Alarm as active

Ensure Alarm Memory Reset On Disarm is enabled (as per Setup)

Solution Panel Driver [bosch_solution_panel.c4z] Actions

Display Diagnostics: Display Internal Diagnostics of Driver to assist with troubleshooting
Display History: Displays History in Lua Output
Display Output States: Displays the state of all output states in Lua Output
Force Reconnect: Forcefully disconnects and reconnects network connection to panel
Remote Control Output: Change the state of a Remote Control output manually

Properties

Cloud Status: Licencing Status of the Driver
Driver Version: Version of the Driver
Automatic Setup: Whether or not the driver will automatically update the driver
Control4 MAC Address: MAC Address of the C4 Controller
Debug Mode: Enable different types of debugging modes for driver.
Debug Level: Verbosity of debugging. ERROR is the least verbose

Driver Information

A-Link/RSC Password: Password required for A-Link / RSC connection. The default is: “0000000000”
User Code: User Code which has been set up for Control4 use to perform actions
Automatically Update Time: Configures Control4 to automatically synchronise Bosch Panel’s time on connection and a regular basis. Most users should keep this option enabled.
Display Zone Number in Zones Interface: Display Zone Numbers in the Zones Interface. This is useful for installers to identify zones easily, or are used to the zone numbers on their keypad.

Panel Details

Status: Shows Connection Status Information
Panel Model: Detected Model of the Bosch panel. This should be “Solution 2000” or “Solution 3000” (other models are not supported)
Panel Firmware: Detected firmware on the bosch panel. This must be a minimum of 2.1.0.2
RPS Protocol: Detected RPS Protocol on the Bosch panel. This should be a minimum of 5.2.0.0
Intrusion Protocol: Detected Intrusion Protocol on the Bosch panel. This should be a minimum of 5.22.0.0
Execute Protocol: Detected Execute Protocol on the Bosch panel. This should be a minimum of 5.2.0.0
Max Areas: Maximum number of areas supported by the panel.
Max Doors: Maximum number of doors supported by the panel. Please note, Solution 2000/3000 does not support Doors (Support for Doors is not included with this driver)
Max Event Records: Maximum Event Log Records supported by the panel.
Max Keypads: Maximum Keypads enabled by panel.
Max Outputs: Maximum Outputs supported by the panel. Please note: This does not include optional output boards
Max Points: Maximum Zones / Points supported by panel
Max Users: Maximum User Codes supported by panel

Output Names

Name – #: Name of the output as provided by the installer
Output States
State – #: Current state of the output (Off / On)
Output Remote Control Event Code Bindings
Code – Output #: Allocated Remote Control Event Code as allocated by the installer. This may not be the same number as the output..

Commands

Remote Control: Set On / Off Remote Control ID. This may not correspond to a specific output.
Turn Output On: Turn Output On
Turn Output Off: Turn Output Off
Toggle Output: Toggle Output On / Off
Trigger Output: Trigger Output for custom time period

Events

Area 1 Exit Delay Started: Area 1 Exit Delay has started
Area 1 Exit Delay Ended: Area 1 Exit Delay has ended or been cancelled
Area 1 Entry Delay Started: Area 1 Entry Delay has started
Area 1 Entry Delay Ended: Area 1 Entry Delay has ended or been cancelled
Area 2 Exit Delay Started: Area 2 Exit Delay has started
Area 2 Exit Delay Ended: Area 2 Exit Delay has ended or been cancelled
Area 2 Entry Delay Started: Area 2 Entry Delay has started
Area 2 Entry Delay Ended: Area 2 Entry Delay has ended or been cancelled
Log Entry Received: Generally used in conjunction with the EVENT_LOG variables for advanced Programming. Identifies that a new log entry has been received

Variables

AREA1_LAST_ARM_USER: UserName who last armed Area 1
AREA1_LAST_ARM_USER_ID: User ID who last armed Area 1
AREA1_LAST_ARM_TIME: Time when Area 1 was last armed. This uses the Panel Time.
AREA1_LAST_ARM_TYPE: Type of arming for Area 1. Generally Away, Stay 1 or Stay 2
AREA1_LAST_DISARM_USER: UserName who last disarmed Area 1
AREA1_LAST_DISARM_USER_ID: User ID who last disarmed Area 1
AREA1_LAST_DISARM_TIME: Time when Area 1 was last disarmed. This uses the Panel Time.
AREA2_LAST ARM_USER_ID: User ID who last armed Area 2
AREA2_LAST_ARM_USER: UserName who last armed Area 2
AREA2_LAST_ARM_TIME: Time when Area 2 was last armed. This uses the Panel Time.
AREA2_LAST_ARM_TYPE: Type of arming for Area 2. Generally Away, Stay 1 or Stay 2
AREA2_LAST_DISARM_USER: UserName who last disarmed Area 2
AREA2_LAST_DISARM_USER_ID: User ID who last disarmed Area 2
AREA2_LAST_DISARM_TIME: Time when Area 2 was last disarmed. This uses the Panel Time.
EVENT_LOG_AREA: Area of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_CONTACT_ID: Contact ID of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_ID: ID of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_PARAM1: Parameter 1 of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_PARAM2: Parameter 2 of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_PARAM3: Parameter 3 of last received Event. Used for Advanced Programming. Refer to Bosch Solution API (Solution Panel Event Log Data) for more info.
EVENT_LOG_TIME: Last Time (based on panel time) of last received Event. Used for Advanced
Programming
EVENT_LOG_TEXT: Text of last received Event. Used for Advanced Programming. Refer to BoschSolution API (Solution Panel Event Log Data) for more info.
PANEL_LAST_ARM_AREA: Area which was last armed
PANEL_LAST_ARM_AREA_ID: Area ID which was last armed
PANEL_LAST_ARM_USER: UserName who last armed the panel
PANEL_LAST_ARM_USER_ID: User ID who last armed the panel
PANEL_LAST_ARM_TIME: Time when the panel was last armed. This uses the Panel Time.
PANEL_LAST_ARM_TYPE: Type of arming for the panel. Generally Away, Stay 1 or Stay 2
PANEL_LAST_DISARM_AREA: Area which was last disarmed
PANEL_LAST_DISARM_AREA_ID: Area ID which was last disarmed
PANEL_LAST_DISARM_USER_ID: User ID who last disarmed the panel
PANEL_LAST_DISARM_USER: UserName who last disarmed the panel

Solution Interface Driver [bosch_solution_ui.c4z]
Actions

Display Diagnostics
Properties
Cloud Status: Licencing Status of the Driver
Driver Version: Version of the Driver
Automatic Setup: Whether or not the driver will automatically update the driver
Control4 MAC Address: MAC Address of the C4 Controller
Debug Mode: Enable different types of debugging modes for driver.
Debug Level: Verbosity of debugging. ERROR is the least verbose
Driver Information
Panel Status: Whether the interface driver is correctly bound to panel driver

Commands

None available or required

Licensing

How does the trial period work? This driver is free to use for a set trial period. When the trial expires the driver will cease to function until you purchase a licence and apply it to the driverCentral project.
Where do I buy a Licence from?

This driver available from driverCentral, Inc https://www.drivercentral.io/ To purchase a driver:

On driverCentral, purchase a license and register it to your project
If the driver is not already installed in your project, download it and install it
If necessary, use the cloud driver’s Action: “Check Drivers” to force the licence to download into the project

Creating a Project on Driver Central

Visit http://www.drivercentral.io
Log into your driver Central dealer account
Click Portal
Click New Project
Enter the project name
Click Add Project
Click on the project we just created
Take note of the Project Token as this will be used later when we install the Cloud Driver
Click Close

Purchasing a Driver Licence

Visit https://www.drivercentral.io and find the product/driver you want to purchase a license for
Click on Add to Cart
Now click the shopping cart icon (top right) and click View cart
Confirm that your order is correct and click on Proceed to checkout
Choose your payment option, provide the relevent details and click Place order
You will now be at a page where you can see your purchased licence
From here assign the licence to the project we created or if you did not follow that step create a new project

Install the driverCentral cloud driver

Visit http://www.drivercentral.io
Log into your driver Central dealer account
Click Portal
Click Cloud Driver
Copy the C4Z driver to My Documents\Control4\Drivers directory
Add the driver to your project
Click on the driver to view it’s properties
Type in the project token we took note of earlier
Click Actions tab
Click Check Drivers

Install Control4 driver

Install the Control4 driver
You will notice that the Activation Status reflects a Licence Activated state
Any driver that does not have a purchased licence will have a trial licence activated via the marketplace
Note that there is no way to reactivate the trial so please use wisely
If you do not then press the Check Drivers action in the driverCentral Cloud driver again