Larnitech CAN Bus Commissioning and Diagnostics in the Panel
A systematic commissioning sequence for Larnitech CAN bus installations — verify the wiring before power-up, confirm every module in the app, document the module map, and prove scenarios end-to-end before sign-off.
Commissioning sequence
Verify wiring and termination
Check CAN High/CAN Low polarity, confirm termination resistors are present at both physical ends of the bus (the Main Gateway's two CAN connections), and that WAGO connectors are properly seated — before powering up.
Configure via the Larnitech app
Power up, open the app (Android, iOS, Linux or Windows), and confirm each module responds and appears in the device list.
Document the module map
Build a channel-assignment sheet and an app configuration snapshot for handover, with the same rigor as any DIN-rail automation project.
Test scenarios end-to-end
Run lighting, climate, and other configured scenarios in full before sign-off, not just individual module checks.
What disciplined commissioning gets you
CAN connections on the Main Gateway
Larnitech's linear bus topology terminates at both ends through the Main Gateway — the physical layout every commissioning check starts from.
Wiring verified before power-up
CAN High/CAN Low polarity, termination at both bus ends, and WAGO connector seating are checked first — not diagnosed after the fact.
App-confirmed module presence
Every module is checked against the Larnitech app's device list (Android, iOS, Linux, Windows) before it's considered commissioned.
Handover-ready documentation
Module map and channel-assignment sheet delivered alongside the app configuration snapshot — not left to memory.
Structured fault isolation
When a module doesn't respond: app status first, then physical continuity and termination, then segment isolation — not a blind full-system restart.
Bus wiring separated from power
The CAN data pair is routed clear of 230V cabling in the panel and cable runs, with shielded twisted pair where the environment is noisy.
Commissioning support package
Panel-side commissioning and diagnostics support for Larnitech CAN bus installations, delivered alongside your panel build.
- Wiring and termination verification
- App-based module configuration check
- Module map and channel-assignment sheet
- App configuration snapshot
- End-to-end scenario testing
Frequently asked questions
A module doesn't appear in the Larnitech app's device list — what do I check first?
Start with the app's connection and status indicators, then verify physical bus continuity and that termination resistors are present at both ends, before assuming the module itself has failed.
Do I need an ETS-style design tool to address Larnitech modules?
No — Larnitech modules are configured directly through the Larnitech app on Android, iOS, Linux or Windows, without a separate ETS-type addressing step like KNX uses.
Is Larnitech's CAN bus the same as KNX or CANopen?
No to both. Larnitech runs its own proprietary protocol over the CAN physical layer — it is not KNX (the open ISO/IEC 14543-3 standard) and not CANopen, and Larnitech modules aren't cross-certified with either ecosystem.
One segment of the bus is unresponsive but the rest works — what's the likely cause?
Isolate to that segment rather than restarting the whole system: check termination and continuity on that run first, since a single break or missing terminator typically affects only the modules downstream of it.
What should go into the handover documentation for a Larnitech panel?
A module map, a channel-assignment sheet, and an app configuration snapshot — the same documentation rigor expected for any DIN-rail automation commissioning.
Building or diagnosing a Larnitech panel?
Our engineers support panel builders and integrators with Larnitech CAN bus wiring review, commissioning, and diagnostics — talk to us before you're on site.