@tom
P.S. I am currently working with the Drone Sentinel VOXL 2 and the drone is connected via LTE but without Wi-Fi, because there is no wifi dongle.

@Bernhard @James-Strawson @Zachary-Lowell-0 @Alex-Kushleyev @nuallaino

I have a brand new Starling 2 Max (received 3 days ago), and I'm having the same problem described by nuallaino and Bernhard (no GPS even when outside for a long time).

My system info and results of px4-listener are pasted below.

I did unplug the Lepton 8-pin JST SH connector as suggested by James Strawson, but that had no effect.

Everything else seems to work fine (haven't tried 5G comm yet), but I'm hesitant to fly without GPS functioning properly, so at this point I'm stuck.

Any suggestions would be most welcome.

Thanks for your help !

system-image: 1.8.02-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Mon Nov 11 22:47:44 UTC 2024 4.19.125
hw platform: M0054
mach.var: 1.0.1
voxl-suite: 1.4.1
current IP: wlan0: 10.0.0.19

voxl2:~$ px4-listener sensor_gps

TOPIC: sensor_gps
sensor_gps
timestamp: 841732144 (0.020669 seconds ago)
timestamp_sample: 0
time_utc_usec: 0
device_id: 11272245 (Type: 0xAC, SERIAL:6 (0x00))
lat: 0
lon: 0
alt: -17000
alt_ellipsoid: 0
s_variance_m_s: 999.00006
c_variance_rad: 3.14159
eph: 4294967.50000
epv: 3796926.25000
hdop: 99.99000
vdop: 99.99000
noise_per_ms: 64
jamming_indicator: 15
vel_m_s: 0.00000
vel_n_m_s: 0.00000
vel_e_m_s: 0.00000
vel_d_m_s: 0.00000
cog_rad: 0.00000
timestamp_time_relative: 0
heading: nan
heading_offset: 0.00000
heading_accuracy: 0.00000
rtcm_injection_rate: 0.00000
automatic_gain_control: 0
fix_type: 0
jamming_state: 0
spoofing_state: 1
vel_ned_valid: False
satellites_used: 0
selected_rtcm_instance: 0

voxl2:~$ px4-listener sensor_mag

TOPIC: sensor_mag
sensor_mag
timestamp: 861420482 (0.006257 seconds ago)
timestamp_sample: 861420007 (475 us before timestamp)
device_id: 527625 (Type: 0x08, I2C:1 (0x0D))
x: -0.04417
y: -0.32142
z: 0.42167
temperature: nan
error_count: 0
voxl2:~$

@Alex-Kushleyev Thanks for letting me know! I'll have to give it a try

@valvarez , the usage for the test tool is as follows:

voxl2:/$ qrb5165io-uart-test -h Description: runs hardware loopback test on specified bus Usage: qrb5165io-uart-test -d <device ID> (eg 3 for /dev/ttyHS3)

So you should run your test as:

voxl2:/$ qrb5165io-uart-test -d 2 [INFO]: success!

@antenna-eng What hardware do you have connected to the VOXL 2 board? Cameras etc.

@Kessie Excellent, glad to hear you got it working! And thanks for adding the details on what you had to do to the posting!

@Alex-Kushleyev That was it! I first tried with a lower baud rate of 250K on PX4 and I started getting the battery info. Then as you recommended, I uploaded new parameters to the ESC. I used:

python3 voxl-esc-upload-params.py --params-file ../voxl-esc-params/D0014_starling_1504_3000kv_ms_props/D0014_starling_1504_3000kv_ms_props.xml

because I will be using it on a drone of similar size and performance. Then with 2M baud rate in PX4, I was able to make it work!

Thank you.

Hello everyone,

We’ve been following this discussion with great interest — especially the insights about the mast kit and the copper shielding solution. We also tried similar approaches on our side and wanted to share our results to contribute to the thread.

We purchased four Starling 2 Max drones for our project at the beginning of the year, and like others here, we are experiencing difficulties with GPS stability outdoors. To mitigate interference, we designed and 3D-printed our own GPS mount to move the antenna away from the main body, and we added a copper shielding layer around it.

We then tested the u-blox M10 GPS outside, under clear sky conditions, with the drone powered on (connected via Wi-Fi to use VOXL-Portal). Over about 10 minutes, the best observation we captured showed 18 satellites with an average SNR around 30–35 dB.
vlcsnap-2025-07-25-14h33m43s700.png
image474.png

However, despite these results, we still cannot achieve a stable outdoor localization, which currently prevents us from flying the drones properly outside. At this point, we’re unsure whether the problem comes mainly from the GPS performance or possibly from the barometer.

We’d really appreciate:

Being included in your support list for this GPS issue, since it affects multiple units on our side (as mentioned by @Alex-Kushleyev). Any guidance or recommendations on how to debug further (extra shielding, hardware setup, barometer validation, software settings, etc.).

Thanks a lot to the ModalAI team and to the community for the shared ideas — we hope our feedback helps others as well.

Best regards,

Quentin

@Eric-Katzfey I did the systemctl stop and started service again. I guess rebooting the board earlier did not have the same effect. The compass calibration in Q is working now (no more "no mag found" error) which I guess it means the mag is working now and our gps is working too.

here is the output of voxl-p4 -d by the way:

INFO [qshell] Send cmd: 'lis3mdl start -R 10 -X -b 1' INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic INFO [muorb] [qshell] qshell gotten: lis3mdl start -R 10 -X -b 1 INFO [muorb] [qshell] arg0 = 'lis3mdl' INFO [muorb] [qshell] arg1 = 'start' INFO [muorb] [qshell] arg2 = '-R' INFO [muorb] [qshell] arg3 = '10' INFO [muorb] [qshell] arg4 = '-X' INFO [muorb] [qshell] arg5 = '-b' INFO [muorb] [qshell] arg6 = '1' INFO [muorb] [drivers__device] *** I2C Device ID 0x51e09 335369 INFO [muorb] [drivers__device] Set up I2C bus mutex for bus 1 INFO [muorb] lis3mdl #0 on I2C bus 1 INFO [muorb] (external) INFO [muorb] address 0x1E INFO [muorb] rotation 10 INFO [muorb] INFO [muorb] [qshell] Ok executing command: lis3mdl start -R 10 -X -b 1

@modalab Hello, can you help me to resolve this problem?

The kernel build is posted at https://gitlab.com/voxl-public/system-image-build/voxl-build

@DillonAllen Without WiFi, the only way you'll be able to debug VOXL related things is via. ADB so I would follow this guide: https://docs.modalai.com/setup-adb/ in order to setup ADB on your host computer.

Sorry for the late response, I've been doing some testing. so I've narrowed it down to the error lying in the stereo cameras, I connected each sensor one at a time, reconfigured, and ran the voxl-streamer and was able to get footage for the hires and tracking, but when it came to the stereo it would not work. When I would reboot the system and inspect the services I would see that the voxl-camera-server is running, but once I tried to voxl-streamer -c stereo it would get stuck at the same place and the voxl-camera-server would stop running. I've confirmed that both of my extension cables are working by testing them with the hires camera. I checked the physcial connections on the stereo cameras and there are no creases in them, they look just as they were folded with the original setup, and I believe that if any of the connections were inverted then the VOXL wouldn't even start up.

@Matt-Turi thanks so much!

@Eric-Katzfey Ok thanks for the fast answer.

@Steve-Turner voxl-build allows you to build the kernel only which you can then flash on top of an existing system. Qualcomm licenses are required in order to build a full system image.

@Huynh-Gremsy No, there is no way to do that. There is no display output

@hmlow Glad it worked! For future reference, the imx214_flip driver should be available internally from SDK 1.1 (system image 1.7) onwards. Rather than downloading from the above links, after SDK 1.1 is released the procedure will be as follows:

rm /usr/lib/camera/com.qti.sensormodule.imx214_3.bin cp /usr/share/modalai/chi-cdk/imx214-flip/com.qti.sensormodule.imx214_flip_3.bin /usr/lib/camera

@tom Thank you so much. It is done.

@tom I had the same idea, so I directly installed Mavproxy and related packages on VOXL2, and successfully resolved the issue with the serial library. However, when running the service, I still couldn't import the Python files related to Mavproxy. Even adding the paths of those Python files to the environment variables didn't solve the problem.