I’m working on a HIL/SITL setup and ran into an issue I can’t solve fully. I’d appreciate some help.
My Setup:
-Hardware: OrangeCube autopilot (shows up as COM11 on Windows, works fine in Mission Planner).
-Software:
- Windows 11
- WSL1 for running SITL and MAVProxy
- Mission Planner on Windows
My Goal:
- Run SITL in WSL (ArduCopter model).
- Use the OrangeCube hardware as the flight controller, but feed it simulated sensors/data from SITL.
- Connect telemetry to the Cube and control SITL through hardware.
What I Achieved So Far
- Followed the ArduPilot Sim-on-Hardware guide.
- Flashed the Cube with the SoH firmware.
- I can now see the
SIM_parameters on the Cube, which indicates the firmware is running correctly. - I can run SITL in WSL and see the available vehicle models.
The Problem:
- I’m stuck at the point of bridging SITL with the Cube.
- The Cube shows up on COM11 in Windows and works with Mission Planner, but on WSL it doesn’t appear as
/dev/tty*. - I tried approaches like
socatandusbipdto forward the serial device into WSL, but haven’t been able to make SITL actually talk to the Cube yet.
Has anyone here successfully run SITL + OrangeCube (SoH) inside WSL?
Any help or suggestions are appreciated!