@greg_s said in Starling 2 not following navigation path:
One thing that looks suspect is the voxl-mapper pipe size 64k bytes is much smaller than expect (usually in MB, e.g. 32MB-64MB). Is this a preloaded 3D map?
Otherwise your VIO data looks good. It appears the drone does go to the 1st setpoint (1st leg of the trajectory) where that setpoint also looks as if it is landing. It's possible the landing detector was triggered and why everything stops.
I suggest the following:
power up, ssh into 2 terminals
terminal 1 -- run the voxl-mapper
terminal 2 -- run voxl-vision-hub --debug_offboard
take off in position mode, bring up the portal into mapper 3D view as normal, perform a 360 yaw to get a good map
Select "Plan a Point": draw your point and position it correctly
switch to offboard mode (which you have set correctly to 'trajectory')
Select GO!
Select "Follow Path"
(If no follow path is offered then the A* path creation failed)
Hopefully with that sequence, you'll see the drone move along the path. If it does not, then the voxl-mapper output in terminal 1 will tell us if a latency is the culprit.
As an example, here's how I expect the above to play out.. If you cannot repeat this then it maybe worth upgrading to SDK 1.6.3 (as the example was generated in).
