Topics created by Thomas MacNamara

Hi Vinny,

Thank you for such a detailed set of answers!

In response to your points:

We will just make a super short connector between the daughterboard and J1. I did like the elegance of a single board that snapped on and did everything we wanted but this really won't add much to the footprint. We are running 12v passive power over ethernet so we will make sure that per the docs there is a nice supply of 5v 6a for the j1 port. Yep just making sure, this will be shunted strait into a usb-to-ethernet setup (based on the rtl8153-cg chip), depending on how annoying the GPIO stuff might be we did think about simply putting a tiny powered usb hub onto the daughterboard and breaking out a usb connection in order to do those tasks (a little more effort to implement but more flexibility) Ooof that is a bit of a minefield isn't it? The BLSPs do look to be the best choice if we go with the GPIO idea. In light of this it might not be that bad an idea to go with the USB microhub idea, that way it would not be hard to implement another discreet microcontroller to deal with any realtime/gpio tasks and simply package that up into a nice neat message to pass upstream.

We will do a bit of planning and let you know where we got to.

Regards,
Thomas

That page needs to be updated. The concepts are good but that xml format is out of date. So, voxl-configure-extrinsics is likely the right approach for changing the values

We will try to get that page updated in the next day or two to be more clear

Great, thank you!

Hey @Thomas-MacNamara ,

I totally hear you... We are reeeeal close to a big docs update...... Should be dropping on the server within days and hopefully we can clear things up. Appreciate the patience and please keep providing feedback as you have issues!

-Travis

After no small amount of playing around and Googling I think I have hit the wall.

If I set them as = y then the build won't boot when deployed through fastboot if I set them as =m then they just stay as unset

# CONFIG_USB_CONFIGFS is not set # CONFIG_USB_GADGETFS is not set

I did check to see if the WIFI was running on the failed boots just incase the change was breaking ADB but it seems the build just does not like those flags.

It is so frustrating to know the hardware is there and the implementation is possible (Rasberry-pi HID is pritty dang easy).
Especially seeing as the underwater stuff is working.

The non USB solution is just to go via ethernet but that is just a lot of things being bolted on to the poor thing.

Thanks for the help though.

@Thomas-MacNamara Awesome! What a cool application!