We're sorry if that happened. Someone from operations will reach out

Hi @Brandon-Wightman
Please review this diagram, and you can see the serial port is not a functional item in "standalone dongle mode", hence why it is DNI'd.
https://docs.modalai.com/microhard-usb-carrier/#block-diagram

If you are referring to the Microhard's UART port that we label "pDDL UART" here: https://docs.modalai.com/microhard-add-on-datasheet/#bottom-of-board
that is present in either standalone or Voxl configs. You are right, we neglected to post that pinout, since you would actually be the first person in almost 4 years since we launched that product to ask for it. Please clarify if that is what you are after, and we can update our tech docs to include that pinout.
However, we do not have Software for it, so you would be trail-blazing both HW and SW efforts here if you plan to develop it on your own.

Thanks!

The Pipe API worked great! Thanks.

Can the hires camera output RBG instead of NV12 and can voxl-camera-server support that?

@Chad-Sweet what is the reason for using Gralloc allocator on apq8096 for buffer allocation instead of ION memory allocator used in the qrb5165 implementation ?

Thanks for the update. Yes, let us know when there is a pre-release.

@Raza-Rizvi That error message "voxl-mavlink-server does not appear to be running" isn't normal. You may want to run through voxl-configure-mpa again, set your host IP in voxl-vision-px4.conf, then reboot your drone.

@Chad-Sweet
Ok, thank you. I understand.

@Chad-Sweet The bad altitude reading will sometimes prevent us from arming - but it also effects the M500s in the air. During a loiter at a specified hold point, one of the M500s was bobbing up/down about ±50ft - another instance resulted in an M500 experiencing CFIT because it thought it was at an altitude higher than what it was

Fantastic, thanks for the support.

Thanks. I missed it.

Hi,

Our next VOXL2 beta release will ship with the drivers, this is slated to be available soon (within weeks) and will provide for initial testing.

I am also trying to understand this. I was able to forward the mavlink messages from voxl to the station via wifi (using voxl-wifi station), but I am not able to specify the port as it streams everything to the default port 14550. How can I specify the port to which I can send the telemetry?

@suvasis You cannot modify the code on our ESC. But you can certainly add a new driver to PX4. I would start with the PX4 documentation: https://docs.px4.io/main/en/development/development.html

Thanks for the lead! Those both include this comment:

# This is NOT a complete set of PX4 parameters. These are non-default parameters # specific to the airframe and are meant to be loaded over the defaults.

A little bit of searching turned up this reference:
https://docs.px4.io/main/en/advanced_config/parameters.html#tools

Looks like my path is to follow that guide to restore all parameters to default values, then load parameters from the files you linked to.

The drone we have shipped with a 4s battery, and ModalAI branded motors. Looks like that leaves us needing portions of each of the two parameter files. My plan is to modify RB5_Flight_V1_param_ModalAIMotors_3s_rev_A.params to include the battery configuration from RB5_Flight_V1_param_HolyBroMotors_4s_rev_A.params, and load the resulting file on top of defaults.