Andrew,

I dont know if you got my 2 Pmails but Iam getting the feel that they are not getting through for some reason.? Ive also replied on the group under the original topic but I dont see those come through in the Digest. So its frustrating things somewhat.
Did you get any Pmails with attachments on this issue with the FTM400 ?

Tony? VK5AH

Ive just sent you another Pmail and some attachments with findings Andrew

Regards? Tony VK5AH

Ok done .? Hope you get the Pmail and all the attachments . Ive given you as much info as I can.

Tony VK5AH

开云体育

That's strange. I wonder why just sending the revised PHG doesn't work.?

开云体育

Hmmm.... that is odd. Can you go into File->Configuration->Expert Mode and ensure on the General tab that AX.25 logging is enabled and using CSV format, then privately send me a sample log file with some of the traffic you are receiving?

Andrew . I hear you . The radio is running UTC +9.5 Hrs . South Australia time or Australian Central Standard time I have tried running it on UTC and it does not help . The PC is running the same time zone on Win10. I have opened the monitor window for the FTM400 Port and looked at the time stamps and they look correct in local time and the Date is also correct. I looked at all this already but I have just checked it again.

So it just does not make sense. Here is what I have found.

1: I never noticed this issue until I disabled all other Ports on YAAC . APRS-IS and AGW Port . Once these are enabled it tends not to show itself as much of the traffic is duplicated.
I was thinking of running with Yaac in the car with FTM400 and a Touch screen on a Pi so APRS-IS and a RF Port on AGW would not be present. Hence I disabled the other Ports to see how it would work in the car.
2: The initial Packet from the Radio that Yaac sees from itself (The first DigiPeat of its own Posit) is correct and shows in the Station/Objects list as heard less than a minute ago when Iook for it.
Subsequent Posits cancel this and show like all other traffic as 9+ hours old in RED .
3: I have found living in this peculiar Time Zone is troublesome . Some software and Modem Firmware does not support it correctly if at all even though it says it does. It often seems to be the 30 min offset that causes issues so Modems end up running on Eastern Standard time 30mins in front of us. Some software (Often US written) cant cope with the idea of being East of the Greenwich +138 degrees and therefore ahead of UTC time.

At present I cant see why its doing this. Before I got the Time/Date format correct in the Yaac Port setup it was showing the Stations/Objects as being over 5000 Days old. I thought I was on the jackpot when I got the Date/Time formats to match but its still out by over 9 Hrs on the station/objects list.

Thanks for the suggestions
Tony VK5AH

Greetings:

Regarding your packet timestamp issues, what timezone is the time on the radio set to, and what timezone is the computer running YAAC set to? And what _time_ is the radio set to? YAAC uses the computer's time-zone configuration, and the present implementation of the Yaesu port driver in YAAC assumes that the packet timestamps reported by the radio are also in the computer's local time zone (whatever that happens to be), so it converts them from computer-local time-zone to UTC for internal processing, and converts them back to local time zone for display on the YAAC windows. If the radios are reporting a different time zone than the computer is expecting, then the computer will be confused. :-)

Try opening the Test Port window on your Yaesu port, and see whether the timestamps coming in from the radio look reasonable (they are in plain text, so are readable in the Test Port window).

Yes, that premature expiration could happen if the packets are being received with an incorrectly decoded timestamp. The vicinity plotting would happen if the first packet heard after the expiration was not a position report, so YAAC had to guess where the stations are.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of wavetel1 <wavetel@...>
Sent: Saturday, May 7, 2022 9:10 PM
To: [email protected]
Subject: [yaac-users] Yaac and FTM400 XDR

Hi all. Its been a while since I posted anything but I have been watching. Ive recently got myself up and running with a FTM400XDR which has given me a new burst of interest and Ive started using Yaac again.
It took some reading but I got it going on a Yaac Port with APRS after figuring out the Time stamp format issues. Some good Previous Posts and Web pages on this I found.
One thing that still had me a bit stumped is the AGE issue with the stations appearing on the Map. I have my 400 set to Local time so the stations appear in the Stations/Objects list Last Heard as Red and 9-10 Hrs old. We are UTC Plus 9.5 Hrs currently in this time zone.

Not sure what to do with this situation but the effect is that stations frequently disappear of the Map and then reappear again on a vicinity plot elsewhere when they previously had a definite posit less than an hour ago.
Do I need to run the Radio in UTC time ? As if/when I do it makes for a APRS station list on the radio that is hard to make sense of.
As yet I have not found a setting in YaaC that allows me to explain a TimeZone or Daylight Savings setting.

Any suggestions would be great. Tony VK5AH Adelaide South Australia

Hi all.? Its been a while since I posted anything but I have been watching. Ive recently got myself up and running with a FTM400XDR which has given me a new burst of interest and Ive started using Yaac again.
It took some reading but I got it going on a Yaac Port with APRS after figuring out the Time stamp format issues. Some good Previous Posts and Web pages on this I found.
One thing that still had me a bit stumped is the AGE issue with the stations appearing on the Map. I have my 400 set to Local time so the stations appear in the Stations/Objects list Last Heard as Red and 9-10 Hrs old. We are UTC Plus 9.5 Hrs currently in this time zone.

Not sure what to do with this situation but the effect is that stations frequently disappear of the Map and then reappear again on a vicinity plot elsewhere when they previously had a definite posit less than an hour ago.
Do I need to run the Radio in UTC time ? As if/when I do it makes for a APRS station list on the radio that is hard to make sense of.
As yet I have not found a setting in YaaC that allows me to explain a TimeZone or Daylight Savings setting.

Any suggestions would be great.? Tony? VK5AH? Adelaide South Australia

Should have sent the official one - my bad
--
Cheers and 73 - Jon N7UV

Hi Andrew,

Thanks for the heads up on the update. Honestly, I haven't touched anything for over a month due to health issues. I need to pull the gear out of the truck and get it on the bench to change the screen orientation, calibrate the touchscreen, and update things. Hopefully, I will be able to get back to that in a week or two.

73,
Michael WA7SKG

Andrew P. wrote on 5/7/22 8:24 AM:

One other note about this is that the USGS topographic data isn't updated that often (every 10 years or so), so unless you've had a new volcano or a major earthquake in your area, you probably don't need to update the topographic data that often.

OpenStreetMap data, on the other hand, is updated constantly (in time; sporadically in geography) as people add new data and corrections where it is of interest to them. So it makes more sense to bring that in more frequently (especially if a new development with new streets was recently built in your area); of course, someone has to _enter_ that new data into OpenStreetMap before it will be available to the public. For example, the new high-density housing built in the next town from me is only partially recorded in OpenStreetMap, because no one has drawn the newest buildings into the dataset yet.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Friday, May 6, 2022 10:36 PM
To: [email protected]
Subject: Re: [yaac-users] Downloading tiles

You get that message when you try to download Topographic (terrain elevation) tiles from the US Geological Survey, because they require you to have a (free) account there to download data. You don't need a login when you try to download OpenStreetMap street data from the YAAC author's website.

If you don't need terrain data, don't try to download it, and you won't get the prompt.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jon Adams <n7uv.jon@...>
Sent: Friday, May 6, 2022 10:31 PM
To: [email protected]
Subject: Re: [yaac-users] Downloading tiles

Me too! Me too!! I’m surprised that no one has yet chimed in on this.
--
Cheers and 73 - Jon N7UV

Hi, Michael.

Just checking in to see how your mobile setup is working. I also wanted to let you know about the new version of the smallscreen plugin (just released May 6th) that allows cellphone-style scrolling of the table views with a touchscreen, by just pressing on the table and dragging it up or down (or left or right) with your fingertip.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
Sent: Tuesday, April 5, 2022 12:27 AM

Get everything installed in the truck. Headed out for a weekend trip,
fired it up and all worked fine.
Until I put on my sunglasses.
With my vision issues I need to wear polarized sunglasses. Blank screen.

No I have to remount the monitor in portrait instead of landscape and
figure out how to rotate the display.

Still have to do all the tweaks to get small screen to come up
automatically and keep me centered. I did it on the main screen, I was
surprised that did not carry over to the small screen map.

I'm getting there, bit by bit.

Michael WA7SKG

next beta build#174 of YAAC ("Yet Another APRS Client"), created 2022-May-06

downloadable from
or

changes and updates include:
1. optimize topographic contour line rendering some more. Still not fast enough
but it's better than it was.
2. tune OpenStreetMap importing a little more.
3. have Edit Filter dialog indicate which particular filters are filtering out
packets.
4. make the Tracked Station table viewable from any other window, not just
map windows, and allow editing station non-responsiveness timer from the
table instead of only from the popup menu entry for editing timeouts.
5. for KISS-over-TCP ports, don't send the Fldigi-specific hardware command
messages if the original "TNC" hardware command doesn't get back a report
that Fldigi is actually being used as the KISS-over-TCP TNC.
6. add a couple more amenity types to the OpenStreetMap importer.
7. add functionality that will be needed in a future version of the OpenStreetMap
importer, so that there won't be unusable errors for users of this version
of YAAC when map data using the new functionality becomes available.
8. fix the AREDN objects plugin to not report errors for querying discovered
nodes on the AREDN network that don't have configured positions.
9. fix Small Screen plugin so touch screen can be used to scroll the tabular
views (Raw Packets, Station List, Text Messages) the way they are scrolled
on cellphone touchscreens.

You get that message when you try to download Topographic (terrain elevation) tiles from the US Geological Survey, because they require you to have a (free) account there to download data. You don't need a login when you try to download OpenStreetMap street data from the YAAC author's website.

If you don't need terrain data, don't try to download it, and you won't get the prompt.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jon Adams <n7uv.jon@...>
Sent: Friday, May 6, 2022 10:31 PM
To: [email protected]
Subject: Re: [yaac-users] Downloading tiles

Me too! Me too!! I’m surprised that no one has yet chimed in on this.
--
Cheers and 73 - Jon N7UV

Me too! Me too!! I’m surprised that no one has yet chimed in on this.
--
Cheers and 73 - Jon N7UV

Meant to send this to the group...
________________________________________

How long have you been listening to these stations? YAAC implements a feature called "vicinity plotting", where, for stations that are transmitting, but haven't yet transmitted a _valid_ position report, Mic-E report, or status message with Maidenhead position, YAAC guesses where the station might be based on the location of the first digipeater or I-gate (if their position is already known) to forward the station's packets. If the original station is sending _invalid_ position reports, they don't count for accurate location, as YAAC can't decode them.

As to why aprs.fi can properly locate those stations, that could be for either of two reasons:

1. aprs.fi has more capability to decode more invalid formats than YAAC does (assuming the stations are sending invalid-format position reports).

2. aprs.fi has a long-term database of history, and may be using the recorded last decodable position for those callsign-SSID combinations.

Note that YAAC can also use vicinity plotting in reverse to guesstimate the location of non-position-beaconing ("stealth") digipeaters that only meet their beaconing requirements by embedding their callsigns in the digipeat path (TRACE mode).