# Requesting the factory original calibration files for ADK Ser#M2500000185 Source: https://forum.modalai.com/topic/4861/requesting-the-factory-original-calibration-files-for-adk-ser-m2500000185 Category: Flight Core and Legacy VOXL (https://forum.modalai.com/category/9/flight-core-and-legacy-voxl) Posted: 2025-11-11 01:56:46 UTC by latif Replies: 23 · Views: 11548 ## latif · 2025-11-11 01:56:46 UTC @support, like to request the following missing/corrupted calibration files (factory original) for my PX4 Autonomy Development Kit with serial number M2500000185. - voxl-imu-server.cal - opencv_tracking_intrinsics.yml ------------------------------------------------------------------ FAILED TO EXECUTE the following steps: voxl-configure-cameras 20 Encountered Problems Configuring MPA Services :-/ Some Services may not start up on next reboot Calibration File Status: **Missing /data/modalai/voxl-imu-server.cal Missing /data/modalai/opencv_tracking_intrinsics.yml** Present /data/px4/param/parameters_gyro.cal Present /data/px4/param/parameters_acc.cal Present /data/px4/param/parameters_level.cal Present /data/px4/param/parameters_mag.cal Detected Missing Calibration Files please run the required cals https://docs.modalai.com/calibration/ PLEASE POWER CYCLE YOUR VOXL ## Reply by tom (ModalAI staff) · 2025-11-11 17:32:56 UTC @latif Checking our records, it looks like the drone you're using is equipped with a C29 camera configuration: MRB-D0012-4-V2-C29-T9-M11-X0 therefore I have the following camera calibration files in our database: opencv_tracking_down_intrinsics.yml opencv_tracking_front_intrinsics.yml If C29 is not showing as an option for you, you may need to re-flash your drone with the correct kernel. Can you confirm what cameras are physically connected to your drone? If the serial number of your drone is indeed correct, in our database it is showing as a Starling 2 Max, can you upload a photo of your drone as a sanity check? ## Reply by latif · 2025-11-11 22:07:11 UTC (in reply to tom) @tom Absolutely. I'd definitely like to have the correct files, On a closer look ![ADK-serial.jpg](https://forum.modalai.com/assets/uploads/files/1762898422932-adk-serial.jpg) I probably read the S as a "5" - the serial number I think is "M250000018S" - that probably changes everything. Here's a photo of the drone: ![ADK.jpg](https://forum.modalai.com/assets/uploads/files/1762898589147-adk.jpg) You'll send me the voxl-imu-server.cal also, right? It's been flagged as missing. Thanks! I'm also attaching the packing slip so we can finalize on what the correct SKU should be. ![f0aa237d-575c-4b63-a6a7-edc1db988a2a-image.png](https://forum.modalai.com/assets/uploads/files/1762898795012-f0aa237d-575c-4b63-a6a7-edc1db988a2a-image.png) ## Reply by tom (ModalAI staff) · 2025-11-11 22:55:27 UTC (in reply to latif) @latif said in [Requesting the factory original calibration files for ADK Ser\#M2500000185](/post/24343): > M250000018S Okay great, I will send you an email with that calibration file. You'll have to re-calibrate the imu yourself. See here for instructions: https://docs.modalai.com/calibrate-imu/#step-3 ## Reply by latif · 2025-11-13 02:10:28 UTC (in reply to latif) @latif Hi @tom, thank you for sending me the yml file. Applying that I get a good healthcheck, after calibrating the imu. I do still have a problem with the cameras. I see that voxl-camera-server is not running (fails at startup). My SKU is the following, having taken the default cam config of 20: family code: MRB-D0011 (px4-autonomy-dev-kit) compute board: 4 (voxl2) hw version: 1 cam config: 20 modem config: 0 (none) tx config: 7 (elrs_beta_fpv) extras config: 0 (none) SKU: MRB-D0011-4-V1-C20-T7-M0-X0 I did see this error while running voxl-configure-mpa: FAILED TO EXECUTE: voxl-configure-cameras 20 ![f7f4529c-e469-4945-b671-54c73ebc44d6-image.png](https://forum.modalai.com/assets/uploads/files/1762999719592-f7f4529c-e469-4945-b671-54c73ebc44d6-image.png) Please advise what camera configuration to use. FYI, I did try 19, and with that it was able to run "voxl-configure-cameras 20", but the final result was the same, voxl-camera-server was not running. ## Reply by latif · 2025-11-13 14:21:33 UTC (in reply to latif) @latif I meant "voxl-configure-cameras 19"... in the post above. ## Reply by tom (ModalAI staff) · 2025-11-13 17:28:22 UTC (in reply to latif) @latif I wonder if you have the wrong kernel on there. If you run `voxl-configure-cameras` what options does it give you? ## Reply by latif · 2025-11-13 18:23:30 UTC (in reply to tom) @tom ![610cafc9-ea38-4c27-98bf-6f251b8ed816-image.png](https://forum.modalai.com/assets/uploads/files/1763058196262-610cafc9-ea38-4c27-98bf-6f251b8ed816-image.png) ## Reply by latif · 2025-11-13 18:27:16 UTC Maybe a different issue, running configure stand-alone shows this problem: ![2b918483-fbaf-4ba1-bbdc-5b74fe69d605-image.png](https://forum.modalai.com/assets/uploads/files/1763058372860-2b918483-fbaf-4ba1-bbdc-5b74fe69d605-image-resized.png) Checking space I see this: ![38c840b4-5eb5-4c4d-a59b-04306a3afeb6-image.png](https://forum.modalai.com/assets/uploads/files/1763058419509-38c840b4-5eb5-4c4d-a59b-04306a3afeb6-image.png) ## Reply by tom (ModalAI staff) · 2025-11-13 18:52:16 UTC (in reply to latif) @latif oh boy, well that is certainly an issue, can you run `sudo du -h -d 1 / 2>/dev/null | sort -h` to see which directory/partition is full? ## Reply by latif · 2025-11-13 19:55:25 UTC (in reply to tom) @tom Yeah, it's starting to look bleak! Here's the output: ![210015b2-efc8-4ece-ab9f-1e2172c7fc4e-image.png](https://forum.modalai.com/assets/uploads/files/1763063538195-210015b2-efc8-4ece-ab9f-1e2172c7fc4e-image.png) The only user data I have is under /home/root, about 1.8GB. I can free up some of it, but how do I redirect the configuration processes to use a different directory other than /usr, /lib, etc.? Also, is there a way to increase the overall storage size? I see that the biggest partition ("sda") is only 118G and now full. ## Reply by tom (ModalAI staff) · 2025-11-13 20:18:21 UTC (in reply to latif) @latif `/var` being that full is very abnormal, here is a screenshot from one of my drones: ![eb2dc6a3-842d-450d-a522-16ae3674ae9b-image.png](https://forum.modalai.com/assets/uploads/files/1763065099192-eb2dc6a3-842d-450d-a522-16ae3674ae9b-image.png) ## Reply by tom (ModalAI staff) · 2025-11-13 20:19:23 UTC (in reply to tom) @tom It's possible `/var/log/journal/` is full for some reason? You could try clearing stale logs from there ## Reply by latif · 2025-11-13 20:20:31 UTC (in reply to tom) @tom Yeah, it's starting to look dangerous. Here's the output: ![4950b4c9-6f61-46c7-aa09-87e8bf9636c4-image.png](https://forum.modalai.com/assets/uploads/files/1763063234121-4950b4c9-6f61-46c7-aa09-87e8bf9636c4-image.png) ## Reply by tom (ModalAI staff) · 2025-11-13 20:21:52 UTC (in reply to latif) @latif You should be able to go into `/var` and see what's full and deleting it ## Reply by latif · 2025-11-13 20:35:44 UTC (in reply to latif) @latif Thanks! syslog was 27G! Emptied it out and running voxl-configure-cameras again. Hopefully this will fix the other issues. ## Reply by latif · 2025-11-13 20:57:27 UTC (in reply to latif) @latif Hi @tom, cleaning up the /var/syslog file enabled the camera server to run - so the cameras are fine. I'm still not sure if all the calibrations are right, I see an error message ![38b571ca-0981-47b6-840b-b372622479ca-image.png](https://forum.modalai.com/assets/uploads/files/1763067156528-38b571ca-0981-47b6-840b-b372622479ca-image.png) when I try to bind the Commando8 Controller. Also, could never get a "READY" sign on QGroundControl. Should I run the "Sensor Calibration" options? Not knowing what that'd do, I didn't run them. If this is relevant information: I'm not getting GPS data consistently (right now getting nothing, but earlier at some point in time I did), right now I see this on QGC: ![cbaf5101-0eef-4acc-a295-5f60a218b725-image.png](https://forum.modalai.com/assets/uploads/files/1763067347746-cbaf5101-0eef-4acc-a295-5f60a218b725-image.png) ## Reply by tom (ModalAI staff) · 2025-11-13 21:17:15 UTC (in reply to latif) @latif What do you see if you run `voxl-check-calibration`? It sometimes takes a while to get a GPS lock for the first time in a new location, may have to let the drone sit outside for 5-10 minutes for the initial lock, will be much faster after that. ## Reply by latif · 2025-11-13 22:26:27 UTC (in reply to tom) @tom I'll let it sit outside for a few minutes for GPS locks. Here's the output for voxl-check-calibration: ![79b81c4c-46e8-43f4-9733-0a577fae95f1-image.png](https://forum.modalai.com/assets/uploads/files/1763072734132-79b81c4c-46e8-43f4-9733-0a577fae95f1-image.png) Still seeing things like ![ac080230-6832-4f96-8494-e5cdb4ed5928-image.png](https://forum.modalai.com/assets/uploads/files/1763072780463-ac080230-6832-4f96-8494-e5cdb4ed5928-image.png) ## Reply by tom (ModalAI staff) · 2025-11-13 23:00:32 UTC (in reply to latif) @latif You'll want to load the GPS specific px4 param file in order for "position" mode to use GPS position as opposed to VIO position. If you run `voxl-configure-px4-params -w` and navigate to `EKF2_helpers` you should be able to see the relevant options. ## Reply by latif · 2025-11-14 16:58:33 UTC (in reply to tom) @tom Now that I seem to have a good health check and the cameras working, I'd like to do the simplest possible first flight -- I went through the video directions in the Bootcamp, but wasn't able to go beyond trying to "arm" it. - I can't tell if it is binding or not. Tried the voxl-elrs -b, which seems to take it as the blue flashing lights become steady, but no movement of the propellers on trying to arm. I'm seeing a "model mismatch" message on the Commando8 Remote Controller. This shipped with the ADK and nothing has been done to it. - I need some help in flying it, indoors if that's ealier without GPS, but ultimately with GPS mission-planning, but I seem to be far from it, because I haven't done even a simple off-the-shelf type of flight. - This is my first time handling a drone of any kind, so I'm lacking some knowledge and could use some instructions to get this simple first flight job done. ## Reply by latif · 2025-11-14 16:59:18 UTC (in reply to latif) @latif ![88031482-bb56-49e6-887e-5152cc35af1e-image.png](https://forum.modalai.com/assets/uploads/files/1763139549019-88031482-bb56-49e6-887e-5152cc35af1e-image.png) ![7999568d-997f-482e-9793-7c056611fb7b-image.png](Request Entity Too Large) ## Reply by Maxwell Schaefer (ModalAI staff) · 2025-11-14 18:50:49 UTC (in reply to latif) @latif You should be able to disable the model match feature on the same screen which displayed the "Model Mismatch" error. By setting the model match id to 0, it will ignore the model match id set on the receiver and connect. The ExpressLRS documentation has more detail about how to set up the RC connection [here](https://www.expresslrs.org/software/model-config-match/#clearing-model-match-number). ![IMG_4890-min.JPG](https://forum.modalai.com/assets/uploads/files/1763146239055-img_4890-min-resized.jpg) ## Reply by latif · 2025-11-14 22:46:27 UTC (in reply to Maxwell Schaefer) @Maxwell-Schaefer Thank you! I was able to set the model match to off using the controller screen.