Digikeijs DR5000

Reference for the Digicentral DR5000 DCC command station in the context of the BigFred hub. Manufacturer documentation: DR5000 Instruction Manual (PDF).

BigFred terminology: command station / centralka — see 00-terminology.md.

1. Role on the layout

The DR5000 is a universal DCC command station (centralka) with almost every common model-railroad bus on one chassis: LocoNet, XpressNet, B-Bus, R-Bus, ext88N/S88N, RS-Bus, LAN, Wi-Fi, and USB. It generates DCC on an H-bridge track output, manages locomotive slots, and can host handhelds, boosters, and feedback modules at the same time.

In a BigFred deployment the Pi host runs loco-server and one dcc-bus daemon per attached command station. On the supported path the daemon talks to the DR5000 over LocoNet serial via an Uhlenbrock 63120 USB interface on LocoNet-T — not over the DR5000's own USB or LAN ports.

Browsers ──HTTP/WS──► loco-server (e.g. Raspberry Pi 5)
                          │
                          ▼
                     dcc-bus ──► /dev/loconet-63120 @ 57600 8N1
                          │
                     Uhlenbrock 63120 (USB 3)
                          │
                     RJ12 LocoNet-T
                          │
                     DR5000 ──► DCC track ──► layout

Full wiring and LNCV setup: hardware §2–§6.

2. Product variants

Third-party PSUs are allowed if 14–22 V DC, CE-approved — Digikeijs accepts no liability for damage from non-supplied PSUs.

Configuration software and firmware updates: www.digikeijs.com/dr5000-information.

3. Technical specifications

3.1 Bus limits (manufacturer)

Each DR5033 booster adds 3 A with automatic phase reversal. Use only electrically isolated boosters (H-bridge output). Common-ground boosters (e.g. older Märklin, Uhlenbrock) must not be used — they cause shorts and can destroy the DR5000.

3.2 Load and current capacity

Maximum track output is 3 A (adjustable in DR5000 Tool → Track Output). With one internal booster only, plan current draw across running locos and accessories; add DR5033 LocoNet or B-Bus boosters when more power is needed.

Locomotive slots (117) are the command station's logical limit, independent of the ampere limit. BigFred does not impose its own slot cap beyond what the DR5000 provides.

4. Supported protocols

The DR5000 implements many protocols simultaneously on different physical buses. For LAN/Wi-Fi, only one protocol is active at a time (selected in DR5000 Tool → LAN settings).

Compatible PC software listed by Digikeijs: iTrain, RocRail, Koploper, TrainController, DecoderPro, WinDigipet, and other LocoNet/XpressNet programs.

4.1 Hardware connectors

Front-panel LEDs indicate track load (short-circuit flashes), LocoNet, Wi-Fi, LAN, USB, and bus activity.

4.2 Safety and wiring warnings

Critical manufacturer rules (warranty void if ignored):

• Never connect external power or another digital system to Track Out or Prog. Track — destroys electronics.
• Never use common-ground boosters with the DR5000.
• 3-wire / H-bridge feedback: do not use DR4088GND or any feedback device that switches against track ground — use DR4088OPTO (or opto-isolated equivalents) instead. Applies to other manufacturers' modules too.
• Turn the DR5000 off before working on track wiring.
• Do not open the housing or PSU (24-month warranty otherwise).
• Use only approved wiring; dry, dust-free environment.

5. RailCom

The DR5000 supports RailCom cut-outs on the main track (DR5000 Tool → Track Output): polarity, automatic polarity change, and cut-out generation.

With DR5088RC RailCom detector modules on LocoNet:

• Block occupancy and RailCom data back to the command station.
• QoS percentage in the built-in speed controller (track/decoder cleanliness).
• POM CV read via Roco Multimaus / wlanMAUS (firmware ≥ 1.5.1, DR5088RC on track, RailCom enabled in decoder and central) — see manual §10.1.

BigFred does not implement RailCom-based auto-addressing or POM from the web UI over the LocoNet serial path — it uses static DCC addresses in the vehicle catalogue. CV access over BigFred's LocoNet driver is not supported (§8.1).

6. LAN and Wi-Fi

The DR5000 includes a built-in network router. Startup takes ~30 seconds.

6.1 Home network (LAN)

Connect the LAN port to the club/home router. The router assigns an IP via DHCP (recommended). The assigned address is shown in DR5000 Tool (firmware ≥ 1.4.x).

Important: the DR5000 cannot join your home network as a Wi-Fi client. Wi-Fi is only for clients connecting to the DR5000 (tablets, wlanMAUS, etc.).

6.2 Wi-Fi access point (factory)

Use for initial setup or direct tablet/handset connection. For BigFred, prefer Ethernet on the Pi and LocoNet serial to the DR5000 — not Wi-Fi to the central.

6.3 LAN/Wi-Fi protocol selection (one at a time)

Configure via DR5000 Tool → LAN settings (USB connection to the DR5000 required; LAN settings are greyed out without LAN cable to router or PC connected to DR5000 Wi-Fi). After changing protocol, wait ~60 s for the LAN/Wi-Fi module to restart.

Digikeijs warning on Z21 LAN: the Z21 UDP protocol lacks end-to-end control; data loss can occur — it is not optimally suited for PC control software when used concurrently with Z21 app / wlanMAUS. BigFred therefore standardises on LocoNet serial for the DR5000, not z21 over LAN.

Gateway vs Bridge: prefer Gateway mode with the DR5000 on the home router. Bridge mode (DR5000 as router, PC on DR5000 LAN only) is for setups without a home network — requires network expertise.

Factory reset of LAN/Wi-Fi settings: Wi-Fi settings menu (software/firmware ≥ 1.4.1). General factory reset does not clear LAN/Wi-Fi.

7. USB

USB serves configuration, firmware update, and virtual COM ports for model-railroad software.

7.1 Virtual COM ports

Windows assigns three COM ports when the DR5000 is connected (numbers vary by PC). Example from the manual:

View assignments in DR5000 Tool → USB 2.0.

Baud rates (manufacturer examples — depend on client software):

Available USB protocols (selectable in configuration): LocoNet®, XpressNet-USB 3.6, LocoNet Binary®, Dr.Command®, Z21®.

7.2 Firmware recovery

If a firmware update fails (serial numbers DR5000-A and later):

1. Disconnect power; connect USB; hold GO, apply power — check Device Manager for “DR5000 Firmware Update” (green + red LEDs on).
2. Full recovery: disconnect all cables; hold GO + STOP, apply power; release; connect USB; run Update DR5000 from USB settings.

After recovery the unit returns to as-delivered condition.

BigFred does not use the DR5000 USB LocoNet port on the supported path — see §8. Keeping USB free simplifies firmware maintenance at the layout.

8. BigFred integration

8.1 Recommended: LocoNet serial via Uhlenbrock 63120

BigFred officially supports the DR5000 through loconet_serial: an Uhlenbrock 63120 on the Pi's USB, cabled to LocoNet-T (never LocoNet-B).

Uhlenbrock 63120 LNCV (LocoNet-Tool, art. 63120): LNCV 2 = 3 (57600 baud), LNCV 4 = 1 (LocoNet Direktmodus / transparent raw frames). Factory defaults are often 115200 + filtered mode — wrong settings cause garbage in BigFred.

URI parser: pkgs/bigfred/dcc-bus/service/station/driver.go.

Example daemon invocation:

dcc-bus \
  --station-kind loconet_serial \
  --station-uri "serial:///dev/loconet-63120:57600" \
  --speed-steps 128 \
  …

Driver: pkgs/loco/commandstation/loconet.go.

BigFred capabilities over LocoNet serial (DR5000):

External observation: 16-dcc-bus/09-external-state-observation.md.

Pin udev rules, dialout group, and optional 62280 Luisa repeater: hardware/04-uhlenbrock-63120.md.

8.2 Alternative: LocoNet over TCP (best-effort)

The DR5000 can expose LocoNet LBServer on LAN/Wi-Fi (set protocol in DR5000 Tool). BigFred's loconet_tcp driver speaks LocoNetOverTcp (SEND / RECEIVE lines):

Requires LAN protocol = LocoNet LBServer, DR5000 on the same network as the Pi, firewall allowing TCP 5550. Same capabilities/limits as serial LocoNet (F0–F28; service-mode CV; no F29+/POM CV). Not the official BigFred runbook path — prefer Uhlenbrock 63120 for observation reliability and documented bring-up.

8.3 Alternative: DR5000 USB LocoNet (best-effort)

The DR5000 USB LocoNet COM port could be opened as loconet_serial on the Pi (e.g. serial:///dev/ttyACM0:57600 or 115200 per client). This doc set standardises on Uhlenbrock 63120 so the central's USB stays on the workshop PC for DR5000 Tool and the hub host is always the Pi (§1.6 in hardware/01-overview).

8.4 Alternative: Z21 over LAN (not recommended)

The DR5000 can select Z21 as the LAN/Wi-Fi protocol for Roco wlanMAUS / Z21 app. Digikeijs warns that UDP Z21 is prone to data loss for PC automation. BigFred supports z21 in code, but DR5000 + z21 is not the supported combination — use loconet_serial.

8.5 What not to use with BigFred

LocoNet-T remains available for FRED, other LocoNet handhelds, and feedback modules while BigFred drives the bus through the Uhlenbrock 63120.

8.6 Handheld compatibility (manual + practice)

9. BigFred setup (summary)

1. Wiring: Uhlenbrock 63120 → Pi USB 3; RJ12 → DR5000 LocoNet-T; DR5000 powered; LNCV 57600 + Direktmodus programmed.
2. udev: pin /dev/loconet-63120; service user in group dialout.
3. Admin → Command stations: e.g. DR5000 (LocoNet), kind loconet_serial, URI serial:///dev/loconet-63120:57600, speed steps 128.
4. Layout: attach to layout (POST /api/v1/layouts/{id}/command-stations).
5. Supervisord starts dcc-bus-<layout>-<station> — 16-dcc-bus/02-process-model-and-cli.md.
6. Driver: pick the command station in the throttle dropdown.

One writer per LocoNet USB port: do not run JMRI LocoNet and dcc-bus on the same /dev/loconet-63120 simultaneously.

10. Bring-up checklist

• [ ] PSU within 14–22 V (recommended 15–18 V); track wiring per H-bridge rules.
• [ ] Uhlenbrock 63120 on LocoNet-T; LNCV 57600 + Direktmodus verified.
• [ ] /dev/loconet-63120 present; user in dialout.
• [ ] DR5000 GO — track power on; LocoNet activity LED responds.
• [ ] BigFred catalogue: loconet_serial, URI serial:///dev/loconet-63120:57600.
• [ ] dcc-bus log: LocoNet connected / no checksum errors.
• [ ] Driver session: setSpeed moves a loco.
• [ ] Physical throttle change visible in UI (LocoNet observe path).
• [ ] Second browser session on another DCC address.

Common issues: wrong LocoNet port (B vs T), wrong LNCV baud/mode, weak LocoNet bus power (add 62280 Luisa), USB autosuspend, parallel serial port users, RailSync mis-wire.

11. Related documents

Back to the command stations index.