RailCommand Desktop App
The RailCommand desktop app is the native operator surface for running trains. Use it when you need local hardware status, session readiness, Engineer Cab controls, CTC dispatching, Yardmaster workflows, tablet pairing, or offline .rspkg operation.
Web, Desktop, and Runtime
RailCommand has three parts:
| Surface | What it is best for |
|---|---|
| RailCommand web | Layout planning, imports, schedules, panels, reports, training, and account-backed management. |
| Desktop app | Live operation, hardware status, running trains, CTC dispatching, Engineer Cab, pairing, and local/offline workflows. |
| UE5/local host | Runtime authority for local graph execution, safety state, and physical-hardware decisions. |
The desktop app presents controls and forwards operator intent. The local runtime owns safety-critical execution decisions.
First Launch
When the desktop app opens:
- Log in to the cloud backend or open a trusted local
.rspkglayout file. - Choose the operating layout.
- Open Hardware Setup if the command station or local runtime needs attention.
- Run Ops Readiness.
- Start, resume, or join an operating session.
- Open the role surface you need: Engineer Cab, CTC Dispatcher, Yardmaster, Crew Management, Roster, Inventory, Layout Editor, or Panel Editor.
When to Use the Desktop App
Use the desktop app for:
- Hardware-connected operating sessions.
- Running locomotives from Engineer Cab.
- Dispatching with a native CTC panel.
- Pairing phones or tablets to a local session.
- Offline operation from a local
.rspkg. - Monitoring local runtime and hardware health.
Use the web app when you are setting up account-level data, writing reports, importing large datasets, reviewing training, or managing organization settings.
Safety Notes
- Do not bypass disabled actions.
- If layout switching is blocked, follow the reason shown by the app.
- If movement is unexpected or uncertain, use emergency stop.
- Do not assume the browser, cloud, or desktop UI alone is the physical-hardware authority.