Fwd: Re: Subsurface-mobile downloadfrom divecomputer

[Anton Lundin]

On 14 February, 2016 - Willem Ferguson wrote:

> On 14/02/2016 22:27, Anton Lundin wrote:
> >On 14 February, 2016 - Willem Ferguson wrote:
> >
> >>On 14/02/2016 06:13, Dirk Hohndel wrote:
> >>>On Sat, Feb 13, 2016 at 08:55:27PM +0200, Willem Ferguson wrote:
> >>>>  I need to filter the above dive computer names to those with FTDI
> >>>>interfaces. In libdivecomputer the dc_descriptor_t contains a lot of
> >>>>information, for instance the transport definition. In addition there is
> >>>>dc_type that also has information. Which is the mechanism to detect
> >>>>which compuyers have an FTDI interface?
> >>>I don't think there's a way to tell from their descriptor. We may have to
> >>>white-list the ones that we know works. Manually.
> >>:-((((
> >>
> >There's not necessary any connection between usb-serial chip and
> >divecomputer. One might use a ftdi usb-to-serial with a old serial cable
> >connected to any serial dive computer.
> >
> >One manufacturer might have used ftdi chips in one generation of serial
> >cables, and silabs in another.
> >
> >
> >If there's a matching PID/VID available on the usb-bus we can use it.
> >
> Anton, thanks very much.
> 
> Is there a way in android to check for a PID? You can imagine that
> the initial step of devising communication will be immensely
> complex.

A PID is useless without the corresponding VID. We already have code
that checks for supported PID/VID's in get_usb_fd(). We would get
intents from the system if a PID/VID that we had listed in the manifest
would be connected to the device too.

I failed to parse the sentence, so please rephrase if you can.


//Anton


-- 
Anton Lundin	+46702-161604