Re: FINALLY! next beta build#182 of YAAC
Wow, you've been busy!?? I hope all of your IGate users update to this release ASAP as what you describe in #1 is definitely a critical fix!
And I admire your efforts on doing your own OSM map rendering, but I'm really glad I didn't make that decision early in my client development based on how many updates involve map upgrades and fixes.?? One of these days I might have the time to look at how you do things to see if I might consider a local OSM tile rendering server based on it that users can run locally as a tile source.?? Thinking standalone Android (or Windows) app that uses your configurable OSM rendering engine but behaves like an OSM-compatible (think mod-tile/renderd/apache2) tile server.
Keep up the good work!
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
toggle quoted message
Show quoted text
On 7/12/2023 12:35 AM, Andrew P. wrote: It took a long time to get this build out. There are a lot of changes and cleanups
in this build, but I hope you will appreciate them all. I won't be releasing an updated
map set for a few days because this build of YAAC supports a changed and enhanced
map importing that older versions of YAAC can't handle, so I want this build to be
available before users start complaining their old build of YAAC can't handle the
updated map set.
--------------------------------------------------------------------------------------------
next beta build#182 of YAAC ("Yet Another APRS Client"), created 2023-Jul-11
downloadable from
or
changes and updates include:
1. fix IS-to-RF (transmit) I-gating to use the I-gate's RF port callsign-SSID
and tocall instead of the original station's values in the raw AX.25
frame. This fixes a possible contributor to the APRS flooding noticed on
#APRSThursday.
2. add new utility called WayAnalyzer to help debug issue with OpenStreetMap
importing and rendering.
3. significant logic and performance improvements in importing OpenStreetMap
datasets, though, alas, there is still more work to come.
4. reaarrange the source code so that Maven builds with POM files will actually
work correctly for both the YAAC application and all the currently
supported plugins, with appropriate adjustments to the Ant build.xml
files to work with the new structure.
5. a new Debug plugin which allows dynamically turning on and off debug logging
from the expert-mode Configuration dialog for different supported categories
of logging while YAAC is running. Also some new core API methods on the
DebugCtl class to permit plugins to register new debug logging categories.
6. version update on the JavaHelp library.
7. some code cleanup for the change to Java 8 as minimum supported runtime
release, so as to reduce warnings from findbugs and IDE, including
identifying interfaces meeting the FunctionalInterface annotation.
8. fix references to old websites in Javadocs to use the current
URLs to avoid redirections by browsers visiting the Javadocs
on the author's website.
9. add configuration option to not gray out old message traffic (to make
it more readable in the UI).
10. fix exceptions thrown when doing a Locate->Landmark search so that all
matches will be reported.
11. first draft at fixing filtered message view.
12. make it possible to select text from the popup OSM node/way information
dialog and copy it to the clipboard. useful for debugging OSM issues.
13. allow configurable level of position ambiguity in locally-originated
beacons.
14. ensure if use of GPS is deselected in the configuration wizard, beacons
configured to use GPS as the position source automatically have the
"Use GPS for Position" option unchecked.
15. fix places in YAAC where HTTPS transactions were still allowed when the
option to force only unencrypted transactions was specified.
16. keep unlabeled OSM ways fronm being selected when clicked on the map if
rendering unlabeled ways is disabled.
17. ensure plugin status tabl is correctly updated when a new plugin is
installed.
18. ensure AX.25 frame command/poll bits are set correctly.
19. fix SRTM (topographic) data downloader to allow the user to abort if they
don't have a USGS account yet to use for the downloading.
20. fix pseudo APRS-IS server plugin so a jammed subordinate client is treated
the same way as a real APRS-IS backbone server would, disconnecting the
client rather than letting all of YAAC get frozen.
21. remove the bluetooth plugin from the supported plugin set, as the BlueCove
library no longer works with current versions of Microsoft Windows.
22. fix port naming in the marineports plugin so the port driver for NMEA-0183
over TCP/IP can actually be used.
|
FINALLY! next beta build#182 of YAAC
It took a long time to get this build out. There are a lot of changes and cleanups
in this build, but I hope you will appreciate them all. I won't be releasing an updated
map set for a few days because this build of YAAC supports a changed and enhanced
map importing that older versions of YAAC can't handle, so I want this build to be
available before users start complaining their old build of YAAC can't handle the
updated map set.
--------------------------------------------------------------------------------------------
next beta build#182 of YAAC ("Yet Another APRS Client"), created 2023-Jul-11
downloadable from
or
changes and updates include:
1. fix IS-to-RF (transmit) I-gating to use the I-gate's RF port callsign-SSID
and tocall instead of the original station's values in the raw AX.25
frame. This fixes a possible contributor to the APRS flooding noticed on
#APRSThursday.
2. add new utility called WayAnalyzer to help debug issue with OpenStreetMap
importing and rendering.
3. significant logic and performance improvements in importing OpenStreetMap
datasets, though, alas, there is still more work to come.
4. reaarrange the source code so that Maven builds with POM files will actually
work correctly for both the YAAC application and all the currently
supported plugins, with appropriate adjustments to the Ant build.xml
files to work with the new structure.
5. a new Debug plugin which allows dynamically turning on and off debug logging
from the expert-mode Configuration dialog for different supported categories
of logging while YAAC is running. Also some new core API methods on the
DebugCtl class to permit plugins to register new debug logging categories.
6. version update on the JavaHelp library.
7. some code cleanup for the change to Java 8 as minimum supported runtime
release, so as to reduce warnings from findbugs and IDE, including
identifying interfaces meeting the FunctionalInterface annotation.
8. fix references to old websites in Javadocs to use the current
URLs to avoid redirections by browsers visiting the Javadocs
on the author's website.
9. add configuration option to not gray out old message traffic (to make
it more readable in the UI).
10. fix exceptions thrown when doing a Locate->Landmark search so that all
matches will be reported.
11. first draft at fixing filtered message view.
12. make it possible to select text from the popup OSM node/way information
dialog and copy it to the clipboard. useful for debugging OSM issues.
13. allow configurable level of position ambiguity in locally-originated
beacons.
14. ensure if use of GPS is deselected in the configuration wizard, beacons
configured to use GPS as the position source automatically have the
"Use GPS for Position" option unchecked.
15. fix places in YAAC where HTTPS transactions were still allowed when the
option to force only unencrypted transactions was specified.
16. keep unlabeled OSM ways fronm being selected when clicked on the map if
rendering unlabeled ways is disabled.
17. ensure plugin status tabl is correctly updated when a new plugin is
installed.
18. ensure AX.25 frame command/poll bits are set correctly.
19. fix SRTM (topographic) data downloader to allow the user to abort if they
don't have a USGS account yet to use for the downloading.
20. fix pseudo APRS-IS server plugin so a jammed subordinate client is treated
the same way as a real APRS-IS backbone server would, disconnecting the
client rather than letting all of YAAC get frozen.
21. remove the bluetooth plugin from the supported plugin set, as the BlueCove
library no longer works with current versions of Microsoft Windows.
22. fix port naming in the marineports plugin so the port driver for NMEA-0183
over TCP/IP can actually be used.
|
Re: BCN beacon transmit greyed out
Is your beacon enabled (checkbox near upper left on beacon editing panel)? If the beacon is not enabled, it will not go out, either automatically or manually. Note that beacons _are_ position reports (in one format or another), so if you want
to send a beacon, you have to send your position as part of it.
Per chance, did you check the box labeled "Use GPS for position"? If so, do you have a valid GPS fix in YAAC (received through an enabled and properly configured Serial_GPS or GPSD port type)? If you demand using GPS position but don't have
one, the GPS-using beacon won't go out. A YAAC design decision was to not send any beacon rather than send an invalid one.
Is there any particular reason you changed the tocall for your beacons to BEACON instead of using the default identifying you as a YAAC user?
Andrew, KA2DDO
author of YAAC
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Kevin Werner via groups.io <kwerner@...>
Sent: Thursday, June 29, 2023 8:33:22 AM
I can transmit messages in chat windows and at bottom of map, but the [BCN] button is greyed out, not clickable for some reason.
In config-transmit, "beacon destination" is set to BEACON. config-beacon I have tried a couple different settings, I have position off.
Thank you,
Kevin KD9SPR
_._,_._,
_._,_._,_
|
BCN beacon transmit greyed out
I can transmit messages in chat windows and at bottom of map, but the [BCN] button is greyed out, not clickable for some reason.
In config-transmit, "beacon destination" is set to BEACON. config-beacon I have tried a couple different settings, I have position off.
Thank you,
Kevin KD9SPR
|
Re: SMS Messages not going through
On 6/27/23 14:08, Patrick wrote:
Ronny, as posted previously it is still up and running currently
though it's hard to say if that will stay that way and I did just
successfully send myself a message from my handheld.
See {etc}
IIUC, that is where some of the abuse originates, when peoples'
phone numbers get posted for public viewing
|
Re: SMS Messages not going through
Sorry I don't catch every message on here. I'm glad they're getting it back together. Hopefully they found a new sponsor.
|
Re: SMS Messages not going through
Ronny, as posted previously it is still up and running currently though it's hard to say if that will stay that way and I did just successfully send myself a message from my handheld.
See https://aprs.fi/?c=message&call=SMSGTE&limit=50
|
Re: SMS Messages not going through
OK, while it looks like my igate is sending the messages received from my handheld it is also sending them over the air and they look to be being rejected by KF7OLD-10, and rightfully so, they don't need to go in via multiple igates.
However if I send a message via YAAC from my desktop either via OUTNET or ARISS,SGATE,WIDE2-1 nothing is ever seen on my phone
|
Re: SMS Messages not going through
SMSGTE was shut down by the team that ran it weeks ago
|
Re: SMS Messages not going through
I also just noticed this...
Jun 27 13:52:56 APRS-iGate direwolf[521]: [0.4] KF7OLB-10>APDW16,N7ISP-10*:}KE6BLR-7>APK102,TCPIP,KF7OLB-10*::KD7WPQ-7 :rej43
Jun 27 13:52:56 APRS-iGate direwolf[521]: "KE6BLR-7" REJected message number "43" from "KD7WPQ-7", Kenwood D710
Jun 27 13:52:59 APRS-iGate direwolf[521]: [ig>tx] KE6BLR-7>S33WXR,N6EX-4*,qAR,KF6NMZ-4:`-GKl*<0x1c>K\]"4q}CAMPING TONIGHT=
Jun 27 13:53:00 APRS-iGate direwolf[521]: Digipeater N7ISP-10 audio level = 84(13/8)?? [NONE]?? __||||___
Jun 27 13:53:00 APRS-iGate direwolf[521]: [0.3] KF7OLB-10>APDW16,N7ISP-10*:}KE6BLR-7>APK102,TCPIP,KF7OLB-10*::KD7WPQ-7 :rej45
Jun 27 13:53:00 APRS-iGate direwolf[521]: "KE6BLR-7" REJected message number "45" from "KD7WPQ-7", Kenwood D710
Jun 27 13:53:02 APRS-iGate direwolf[521]: Digipeater N7ISP-10 audio level = 76(14/9)?? [NONE]?? __|||||__
Jun 27 13:53:02 APRS-iGate direwolf[521]: [0.4] KF7OLB-10>APDW16,N7ISP-10*:}KE6BLR-7>S33WXR,TCPIP,KF7OLB-10*:`-GKl*<0x1c>K\]"4q}CAMPING TONIGHT=
Thing is, this is directly to my igate, I'm sitting next to it, it should have gone out my igate not sent to another, if that is the case.
|
Re: SMS Messages not going through
OK, I just tried via my handheld and didn't get a text, here is what direwolf said in it's logs...
[0.4] KD7WPQ-7>APY03D,WIDE1-1,WIDE2-1::SMSGTE?? :@208####### Hi{45<0x0d>
The APRS protocol specification says nothing about a possible carriage return after the
message id.? Adding CR might prevent proper interoperability with with other applications.
APRS Message, number "45", from "KD7WPQ-7" to "SMSGTE", Yaesu FT3D series
@208####### Hi
SMSGTE>APSMS1,TCPIP,qAS,VE3OTB-12::KD7WPQ-7 :ack45
|
Re: SMS Messages not going through
The ones from 6-24 were over the weekend, and sent over the air from a remote offline site.
In this case I am connecting directly to my igate on my network.
There should have been sent test messages on 6-26 and 6-27
As far as I know OUTNET is supposed to be out my local internet connection via my igate
The reason I am troubleshooting this is if it is supposed to be working and my igate is the problem I should fix it or my igate is not doing what it should be doing.
However with that said, if I broadcast via my handheld over the air the messages do seem to go through.
|
Re: SMS Messages not going through
Patrick,
One thing that appears very odd is that you are specifying OUTNET as your one and only digipeater alias. As such, unless you are within direct (no-digipeat) range of an I-gate, your message will never
get to the SMSGTE server because it will never get to get to the APRS-IS backbone; most digipeaters willnot recognize OUTNET as an alias they support. Or is OUTNET the tactical name of a digipeater in your immediate vicinity?
Andrew, KA2DDO
author of YAAC
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Lynn Deffenbaugh <kj4erj@...>
Sent: Tuesday, June 27, 2023 10:31:47?
Can you do another test??? Your last interaction from KD7WPQ (2023-06-24 18:21:25 EDT, apparently an attempt to go through the ISS according to the path) rolled off the aprs.fi raw packets display for SMSGTE about 1 hour after that
time.?? Unless you were using a different -SSID more recently?
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 6/27/2023 6:25 AM, Patrick wrote:
I posted this in the direwolf thread as well as I'm not sure if it's a YAAC issue or a direwolf issue but here is the problem....
If I try to send a sms message via YAAC connected to direwolf via my local network the message never makes it through.
I am able to send messages, or I think I am but not SMS for some reason.
Here is my YAAC port configuration...
Here is the message in the direwolf log when I attempt to send a sms....
[0L] KD7WPQ>APJYC1,OUTNET::SMSGTE?? :@208####### testing{m000a
Anyone have any ideas on what I'm missing?
_._,_.
_._,_._,_
|
Re: SMS Messages not going through
Can you do another test??? Your last
interaction from KD7WPQ (2023-06-24 18:21:25 EDT, apparently an
attempt to go through the ISS according to the path) rolled off
the aprs.fi raw packets display for SMSGTE about 1 hour after that
time.?? Unless you were using a different -SSID more recently?
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 6/27/2023 6:25 AM, Patrick wrote:
toggle quoted message
Show quoted text
I posted this in the direwolf thread as well as I'm not sure if
it's a YAAC issue or a direwolf issue but here is the
problem....
If I try to send a sms message via YAAC connected to direwolf
via my local network the message never makes it through.
I am able to send messages, or I think I am but not SMS for some
reason.
Here is my YAAC port configuration...
Here is the message in the direwolf log when I attempt to send a
sms....
[0L] KD7WPQ>APJYC1,OUTNET::SMSGTE?? :@208#######
testing{m000a
Anyone have any ideas on what I'm missing?
|
Re: SMS Messages not going through
If you check the aprs.fi logs, SMSGTE is
actually online and working, regardless of what their web page
says.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 6/27/2023 7:58 AM, km4ack wrote:
toggle quoted message
Show quoted text
The SMSGTE service is offline. See for
details.
73, de KM4ACK
|
Re: SMS Messages not going through
The SMSGTE service is offline. See for details.
73, de KM4ACK
|
SMS Messages not going through
I posted this in the direwolf thread as well as I'm not sure if it's a YAAC issue or a direwolf issue but here is the problem....
If I try to send a sms message via YAAC connected to direwolf via my local network the message never makes it through.
I am able to send messages, or I think I am but not SMS for some reason.
Here is my YAAC port configuration...
Here is the message in the direwolf log when I attempt to send a sms....
[0L] KD7WPQ>APJYC1,OUTNET::SMSGTE?? :@208####### testing{m000a
Anyone have any ideas on what I'm missing?
|
Map labelling (was: Re: Font/icon size)
Map labelling is displayed based on the current map zoom level and the type of item being labelled. For example, the name of a tiny hamlet would stop being rendered sooner upon zooming out than the name of an entire province would be. The exact
default zoom level settings were chosen based on the density of map features in my area (since I look at that part of the map the most).
However, those defaults might not be appropriate for your area. The settings can be changed by going to View->Layers...->Select Geographical Map Layers, and adjusting the zoom level numbers on the tabular lists for Ways and Places.
toggle quoted message
Show quoted text
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Giovanni IZ5PQT <iz5pqt@...>
Sent: Wednesday, June 7, 2023, 2:39 PM
To: yaac-users@groups.io <yaac-users@groups.io>
Subject: Re: Font/icon size (was: Re: [yaac-users] Disk space issue)
Andrew,?
OK, got it. Now another small problem: the maps are not showing anymore the names of places
( I mean towns, villages. localities etc. ). The only names that appear are those of rivers (!!).?
I have the impression that it was not like so when? I started, so maybe I have messed up something!
I appreciate all the effort you are doing to support this nice piece of software!?
73 Giovanni iz5pqt?
_._,_._,_
|
Re: Font/icon size (was: Re: [yaac-users] Disk space issue)
Andrew,?
OK, got it. Now another small problem: the maps are not showing anymore the names of places ( I mean towns, villages. localities etc. ). The only names that appear are those of rivers (!!).? I have the impression that it was not like so when? I started, so maybe I have messed up something! I appreciate all the effort you are doing to support this nice piece of software!?
73 Giovanni iz5pqt?
Il giorno mer 7 giu 2023 alle ore 15:04 Andrew P. < andrewemt@...> ha scritto:
No, it was me forgetting where I put it. It's actually on the View menu, specifically View->Layers...->Show Double-Sized Icons.
Andrew, KA2DDO
author of YAAC (program now 12 years old!)
Andrew,
I think there is a disgreement between the versions. I am using 1.0-beta181 (Windows) and I do not see any checkbox in the preference tab to choose double-sized icons. See attached image below.?
Also, when I right-click on the icon of a station, there is no "Show Double-Sized Icon" in the Menu.
The only way it works for me is to select the station for tacking and then to tick the Double-Sized checkbox in the track list
|
Re: Font/icon size (was: Re: [yaac-users] Disk space issue)
Also, I forgot that the individual double-sizing control is in the Tracked Stations table view, so you have to Track This Station to get it on the list so you can pick double-sizing its icon.
Andrew, KA2DDO
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Andrew P.
Sent: Wednesday, June 7, 2023, 9:04?
No, it was me forgetting where I put it. It's actually on the View menu, specifically View->Layers...->Show Double-Sized Icons.
Andrew, KA2DDO
author of YAAC (program now 12 years old!)
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Giovanni IZ5PQT
Sent: Wednesday, June 7, 2023, 8:19 AM
Andrew,
I think there is a disgreement between the versions. I am using 1.0-beta181 (Windows) and I do not see any checkbox in the preference tab to choose double-sized icons. See attached image below.?
Also, when I right-click on the icon of a station, there is no "Show Double-Sized Icon" in the Menu.
The only way it works for me is to select the station for tacking and then to tick the Double-Sized checkbox in the track list
_._,_._,_
|
km4ack
Giovanni IZ5PQT
