Well.... as a crude way to check my RF (knowing full well aprs.fi is not completely reliable). But with the links you sent me that show my statistics I guess I could enable both the APRS-IS port and my KISS port for messages and beacons.
I do like the idea of the GATE messages going over the APRS-IS port only. Since they are for interfacing to the internet it makes sense to me if it isn't a major deal to implement.
--- In firstname.lastname@example.org, "Lynn W Deffenbaugh (Mr)" wrote:
> What do you have checked on your Configure / Ports / APRS-IS dialog? I
> suspect you don't have Messages nor Beaconing enabled. Messages because
> I tried some remote queries and got no answers. And Beaconing
> suppresses not only the beacons, but also the status and capability
> (IGATE) packets from being allowed to go to the APRS-IS. And the IGATE
> packets ONLY try to go to the -IS if you have it enabled.
> Maybe I need to change that to force the IGATE packets out over RF if
> you have Beaconing disabled on the APRS-IS port...
> So, exactly why do you have Beaconing disabled on your APRS-IS port?
> Remember, APRS is not suitable for propagation detection (mostly because
> of the dupe suppression on the APRS-IS), so why force the beacons to
> only go via RF?
> Lynn (D) - KJ4ERJ -Author of APRSISCE for Windows Mobile and Win32
> On 1/30/2013 10:09 PM, Jim in Downers Grove wrote:
> > Another newbie question....
> > I see in my transmit log that the IGATE message is generated and is routed to IS but when I look at raw packets on aprs.fi (I know not the most reliable) I never see these messages, ever. I do see them for other stations though, just not mine.
> > Is there a configuration that I missed?
> > Jim