Hello,
I was looking into creating a custom frame and followed the steps in the outdate Ardusub documentation. I understand that this procedure may not translate to how it should be done for BlueOS and the Navigator board (I am using Navigator not PixHawk) so I wanted to know if there is anyway to confirm the custom frame is recognized by Ardusub and BlueOS thats on my Pi4.
I did everything through the BlueOS terminal and first i pulled the ardusub repo. Then edited the AP_Motors6DOF.cpp file through the terminal. then followed the ./waf commands as described in the ardusub doc. After setting the FRAME_CONFIG to custom and rebooting I wasn’t able to confirm if any of the changes took hold. I currently dont have all the hardware needed to test the firmware (T200 thrusters and ESC) so I wanted a way validify the software before I get my hands on those.
My custom frame is very similar to the BlueROV1 frame so I copied that code and adjusted a few lines.
Can anyone let me know if the steps I followed would actually work for my case and if not any suggestions to help? I was able to find a few discussion posts like this one asking a very similar question but most of them seemed incomplete or were specific to QGroundContorl and the PixHawk.