Awesome video Phil! It's so cool to see content like that. There's so much we can do with regular docs and in-app tutorials. This kind of in-depth overview has the potential to really help people starting in the software. Excited to add new stuff to be covered, specially around mission-planning :D
Hey there! Thanks for the comment - I’ve actually never heard of iNav / Betaflight. Are they open source drone firmware, like ArduPilot and Px4? Please elaborate as I’d love to learn more!
@@philparisi_ Yes, they are. That's interesting you haven't heard of them because TH-cam search shows: 1.2 million results for Ardupilot 1.6 million for Betaflight 1.7 million for INAV Betaflight and INAV are brothers, both forked from Cleanflight years ago. Each being more popular than Ardupilot. :)
@@philparisi_ Hi Phil. Nice to meet you. :) I'm not sure if my reply posted the first time. Yes, they are open source autopilots. As a rough indicator of popularity, Google shows: 1.35 million results for Ardupilot 1.5 million results for Betaflight 1.7 million results for INAV So what I heard is something like "I haven't heard of McDonald's, is it kinda like Burger King?" 😀
From a quick look at their telemetry docs, iNav and Betaflight both apparently support MAVLink output, although I'm unsure whether using it requires extra configuration, and that doesn't help with getting control inputs from an operator. I looked into MSP a little bit and it's seemingly mostly used with OSD devices, although I may be misunderstanding. If you think it would be valuable to include in Cockpit then I recommend raising an Issue for it in the bluerobotics/Cockpit GitHub repository, where you can lay out the features it would provide that Cockpit doesn't currently support 🙂 It's worth noting that Cockpit is based on web technologies, and requires a translation layer for accessing serial protocols. For MAVLink that's currently provided by MAVLink2REST, running in BlueOS on the vehicle's onboard (companion) computer, although there are plans to add a MAVLink2REST (or equivalent) server to the desktop version of Cockpit in future, so it doesn't require BlueOS to connect to an autopilot. MSP support would require a similar translation, although if the protocol is quite simple then that may not be too difficult to include/provide.
Cockpit looks like a nice tool with an awesome set of features! Can't wait to test it out!
Hope enjoy it! I’m really looking forward to using it with the Blue Boat and mission planning in general.
Awesome video Phil!
It's so cool to see content like that. There's so much we can do with regular docs and in-app tutorials. This kind of in-depth overview has the potential to really help people starting in the software.
Excited to add new stuff to be covered, specially around mission-planning :D
Glad I could help get things rolling! I’m excited to see how Cockpit mission planning progresses and hope to make a similar video for the BlueBoat 🤙🏽
It would be cool if this would support INAV and Betaflight by being able to use MSP.
Hey there! Thanks for the comment - I’ve actually never heard of iNav / Betaflight. Are they open source drone firmware, like ArduPilot and Px4? Please elaborate as I’d love to learn more!
@@philparisi_
Yes, they are.
That's interesting you haven't heard of them because TH-cam search shows:
1.2 million results for Ardupilot
1.6 million for Betaflight
1.7 million for INAV
Betaflight and INAV are brothers, both forked from Cleanflight years ago. Each being more popular than Ardupilot. :)
@@philparisi_
Hi Phil. Nice to meet you. :)
I'm not sure if my reply posted the first time. Yes, they are open source autopilots. As a rough indicator of popularity, Google shows:
1.35 million results for Ardupilot
1.5 million results for Betaflight
1.7 million results for INAV
So what I heard is something like "I haven't heard of McDonald's, is it kinda like Burger King?" 😀
From a quick look at their telemetry docs, iNav and Betaflight both apparently support MAVLink output, although I'm unsure whether using it requires extra configuration, and that doesn't help with getting control inputs from an operator.
I looked into MSP a little bit and it's seemingly mostly used with OSD devices, although I may be misunderstanding. If you think it would be valuable to include in Cockpit then I recommend raising an Issue for it in the bluerobotics/Cockpit GitHub repository, where you can lay out the features it would provide that Cockpit doesn't currently support 🙂
It's worth noting that Cockpit is based on web technologies, and requires a translation layer for accessing serial protocols. For MAVLink that's currently provided by MAVLink2REST, running in BlueOS on the vehicle's onboard (companion) computer, although there are plans to add a MAVLink2REST (or equivalent) server to the desktop version of Cockpit in future, so it doesn't require BlueOS to connect to an autopilot. MSP support would require a similar translation, although if the protocol is quite simple then that may not be too difficult to include/provide.