SEG Main applications
Tip
This page contains application specific configuration for the various SEG applications and is intended for advanced users.
| Application | Supported | Note |
|---|---|---|
| SEM (secure-edge-module) | Yes | Connection to SmartCloud. |
| WDC (Web Data Central) | Yes | Require license file for additional data points. |
| Yanzi Gateway | Yes | Support for Yanzi infrastructure and sensors. |
| Cirrus tunnel | Yes | Some features may require activation. |
| Data Points | up to 12000pcs | Requires license. |
| Analysis Tool | Yes | Requires license. |
| Ecopilot | Yes | Requires license. |
| Ecopilot, PowerPilot | Yes | Requires license. |
| Ecopilot, PricePilot | No | Currently not supported. |
| Ecopilot, Weather forecast | Yes | Requires license. |
| Ecopilot, Weather forecast widget | see Note | Foreca Box from 3rd party supplier, new forecast locations will not be added. |
| Ecopilot, Dynamical floor plans | Yes | Require production tool from Nordomatic. |
| Ecopilot, Heatmaps | Yes | Addon to the dynamical floor plans. Colors the surrounding area of a sensor with regards to the Ecopilot zone settings |
| Ecopilot, WDC Controllers | Yes | Ability to automatically create room controllers that uses the settings from the corresponding Ecopilot zone. |
| 3rd party devices | 400pcs | Possibility to connect 400 devices via the supported built-in drivers. |
| Custom Java program | Yes | plc.jar and eon.jar are supported. |
| HMI | Yes | HTTP web server. Can be accessed via SmartCloud and locally on LAN interface at port 80. |
| Backup file | Yes | Can be used to restore SEG (Yanzi data is not included). |
| Kiosk TV (Kabona TV) | No | Last order date 2016/2017. |
| Mybis WDC | No | Last order date 2019-01-30, replaced with SmartCloud. |
| Master WDC | No | Last order date 2019-01-30, replaced with SmartCloud. |
| WAN to LAN Port forward | No | Replaced with Cirrus tunnel. |
Network
| Network | Supported | Note |
|---|---|---|
| LAN port | Yes | IPv4/IPv6 |
| WAN port | Yes | IPv4/IPv6 |
| DHCP server on LAN | Yes | (Supports IPv4, IPv6 and multicast on LAN port)??? |
| DNS proxy on LAN | Yes |
Ecopilot
Requirements:
- SEG connected to Nordomatic SmartCloud.
- Ecopilot license.
- At least one referens sensor for room temperature.
- An outside air temperature sensor.
| Ecopilot | Quantity | Note |
|---|---|---|
| Weather forecast | 1 | One weather forecast in one Ecopilot. |
| Outside air temperature | 1 | One outside air sensor in one Ecopilot. |
| Zones | 50 | Max number of Ecopilot zones. |
| Temperature sensors | 30 | Max number of sensors in one zone. |
| CO₂ sensors | 30 | Max number of sensors in one zone. |
| HVAC systems | 50 | Max number of systems in one Ecopilot |
| Heating systems/zone | 5 | Max number of heating systems in one zone. |
| Cooling system/zone | 5 | Max number of cooling systems in one zone. |
| Ventilation system/zone | 3 | Max number of ventilation systems in one zone. |
An Ecopilot system is a system affecting the indoor climate. Estimated savings are based on all central systems for heating, cooling and ventilation being included in Ecopilot. It is recommended to have 3 or more temperature sensors per zone. It is recommended to have approximately one sensor/100m². A reference room sensor can only be active/selected in one zone.
PowerPilot
PowerPilot is designed to level and limit the power for water-based heating systems during the day.
The primary target is not to reduce the total energy usage, but to level the power outtake by borrowing and returning energy from a slow system like a water-based radiator system.
Normally this strategy has a very small impact on the the indoor climate, but depending on how the peak power limit is set, it can have.
For a cooling system the peak power will probably occure in the afternoon just before ventilation units are turned off in a normal office building.
If PowerPilot this is used for cooling systems, it would probably only act as a limiter as the chilled water usually is distributed via ventilation.
Requirements:
- Configured Ecopilot.
- Main heat energy meter with:
- power reading in [kW].
- update time < 5min.
- One or more water based radiator heating systems with flow temperature control [°C].
Target group:
- Building heated by district heating.
- Building with larger temporary loads during the day.
(Like Multi residential buildings were the domestic hot water is a momentary significant load). - Customer who benefits from reducing the power peaks.
Heatmaps
Heatmaps is an addon to the dynamical floor plans and require Ecopilot.
The feature uses the Ecopilot zone settings for temperature and CO2 level to color the surrounding area of each sensor.
Surrounding area will fade between blue, none and red depending on the actual value being close or outside the low or high limit.
Relative feature will not be colored as humidity sensors can't be selected in Ecopilot.
Heatmaps function require that point names are described on the following form:
- b[building number]fl[floor number]z[zone number].room[medium][room number].cm
- b[building number]fl[floor number]z[zone number].roomtempcont[room number].ms
- b[building number]fl[floor number]z[zone number].roomtempcont[room number].cs
Building and zone number may be excluded if not applicable.
Supported [medium] types:
- temp for temperature.
- carbon for CO2-level.
- hum for relative humidity.
Supported units:
- [°C] for temperature.
- [ppm] for CO2-level.
- [%rH] or [%] for relative humidity.
WDC Room Controllers
This feature is an ability to automatically create room controllers using the settings from the corresponding Ecopilot zone. Outputs for heating, cooling and air volume are automatically paired with a room sensor selected in Ecopilot by their point names. The controller is energy efficiant and harmonises well with the indoor climate.
- Sensor and output are pared by point name depending on building, zone, floor and room number.
- Temperature and CO2 level sensors are supported.
- The controller will use the settings in the cooresponding Ecopilot zone.
- A temperature setpoint offset is generated for personal adjustment of +/- 1°C.
- One temperature sensor can only be paired with one heating output signal.
- One temperature sensor can only be paired with one cooling output signal.
- An average room temperature of multiple sensors can be automatically generated.
- Cooling and air volume will follow each other based on temperature demand.
- For damper outputs a minimum and maximum damper position is automatically generated for adjustment.
- Easy to maintain as it has no control loop settings.
- Wireless sensors can be used.
Room sensors
The function supports temperature and CO2 level sensors named as below.
| Point name | Description |
|---|---|
| .roomtempcont[room number].ms | Room temperature |
| .roomtempcont[room number].cs | Room CO2 level |
Multiple room sensors can be automatically averaged to control the same outputs. First sensor is named .ms1 second .ms2 and so on. A new average sensor .ms will be generated and used for the control loop.
Example:
sensor 1 = fl01.roomtempcont101.ms1
sensor 2 = fl01.roomtempcont101.ms2
sensor 3 = fl01.roomtempcont101.ms3
A new sensor for the average room temperature will be automatically generated as fl01.roomtempcont101.ms.
Possible output types
| Output | Description |
|---|---|
.out |
Standard analog 0-100% output. |
.out |
Standard analog 0-100% output. |
.pwm |
Pulse width modulated digital output. Cycle time is 15min and shortest activation time is 1min. This gives 1/15 = 6,7% as smallest output |
Cooling signals
| Point name | Description |
|---|---|
| .aircooler[room number]. | Cooling sequence active when ventilation is active. Chilled beams, cooling coils, Fan Coils |
| .cooler[room number]. | Cooling sequence active when cooling systems are |
| .fancooler[room number]. | Stand alone fan cooler |
Heating signals
| Point name | Description |
|---|---|
| .airheater[room number]. | Heating sequence active when ventilation is active. Heating coils, Fan Coils |
| .heater[room number]. | Heating sequence active heating systems are |
| .fanheater[room number]. | Stand alone fan heater |
| .radheater[room number]. | Radiator valve |
| .floorheater[room number]. | Under floor heating |
Air quality signals
| Point name | Description |
|---|---|
| .vavdamper[room number]. | Supply/Extract air damper. This signal assumes an air flow control in the device |
| .supdamper[room number]. | position-controlled supply air damper. Min and max damper position will be generated for adjustment |
| .exhdamper[room number]. | position-controlled extract air damper. Min and max damper position will be generated for adjustment |
Cold air down draught protection
The generated controllers has a built-in cold air draught protection for the following outputs.
- heater
- fanheater
- radheater
- floorheater
The function kicks in when the heating demand for the cooresponding Ecopilot zone is above 15% and the room temperature is below the zones comfort temperature with hysteresis. When the protection is active the output is controlled partly depending on heating demnad and partly on room temperature. The controller reverts back to normal control, room temperature, when the heating demand decrease below 10% or the room temperature decrease above the zones comfort temperature with hysteres.
WDC
| Feature | Supported | Note |
|---|---|---|
| Alarm email server | Yes | Via jsonrpc@event.kabona.com. |
| Alarm email receivers | Yes | Set by priority for each email receiver. |
| Custom dynamical pictures | Yes | Supports files generated by kad-4.10.0. |
| Custom functional description | Yes | Supports files generated by kad-4.10.0. |
| General building information | Yes | Supports html files based on the doc_totsys template. |
| Custom documentation | Deprecated | Cabinet schematics, plumbing's, ventilation schematics etc. |
| Custom Network schematics | Yes | Uploaded as network_[XX].gif |
| Custom system menu | Yes | Reorder, rename, hide, group, change system type. |
| Store/restore setting values | Yes | Possibility to store up to 10 sets of values that are considered setting value by point name attribute. |
| Time schedule | Yes | Generated for Boolean points with the format xxx.xxx.tc |
| Generation of derivative for meters | Yes | Generated for meters measured in [kWh], [m³]. |
| Runtime, activation | Yes | Possibility to activate runtime measurement for digital point. |
| Runtime, service alarm | Yes | Alarm limit and alarm is generated for runtime measurement. |
Analysis tool
| Feature | Supported | Note |
|---|---|---|
| Energy signature | Yes | Require energy meter in [kW], or [kWh] and outside air temperature in [°C]. |
| Meter report | Yes | 10 years with monthly usage for meters measured in [kW], [kWh], [MW], [m³], [m³/h]. |
| Outside air temperature report | Yes | 10 years with monthly average outside air temperature [°C]. |
| Graph tool, multiplot | Yes | Up to 30 measuring series to a plot. |
| Graph tool, custom plot | Yes | Freely add up to 30 measuring series to a plot. |
| Graph tool, store a plot | Yes | Store a customized plot that can be accessed by other users. |
| Graph tool, custom standard plot | Yes | Customize the standard plot for all users. |
Local data storage
| Data storage | Resolution |
|---|---|
| Last 4h | 30s |
| Last 8 days | 5min |
| Last 4 weeks | Hourly sliding average and hourly min/max value |
| Last 2 years | Daily sliding average and daily min/max value |
Drivers and Servers
| Driver | LAN port | WAN port | Note |
|---|---|---|---|
| Modbus TCP/IP | Yes | Yes | |
| M-bus (Meter-bus) TCP/IP | Yes | Yes | Based on automatic discovery of the measurement series. Does not support all M-bus meters |
| BACnet UDP/IP | Yes | No | Not built in. Require custom BACnet Java program. |
| JSON-RPC TCP/IP | Yes | Yes | |
| PSR-COM | No | No | Not supported in SEG. |
| Server | LAN port | WAN port | Note |
|---|---|---|---|
| Modbus TCP/IP | No | No | |
| M-bus TCP/IP | No | No | |
| BACnet UDP/IP | No | No | |
| JSON-RPC TCP/IP | Yes | No | Only for data exchange with other SEG´s. |