Installing Bolid C2000 Drivers in Rapid SCADA Communicator

Problem Overview

The Bolid C2000 panel appears in the Rapid SCADA device-type list of the Administrator application, but no matching driver shows up in the driver selection dialog — neither in the base installation nor after installing the additional driver package downloaded from the vendor site. The device entry exists as a catalog item; the communication logic lives in a separate DLL that must be present in the Communicator driver folder before it becomes selectable.

Two distinct issues cause the empty list:

1. The Bolid drivers ship in the paid Driver Pack, not in the free driver bundle. They are not installed by default.
2. Even after copying the DLL, Windows may keep the file in a blocked state (mark-of-the-web), so the Communicator host process refuses to load the assembly and the driver silently never registers.

Driver Selection: KpS2000 vs KpS2000PP

Two Bolid communication drivers exist in the Driver Pack. They are not interchangeable, and only one has a future.

Practical consequence: if you architect the system around KpS2000.dll, you create a hard migration wall at the Rapid SCADA 6 upgrade — the driver simply will not exist. Specify the C2000-PP integration module on the fire/security panel side and drive it with KpS2000PP.dll. The C2000-PP acts as the protocol converter between the Bolid device bus and the SCADA host, so the SCADA side reads a normalized register set rather than the raw panel protocol.

Both drivers are commercial. The Driver Pack is a paid product; the Bolid drivers were paid items in the version 5 line as well. Pricing is published in the vendor price list — request current terms through official vendor sales channels rather than assuming legacy pricing.

Installation Procedure

1. Obtain the Driver Pack. Download the driver package archive from the official Rapid SCADA download page. The free additional-driver bundle does not contain the Bolid files — verify the archive actually contains KpS2000.dll and KpS2000PP.dll before proceeding.
2. Stop the Communicator service. Copying a DLL over a loaded assembly fails or produces a partially updated folder. Stop ScadaComm (service or console) and close Administrator.
3. Copy the driver files. Place KpS2000.dll and KpS2000PP.dll into:

   SCADA\ScadaComm\KP\

   On a default Windows installation this resolves under the Rapid SCADA program directory. Copy both files even if you only intend to use the PP variant — the folder is scanned as a whole and the extra file costs nothing.
4. Unblock the DLLs. Files extracted from a downloaded archive inherit the internet zone marker. Right-click each DLL → Properties → check Unblock at the bottom of the General tab → Apply. For bulk unblocking from an elevated PowerShell prompt:

   Unblock-File -Path "C:\SCADA\ScadaComm\KP\KpS2000*.dll"

   This is the single most common reason a correctly copied driver never appears.
5. Restart Administrator. Start the Communicator service, then reopen the Administrator application. The Bolid drivers now appear in the device driver selection list.
6. Create the communication line and device. Add the device under the appropriate Communicator line, select KpS2000PP as the driver, and set the device address to match the C2000-PP configuration.

Configuration Base: Required Enumerations

Before creating input/output channels for the Bolid device, define the enumerations in the Formats table of the configuration base. Without these, channel values display as raw integers and command channels offer no operator-meaningful choices.

Value ordering is positional — the enumeration index maps directly to the numeric value the driver reports or transmits, so do not reorder or insert entries. Semantic mapping of the state list:

Assign BolidState to input channels representing zones (loops) and partitions. Assign BolidCommand or the reduced DisarmArm set to output/command channels depending on whether the operator should have access to the extinguishing-system commands.

Supported Control Functions and Event Reporting

Confirmed control capability through the C2000-PP path:

• Arm and disarm partitions (sections) from SCADA command channels.
• Arm and disarm individual loops (zones).
• Automation enable/disable and extinguishing start/reset commands are exposed in the BolidCommand enumeration.

Pushing alarm events from Rapid SCADA into the Bolid system

Whether Rapid SCADA can originate alarm events into the C2000 system (as opposed to reading them) is not a confirmed capability. This depends entirely on what the C2000-PP integration module exposes on its protocol interface. Decision path:

1. Consult the C2000-PP module documentation and identify whether writable event/alarm registers exist, or whether the interface is read-only for status plus a fixed command set.
2. If writable objects exist, map them to Rapid SCADA output channels and verify with a loopback test on non-production hardware.
3. If they do not, implement the alarm annunciation in the SCADA layer (events, notifications) and treat the panel as the authoritative source of fire/security state.

Do not design the life-safety annunciation chain around an unverified write path. Verify against the C2000-PP protocol documentation first.

Migration Planning for Rapid SCADA 6

Because the configuration base (channels, enumerations, views) is largely portable while the driver layer is not, the driver choice — not the channel design — is the migration risk. Standardize on the C2000-PP module across sites so a single driver port covers the whole fleet.

Commissioning Checklist

1. Driver files present in SCADA\ScadaComm\KP and unblocked.
2. Driver visible in Administrator device configuration dialog.
3. Communication line opens the serial/network port without error in the Communicator log.
4. Device polls successfully; raw state values increment through the expected 0–10 range when zones are exercised.
5. BolidState, BolidCommand, DisarmArm enumerations created in Formats and bound to the correct channels.
6. Arm/disarm command round-trip verified: send command, confirm panel state change, confirm SCADA reads back Vzyat/Snyat.
7. Extinguishing commands access-controlled or removed from operator views.

FAQ