Keyboard Shortcuts
Likes
Search
Re: APRS iGate stopped working!
Lynn Deffenbaugh
¿ªÔÆÌåÓýLet's take this one step at a time.?? First to answer some mis-statements that I read in various responses in this thread: 1) aprs.fi and the APRS-IS in general are NOT the place to determine if your IGate is working.? Nor are they reliable for ANY APRS RF analysis.?? Due to the APRS-IS dupe suppression, only the FIRST gated instance of any packet are propagated through the network.? If a new IGate was brought up in your vicinity that is even slightly faster than your's, none of your gated packets will show up on the APRS-IS and therefore will also not appear on aprs.fi. 2) The zoom level of the APRSIS32 display has nothing to do with what packets are gated.?? There was one statement that alluded that your range is limited based on your zoom.? While it may be true that some filters are modified by the zoom of a window, those filters only determine what packets are sent TO your client FROM the APRS-IS.?? APRSIS32 will forward ALL RF-received packets to the APRS-IS by default unless you've messed with settings. Now, to diagnose your IGate: 1) Listen to 144.390 (or whatever your local APRS frequency is) and make sure you are at least audibly hearing packets.?? If not, check your radio and antenna.?? It is important that you do this audio test on the radio you are using for you IGate! 2) Diagnose your TNC with a terminal emulator or other suitable software (telnet?) depending on its connection to the APRSIS32 computer.?? Even in KISS mode, you should see something from the TNC whenever a packet is decoded.? If you see nothing, then check the audio connections between the TNC and your radio and/or the tuning parameters of the TNC itself.?? Or possibly the serial (or other) connection to the TNC. 3) If you pass those tests, then bring up the Port(<YourPortName>) trace log and enable? it.? Then disable and enable your RF port to see what the trace shows.? Then wait for packets to be received and see what the trace log shows. 4) Check the various IGate(*) trace logs.? Enable them and watch what they say or do not say. 5) See if any of the packets showing up in the packet scroller have an asterisk on them.?? Those indicate RF-received packets. And finally, if you're asking for help, please include all of the details of your station!?? AB9NN-48 is a really strange -SSID for an IGate.?? What radio??? What TNC??? What connection from the TNC to the APRSIS32 computer??? What port type are you using in APRSIS32??? What changed between when it was working and when it wasn't working?? Inquiring minds need to know these things to formulate reasonable suggestions. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 4/24/2024 10:32 AM, AB9NN - Jon
Kreski wrote:
What the???? My iGate which was processing nicely virtually all the APRS traffic in our rural area for many monts seemingly just stopped working.? I checked my radio, correct frequency, etc. and checked my cables.? Nothing seems wrong.? I took a quick look at the APRSIS32 screen and saw a few odd things.? One is that the bar on the left side of the screen is red.? Not sure that is right.? Also, there are two objects on the screen, both of which are me.? One is ME which I believe is AB9NN-48, my base station igate and is centered on the screen. The other is AB9NN? which is NW of center.? That is my callsign.? Why would there be two objects showing up?? I know it's not processing any APRS packets because I just drove my mobile multiple times and it always proceesses them even though there is another digipeter in the area.? That digipeater doesn't have the footprint that I do and I process 99.99% of the APRS traffic in the area when my iGate is working. |