T2_C2

What is T2_C2?

T2_C2 is a Master Control Program (MCP) server for the Blade Runner project. It manages connections from CCPs (Blade Runner controllers), stations, and LED controllers over UDP port 2001, logs events, and coordinates calibration and train operations. It is designed for controlling a model railway system with multiple autonomous vehicles.

How to use T2_C2?

The server listens on UDP port 2001 for incoming connections from CCPs, stations, and LED controllers. Calibration begins when Blade Runners are placed on the track; the system identifies each unit’s station location before starting a session. The README does not provide explicit installation or configuration steps beyond referencing the port.

Key features of T2_C2

• Manages multiple incoming connections from CCPs, stations, and LED controllers (100% working)
• Logs all significant events, statuses, and errors for monitoring (100% working)
• Sends basic initialization acknowledgments to CCPs (50% ongoing)
• Tracks Blade Runner positions from status updates (40% ongoing)
• Sends basic speed commands (SLOW, FAST) to CCPs (30% ongoing)
• Receives and logs status updates from all components (40% ongoing)
• Planned: collision prevention, door control, LED control, error handling, system-wide actions

Use cases of T2_C2

• Calibrating the positions of multiple Blade Runners on a track before a session begins
• Managing the movement and speed of Blade Runners on a track system
• Coordinating stops at stations using sensor data (under development)
• Preventing collisions through block occupancy management (under development)
• Synchronizing doors and LED signaling across stations and Blade Runners (planned)

FAQ from T2_C2

What transport protocol does T2_C2 use?

The server listens on a designated UDP port (2001) for connections from CCPs, stations, and LED controllers.

How does calibration work?

When a Blade Runner is placed on the track, it runs to the first station to register its location. All Blade Runners must be placed and identified before a session starts.

Are all features fully implemented?

No. Only connection management and event logging are 100% complete. Other features like position tracking, speed control, and status processing are partially implemented. Features like collision prevention, door control, and error handling are not yet implemented.

Where does T2_C2 store data?

The server logs events and statuses; the README does not specify a storage mechanism or location for persistent data.

Can T2_C2 handle reconnections?

The server can detect lost connections and will attempt to reconnect; if reconnection fails, it can issue emergency stop commands. This logic is not yet implemented.