One thing to remember about this experiment, APRS packets are a UI unconnected broadcast and you are not guaranteed delivery of the pack to the other end even if you do use the specific path method

Got it thank you! Dan W5DMH

Transmit pressure. When it gets to the end, it should transmit. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 1/7/2022 3:47 PM, Dan

What is the colored bar between the Port / Time and the Scroller list indicating?

Thanks Lynn, For the record I am using Xastir at this moment because the path is really easy to change for this testing . I can look at the direwolf output which should be completely raw. Dan W5DMH

It may be that Xastir is filtering the NOGATE before showing you the log of received packets. You need to be looking at the actual RF received traffic to know if you copied the digipeat.

Yes I'm running direwolf connected to an FT-857d connected to a full wave 2m ant on the top of a 55ft tower...I have internet turned off for this testing. Dan W5DMH

NOGATE means that your packet will not be forwarded to the APRS-IS by compliant I-gates. Do NOT look at aprs.fi or other APRS-IS feeds for your information. The APRS-IS feed is heavily filtered, so

Maybe I am looking at success all wrong .... I am first looking at the live traffic in Xastir to see if the first digi in my path string is receiving it and repeating it. I am not seeing a repeat

No I am putting it as the last entry at the end....typical path looks like: MAYVIL,JAMTWP,K8FSU,NOGATE Dan W5DMH

The reason is not so lofty....my buddy has a digi/igate at his location however he is in an area that routinely loses internet and only has one wide digi that can reach him (and that is questionable)

Dan, Where are you putting NOGATE in your outbound path? Put it at the end. I suspect you have it as the first hop. Digipeaters look at the first unused hop request. If NOGATE is the first hop

Rob, You can be sure of the path taken by observing the used path elements in the received packet. Of course this means actually looking at the packets received, but if Dan is interested in

I'm struggling with this....NOGATE seems to cause the digi to ignore the packet When I remove NOGATE, even though I have a specified path, the local digi will repeat it anyway I tried RFONLY too and

Dan, Like Rob said, if your buddy can hear the third digi, don’t put more path elements in the outbound path. You have a specific station you are aiming to contact, so there is no need to flood an

Probably a good idea, if you want it to be RF only. Otherwise, you can't be sure. Rob KB8RCO

Should I have NOGATE in my path to insure it doesn't get gated at the first DIGI ? (These are big wide area digi's that all igate also) Dan W5DMH

If you reach your destination aftrr K8FSU, you don't need any more path elements - WIDE2-1 will only add to RF. Now the catch. If any of those stations don't DIGI your packet, it fails. Including

So I have MAYVIL close to me and I know MAYVIL can reach JAMTWP and I know JAMTWP can reach K8FSU and I know K8FSU can reach my buddy KE8OHG So my path should be simply "MAYVIL,JAMTWP, K8FSU,

Morning Dan, Yes it will. you can also do it for specific objects. Keep in mind that any station that can hear one of the stations in that path will hear it, but it should only be repeated by the