@kestrelsystemsbp Take a look at Python MPA interface: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/tree/dev/python?ref_type=heads

It seems that a similar functionality has been shown in an experimental python branch: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/python/pympa-resize.py. Is this a recommended way to go about this (if so, how do I get these libraries and their C-bindings onto my voxl2) or is there an easier approach?

@Sam-Kiley Yeah, try dpkg --force-all -i <package-name>

@KnightHawk06 That is the source, yes.

@Eric-Katzfey

Okay, I'll keep this in mind as I develop toward offboard control. If I find any more information, I'll follow up here.

Just a side note: I don't see this behavior in real-world flight during manual or position, seems to be isolated to HITL at this point in time.

Thanks!

@Vinny

Really appreciate the in-depth response and thoughtfulness, your intuition was correct 👏

I tried to reproduce the setup from the windows PC

Wall power supply to Starling 2 (Same mains outlet) 12VAC to 5VDC to doodle labs radio Twisted D-/+ cables

Upon USB connection, I'm able to see the following on dmesg -w:

[ 1156.696173] usb 1-1: new high-speed USB device number 6 using xhci-hcd [ 1156.832876] usb 1-1: New USB device found, idVendor=0424, idProduct=9e00, bcdDevice= 3.00 [ 1156.832886] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1156.848011] smsc95xx v1.0.6 [ 1156.912009] smsc95xx 1-1:1.0 eth0: register 'smsc95xx' at usb-xhci-hcd.0.auto-1, smsc95xx USB 2.0 Ethernet, 00:30:1a:3a:eb:c8 [ 1156.981572] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1156.989474] QTI:Netlink Query to Kernel Success [ 1158.456775] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1158.464411] QTI:LINK_UP message posted [ 1158.465167] QTI:Processing LINK_UP [ 1158.465606] smsc95xx 1-1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 1158.472660] QTI:Enable mobileap [ 1158.479629] QCMAP:Enable mobileap [ 1158.598399] QCMAP:Enable mobileap done [ 1158.602320] QTI:Setup TETHERED link [ 1158.676632] QTI:LINK_UP Processed

and am able to stream data via voxl portal for a few seconds. Afterwards, the USB connection goes into a repeated disconnect/reconnect cycle.

Moving forward for next testing (and obviously final configuration), I'll power both from the same source (w/ a BEC), shorten the cables, and be sure to twist the data lines (similar to mcbl-0085)

@h3robotics I've been using v2.5 on my development machine and it works fine so v2.7 should also be fine. (Dang, I need to update 😉 )

Hi @serviceberry
I happened to stumble on your post here, sorry it looks like no one ever responded to you.
Is your HW still in error?
Can you confirm how you are powering the VOXL 2 mini, and if anything changed before this issue?
The two ICs you show that are smoking hot are interesting.
The one at 156C is the level translator for our I2C bus on the power connector.
Are you sure you have pins 1 and 2 as power, and not pins 3 & 4? If pins 3 & 4 were accidentally used to power the VOXL 2 Mini, this chip would indeed see the brunt of that issue.
The other chip heating up may just be secondary due to the other failure since that chip is downstream of this one for powering the board from the voltage impacted.
Looking forward to your response and sorry again no one responded (or did you submit a second case??)
Thanks!

Hi @SKA
Alex's instincts are correct, we do not have a smaller plug in board for just tracking in a synce'd config. We only had an M0155 for one image sensor for a while, so your best bet is what Alex said and get the new M0188 for VOXL 2 Mini (VOXL 2 uses M0173, whereas VOXL 2 Mini uses M0188)
It's quite cost competitive for what it does!!
https://www.modalai.com/collections/all/products/m0188

@astro_phil with some further investigation over the weekend, i found a small fix in the px4 codebase that seems to reduce the velocity estimation error. I low pass filtered the delta time (dt) value that is used to integrate the linear acceleration to obtain the velocity estimate.

vibration_fix.png

Left is without the "fix" and right is with the "fix". Flying in position hold.

WhatsApp Image 2025-05-03 at 15.50.57.jpeg

I tried to induce more vibration on purpose to test the impact on position tracking.
Both flights shown in the plot where done with the system shown in the picture.

@Alex-Kushleyev thank you so much. I can wait till the changes are merged and available to update directly on the voxl2.

Yes, I am using the IMX412 camera.

I can start off with whatever you have got for now and hope for a good video feed on my drone without any gimbal. As new changes come along, I will update.

I have never setup a build environment for voxl repos. I am used to building PX4 etc. with some of my custom changes. I would love to learn how to setup the build environment for the voxl repos. So if you can point me in the right direction, that would be great! I see in the docs, under "voxl SDK > custom voxl applications", there are some instructions.

Thank you!

Hi @Alex-Kushleyev @modaltb @Eric-Katzfey
I still have the same error when i use my custom board. Could you verify my board pinouts.

image (2).png

@Eric-Katzfey

From other discussion,
I add

qshell gps start -d 7 -b 115200

and get the GPS now.

Here is my setting and please let me know if any questions.
Thank you for your precious time on this matter.

AIRFRAME=MULTICOPTER
GPS=AUTODETECT
RC=CRSF_RAW
ESC=VOXL_ESC
POWER_MANAGER=VOXLPM
AIRSPEED_SENSOR=NONE
DISTANCE_SENSOR=NONE
OSD=DISABLE
DAEMON_MODE=ENABLE
SENSOR_CAL=ACTUAL
ARTIFACT_MODE=DISABLE
EXTRA_STEPS=(
qshell gps start -d 7 -b 115200
)