More Mobile Software

I just recently used my Apple Watch Ultra to record a dive. I then used AWU2UDDF (a beta iphone app) to export the data from the phone into UDDF format so that I could turn around and import into DiveLog. This all worked as expected until I looked more closely at the dive time.

The Oceanic+ app was reporting a dive time of 20:30, DiveLog was showing 15:00. Visually, the depth profiles look the same but the time scales are off.

Comparing the original UDDF imported into DiveLog and a CSV version of the profile from DiveLog, I notice a couple of things. First, the number of samples is identical. Second, comparing the depth of each sample is the same (within rounding error, as DiveLog exported the depths as integer feet). What's off is the time. The CSV export from DiveLog shows the time sample interval at 2s, but the original imported UDDF does not have regular sample intervals.

It seems like an issue with the UDDF import on DiveLog -- or is it user-error? Has anyone else run into this?

Hi,

THe best way to answer your question is to have you send me the UDDF file that you got from AWU2UDDF. UDDF is a *very* complicated format and it is hard to know without seeing the data if the issue is with how the UDDF was generated or with how it was interpreted by DiveLog. Dive Log does always have fixed sample time and as a general rule we convert variable rate sample intervals to a matching fixed interval. However, this is often an area where issues can creep in (particularly with UDDF).

Please send me your UDDF file via email (support 'at' moremobilesoftware 'dot' com) and I'll take a closer look for you and see if we need to make any adjustments in Dive Log or if there is some feedback we can provide to the developer of AWU2UDDF.

Thanks,

Greg

An updated version of Dive Log (3.7) was just released to the App Store that resolves the issue with importing UDDF files generated by the AWU2UDDF application for anyone using that to fetch information from the Apple Watch Ultra.

Cheers,

Greg