Node-HIU controls and monitoring documentation

Node-HIU Switch

M8

A walk-through of the the Node-HIU Dashboard on a real world development.

The Node-HIU Switch is used to connect HIUs to a Local Area Network (LAN) to provide remote connectivity, and implement control strategies through distributed logic.

It guarantees efficient and reliable heat network operation, and is used by a growing number of house builders and local authorities.

Not just any BMS motioning system - the most advanced HIU management system in existence, from the manufacturers of the most efficient HIUs in existence.

The Node-HIU Switch Provides

Cloud2
  • 100% accurate commissioning of every single HIU on a heat network
  • Real-time, one second resolution data, so every event is captured
  • Remote commissioning
  • Remote user control
  • Warning and alarm detection, so no problem goes unrecognised
  • Routing of alarms to personnel, so no problem goes unreported
  • Performance monitoring and tracking
  • Reports from various stages of installation through commissioning, to to hand-over and beyond, uploaded to a shareable Dropbox folder
  • A connection between BMS systems in plantroom and HIUs as a Modbus slave
  • The means to implement peak load (capital expense) saving strategies, such as rapid load shedding
  • Additional sensor options for differential pressure and temperature sensing on network
  • Plantroom BMS functionality, including pump and boiler control as a Modbus master
  • End to end functionality on the same software platform
  • Device communications over RS485, RS232, Modbus, OneWire & Relays
  • Network communications over Ethernet, WiFi, GSM, or USSD
  • Built on unified open-source technologies

Fully automated, exceptionally efficient heat networks, with a resilient architecture based on distributed nodes that monitor performance and route alarms when they appear.

An IoT network for a heat network.

Documentation

Network Dashboard

The Network Dashboard is run from one or two Node-HIU Switches on a network, having a fixed network address, to provide access to a browser based dashboard system.

This dashboard reads and filters all HIU traffic to present important information in the most useful way.

System Summary

To provide installation teams and site management with a simple visual indicator of a heat network's health and performance.

The number of warnings and alarms are clearly indicated, as well as the current system demand (litre/minute), and VWART (Volume Weighed Average Return Temperature).

Dashd1

As new warnings and alarms appear, they are forwarded via email to the relevant persons. The Node-RED programming environment allows alarms to be routed based on any logic required. Typically alarms will go to front-line engineers first, and if the persist after a specified time will go to a second tier of management, and so on.

Historic Loads and VWARTs

The summary page provides a link to the recorded load history, at 5 second resolution.

Vwload2

Commissioning Dashboard

The HIU Commissioning Dashboard provides access to data from all HIUs on the network.

Changes in HIU data are updated every second.

Dashc1

The dashboard shows current HIU readings, as well as settings, and operational parameters and checks. Alarms (need attention now) and warnings (need attention when convenient) are presented in the form of coloured boxes, giving a clear indication of what needs attention.

The following problems can be automatically identified by the system and presented as alarms:

  • Incorrect HIU settings
  • Low central heating pressure and leaks on heating circuit
  • Low differential pressure on network
  • Low temperature on heat network
  • Crossed pipes
  • Bypass flow on network
  • Blocked strainers and pipework
  • High/low/failure on central heating pump
  • Excessive delays in generation of DHW (hot water to taps)
  • Unbalanced radiators
  • HIU power off (loss of communication to single HIU)
  • Node power off(loss of communication to Node-HIU Switch)
  • Ethernet down (general loss of communication)

The data is also summed to drive operational statistics, such as the current and historic VWART - average return temperature weighed by volume.

Engineer Screen

The Engineer Screen provides more detailed data on selected HIUs, and allows HIU settings to be changed.

Dashe1

The engineer screen provides links to one second resolution recordings of all recent hot water events.

Dashdhw1

Other Dashboards

  • Plantroom control panel display

  • Remote DP & Temperature Sensor

  • Plantroom control system

  • Diversified load analysis

  • M-Bus

  • Data options

  • HIU readings

Plantroom control panel displayRemote DP & Temperature SensorPlantroom control systemDiversified load analysisM-BusData optionsHIU readings

Network Topology

Mobile Infrastructure

File:mobileswitches.svg

Mobileswitches

A temporary infrastructure enables the full system to be deployed without any cabling, using GSM communications to a cloud server.

Data charges for each system are approximately £1.50 per month per HIU, making hard-wired infrastructure preferable for long term use on large numbers of dwellings.

Wired Infrastructure

Ethernet

File:Node-hiu-switches.svg

Node-hiu-switches

Extended to Fibre

Node-hiu-switches-extended

Integral Ethernet

The following layout is for HIUs with onboard Ethernet (build in Node Switch).

Node-hiu-internal-ethernet

Modbus

The following layout is for HIUs with onboard Modbus.

Node-hiu-switches-modbus

MQTT Infrastructure

  • One to eight HIUs (Hydraulic Interface Units) connecting to a single Node-HIU Switch, over RS485. Cat6 cable (4 twisted pairs) is used to also convey M-Bus data, and two other.

  • One to eight (or more) Node-HIU Switches connect to an Ethernet Switch, typically using PoE (Power Over Ethernet) to obtain power as well as a network connection. Cat6 network cable is used for connection. From the Nodes, the M-Bus network is run separately, in parallel, in 2.5mm twin core cable.

  • Network Switches daisy chain (or loop) to the Internet Router / Modem / default gateway. Cat6 network cable is used for connection.

  • One or two Node-HIU Switches on a network are given a fixed address and host the key services with redundancy:

    • MQTT Messaging Service (can optionally be a cloud based service)
    • User Dashboard
    • VPN Service, for secure remote connection to dashboard

Optionally:

  • A Node-HIU Switch provides a Modbus Interface to BMS.
  • One or more Node-HIU Switches with attached differential pressure & temperature sensors to feed back riser data for pump control.
  • A port on the local network (LAN) is forwarded (by the default gateway) to the designated Node-HIU Switch providing the local networks MQTT services. This is to enable connections to be established from a plantroom, or for protected user connectivity via MQTT enabled phone apps.
  • A port on the local network (LAN) is forwarded (by the default gateway) to a designated Node-HIU Switch providing
    • HTTPS Connection, for encrypted remote connection
    • Reverse Proxy Hosting, for addressing devices running browser based services

And where cabling is not possible the GSM route is available.

  • Wiring

  • GSM Wiring

Compatible HIUs

The Node-HIU system is designed to work with our full range of electronic HIUs, known across the industry as the most efficient systems ever tested independently to the BESA standards, as referred to in the latest codes of practice.

The DATA HIU

  • The SLIM HIU Single Plate HIU for DHW or UFH. More...

  • The DIGI HIU Single Plate Electronic HIU for DHW with Direct Heating. More...

  • The DATA HIU Twin Plate Electronic HIU. More...

  • The SLIM Extra HIU Single Plate Electronic HIU. More...

  • The DATA SPLIT HIU Twin Plate Electronic HIU. More...

  • The DATA Extra HIU Twin Plate Electronic HIU with 70kW Heating Output More...

The SLIM HIU Single Plate HIU for DHW or UFH. More...The DIGI HIU Single Plate Electronic HIU for DHW with Direct Heating. More...The DATA HIU Twin Plate Electronic HIU. More...The SLIM Extra HIU Single Plate Electronic HIU. More...The DATA SPLIT HIU Twin Plate Electronic HIU. More...The DATA Extra HIU Twin Plate Electronic HIU with 70kW Heating Output More...

The system can also interface with any HIU that uses Modbus RTU for communications.

Hardware Specification

Nodehiuswitch
ModelNode-HIU Switch M8
HIU Connections8 x RS485 8 x M-Bus (separate network)
Network Connections1 x Ethernet 2 x M-Bus WiFi Bluetooth Low Energy (BLE) Modbus RTU (utilises one of the RS485 ports)
PowerStandard: 5v 2.5A Mains Plug Adapter Option: Power Over Ethernet (PoE)
ProcessorQuad Core 1.2GHz Broadcom BCM2837 64bit CPU
Memory1GB RAM
Expansion2 x USB Ports 40 Pin GPIO Header
Optional PeripheralsTemperature Sensors (daisy chain of up to 10) Differential Pressure Sensor GSM USSD Modem Flash Data Storage Drive

Software Specification

Logic ControlNode-RED
Communications ProtocolsMQTT HTTP HTTPS M-Bus (Master) Modbus (Master/Slave) HIU Serial (Thermal Integration) User Defined Serial
Hosted ServicesNode-RED Dashboard Mosquitto MQTT Service VPN Host HTTPS Reverse Proxy (certificates required)
Client ServicesHeatweb Cloud Storage, for data logging Dropbox, for shared data storage and retrieval Email, for reporting and alarms
Software PlatformsNode.js (Node-RED) Python

MQTT

MQTT Topic Structure

We use a common MQTT topic structure across all projects.

Topics are split into 5 levels, separated by a slash. They are case sensitive and should be free of spaces or special characters.

network / node / device / group / key

These levels allow us to organise data in a standard structure, and to set permissions accordingly.

LevelDescription.
networkA unique identifier for the heat network.
nodeAn unique (for each network) identifier for each system running Node-RED on a network, MAC address, or a fixed LAN ip address.
deviceAn identifier for the connected device (e.g. HIU serial number) or sub-system.
groupThe type of data. This is used for basic grouping, and for controlling data access.
keyAn identifier for the data.

As an example, the following would be a typical topic referring to temperature data:

CO102XW/b4hdn76s/d234ab3c7800fee1/dat/tH

Standard MQTT Topics for HIUs

The following table shows the structure of standard topics available for each HIU.

Readings

GroupKeyDescriptionUnits
dattCHoTemperature of flow to central heating°C
dattHTemperature of primary flow°C
dattHoCHTemperature of primary return on central heating°C
dattCoTemperature of DHW flow to taps°C
dattHoDHWTemperature of primary return on DHW°C
datlast_tCoLast recorded tap use, DHW supply temperature°C
datlast_tHLast recorded tap use, primary supply temperature°C
datlast_tHoDHWLast recorded tap use, primary return temperature°C
datTTdhwSetpoint temperature for DHW°C
datfHCHFlow rate on primary for central heatingltr/min
datfCFlow rate of DHW to tapsltr/min
datfHDHWFlow rate on primary for DHWltr/min
datdpHDifferential pressure on primary circuitbar
datpCHCentral heating pressurebar
datstatCall for central heating (room thermostat) on volt free wiring connection0 / 1
datpumpPump activated0 / 1
datxCHCentral heating valve position0-270
datxDHWDHW valve position0-270
datstSystem state
dateSError state
dateTTime in error stateseconds
datvHVolume drawn on primary since bootlitres

Settings

GroupKeyDescriptionUnits
settingssetpointSetpoint temperature for DHW°C
settingsWarmupBoostBoost flow rate when flushing cold primary feedltr/min
settingsEcoModeKeep warm modeeco / comfort
settingsPressureModeDifferential pressure calculation modeauto / bar
settingsPowerUpCounterNumber of times the HIU controller has been powered
settingsErrorCounterTime in error stateseconds
settingsDHReturnLimitCentral heating primary return limit°C
settingsHESupplyMaximum central heating supply temperature°C
settingsPumpTimeoutCentral heating pump over-runseconds
settingsPumpProtectionPump low pressure protection enabled0 / 1
settingsHEProtectionModeCentral heating return limit enabled0 / 1
settingsDHWExchangerAntiLegionellaAnti-Legionella cycle enabled0 / 1
settingsDHWExchangerEcoHeatTemperatureKeep warm temperature°C
settingsDHWExchangerEcoHeatTimeKeep warm timerminutes
settingsCentralHeatingControlCentral heating enabled0 / 1
settingsPrePayShutOffHIU enabled (for prepay control)0 / 1
settingsBUILDDATEFirmware build date
settingsBUILDTIMEFirmware build time

Statistics

GroupKeyDescriptionUnits
statvCDHW accumulated totallitres
statDHWCountNumber of tap uses
state_TEMPERATURESENSORSError relating to temperature sensors
state_FLOWSENSORError relating to DHW flow sensor
state_PRIMARYCONTROLError relating to valves
state_DISTRICTHEATINGError relating to heat network
state_CHRETURNTEMPError relating to central heating return sensor
state_DHWTEMPError relating to DHW temperature sensor
state_DISTRICTHEATINGTEMPError relating to heat network temperatures
state_DHRETURNTEMPError relating to DHW return sensor
state_CENTRALHEATINGError relating to central heating
state_WARMUPTIMERError relating to warm-up times
state_CHTEMPWARNINGWarning relating to central heating temperatures
state_CHTEMPERRORError relating to central heating temperature sensor
stattisTime in current stateseconds
statbeaconHIU alive beacon

System Variables

GroupKeyDescriptionUnits
systemnodeA unique identifier for the Node-HIU Switch
systemnetworkA unique identifier for the network
systemSerialThe serial number of the HIU
systemlastcontactThe time the HIU last made contact
systemtimeThe unix time the HIU last made contact
systempropertyThe property location
systemFirmwareHIU firmware version
systemCPUcore_1Node processor 1 usage%
systemCPUcore_2Node processor 2 usage%
systemCPUcore_3Node processor 3 usage%
systemCPUcore_4Node processor 4 usage%
systemCPUMemoryNode memory usage%
systemiplanIP address on local network
systemmacMAC address
systemipwanIP address on internet
systemtempidTemporary (weekly) id for HIU
systemusbUSB port identifier for HIU
systemNodewareNode software version

Node Settings

GroupKeyDescriptionUnits
localn_tempidTemporary id
localn_logtosdLog data to SD card
localn_logtoheatwebLog data to heatweb.info
localn_logtopoolLog DHW data to public data pool under temporary (anonymous) id
localn_ptypeProperty type
localn_flowNode-red flow template
localn_networkNetwork id
localn_rolemodelNode-red flow template author system
localn_SYSidheatweb.info id
localn_nodeNode id
localn_readonlyread only file system
localn_emailAdministrator email address
localn_runcountNode power-up counter

MQTT is a publish/subscribe system, and devices can subscribe to topics using wildcards.

DescriptionMQTT Topic
All network data (admin level)network/#
All data from a unique node+/node/#
All differential pressure data on the networknetwork/+/+/+/dpH
All DS18B20 temperature sensors on networknetwork/+/+/ds18b20/#
All Alarms from networknetwork/+/+/alarm/#

Standard MQTT Topics for Heat Meters

The following table shows the structure of standard topics available for heat meters.

Readings

Note that HM stands for Heat Meter. Cooling meters would have a CM instead.

In the topic structure, the Node level represents the unique identifier (serial number) of the M-Bus Gateway the meter is connected to.

GroupKeyDescriptionUnits
dattHMfTemperature of primary flow°C
dattHMrTemperature of primary return°C
datkwhHMEnergy used to datekWh
datkwHMCurent powerkW
datfHMCurrent primary flow ratelitres/minute
datvHMVolume used to datelitres

Stored Data

Where data is stored it is in JSON format, the IoT standard.

The topic CO102XW/b4hdn76s/d234ab3c7800fee1/dat/tH would form part of a data object with the following structure:

CO102XW.b4hdn76s.d234ab3c7800fee1.dat.tH = 75.3

The output JSON would look like:

{"CO102XW":{"b4hdn76s":{"d234ab3c7800fee1":{"dat":{"tH":75.3}}}}}

For multiple devices this may look like:

{"CO102XW":{"b4hdn76s":{"d234ab3c7800fee1":{"dat":{"tH":75.3,"tHoCH":42.3}}},"cfg566fg":{"d65ahchddk8899hh":{"dat":{"tH":70.1}}}}}

File:test.json

Modbus

Modbus Slave Request Log

Nodedp2

Modbus Setup

Address17
Baud9600
Data Bits8
ParityNone
Stop Bits2
Data Type16INT
Function Codes3 (read), 6 (write)

Modbus Registers

DescriptionRegisterUnits
Lowest differential pressure1kPa [x10]
Age of Lowest2seconds
Highest differential pressure3kPa [x10]
Age of Highest4seconds

Node-RED

Node-RED is an open-source visual programming system, developed by IBM, based on JavaScript code and nodes that are programmed and wired together in a browser based editor. It can run on just about any computer system, from the humble Raspberry Pi to cloud based platforms.

Noderedflow2

It is used at every level of the Node-HIU system, and not just on our own systems, but also those of the mobile providers and IT equipment manufacturers. For the first time, all software logic is unified under one roof, making Node-RED a viable alternative to established BMS technologies.

  • HIU interface
  • Modbus interface to plantroom
  • Network DP & Temperature sensors
  • Cloud services on our Heatweb
  • Thingstream API, for logic routing of USSD messages over mobile network
  • Multitech LoraWAN wireless gateways, for logic routing network traffic

These virtual 'wiring diagrams' are known as a flows, with a number of flows combining to form the overall package. The flow file is saved in a json format that can be imported into other systems.

There are a huge array of existing nodes to be dropped into flows, with more web based service providers, OEMs, and collaborative groups, launching their own. The array and flexibility of these nodes puts existing BMS systems to shame.

Nodes

The function node allows user defined software code, written in JavaScript, to create more complex functionality.

Node-HIU GSM Switch

Tempgsm1
  • Sends data from anywhere there is any mobile signal on any network
  • Just requires power, via a standard plug socket or USB power source
  • From one to ten daisy-chained temperature sensors, 2 as standard.
  • Optional FTDI cable to connect to HIUs
  • Optional DP/Temp sensor

Node-HIU Touchscreen Panel

Plantroom Control Panel - Cover Off

The heart of the system.

Plantroom Control Panel - Cover On
  • Touch screen display
  • GSM modem
  • 2 year SIM contract with 5GB/m and fixed public IP address
  • Power supplies for controls
  • Node-RED controllers
  • MQTT server
  • VPN server
  • Valid HTTPS certificate
  • Reverse proxy
  • Pre-commissioned before arriving on site
  • Optional Modbus I/O module(s) for
    • analogue (0-20mA / 0-10v) inputs and outputs
    • digital inputs and outputs
    • SSR relay outputs
  • Optional M-Bus module(s) for meter reading
  • All network variables, inc. HIU data, plantroom data, meter data, and operational data presented over standardised MQTT data structure
  • Alarm detection and reporting via email, SMS, automated voice call or postal letter

See Also

Converted from the Heatweb wiki article “Node-HIU Switch”, last edited 2020-11-23. Under review for the new site.

Talk to an engineer

Tell us about your network and we will come back with a practical next step, usually within one working day.