Examples

Modbus Gateway Installation

A NODA Modbus Gateway can connect to any Modbus TCP or RTU capable energy controller. The NODA Modbus Gateway then reads and writes values to the energy controller using the Modbus protocol.

Installation complexity varies depending on the installation scenario;

• Freely programmable controller: Configurable Modbus layout and programmable logic.
• Application-specific controller: Static Modbus layout with only parameterise logic.

A freely programmable controller has to be configured to expose the required values. An application-specific controller seldom has the option to change the Modbus layout. Nor is it often possible to handle a failsafe mode directly in the controller using software logic.

An application-specific controller may contain this feature if the specific feature was part of the requirements when the controller was designed.

To solve this problem, NODA has developed the NODA Modbus Gateway Addon. A device that sits between the energy controller and the NODA Modbus Gateway and provides the missing logic required to handle situations when a connection to the internet fails for several hours or days.

graph TD
    subgraph clusterAWSIoT["AWS IoT"]
        IoT_Server["IoT Server"]
    end

    subgraph clusterSiteA["Customer Site"]
        Modbus_Gateway["Modbus Gateway"]
        Modbus_Gateway_Addon["Modbus Gateway Addon\n(optional)"]
        Energy_Controller["Energy Controller"]
    end

    Modbus_Gateway -->| | Modbus_Gateway_Addon
    Modbus_Gateway_Addon -->| | Energy_Controller
    Modbus_Gateway -->|"🔒"| IoT_Server

The NODA Modbus Gateway connect to the secure endpoint on AWS IoT. Data is then forwarded to the NODA system and handled by various processes. The system crunches the numbers and sends control signals back the controller via AWS IoT and the NODA Modbus Gateway.

Finally, a customer connects to the EnergyView (or My Pages) system to browse the data at their heart's content.

graph LR
    subgraph clusterNodaPrivate["Noda Private"]
        DBMS[("DBMS")]
        Mosquitto["Mosquitto"]
    end

    subgraph clusterNodaPublic["Noda Public"]
        EnergyView["EnergyView"]
        Mosquitto["Mosquitto"]
    end

    subgraph clusterAWSIoT["AWS IoT"]
        IoT_Server["IoT Server"]
    end

    subgraph clusterSiteA["Customer Site"]
        Modbus_Gateway["Modbus Gateway"]
    end

    Mosquitto -->| | DBMS
    EnergyView -->| | DBMS
    IoT_Server -->|"🔒"| Mosquitto
    Modbus_Gateway -->|"🔒"| IoT_Server

    Customer["💻 Customer"]
    Customer -->|"🔒"| EnergyView

Indoor Sensors Installation

There are several ways to get indoor sensor data into the NODA system.

The most common way is for equipment in the field to send data to NODA. This can be either via Wireless M-Bus gateways or via MQTT or HTTP from a gateway connected to a LoRa network.

These devices are often provisioned once and usually work for several years without intervention.

graph LR
    subgraph clusterNodaPrivate["Noda Private"]
        DBMS[("DBMS")]
    end

    subgraph clusterNodaPublic["Noda Public"]
        EnergyView["EnergyView"] -->| | DBMS
        W_MBus["W-MBus"] -->| | DBMS
    end

    subgraph clusterSite["Customer Site"]
        Indoor_Sensors["🌡️ Indoor Sensors"]
        Indoor_Sensors -->|"🔒"| W_MBus
    end

    Customer["💻 Customer"]
    Customer -->|"🔒"| EnergyView

Typical logging intervals are between 5 and 15 minutes, depending on expected lifespan, technology and so forth. Once the data has landed in the NODA system it can be viewed by customers using either EnergyView or My Pages.

3rd Party Integration Installation

While not very common, NODA allows for customer specific intergrations. This is often solved by using the NODA EnergyView API or the NODA Self-host API.

graph LR
    subgraph clusterNodaPrivate["Noda Private"]
        DBMS[("DBMS")]
    end

    subgraph clusterNodaPublic["Noda Public"]
        EnergyView["EnergyView"] -->| | DBMS
    end

    subgraph clusterSiteC["Customer Site"]
        Third_Party_Solution["3rd party solution"] -->|"🔒"| EnergyView
    end

    Customer["💻 Customer"]
    Customer -->|"🔒"| EnergyView

IEC Installation

NOTICE: This solution reaches end of life (EOL) on the 31st of December 2022.

The NODA IEC is a solution built in-house by NODA. It sits between an outdoor sensor (RTD) and the energy controller. The IEC measures the resistance of the outdoor sensors, converts it to a temperature, applies an offset (or not) and converts the new temperature back to a resistance value for the controller.

This solution has both benefits and drawbacks. Using this method, one can not control specific circuits in a building unless there is one controller for each circuit. In addition, everything affected by the outdoor temperature will be affected by an offset.

However, it's a simple concept and works well if used in the right circumstances.

graph LR
    subgraph clusterNodaPrivate["Noda Private"]
        DBMS[("DBMS")]
    end

    subgraph clusterNodaPublic["Noda Public"]
        EnergyView["EnergyView"]
        IEC_Sync["IEC Sync"]
    end

    subgraph clusterSiteA["Customer Site"]
        IEC["IEC"]
    end

    EnergyView -->| | DBMS
    IEC_Sync -->| | DBMS
    IEC -->|"🔒"| IEC_Sync

    Customer["💻 Customer"]
    Customer -->|"🔒"| EnergyView

Since the IEC cannot query an energy controller for measured values, these are collected by installing surface-mounted 1-wire temperature sensors on the essential circuits.