4 Local Web Interface

4.1 Overview

The Micro Web interface (Rune) is accessed on site via a laptop or a smartphone using the LAN. The interface provides the user with an overview of the status of the Micro Modular system and active alarms. It also offers possibilities to configure the system, update controller softwares and download backup data.

Rune runs on port 3000 and requires authentication to access all pages except the login screen.

From the front page, which displays an overview of the most important system information, tabs with more detailed information about various system parts are accessed. An example of the view on the Rune front page is shown in Section 4.3. Click the labels on the menu bar to access the detailed information sections and to configure the system.

4.2 Authentication

4.2.1 User Levels

Rune supports two user levels, 'Operator' and 'Admin'. Each user requires a unique user name and a password. Default passwords are provided by Clear Blue Technologies. Passwords may only be changed by an 'Admin' user.

4.2.2 Password Change

Available from the user profile dropdown. Requirements:

Minimum 8 characters

4.3 Dashboard

The dashboard displays real-time system data, updated every 1 second.

System

Battery

Solar & Load

External Solar Chargers

Gensets & Grid

Tenant Power

Power readings for up to 10 individually measured tenants (Tenant 1–10), displayed in Watts.

4.4 Battery Information

The Battery page provides detailed battery monitoring and control.

Status Fields

Battery Controls

BMU Data (Battery Management Units)

For each installed BMU (up to 16):

4.5 Genset Information

The system supports up to two gensets. Each has a dedicated page (Genset 1, Genset 2) with identical layouts.

Status Fields

Three-Phase Power (L1, L2, L3)

Fuel Monitoring

Genset Controls

4.6 Solar Information

Total Solar

Green Power Influx (expandable section)

Per-Array Data (up to 3 solar arrays)

Each array also has Show Errors and Show Info buttons for detailed diagnostics.

4.7 Grid Information

Three-Phase Power (L1, L2, L3)

4.8 Active Alerts

Active system alerts are displayed in a notification dropdown accessible from the bell icon in the top navigation bar. Each alert shows:

• Severity indicator: F (Fatal/danger), E (Error/warning), W (Warning/info)
• Event name
• Count (if multiple instances of the same event)
• Date and time of activation

4.9 CAN Diagnostics

The CAN Diagnostics page provides real-time monitoring of converter units and their CAN bus nodes.

Converter Unit Cards

Each registered converter unit is displayed as a card showing:

• Unit ID and serial number
• Configuration type badge (e.g., R3_S3, R2_S1 — indicating number of ACDC and SOLAR nodes)
• Error count badge (if errors exist)
• 3×2 grid of node status indicators

Node Status

Each node (ACDC 1–3, SOLAR 1–6) shows:

• Status color: Green (OK), Red with animation (Error/Timeout), Gray (empty slot)
• Clicking a node opens a detail modal

Node Detail Modal

Actions:

• Ping — Send a CAN ping to the node
• Reset — Reset the node via CAN

Node status auto-refreshes every 5 seconds.

4.10 Converter Units

The Converter Units page displays all detected converter units with their registration status.

A maximum of 3 units can be registered simultaneously. When the system is in Registration Mode (system_mode = 6), a warning banner is displayed.

Warning: Before unregistering a unit, switch off all AC/Solar power input to the system. The unit must not be actively converting at the time of unregistering.

4.11 Settings

Settings are accessed from the sidebar. Each settings page displays current values and allows entering new values. Click Confirm to apply changes.

When a setting is changed via the web UI, the new value is written to the site_data SQLite database and the PD Manager process is notified via IPC. PD Manager then propagates the change to the control algorithm via shared memory.

4.11.0 Setting User Interface

4.11.0.1 Confirm Configuration Changes

Confirm button:
Confirms the setting changes and starts the process of writing the changes to the RMC, unless any of the settings has failed the pre range-check indicated by a pulsing red number/text on the right-hand side of the arrow.

Example of a failed pre range-check is shown here #id-4.11.0.1-confirm-configuration-changes for the "Voltage Cycle Start" setting.

If any of the setting changes fails the pre range-check the settings wont be removed from this list but the list will be hidden and the user will be shown an error message. Example: #id-4.11.0.2-configuration-change-error

Cancel button:
Will close the Confirm Configuration Changes window. Setting in the list will be saved and the window can simply be shown again by pressing the confirm button on the bottom left hand side of the page.

Clear Button:
Will remove all settings from the list and close the confirm configurations changes window.

Per setting cross-button:
Will remove the setting on the corresponding row from the list and prevent it from being changed.

4.11.0.2 Configuration Change Error

4.11.0.3 Graph Style Setting

Example of a graph-style setting with movable points.

Functionality:

• Scroll up: Zoom in
• Scroll down: Zoom out
• Scroll on X axis: Vertical zoom in/out
• Scroll on Y axis: Horizontal zoom in/out
• Drag on graph area: Move graph area
• Double click: Resize graph area to min/max value of X and Y

Fit Points Button: Fit all points in the graph area

Fit Min Max: Resize graph area to min/max value of X and Y

Arrow Button (top-right corner): Extends window to show points in a table format, see #id-4.11.0.4-graph-style-setting-extended-points

4.11.0.4 Graph Style Setting Extended Points

Extra functionality extended points:

• When dragging any point: Highlights point in table
• When editing value of a point in table section: Highlights point in graph area

4.11.1 Setting Relationships and Dependencies

Understanding how settings interact is critical for correct system configuration. The diagram below shows the major dependency chains:

├─► AC Source Selection (Source A / Source B)
│     ├─► Determines which Status pages appear (Grid, Genset 1, Genset 2)
│     ├─► Controls which Genset Settings sections are visible
│     ├─► Sets rectifier current limits and power source arbitration
│     └─► Affects Digital Output assignment (Source B = Genset2 → DO2 = 3)
│
├─► Battery Type Selection
│     ├─► Determines available Charge Strategies (Lead-Acid: 3, Li-ion: 2)
│     ├─► Loads strategy-specific parameters (voltage, SoC, current limits)
│     ├─► Sets default temperature alarm thresholds from battery template
│     └─► Controls which charge modes are available (Balancing for Li-ion, Equalize for Lead-Acid)
│
├─► Charge Strategy → Parameter Visibility
│     ├─ Voltage Cycling → Shows cycle start/stop voltages and timing
│     ├─ Static SoC → Shows SoC window start/stop percentages
│     └─ Partial SoC → Shows partial SoC parameters (Lead-Acid only)
│
├─► Cabinet Cooling Mode → Which temperature thresholds are editable
│     ├─ Delta Ambient → Delta Fan On/Off fields
│     └─ Battery Temp Levels → Absolute temperature Fan On/Off fields
│
├─► Modbus Server Enable → Disables BMU and Genset Modbus communication
│
└─► Fuel Sensor Type → Which tank dimension and calibration fields appear
      ├─ Height sensor → Tank shape + dimensions
      ├─ Litre sensor → Max litre capacity
      └─ Lookup sensor → 10-point voltage-to-litre calibration table

Key interaction rules:

• AC Source A and B are mutually exclusive for certain combinations (e.g., both cannot be the same genset).
• Changing the battery type reloads all charge parameters from the selected battery template database.
• Enabling the Modbus Server disables direct BMU and genset Modbus RTU communication.
• Night Silence, Hybrid Shifting, and Peak Load Shifting each define time windows that affect genset and grid behavior — overlapping windows should be configured carefully.

4.11.2 General Settings

These identify the site and configure the system clock. The Micro Name and ID are transmitted to the Illumience cloud platform for remote identification. Changing the timezone triggers a systemctl restart sysconfig to apply the new zone system-wide.

4.11.3 Rectifier (AC Source) Settings

The rectifier converts AC power (from gensets or grid) into DC power for battery charging. Source A and Source B define the two AC input paths. The system uses source arbitration to select the active input based on availability and priority, with automatic fallback if the primary source becomes unavailable.

The PI compensator implements closed-loop current regulation for battery charging. Increasing P Gain improves response speed but may cause oscillation; increasing I Gain eliminates steady-state error but may cause overshoot. Max/Min Range limits the compensator output to prevent damage.

The CPU Temperature Derate curve progressively reduces rectifier output power as the converter CPU heats up, preventing thermal shutdown. When temperature exceeds configured thresholds, alarms are raised and power output is reduced according to the derate curve.

4.11.4 Battery Settings

Battery settings is a large configuration page covering battery profiles, charge strategies, and detailed electrical parameters.

Battery Profile: Select from a dropdown of predefined battery configurations (30+ types including AR400, AR600, LG Chem, Vision, Narada, Polarium, etc.). Selecting a profile loads all charge parameters, alarm thresholds, and strategy options from a dedicated battery template database.

Battery Chemistry: Lithium-Ion or Lead-Acid. This fundamentally changes which parameters and charge modes are available.

Charge Strategy: Determines how the control algorithm manages battery charge/discharge cycles:

• Voltage Cycling (Lead-Acid & Li-ion): The most traditional approach. Charges the battery by monitoring voltage levels through absorption and float phases. Uses temperature-compensated voltage setpoints. The cycle starts when battery voltage drops below Start Voltage and stops when it reaches Stop Voltage for the configured Stop Time at or below Stop Current.
• Static SoC (Lead-Acid & Li-ion): Maintains battery State of Charge within a fixed window. Charging starts when SoC drops below Window Start % and stops when SoC reaches Window Stop %. Keeps the battery at a constant operational range, reducing deep discharge stress. For Li-ion, an additional "Balancing SoC" option is available that incorporates cell balancing.
• Partial SoC (Lead-Acid only): Cycles the battery between partial charge levels rather than full cycles. Reduces stress from full charge/discharge, extending battery life. Better for long-term health at the cost of reduced usable capacity per cycle.

Key parameter groups (fields vary by chemistry and charge strategy):

Charge Modes (automatic and manual):

Save and Load configuration buttons allow exporting/importing battery profiles.

4.11.5 Solar Settings (Green Power Influx)

Green Power Influx (GPI) is a mode that prioritizes renewable energy sources (solar) for battery charging. When enabled and all trigger conditions are met, the system preferentially uses solar power and may inhibit genset starts. This reduces fuel consumption during periods of high solar availability.

GPI uses a multi-condition trigger — all configured conditions must be satisfied simultaneously for the mode to activate:

4.11.6 Grid Settings

Fuse: Sets the maximum current the grid rectifier is allowed to draw per phase. This protects the site's grid connection and upstream breakers.

Per-Phase Settings (Phase A, B, C):

These are hysteresis thresholds that determine when the grid is considered healthy or unhealthy on each phase. The system monitors all three phases independently. If any phase goes out of range, the grid source may be inhibited.

• Low/High Voltage On/Off: The "On" threshold triggers a state change (e.g., grid inhibited) when voltage crosses that level. The "Off" threshold clears the state. The gap between On and Off provides hysteresis to prevent rapid switching when voltage fluctuates near a threshold.
• Low/High Frequency On/Off: Same hysteresis logic for frequency. Frequency deviation from 50/60 Hz indicates grid instability or generator issues.

Peak Load Shifting:

During peak demand periods (defined by the time window), the system raises the grid float voltage setpoint. This reduces load drawn from the grid, lowering peak demand charges from the utility. The battery absorbs more of the load during peak hours.

4.11.7 Genset Settings

The genset (generator set) is an AC power source that charges the battery when solar/grid is insufficient. The control algorithm manages genset startup sequences, power ramping, and shutdown with configurable timing to protect the engine and prevent fuel waste. Genset settings are only visible when AC Source A or B is configured to a genset.

Per-Genset (Genset 1, Genset 2):

The startup/shutdown sequence follows this order: Start → Warmup → Ramp-up → Run → Ramp-down → Cooldown → Off-delay → Stopped. Each phase has a configurable duration.

Hybrid Shifting:

Hybrid shifting reduces fuel consumption during periods when renewable sources (solar) are expected to be available. During the configured time window, the genset stop voltage setpoint is raised, causing the genset to stop earlier and allow the battery to float on solar power. Typically configured for daylight hours.

4.11.8 Load Control (Load Disconnect)

Load control protects the battery from deep discharge by disconnecting loads when battery voltage drops too low. The system has two load tiers: Low Priority loads are shed first (at higher voltage), and High Priority loads are shed only if the battery continues to drop further. Both voltage AND current conditions must be met for reconnection — this prevents reconnecting when the system cannot support additional load.

Low Priority Load:

High Priority Load:

4.11.9 Cabinet Cooling

Controls the battery cabinet ventilation fan. The mode selection determines which temperature thresholds are used. If the temperature sensor fails, the system enters a Fallback mode and forces the fan on as a safety measure.

Fields are conditionally visible based on the selected cooling mode.

4.11.10 Input/Output Configuration

Maps physical digital inputs on the hardware to system functions. Each input can be assigned to monitor a specific external signal. The system reads the input state and generates events/alarms accordingly.

Digital Inputs (DI 1–9):

Each input has:

Digital Input Functions:

4.11.11 Network Configuration

Configures the eth0 network interface. Changes trigger systemctl start set-ip-address to apply. Since the web interface is accessed over this network, incorrect settings will lock you out.

Warning: Changing network settings may cause loss of connection. Ensure you have physical access to the device.

4.11.12 Alarm Settings

All alarms use temporal debouncing (configurable delays or internal counters) to prevent false triggers from transient conditions. The event handler records alarms in the event database with timestamps and severity levels.

Load Alarms:

Tenant Alarms (Tenant 1–10):

Each tenant (individually metered customer on the site) has its own load alarm. This prevents one tenant from overloading the system without being identified.

Voltage Alarms:

Temperature Alarms:

Fuel Alarms:

Genset Service Alarms:

4.11.13 Fuel Monitor Settings

Monitors fuel levels in genset tanks using analog sensors. The system converts raw sensor readings (voltage) into fuel volume using the configured sensor type, tank geometry, and calibration data. Each tank is independently configured and can be linked to a specific genset for per-genset fuel consumption tracking.

Configured per tank (Tank 1, Tank 2). Each tank has:

Sensor Types Explained:

4.11.14 Night Silence

Night Silence prevents genset startups during sleeping hours to reduce noise pollution at the site. The system runs on battery power alone during the silent period. Safety thresholds ensure the battery doesn't discharge to a dangerous level — if voltage or SoC drops below the configured minimums, the genset is allowed to start and the silent period ends early.

The Safety Capacity setting is used to calculate whether the battery has enough energy to last through the remaining silent period. If estimated autonomous energy is insufficient, the genset starts despite the silence window.

4.11.15 Modbus Server

The Modbus Server exposes the RMC's data registers to external systems (SCADA, building management, remote monitoring) via the Modbus protocol. External systems can read operational data and write control commands.

Important: Enabling the Modbus Server disables direct BMU and genset Modbus RTU communication on the same serial bus, since the RMC switches from master to slave role. Changes trigger systemctl restart modbus-handler.

4.11.16 Modbus Master

The Modbus Master enables the RMC to communicate with external battery management systems (BMU) and genset controllers via Modbus RTU. The RMC acts as the bus master, polling slave devices for real-time data (SoC, voltage, current, temperature, fault codes) and sending control commands (start/stop genset, reset alarms).

Each battery type uses a different Modbus register mapping and communication protocol, so the correct battery protocol must be selected to match the installed hardware.

12 System

12.1 Reboot

Initiates a system reboot via systemctl. A confirmation dialog is shown before execution.

12.2 Shutdown

Initiates a system shutdown via systemctl. A confirmation dialog is shown before execution.

12.3 Software Update

The software update process has three stages:

1. Upload — Select a firmware image file (max 150 MB) and upload it to the server. A progress bar shows upload status.
2. Verify — The uploaded image is decrypted (AES-256-CBC) and verified. This can take several minutes.
3. Install — The verified image is installed via mender. The system will be unresponsive during the update and reboots automatically on completion.

If verification or installation fails, an error message is displayed with details.

13 Tests

13.1 Ping

Enter a hostname or IP address and click Ping to send 10 ICMP ping packets. Results are displayed on the page.

14 Delivery Mode / Commissioning

When the system is in delivery mode, all requests are redirected to the commissioning page. This page provides:

1. Minimal configuration — Set the Micro Site Name, Micro ID, and other essential settings required to complete commissioning.
2. Unit registration — Register converter units (same interface as the Converter Units page). When registration is complete, the refresh button redirects to the dashboard.