<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:13px"><div><span></span></div><div id="yui_3_16_0_1_1433624546349_40963" dir="ltr">Then why does the timestamp on findu match the time the beacon was received back and not the time it was actually sent. I have noticed this behavior many times over the years using various Igate software programs. I can also duplicate the problem anytime.</div><div id="yui_3_16_0_1_1433624546349_41049" dir="ltr"><br></div><div id="yui_3_16_0_1_1433624546349_41441" dir="ltr">Back years ago when I first discovered the problem I did a test. I configured my mobile station to the same ssid as my igate and drove to a digi that was about 25 miles away. Using only a few miliwatts of power I sent some beacons that my igate couldn't hear direct, only the digi. The beacons appeared as if my igate had sent them directly to the aprs-is with no sign of the digi.</div><div id="yui_3_16_0_1_1433624546349_41757" dir="ltr"><br></div><div id="yui_3_16_0_1_1433624546349_41918" dir="ltr">I don't know if it is an igate problem or an aprs-is problem but I see it happen all the time. I can understand it being considered a duplicate, but why does the path get changed and made to look like it was sent direct to the aprs-is when it wasn't? And the example beacon WAS sent out RF only.</div><div id="yui_3_16_0_1_1433624546349_41930" dir="ltr"><br></div><div id="yui_3_16_0_1_1433624546349_41951" dir="ltr">Max KG4PID<br> </div><div id="yui_3_16_0_1_1433624546349_40634" style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 13px;"> <div id="yui_3_16_0_1_1433624546349_40633" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1433624546349_40632" dir="ltr"> <hr size="1"> <font id="yui_3_16_0_1_1433624546349_40635" face="Arial" size="2"> <b><span style="font-weight: bold;">From:</span></b> Steve Dimse via aprssig <aprssig@tapr.org><br> <b><span style="font-weight: bold;">To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, June 7, 2015 12:38 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [aprssig] PSAT & igating and Optimum antenna<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1433624546349_40636"><br><br clear="none">On Jun 7, 2015, at 9:55 AM, Max Harper via aprssig <<a href="mailto:aprssig@tapr.org" shape="rect" ymailto="mailto:aprssig@tapr.org">aprssig@tapr.org</a>> wrote:<br clear="none"><br clear="none">> Another problem (if you ask me) is that when you send a beacon, and that beacon gets digi'ed, and your own station recieves it back and igates it, the station that digi'ed it gets stripped out of the packet.<br clear="none">> This beacon is set to go out via 'RF only' but looks like is was sent direct to the APRS-IS. Also note the time stamp at the beginning of the payload as well as the timestamp from findu showing 5 seconds difference. There was one or more digi's in there<br clear="none">> <br clear="none">> 20150607070734,KG4PID-14>APRX28,TCPIP*,qAC,T2TEXAS:/070729h3417.45N/08742.32W#PHG7250 Bear Creek, Al<br clear="none"><br clear="none">This is the dup check issue already discussed. Regardless of whether you intended to send it RF only, if the path says TCPIP* it was sent directly to the APRS-IS, it was not IGated from RF. The q construct confirms it was a direct to internet packet. The path was not changed, it was the direct to internet packet which reached findU first (no surprise), somewhere along the line any RF IGated packets were removed by dup check.<br clear="none"><br clear="none">You are connected to a tier 2 server, so the packet travelled through a number of servers before it got to findU, each can add a few tenths of a second of latency. The order in which a program performs tasks also gets involved. findU timestamps are not a reliable way to determine RF propagation time, or in this case to try to prove RF propagation occurred. <br clear="none"><br clear="none">Steve K4HG<div class="qtdSeparateBR"><br><br></div><div class="yqt9432989454" id="yqtfd52614"><br clear="none">_______________________________________________<br clear="none">aprssig mailing list<br clear="none"><a href="mailto:aprssig@tapr.org" shape="rect" ymailto="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br clear="none"><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank" shape="rect">http://www.tapr.org/mailman/listinfo/aprssig</a><br clear="none"></div><br><br></div> </div> </div> </div></body></html>