PX4-user_guide icon indicating copy to clipboard operation
PX4-user_guide copied to clipboard

[Discussion] Integrated companion/fc pulled out

Open hamishwillee opened this issue 2 years ago • 3 comments

@bkueng Following our discussion on "longer term having a section on integrated FC/Companion" I thought I'd have a look at what it might look like. Essentially this makes the integrated fc/companion a peer of autopilots and cross links to the companion section for the software setup.

image

  1. Is this OK/better/worth doing now.
  2. Are there any other solutions like this you know of?

I am not 100% convinced of this; after all, there are other solutions that are "advanced", like running PX4 on a companion. Also it gets complicated if we start having non-Pixhawk FCs in these things.

Another possibility is to do (something like) this:

image

ie. moving FC and FC/Companion as the top level and having peripherals etc underneath. I don't think we need to consider this right now.

hamishwillee avatar Jan 25 '23 05:01 hamishwillee

Thanks @bkueng . PX4 hasn't really "committed" to the companion software stack; my thinking was that this is not needed yet, but if I do this it might help encourage adoption? Make the hardware accessible and the software standardization will come?

Option 2 is also good, and long term better. I'll leave this open in draft and perhaps look at this again.

Are there any other solutions like this you know of?

Skynode :)

Well, it's custom PX4 build with a sandboxed proprietary container for software development. So you might argue that it isn't "PX4" at all from a development point of view. I guess this might be something you had in a "Turnkey companion solutions" section? More for marketing that PX4 is used than for actual PX4 development. Bit like the things in this list: http://docs.px4.io/main/en/complete_vehicles/#fully-assembled-custom-px4

hamishwillee avatar Jan 25 '23 23:01 hamishwillee

FYI @julianoes , just added you in case you had interest/thoughts on companion computer structuring. I'm also leaning towards "option 2" in the description.

hamishwillee avatar Jan 25 '23 23:01 hamishwillee

Well, it's custom PX4 build with a sandboxed proprietary container for software development. So you might argue that it isn't "PX4" at all from a development point of view. I guess this might be something you had in a "Turnkey companion solutions" section? More for marketing that PX4 is used than for actual PX4 development. Bit like the things in this list: http://docs.px4.io/main/en/complete_vehicles/#fully-assembled-custom-px4

You can use it with upstream PX4, and some people do. But yes the companion is currently largely proprietary.

bkueng avatar Jan 26 '23 07:01 bkueng