I have been having the same issue. Curiously, on days with really nice weather and no wind, my One registers landings almost immediately. When it’s a windy day, every jump takes a few minutes (or sometimes doesn’t) to register. I try to stand in one spot as long as possible, but obviously it can’t be helped if you need to head back into the hangar for stuff…
Me, three! 1st 5 jumps on it I was still “at 20-30 feet and did not land until a few minutes later” the last jump it showed me at 200 feet at touchdown. It recorded a two hour canopy ride, which included the drive home.
I get this on every jump with my device.
from one of the DZ’s I jump at I have notices the PLA isnt flat or level,
I can only assume that this is due to a GPS’s inability to distinguish altitude at such a low static level, unlike free-fall while the devices relevant position in 3D space is continuously altering.
While in a static location on the PLA after a jump, the device isn’t moving through measurable variations like free-fall or canopy ride.
this is my thoughts on it, but I may be way off.
I think its like a number of the measurable parameters on the device, once they have been flagged and Panelized , the algorithms for the parameter of measurements can be refined.
looking at the post analysis of each jump on the maps, the device is accurate, and will become more so with the data as long as we flag the errors up as we go.
Jup, Same here. Tried my new One for the first time today. It was in Canopy Mode and still „moving“ in different speeds, while actually laying right next to my stuff (which is where I activated it prior to the First jump). This happened on both of my two jumps today.
Hey guys, a fix for this bug is on its way, currently testing the firmware before we roll it out.
This bug is not affecting the integrity of the altimeter during plane/freefall/canopy modes - if you think this is not the case with your device please report to email@example.com as soon as possible so it can be investigated.
Thanks for feeding back!