Keyboard Shortcuts
Likes
Search
APRS iGate stopped working!
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.
What steps should I take to resolve this?? I also did a test transmission to a repeater across Lake Michigan to ensure it wasn't the coax or the antenna and I was able to raise the repeater with an S10 signal returned. Thanks! |
Not sure how to answer this with so little information.
I am pretty sure the RED on the far left is because you are zoomed in to "maximum".??As you zoom out, the color will change. ? ?The reason only 2 objects are on screen and no map detail?is also because of how "zoomed in" you are. ? ?So from your comments, I would guess the screen was zoomed in by accident. ? ?The next logical question would be what else changed "unexpectedly". Why do you think your IGATE isn't working? ? ?Is the scroller working? ------- Robert Giuliano KB8RCO |
The scroller will turn red if you have "Freeze on click" configured, and you click on the scroller. No incoming messages wil display. On Wed, Apr 24, 2024 at 10:11?AM Rob Giuliano via <kb8rco=[email protected]> wrote: Not sure how to answer this with so little information. |
I should have mentioned, click anywhere outside the scroller to release it. On Wed, Apr 24, 2024 at 11:34?AM Ben Miller via <bmilleng=[email protected]> wrote:
|
I just noticed your screenshot, so ignore my answer. The other response was correct ,that you are zoomed in. The bar gets shorter and changes color as you zoom out. On Wed, Apr 24, 2024 at 11:36?AM Ben Miller via <bmilleng=[email protected]> wrote:
|
Thanks!? Does that mean that no APRS packets will be iGated by my computer into the internet and therefore will not show up on ? Jon Kreski AB9NN - FCC Ham Radio Call Sign (920) 931 - 5511 - Cell (231)3 83 - 4425 - Home Jon E. Kreski - is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to , , or . On Wed, Apr 24, 2024 at 12:34?PM Ben Miller via <bmilleng=[email protected]> wrote:
|
¿ªÔÆÌåÓýRob, I interpreted the OP¡¯s image at miles, I don¡¯t see a metric notation anywhere. Yeah, where did I come up with 22 miles. LOL Perhaps I¡¯m confusing posts. ? Anyhoo, my zooming in/out results in SAE measurements. ? ? From: [email protected] <[email protected]> On Behalf Of Rob Giuliano via groups.io
Sent: Wednesday, April 24, 2024 3:40 PM To: [email protected] Subject: Re: [APRSISCE] APRS iGate stopped working! ? The screen shot I saw had 4m (4 meters) for the range. |
¿ªÔÆÌåÓýJudging by the messages I got back when I queried you station it looks like you've lost connection with your 857. What is the connection to that??
I'm gonna guess it's the tt4 that you mentioned in the tiny trak group. Is the yellow light flashing at all when packets are heard??
It may need power cycled. There is a known issue with the tt4 randomly locking up on bad packets but they have not been identified on what packets they are.?
My digi gate and my buddy's digi both power cycle every night and we have not noticed the lockups since we started the cycles.?
KB3KBR Greg. Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: AB9NN - Jon Kreski <jkreski@...>
Date: 4/24/24 10:33 (GMT-05:00)
Subject: [APRSISCE] APRS iGate stopped working!
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.
What steps should I take to resolve this?? I also did a test transmission to a repeater across Lake Michigan to ensure it wasn't the coax or the antenna and I was able to raise the repeater with an S10 signal returned. Thanks! |
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. |
On Wed, Apr 24, 2024 at 09:25 PM, Lynn Deffenbaugh wrote:
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??Thanks so much!? I realize that APRS.FI is the place to check to see if my station is iGating.? When my station is working properly it iGates 99.99% of the APRS traffic in our rural area because of the footprint of my antenna, it's gain and the speed of my computer and internet connection.? So I know it's not working.? I have checked the following: *? Antenna and coax - I get an S10 meter reading when I raise the repeater all the way across Lake Michigan into Wisconsin from NW Lower Michigan. *? Radio - Yeasu FTM400XDR.? I have both A and B on 144.390 on simplex with lowest squelch.? I see and hear the APRS packets being processed. *? TinyTrak4 - This is not new and as I see APRS traffic on the radio I see the TT4 doing it's thing with lights of various colors flashing as they should be. *? Ports - I have a KISS port that I configured months ago and did no change.? In APRSIS32 I checked the baud rate and it is 19200 as it should be. *? TinyTrak4 - I used TeraTerm Pro and accessed the software on the device.? It is also configured at 19200 as it should be. *? Cables - they have not changed.? I ensured all connections were snug. *? Windows 11 PC connection.? I used Device Manager to verify that my TT4 was on port 5.? This matched the APRSIS32 setting.? I unplugged the TT4 and the connection disapeared from device manager. ? ? I plugged the cable back in and the port 5 connection reappeared. *? AB9NN-48 - I selected this as it has a little house icon on APRSIS32 which is what my station is.? Is there something better to use? Obviously something changed but I don't think I conciously changed any settings.? I went through APRSIS32 menus to make sure Internet was enabled and it was checked.? My port looks OK.? Someone said they queried my station thru APRS and it returned that the radio port was not connected.? My port in APRSIS32 is mislabled as FT857d as I used to that that radio and simply didn't change the name when I reconfigured it. Cables have been the same for close to a year.? I have the correct chip(s) in the cables asn I know they worked for a long time and I have not changed them. I have attached as screen shot of my Enables for your reference.? I am thinking that with all the checking I have done it must be some simple little setting that I am miissing.? I will dig into the logs today.? Hope this helps clarify things! |
Lynn Deffenbaugh
¿ªÔÆÌåÓýCan you screen capture the port settings of your RF port and your APRS-IS port??? There are checkboxes in those that affect IGate operation.?? You can also view and enable the various IGate(*) Trace Logs. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 4/28/2024 10:08 AM, AB9NN - Jon
Kreski wrote:
On Wed, Apr 24, 2024 at 09:25 PM, Lynn Deffenbaugh wrote: |
Lynn Deffenbaugh
¿ªÔÆÌåÓýI've attached my APRS monitor logs for your station from both RF reports and -IS gated packet captures for the 20s of April.?? Your AB9NN-48 IS IGating some packets, but on the RF side, it is very intermittent as to when it is copying packets and when it is not sending anything via UDP to my backend logger.? Are you sure everything about your station is stable?? Or do you not run it 24x7? According to
your station last beaconed 12 hours ago.?? And eye-balling the
<IGATE reports, it appears that there are extended periods
where your DIR_CNT and RF_CNT are both zero indicating that
APRSIS32 is not receiving anything from the RF port.?? No packets
= No IGate, obviously.?? And there are also time ranges where an
<IGATE packet wasn't even generated.?? I'd have to look at the
source to remind myself what that might mean, but it may mean that
all of the values are zero. If you double-click the upper left corner box, you should get a "Port Status" window that will show you the packet rates per hour for the most recent (left) 8 hours.?? If your RF port isn't showing any traffic, then by definition, APRSIS32 won't be gating because nothing was received to forward on to the APRS-IS. You'll see a BIG difference between the RF logged packets and the
ones that show your station as gating the first copy of the packet
to the APRS-IS.? I'll leave it as an exercise for the reader to
track down why other directly-received RF packets are not in the
-IS log.?? Likely some other station was faster and gating the
packet.? Maybe a new IGate is up and running in your area? Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 4/28/2024 10:08 AM, AB9NN - Jon
Kreski wrote:
On Wed, Apr 24, 2024 at 09:25 PM, Lynn Deffenbaugh wrote: |
Lynn Deffenbaugh
¿ªÔÆÌåÓýThose look correct.?? Based on the log captures and aprs.fi's raw packet view, it definitely appears that you are having intermittent RF reception (or at least, getting the packets into APRSIS32) and either your instance is not running 24x7 or it is also having APRS-IS connectivity issues.?? The first bit comes from the RF packet capture logs as well as the >IGATE packets from aprs.fi's raw view.?? The last part is inferred by the lack of even beacon packets in aprs.fi's raw packet views for AB9NN-48. For instance, on the 2nd bit, the gap in beacon timestamps at
2024-04-28 20:21:09 EDT:?>APWW11,TCPIP*,qAC,T2YANTAI:>290025zAPRS?iGate?in?Beulah,?Michigan?-?NW?Lower?Michigan 2024-04-29 08:13:44 EDT:?>APWW11,TCPIP*,qAC,T2CSNGRAD:@121811h4437.84N/08604.35W-!INSERVICE! And then the length of time before the
>IGATE status actually reflected RF-received stations:
2024-04-29 08:13:44 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:@121811h4437.84N/08604.35W-!INSERVICE! 2024-04-29 09:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*W8TVI-9(9km@16<0xb0>) 2024-04-29 10:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=2,DX=1*W8TVI-9(9km@16<0xb0>) 2024-04-29 11:07:59 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=3,DIR_CNT=1,RF_CNT=5,DX=1*KD9VQI-10(103km@292<0xb0>) 2024-04-29 12:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=1,DIR_CNT=1,RF_CNT=1 2024-04-29 13:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*KD9VQI-10(103km@292<0xb0>) 2024-04-29 14:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=1*KD9VQI-10(103km@292<0xb0>) 2024-04-29 15:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=2,DIR_CNT=1,RF_CNT=2,DX=1*KD9VQI-10(103km@292<0xb0>) 2024-04-29 16:08:29 EDT: AB9NN-48>APWW11,TCPIP*,qAC,T2CSNGRAD:<IGATE,MSG_CNT=0,LOC_CNT=2,DIR_CNT=0,RF_CNT=2,DX=1*KD9VQI-10(103km@292<0xb0>) And finally, the hourly packet counts I
just got in response to a ?APRSS query.? These are the same hourly
packet counts you can view locally by double-clicking on the upper
left corner of the main APRSIS32 window.
17:00:21 New Chat Between KJ4ERJ and AB9NN-48 on 2024-04-29 17:00:23> ?igate 17:00:24< IGate[1/2] LOC_CNT=10 DIR_CNT=1 RF_CNT=21 (*2-17:00:24) < IGate[2/2] FT857d[Simply(KISS)] Bi-Directional+ (*2-17:00:24) < DX=3*KD9VQI-10(103km@292¡ã) (*2-17:00:24) 17:00:31> ?aprss 17:00:32< Ports[1/2] 04-29 08:18:10 APRS-IS OK 492 482 523 534 561 603 713+ (*2-17:00:32) < 634 /hr (*2-17:00:32) < Ports[2/2] 04-29 08:10:27 FT857d OK 48 38 8 0 0 31 68 24 /hr+ (*2-17:00:32) First, your machine doesn't seem to know
what time it is given that here at 17:00 east coast time it showed
me 08:10 where you are in Michigan.
Second, those two zeros in the middle
tell me that 3 and 4 hours ago, you received zero packets from the
RF port that you called FT857d.?? And 2 hours ago appears
incomplete because it only shows 8 packets in that hour.?? So I
really think you need to look at the RF reception and decoding for
your IGate as the numbers and logs seem to indicate that's where
the problem is.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 4/29/2024 8:56 AM, AB9NN - Jon
Kreski wrote:
Here are the two screen shots requested! |
Thanks so much for the detailed analysis.? Not sure what to think about the time setting.? Time on the PC seems right.? I recall I have a utillity to keep it set via atomic clock.? Not sure of the name of the utility or if it's still running.? I checked the Receive Amp setting on the TT4.? I had it tuned and it was working well but when I monitored the line with TeraTerm Pro I got 1's.? Something closer to 100 is a normal signal.? I reset the amp to a higher level.? That may have been the problem.? I will know in the morning when I go and get the mail and check my APRS track on APRS.FI.? Setting the amp levels on the TinyTrak4 are a bit wonky as with my radio the volume setting of the radio plays a part in it.? The volume may have also been bumped over some time period.? I will let you know if this corrected the problem but for now it looks like it was at least not set correctly...? sigh...
|
On the receive?level, the TinyTrak pot and the radio volume do the? same thing. I generally fix one at a typical level, and then just use the other one to fine tune. Otherwise, they interact and you will be constantly chasing the level. Transmit is only the TinyTrak pot so it is easier. On Mon, Apr 29, 2024 at 6:58?PM AB9NN - Jon Kreski via <jkreski=[email protected]> wrote: Thanks so much for the detailed analysis.? Not sure what to think about the time setting.? Time on the PC seems right.? I recall I have a utillity to keep it set via atomic clock.? Not sure of the name of the utility or if it's still running.? I checked the Receive Amp setting on the TT4.? I had it tuned and it was working well but when I monitored the line with TeraTerm Pro I got 1's.? Something closer to 100 is a normal signal.? I reset the amp to a higher level.? That may have been the problem.? I will know in the morning when I go and get the mail and check my APRS track on .? Setting the amp levels on the TinyTrak4 are a bit wonky as with my radio the volume setting of the radio plays a part in it.? The volume may have also been bumped over some time period.? I will let you know if this corrected the problem but for now it looks like it was at least not set correctly...? sigh... |