Honeywell CIPer Model 50

Building automation controller

Honeywell describes CIPer Model 50 as a Niagara 4 plant controller with BACnet/IP and BACnet MS/TP communications, 26 onboard I/O terminations and expansion for large multi-protocol applications. The public material confirms the controller family and transports, but does not provide an exact hardware and Niagara-version PICS, commissioned object schedule, client permissions or point-quality contract. Direct Edge monitoring therefore remains unverified. The CIPer controller and its authorised BMS remain authoritative for HVAC logic, schedules, alarms and outputs.

  • BACnet/IP
  • BACnet MS/TP

Building automation controller

Compatibility

Direct Edge integration not yet verified

Honeywell publishes BACnet/IP and BACnet MS/TP support for CIPer Model 50. The retained public sources do not identify an exact order code and Niagara build with its matching PICS, commissioned BACnet object schedule, network policy or read permissions. A protocol label alone does not release a direct client path.

Record the complete CIPer Model 50 order code, hardware revision, Niagara 4 version, station backup and installed drivers. Obtain the matching Honeywell or Tridium PICS and the commissioned BACnet object export through the authorised BMS channel. Monitoring must be read-only. Do not change schedules, setpoints, priorities, overrides, alarms, logic, outputs or equipment commands.

Models

Download
ModelsInterfaceRoute into Edge
CIPer Model 50Honeywell publishes BACnet/IP, BACnet MS/TP, Niagara 4, 26 onboard I/O terminations and panel-bus expansion for plant-controller applications.Hold a direct Edge route until the exact installed controller, Niagara version, PICS, commissioned object schedule and read permissions are retained.
CIPer Model 30 and CIPer Model 10Separate CIPer controllers with different hardware, switching, I/O and application roles.Do not reuse the Model 50 identity, capacity or network assumptions for another CIPer model.
XL-500 and XL-800 retrofit installationsHoneywell describes Model 50 as able to reuse existing panel-bus I/O in retrofit work.Treat the retained field I/O, controller station and exposed BACnet objects as project evidence. Retrofit capability does not create a fixed object map.

Specifications

The product page names BACnet/IP and BACnet MS/TP communications to ANSI/ASHRAE 135-2012. It does not publish the installed station's object identifiers, units, commandability or access policy.1

Exact family
CIPer Model 50 plant controller; exact order code and hardware revision remain installation evidence12
Framework
Niagara 412
Published BACnet transports
BACnet/IP and BACnet MS/TP1
Onboard I/O
26 terminations according to the product brochure2
Expansion statement
Up to 2,500 points; actual station capacity and exposed objects depend on licence, drivers, engineering and installed I/O1
Evidence gap
No retained exact-order-code PICS, Niagara-version object contract, commissioned object export, client permission model or published Edge pairing12

Interface

Documented measurements and integration boundaries for CIPer Model 50.

  • Potential room, plant, flow, temperature, pressure, energy and equipment-state observations depend on the commissioned Niagara station and BACnet object schedule.
  • Record each approved BACnet device and object identifier, object type, engineering unit, source sensor or meter, update behavior and quality indication.
  • Keep alarms, schedules, histories and derived values distinct from live physical measurements and preserve their Niagara source and time basis.
  • Setpoints, commandable objects, priority-array writes, overrides, alarm acknowledgements, schedules, logic, outputs and equipment commands remain outside this guide.

Assessment

An exact CIPer Model 50 installation after order code, Niagara version, station, PICS, object export and network policy are retained; no released Edge path or control.

InteroperabilityLimited
Honeywell confirms BACnet/IP and BACnet MS/TP, but the public material does not provide the exact installed PICS or commissioned object schedule.1
AccuracyNot yet assessed
The station can contain local, integrated and derived points, but the public sources do not establish source accuracy, units or quality behavior for a project point.2
SecurityNot yet assessed
The retained public sources do not define the installed Niagara account, BACnet network policy, encryption or client privilege boundary.1
ReliabilityNot yet assessed
No retained contract defines external polling limits, stale values, quality propagation or restart behavior for the installed station.2
RuggednessSupported with conditions
Honeywell identifies EN 60730-1, EN 60730-2-9, UL 60730 and UL 916 certifications, while installation ratings still require the exact hardware documentation.1
ScalabilitySupported with conditions
Honeywell states expansion for up to 2,500 points, but licences, drivers, network load and exposed objects bound the actual project.1
LifecycleSupported with conditions
Honeywell retains the product and controller-family material, but exact market availability, Niagara support and authorised service status must be checked for the installed unit.12

Setup

  1. Record the exact installed controller

    Record the CIPer order code, hardware revision, serial number, Niagara version, station name, licence and installed drivers. Obtain an authorised station backup before planning an external client.

  2. Obtain the commissioned object contract

    Request the matching PICS and BACnet export from the BMS owner. For each required observation retain the device and object identifiers, type, name, unit, source, quality behavior, update interval and commandability.

  3. Protect the controls network

    Use the approved building-controls network design and a dedicated read-only client identity where the installed platform supports one. Do not bridge an MS/TP trunk directly or bypass the site's BACnet routing and security policy.

  4. Prove a small observation set

    Compare a bounded set of non-commandable objects with the Niagara view and original sensors or meters. Test stale data, controller restart and communications loss without changing plant operation.

Common questions

Can Edge monitor CIPer Model 50 over BACnet/IP?
Honeywell confirms BACnet/IP support, but the public material does not provide the exact installed PICS, object schedule or read-permission contract needed to release a direct Edge path. The integration remains unverified until those project documents and a read-only pilot are reviewed.1
Does the 2,500-point statement mean every point is available to Edge?
No. It is a controller expansion statement. The available BACnet objects depend on licence, installed drivers, station engineering, point exposure, network policy and the commissioned application.12
Can Edge write HVAC setpoints or schedules through this guide?
No. The CIPer controller and authorised BMS remain responsible for plant logic and command priority. This guide releases no write, override, alarm acknowledgement, schedule change or equipment command.2

Sources

  1. CIPer Model 50 Controller product page (opens in a new tab) Honeywell Building Automation
  2. CIPer Controllers product brochure 01-00112 (opens in a new tab) (PDF) Honeywell Building Automation

Further reading

Product names and trademarks belong to their owners. Publication does not imply endorsement or a commercial relationship.