Early Access & Testing
PanelsDCC is made up of three closely related parts that work together:
- PanelsDCC Design – configure trains, accessories, and visual panels in the cloud, away from the layout.
- PanelsDCC Control – run the railway from a Raspberry Pi, using phones, tablets, laptops, and big screens over your local network.
- PanelsDCC Connect – link the Raspberry Pi to your DCC command station.
If you’d like a deeper tour of how these fit together, you can read more on the architecture and installation pages, but you don’t need to know every detail to help with testing.
Learn more about the PanelsDCC architecture →
Read the PanelsDCC installation overview →
Where testing fits
Phase 1 of the early access programme focuses on PanelsDCC Connect – the part that talks directly to your DCC command station. The aim is to run a few focused tests with a range of controllers and build confidence in the hardware link across different systems.
What needs testing
PanelsDCC Connect is the bridge between your physical DCC layout and the PanelsDCC Control application running on a Raspberry Pi. The primary target is a Raspberry Pi connected to your DCC command station, but PanelsDCC Connect can also be run on other Java-capable platforms.
PanelsDCC Connect is built on top of JMRI’s connection abstraction layer – the part of JMRI that talks to different DCC systems. PanelsDCC uses this layer purely for controller connectivity, not for JMRI’s own panels, automation, or configuration tools.
PanelsDCC Connect is open source and available on GitHub: PanelsDCC/connect. The README explains how it works and documents the API that PanelsDCC Connect exposes to PanelsDCC Control.
If you’re confident with software, you can also experiment with running PanelsDCC Connect on other platforms and let us know how it behaves.
Why your help is needed
PanelsDCC is a hobby project that has taken years to reach this point, developed alongside a full‑time job and family life (as mentioned on the future plans page). There’s no big team or corporate backing – just one person building something they hope will help more people enjoy the hobby.
So far, most testing has been with a Hornby Elite controller, which works well and even auto‑detects when connected to a Raspberry Pi. To make PanelsDCC genuinely useful, the hardware link needs to be proven with a much wider range of command stations.
That’s where you can make a big difference: by running a short, focused set of tests with your own controller and sharing what you find.
Who this is for
PanelsDCC is still evolving, and there are practical constraints on available time and access to different hardware.
Ideal volunteers:
- Are comfortable running in‑development software
- Have experience connecting command stations to PCs
- Ideally have some experience with JMRI and know what already works for their setup
Even better: If you’re familiar with JMRI’s connection layers or confident using AI‑assisted tools (such as Cursor) to work in Java or Kotlin, you can help by contributing directly to the PanelsDCC Connect code via pull requests – especially for new controllers.
Alternatively, if you’re willing to lend a controller (with the necessary PC connection parts), that can help accelerate support for that system.
Time constraints: I can’t provide detailed one‑to‑one setup support beyond what’s written in the installation and testing guides, especially for controllers I don’t physically own. If you’re happy to follow technical instructions and troubleshoot, you’re exactly who this phase is aimed at.
Important disclaimer: All testing software is provided without warranty. You use it entirely at your own risk and remain responsible for your own equipment.
What you’ll actually test
If you join Phase 1, you’ll focus on a small but representative set of checks:
- PanelDCC Connect installation on a Raspberry Pi
- Controller detection and connection with your specific command station
- Basic train control – one test locomotive: speed, direction, and a few key functions
- Accessory control – at least one accessory address, thrown and closed
- Stability and reliability over a short operating session
PanelsDCC Connect includes a local configuration web interface so you can configure the connection and run these tests without needing your full PanelsDCC layout configured.
Controller status
This table focuses on a few common systems and whether PanelsDCC Connect has a direct integration yet. It’s intentionally limited because my direct access to hardware is limited – which is exactly why this early access programme exists. If you have spare command stations and their PC interfaces that you can lend for a period, that can significantly accelerate testing and implementation, especially for widely used systems.
| Controller | Implemented in PanelsDCC Connect | Status | Notes |
|---|---|---|---|
Hornby Elite / XpressNet (xnet-elite) |
Yes | Working | Reference controller for development; used to prove the end‑to‑end PanelsDCC Connect flow. |
DCC-EX CSB1 (USB) (dccpp-ex-usb) |
Yes | Working | DCC++ / DCC‑EX command station; fully tested with PanelsDCC Connect over USB. |
NCE PowerCab (serial) (nce-serial) |
Yes | Untested | |
NCE PowerCab (USB) (nce-usb) |
Yes | Untested | |
DCC++ (Ethernet) (dccpp-ethernet) |
Yes | Untested |
If you have a controller that is listed as untested – or a completely different system that JMRI already supports – your feedback in Phase 1 is especially valuable.
JMRI command stations that PanelsDCC could target
Because PanelsDCC Connect builds on top of JMRI, many more command stations are theoretically reachable. The list below is based on the JMRI hardware documentation and shows systems that JMRI can already talk to, even if PanelsDCC Connect does not yet integrate them directly.
| JMRI-supported command station | Notes |
|---|---|
| Atlas Commander | Connected via Lenz / XPressNet style interfaces. |
| CVP EasyDCC | Serial or terminal server connection. |
| DCC-EX EX-CommandStation | Open‑source Arduino‑based command station. |
| DCC++ | Open‑source Arduino‑based command station. |
| Digikeijs DR5000 | Multi‑protocol command station. |
| Digitrax command stations | Connected via LocoNet interfaces (PR3/PR4, LocoBuffer, etc.). |
| ESU ECoS | Ethernet‑connected command station. |
| Fleischmann Twin Centre | LocoNet‑based; also supports Z21 / z21 via Ethernet. |
| Hornby Elite / Select | USB or XPressNet‑style connections. |
| Lenz systems | XPressNet‑based command stations and interfaces. |
| Lionel TMCC | Serial‑connected command base. |
| Märklin CS2 | Ethernet‑connected command station. |
| MRC command stations | JMRI can configure decoders; see JMRI docs for details. |
| NCE PowerCab / Power Pro | Serial or USB connections, depending on hardware. |
| Roco LocoMaus / MultiMaus / multiZENTRAL‑Pro | Typically via XPressNet‑compatible interfaces. |
| Roco Z21 / z21 | Ethernet‑connected command stations. |
| SPROG DCC / SPROG Generation 5 | Can act as stand‑alone command station and programmer. |
| TAMS Master Control | TAMS command station family. |
| TCS CS‑105 | TCS command station. |
| Uhlenbrock Intellibox (I / II) | LocoNet, serial, or USB connections depending on model. |
| Viessmann Commander | XPressNet‑style connection via Lenz‑type interfaces. |
| Wangrow System One | Serial‑connected command station. |
| Zimo MX‑1 | Zimo command station. |
| ZTC Controls systems | ZTC 511/521 and related systems via XPressNet‑style interfaces. |
If you run one of these systems and would like to see PanelsDCC Connect support it explicitly, please mention the exact model when you register for early access.
How to install PanelsDCC Connect
The installation flow for PanelsDCC Connect is described on the installation page, alongside the rest of the PanelsDCC setup. If you’re joining Phase 1, start there, then come back to this page for the testing checklist.
Your Phase 1 checklist
Once PanelsDCC Connect is installed, use the local web interface to run through a short checklist:
- Confirm PanelsDCC Connect starts cleanly and shows your controller connection options.
- Select your controller type and connection, then verify it reports as connected.
- Drive a single locomotive address: start, stop, change direction, and toggle at least one function.
- Operate at least one accessory address and confirm both thrown and closed states work.
- Leave the system running for a short session and note whether any errors or disconnects occur.
For more background on how PanelsDCC Connect fits with the rest of the system, you can also read the architecture overview.
Sending feedback and results
Your results are essential for deciding which controllers can be marked as supported, and where extra work is needed.
When you send feedback (ideally via email or GitHub), please include:
Setup details:
- Controller make and model
- Platform (e.g. Raspberry Pi model and OS version, or other platform)
- How you connected the controller (USB, serial, network, etc.)
Test outcomes:
- Controller detection: working / partial / not working, plus any messages shown
- Train control: what worked, what didn’t, and any odd behaviours
- Accessory control: which addresses you tried and what happened
- Stability: whether the system stayed connected and responsive during your session
You can either email your results or, if you’re comfortable with GitHub, raise an issue on the PanelsDCC Connect repository.
What happens next
As results come in, the controller matrix on the Phase 1 page will be updated, issues will be prioritised and fixed, and guidance for specific systems will be refined.
Your participation directly shapes which controllers are supported first and how smooth the setup is for the next person with the same hardware.