Re: Coordinates and dive mapping

On Tue, Sep 29, 2015 at 05:16:41AM +0200, Willem Ferguson wrote: > I have three issues with a very recent git master (SHA c4eb957). That's 21 commits ago :-) (but I doubt this matters here) > 1) Entering coordinates by hand. > When I enter GPS coordinates by hand, Subsurface often loses some of

Re: ostc BT download failure

Or it could be too old qt (5.4.1). Is there any easy way to upgrade to 5.5 with poor Internet connection? miika On Tue, Sep 29, 2015 at 2:44 PM, Claudiu Olteanu wrote: > Hi, > > Anton is right. It seems that after it sends a command to the device, > the

Re: [PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

On 29 September, 2015 - Thiago Macieira wrote: > On Tuesday 29 September 2015 21:59:31 Anton Lundin wrote: > > - rc = device->socket->write((char *) data + nbytes, size - > > nbytes); > > + rc = device->socket->write((char *) data + nbytes, > > size - nbytes > 16 ? 16

Re: [PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

Hi there, I just tested the patches and all seems good. Thanks for making time to resolve this issue. I managed to update the firmware on my OSTC Sport device using our BTH implementation (from 10.18 to 10.20). I also have an OSTC 2 device with an old firmware (1.81) but it doesn't detect that

Re: [PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

On Tuesday 29 September 2015 21:59:31 Anton Lundin wrote: > - rc = device->socket->write((char *) data + nbytes, size - > nbytes); > + rc = device->socket->write((char *) data + nbytes, > size - nbytes > 16 ? 16 : size - nbytes); Yeah, that really shows the bug is

Re: ostc BT download failure

On Tuesday 29 September 2015 17:25:34 Miika Turkia wrote: > Or it could be too old qt (5.4.1). Is there any easy way to upgrade to > 5.5 with poor Internet connection? Hi Miika, Sorry, no easy way to do that. The libraries are big... -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT)

ostc BT download failure

Hi Claudiu and Thiago, I am testing out OSTC sport and BT download. However, this fails miserably: ---8<--- INFO: Sleep: value=300 Event: model=18 (0x0012), firmware=2578 (0x0a12), serial=10321 (0x2851) ERROR: Unsupported command. [in hw_ostc3.c:207 (hw_ostc3_transfer)] ERROR: Failed

Re: ostc BT download failure

On 29 September, 2015 - Miika Turkia wrote: > Hi Claudiu and Thiago, > > I am testing out OSTC sport and BT download. However, this fails miserably: > ---8<--- > INFO: Sleep: value=300 > Event: model=18 (0x0012), firmware=2578 (0x0a12), serial=10321 > (0x2851) > ERROR: Unsupported

[PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

This adds the QIODevice::Unbuffered flag to our rfcomm connections to bypass the buffering layer in QIODevice. This fixes so firmware upgrades work against the OSTC Sport. Signed-off-by: Anton Lundin --- I'm CC'ing Thiago and Claudiu here, so they can take a look and stop me

[PATCH 1/2] qtserialbluetooth: Remove no-op calls

waitForReadyRead and waitForBytesWritten not overridden in QBluetoothSocket and the default implementation in QIODevice are just no-ops that always return false. This removes those calls to lessen the confusion for anyone who looks at the code. Signed-off-by: Anton Lundin ---

Re: ostc BT download failure

Hi, Anton is right. It seems that after it sends a command to the device, the received response is not a valid one (your device doesn't recognize the command sent). Therefore it could be a problem with the version of your firmware. Claudiu ___

Re: [PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

On Tuesday 29 September 2015 21:12:55 Anton Lundin wrote: > This adds the QIODevice::Unbuffered flag to our rfcomm connections to > bypass the buffering layer in QIODevice. > > This fixes so firmware upgrades work against the OSTC Sport. Both patches look good. The unbuffered mode should not

Re: [PATCH 2/2] qtserialbluetooth: use QIODevice::Unbuffered io

On 29 September, 2015 - Thiago Macieira wrote: > On Tuesday 29 September 2015 21:12:55 Anton Lundin wrote: > > This adds the QIODevice::Unbuffered flag to our rfcomm connections to > > bypass the buffering layer in QIODevice. > > > > This fixes so firmware upgrades work against the OSTC Sport. >