Execution modes

The execution mode tells TrainPanel where to send commands: to the internal simulator, to your command station, or to both. It is independent of the interaction mode — so Manual + Sim is just as valid as Auto + Normal.

Simulation

No command is sent to hardware. A built-in physics engine moves locomotives on the screen, based on their target speed, acceleration and calibration table. Sensors are triggered automatically when a virtual train crosses them.

When to use it:

• When you don’t have (yet) a command station.
• To work out an automation scenario before trying it for real.
• To test layout changes without disturbing trains that are running.

Real

All commands (speed, turnouts, status) are sent to the command station over the local network. Real sensors trigger block events.

See Z21 connection (coming soon).

Mixed

The hybrid mode: the real command station is driven as in Normal, but the physics engine also runs and propagates position changes to locomotives that are not physically on the layout.

In practice:

• A real locomotive on the layout reacts to commands sent to the command station.
• A virtual locomotive (declared in TrainPanel but with no physical counterpart) is updated by the simulator.

This is useful for:

• Keeping a digital twin of your layout during operation.
• Validating automation without having to bring all locos physically on the layout.

Summary

Mode	DCC commands	Physics engine	Real sensors	Simulated sensors
Simulation	❌	✅	❌	✅
Normal	✅	✅	✅	❌
Mixed	✅	✅	✅	❌

In Normal + Auto, the simulator stays active to track the estimated position of locomotives between sensors (needed for routing).