Re: Troubles with SmartTrak log import

[Robert Helling]

HI,

> On 9. Aug 2018, at 22:45, Franck TACHOUERES  
> wrote:
> 
> I definitely opted for Subsurface which I find admirable.
> Open source project very active and free, independent of computer 
> manufacturers friendly UI: what more could you ask for!
> It was for the compliments you deserve ;-)
> 
> I just tried (in version 4.8.1) the import of Scubapro SmartTrak logs.
> With the executable program on Windows or the webservice I get the same 
> result: no output file.
> In addition, I did not find a log nor any error message.
> 
> I'm attaching my SmartTrak newspaper (aladin prime) if you can help.
> 
> Maybe the log is too big (more than 400 dives)?

I tried to run the converter on the command line. For some reason it dies. Have 
to investigate this further.

BEst
Robert


signature.asc
Description: Message signed with OpenPGP
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Cross-compile for RPi

[Robert Helling]

Hi,

> On 9. Aug 2018, at 18:27, Robert Helling  wrote:
> 
> Right now, I have to run. The next thing to try will be to start with a more 
> recent Debian stretch.

success! I started from a fresh stretch image. Had some problems with the 
required debian packages (as listed in the INSTALL file), some were 
non-existent, some I had to install manually for whatever reason. But then it 
built (taking forever). I had to comment out some GL functions from 
subsurface-desktop-main.cpp as the linker had problems but those affect only 
the GL version determination. I ended up with a working Subsurface built 
natively on RaspberryPi (including google maps).

The mentioned problems are not of my concern as my application would be a 
headless command line version of Subsurface anyway.

Best
Robert


signature.asc
Description: Message signed with OpenPGP
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: help needed: Android devices and FTDI dive computers

[Dirk Hohndel]

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
> > Device Path: /dev/bus/usb/001/002
> > Device Class: Use class information in the Interface Descriptors (0x0)
> > Vendor ID:  0403
> > Vendor Name (reported):  FTDI
> > Vendor Name (from DB):  Future Technology Devices International, Ltd
> > Product ID:  6015
> 
> So that's 1027/24597
> 
> +
> 
> Which is why I don't understand why the page didn't open...

I looked through your log again. You were running .161 which should have
exactly that line in it's device-filter.xml in the sources.
But then I unpack the .apk and see that the device-filter.xml in there is
the old one.

ARG. android/res vs. android-mobile/res

Fixed. I hope. New binary is up:

http://subsurface-divelog.org/downloads/test/Subsurface-mobile-4.8.1.162-arm.apk

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: help needed: Android devices and FTDI dive computers

[Dirk Hohndel]

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...

http://subsurface-divelog.org/downloads/test/Subsurface-mobile-4.8.1.161-arm.apk

This tries to
a) get your i750TC recognized (not sure if that will help with download)
b) switch to the Download page even if Subsurface-mobile wasn't running
when you plugged in your device

So far I can tell you "it compiles". I might have completely broken things
and nothing might work anymore... but if you happen to have a moment, I'd
appreciate more testing :-)

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: help needed: Android devices and FTDI dive computers

[Matt Thompson]

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: "Unable to open ftdi Aqualung (i750TC)"
> > > "19.795: Unsupported operation"
> > > no new dives downloaded
> > > "19.821: DCDownloadThread finished"
> > >
> > > -- libdivecomputer.log --
> > > Subsurface: v4.8.1-156-g23b7970459b6, built with libdivecomputer
> > > v0.7.0-devel-Subsurface-NG (bb985eedbb3e686e5a71bf2aa234fb49f8cab653)
> > > INFO: Open: name=ftdi
> > > ERROR: No such file or directory (2) [in
> > > /data/android/subsurface/libdivecomputer/src/serial_posix.c:295
> > > (dc_serial_open)]
> > > -- finish --
> >
> > This might be a sign that your phone doesn't allow access to '/sys' as a
> > "security precaution" and that currently breaks our ability to download
> > via FTDI.
>
> Actually, since you are able to do Cobalt downloads on that phone... I'm
> not sure this is true. That should run into the same libusb problems, I
> think...
>
>
I was able to download from my D4i as well so I'm not sure what's going on
with the 750.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: more help needed: Android + FTDI, Cobalt, Suunot EON Steel/Core, Scubapro G2/Aladin Square

[Dirk Hohndel]

On Thu, Aug 09, 2018 at 08:41:41AM +0200, Dietrich Meyer wrote:
> Hi Dirk,
> 
> Phone: Samsung Galaxy S7 Edge, LineageOS 14.1
> DC: Suunto Vyper 2
> FTDI cable: NoName...
> Subsurface 4.8.1.156
> 
> > Start Subsurface-mobile (I need to poke at this a little more in order for
> > it to work correctly when Subsurface-mobile gets started because you
> > plugged in a dive computer)
> 
> On my phone, subsurface always gets started automatically, when I connect the 
> FTDI cable - this did work already for the last year - nothing new here

Yes, that had worked in the past - I explained this poorly in my post.
What's new is that we try to open the download page and populate some of
the information based on the information that Android gives us.

> > Once Subsurface-mobile is running, plug in your dive computer. Android
> > should ask you if you want to connect the device with Subsurface-mobile.
> > If it doesn't ask, I want to know more about your dive computer and cable
> > in order to be able to fix this. Right now I think it should ask for all
> > the dive computers referenced in the Subject line of this email.
> 
> Didn't get any request, but I think that is because somehow the Android on my 
> phone already had the connection between the FTDI cable and subsurface (I 
> vaguely remember having seen such dialogue when I first used 
> subsurface-mobile 
> to download from my DC.

Yes, you can tell Android not to ask you anymore and to just start the app
whenever that device is plugged in.

> > Once you accept the request, Subsurface-mobile should switch to the
> > Download page, and depending on your specific situation, some / most / all
> > of the information for the three comboboxes should be filled in.
> 
> This is indeed new: It does now switch automatically to the download page.
> However: It does only do this when subsurface was already running.
> If I did not start subsurface previously but let it start by inserting the 
> FTDI cable, then it does not switch to the download page.

See my response to Matt a moment ago. There's a bit more code that I need
to write in order for that to work.

> > Please note which options were selected for vendor / product / connection
> 
> Vendor: Empty
> Product: Empty
> Connection: FTDI
> 
> Since my FTDI cable does not provide any more information, this makes sense...

Yep

> When I manually open the download page, then the vendor (Suunto) and product 
> (Vyper2) are preselected - remembered from previous downloads. But the 
> connection field is empty.

The goal is to get you the best of both worlds. The information it
remembered plus what it can learn from the cable plugged in. Also code
that is not complete, yet.

> "26.372: UsbDevice[mName=/dev/bus/usb/
> 001/003,mVendorId=1027,mProductId=24577,mClass=0,mSubclass=0,mProtocol=0,mManufacturerName=Smartinterface,mProductName=USB
>  
> <-> Serial 
> Cable,mVersion=2.0,mSerialNumber=null,mConfigurations=[\nUsbConfiguration[mId=1,mName=null,mAttributes=160,mMaxPower=250,mInterfaces=[\nUsbInterface[mId=0,mAlternateSetting=0,mName=USB
>  
> <-> Serial 
> Cable,mClass=255,mSubclass=255,mProtocol=255,mEndpoints=[\nUsbEndpoint[mAddress=129,mAttributes=2,mMaxPacketSize=64,mInterval=0]
> \nUsbEndpoint[mAddress=2,mAttributes=2,mMaxPacketSize=64,mInterval=0"

Yes, the best we can do here is guess that this is an FTDI device.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: help needed: Android devices and FTDI dive computers

[Dirk Hohndel]

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 operation"
> > no new dives downloaded
> > "19.821: DCDownloadThread finished"
> > 
> > -- libdivecomputer.log --
> > Subsurface: v4.8.1-156-g23b7970459b6, built with libdivecomputer
> > v0.7.0-devel-Subsurface-NG (bb985eedbb3e686e5a71bf2aa234fb49f8cab653)
> > INFO: Open: name=ftdi
> > ERROR: No such file or directory (2) [in
> > /data/android/subsurface/libdivecomputer/src/serial_posix.c:295
> > (dc_serial_open)]
> > -- finish --
> 
> This might be a sign that your phone doesn't allow access to '/sys' as a
> "security precaution" and that currently breaks our ability to download
> via FTDI.

Actually, since you are able to do Cobalt downloads on that phone... I'm
not sure this is true. That should run into the same libusb problems, I
think...

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: more help needed: Android + FTDI, Cobalt, Suunot EON Steel/Core, Scubapro G2/Aladin Square

[Dirk Hohndel]

On Wed, Aug 08, 2018 at 11:55:42PM -0500, Matt Thompson wrote:
> >
> > Here's what I'd like people to try - even if you only have an Android
> > device that currently doesn't allow us to download via USB OTG! We won't
> > try to download, we just want to see if the automation for picking the
> > right vendor / product / connection is working as intended...
>
> Auto launched Subsurface mobile with both the Cobalt 2 and Suunto D4i.  If
> Subsurface was not already running it did not switch to the download page
> automatically. 

Correct. There is some code missing that I still need to write. When
Subsurface-mobile is launched by the Intent (i.e., by Android detecting a
USB devie we have registered our interest in) we need to wait until the
app is fully launched and ready before we try to open the download page.

So this is a known issue and will be addressed. Once I find the time to
work on it :-)

> If Subsurface was open or running in the background it did
> automatically pull up the download page and fill in details.  Cobalt 2 was
> completely ready to go.  Suunto only had the manufacturer selected
> (probably all we can hope for based on the cable implementation.)

Thanks for the confirmation that this works as I had hoped.

> i750TC did not ask about which app to use when I plugged it in.  Info sent
> on the other thread.

Yes, that will be fixed in the next build.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: help needed: Android devices and FTDI dive computers

[Dirk Hohndel]

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 Class: Use class information in the Interface Descriptors (0x0)
> Vendor ID:  0403
> Vendor Name (reported):  FTDI
> Vendor Name (from DB):  Future Technology Devices International, Ltd
> Product ID:  6015
> Product Name (reported):  FT231X USB UART
> Product Name (from DB):  not found

So this appears to be a Product ID for FTDI that we hadn't seen before.
It's unclear, of course, if this is Aqualung specific or just another
generic one.

I'll add this to the ones we recognize, but for now without making it
pre-select Aqualung.

> Looks like we don't have this one working for download at all just yet in
> mobile.  I was able to select everything but downloads fail.  Logs follow.

I'm adding this to my branch right now.

> -- 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 operation"
> no new dives downloaded
> "19.821: DCDownloadThread finished"
> 
> -- libdivecomputer.log --
> Subsurface: v4.8.1-156-g23b7970459b6, built with libdivecomputer
> v0.7.0-devel-Subsurface-NG (bb985eedbb3e686e5a71bf2aa234fb49f8cab653)
> INFO: Open: name=ftdi
> ERROR: No such file or directory (2) [in
> /data/android/subsurface/libdivecomputer/src/serial_posix.c:295
> (dc_serial_open)]
> -- finish --

This might be a sign that your phone doesn't allow access to '/sys' as a
"security precaution" and that currently breaks our ability to download
via FTDI.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: QML help sought

[Joakim Bygdell]

Hi Robert,

You need to add "import QtQuick.Controls 2.2 as Controls" in the
reportBugPage.qml

 file

/ Jocke
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: more help needed: Android + FTDI, Cobalt, Suunot EON Steel/Core, Scubapro G2/Aladin Square

[Anton Lundin]

Nice work Dirk.

I'll dump some data from my devices when I get back home.

I'd love to see parts of this feature ported to the desktop ui to. On Linux we 
can dig out info about ftdi devices from sysfs, and we might be able to do 
something equivalent on windows and Mac.

//Anton - sorry for the top post, on my cell

On August 9, 2018 6:21:05 AM GMT+02:00, Dirk Hohndel  wrote:
>Once again, this was written without being able to test the code as I
>didn't take any dive computers (or the old phone that allows access to
>/sys) with me on this business trip... based on Matt's test of an
>earlier
>version I am, however, hopeful that this might be going in the right
>direction.
>
>Here's what I'd like people to try - even if you only have an Android
>device that currently doesn't allow us to download via USB OTG! We
>won't
>try to download, we just want to see if the automation for picking the
>right vendor / product / connection is working as intended...
>
>Download the latest test build
>http://subsurface-divelog.org/downloads/test/Subsurface-mobile-4.8.1.156-arm.apk
>
>Start Subsurface-mobile (I need to poke at this a little more in order
>for
>it to work correctly when Subsurface-mobile gets started because you
>plugged in a dive computer)
>
>Once Subsurface-mobile is running, plug in your dive computer. Android
>should ask you if you want to connect the device with
>Subsurface-mobile.
>If it doesn't ask, I want to know more about your dive computer and
>cable
>in order to be able to fix this. Right now I think it should ask for
>all
>the dive computers referenced in the Subject line of this email.
>
>Once you accept the request, Subsurface-mobile should switch to the
>Download page, and depending on your specific situation, some / most /
>all
>of the information for the three comboboxes should be filled in.
>
>Please note which options were selected for vendor / product /
>connection
>
>Now go to the About page, copy the logs and send all the information
>(which dive computer, which cable, did this all work, which v/p/c was
>selected when the download page opened) plus of course the logs to the
>mailing list.
>
>I'd love to see the information we can get from the various USB based
>OSTC
>dive computers (maybe Matthias can help there?). And also for any other
>dive computer that you happen to have a cable for.
>
>
>Thanks, I really appreciate the help :-)
>
>/D
>
>PS: and now, of course, I hope I didn't mess up something stupid,
>everyong
>tries and nothing works at all...
>___
>subsurface mailing list
>subsurface@subsurface-divelog.org
>http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: more help needed: Android + FTDI, Cobalt, Suunot EON Steel/Core, Scubapro G2/Aladin Square

[Dietrich Meyer]

Hi Dirk,

Phone: Samsung Galaxy S7 Edge, LineageOS 14.1
DC: Suunto Vyper 2
FTDI cable: NoName...
Subsurface 4.8.1.156


> Start Subsurface-mobile (I need to poke at this a little more in order for
> it to work correctly when Subsurface-mobile gets started because you
> plugged in a dive computer)

On my phone, subsurface always gets started automatically, when I connect the 
FTDI cable - this did work already for the last year - nothing new here



> 
> Once Subsurface-mobile is running, plug in your dive computer. Android
> should ask you if you want to connect the device with Subsurface-mobile.
> If it doesn't ask, I want to know more about your dive computer and cable
> in order to be able to fix this. Right now I think it should ask for all
> the dive computers referenced in the Subject line of this email.
> 

Didn't get any request, but I think that is because somehow the Android on my 
phone already had the connection between the FTDI cable and subsurface (I 
vaguely remember having seen such dialogue when I first used subsurface-mobile 
to download from my DC.


> Once you accept the request, Subsurface-mobile should switch to the
> Download page, and depending on your specific situation, some / most / all
> of the information for the three comboboxes should be filled in.
> 

This is indeed new: It does now switch automatically to the download page.
However: It does only do this when subsurface was already running.
If I did not start subsurface previously but let it start by inserting the 
FTDI cable, then it does not switch to the download page.



> Please note which options were selected for vendor / product / connection

Vendor: Empty
Product: Empty
Connection: FTDI

Since my FTDI cable does not provide any more information, this makes sense...
When I manually open the download page, then the vendor (Suunto) and product 
(Vyper2) are preselected - remembered from previous downloads. But the 
connection field is empty.




> 
> Now go to the About page, copy the logs and send all the information
> (which dive computer, which cable, did this all work, which v/p/c was
> selected when the download page opened) plus of course the logs to the
> mailing list.

-- subsurface.log --
Empty filename passed to function
"0.014: Successfully opened logfile /storage/emulated/0/subsurface.log at Do. 
Aug. 9 08:28:19 2018"
"0.015: Starting Subsurface-mobile:2.1.1(4.8.1.156):Android Nougat 
(7.1):arm:de-DE"
"0.016: built with libdivecomputer v0.7.0-devel-Subsurface-NG 
(bb985eedbb3e686e5a71bf2aa234fb49f8cab653)"
"0.016: built with Qt Version 5.11.1, runtime from Qt Version 5.11.1"
"0.016: built with libgit2 0.26.0"
localBtDevice isn't valid or not connectable
"Created position source android"
"0.037: Created position source android"
"Set GPS service update interval to 300 s"
"0.038: Set GPS service update interval to 300 s"
"0.038: location service is available"
"0.648: Datendatei wird synchronisiert"
"0.651: Lade Tauchgänge aus dem lokalen Zwischenspeicher"
"0.890: Tauchdaten erfolgreich geöffnet"
"0.914: AppState changed to active with save ongoing and no unsaved changes"
"0.916: 344 dives loaded from cache"
"0.918: have cloud credentials, trying to connect"
"0.918: Have credentials, let's see if they are valid"
Completed connection with cloud storage backend, response "[OK]"
"Set GPS service update interval to 300 s"
"2.403: Set GPS service update interval to 300 s"
Using the following font: Roboto
qqwindow devicePixelRatio 3.50285 3.50285
Supported dive computers:
"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), 
Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), 
Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), 
Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"
"Aqualung: i200 (SERIAL), i300 (SERIAL), i450T (SERIAL), i550 (SERIAL), i750TC 
(SERIAL, BT)"
"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"
"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"
"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), 
EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"
"Cressi: Drake (SERIAL), Giotto (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"
"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"
"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, 
BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 
(SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, 
BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"
"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"
"Mares: Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), 
Smart (SERIAL, BLE)"
"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 
(SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 
(SERIAL), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro 
Plus 2.1 (SERIAL),