Fwd: OSTC 2 issues on iOS

Dirk Hohndel dirk at hohndel.org
Mon Jul 2 10:33:41 PDT 2018



> Begin forwarded message:
> 
> From: patrick werner <pa7r1clc at gmail.com>
> Subject: Re: OSTC 2 issues on iOS
> Date: July 2, 2018 at 10:18:22 AM PDT
> To: Dirk Hohndel <dirk at hohndel.org>
> 
> Hi Dirk, thank you for your help. my english  is not the best one.
> but in understand 90 % of your text :-)
> 
> it works with the connection   LE:{271d26ef-9793-7f63-79be-a6aef34c1f33}
> its the first time running, yeahr :-)
> 
> but i dont understand it, before i wrote to you i test all of the connections and diver computers but it doesent work :-(
> 
> and nof it works, mhhh.
> 
> but thank you for your help!!!!
> 
> Patrick 
> 
> and sry for my english :-)
> 
> 
> 
> 2018-07-02 18:39 GMT+02:00 Dirk Hohndel <dirk at hohndel.org <mailto:dirk at hohndel.org>>:
> OK, I figured out what caused us not to recognize your dive computer in the first place.
> The logic of how we got there is a bit convoluted - part of this is that the OSTC family of dive computers displays different names on Bluetooth that don't always match their model number. Yours, for example, reports "OSTC+ 16602" (where 16602 is the serial number).
> Our code to match this to a specific model was written when all we cared about was the correct download protocol, so we assumed that this was an OSTC 3 (as all three of those models use the same download protocol). But later libdivecomputer started to differentiate the models not just by download protocol, but also by transfer mechanism - and the OSTC 3 doesn't support BLE, but the OSTC 2 and OSTC Plus (who both identify themselves as "OSTC+ xxxxx") both do. As I said, convoluted, and not exactly relevant to a user. 
> 
> To sum it up, this is now fixed in our code base, the next version of Subsurface-mobile for iOS should identify your dive computer as OSTC 2 and mark the connection accordingly.
> 
> In the meantime I'm still interested in whether the download works for you if you manually pick the correct BLE connection.
> 
> Thanks
> 
> /D
> 
> > On Jul 2, 2018, at 8:15 AM, Dirk Hohndel <dirk at hohndel.org <mailto:dirk at hohndel.org>> wrote:
> > 
> > Hi Patrick,
> > 
> > From your log it looks like we need to slightly adjust our pattern matching - I thought we already recognized "OSTC+" as an OSTC dive computer, but apparently we don't.
> > 
> > Found new device: "Torantrieb" "LE:{1cc8fa89-54ed-49f8-b4e7-63b9ec1b2bc8}"
> > Not recognized as dive computer
> > Found new device: "OSTC+ 16602" "LE:{271d26ef-9793-7f63-79be-a6aef34c1f33}"
> > Not recognized as dive computer
> > 
> > Nevertheless, this should already work.
> > Pick OSTC 2 in the product drop down and select LE:{271d26ef-9793-7f63-79be-a6aef34c1f33} as connection. Then tap on Download (with the OSTC in Bluetooth mode, of course).
> > 
> > If that fails, please again collect the logs and send them to our mailing list (I have added you to the auto-approval, so you won't get stuck in moderation again).
> > 
> > Thanks
> > 
> > /D
> > _______________________________________________
> > subsurface mailing list
> > subsurface at subsurface-divelog.org <mailto:subsurface at subsurface-divelog.org>
> > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface <http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20180702/2c64b3e7/attachment-0001.html>


More information about the subsurface mailing list