I have two Igates that are 33 miles apart. They both report packets the other should have. Both are Raspberry Pi 2s identically configured using the same model of radios. One is on Spectrum Business Class, one is on Verizon for Internet access. They do have different antennas and have different coverage ranges. Both report lots of packets to the south, but not the other directions.
With APRS multiple stations can be transmitting at the same time. That can cause one Igate to miss what another hears. The Igates may be? forwarding to different pool servers. Those servers load levels might be different, which could get in the way as well.
As the FCC requires a station to identity every 10 minutes, so my Igates ID every 10 minutes, but with a Wide 1,1 so it's not digipeated.
Jim Bacher, WB8VSU
wb8vsu@...
https:\\
On May 8, 2022, at 11:54 PM, Patrick <
kd7wpq@...> wrote:
--
Packet #1 is a standard info beacon with a position.? That really should
happen no quicker than every 10 minutes and realistically, can come far
less often.. say every 30min.? Packet #2 is the the beginning of a set
of telemetry packets.? Consider these the column titles for the rest of
the telemetry data.? Packet #3 are the units for those columns.? The
rest is the various data.? The more often you send it, the more
resolution you have in the data but one needs to question do they need
that much resolution.? I would argue NO. You can see a graphical
depiction of that data here:
Btw.. if this location is correct.. it seems that the INDMT node has
some decent elevation which helps in all respects for distance, more
packet decodes, etc.
--
OK and understood on both counts
It's not a competition. I just have to wonder why my iGate is not
catching traffic that is closer than the other iGate. Those you have all
already gone over. It was more or less basically, "What am I doing wrong?".
Redundancy is great, for sure!
As for my internet, I have high speed cable internet, 2 modems, 200x20
each and soon I'll have 1,000/1,000 fiber along with 2 modems to ensure
up time, currently load balanced, later will be failover. The two modem
are basically for troubleshooting purposes between the cable company and I.
For my router I'm running PfSense on a A1SRi-2758. This may likely
change to a higher performance machine in later days as it'll just
barely handle the up coming 1Gb. Not that I'll be using all that
bandwidth but I'd rather the internet be the bottle neck, not my router.
Ping times vary between about 9 and 30ms but one modem does have some
periodic but minute packet loss we haven't been able to figure out.
Regarding the 440 or BBS stuff, I'll look into that. That would be handy.
Regarding filters, the only issue I've noticed is my antennas are too
close together. Something I'll need to remedy in the future as the iGate
de-senses my 706 on 2M and the 706 will de-sense the iGate. Something to
be expected but I don't use my desk radio too often, just every now and
then.
Regarding the TXDELAY, yea, I understand what it's for. Basically to
allow the transmitter to trigger and stabilize prior to actual activity.
I went ahead and pulled out the "/3". The only thing running on that
machine is a GUI, Direwolf and a KISS interface, that's it's whole
purpose in life at the moment. I'm perfectly content with some extra CPU
usage and I'm not worried about heat as all Pis I put to use have a big
solid aluminum heatsink. Under normal conditions they can't overheat,
I've tried purposefully just to see if they could.
OK, well thank you everyone for your input. I'm glad to have a better
configuration running on the iGate which should serve this area better
than it was.
Now to get the iGate up north working that should already be working but
that's another story.
