Re: Igate verification
Look under Enables / View Log for any IGate* logs. Bring each of those up and enable it. One of them should tell you whether or not packets are being gated to the APRS-IS.
However, those are not "CQ" packets from the ISS. That's actually the ToCall or UnProto piece. The packet is from RS0ISS (the first part before the >) with a destination (ToCall/UnProto) of CQ (the part after the > until either a comma or colon). It has an empty path (colon immediately follows ToCall with no commas) and is actually a status packet (the > after the colon). Therefore it has no location (the ISS never actually says where it is), so it will show up on your map at 0,0 or at the Null Island.
But one of the IGate* trace logs should be able to answer your question.
Well, sort of. Your question was whether the packet is "reaching aprs.fi", but that is not under APRSIS32's direct control. APRSIS32 is only responsible for delivering gated packets to your immediate upstream (directly connected) APRS-IS server. Whether your packet actually gets distributed, and how far, through the APRS-IS is dependent on timing and the duplicate suppression rules of the APRS-IS servers.
A quick check at https://aprs.fi/?c=raw&call=RS0ISS&limit=1000&view=normal doesn't show anything from VU3NUF, which I assume (possibly incorrectly) is the callsign under which you are running APRSIS32?
Remember, aprs.fi is simply (albeit quite complex actually) a
database capturing and displaying data from the APRS-IS as well as
several other sources. It is NOT the APRS-IS network.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 4/16/2020 10:55 AM, Yatharth Verma via groups.io wrote: