Tim, One thing that would help is including your callsign so that we have a chance of helping you understand your local RF environment. It appears that your email address is your name, and your name

I have the dubious distinction of being one of the few igates in this part of NE PA according to APRS.fi. Lots of digipeaters but no igates. I liken that distinction to being the elephant (big ears)

If I could interject here, I had a fill in digi and igate that covered a hole in the local area. It doesn’t gate often, but what it did was fill that hole. Mine has been down for a while because

The most significant factor is the latency between your station and the IS server to which your station is connected. When I had an IGate in Northern VA a few years back I noticed a similar situation

But that is exactly my point. I understand wanting to contribute. Not trying to say this 'isn't contributing". The system may work just fine (now) if this (or that) station is removed, but if too

Hi Robert, for some of us, the reason we set up an APRS station is to be able to contribute and do something for the ham community. Maybe getting enjoyment out of being able to provide something for

I don't understand the question. There is no reward for providing the most packets to the APRS system. Why is it so important to have "your igate" be the one that gets the packet posted? The

Get a faster network connection. -- James VE6SRV

Hello All! Just downloaded and set up the software for use as an RX/TX Igate. Wow, what a wonder program! For as many features as it has, it really works so well and is very intuitive. I am using

Looks like firenet has gotten too popular for just 3 servers... Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 8/20/2020 1:14 PM,

Log: Port(APRS-IS):2020-08-20T17:12:20.146 Restarting Reader... Port(APRS-IS):2020-08-20T17:12:20.146 TcpReader Running on @45.79.131.203 or 45.79.131.203:14580 (0 OpenCmds, 0

Try using firenet.us. My firenet.us full feed from port 10152 is working fine: Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On

I have to correct myself. Two of the three now don't work (show "delay") and the remaining one displays "OK" but I get that annoying ding as if it isn't connected. Back to

On Thu, Aug 20, 2020 at 11:31 AM, Lynn Deffenbaugh wrote: firenet.aprs2.net = 129.15.108.120 firenet.aprs2.net = 45.79.131.203 firenet.aprs2.net = 44.155.254.6The third one listed isn't cooperating

Maybe just one of the servers is down. Try disabling and re-enabling the port which causes APRSIS32 to (possibly) select a different translation. Turns out that firenet.us and

It appears that Firenet.aprs2.net isn't functioning today, at least so far. I've switched my feed to noam.aprs2.net. Anyone have feedback if this is a temporary situation? 73, Glenn-KF0ED

Don, Probably the most important part of this is to learn the various parts of an AX.25 packet. There's basically the source, destination, path, and payload sections of a packet. Once you can find

Thanks for the info - I'll study the packet info in the link you sent. 73's Don W. KD4APP

I run a 30m receive aprs from time to time, park on 40m after 30m go's dead... 7.109.5 L I think.... there is a little 300bps at times... switching out pc's in the shack right now and it's not

The XML is purposely not documented as it is subject to change without notice. But the elements you are inquiring about are what drive the symbols under the covers of the View / Symbols