T2_C2
by keval17-wq
The T2_C2 server is the Master Control Program (MCP) for the Blade Runner project, designed to manage and coordinate various components of the system. It handles connections, tracks Blade Runner positions, manages speed, and processes status updates to ensure smooth and safe operation.
Last updated: N/A
What is T2_C2?
The T2_C2 server is the Master Control Program (MCP) responsible for managing and coordinating the Blade Runner system. It acts as a central hub for communication between various components, including CCPs, stations, and LED controllers.
How to use T2_C2?
To use the MCP server, you need to establish connections from CCPs, stations, and LED controllers to the designated UDP port (2001). The server then processes incoming data, sends commands, and manages the overall system operation. Refer to the documentation for specific command formats and initialization procedures.
Key features of T2_C2
Manages connections from CCPs, stations, and LED controllers
Logs events and statuses for monitoring and debugging
Initiates communication and handles initialization sequences
Tracks Blade Runner positions and prevents collisions
Manages Blade Runner speed based on track conditions
Use cases of T2_C2
Coordinating multiple Blade Runners on a track
Preventing collisions between Blade Runners
Managing the speed and position of Blade Runners
Controlling doors at stations and Blade Runners
Signaling block occupancy using LEDs
FAQ from T2_C2
What is the purpose of the MCP server?
What is the purpose of the MCP server?
The MCP server is the central control program for the Blade Runner system, responsible for managing communication, tracking positions, and ensuring safe operation.
How does the MCP server handle connections?
How does the MCP server handle connections?
The MCP server listens for incoming connections on a designated UDP port (2001) and can handle multiple connections from CCPs, stations, and LED controllers.
What are the ongoing features of the MCP server?
What are the ongoing features of the MCP server?
Ongoing features include initiating communication, tracking Blade Runner positions, managing Blade Runner speed, and receiving and processing status updates.
What features are not yet implemented in the MCP server?
What features are not yet implemented in the MCP server?
Not implemented features include collision prevention, coordinating stopping at stations, controlling doors, controlling LEDs, handling errors and reconnections, and initiating system-wide actions.
How does the MCP server prevent collisions?
How does the MCP server prevent collisions?
Currently, collision prevention is not implemented. The plan is to implement block occupancy logic and stop commands to prevent multiple Blade Runners from entering the same block.