Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRStt software?

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Wed May 20 16:47:05 UTC 2009


As Scott said, I'm not at all concerned about PC software, or even a 
Windows Mobile implementation (assuming the TouchTone decoder software 
is portable).  But there was discussion about doing this on the 
OpenTracker platform and other embedded systems.  PIC platforms measure 
code in K (if you're lucky) or variable space in bytes.  All memory is 
statically allocated and there's no heap or other dynamic stuff available.

My professional life deals with memory-resident data in the Gigabytes, 
but I've also programmed Basic Stamps, SX controllers, and have watched 
my son program the Propellor (a multi-core PIC).  It's a completely 
different world there.  Even DOS's 640K was tons of space compared to 
the controllers in the TinyTrak and OpenTrack hardware.

Lynn (D) - KJ4ERJ

Rick Ruhl wrote:
> Ive been writing link lists since I was in high school.  It's easy to do a
> linked list for even 200 stations in a system that only has 256 meg of ram..
> and that's what you need to run XP at the lowest.  Goodness. This may take
> up 2 or 3 meg of memory when Im done with it.
>
> Most of you guys don't know me, but in the 80's I was part of the team that
> wrote the PC-MOS O/S (multiuser DOS). I always write small code.. I used to
> have to put things in 8 and 16K.. been there done that, like you guys have!
>
> Rick - W4PC
>
>
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
> Of Lynn W. Deffenbaugh (Mr)
> Sent: Wednesday, May 20, 2009 10:50 AM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] APRStt software?
>
> Bob Bruninga wrote:
>   
>>> If I remember the APRStt spec correctly, 
>>> it actually requires a DB of callsign 
>>> shortcuts that might be quite a challenge...
>>>     
>>>       
>> That was abandoned in this new rendition of APRStt.  In this version,
>>     
> users always send their full callsign first (with overlay character).  After
> that, they can use only their 3 digit suffix (plus overlay character)
>   
>>   
>>     
> Anytime someone can use a full callsign and follow it up with a 3 digit 
> suffix, the APRStt server needs to be remembering the original to match 
> against for the shortcuts.  That's the part that I was indicating a DB 
> (or lookup table or some-such) would be necessary and possibly a 
> challenge for resource-constrained platforms, especially if the 
> shortcuts are valid for 30 minutes or so.
>
> Lynn (D) - KJ4ERJ - Not dashing the spec, but "real-worlding" some 
> expectations
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.238 / Virus Database: 270.12.33/2120 - Release Date: 05/19/09
> 06:21:00
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>   




More information about the aprssig mailing list