Oh, and this whole thing comes down to the fundamental statement that: APRS-IS is NOT a suitable tool for determining RF propagation of APRS packets. Lynn (D)Message 1 of 34 , Jan 9View SourceOh, and this whole thing comes down to the fundamental statement that:
APRS-IS is NOT a suitable tool for determining RF propagation of APRS packets.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 1/9/2013 8:53 PM, Lynn W Deffenbaugh (Mr) wrote:
But to reinforce the statements about concurrent APRS-IS and RF beaconing, if you look at http://aprs.fi/?c=raw&call=VA6OO you will notice that every packet was directly injected via TCPIP*. A station that beacons to RF and APRS-IS simultaneously should never be observed via RF when looking at anything drawing from the APRS-IS feed. The directly injected packet should always arrive before any RF copy of that packet.
APRSISCE/32 trace logs will show the reception of digipeats of your RF packet, and the Transmit log should show IS+RF on that packet, but the APRS-IS, as was stated earlier, will only pass the FIRST copy of any given packet within a 30 second window.
Lynn (D) - KJ4ERJ -Author of APRSISCE for Windows Mobile and Win32
On 1/9/2013 7:02 PM, Tony VE6MVP wrote:
At 03:54 PM 2013-01-09, Jim in Downers Grove wrote:
When I go to aprs.fi and look at stations that heard me directly, there are none since I've switched programs.
You appear to be using KC9AOP-15 with APRSIS32. Your igate has heard a few APRS beacons today and have beat the other igates into the APRSIS network. http://aprs.fi/info/a/KC9AOP-15 and down at the Stations heard directly station although not a lot of them.
When I look at http://aprs.fi/info/a/KC9VIX which is a nearby digi it last heard your station directly on the 4th of January. So what did you change then? <smile>
When my igate beacons, on the APRSIS screen on the left hand side, I can see a star * and usually a 2 behind it. Such as VA6OO*2. This tells me that two area digis heard my beacon and my igate in turn heard those beacons. (I can usually hear four digis when there is nearby APRS traffic but two of the four beacons are missed because the TNC in the D710 radio takes about 400 msec to switch out of TNC transmit mode..) When I go to my port log I see the following:
Port(KwdD710):2013-01-09T23:43:36.938 Kenwood:VA6OO>APWW10,VERMLN*,WIDE2-1:@234333h5321.29NT11050.76W&PHG7160APRS-IS32, Igate, Msg capable, tony @...
So I can see from the packet that the VERMLN digi saw my beacon, digi'd it and now my igate received it.
My point being that once you are successfully beaconing you should also be seeing the same kind of beacons back from your local digis.
WOW! I finally got some time to spend with the links you noted below, and found them quite helpful. I have tried to do some of this manually from aprs.fiMessage 34 of 34 , Feb 1View SourceWOW! I finally got some time to spend with the links you noted below, and found them quite helpful. I have tried to do some of this manually from aprs.fi etc., but the accuracy is limited for the reasons previously noted. When I went to your webpages, there the data was...in nice graphs and tabular formats.
I can hardly wait for the first development release that starts to build "some of this capability directly into APRSISCE/32." I have never seen this type of capability built into a software package, but I must qualify my comment in that I don't use other APRS software anymore.
--- In email@example.com, "Lynn W Deffenbaugh (Mr)" wrote:
> >> That said, you might want to take a look at:
> >> http://tinyurl.com/IGATE-KC9AOP-15 - Table of stations recently heard
> >> and hearing you
> >> and
> >> http://tinyurl.com/bkr27hn - More details about what your IGate is hearing
> >> Note that these graphs are generated from data not taken from the
> >> APRS-IS, but from direct, non-dupe-suppressed feeds of RF packets heard
> >> by APRSISCE/32 instances around the planet. I will eventually build
> >> some of this capability directly into APRSISCE/32.