Eng Meet Train Embarkation V110 V2412 Install
| Symptom | Likely Cause | Solution |
|---------|--------------|----------|
| meet-ctl fails to detect v2412 | Version mismatch or timeout | Check meetd log: journalctl -u meet-v110 -f. Ensure v2412 container is on same network. |
| Door sequencing ignored | Legacy config in v110 overrides | Remove door_legacy_mode=true from C:\rail\meet\config.ini and restart service. |
| v2412 crashes on boarding compute | Insufficient RAM for AI model | Increase container memory: docker update --memory=4g embark-v2412 |
| eng meet train embarkation stuck at 99% | Deadlock between MEET event bus and embarkation callback | Restart both services in order: 1) MEET v110, 2) Embark v2412, 3) Register via CLI. |
Before touching the installer packages, confirm your target environment meets these baseline requirements: eng meet train embarkation v110 v2412 install
| Component | Minimum Specification | |-----------|----------------------| | OS | Windows 10 IoT Enterprise LTSC / Ubuntu 22.04 LTS (check your deployment) | | RAM | 16 GB (32 GB recommended for v2412 simulation) | | Storage | 50 GB free (SSD required) | | Dependencies | .NET 8.0 Runtime, Python 3.11+, Docker (for containerized embarkation modules) | | Network | Gigabit Ethernet, low-latency to train PLCs/TIMS | | Symptom | Likely Cause | Solution |
Critical: Backup all existing meet_cfg and embarkation_logs directories. Version v2412 overwrites rail mission profiles. Before touching the installer packages, confirm your target
The installer is packaged as a containerized microservice for isolation.
# Load Docker image
docker load -i EMBARK_v2412.bin
docker tag embark:v2412 rail/embark:latest