System architecture
Eight typical setups Coselium devices are used in: what connects to what, over which line and protocol. Values are the factory defaults from the product datasheets.
Setup A
FiOC-40 as the panel controller
In an AHU, pump set, boiler or chiller panel the control logic runs on the FiOC-40 as a Sedona application. Sensors and outputs are wired to the terminals; devices such as energy meters or drives are read over the RS-485 line with Modbus RTU. The application is edited live with Coselium Workbench, and initial settings can be made on site from a phone over BLE.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| Temperature, humidity and pressure sensors | FiOC-40 UI | Terminals | NTC, PT1000, NI1000, 0–10 V, 4–20 mA |
| FiOC-40 FIO / DO | Valves, dampers, pumps and fans | Terminals | 0–10 V / 2–10 V analogue output, relay |
| FiOC-40 | Energy meter, drive | RS-485 | Modbus RTU master, 9600 8N1 |
| Engineering PC | FiOC-40 | Ethernet | Coselium Workbench, SOX (UDP 1876) |
| Phone | FiOC-40 | Bluetooth LE | Mobile commissioning |
Setup B
Adding points to an existing BMS: FiO-40
FiO-40 is a remote I/O that needs no programming. With its fixed Modbus register map and BACnet object model it connects directly to an existing BMS or controller; in retrofits it adds dry contacts, analogue sensors and outputs. One protocol runs on site at a time: Modbus or BACnet. If communication is lost, outputs go to per-channel default values.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| BMS / SCADA | FiO-40 | Ethernet | Modbus TCP (port 502) or BACnet/IP (UDP 47808) |
| Controller | FiO-40 | RS-485 | Modbus RTU slave (9600 8N1) or BACnet MS/TP (38400) |
| Contacts, sensors, meters | FiO-40 DI / UI | Terminals | DI1–DI4 can also be pulse counters |
Setup C
I/O expansion: FiOC-40 and FiO-40
When a panel needs more than 40 points, the control logic stays on the FiOC-40 and the extra points come from FiO-40 modules. The FiOC-40 reads and writes the FiO-40s as a Modbus master: Modbus RTU on the RS-485 line or Modbus TCP over Ethernet. Because the FiO-40 register map is fixed, nothing is programmed on the FiO-40 side. Planning allows up to four FiO-40s per FiOC-40; Configurator, the tool our dealers use, distributes points over the devices by this rule. The supervisory system sees the FiO-40 points through the FiOC-40.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| FiOC-40 | FiO-40 (RTU address 1–4) | RS-485 | Modbus RTU master → slave, 9600 8N1 |
| FiOC-40 | FiO-40 | Ethernet | Modbus TCP master → FiO-40, port 502 |
| FiOC-40 application | BMS / Niagara | Ethernet | Modbus TCP slave, BACnet/IP or cosel modules |
| Engineering PC | FiOC-40 | Ethernet | Coselium Workbench, SOX (UDP 1876) |
Setup D
RS-485 field devices: drives and energy meters
The FiOC-40 works as a Modbus RTU master on the RS-485 line. Modbus RTU devices such as variable frequency drives and energy meters are daisy-chained on the same line, each with its own slave address. Line speed is 2400–115200 baud with no, odd or even parity; the default is 9600 8N1. One serial protocol runs on the line at a time. Termination (EOL) is switched on at the devices at both ends of the line, BIAS is selected on a single mid-line device on long lines and the rest stay OFF; on Coselium devices this is a three-position switch next to the RS-485 terminals. The values read are used in the application and can be served to the supervisory system over Modbus slave or BACnet.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| FiOC-40 | Drives, energy meter | RS-485 | Modbus RTU master, a slave address per device |
| Line start (FiOC-40) and last device | — | RS-485 | BIAS/EOL: EOL at both ends, OFF in between |
| BMS / SCADA | FiOC-40 | Ethernet | Modbus TCP slave (port 502) or BACnet/IP (UDP 47808) |
Setup E
Bringing MS/TP devices onto BACnet/IP: router
BACnet MS/TP devices such as fan-coil thermostats are connected to the FiOC-40 RS-485 line. When BACnet/IP and MS/TP are enabled together on the FiOC-40, the device routes between the two networks; the BMS sees the MS/TP devices over BACnet/IP. This is enabled by the optional router feature on top of the base licence. The IP and MS/TP network numbers must differ (default 1 and 2). FiO-40 does the same job with a Level 2 licence.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| BMS | FiOC-40 | Ethernet | BACnet/IP, UDP 47808, network 1 |
| FiOC-40 | Fan-coil thermostats | RS-485 | BACnet MS/TP, 38400 baud, network 2 |
Setup F
With Niagara N4
Coselium devices connect to Niagara N4 with the cosel module family (Niagara 4.12 and later). There are two paths. If the service PC can reach the device network, the device can be reached directly from Niagara Workbench and the application programmed without setting up a station. If the device must be monitored continuously, the station driver is used: the station finds the device and brings in its points and schedules. Remote access goes through the station. FiO-40 does not connect to Niagara directly: it is connected to a FiOC-40 and its points reach the station through the FiOC-40.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| Niagara Workbench | FiOC-40 | Ethernet | Direct connection (SOX, UDP 1876) |
| Niagara station | FiOC-40 | Ethernet | cosel station driver: device, points and schedules |
| FiOC-40 | FiO-40 | RS-485 | Modbus RTU or Modbus TCP; points reach the station through the FiOC-40 |
Setup G
Joining two lines: FiO-40 gateway and router
Gateway and router functions, enabled by licence, join two lines without a separate network device. With a Level 1 licence the FiO-40 is a Modbus gateway in both directions: a Modbus TCP client on Ethernet reaches the Modbus RTU devices on the RS-485 line (one client at a time), or an external RTU master on the line reaches a Modbus TCP device on Ethernet. A Level 2 licence adds the BACnet/IP ↔ MS/TP router; the IP and MS/TP network numbers must differ.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| Modbus TCP client | Modbus RTU devices on RS-485 | Ethernet ↔ RS-485 | Modbus TCP → RTU gateway — Level 1 |
| External RTU master on the line | Modbus TCP target | Ethernet ↔ RS-485 | Modbus RTU → TCP gateway — Level 1 |
| BACnet/IP network | BACnet MS/TP line | Ethernet ↔ RS-485 | BACnet router — Level 2 |
Setup H
Sending data to a broker with MQTT
The FiOC-40 connects to an MQTT broker; MQTT needs no licence. Values in the application are published to the broker and writable values take commands through it, so a dashboard, SCADA or another application can monitor values and send settings. Each device is identified on the broker by its serial number. The connection can be protected with TLS (server certificate or mutual TLS); certificates are uploaded from the device web interface. The topic structure is given in the product datasheet; our dealers can assist with the setup.
| From | To | Line | Protocol / setting |
|---|---|---|---|
| FiOC-40 | MQTT broker | Ethernet | port 1883; 8883 with TLS |
| FiOC-40 | Dashboard / SCADA | Ethernet | Value publishing |
| Application | FiOC-40 | Ethernet | Commands (writable values) |
Ports and factory defaults
| Interface | Function | Default | Device |
|---|---|---|---|
| Ethernet | Modbus TCP | port 502 | FiOC-40, FiO-40 |
| Ethernet | BACnet/IP | UDP 47808 | FiOC-40, FiO-40 |
| Ethernet | MQTT | port 1883; 8883 with TLS | FiOC-40 |
| Ethernet | Workbench connection (SOX/DASP) | UDP 1876 | FiOC-40 |
| Ethernet | Web interface | HTTP, port 80 | FiOC-40, FiO-40 |
| Ethernet | Modbus gateway-server | port 504 (Level 1 licence) | FiO-40 |
| Ethernet | Modbus gateway-client target | 192.168.1.50 / 1502 | FiO-40 |
| Ethernet | Factory IP address | 192.168.1.160/24 | FiOC-40, FiO-40 |
| RS-485 | Modbus RTU | 9600 8N1 | FiOC-40 (master/slave), FiO-40 (slave) |
| RS-485 | BACnet MS/TP | 38400 baud | FiOC-40, FiO-40 |
| Ethernet ↔ RS-485 | BACnet network numbers (router) | IP 1, MS/TP 2 | FiOC-40, FiO-40 |
| Bluetooth LE | Mobile commissioning | — | FiOC-40, FiO-40 |
Values are factory defaults and are changed per project; the full list is in the product datasheets.
Who installs it?
Design, installation and commissioning are carried out by our partner dealers. For help with product selection or to find a dealer in your region, please contact us.