Support for Scubapro Aladin Sport Matrix

[William Wilson]

Can anyone verify if the Scubapro/Uwatec Aladin Sport Matrix is supported?  I see tons of other Aladin models, but not that one.

Thanks, 

Trace Wilson

[Dirk Hohndel]

Suport for the Aladin Sport Matrix is in the latest test builds for Subsurface and we are right now working to try to get it supported in Subsurface-mobile as well.

The current release versions do not support the Sport Matrix, yet.

/D

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/44a2fe49-2cdc-438e-bdb4-a04458164573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[William Wilson]

On Monday, November 27, 2017 at 5:09:57 PM UTC-5, Dirk wrote:

Suport for the Aladin Sport Matrix is in the latest test builds for Subsurface and we are right now working to try to get it supported in Subsurface-mobile as well.

The current release versions do not support the Sport Matrix, yet.

/D

Any ETA on when we hope the Matrix work will be complete?

Trace

[Dirk Hohndel]

I repeat, it's already in the test builds of Subsurface:

The purpose of those builds is so that people with the actual hardware can TEST that things work as expect. Otherwise we might release the functionality and you find out that it doesn't work.

Which OS are you on, so I can point you to the correct binary?

/D

[William Wilson]

Dirk, 

Finally got the Sport Matrix, and seeing the following error when attempting to D/L from it:

 Subsurface: v4.7.7, built with libdivecomputer v0.7.0-devel-Subsurface-branch (8cf5209d318170d88a4b257d48dae1635d2eda53)

ERROR: Unknown USB ID for Scubapro model 0x17 [in /data/src/win/subsurface/libdivecomputer/src/scubapro_g2.c:247 (scubapro_g2_device_open)]

What does currently work is D/L the dive info via my phone into Subsurface-mobile, then syncing to the cloud.

If you could point me to the test binaries, I'll be happy to try them out on my Win10 desktop.

Thanks, 

Trace

[Miika Turkia]

You should find the test builds from:
https://github.com/Subsurface-divelog/subsurface/releases

[Linus Torvalds]

On Tue, Feb 27, 2018 at 6:41 PM, William Wilson <dm99...@gmail.com> wrote:
>
> Finally got the Sport Matrix, and seeing the following error when attempting
> to D/L from it:
>
> Subsurface: v4.7.7, built with libdivecomputer
> v0.7.0-devel-Subsurface-branch (8cf5209d318170d88a4b257d48dae1635d2eda53)
> ERROR: Unknown USB ID for Scubapro model 0x17 [in
> /data/src/win/subsurface/libdivecomputer/src/scubapro_g2.c:247
> (scubapro_g2_device_open)]

Ok, we don't have model 0x17 (ALADINSPORTMATRIX) covered.

We have

{ G2, 0x2e6c, 0x3201 }, // Scubapro G2
{ ALADINSQUARE, 0xc251, 0x2006 }, // Scubapro
Aladin Square

but not the USB ID's for ALADINSPORTMATRIX.

Can you do an lsusb to figure out what the USB vendor and device ID's
are for your Sport Matrix?

I don't know what OS you're using, and what the equivalent of "lsusb"
is on Windows or OS X.

Oh, some googling shows that it's "ioreg -p IOUSB" on OS X. And I
guess you can see it in the device manager on Windows.

Linus

[Linus Torvalds]

On Wed, Feb 28, 2018 at 11:32 AM, Linus Torvalds
<torv...@linux-foundation.org> wrote:
>
> Ok, we don't have model 0x17 (ALADINSPORTMATRIX) covered.

If Jef's code works on USB, that would imply that it's using the exact
same ID as the Scubapro G2. Odd, but possible, of course.

It's nasty that we have to have that USB ID mapping, I wonder if it
would be doable some other way.

Linus

[William Wilson]

On Wednesday, February 28, 2018 at 2:32:13 PM UTC-5, Linus Torvalds wrote:

Ok, we don't have model 0x17 (ALADINSPORTMATRIX) covered.

We have

                { G2,           0x2e6c, 0x3201 },       // Scubapro G2
                { ALADINSQUARE, 0xc251, 0x2006 },       // Scubapro
Aladin Square

but not the USB ID's for ALADINSPORTMATRIX.

Can you do an lsusb to figure out what the USB vendor and device ID's
are for your Sport Matrix?

I don't know what OS you're using, and what the equivalent of "lsusb"
is on Windows or OS X.

Oh, some googling shows that it's "ioreg -p IOUSB" on OS X. And I
guess you can see it in the device manager on Windows.

              Linus

Linus, 

This dive computer connects via Bluetooth LE.  My Windows 10 desktop did not have BT builtin, so I acquired a USB dongle.  The dive computer has successfully paired with the desktop, and Scubapro's LogTrak is able to see and D/L info from it.

In Subsurface, however, when in Import > Import from dive computer,when I check "Choose Bluetooth download mode", Bluetooth mode is Auto, but a Scan returns "Device discovery error: The Bluetooth adapter is powered off, power it on before doing discovery."

Regarding the device ids, I found on Windows there is a command line tool that comes with the WDK, named DevCon.exe.  When listing the USB ids on my machine, I didn't see anything that looked like it was the dive computer related, which makes sense (to me) since it's connecting via BLE.  When listing Bluetooth devices, I do see my dive computer, but I'm not sure how to interpret the device information: 

BTHLE\DEV_001343359EDC\7&CE5A0A3&0&001343359EDC

    Name: Aladin Sport - Trace

    Hardware IDs:

        BTHLE\Dev_001343359edc

    Compatible IDs:

        BTHLE\GenericDevice

BTHLE\DEV_0013433ABCCF\7&CE5A0A3&0&0013433ABCCF

    Name: Aladin Sport

    Hardware IDs:

        BTHLE\Dev_0013433abccf

    Compatible IDs:

        BTHLE\GenericDevice

(The second entry is for my wife's dive computer)

I also found another couple of device entries that look related: 

BTHLEDEVICE\{0000180A-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_001343359EDC\8&2291BCB0&2&0010

    Name: Device Information Service

    Hardware IDs:

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{0000180F-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_001343359EDC\8&2291BCB0&2&0021

    Name: Bluetooth LE Generic Attribute Service

    Hardware IDs:

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{FDCDEAAA-295D-470E-BF15-04217B7AA0A0}_DEV_VID&01024A_PID&0000_REV&0000_001343359EDC\8&2291BCB0&2&0035

    Name: Bluetooth LE Generic Attribute Service

    Hardware IDs:

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{00001800-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_001343359EDC\8&2291BCB0&2&0001

    Name: Generic Access Profile

    Hardware IDs:

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{00001801-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_001343359EDC\8&2291BCB0&2&000C

    Name: Generic Attribute Profile

    Hardware IDs:

        BTHLEDevice\{00001801-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{00001801-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{00001801-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{00001801-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{0000181A-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_0013433ABCCF\8&1F104B8A&2&0025

    Name: Bluetooth LE Generic Attribute Service

    Hardware IDs:

        BTHLEDevice\{0000181a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{0000181a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{0000181a-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{0000181a-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{0000180A-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_0013433ABCCF\8&1F104B8A&2&0010

    Name: Device Information Service

    Hardware IDs:

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{0000180a-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{0000180F-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_0013433ABCCF\8&1F104B8A&2&0021

    Name: Bluetooth LE Generic Attribute Service

    Hardware IDs:

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{0000180f-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{FDCDEAAA-295D-470E-BF15-04217B7AA0A0}_DEV_VID&01024A_PID&0000_REV&0000_0013433ABCCF\8&1F104B8A&2&0035

    Name: Bluetooth LE Generic Attribute Service

    Hardware IDs:

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{fdcdeaaa-295d-470e-bf15-04217b7aa0a0}

        BTHLEDevice\GenericATTService

BTHLEDEVICE\{00001800-0000-1000-8000-00805F9B34FB}_DEV_VID&01024A_PID&0000_REV&0000_0013433ABCCF\8&1F104B8A&2&0001

    Name: Generic Access Profile

    Hardware IDs:

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000_REV&0000

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_Dev_VID&01024a_PID&0000

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

    Compatible IDs:

        BTHLEDevice\{00001800-0000-1000-8000-00805f9b34fb}

        BTHLEDevice\GenericATTService

Hopefully this info is helpful, but if not, I'll try to gather any other info that may be helpful.

Thanks in advance!!

Trace Wilson

[Linus Torvalds]

On Wed, Feb 28, 2018 at 12:58 PM, William Wilson <dm99...@gmail.com> wrote:
>
> This dive computer connects via Bluetooth LE.

Oh, if you connect over BLE, then you should never get to that error
in the first place.

So if you get that

ERROR: Unknown USB ID for Scubapro model 0x17

then the BT path wasn't even triggered in the first place.

So does the Aladin Sport Matrix have no USB at all? How do you charge
it? Is it a replaceable battery?

> My Windows 10 desktop did not
> have BT builtin, so I acquired a USB dongle.

Ahh. Windows. Sadly, BLE doesn't work at all on Subsurface under Windows.

So if the dive computer is BLE only, then you're stuck with just the
mobile app downloading. You can obviously sync to the Windows machine
afterwards over the cloud, but right now the direct download will
simply not work.

Linus

[William Wilson]

Yes, this one connects BLE only, no USB port, replaceable battery.  Bummer about  the BLE on Windows.  Is that in the plans, or never gunna happen?

Upside, the D/L via mobile + Sync to desktop is working well, just a little cumbersome.

Thanks again, 

Trace

[Linus Torvalds]

On Wed, Feb 28, 2018 at 1:14 PM, William Wilson <dm99...@gmail.com> wrote:
>
> Yes, this one connects BLE only, no USB port, replaceable battery. Bummer
> about the BLE on Windows. Is that in the plans, or never gunna happen?

Qt - the cross-platform library we use - doesn't support BLE on Windows.

The moment it does, we'll support it too, but in the meantime we're
kind of stuck.

> Upside, the D/L via mobile + Sync to desktop is working well, just a little
> cumbersome.

Yeah, understood.

Linus

[Ran Maggs]

For the sake of completeness, I can confirm that the Matrix connects to Subsurface 4.8.5 on Windows 10 via Bluetooth by selecting Aladin Sport Matrix.