I think it’s a function of multiple lines referencing the ardupilot directory in your ~/.profile as a result of running the install script more than once on different clones. Open it in an editor and remove duplicate looking lines that reference the old clone. Then log out and log back in.
im not sure i follow. theres only one clone. I just setup a new instance of wsl/ubuntu. i completely wiped the last one and ran the script once in the ~ directory.
Ok, that’s no factor then.
Did you log out and log in again after running the prereqs script?
I did. yes.
command not found indicates something not installed ?
Indicates that the script is not found in your user path, which is something that should be automatically configured when you run the script.
I’m going to create a new WSL2 instance and test with our latest branch to see if maybe something is broken. Will get back to you shortly.
thank you so much for the help
hey i just completely shut down vscode and got ALL the way out, used powershell to do a wsl shutdown, restarted it all and now it appears the command is working. this is what im getting now.
in the correct directory it is working now. Thanks again.
Change directory to ArduCopter (or whatever other vehicle you want to use) and run the script from there.
1 Like
i started qgc and it “just works” … there is no comm link listed, side topic, but do you know how that is? whats the connection to mavproxy?
I never use QGC (frankly, I rather despise it).
You should see something in the script output that looks like:
SIM_VEHICLE: Run MavProxy
SIM_VEHICLE: "mavproxy.py" "--out" "xxx.xx.xx.1:14550" "--master" "tcp:127.0.0.1:5760" "--sitl" "127.0.0.1:5501" "--map" "--console"
Copy the UDP IP address and port to use for the link.
i like mp but qgc is easier to use for my team. so thats what i teach them to use. I;ll look for the output. just suprised the link didnt show up, probably in the mavlink section but i closed out already. have a good one!
If you run the script with sim_vehicle.py --console --map, you should get an instance of MavProxy directly from WSL2 without needing to start it separately, as well.
WSL2 supports X forwarding natively now, and the MavProxy windows should just show up.