Re: help needed: Android devices and FTDI dive computers

Perhaps a bit late but here is the information for ab Oceanic data cable, Part # 04.9600 that I use with an Aeris Atmos AI. It operates at 9600 baud. Device Info Device Path: /dev/bus/usb/002/002 Device Class: Use class information in the Interface Descriptors (0x0) Vendor ID: 0403 Vendor Name

Re: help needed: Android devices and FTDI dive computers

> On Aug 13, 2018, at 8:19 PM, Matt Thompson wrote: > > On Sat, Aug 11, 2018 at 9:38 AM Dirk Hohndel > wrote: > > And that is up. Matt, if you aren't tired of trying by now, this might support > the i750TC over FTDI > >

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 9:38 AM Dirk Hohndel wrote: > > And that is up. Matt, if you aren't tired of trying by now, this might > support > the i750TC over FTDI > > > http://subsurface-divelog.org/downloads/test/Subsurface-mobile-4.8.1.166-arm.apk > > /D That looks like it works! I was able to

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 9:38 AM Dirk Hohndel wrote: > > > On Aug 11, 2018, at 7:14 AM, Dirk Hohndel wrote: > > > > > >> On Aug 10, 2018, at 11:08 PM, Anton Lundin wrote: > >> > >> I'd rather say that we don't have this pid listed in serial_ftdi.c > > > > You are of course correct. > > > > The

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 11:57:03AM -0700, Dirk Hohndel wrote: > > > > > > https://stackoverflow.com/a/8328814 > > > > Well, that one used hex numbers without a 0x prefix. > > > > Does it perhaps work if you do > > > > > > > > instead? Because if the number parsing is based on _anything_

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 11:19:29AM -0700, Linus Torvalds wrote: > On Sat, Aug 11, 2018 at 11:09 AM Dirk Hohndel wrote: > > > > > > Yep, I remembered correctly: > > > > https://stackoverflow.com/a/8328814 > > Well, that one used hex numbers without a 0x prefix. > > Does it perhaps work if you do

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 06:45:42PM +0200, Anton Lundin wrote: > > Meanwhile I had a 3 year old "diver" in the bathtub next to me, I > managed to get some time to dump out some data from a bunch of dive > computers: Thanks - that's super helpful. > A suunto cable from smartinterface.de : > >

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 11:09 AM Dirk Hohndel wrote: > > > Yep, I remembered correctly: > > https://stackoverflow.com/a/8328814 Well, that one used hex numbers without a 0x prefix. Does it perhaps work if you do instead? Because if the number parsing is based on _anything_ normal, then it

Re: help needed: Android devices and FTDI dive computers

On Sat, Aug 11, 2018 at 10:25:51AM -0700, Dirk Hohndel wrote: > > The fact that everywhere else we use the decimal value of VID/PID, but in > > that file we use hex really doesn't make it easier to find what could be > > wrong > > when you are searching for it. > > > > Honestly, it's the

Re: help needed: Android devices and FTDI dive computers

> On Aug 11, 2018, at 10:03 AM, Linus Torvalds > wrote: > > > > On Sat, Aug 11, 2018, 07:14 Dirk Hohndel > wrote: > > The fact that everywhere else we use the decimal value of VID/PID, but in > that file we use hex really doesn't make it easier to find what could

Re: help needed: Android devices and FTDI dive computers

On 08 August, 2018 - Dirk Hohndel wrote: > I need help from people who have both an Android device, an FTDI dive > computer / download cable, and a way to connect the two (OTG cable for > older phones - for USB C phones this tends to be simply a USB C/A adapter) > > Can you install the USB

Re: help needed: Android devices and FTDI dive computers

On 11 August, 2018 - Dirk Hohndel wrote: > > > On Aug 10, 2018, at 11:08 PM, Anton Lundin wrote: > > > > I'd rather say that we don't have this pid listed in serial_ftdi.c > > You are of course correct. > > The fact that everywhere else we use the decimal value of VID/PID, but in > that

Re: help needed: Android devices and FTDI dive computers

Thanks Thomas. The Mares family of dive computers use a Silicon Labs cable, and sadly I haven't found a user space driver for that. So with our current approach, we cannot download from those on Android. The data, however, are useful and great to have for future reference. So much appreciated.

Re: help needed: Android devices and FTDI dive computers

> On Aug 11, 2018, at 7:14 AM, Dirk Hohndel wrote: > > >> On Aug 10, 2018, at 11:08 PM, Anton Lundin wrote: >> >> I'd rather say that we don't have this pid listed in serial_ftdi.c > > You are of course correct. > > The fact that everywhere else we use the decimal value of VID/PID, but in

Re: help needed: Android devices and FTDI dive computers

> On Aug 10, 2018, at 11:08 PM, Anton Lundin wrote: > > I'd rather say that we don't have this pid listed in serial_ftdi.c You are of course correct. The fact that everywhere else we use the decimal value of VID/PID, but in that file we use hex really doesn't make it easier to find what

Re: help needed: Android devices and FTDI dive computers

On August 9, 2018 2:41:58 PM GMT+02:00, Dirk Hohndel wrote: >On Wed, Aug 08, 2018 at 11:50:21PM -0500, Matt Thompson wrote: >> Don't know why I didn't think to send this earlier with the other two >but >> here is the USB info for the Aqualung i750TC using the standard >Aqualung >> connector. >

Re: help needed: Android devices and FTDI dive computers

Hi Dirk, Connected my Mares Dive Link cable to my Sony Xperia XZ2 Compact (using a USB-C OTG cable), and the USB Device Info app said the following: Device Info Device Path: /dev/bus/usb/001/002 Device Class: Use class information in the Interface Descriptors (0x0) Vendor ID: 10c4 Vendor Name

Re: help needed: Android devices and FTDI dive computers

On Thu, Aug 09, 2018 at 10:00:48AM -0700, Dirk Hohndel wrote: > > > Oh, and I don't understand why you weren't asked to open Subsurface-mobile > > > when you plugged it in. Is there a typo in my code? Can you again send me > > > the data from USB Device Info for that cable? > > > > Device Info > >

Re: help needed: Android devices and FTDI dive computers

On Thu, Aug 09, 2018 at 08:14:00AM -0500, Matt Thompson wrote: > > > I was able to download from my D4i as well so I'm not sure what's going on > with the 750. Well, since I am on a run having you test completely untested code... here's one that's even more untested...

Re: help needed: Android devices and FTDI dive computers

On Thu, Aug 9, 2018 at 7:50 AM Dirk Hohndel wrote: > On Thu, Aug 09, 2018 at 05:41:58AM -0700, Dirk Hohndel wrote: > > > -- subsurface.log -- > > > "19.780: DCDownloadThread started for Aqualung i750TC on FTDI" > > > Starting download from ftdi > > > Finishing download thread:

Re: help needed: Android devices and FTDI dive computers

On Thu, Aug 09, 2018 at 05:41:58AM -0700, Dirk Hohndel wrote: > > -- subsurface.log -- > > "19.780: DCDownloadThread started for Aqualung i750TC on FTDI" > > Starting download from ftdi > > Finishing download thread: "Unable to open ftdi Aqualung (i750TC)" > > "19.795: Unsupported

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 08, 2018 at 11:50:21PM -0500, Matt Thompson wrote: > Don't know why I didn't think to send this earlier with the other two but > here is the USB info for the Aqualung i750TC using the standard Aqualung > connector. Nice > Device Info > Device Path: /dev/bus/usb/001/005 > Device

Re: help needed: Android devices and FTDI dive computers

Don't know why I didn't think to send this earlier with the other two but here is the USB info for the Aqualung i750TC using the standard Aqualung connector. Device Info Device Path: /dev/bus/usb/001/005 Device Class: Use class information in the Interface Descriptors (0x0) Vendor ID: 0403

Re: help needed: Android devices and FTDI dive computers

> > > And here is data from a Cobalt 2 with the standard Cobalt adapter: Device Info Device Path: /dev/bus/usb/001/003 Device Class: Diagnostics Device (0xdc) Vendor ID: 0471 Vendor Name (reported): ATOMIC AQUATICS Vendor Name (from DB): Philips (or NXP) Product ID: 0888 Product Name

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 8, 2018 at 11:41 AM Dirk Hohndel wrote: > I need help from people who have both an Android device, an FTDI dive > computer / download cable, and a way to connect the two (OTG cable for > older phones - for USB C phones this tends to be simply a USB C/A adapter) > > Can you install

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 8, 2018 at 12:07 PM Dirk Hohndel wrote: > > I believe that to be wrong. As you see in the screenshot posted here, > there's a name from a database, and a name as reported from the device. > Clearly the name "Smartinterface" is not what came from some database for > Vendor ID 0403 - as

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 8, 2018 at 11:58 AM Dirk Hohndel wrote: > > Vendor ID: 0403 > Vendor Name: FTDI > Product ID: f460 > Product Name (reported): TTL232R-3V3 I have no idea where it got the TTL232R-3V3 from. As mentioned, the names just come from some user space ID database. The kernel calls this

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 08, 2018 at 12:00:50PM -0700, Linus Torvalds wrote: > On Wed, Aug 8, 2018 at 11:50 AM Dirk Hohndel wrote: > > > > Since you have at least one of those cables, would you mind installing the > > app and sending me the output? Just so I know which information I can get > > from an

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 8, 2018 at 11:50 AM Dirk Hohndel wrote: > > Since you have at least one of those cables, would you mind installing the > app and sending me the output? Just so I know which information I can get > from an official Suunto cable? I tried to, but I have once more completely mis-placed

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 08, 2018 at 08:50:21PM +0300, Chirana Gheorghita Eugeniu Theodor wrote: > I don't think it will help bet here goes Actually, this does help a lot. It tells me that Tusa didn't modify the default information for the FTDI TTL232R-3V3 chip that they use. That's a great data point to

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 08, 2018 at 11:13:18AM -0700, Linus Torvalds wrote: > On Wed, Aug 8, 2018 at 9:32 AM Dirk Hohndel wrote: > > > > Can you install the USB Device Info app from the app store, plug in the > > FTDI cable, and send me the device info that is shown (plus any > > descriptive information

Re: help needed: Android devices and FTDI dive computers

On Wed, Aug 8, 2018 at 9:32 AM Dirk Hohndel wrote: > > Can you install the USB Device Info app from the app store, plug in the > FTDI cable, and send me the device info that is shown (plus any > descriptive information about the dive computer / download cable that you > used)? Sadly, at least

Re: help needed: Android devices and FTDI dive computers

I don't think it will help bet here goes Tusa zen iq900 Usb cable connected to galaxy s9+ Official android 8.0.0 Cable not original is a ttl232r3v3we USB Device Info Device Info Device Path: /dev/bus/usb/001/002 Device Class: Use class information in the Interface Descriptors (0x0) Vendor ID:

help needed: Android devices and FTDI dive computers

I need help from people who have both an Android device, an FTDI dive computer / download cable, and a way to connect the two (OTG cable for older phones - for USB C phones this tends to be simply a USB C/A adapter) Can you install the USB Device Info app from the app store, plug in the FTDI