Honeywell CIPer Model 50

Compatibility

Compatible with EpiSensor Edge over BACnet/IP

Edge’s BACnet/IP client reads the objects the commissioned Niagara station exposes on the controller’s Ethernet network. Honeywell documents the BACnet B-BC profile and BACnet/IP and BACnet MS/TP transports, and user guide 31-00198-03 gives network and update-rate starting points. Object identifiers come from the installed station, not a factory point map. BACnet MS/TP is not an Edge route.

Use product data 31-00197-03 and user guide 31-00198-03, Rev 07-2021. Site check: record the installed order code, Niagara version and station identity, then compare one selected value with the Niagara point view. Keep the existing network, application and control configuration unchanged.

Connect it with

• Gateway ZGW-20 From €899 ex VAT Configure
• Evaluation Gateway on a Raspberry Pi Edge with one device licensed Free Set up

Models

Specifications

Honeywell identifies CIPer Model 50 as a Niagara 4 plant controller for multi-protocol applications, with a configurable display and expansion for up to 2,500 points.^{1, 2, 3, 4}

Exact family

CIPer Model 50 plant controller; record the exact order code and hardware revision^1, 2

Framework

Niagara 4^1, 2

Published BACnet transports

BACnet/IP and BACnet MS/TP¹

Onboard I/O

26 terminations according to the product brochure²

Expansion statement

Up to 2,500 points; actual station capacity and exposed objects depend on licence, drivers, engineering and installed I/O¹

Edge route

BACnet/IP client reading the station’s exposed objects; object identifiers and access settings come from the installed station^{1, 2, 3, 4}

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.

Setup

1. Record the exact installed controller

   Record the order code, Niagara version, station name and licensed drivers. Use the actual network settings: the manual defaults are Ethernet 1 at 192.168.200.20/24 and Ethernet 2 at 192.168.201.20/24, on separated networks. They are identification clues, not addresses to impose on an existing site.

2. Select one existing station point

   Open the existing Niagara graphical point view and select an identified physical temperature or meter reading. Record its station path, displayed value, unit and source. A synthetic 23.4 °C display means 23.4 °C, not a raw register needing another scale. If that point is already exposed over BACnet, retain its actual device/object identifiers and compare an external read with this same view. Ask for an export only when the station does not expose the required point.

3. Protect the controls network

   Use the approved internal Ethernet network or VPN; Honeywell explicitly excludes Internet exposure of BACnet port 47808. RS485-1 is isolated, RS485-2 is not; each may already serve Panel Bus, BACnet MS/TP or Modbus. Preserve its assigned role and termination. Niagara user permissions are distinct from BACnet network access.

4. Prove a small observation set

   Compare repeated readings against the station and physical source at the same time. Panel Bus Normal polling defaults to 10s, so a faster external poll cannot make its source fresher. The manual reports occasional MS/TP update delays in its example tests and recommends keeping CPU load below 80%. Inspect current load and point timing before expanding; these examples are not a universal external-client capacity.

Common questions

Can Edge monitor CIPer Model 50 over BACnet/IP?

Yes. Edge’s BACnet/IP client reads the objects the commissioned station exposes, and the public manuals provide a practical network and point-comparison starting point. Use the installed station’s object identities and compare a read with Niagara. A firmware-matched universal object schedule is not needed to start.^1, 3, 4

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.^1, 2

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.²