Hi all, I’m having issues with first time setup, and can’t figure out what my next steps are.
BlueOS, currently running master updated 5 hours ago. Running on a Pi3b.
Autopilot is a Holybro Kakute H743-wing with Ardusub 4.5.7 flashed through mission planner. Bootloader was also updated through mission planner.
In the vehicle configuration wizard it fails to load scripts and fails to load parameters. If I try to install firmware, I can correctly set the board and vehicle type, but after searching for a minute, it says “no data available” in the firmware drop-down.
If I download the firmware from Ardupilot and try to upload the firmware file, I get an error saying “could not load firmware file for validation”.
Am I doing something wrong somewhere, or is it not possible to use the Kakute H7 FC?
I should also mention that I tried following what was listed here ( H743 wlite compatability ) but after decompressing the file for a few minutes, it just resets back to the version chooser page.
You can try Willian’s all_boards_for_real_this_time docker image - that’s the current latest progress on broader serial board support (he’s been alternating updates between that and the original all_boards image).
I would note that I’m unsure whether the Kakute H7 has been used for ArduSub before, so it’s possible there are some common features not included in the default build flags, or some configuration related issues we’re not aware of. Let us know if you run into any issues!
I’ve been playing with this setup for a few days now and still don’t think I’m doing things right.
I got the all_boards_for_real_this_time and now it shows the autopilot version which it didn’t before. It also allows for installing other firmwares to the autopilot.
Going through the setup wizard in BlueOS it still cannot find the scripts or parameters for the board and I think (from looking at other screenshots online) that I’m missing options in the vehicle setup tab.
I also tried a Matek F405 Wing FC and a Speedybee F405 Wing Mini FC with it and seem to get the same results.
I was originally interested in trying to use these flight controllers I had laying around, but now I’m thinking about swapping the the Navigator. I’ll keep researching and see what else I can come up with.
The firmware has default parameters built into it for a minimal setup, but we apply some additional defaults for Blue Robotics vehicles because we have more expectations about what is connected to it and where. Those extra things are what the BlueOS wizard are looking for, so if you’re not using a standard Blue Robotics vehicle it’s expected that there won’t be any relevant scripts to download or extra parameters to apply.
The available pages are documented, but understandably newer versions of the software introduce new features (so some may be missing if you’re on an old BlueOS version), and not every feature is available (or well-tested / supported) on every flight controller board.
I would expect the sensor calibrations and the like to work fine, but some of the output configuration functionality may be limited or incorrect if your board isn’t similar to a Pixhawk or Navigator. If that’s the case, please let us know, so we can try to improve support for the hardware you’re using!
If you share which BlueOS version you’re using and which pages you’re seeing we can try to confirm whether that’s expected (although probably not until the new year - we’re on holidays, and that doesn’t seem super fun to check )
So, it turns out I just don’t have any idea what I’m doing. Haha.
I saw that you were on holidays so I didn’t expect a reply right away. I started to figure out that there might not be pre built scripts and parameters after I had written that last message, but was playing a bit more before replying again.
I’m at work today and am writing this quickly, so hopefully it makes sense.
I installed the rpi3b version of BlueOS onto the SD card, then updated through the chooser. I then switched to the newest build of the all_boards_for_real_this_time and it looks like it’smostly working.
All the gyro/accel data appears to be working and I can calibrate it. I have a GPS/compass module that is working (I’m aware GPS won’t work underwater). BMP280 built in to the FC also shows air pressure and temp. The camera tilt servo is working and will keep the cam level when I move the electronics tray. My bar30 wasn’t automatically detected when I plugged it in to the i2c port, but I haven’t done any troubleshooting with it yet. I’ll get to it sometime in the next few days.
)