Re: Not Receiving Reports from WXSVR-AU
Ok, let me see if I have this setup correct. Your APRSIS32 instance is called VK3YPE and talks through Direwolf to a radio. VK3YPE has no APRS-IS access itself. Correct so far? I tried to confirm this via aprs.fi's raw packets, but apparently you've changed it to VK3YPE-15 sometime yesterday.
It appears that VK3RSA-1 gates your packets to the APRS-IS receiving them simplex (no hops used). VK3RSA-1 has a ToCall of APMI04 which would make it a MicroSat. http://www.aprs.org/aprs11/tocalls.txt says "APMIxx SQ3PLX http://microsat.com.pl/"
In your example that worked, VK3RSA-1 is the source of the 3rd party packet containing the response message from WXBOT.
If all this is true, and you never receive any response from WXSVR-AU on RF, then I would have to say that the IGate functionality in the VK3RSA-1's MicroSat is defective and is not forwarding messages coming from non-AX.25 -SSIDs.
As a possible way to prove or deny this assumption, try sending a callsign lookup to WHO-15 and WHO-IS. Both of these are implemented in a single APRS-IS-based server. If you get a response from WHO-15 but not from WHO-IS, then it would definitely seem to indicate an IGate issue.Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 11/21/2020 7:02 PM, Peter VK3PYE wrote:
Hi Lynn ... here are a couple of screen grabs from the Direwolf window, that I hope can help you ...