# "set_position_target_local_ned: coordinate frame 0 unsupported" error in QGroundControl

Source: https://forum.modalai.com/topic/5247/set_position_target_local_ned-coordinate-frame-0-unsupported-error-in-qgroundcontrol
Category: Development Drones (https://forum.modalai.com/category/44/development-drones)
Tags: starling
Posted: 2026-06-04 22:08:56 UTC by Hector Gutierrez
Replies: 5 · Views: 1059

## Hector Gutierrez · 2026-06-04 22:08:56 UTC

Hello - 
After upgrading SDK from 1.5.0 to 1.6.3, I am unable to calibrate the Starling 2 in QGroundControl  (Version 4.4.4)
Error message: "set_position_target_local_ned: coordinate frame 0 unsupported"
It seems the Starling 2 is sending a Mavlink message that is trying to set the coordinate frame to 0 (MAV_FRAME_GLOBAL), which cannot be processed by the local NED setpoint command.
Any suggestions on how to correct this error would be appreciated.
Thanks

## Reply by Eric Katzfey (ModalAI staff) · 2026-06-05 14:24:05 UTC

@Hector-Gutierrez What calibration step is not working? Are you running any custom software, like ROS or MAVSDK based applications? If you disable voxl-vision-hub does the error go away?

## Reply by Hector Gutierrez · 2026-06-05 16:11:59 UTC (in reply to Eric Katzfey)

@Eric-Katzfey : I'm not running any custom software other than voxl-vision-hub.
If I stop and disable voxl-vision-hub, the  "set_position_target_local_ned: coordinate frame 0 unsupported" error goes away !
With this I am able to complete calibration (compass and IMU) successfully in GQC, BUT drone fails to arm in Position mode **even though QGC shows "Ready to Fly" and all Sensor status show as "normal".** 
Checking VIO in VOXL Portal shows correct operation of VIO:  VIO plot follows drone motion, which seems to indicate that VIO is working fine, but 
QGC shows "Yaw estimate error" , and "--"  as altitude estimate, which prevent the drone from arming in Position mode.
Then I re-enable and restart voxl-vision-hub.
Now GQC receives altitude estimates and I'm able to arm the drone in position mode ! 
So the trick seems to be to disable/stop  voxl-vision-hub, calibrate IMU if needed, and enable/restart voxl-vision-hub, to be able to arm in Position mode.
Seems odd but I'll take it !   Let me know if you have any comments or suggestions.  Thanks.

## Reply by Eric Katzfey (ModalAI staff) · 2026-06-05 16:20:47 UTC (in reply to Hector Gutierrez)

@Hector-Gutierrez Well, I'm happy that worked, but you shouldn't have to disable voxl-vision-hub like that. I only suggested that as a debug step. We'll take a look and see if we can reproduce the error and come up with a better solution.

## Reply by ApoorvThapliyal · 2026-06-05 17:20:43 UTC

Hey @Hector-Gutierrez 
I tried recreating your issue, however I am able to calibrate the imu over QGC and then arm the drone too, while running voxl-vision-hub and voxl-open-vins-server
May I know what changes you made to `voxl-vision-hub`? Could you share your `voxl-vision-hub.conf` file too?  
Am I correct to assume that you made your changes to the voxl-vision-hub **dev** branch then installed it on the starling 2?

## Reply by Hector Gutierrez · 2026-06-05 18:09:42 UTC (in reply to ApoorvThapliyal)

@ApoorvThapliyal : the problem (Error message: "set_position_target_local_ned: coordinate frame 0 unsupported") appeared in QGC after updating VOXL SDK from 1.5.0 to 1.6.3.
The error blocked me from being able to use QGC to calibrate or arm the drone.   Stopping and restarting voxl-vision-hub solved the problem.
For now I'm using voxl-vision-hub as it comes on SDK 1.6.3 (no changes yet)  and have not made changes to the .conf file (yet).