note the dekunu logo in the picture⌠whoosh noise
Warranty isnât voided, just be aware that any changes that you make yourself could affect the integrity of the device and it may act 'unusuallyâ
I had no idea we had so many âtech nerdsâ out there if anyone is keen to be even more involved in the development of the device, we are all ears
Shoot us an email support@dekunu.tech
Iâm keen to get more involved, will hit you up via email. Updated my setting to 500ft. 7 jumps today, very happy with the results.
HAH âdidnât know there are so many tech nerdsâ
I mean, we are buying smart alti, not some analog, right?
Hi,
As you know I changed mine to 1000ft. All seems to work ok. There is another thing that got my attention. I still need to test it properly. Maybe you can check if you have the same:
In my logbook on the device my exit altitude is a 1000ft lower than it should be. Can you check yours to see if it is 500 ft lower? I will make some jumps with a different setting to see if this is the case. I also noticed a difference in the log book on the device, in the cloud and even when you open the jump in the cloud. I will open a new topic about this.
I hadnât noticed, but will pay more attention tmrw.
As a developer and skydiver, it would be interesting to help you guys! Count me in!
Seems like the device logbook is 500ft lower then actual exit, even on the jumps prior to making the config change. wild guess is that the current algorithm is relying on GPS as primary for data, and baro as secondary⌠so as you get out of the plane it doesnât reliably provide data until that time, donât think it has anything to do with our tinkering.
(@bruce - attaching the dekunu robot to this post, it literally took 15 seconds in mspaint though⌠get your own robot ;-P)
Hi Andrew,
I checked it on the last jumps. Changed my setting from 1000ft to 500ft and indeed now the exit altitude on the Dekunu shows 500 ft lower. So it looks like the unit somehow uses this number. But it is already know that they will work on calculations in the unit. Hope with the next firmware these issues will be solved.