Suunto Eon 16/19 dives

[Linus Torvalds]

On Wed, May 20, 2015 at 11:10 AM, Robert C. Helling <helling at atdotde.de> wrote:
>
> I don’t know what happened there but he actually sent it twice and this
> version looks complete to me

Yup, that looks better. Now I see it actually downloading all the dives too.

And it definitely looks up all 20 dives, but then we have this:

ERROR: incomplete read interrupt transfer [in suunto_eonsteel.c:139
(receive_data)]
ERROR: short command reply (-1) [in suunto_eonsteel.c:243 (send_receive)]
ERROR: unable to read 0:/dives/554F62F5.LOG [in suunto_eonsteel.c:321
(read_file)]

ERROR: incomplete read interrupt transfer [in suunto_eonsteel.c:139
(receive_data)]
ERROR: short command reply (-1) [in suunto_eonsteel.c:243 (send_receive)]
ERROR: unable to read 0:/dives/554E0B95.LOG [in suunto_eonsteel.c:321
(read_file)]

ERROR: incomplete read interrupt transfer [in suunto_eonsteel.c:139
(receive_data)]
ERROR: short command reply (-1) [in suunto_eonsteel.c:243 (send_receive)]
ERROR: unable to read 0:/dives/5548D05C.LOG [in suunto_eonsteel.c:321
(read_file)]

which ends up breaking three of them, giving us 17 dives.

And that's the right number: your "16/19 dives" is for the dive trip,
the screenshot clearly shows 17 dives, it's just that the first one is
the (presumably uninteresting to Guenther) first test-dive, not from
the dive trip.

I'll try to figure out *why* those three dives fail to download. I
suspect it's some issue where the length of the dive is just right to
cause a packetization case that I don't handle right. I'll have to
analyze those three cases more closely.

But I probably won't get to that until this evening. But the debug
data looks good and sufficient,

               Linus