[aprssig] KC0YA-11 and AE0SS-11 Balloons Aloft
Tom Hayward esarfl at gmail.comSat Mar 12 19:36:38 UTC 2011
- Previous message: [aprssig] KC0YA-11 and AE0SS-11 Balloons Aloft
- Next message: [aprssig] KPC3+ induced errors (was: KC0YA-11 and AE0SS-11 Balloons Aloft)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Mar 12, 2011 at 09:46, Keith VE7GDH <ve7gdh at rac.ca> wrote: > Stephen WA8LMF wrote... > >> Two simultaneous balloon launches by EOSS about 45 miles north of >> Denver, CO are now aloft. Both are experiencing a really severe case >> of the KPC3+ KISS delayed packet syndrome from an IGate somewhere >> in the north-eastern Colorado area... <http://wa8lmf.net/LiveTrack> > > Perhaps the APRS frequency isn't overly busy in CO, but I see that at > least one of tem is beaconing full NMEA sentences with a WIDE2-2 path > (at least they weren't using WIDE1-1)... Their website says they use 144.340 MHz for APRS and ask a few local igate operators to change frequencies to support the flight and recovery. I got the impression they put a portable digipeater in the expected recovery area, but I may have read that wrong. http://www.eoss.org/flight/index.html While they're probably not bothering anyone on 144.340, I still don't agree with beaconing full NMEA sentences. Base91 compressed packets seem like a better alternative for high-accuracy beacons. Tom KD7LXL
- Previous message: [aprssig] KC0YA-11 and AE0SS-11 Balloons Aloft
- Next message: [aprssig] KPC3+ induced errors (was: KC0YA-11 and AE0SS-11 Balloons Aloft)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
