You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know, WSL can often be a headache when dealing with hardware. I'm not sure anyone has tried running the simulator with WSL. At least I haven't tried. But thank you for sharing the experience.
The b is an alias for build, so it builds the image but doesn't actually run the container. If you are using the latest main branch, the log should provide information about your connected sniffer, autopilot and git environment. The argument --force has no sense for the build command.
If you want to run dronecan quadcopter simulation, you can try the following sequence of commands:
# Just in case if it is not the latest version:
git pull
git submodule update --init --recursive
./scripts/sim.py b # b is alias for build# Note that --force will override your autopilot's firmware and reconfigure all parameters.# Save the parameters before running it.
./scripts/sim.py dq --force # dq is alias for dronecan quadcopter
Then you should be able to fly in QGC.
Please, let me know if you encounter any further issues.
I have fc pixhawk 6c and sniffer like readme
Important note: I am using wsl with Ubuntu 22.04
Steps to reproduce:
./scripts/sim.py b --force
Sniffer and fc recognized by device manager and drone CAN GUI tool
but Result: container terminates in a second
The text was updated successfully, but these errors were encountered: