Orisec CP-series
Orisec CP-series alarm panels on Control4 as a security panel, with a real sensor device for every zone.
£ 0.00
£ 0.00
Invalid email
Orisec CP-series
Orisec CP-series alarm panels on Control4 as a security panel, with a real sensor device for every zone.
An Orisec CP-50, CP-100 or CP-200 streams its zones and states on its Control 4 port. This driver reads that port over RS-232 or over the network and presents the panel to Control4 as a Security Panel with its partitions and zones.
It goes a step further than a zone list. On request, or automatically after each read, it creates a Control4 sensor device for every zone: a door or window contact, motion sensor, smoke detector, CO detector or water sensor, bound to the panel's own zone output and kept up to date with the zone's open and closed state. Each one can be placed in a room, used in programming and shown in the customer app.
The panel owns the alarm, so the driver takes it at its word. Each zone's Control4 type is the one the panel reports, never a guess from the zone's name, and changing a type is done where it belongs, in the panel's zone programming.
- A device for every zone
- Provision Zone Devices creates a Control4 sensor device per zone, names it from the zone, binds it to the panel and keeps its state live. Set Auto Provision Zone Devices to Yes and it happens a few seconds after each read.
- Safe to run again
- Provisioning skips any zone that already has a device, so a second read or a second click never creates duplicates. Remove Provisioned Zone Devices deletes only the devices the driver created; devices added by hand are never touched.
- Zone types from the panel
- The driver relays the Control4 type the panel publishes for each zone. How an engineer names a zone never changes how Control4 treats it.
- Room visibility in one step
- Move each sensor to its room, then run Hide Provisioned Sensors In Other Rooms: each stays visible where it lives and disappears everywhere else. A paired action shows them all again.
- Serial or IP
- Bind either the serial connection or the network connection and the driver uses whichever is connected, so the panel does not have to sit next to the controller.
- Reads large panels without stalling
- Each zone is enrolled once rather than removed and re-added on every Read from Panel, which is what stalled Composer on panels with many zones.
| Model | Orisec CP-50, CP-100 and CP-200 alarm panels |
|---|---|
| Manufacturer | Orisec |
| Panel port | The panel communications port set to Control 4 |
| Transport | Serial RS-232, 9600 8N1 over a 9-pin null-modem lead, or TCP through the panel's IP module or a serial-to-IP gateway |
| Control4 proxies | Security Panel and security partitions |
| Arm modes | Full Arm and three Part Arm modes; the Part Arm labels are editable |
| Sensor devices | Door and window contacts, motion, smoke, CO, water, and a contact switch for anything else |
| Platform | Control4 DriverWorks, Lua |
Which zones come through to Control4?
Every zone with the panel's Send real-time status attribute set. Set it in the panel's zone programming, then run Read from Panel; it can be run again at any time to refresh the list.
A zone shows the wrong type. Can I change it in Composer?
No, by design. The type comes from the panel. Change the zone's type in the panel's zone programming and read again, and provisioning follows.
Why are there no glass-break, gas or heat devices?
The panel does not distinguish those devices, so it never reports those Control4 types. Fire zones become a Smoke Detector and anything without a matching device becomes a Contact Switch.
Does it need a serial cable to the controller?
No. Where the panel is not next to the controller, connect its Control 4 port to the network through the panel's IP module or a serial-to-IP gateway, and set the driver's Network Port to match.