[aprssig] New IGate Operator

Gregg Wonderly gregg at wonderly.org
Wed Jan 4 21:57:00 CST 2017

I think its gotten to the point that refusing to consider Radio transmissions on non-amateur frequencies as “not RF” is extremely silly.  Not everyone is going to have Ham equipment with them at all times, in all places.  APRS on mobile devices no matter what frequency they operate on, is what APRS is about.

The reason why amatuer radio is so non interesting is the rediculously immature technologies we are still using decades later with no evolution.  We need devices we can upgrade software on dynamically.

Frankly I think it’s time to pitch all the old stuff and move on.

I’d vote for using OpenTrac instead of APRS and just move on down the road…


> On Jan 4, 2017, at 10:51 AM, Nagi Punyamurthula <n0agi at n0agi.com> wrote:
> I usually stay away from IS->RF forwarding.  APRS was (I would say still is IMHO) originally intended to enable simple packet ops for the RF traffic.  The IS stack came into picture to enable reporting on the front end visualization. If a source station originated from TCP/IP (IS), leave it there – since the source station’s intent is not so much for letting RF know, but, to let other TCP/IP users know via visualization tools such as aprs.fi <http://aprs.fi/>.
> Pete, fyi, I have been using the Microsat’s Wx3in1 Plus and Mini for a few years now (for local APRS WIDE digipeater / iGate and also for my sGate ops as igate) – I agree, they’re great products. I am happy to assist w/ any settings related questions you might have. Best wishes
> 73, N0AGI-Nagi
> http://N0AGI.com/ <http://n0agi.com/>
> http://call.n0agi.com/ <http://call.n0agi.com/>
> http://arissdash.n0agi.com/ <http://arissdash.n0agi.com/>
> http://MNDMR.net/ <http://mndmr.net/>
> http://services.n0agi.com/ <http://services.n0agi.com/>
> http://cubes.n0agi.com/ <http://cubes.n0agi.com/>
> http://MNMesh.net/ <http://mnmesh.net/>
>   <>
> From: aprssig [mailto:aprssig-bounces at tapr.org <mailto:aprssig-bounces at tapr.org>] On Behalf Of Lee Bengston
> Sent: Tuesday, January 3, 2017 8:27 PM
> To: TAPR APRS Mailing List <aprssig at tapr.org <mailto:aprssig at tapr.org>>
> Subject: Re: [aprssig] New IGate Operator
> On Jan 3, 2017 1:08 PM, "Jason KG4WSV" <kg4wsv at gmail.com <mailto:kg4wsv at gmail.com>> wrote:
> On Tue, Jan 3, 2017 at 8:52 AM, Jim Conrad <jjc at oceanviewcom.com <mailto:jjc at oceanviewcom.com>> wrote:
> My thought process is that positions no matter the source of actual hams (not objects) should be reflected on RF which provides a coherent picture for the RF stations.
> IMO you're sort of contradicting yourself.  How does giving a picture of hams on cell/IP give you a picture of RF?  It doesn't.  It's noise. If they're not on RF, then they don't need to be on RF.
> Actually he referred to providing a picture for RF stations as opposed to a picture of RF.  I can see the benefit with respect to messaging. Someone on RF could see someone on a phone, and send them a message.
> There was a bug in AprsDroid a while back (now fixed as far as I know) that resulted in stations sending positions very rapidly, so there is the risk of gating an Android device running an old version.
> IMO it all depends on RF traffic in a local area. If it's very low, it should be OK to RF gate the phones, especially with rate limiting functionality in the Igate. How low is low - yeah, it's subjective. Whether the device in question can do it is really a question for the maker of that device - does it have its own mailing list?
> Now for non-APRS RF resources that may benefit by being announced on APRS, which what you may be headed toward, look at Bob's info here: http://www.aprs.org/localinfo.html <http://www.aprs.org/localinfo.html>
> I have to admit I haven't looked at that yet; thanks for sharing.  Off to take a look.
> Lee - K5DAT 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org <mailto:aprssig at tapr.org>
> http://www.tapr.org/mailman/listinfo/aprssig <http://www.tapr.org/mailman/listinfo/aprssig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20170104/c0cdce13/attachment.html>

More information about the aprssig mailing list