Software
Devices and command stations
Before LoDi-Aura can drive, switch and receive feedback, it has to know your devices. On this page you search for and add the LoDi-Rektor, LoDi-S88-Commander, LoDi-Shift-Commander and – if you have one – your existing command station, switch them online and decide what each device may be used for.
Where your devices are
In the “System” tab, the “My layout” section shows every device you have set up as a card. Below it come the “System areas”, including “Interfaces”. That's where you set up new devices.
Each card has three buttons: “Online” or “Offline” switches the device, the middle button takes you straight to its bus (“LoDi bus” for the LoDi-Rektor, “Modules” for the S88-Commander, “Buses” for the Shift-Commander, otherwise “Overview”), and “Open” shows the device page. “All interfaces” takes you to the “Interfaces & Devices” page.
| Item on the card | Meaning |
|---|---|
| Type and name | Device type (e.g. “LoDi-Shift-Commander LX”) and the name the device has in the project. |
| Status | “online”, “connecting …”, “unreachable”, “disabled” or “ready · offline”. Hover the mouse over the status to see an explanation. |
| Summary | For the LoDi-Rektor, the number of LoDi-Bus modules; for the S88-Commander, the number of feedback modules; for the Shift-Commander, “Switching Bus and Outputs”; otherwise the capabilities (Driving · Switching · Feedback · Booster). |
| Firmware · IP address | The firmware version last read and the device's network address. |
Searching for and adding devices
LoDi-Aura searches for devices once by itself when the program starts. After that it only searches when you tell it to – there is no continuous search. The search finds LoDi devices and the supported third-party command stations on the same network as the layout computer.
- Open the pageOpen “System” › “Interfaces”. The page is called “Interfaces & Devices”.
- SearchIn the “LoDi Network” card, click “Search for devices”. During the search it says “Scanning LoDi network …”. The result is split into “New Devices” and “Already set up”.
- AddClick “Apply” for each new device. It appears under “Configured Interfaces” and as a card under “My layout”.
- Switch onlineSwitch the device online with “Set online” on its card. “All online” above the list or the “Layout” switch in the header connects all devices at once.
- Turn on track powerSwitch on “Booster” in the header. Only then is there track power on the rails.
Checking a device with a known address
If the search doesn't find a device – because it is on a different network, for example – enter its address under “IP address” in the “LoDi Network” card and click “Check now”. The IP address is enough; you don't enter a port: LoDi-Aura works out by itself whether there's a LoDi device, a Märklin® CS3, an ESU ECoS, a Z21 or a Lenz interface behind it, and asks each on its own port. If it doesn't work, LoDi-Aura gives the reason for each possibility.
Z21-compatible command stations from YaMoRC are also entered by hand this way, because they don't respond to the search.
Device without firmware
If a device is in the bootloader, it has no firmware. The search still shows it, with the note “In the bootloader — no firmware”. Add it as usual and then install the firmware on the device page in the “Firmware” card.
Bringing a device into the network with “Prog IP”
Older devices – the LoDi-Rektor, LoDi-Shift-Commander and the old LoDi-S88-Commander – get their network address by broadcast. You do this with the “Prog IP” button in the “LoDi Network” card. The LoDi-S88-Commander LX gets its address via DHCP and doesn't need this.
- Press the button on the devicePress the Prog IP button on the device. The red LED shows that it is ready.
- Open the dialogClick “Prog IP”. The “Prog IP — bring the device into the network” dialog opens.
- Enter the valuesChoose the “Device name” (or “custom name …” with at most 16 characters, without umlauts or spaces), the computer's “Network interface” and an “IP address”. “check” tests whether the address is free, “Suggestion” proposes one. Add “Gateway” and “MAC address” (with “generate”) if needed.
- ApplyClick “Apply”. LoDi-Aura sends the settings, the device restarts and a new search runs automatically.
The device page
“Open” on a card under “My layout” or “Open device ›” on the “Interfaces & Devices” page shows the device page. At the top are the name, address, firmware and transport, next to them the status and the “Set online” or “Set offline” button. “← All Interfaces” takes you back to the overview.
| Tab | Content |
|---|---|
| “Device” | Device data, capabilities and usage, the settings specific to the device type, network and firmware. |
| Bus tab | Depending on the device it is called “LoDi bus” (LoDi-Rektor), “S88.2 bus” (S88-Commander), “Shift buses & modules” (Shift-Commander), “R-Bus” (Z21) or “Buses & Modules”. This is where you see and manage the connected modules. |
| “Diagnostics” | Connection and live values of the device. |
The “Device” card
| Row | Meaning |
|---|---|
| Type | The detected device type, e.g. “LoDi-S88-Commander LX”. |
| Address | IP address and port. |
| Firmware | The firmware version read when connecting. |
| Transport | Whether LoDi-Aura talks to the device via UDP or TCP. This depends on the device and firmware; you don't set anything. |
| Status | The current state of the connection. |
| Last check | When LoDi-Aura last reached the device. |
Capabilities and usage
Under “Capabilities & Usage” you use tick boxes to decide what LoDi-Aura may use the device for. Only what the device can do is offered.
| Tick box | Effect |
|---|---|
| “Go online with the layout switch (top)” | When you flip the “Layout” switch in the header, this device is connected too. Untick it for a device the switch shouldn't touch, e.g. a separate second system. |
| “Use for driving” | Locos may be driven via this device. |
| “Enable for switching (track plan)” | The device appears in the track plan as a “Switching command station” for turnouts, signals and lights. |
| “Use feedback” | The feedback sensors of this device count towards block occupancy. |
| “Model time master (sets the pace — the other devices with a clock follow)” | This device sets the model time. |
| “Evaluate RailCom” | LoDi-Aura evaluates the RailCom messages from this device. |
| “Booster connected” | LoDi-Rektor only, ticked by default: LoDi-Aura manages the boosters on its LoDi-Bus. |
| “on the main switch (central GO/STOP)” | LoDi-Rektor only: it is switched along with the central main switch. Untick it for a separate second system that the main switch doesn't touch. |
| “Track boosters off if this device goes offline unintentionally” | On all devices except the LoDi-Rektor. Only takes effect on an unintended failure, not when you switch the device offline by hand. Requires the LoDi-Rektor to be able to switch the track boosters. |
| “Receive watchdog — report failure after … s” | S88-Commander only: if no packet arrives for this long (1 to 5 s, default 3 s), the device counts as failed and goes offline – and with the tick box above, the track boosters too. |
Disabled devices
“Disabled” means: the device doesn't go online with the “Layout” switch, and the header doesn't count it. To switch it back on, open the device page and tick “Go online with the layout switch (top)” in the “Device” tab. Anything another window sets up or removes appears in every open window without reloading.
Network / IP
The “Network / IP” card shows the device's network data. What you can do there depends on whether the device is online.
| State | What the card offers |
|---|---|
| Device offline | “IP address (where to search)”: if the device has been given a new address (e.g. by the router), enter it here and click “Apply address”. LoDi-Aura connects there the next time you choose “Set online”. The device itself isn't reprogrammed, and all links in the project are kept. |
| Device online | “Device name”, “IP address”, “Subnet mask”, “Gateway”, “UDP port (fixed)” and “MAC address”. “Read again” fetches the values from the device, “Apply IP” writes them. |
| Device with its own web interface | On the LoDi-S88-Commander LX from firmware 7 and the LoDi-Shift-Commander LX, the device manages its address, subnet mask, gateway and name itself, on its web interface under “System” › “Network”. The card shows a button leading there, and the address (see Web interface). |
Firmware
The “Firmware” card shows the “Installed” version and what the “Update server” offers: “up to date” or “Update available”. In the version list, “Install” installs a version and “Flash again” writes the existing one once more. “⟳” reads the versions again.
The device is switched offline automatically for the update and restarts afterwards. At the end, LoDi-Aura reports “Firmware update finished — device has restarted.”
The LoDi-Shift-Commander LX and the LoDi-S88-Commander LX from firmware 7 update their firmware themselves, on their own web interface. The “Firmware” card then points you there.
Removing a device
“Remove interface from the project” at the bottom of the device page – or the bin icon “Remove from project” on the card on the “Interfaces & Devices” page – takes the device out of the project.
LoDi devices
How to configure the individual LoDi devices – buses, modules, outputs, boosters – is described on the devices' setup pages. Here you only find what LoDi-Aura uses them for.
| Device | Job in LoDi-Aura | Setup |
|---|---|---|
| LoDi-Rektor | Driving and switching, plus the LoDi-Bus with its modules. Its track protocols and options are on the device page in the “Rektor protocols” card. | Setting up the LoDi-Rektor |
| LoDi-S88-Commander (LX) | Feedback module. Delivers the feedback sensors from which LoDi-Aura works out the train position. The old S88-Commander (without LX, firmware below 6) only speaks UDP – LoDi-Aura adjusts to this by itself. | Setting up the LoDi-S88-Commander LX |
| LoDi-Shift-Commander (LX) | Switching bus and outputs for turnouts, signals and accessories. LoDi-Aura talks to the Shift-Commander LX (firmware 2 and later) via TCP and to the old Shift-Commander (firmware 1) via UDP. On the card, the LX is called “LoDi-Shift-Commander LX”; it manages its device settings and firmware on its own web interface. You still operate Shift buses, turnouts and lighting in LoDi-Aura. | Setting up the LoDi-Shift-Commander, Setting up the LoDi operators |
| LoDi-Booster, LoDi-Booster 10A (+), LoDi-8-GBM(-P) | Track power and current measurement per channel. | Setting up the LoDi-Booster, Setting up the LoDi-Booster 10A (+), Setting up the LoDi-8-GBM(-P) |
| LoDi-CV-Programmer | Read and write CVs, read out mfx decoders. | Setting up the LoDi-CV-Programmer |
Third-party command stations
Your existing command station can stay. LoDi-Aura integrates the Roco/Fleischmann Z21, Märklin® CS3, ESU ECoS and Lenz command stations with XpressNet (LZV200 on the 23151 interface). “Search for devices” finds them on your own network; if the command station is somewhere else, enter it with “Check now”. After that it appears just like a LoDi device, with a card, device page and capabilities.
| Command station | Connection | What LoDi-Aura can do with it | Limits |
|---|---|---|---|
| Roco/Fleischmann Z21 and Z21-compatible command stations (card: “Roco Z21”) | Network, UDP port 21105. The search finds them by broadcast; enter YaMoRC command stations by hand. | Driving with 14, 28 or 128 speed steps, track power, switching turnouts and accessories (DCC), feedback modules on the R-Bus (up to 20 modules with 8 inputs each), CVs on the programming track and on the main track (reading via RailCom), accessory CVs on the main track, model clock from Z21 firmware 1.43. Track power state, short circuit, and current, voltage and temperature appear in the booster overview. | No Motorola accessories – please run turnouts as DCC. No extended accessory command (signal aspects). No 27 speed steps. CVs for DCC decoders only. LoDi-Aura doesn't evaluate the Z21's RailCom data. |
| Märklin® CS3 | Network, TCP port 15731. | Driving (DCC, Motorola, mfx®), track power, switching turnouts and signals, feedback modules via the CS3's Link S88 (sensors e.g. 1101.5), reading and writing mfx decoders, importing the CS3's loco list. Stop/Go on the CS3 as well as current, voltage and temperature appear in the booster overview. | Driving commands given on the CS3 itself or on a Mobile Station don't appear in LoDi-Aura. LoDi-Aura only knows whether track power is on at startup after the first Stop or Go. |
| ESU ECoS | Network, TCP port 15471. | Driving, track power, switching turnouts and accessories (DCC and Motorola), feedback modules (module 1 is the ECoS's first feedback module), CVs on the programming track and on the main track, importing the ECoS's loco list. Driving with the ECoS throttle appears in LoDi-Aura. | Every loco must be set up in the ECoS – otherwise LoDi-Aura reports “is not set up in the ECoS”. Feedback modules only report occupied or free, without current and without RailCom. No extended accessory command. Instead of measured values, the ECoS only shows its configured current limit. |
| Lenz LZV200 on the 23151 interface (card: “XpressNet”) | Network, TCP port 5550. The search only finds the interface on your own network; otherwise enter its IP address under “Check now”. | Driving with 14, 27, 28 or 128 speed steps and F0 to F28, track power, switching turnouts and accessories (DCC, addresses 1 to 2040), feedback modules on the R/S bus (e.g. LR101), CVs on the programming track and on the main track (reading on the main track from command station version 3.8). | No Motorola and no mfx. No extended accessory command. Feedback modules only report occupied or free. LoDi-Aura only polls the feedback modules that are used in the track plan. CV 7 is never written on the main track, because on the LZV200 that changes the command station itself. |
Z21 settings
Turnout 1 in LoDi-Aura is turnout 1 in the Z21 app – both when switching and when reading accessory CVs. How the Z21 counts turnouts is set in the Z21 itself: Z21 Maintenance Tool › Settings › “DCC turnout addressing compliant with RCN-213”. Switched on, it counts like other command stations (turnout 1 = decoder 1); by default it is off (turnout 1 = decoder 0).
“Feedback modules on the R-Bus” (1 to 20, default 20): the Z21 doesn't tell how many modules are connected – a missing module simply reports “free”. Modules 1 to 20 are the R-Bus addresses set on the modules, and each has eight inputs. A changed number applies the next time you switch online.
“Keep the Z21's model clock in step”: when ticked, the Z21's clock follows LoDi-Aura's model time – to the minute and with whole-number factors from 1 to 63. When unticked, it runs on its own.
XpressNet command station settings
The “DCC turnout offset (RCN-213)” tick box sets how LoDi-Aura counts the turnouts on this command station. When ticked, it counts like the XpressNet command station itself and like the ECoS – that's the normal case. When unticked, it counts four lower, like a Z21 with factory settings, a multiMaus or the LoDi-Rektor without this tick. Use that if your decoders were given their numbers there.
How you notice it: you switch number 1, and the turnout you set up as 5 moves. Turnouts 1 to 4 don't exist on the XpressNet command station without the tick.
On the LoDi-Rektor, the same tick box is called “DCC turnout offset” and is in the “Rektor protocols” card (see Turnouts and signals). If a single turnout switches the wrong way round, change that on the turnout itself – with “Connection swapped (straight ↔ diverging)”, not on the command station.
Importing locos from the command station
When a CS3 or ECoS is online, “⤵ Import” in the “Vehicles” tab asks where the locos should come from: “From the Märklin CS3” or “From the ESU ECoS” imports all the command station's locos – only locos, no turnouts – and “From file (iTrain)” reads a file. The locos are copied once; after that you maintain them in LoDi-Aura. More on this under Locos, cars and trains.
Booster overview and track power
You open the booster overview with “Booster ⧉” on the right of the tab bar. It shows all boosters with live current per channel. A short circuit is a state of its own, not just an error message.
At the top, under “Command station current”, the command stations are shown as cards, each with its own track power switch. A LoDi-Rektor with its own boosters groups them on its card; its switch switches them all. “⏻ All on” or “⏻ All off” switches everything connected to the main switch. “Separate window” moves the overview into a window of its own.
You can also switch the track power of all boosters with “Booster” in the header.
Problems?
| Problem | Solution |
|---|---|
| The search doesn't find a device. | If it's on a different network, enter it with “Check now”. Always enter YaMoRC command stations by hand. Bring an older LoDi device without a valid address into the network with “Prog IP”. |
| A device has been given a new IP address. | Switch it offline, enter the new address in the “Network / IP” card and click “Apply address”. There's no need to delete it and add it again. |
| The “Switching command station” selection on a turnout is empty. | Tick “Enable for switching (track plan)” on the device page. |
| A device doesn't go online with “Layout”. | It's disabled. Tick “Go online with the layout switch (top)”. |
| The wrong turnout switches, four numbers off. | Check the turnout numbering: “DCC turnout offset” on the LoDi-Rektor, “DCC turnout offset (RCN-213)” on the XpressNet command station, and on the Z21 the RCN-213 setting in the Z21 itself. |
| A turnout switches the wrong way round. | Tick “Connection swapped (straight ↔ diverging)” on the turnout in the track plan. |
| A loco doesn't run on the ECoS. | Set up the loco in the ECoS or import it from there. |

