# System Overview for Installers
This article is an architecture guide from a mounting and commissioning perspective. Terminology (bus, HUB, Logic Blocks, Volang) is covered in Core concepts and terminology. Here we focus on physical structure, field limits, and what matters in day-to-day installer work.
# Physical layer: panel and bus
A Voldeno installation is built from DIN-rail modules in a panel or cabinet. All such modules share the Voldeno Bus: common 24 V DC, ground, and CAN-FD with Voldeno’s message specification.
In the field you must use a linear daisy-chain topology — no loops and no branches off the main line. Power and CAN follow the module connector Input / Output convention. Termination is on-module (switch): enable it on the first and last module of the chain only.
Hard numbers you need for cable design (e.g. maximum modules per bus, bus length, stubs, termination, power per row) live in Bus topology & wiring. We do not duplicate those tables here — treat that document as mandatory reading for installation.
Power budgeting and 24 V distribution: Power supply. HUB wiring (Ethernet, bus, power): HUB wiring.
# HUB vs the rest of the system
The HUB is a gateway: Ethernet, local persistence, paths for remote service of the installation. For availability, the product story is important: losing the HUB does not automatically mean all bus-based automation stops — modules and distributed logic can keep cooperating over the Voldeno Bus, while the HUB is the integration point to IP networks and configuration tools, not a classic “single brain” whose failure always freezes the whole home.
Conceptual detail: Concepts.
# Reliability and responsiveness
The system targets high availability and low-latency control: direct CAN-FD bus traffic (a protocol with a strong track record in automation and industry), fault-tolerant architecture, and no mandatory cloud — logic runs locally even without internet.
This page is not an SLA spec; marketing figures (e.g. response time) are indicative only. Authoritative limits for wiring and topology remain the bus documentation.
# Modularity and expansion
You can start with fewer modules and add more without replacing the existing “core” of the system — as long as new bus segments respect length and node limits. Adding new standards or features should follow an expansion model rather than forcing a full panel swap each product generation (see also the product Features page).
# Hardware quality and typical protections
Modules are intended for long-term panel operation and protection against common wiring mistakes (e.g. reverse polarity, over-current, over-voltage, temperature monitoring, power measurement — as communicated in product materials). Always confirm electrical detail from the module datasheet / manual and wiring docs.
# Installer workflow (short)
- Install — DIN layout, bus per topology, power per power supply.
- Configure — Voldeno Studio: devices, Logic Blocks, optional Volang, simulation before deploy.
- Handover — functional test, bus diagnostics if needed (Bus communication), client app and user guidance.
# Software, firmware, and integrations
- Firmware for modules and HUB is typically applied from Studio (see FAQ).
- New logic (blocks) can often be deployed without a firmware update for every logic change — unlike many “central unit + flash for every scenario” systems.
- Integrations (HTTP, Modbus, TCP/UDP, etc.) are project-specific — see FAQ — integrations & connectivity for orientation.
# What to read next
| Need | Document |
|---|---|
| Definitions: Bus, HUB, blocks, Volang, Studio | Concepts |
| Numbers, connectors, termination, install steps | Bus topology |
| 24 V, panel rows, voltage drop | Power supply |
| HUB terminals | HUB wiring |
| Bus problems | Bus communication |
| General Q&A | FAQ |
Marketing material for partners (For professionals) adds business benefits and full capability lists — here the emphasis is architecture and technical documentation.