Product / vendor on mobile download
thomas.fange at gmail.com
Wed Jun 20 13:41:36 PDT 2018
Sorry for this, I sent the video directly to Dirk, since it was too large
for the forum mailserver...
Den ons 20 juni 2018 21:53Thomas Fänge <thomas.fange at gmail.com> skrev:
> Hi Dirk!
> No problem, happy to help out!
> I include a video - easier to explain. When BT is on, I can only see
> Mac-addresses in the drop-down box, and when I turn BT off, I can only see
> FTDI. Previously both Mac-addresses and FTDI was available even when BT
> was on.
> I guessed previously that dc_serial_open failed, since Libdivecomputer.log
> Subsurface: v4.7.8-213-g6a91611e90cc, built with libdivecomputer
> v0.7.0-devel-Subsurface-NG (e97a47cca55973199715df0f818b4955e60d3a31)
> INFO: Open: name=ftdi
> ERROR: No such file or directory (2) [in
> This I think resulted in the "Unsupported operation" error message.
> Best regards,
> Den ons 20 juni 2018 21:16Dirk Hohndel <dirk at hohndel.org> skrev:
>> Hi Thomas,
>> Thanks for testing. I wasn't all that optimistic, but based on Anton's
>> post it seemed possible that it was as simple as this.
>> > On Jun 20, 2018, at 11:07 PM, Thomas Fänge <thomas.fange at gmail.com>
>> > No success, it just behaves as before, same log as before, but the
>> reference to "localBtDevice isn't valid or not connect" I don't recognize
>> from before. I still think that the log at 27.556:"Unsupported operation"
>> should tell us something.
>> > "27.553: DCDownloadThread started for Mares Puck Pro on FTDI"
>> > Starting download from ftdi
>> > Starting the thread 0
>> > Finishing the thread Unable to open %s %s (%s) dives downloaded 0
>> I need to fix that debug message. Grmbl.
>> So we still fail to open the FTDI device - but at least we are trying to
>> open the right thing.
>> > "27.556: Unsupported operation"
>> > no new dives downloaded
>> > "27.557: DCDownloadThread finished"
>> > localBtDevice isn't valid or not connecta
>> > Same on all devices I tested on.
>> > I also noticed that I had to disable Bluetooth for FTDI to appear as a
>> valid option for connection.
>> That's strange, can you say more? I see FTDI here on my devices with BT
>> > Nor can I test with version 18.104.22.1680 that other claims should work,
>> since Mares DC is not enabled in that version. 😕
>> Worst case I can go back and hack that, I guess...
>> > And yes, I have new dives on the DC... 😉
>> The error "unable to open" made it clear that this is not just a "no new
>> dives" issue, but thanks for explicitly stating that.
>> > ---------- libdivecomputer.log ----------
>> > Subsurface: v4.7.8-287-g76f61468e690, built with libdivecomputer
>> v0.7.0-devel-Subsurface-NG (e97a47cca55973199715df0f818b4955e60d3a31)
>> > INFO: Open: name=ftdi
>> > ERROR: No such file or directory (2) [in
>> This sounds like the ftdi code isn't triggered. Maybe that's what is
>> actually broken - when we did the NG merge of libdivecomputer...
>> Linus, could that be the actual culprit?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the subsurface