Using latest Firmware;
Can’t forget wireless network
Screen flashes a couple of times, but wireless network (which is still active and connected to can’t be dropped) either will not drop or instantly reconnects.
EDIT: I’m now able to disconnect from a hotspot with an iPhone. I suspect that the problem was because the device was attempting to upload a log and had got stuck doing so.
Post update - Logging functions have display issues.
LOG BOOK -> Page 1/4 empty. The second page shows some jumps but the pages
Main display shows the device is back on jump #1
The device wouldn’t sync logs to the cloud over the space of 2 hours.
The only way I could work around this was to turn the device off, turn it on, wait until one more jump had been uploaded and then repeat until the device was fully synced
More unrelated DZ are popping up in the “Change Dropzone” options - none of which are in my cloud profile or even in the same country - some of the DZ in the same country ARE there - but I never added them.
Unrelated to the firmware update;
I can’t charge the device with the supplied cable when using the silicone bumper.
I’ve had to take the bumper off at least once a day to take the device out of the red (battery) and have pulled the rubber cover (for the power button) out several times - sooner or later it’s going to get lost.
Cloud data isn’t showing a lot of data correctly - or device is not saving data correctly.
Deployment height of canopy - clearly wrong on a lot of the most recent jumps.
See image here
I’ve not noticed this issue before - however haven’t specifically checked either.
Unsure if it’s a corruption or change in the way data is uploaded \ interpreted or just general bug - but I can assure you, I’ve not been doing 9, 11 and 15k hop ‘n’ pops all day.
Hi guys, thanks for the bug reports. We are aware of a lot of the issues. Each software rollout does not fix everything but are incremental updates and fixes. Please update to v3.3.4 for additional stability https://dekunu.info/2H9JoTX
this was a wingsuit jump that i deployed at around 4k. Unit says i deployed 100 ft after exiting. Inconsistant readings when comparing heading and ground speed when comparing to plane instrumentation. Also temperatures are way off
Hey @Hollywood & @corbinhand - the plane takeoff recognition formula is a bit too sensitive. I’m working on alternate calculations at the moment. For now, just press the reset button to reboot the device.
The temp sensor will be buried inside the device, and the device also generates heat. Most notably the screen.
It’s probably to be expected that the temp readings will be slow to adjust to the outside environment and higher than they actually are.
Suggestion for the developers is to intergrate a heat conducting element into a small area of the device.
Something like a small metal lug that is exposed (but flush) to the outside airflow which in turn the heat sensor is attached or reads from.