Hi, Sven Knoch of divinglog.de suggested I ask here. Having upgraded my tablet to Windows 11 ARM64 (from Android) I decided to install Diving Log 6.0 to test for this years dive trip. The dive computer is Suunto Zoop (not Novo) I am using a USB interface from smartinterface.de and have loaded the latest FTDI signed ARM64 drivers. The interface shows as a serial port on COM3. The dive download fails with error ERROR: DC_STATUS_PROTOCOL after starting communication. Logfile is attached. I have downloaded the latest libdivecomputer version from the Diving Log website. The dive computer has plenty of battery life. Trying Suunto SDM3.1.0 shows some communication with the Zoop (serial number) but does not download dives. There are 46 dives present on the Zoop. I would be grateful for any help making this work. Kind regards, Stuart Burton
Stuart, The attached log file shows a successful download without any errors. Is this log file from another download attempt than the one you are reporting? To be able to help with a failure, I need to see the log file from the failed attempt. Now I can only say the log shows no problem at all. Jef On 4/10/2024 18:26, Stuart Burton wrote:
Hi,
Sven Knoch of divinglog.de suggested I ask here.
Having upgraded my tablet to Windows 11 ARM64 (from Android) I decided to install Diving Log 6.0 to test for this years dive trip.
The dive computer is Suunto Zoop (not Novo) I am using a USB interface from smartinterface.de and have loaded the latest FTDI signed ARM64 drivers. The interface shows as a serial port on COM3. The dive download fails with error ERROR: DC_STATUS_PROTOCOL after starting communication. Logfile is attached. I have downloaded the latest libdivecomputer version from the Diving Log website. The dive computer has plenty of battery life.
Trying Suunto SDM3.1.0 shows some communication with the Zoop (serial number) but does not download dives. There are 46 dives present on the Zoop.
I would be grateful for any help making this work.
Kind regards, Stuart Burton
Hi Jef, That's because I am an idiot. What an embarrassing start. The previous log file was from my Windows 10 laptop which did work. (but is far too large to take on holiday) Please find attached two log files of failures on my Windows 11 ARM64 tablet Kind regards, Stuart Burton
Stuart,
The attached log file shows a successful download without any errors. Is this log file from another download attempt than the one you are reporting? To be able to help with a failure, I need to see the log file from the failed attempt. Now I can only say the log shows no problem at all.
Jef
On 4/10/2024 18:26, Stuart Burton wrote:
Hi,
Sven Knoch of divinglog.de suggested I ask here. Having upgraded my tablet to Windows 11 ARM64 (from Android) I decided to > install Diving Log 6.0 to test for this years dive trip. The dive computer is Suunto Zoop (not Novo) I am using a USB interface from smartinterface.de and have loaded the latest > FTDI signed ARM64 drivers. The interface shows as a serial port on COM3. The dive download fails with error ERROR: DC_STATUS_PROTOCOL after starting > communication. Logfile is attached. I have downloaded the latest libdivecomputer version from the Diving Log website. The dive computer has plenty of battery life. Trying Suunto SDM3.1.0 shows some communication with the Zoop (serial number) > but does not download dives. There are 46 dives present on the Zoop. I would be grateful for any help making this work. Kind regards, Stuart Burton
It may seem naive, but just to rule out power issues,I would try to connect the dive computer and the table using a powered hub and/or different cables Il sab 5 ott 2024, 14:46 Stuart Burton <stuart@have-scope.co.uk> ha scritto:
Hi Jef,
That's because I am an idiot. What an embarrassing start.
The previous log file was from my Windows 10 laptop which did work. (but is far too large to take on holiday)
Please find attached two log files of failures on my Windows 11 ARM64 tablet
Kind regards, Stuart Burton
Stuart,
The attached log file shows a successful download without any errors. Is this log file from another download attempt than the one you are reporting? To be able to help with a failure, I need to see the log file from the failed attempt. Now I can only say the log shows no problem at all.
Jef
On 4/10/2024 18:26, Stuart Burton wrote:
Hi,
Sven Knoch of divinglog.de suggested I ask here. Having upgraded my tablet to Windows 11 ARM64 (from Android) I decided to
install Diving Log 6.0 to test for this years dive trip. The dive computer is Suunto Zoop (not Novo)
I am using a USB interface from smartinterface.de and have loaded the latest > FTDI signed ARM64 drivers. The interface shows as a serial port on COM3. The dive download fails with error ERROR: DC_STATUS_PROTOCOL after starting > communication. Logfile is attached. I have downloaded the latest libdivecomputer version from the Diving Log website. The dive computer has plenty of battery life.
Trying Suunto SDM3.1.0 shows some communication with the Zoop (serial number) > but does not download dives. There are 46 dives present on the Zoop. I would be grateful for any help making this work. Kind regards,
Stuart Burton
_______________________________________________ devel mailing list devel@libdivecomputer.org https://libdivecomputer.org/cgi-bin/mailman/listinfo/devel
Hi Giorgio, Tried but no difference, thank you. I only have the one dive computer interface so could not try an alternative. I don't really want to buy another just for testing given that it works on every device but this one. Kind regards, Stuart Burton
It may seem naive, but just to rule out power issues,I would try to connect the dive computer and the table using a powered hub and/or different cables Il sab 5 ott 2024, 14:46 Stuart Burton <stuart@have-scope.co.uk> ha scritto:
Hi Jef,
That's because I am an idiot. What an embarrassing start. The previous log file was from my Windows 10 laptop which did work. (but is far too large to take on holiday) Please find attached two log files of failures on my Windows 11 ARM64 tablet
Kind regards, Stuart Burton
Stuart,
The attached log file shows a successful download without any errors. Is this log file from another download attempt than the one you are reporting? To be able to help with a failure, I need to see the log file from the failed attempt. Now I can only say the log shows no problem at all.
Jef
On 4/10/2024 18:26, Stuart Burton wrote:
Hi,
Sven Knoch of divinglog.de suggested I ask here. Having upgraded my tablet to Windows 11 ARM64 (from Android) I decided to > install Diving Log 6.0 to test for this years dive trip. The dive computer is Suunto Zoop (not Novo) I am using a USB interface from smartinterface.de and have loaded the latest > FTDI signed ARM64 drivers. The interface shows as a serial port on COM3. The dive download fails with error ERROR: DC_STATUS_PROTOCOL after starting > communication. Logfile is attached. I have downloaded the latest libdivecomputer version from the Diving Log website. The dive computer has plenty of battery life. Trying Suunto SDM3.1.0 shows some communication with the Zoop (serial number) > but does not download dives. There are 46 dives present on the Zoop. I would be grateful for any help making this work. Kind regards, Stuart Burton
_______________________________________________ devel mailing list devel@libdivecomputer.org https://libdivecomputer.org/cgi-bin/mailman/listinfo/devel
On 5/10/2024 14:45, Stuart Burton wrote:
Please find attached two log files of failures on my Windows 11 ARM64 tablet
The first one failed with a checksum error: INFO: Read: size=33, data=93001E1D807D050001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9 ERROR: Unexpected answer checksum. [in suunto_vyper.c:370 (suunto_vyper_read_dive)] ERROR: DC_STATUS_PROTOCOL From your first successful log, we have the expected packet: INFO: Read: size=33, data=93001E1D807D010001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9 There is indeed a byte that has changed from 0x01 to 0x05. That's one bit that flipped during the transmission. In the second log, you get a packet that is too small, and contains complete garbage: INFO: Read: size=14, data=F4FEFF80C0C1CD3FFA7FFDA88DFF ERROR: Failed to receive the answer. [in suunto_vyper.c:212 (suunto_vyper_transfer)] ERROR: DC_STATUS_TIMEOUT The expected packet here was: INFO: Read: size=25, data=050016140001A21C0000000034DB569A0135160A35251344F4 Looks like a bad connection somewhere. Or maybe as Giorgio suggested your ARM tablet does not supply enough power for the PC interface? In that case using an intermediate powered USB hub might indeed help. Jef
Hi Jef, Thanks for the reply and guidance. I'll try another USB powered hub. Kind regards, Stuart Burton
On 5/10/2024 14:45, Stuart Burton wrote:
Please find attached two log files of failures on my Windows 11 ARM64 tablet
The first one failed with a checksum error:
INFO: Read: size=33, data=93001E1D807D050001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9 ERROR: Unexpected answer checksum. [in suunto_vyper.c:370 (suunto_vyper_read_dive)] ERROR: DC_STATUS_PROTOCOL
From your first successful log, we have the expected packet:
INFO: Read: size=33, data=93001E1D807D010001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9
There is indeed a byte that has changed from 0x01 to 0x05. That's one bit that flipped during the transmission.
In the second log, you get a packet that is too small, and contains complete garbage:
INFO: Read: size=14, data=F4FEFF80C0C1CD3FFA7FFDA88DFF ERROR: Failed to receive the answer. [in suunto_vyper.c:212 (suunto_vyper_transfer)] ERROR: DC_STATUS_TIMEOUT
The expected packet here was:
INFO: Read: size=25, data=050016140001A21C0000000034DB569A0135160A35251344F4
Looks like a bad connection somewhere. Or maybe as Giorgio suggested your ARM tablet does not supply enough power for the PC interface? In that case using an intermediate powered USB hub might indeed help.
Jef
Hi Jef, Thank you to both you and Giorgio. The second powered USB hub works consistently. One final request. Could you look at the attached log file and tell me if it contains records of valid dive data? Diving Log 6.0 appears to download all 46 dives but after a successful download imports 46 blank dives with no profile and the date and time of download. Subsurface downloads fine. I just want to make sure the download is OK before going back to Sven. Thanks again. Kind regards, Stuart Burton
Hi Jef,
Thanks for the reply and guidance. I'll try another USB powered hub.
Kind regards, Stuart Burton
On 5/10/2024 14:45, Stuart Burton wrote:
Please find attached two log files of failures on my Windows 11 ARM64 tablet
The first one failed with a checksum error:
INFO: Read: size=33, data=93001E1D807D050001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9 ERROR: Unexpected answer checksum. [in suunto_vyper.c:370 (suunto_vyper_read_dive)] ERROR: DC_STATUS_PROTOCOL
From your first successful log, we have the expected packet:
INFO: Read: size=33, data=93001E1D807D010001FD0000000100FF00FF00FF00FFFE00FF0001FE0000FF01B9
There is indeed a byte that has changed from 0x01 to 0x05. That's one bit that flipped during the transmission.
In the second log, you get a packet that is too small, and contains complete garbage:
INFO: Read: size=14, data=F4FEFF80C0C1CD3FFA7FFDA88DFF ERROR: Failed to receive the answer. [in suunto_vyper.c:212 (suunto_vyper_transfer)] ERROR: DC_STATUS_TIMEOUT
The expected packet here was:
INFO: Read: size=25, data=050016140001A21C0000000034DB569A0135160A35251344F4
Looks like a bad connection somewhere. Or maybe as Giorgio suggested your ARM tablet does not supply enough power for the PC interface? In that case using an intermediate powered USB hub might indeed help.
Jef
participants (3)
-
Giorgio Marzano -
Jef Driesen -
Stuart Burton