[aprssig] APRS Runner Tracking

ka8vit at ka8vit.com ka8vit at ka8vit.com
Thu Aug 8 06:42:40 CDT 2013


I would agree with you, Bob.

I think Andrew's concerns are unfounded.

The only time I have ever seen a flash or EEPROM "wear out" due
to exceeding the number of read/write cycles is when my code
had a bug and was stuck in a loop.

And even then it only "wore out" the 10-bytes I was writing to.

Have never heard of it happening with even extreme use.

73 - Bill KA8VIT


> On August 7, 2013 at 3:54 PM Robert Bruninga <bruninga at usna.edu> wrote:
>
>
> >> Set your position to your checkpoint. Then each time you want to
> >> report a particular runner number, just change the MYCALL of the radio
> >> to the runner number...
>
> > Interesting idea but you won't catch me doing it and
> > that's because you're forgetting that the radio stores data
> > in flash memory which has a finite lifetime. I prefer
> > not to wear out the flash memory in my radio prematurely
>
> Hummh. I have about 8 or so D7's between my oriingal prototype and all
> the ones at work, and so the age is from 15 years old to about 10 years
> old, and not one of them has failed for anything, though several have no
> control knob from having bounced on concrete numerous times.
>
> > It all gets stored in flash which wears out.
>
> Yes, but 100,000 cycles is sure a long long time. Let say 20 entries per
> marathon 5 marathons a year, that is about 1000 years life. I doubt even
> Kenwood will be around then...
>
> Bob

====================================
Bill Chaikin, KA8VIT
USS COD Amateur Radio Club - W8COD
WW2 Submarine USS COD SS-224 (NECO)

ka8vit at ka8vit.com
http://ka8vit.com
http://www.usscod.org
====================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20130808/30f3f473/attachment.html>


More information about the aprssig mailing list