Hi Linus. That’s good advice, it was quite slow to compile in place but I had plenty of other things to get on with while it was chugging away (such as sleep). As I’m currently inflicted with a Mac, so doing things that are simple in linux are never as easy as they should be. That’s why I ignored your suggestion and compiled in place. I don’t remember exact process I followed, but it was easy; looked at the waf script, frob frob frob, nice new
build/blue/bin/ardurover binary that runs with sudo.
Rover build is stalled waiting for a bits and pieces to arrive in the mail, but I already like the lack of wires and onboard battery management; very convenient “on the bench”. First iteration of rover will have minimal components; bbblue, gps, DSM2 RX, power and actuators. I’ll use wifi for telemetry (don’t need range or reliability, this thing has a top speed of about 1.5 m/s). It’s very tidy.
The DSM-only RC input is slightly annoying, ideally i’d like PPM so I can have two transmitters/receivers in the rover with a PPM encoder (current 3 channel ground vehicle transmitter for the driver + copilot tx with knobs and switches for his dad). But I’ll deal with that using a RX and PPM encoder on copilot TX buddy box input. It just means both TX will need to be present for my son to drive it, whereas in simple RC configuration he currently enjoys driving it around on his own sometimes. I suppose I could probably figure something out with some of the ADCs on the BBBlue, or maybe just convert him to a TX with sticks.
My next step will be to setup mavproxy and an init.d script (or however we do that these days) so it boots into “ready for business”. I have never done ardupilot on linux and have a silly noob question - how do I start the program and connect it to mavproxy?