<div dir="ltr"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 9, 2020 at 3:40 PM Christof Arnosti via subsurface <<a href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi everybody,</p>
<p>There seems to be some general problems with Suunto dive computer
synchronisation.</p>
<p>We got reports so far from the following Suunto computers which
use some different libdivecomputer-classes (according to
<a href="https://github.com/Subsurface-divelog/subsurface/blob/master/descriptor3.tsv" target="_blank">https://github.com/Subsurface-divelog/subsurface/blob/master/descriptor3.tsv</a><tt>):</tt></p>
<p>- Suunto Zoop (uses SUUNTO_VYPER): Does not work. After
Timeout-Fix: First read returns size=0<br>
- 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.<br>
- Suunto D4i (uses SUUNTO_D9): Report of working download<br>
- Suunto Vyper Air (uses SUUNTO_VYPER2): Gets stuck on
"Connecting", might be because of unofficial cable.</p>
<p>The "sleep and purge to surpress possible echo" thing seems to be
exclusive to the suunto_vyper computers.</p>
<p>What I find interesting is that the D4 and D4i (which are using
the same driver suunto_d9) have different results. <br>
</p>
<p></p></div></blockquote><div>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.</div><div><br></div></div></div>