The LoDi system

How the LoDi system works

One PC, one network and three interfaces, one for each job. This page explains how the parts work together – and at the very end the layout planner works out what your layout needs.

The idea

  1. The PC thinks

    The intelligence sits in your control software, such as iTrain, WinDigipet or Modellbahnstellwerk. It plans routes and runs the trains automatically; the LoDi devices are its eyes, ears and hands. You set them up with the free LoDi-ProgrammerFX for Windows, macOS and Linux.

  2. The network connects

    The PC and the devices sit on your ordinary router or switch – with the yellow network cable that comes with every interface. No special cable to the PC, no interface card.

  3. Each job has its own bus

    Running, switching and feedback go through three separate interfaces, each with a bus of its own. Setting turnouts never slows the trains, and you only build the part you need right now.

Three jobs, three interfaces

There is one LoDi-Rektor per layout, and one of each Commander is usually enough – a second only comes in with a great many modules. Behind them go as many modules as your layout needs.

Running

Making the commands and putting power on the track.

Interface
LoDi-Rektor – the command station
Bus
LoDi bus, green
Behind it
LoDi-Booster with two power districts of 2.3 A each; for the large scales the Booster 10A and 10A+

The Rektor turns the PC’s commands into the track signal in DCC, mfx® and Motorola and drives every booster. On a short circuit a booster cuts only the district concerned and reports where it happened.

Switching & lights

Turnouts, signals and lighting on a bus of their own.

Interface
LoDi-Shift-Commander
Bus
SC bus, purple
Behind it
Operator modules: 4-WD for turnouts (AC or DC), 16-SD-FL for signals and lights, Light-Operator for the room lighting

Up to 480 switching outputs on one Shift-Commander, with no load on the track signal. The modules are daisy-chained with patch cables and recognised when plugged in; the timing for the room lighting is built in.

Feedback

From the track back to the software: which train is where?

Interface
LoDi-S88-Commander LX
Bus
S88.2 bus, blue
Behind it
LoDi-8-GBM v2 for eight sections, 8-GBM-P for the large scales, RM-16+ for three-rail contact tracks

The detectors spot occupied track, read over RailCom which loco is there and pin a short circuit down to the block. The S88-Commander collects this from up to 96 modules and hands it on to the control software.

You can tell the cables by their colour

Every connection has its colour – on the cables, the sockets and the bus LEDs of the modules. So even under the layout you see at once what goes where.

  • Yellow: network Not a bus but the LAN line from the router to the three interfaces. Yellow is the usual standard for computer networks.
  • Green: LoDi bus From the LoDi-Rektor to the boosters – running.
  • Purple: SC bus From the Shift-Commander to the Operator modules – switching and lights.
  • Blue: S88.2 bus From the detectors to the S88-Commander LX – feedback.
  • Red: switching over DCC Decoders that read their commands straight from the track signal – the second way of switching, see below.

Switching works without a second bus too

Turnout and servo decoders for DCC need no interface: they sit straight on the track signal and work with any DCC command station, including one from another maker. That pays off for a few turnouts or servos. For many outputs, for signals and for lights the Shift-Commander is the better way – lights only go through it.

What you already have stays

  • Your current command station

    With the LoDi-Rektor it can stay on the layout as a hand controller.

  • Your feedback modules

    Existing s88 and s88N detectors keep working on the S88-Commander LX.

  • Another maker’s command station

    The LoDi-Con hand controller also talks to command stations using the Z21 protocol, CS2/CS3, ECoS or Lenz, and the DCC decoders switch on any DCC command station.

Layout planner

Which devices do I need?

Describe your layout; the planner works out which LoDi devices you need and puts them all in the cart.

1Which track?

Centre conductor like Märklin®, or two rails

2Which scale?

decides the booster and the detectors

3What do your locos speak?

Motorola locos do not report over RailCom

4How many power districts?

separately powered track sections

5How many detection sections?

blocks in which the software sees the locos

6How many turnouts?

set electrically

7How are they switched?

straight off the track or over a bus of their own

8Turnout drives

solenoid, motor or servo

9How many LED outputs?

for light signals, lamps and effects

10Dim the room lighting?

day and night with RGBW LED strips

11Add a hand controller?

LoDi-Con, over Wi-Fi