[aprssig] Dayton/xenia
chiefsfan2 at cox.net
chiefsfan2 at cox.net
Wed May 1 14:53:03 EDT 2019
If you used the split tx/rx you would still have to rx the wall to wall meaningless position beacons of of vehicles in the parking lot. If you used 144.990 simplex it would hopefully only be portable stations around the fairgrounds with a lot less QRM.
On May 1, 2019, 10:30 -0500, Randy Love <rlove31 at gmail.com>, wrote:
> APRS digipeaters usually self-identify. It makes no difference rules wise if it digitpeats on the same or different frequencies.
>
> > On Wed, May 1, 2019, 11:26 AM John D. Hays <john at hays.org> wrote:
> > > Wouldn't that be a repeater, with repeater rules?
> > >
> > > > On Wed, May 1, 2019, 08:04 Robert Bruninga <bruninga at usna.edu> wrote:
> > > > > What we need is for someone to put up a digipeater right at the fairgrouinds with a NOT-HIGH antenna that takes INPUT on 144.99 and TX's on 144.39
> > > > >
> > > > > Then everone right at the fairgrounds has priority input to the digi, but everyone still hears everything on 144.39
> > > > >
> > > > > THen HT's use normal APRS but with +600 offset.
> > > > >
> > > > > bob
> > > > >
> > > > >
> > > > > > On Tue, Apr 30, 2019 at 5:50 PM <chiefsfan2 at cox.net> wrote:
> > > > > > > The past few years I have been at Dayton/Xenia hamvention the main aprs frequency of 144.390 has been wall to wall position beacons. If users wanted to send situational awareness txt messages using an ht it would be very difficult. Hamvention has set up a cell group texting service for cell phones that works very well. It seems we are missing a great opportunity to use aprs radios for some messaging while on the fairgrounds. I'm not saying use aprs exclusively but it would be a good learning tools for aprs txt. I wonder if an alternate frequency for aprs ht' to use for txt messages would be a good idea? Maybe 144.990 as mentioned on bobs aprs.org website.
> > > > > > > _______________________________________________
> > > > > > > aprssig mailing list
> > > > > > > aprssig at lists.tapr.org
> > > > > > > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> > > > > _______________________________________________
> > > > > aprssig mailing list
> > > > > aprssig at lists.tapr.org
> > > > > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> > > _______________________________________________
> > > aprssig mailing list
> > > aprssig at lists.tapr.org
> > > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20190501/7be61ced/attachment.html>
More information about the aprssig
mailing list