@tom Filepath noted, and fortunately we did just update to 0.9.5 SDK. Files received! Thank you.

@tom said in Request for OpenCV calibration YAMLs:

the sticker is likely on the outside of the 3d printed enclosure of the dr

Awesome! Thanks @tom. I saw the small white stickers but wasn't sure since there are additional stickers located inside of the enclosure with different values. The value for the one on the outside of the enclosure is M2100000CUH. I did notice a conflict on the aforementioned page with conflicting file paths for where to drop the files. Should they all just be dropped in a single directory?

Hi @Chad-Sweet, thanks for the response. I did not explicitly, but I assumed /data was wiped when flashing the device (since they are supposed to be backed up prior to flashing). The device in question was stuck in fastboot, so I had no option. I just realized the other two device's files should still be sitting in /data.

I saw various locations mentioned on this page =https://docs.modalai.com/Qualcomm-Flight-RB5-system-image/ (namely: /etc/modalai, /data/misc, /data/modalai).

Where can I locate the serial number (for the device in question, that was flashed without backup)?

Hi @tom, any chance to acquire these camera cal files directly from ModalAI, or should I just proceed with the manual calibration?

Hello,

I saw a video suggesting that copies of the camera calibration files are typically maintained, and may be requested by posting the device's serial number in this forum.

Please let me know specifically where to locate the identifying information on the device if you are able to assist. I need the files for one device, but would like the files for all three of the devices in my possession if possible.

Devices: (3x) Qualcomm RB5 Flight dev drone.

Thanks.

Fantastic, thanks for the support.

Awesome! Thanks Tom, that worked. Just for my awareness, how did you know which SDK maps to which specific tag (SDK 0.9.5 -> v0.7.6 tag)?

Hello,

I'm building out voxl-mpa-tools from source. I'm interested in voxl-inspect-gps. The app that is installed on the device's stock build runs/outputs as expected, but the one that I am building from source (without any modifications) gets hung with the following output: waiting for Autopilot /run/mpa/mavlink_gps_raw_int/. There are no errors/warning from CMake, and I am following the READMEs verbatim.

I assumed after cloning voxl-mpa-tools and voxl-docker that I would be able to just run the build and deploy the working app(s). Any hints as to why this might not be working as anticipated?

• Device version of voxl-suite: 0.9.5
• I've tried the latest dev branch of voxl-mpa-tools (v1.0.1) and v0.9.5.
• I've tried using voxl-cross V2.5 and V2.4 to build.
• Host = Ubuntu 18.04.6 LTS
• Device = Qualcomm Flight RB5

I haven't troubleshot much farther than pipe_client_open (247, voxl-inspect-gps.c).
Just wanted to sanity check here first before going down a rabbit hole.

Thanks!