deviceid

Anton Lundin glance at acc.umu.se
Fri Nov 21 15:08:59 PST 2014


On 21 November, 2014 - boret wrote:

> Hi Anton.
> 
> On Viernes, 21 de noviembre de 2014 16:59:30 Anton Lundin escribió:
> 
> > My regular cycle is:
> > * open subsurface
> > * download from the ostc
> > * see how it downloads duplicates of lots of dives, and thus screwing up
> >   the nice cleaned gas lists
>             ^^^^^^^^^^^^^^
> I think this is the point of the question.  I used to have all six gases 
> actives, then, after downloading with a new fw (changed deviceid) I had the 
> same problem with the previously cleaned lists.  I changed my way having 
> active only the used gases, and the problem disappeared  (probably because 
> there is no difference between dives in log and newly downloaded dives).
> 
> > * swear
> 
> I used to too.
> 
> > * quit subsurface without saving
> > * open subsurface
> > * download into a private trip
> > * remove the duplicates from the private trip
> > * merge the private trip downloads into the appropriate dives.
> > * vim xml-file , :%s/old_deviceid/new_deviceid/g
> > 
> > So, it happens on a quite regular basis for me.
> 
> I use a 2N and  now it happens no more for me (I even thought it had been a 
> change in subsurface, but your list has made me remember those issues with 
> gases). In fact, I use the alias for the dc to keep track of the fw version 
> and I've now 4 deviceids for the same dc.
> 
> BTW, have just updated the OSTC fw to 3.0 with subsurface's new features for 
> OSTC (that's your child), *and worked great*, better than the tiny H&W 
> bootloader for win or JDivelog, as with your code OSTC reboots without user 
> having to force it.
> I've noticed some weird thing related to the tasks flow, but I recognize I was 
Parts of it is my work, but the heavy lifting for the OSTC/mk2/2N is
written by Jef in libdivecomputer. I just wired it up.

The config bits are all my mess.
( And yes, that code is messy. I can imagine how a embedded developer
thought 512 bytes config blocks was a nice way to read and write config,
but its _messy_ to handle! The OSTC3 have a way nicer interface, and it
can actually validate the config values you try to give it.)

There is FW update code for the OSTC3 in review too, so that will show
up to users soon to =)

> a bit scared to use such an untested software to pay the needed attention.
> 

Yea, there are some progress-bar work that probably should happen there.
I haven't gotten around to do that.

Especially some of the slower protocols, like the Suunto, and when
talking to a OSTC Sport do really need some user feedback on whats
happening.

I'll hammer out a ticket in trac to remember to do that.


//Anton


-- 
Anton Lundin	+46702-161604


More information about the subsurface mailing list