IGate question


N5ODX
 

I have been reading the posts in Ref to "IGate" contained on this great site. Having said that I am still a bit lost.
Here is my operating station:
1 Yaesu FTM440XGR
functioning as an Igate,  it works well but only the first packet is shown,  I'm thinking the IGate looks more than one packet from same call is 
dup.  No tail is shown just the stationary symbol  
Is there a method to pass more than one packet? If so how?


Lynn Deffenbaugh
 

First, can you tell me what an FTM440XGR is?  Or is that an FTM-400 XGR with a typo?

Second, describe the connections and port type that you are using in APRSISCE/32.

Third, provide the exact callsign-SSID that you have configured into the radio and also what is configured into APRSIS32.

Fourth, where are you looking that seems to be showing only the "first packet"?  And what specific callsign-SSID is that packet for?

Fifth, are you aware of the de-duplication process that is inherent in the APRS-IS network?

Complete and detailed answers to these questions may help us to understand enough to answer your question.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/16/2022 7:24 PM, N5ODX wrote:

I have been reading the posts in Ref to "IGate" contained on this great site. Having said that I am still a bit lost.
Here is my operating station:
1 Yaesu FTM440XGR
functioning as an Igate,  it works well but only the first packet is shown,  I'm thinking the IGate looks more than one packet from same call is 
dup.  No tail is shown just the stationary symbol  
Is there a method to pass more than one packet? If so how?


Lynn Deffenbaugh
 

I should have also asked if your callsign is N5ODX as your humanly-readable name shows, or KG4ODX as is shown in your gmail address?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/16/2022 7:24 PM, N5ODX wrote:

I have been reading the posts in Ref to "IGate" contained on this great site. Having said that I am still a bit lost.
Here is my operating station:
1 Yaesu FTM440XGR
functioning as an Igate,  it works well but only the first packet is shown,  I'm thinking the IGate looks more than one packet from same call is 
dup.  No tail is shown just the stationary symbol  
Is there a method to pass more than one packet? If so how?


N5ODX
 

MY CALL IS N5ODX,  my email is BILL.KG4ODX@...
MY SSID IS N5ODX-10
THE RADIO IS a Yaesu FTM400XDR
THE PACKET:  An RF packet to and through the IGate
THE CABLE: cable from the FTM400XDR  to my laptop, this is the programing cable that came with FTM400XDR
FITH: yes I am


N5ODX
 

Thanks for the interest in helping,  but I found the issue and now it's tracking 


Lynn Deffenbaugh
 

Ok, a few more questions:

Why do you have 3 RF ports configured, only one of which is working?  And why do you have an NMEA port configured which is also failing to open?  I don't believe the FTM-400 passes GPS data through to the connected PC.  You need to disable and delete the non-functioning and duplicate ports.

So, we're talking about your FYM400XDR port which is of type FTM350v1.3(RO) and supposedly receives data via the programming cable, presumably via a serial port on the PC.

Can you enable the trace log called Port(FYM400XDR) and monitor it while packets are being received?  It may tell us what is going on.

Do the same for the IGate trace log and IGate(Not) as well just for good measure.

Are you in a fairly quiet APRS RF neighborhood?  I ask this because nothing has been heard by any of your RF ports in the past 30 minutes and the hourly gating rates over the past 8 hours are fairly low.  But yet your N5ODX-10 is transmitting approximately 2 packets per minute to the APRS-IS.

N5ODX-10 via T2OSAKA+
HeardBy: BLKWTR N5LEA POTOSI KC5HNH-7 KC5MVZ-2 KC5MVZ-8 WAYSID
Hearing: KC5MVZ-2 N5ODX-9
I+G: 80+0 124+0 150+12 106+77 106+12 102+0 52+2 74+0

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  Here's what I learned of your N5ODX-10 station via APRS message queries:

19:34:56  New Chat Between KJ4ERJ and N5ODX-10 on 2022-07-16
19:34:58> ?IGATE
19:35:00< IGate[1/4] No IGate Activity Receive-Only! (*2-19:35:00)
        < IGate[2/4] FYM400XDR[FTM350v1.3(RO)] Receive-Only+ (*2-19:35:00)
        < DX=1*N5ODX-9(6mi@269°) (*2-19:35:00)
        < IGate[3/4] RADIO[Simply(KISS)] Bi-Directional (*2-19:35:00)
        < IGate[4/4] RADIO 1[FTM350v1.3(RO)] Receive-Only (*2-19:35:00)
19:35:16> ?aprss
19:35:17< Ports[1/5] 07-16 13:30:13 APRS-IS OK 49 52 45 45 45 18 36 44 /hr (*2-19:35:18)
        < Ports[2/5] 07-16 18:34:04 FYM400XDR OK 0 4 28 4 0 1 0 32 /hr+ (*2-19:35:18)
19:35:18< Ports[3/5] 07-16 18:34:11 NMEA Open (*2-19:35:18)
        < Ports[4/5] 07-16 18:34:13 RADIO Open (*2-19:35:18)
        < Ports[5/5] 07-16 18:33:26 RADIO 1 Delay (*2-19:35:18)
19:35:41> ?aprsh *
19:35:42< Nothing Heard via RF (*2-19:35:42)

On 7/16/2022 8:15 PM, N5ODX wrote:

MY CALL IS N5ODX,  my email is BILL.KG4ODX@...
MY SSID IS N5ODX-10
THE RADIO IS a Yaesu FTM400XDR
THE PACKET:  An RF packet to and through the IGate
THE CABLE: cable from the FTM400XDR  to my laptop, this is the programing cable that came with FTM400XDR
FITH: yes I am


Lynn Deffenbaugh
 

Can you share what the issue was so we have better questions to ask the next time it happens to someone?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/16/2022 8:38 PM, N5ODX wrote:

Thanks for the interest in helping,  but I found the issue and now it's tracking 


N5ODX
 

We are in a very remote area,  the problem was that it appeared the radio/system was not tracking.  It may have been I just wasn't zoomed in far enough.  At this point, I believe it was P.I.C.N.I.C.
"Problem in Chair not in Computer"  Thanks again and 73


Lynn Deffenbaugh
 

A software support specialist friend of mine called it a PBKC -  "Problem Between the Keyboard and the Chair"!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/17/2022 9:51 AM, N5ODX wrote:

We are in a very remote area,  the problem was that it appeared the radio/system was not tracking.  It may have been I just wasn't zoomed in far enough.  At this point, I believe it was P.I.C.N.I.C.
"Problem in Chair not in Computer"  Thanks again and 73


Mark, KE6BB
 

I have always said it was due to "A loose nut on the mouse" or "A loose nut on the keyboard." Same "loose nut" actually.

Sorry for the sudden pop-up. I'm outta here!

Mark
KE6BB


On July 17, 2022 7:45:39 AM PDT, Lynn Deffenbaugh <kj4erj@...> wrote:

A software support specialist friend of mine called it a PBKC -  "Problem Between the Keyboard and the Chair"!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/17/2022 9:51 AM, N5ODX wrote:
We are in a very remote area,  the problem was that it appeared the radio/system was not tracking.  It may have been I just wasn't zoomed in far enough.  At this point, I believe it was P.I.C.N.I.C.
"Problem in Chair not in Computer"  Thanks again and 73


N5ODX
 

:) lol

On Sun, Jul 17, 2022 at 10:21 AM Mark, KE6BB via groups.io <rv6amark=yahoo.com@groups.io> wrote:
I have always said it was due to "A loose nut on the mouse" or "A loose nut on the keyboard." Same "loose nut" actually.

Sorry for the sudden pop-up. I'm outta here!

Mark
KE6BB


On July 17, 2022 7:45:39 AM PDT, Lynn Deffenbaugh <kj4erj@...> wrote:

A software support specialist friend of mine called it a PBKC -  "Problem Between the Keyboard and the Chair"!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 7/17/2022 9:51 AM, N5ODX wrote:
We are in a very remote area,  the problem was that it appeared the radio/system was not tracking.  It may have been I just wasn't zoomed in far enough.  At this point, I believe it was P.I.C.N.I.C.
"Problem in Chair not in Computer"  Thanks again and 73


Virus-free. www.avg.com