erreur d'importation

[jean-yves coppin]

bonjour,


je rencontre ce problème sur mon Galileo Sol full de chez UWATEC depuis le changement de version 4.8.3.

j'ai mème essayé de revenir sur l'ancienne version rien a faire

subsurface ne veut plus m’importer mais plongée

il n'y a pas eu enregistrement de fichier subsurface.bin

j’espère que vous trouverez le problème


cordialement,

jean-yves

[Loading Image...]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Garanti sans virus. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

[Linus Torvalds]

subsurface ne veut plus m’importer mais plongée

My french is non-existent (two years of French in highschool), but google helps.

The problem is that your dive computer claims that it has 234226 bytes
of data to transfer:

INFO: Write: size=9, data=C60000000010270000
INFO: Read: size=4, data=EE920300
INFO: Write: size=9, data=C40000000010270000
INFO: Read: size=4, data=F2920300

the above is us asking for the data size (the C6 packet write) getting
back "0x000392ee" (it that 234226 length) followed by us actually
asking for the data itself (the C4 packet), getting back first the
full data size (4 bytes of length plus the expected size: 0x000392f2),
and then we get the data itself:

INFO: Read: size=32,
data=A5A55A5ACA050000D490A13B0000BA00040100060002600682031F00A0008C00
INFO: Read: size=32,
data=DD0000000000000000000000150000000000283F00000000ED5F000000000300
...

but we actually only get 2514 bytes, and then the read fails:

INFO: Available: value=0
INFO: Read: size=0, data=

and libdivecomputer gives up:

ERROR: Failed to receive the data packet. [in
/data/src/win/subsurface/libdivecomputer/src/uwatec_smart.c:137
(uwatec_smart_irda_receive)]
ERROR: Failed to receive the answer. [in
/data/src/win/subsurface/libdivecomputer/src/uwatec_smart.c:611
(uwatec_smart_device_dump)]

but the logs do say that communication *starts*, and seems to be
working, it just doesn't get the expected amount of data.

It sounds like it might just be a temporary communication issue and it
might be worth just trying again a few times.

Linus

[Thiago Macieira]

Post by jean-yves coppin
bonjour,
je rencontre ce problème sur mon Galileo Sol full de chez UWATEC depuis le
changement de version 4.8.3.

Inline translation:

I am facing this problem on my Galileo Sol Full from UWATEC after the change
of version (upgraded, I guess) 4.8.3

Post by jean-yves coppin
j'ai mème essayé de revenir sur l'ancienne version rien a faire

I have even tried to go back to the old version -- nothing happened.

Post by jean-yves coppin
subsurface ne veut plus m’importer mais plongée

Subsurface does not want to import my dives any more.

Post by jean-yves coppin
il n'y a pas eu enregistrement de fichier subsurface.bin

There haven't been any modifications to the file subsurface.bin.

Post by jean-yves coppin
j’espère que vous trouverez le problème

I hope you'll find this problem.

[Willem Ferguson]

Post by Thiago Macieira

Post by jean-yves coppin
bonjour,
je rencontre ce problÚme sur mon Galileo Sol full de chez UWATEC depuis le
changement de version 4.8.3.

I am facing this problem on my Galileo Sol Full from UWATEC after the change
of version (upgraded, I guess) 4.8.3

Post by jean-yves coppin
j'ai mÚme essayé de revenir sur l'ancienne version rien a faire

I have even tried to go back to the old version -- nothing happened.

Post by jean-yves coppin
subsurface ne veut plus m’importer mais plongée

Subsurface does not want to import my dives any more.

Post by jean-yves coppin
il n'y a pas eu enregistrement de fichier subsurface.bin

There haven't been any modifications to the file subsurface.bin.

Post by jean-yves coppin
j’espÚre que vous trouverez le problÚme

I hope you'll find this problem.

J'espÚre que Jean-Yves rÚpond á cette correspondence, d'autant plus le
message de Linus il y a deux jours.

J'ai un Uwatec Galileo Trimix et je n'ai pas cette erreur: m'importation
est parfaite utilisant 4.8.3. Peut-être cette problÚme est locale sur
l'ordinateur de Jean-Yves?

Cordialement,

willem