On Mon, Mar 9, 2020 at 3:40 PM Christof Arnosti via subsurface < subsurface@subsurface-divelog.org> wrote:
> Hi everybody, > > There seems to be some general problems with Suunto dive computer > synchronisation. > > We got reports so far from the following Suunto computers which use some > different libdivecomputer-classes (according to > https://github.com/Subsurface-divelog/subsurface/blob/master/descriptor3.tsv > ): > > - Suunto Zoop (uses SUUNTO_VYPER): Does not work. After Timeout-Fix: First > read returns size=0 > - Suunto D4 (uses SUUNTO_D9): App (or Download?) Crashes after about 4 > downloaded drives. There should be a mail with logs in the support mail > address. > - Suunto D4i (uses SUUNTO_D9): Report of working download > - Suunto Vyper Air (uses SUUNTO_VYPER2): Gets stuck on "Connecting", might > be because of unofficial cable. > > The "sleep and purge to surpress possible echo" thing seems to be > exclusive to the suunto_vyper computers. > > What I find interesting is that the D4 and D4i (which are using the same > driver suunto_d9) have different results. > > For my first round of testing with the D4i, I didn't have any new dives so I was tecnically only reporting that the communication was successful. I did a force download of all dives on my D4i and was able to successfully download ~150 dives. I didn't check profiles but the dates and times looked reasonable.
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface