Failed OSTC3 fw update
Dirk Hohndel
dirk at hohndel.org
Mon Sep 21 11:12:26 PDT 2015
On Mon, Sep 21, 2015 at 07:56:19PM +0200, Anton Lundin wrote:
> On 17 September, 2015 - "Paul-Erik Törrönen" wrote:
>
> The dc went into maintenance-mode but got stuck in uploading the new
> firmware to the device, and never got a reply.
>
>
> The lack of reply is probably due to a crappy battery running out, but
> the qtserialbluetooth code never times out on read. Thats bad, and makes
> the hole ui hang.
>
> I'm going to try to remember to by some batteries and test it again, but
> the bt code needs a timeout anyhow.
Send me your address and I'll have Amazon drop a few dozen AA batteries at
your house :-)
It would be exceptionally useful if this got tested and worked correctly
by the time we release 4.5 (assuming we do ever release 4.5)
/D
More information about the subsurface
mailing list