[hpsdr] Database reset = loss of calibration data?

[Greg - ZL3IX]

I also think that it's a pity the designers didn't do a bit more to 
maintain database compatibility between versions.  I don't think it's 
too hard, provided that the original design makes database compatibility 
a priority.

I work for a radio company, and we had this dilemma in 2002 when moving 
into the SDR arena, and a decision was taken to use tags with database 
items.  The radio app, and the programming app will use the tags they 
understand, and ignore the ones they don't, using defaults for those 
items.   The programming app will also read a much newer radio, and save 
its configuration, even though it doesn't understand the tags that it 
reads.  That scheme works extremely well, and has resulted in backwards 
and forwards quasi compatibility for the last 12 years.

73, Greg, ZL3IX


On 2014-07-12 02:30 p.m., Brian Lloyd wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
>
>
>     On Fri, Jul 11, 2014 at 8:22 PM, John Ackermann N8UR <jra at febo.com
>     <mailto:jra at febo.com>> wrote:
>
>         ***** High Performance Software Defined Radio Discussion List
>         *****
>
>         I find myself needing to upgrade from mRX PS 3.2.10 to 3.2.17
>         and see that at 3.2.12 there was an instruction to reset the
>         database.
>
>         Sorry if this is a dumb/obvious question, but when you reset
>         can you then re-import a saved database from the previous
>         version (ie, suck the old data into the new database format)? 
>
>
> Actually Ray (K9DUR if I recall) wrote a program to do this for 
> PowerSDR but then decided he was only going to support the Flex 
> version of PowerSDR.
>
> Still, it would be relatively easy to add a simple version number to 
> the database so that the software would look at the version number an 
> not try to load an incompatible version of the database thus ending 
> the continuing stream of, "I just loaded the new version and it must 
> be broken because now PowerSDR is going all kinds of weird stuff it 
> isn't supposed to do and how do I fix it," queries.
>
> Or, better still, take each section (your calibration maybe?) and give 
> each section a version number. Now the software can load only those 
> portions of the database that are still compatible. OK, you would have 
> to reenter SOME stuff but not everything. That is only marginally more 
> difficult than the step above but still within reason.
>
> But I guess the idea of a version number in the DB is really hard.
>
> -- 
> Brian Lloyd
> Lloyd Aviation
> 706 Flightline Drive
> Spring Branch, TX 78070
> brian at lloyd.com <mailto:brian at lloyd.com>
> +1.916.877.5067
>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20140712/ae68ae93/attachment-0003.htm>