@YUUJI-INOUE
Glad to hear!

All the best,
ZBFT

@sansoy Can you please provide some details on your setup? What hardware are you using? Which software are you using (including versions)?

@Denver-Bennett said in How do I connect MAVROS to PX4 with UDP ports?:

voxl-vision-hub.conf

did you ever get this resolved? having same issue.
S

@Moderator Hi Modal,

Does this mean you can create a custom data file partition that you can flash using fastboot?

Yes that is correct.

We have not explored this before but it has been asked a few times. This could be very helpful for other developers.

I'm certainly hopeful that it will be helpful here at Cleo Robotics! So far with my prototyping it works as expected and cuts flashing time of some large docker images we have here at Cleo down by a noticeable fraction (no file overhead via fastboot like with ADB).

I think the snippet I posted covers the baseline functionality of getting a custom "payload" into the data partition. However if there is more I can elaborate on in terms of the toolchain / what's in the payload, and if that elaboration will be helpful to other VOXL2 developers, I would be happy to elaborate 🙂 Just let me know!

Other similar discussion points I tackled recently that I'm happy to talk about lessons of:

Flashing the system image and VOXL/CLEO SDK through a Windows Machine (journeys in USB device drivers) Building Flutter applications for uniform flashing process across all operating systems Building release bundles (i.e. a collection of partition binaries) in CI

@Aaky After that much use it could very well be ESD damage. It seems unlikely we would be able to fix via RMA.

@qubotics-admin Hi, we sell all of those components for companies to integrate into their products.

The Flir Hadron adapter (MDK-M0202-1-00) can be requested by reaching out to sales at https://modalai.com/contact

The rest of the components should be available to purchase at modalai.com

@JoonaR Hi Joona, the DP should work to drive an HDMI projector with the appropriate adapter. This adapter has been tested to work: https://www.amazon.com/Cable-Matters-48Gbps-Adapter-Supporting/dp/B08MSWMXT4?th=1

@Piyush-Singh Have you tried voxl-camera-server -d0 found here https://docs.modalai.com/voxl-camera-server/#troubleshooting ?

You cannot plug in cameras arbitrarily, you'll need to use one of the supported camera configurations: https://docs.modalai.com/voxl2-camera-configs/

@colombe-ai currently 30 business days is quoted on the website: https://www.modalai.com/products/starling-2-max

It typically should ship more quickly than that though, likely 2-3 weeks

There is no overnight shipping option as all of the drones are built to order

@colombe-ai

You can find the batteries here: https://www.modalai.com/products/m10000538
Any 2S LiIon hobby charger will work. Something like this is all you need: https://www.amazon.com/ISDT-608PD-Battery-Charger-Discharger/dp/B0CM9BFQSX

Handheld transmitter depends on the configuration of the drone. You can order the drone with a pre-bound charger ready to fly from the website.

The main debugging cable is a standard USB-C cable

@Sarika-Sharma ,

The preview width and height parameters are always in the camera config file, so if you added them, they are duplicates (and will be ignored).

Please read through this thread as it has pretty detailed explanation how to configure the correct tof sensor (old or new) for a custom configuration.

Camera-server-config-helper is indeed helpful. If you use it correctly, you should not have to manually modify the resolution in the config file.

If you still cannot get this to work, please let me know what cameras you have plugged in (and which camera ports) on your voxl 2 mini.

Alex

@Sarika-Sharma Now TOF is detected. I have choosed pmd-tof instead of pmd-tof-liow2.
But please give solution for the following problem.
When I used J7 according to the following configuration
Hardware Setup
M0104 Connector Interposer Sensor HW ID
J7 M0135 JL Tracking (M0014 ) 2
J7 M0135 JU Hires (M0025-2 ) 3
OR
J7 M0135 JL Hires (M0025-2 ) 2
J7 M0135 JU Tracking (M0014 ) 3

ONLY , The camera which is connected to JL is working either tracking or hires.
Cameras connected to JU is not working.
When i run voxl-camera-server it gives this
WARNING: cam tracking (id 1) does not seem to be alive

------ voxl-camera-server: Started 1 of 2 cameras

------ voxl-camera-server: Camera server is now running
OR
When i run voxl-camera-server it gives this
WARNING: cam hires (id 1) does not seem to be alive

------ voxl-camera-server: Started 1 of 2 cameras

------ voxl-camera-server: Camera server is now running/home/idr/Downloads/WhatsApp Image 2025-12-26 at 5.31.01 PM.jpeg

@Sarika-Sharma Kindly resolve this issue also https://forum.modalai.com/topic/4952/pmd-tof-not-detected-on-voxl2?_=1766730439331.

Hello @HsinSWT ,

When i see results like this, i would say there is probably 90% chance that the motor is bad. Unfortunately, there is a chance that the ESC is bad as well, and there is no good way to check the ESC without a known good motor (however the ESC failure is unlikely).

As I mentioned in the previous post, if you had a milli-ohm meter, you could test the motor winding resistance to confirm whether the motor is good or bad. A tool like that measures resistance with high precision (similar to a regular Ohm meter). However, if you don't have one, it may not be worth buying it..

You will not be able to measure the winding resistance of these motors correctly with a regular Ohm meter. However, you will be able to detect a complete open circuit (which could be the case, maybe worth trying). If testing resistance using a regular Ohm meter, any two connections between the 3 motor phases will read 0 ohm (or close to that). If a wire is broken, then you can detect it.

The Starling 2 motor (3000kV) has around 0.360 - 0.370 Ohm phase-to-phase winding resistance.

In order to confirm that the ESC is working properly, you could temporarily connect one of the working motors to the ESC Channel 0 and do the same spin test (using voxl-esc tools), just to confirm that the ESC Channel 0 is working fine.

In order to fix the issue, you could order a new motor and replace it yourself (will be a lot cheaper): https://www.modalai.com/products/starling-2-replacement-parts?variant=49707605393712

You could also send the whole drone back for repair (https://www.modalai.com/rma)

Alex

@Alex-Kushleyev Thanks for the help !

@Alex-Kushleyev Thanks for detailed information and analysis. I am going ahead with further testing with this ESC as per your suggestion.

I have changed my propulsion system as follows: Emax Eco II seroes 2306 2400kv motor, propeller Gemfan 5177 and 15000 mah 4S battery.

Here is my file with ESC calibration : https://drive.google.com/file/d/1uzbx9MGwF1EvRqJx6tXBqqc-j3XZSgu_/view?usp=sharing

All the motor directions are checked and they are correct as per airframe reference. My UAV is able to takeoff a bit but at around 0.5 meters it again decreases its altitude and then after scratching the surface is flipping over.

Here is the logs : https://review.px4.io/plot_app?log=08691d7d-887d-41d8-b00d-d543febeea59

Can you spot is my ESC configuration wrong or anything I am missing in PX4 configuration? This flip happened twice in a row and all motor direction are verified to be correct since UAV is able to takeoff. Also any advantage of RPM vs PWM control in VOXL ESC PX4 parameter setup?

Also my voxl2 is unpside down so I have set ROLL_180 in Autopilot orientation, but is this creating some problem anywhere is unknown since I can see yaw reset EKF2 estimator flag set as soon as I takeoff.

Hello @taiwohazeez ,

Thank you for sending updated images.

Just for sanity checking, please double check that the other tracking camera on your drone is in focus and does not have this issue.. (i assume that is true).

To me, it definitely looks likes either

damaged or dirty lens on the external lens surface damaged or dirty lens on the internal lens surface (the back surface of the lens) dirty surface of the camera sensor itself (inside the camera module)

If you are comfortable with unscrewing the lens completely and wiping it (front and back) with a new microfiber cloth (preferably long strand) and screw it back again to check if there is any improvement. Also, once you remove the lens, you can take a look at the sensor itself, any dirt or smudges should be very easy to detect because the surface of the camera sensor is very reflective and should be perfectly clean. I can't recommend cleaning the sensor itself on your own, since that would involve inserting something inside the camera module, which could lead to damage. Please dont keep the lens out of the lens holder for a long time (hours) as dust or dirt may get inside on the surface of the sensor (do not perform this procedure in a dusty environment).

Please reach out to https://www.modalai.com/pages/rma if you need further help to get this fixed / replaced.

Alex

@l05 , when in doubt, you can add a print statement in your app as a sanity check to make sure you are running the correct version of the application. Then check your print statement at run time.

If you are modifying an existing app in voxl-mpa-tools, you just need to use the voxl-cross docker image to

build the source code build the package (deb) deploy the package (either manually pushing and dpkg -i <package.deb> on target) or using a convenience script deploy_to_voxl.sh which is typically present in most voxl projects -- this script will push the deb to voxl2 and install the deb. run your new application on voxl and confirm functionality

If you are adding a new app to voxl-mpa-tools project, you will need to modify the CMakeLists.txt file in the tools folder, it should be self explanatory how to add a simple app. Once you build and deploy, your new app will be installed into /usr/bin on voxl2.

If you have any other questions, let me know.

Alex