<div dir="ltr"><div>Official Suunto Vyper Air cable gives me this:</div><div><br></div><div>[63386.597279] usb 1-2: new full-speed USB device number 18 using xhci_hcd<br>[63386.752599] usb 1-2: New USB device found, idVendor=0403, idProduct=f680<br>[63386.752606] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br>[63386.752611] usb 1-2: Product: Suunto Sports Instrument<br>[63386.752614] usb 1-2: Manufacturer: Suunto<br>[63386.752617] usb 1-2: SerialNumber: ST000001<br>[63386.756520] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected<br>[63386.756623] usb 1-2: Detected FT232BM<br>[63386.757039] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0</div><div><br></div><div>Unfortunately the cable is broken, so cannot test downloading with it.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 11, 2020 at 10:28 AM Miika Turkia <<a href="mailto:miika.turkia@gmail.com">miika.turkia@gmail.com</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 dir="auto"><div dir="ltr">Different cable, Vyper was a serial cable. I attached it using a random Chinese usb-serial adapter.</div><div dir="ltr"><br><blockquote type="cite">On 11. Mar 2020, at 6.34, Christof Arnosti <<a href="mailto:charno@charno.ch" target="_blank">charno@charno.ch</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<p>Hi Miika,</p>
<p>Just a short question: Did you use the same cable for both the D4
and the Vyper? If not, could you also send me the PID/VID of the
Vyper cable?</p>
<p>Thanks<br>
Christof<br>
</p>
<div>On 10.03.20 09:12, Miika Turkia wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Well, what do you know, everything worked with
logcat running. Both D4 and Vyper Air started downloading fine.
D4 ran all the way through. Vyper I terminated after a few dives
were loaded. Will do more testing when I have time.</div>
<div dir="ltr"><br>
<blockquote type="cite">On 10. Mar 2020, at 7.40, Miika Turkia
<a href="mailto:miika.turkia@gmail.com" target="_blank"><miika.turkia@gmail.com></a> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">I should be able to run logcat once I have
collected more test data. I just need to figure out how to
do that over wifi or BT. Have always connected with usb
cable before, but that is not an option this time :)</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">BTW I just realized that Garmin is not
supported, but it should probably be relatively easy to add.
It is mounted as a disk and we need to just point to right
mount point. Or am I missing something?</div>
<div dir="ltr"><br>
<blockquote type="cite">On 10. Mar 2020, at 6.45, Christof
Arnosti <a href="mailto:charno@charno.ch" target="_blank"><charno@charno.ch></a> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<p>Hi,</p>
<p>Thanks. The Info (idVendor / idProduct) is already in
the log you sent, so no need to download the app.<br>
</p>
<p>I want to get some (more or less) statistical data
about which usb-to-serial chipset behaves how. This is a
big help! :)</p>
<p>If you have some experience in the android world, could
you maybe try to run "adb logcat" while downloading the
dives? The logcat output might help with pinpointing the
application crash, and I think until now yours is the
only report of an actual application crash.<br>
</p>
<p>Best regards<br>
Christof</p>
<div>Am 09.03.20 um 23:39 schrieb
Miika Turkia:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 10,
2020 at 6:32 AM Christof Arnosti via subsurface
<<a href="mailto:subsurface@subsurface-divelog.org" target="_blank">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>Thanks for the more in-depth ;-) test.</p>
<p>Having a look at the serial-interface
chipset-list at <a href="http://libdivecomputer.org/drivers.html" target="_blank">http://libdivecomputer.org/drivers.html</a>
I noticed that suunto uses two different
chipsets. Maybe this could be a lead to follow
up? <br>
</p>
<p>Can the people owning a suunto computer maybe
post the Vendor ID / Product ID of their
cable, and if it works or not? The App <a href="https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator" target="_blank">https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator</a>
shows these values.<br>
</p>
</div>
</blockquote>
<div>This is what I get on dmesg when attaching the
D4 cable:</div>
<div>---8<---<br>
</div>
<div>[30804.146977] usb 1-2: new full-speed USB
device number 12 using xhci_hcd<br>
[30804.301648] usb 1-2: New USB device found,
idVendor=0403, idProduct=6001<br>
[30804.301653] usb 1-2: New USB device strings:
Mfr=1, Product=2, SerialNumber=0<br>
[30804.301657] usb 1-2: Product: USB <->
Serial Cable<br>
[30804.301660] usb 1-2: Manufacturer:
Smartinterface<br>
[30804.890118] usbcore: registered new interface
driver ftdi_sio<br>
[30804.890187] usbserial: USB Serial support
registered for FTDI USB Serial Device<br>
[30804.890504] ftdi_sio 1-2:1.0: FTDI USB Serial
Device converter detected<br>
[30804.890728] usb 1-2: Detected FT232RL<br>
[30804.891105] usb 1-2: FTDI USB Serial Device
converter now attached to ttyUSB0</div>
<div>---8<---</div>
<div><br>
</div>
<div>Downloading from D4 with this cable on Android
7.1.1, the Subsurface crashes after about 4 dives.
Do you think the OTG cable plays a part on this? I
can try the app you mention if that would be
beneficial.</div>
<div><br>
</div>
<div>miika<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</blockquote>
</div></blockquote></div></blockquote></div>