¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

External Message

 

Hello,

Thank you for creating and maintaining this project, it is far better than Xastir!

I am trying to use an external message port to interface with a python script the will send DMR SMS messages to APRS, and the other way around.
I have successfully created a python script that opens a socket to the external message server, which is in "src>dst:message" mode. YAAC is receiving and re-transmitting packets. However, I notice when they show up in APRS.fi, they are formatted as "SOURCE>DESTINATION,PATH:MESSAGE". When sent over RF, my TH-D72 is not receiving the message packet, but can see the packet digipeated. I have noticed that other messages from YAAC interface, APRSdroid, etc. follow "SOURCE>PATH,DESTINATION:MESSAGE" format. I have played around with the path settings in the external message port, but the destination call is always before the path. Maybe I am doing something wrong, or could it be a bug?

I really appreciate YAAC, and the fact it has the ability to interface with other scripts.

Thank you for your time.

KF7EEL
Eric C


Re: YAAC SSL

 

Thank you. How stupid. The SSL port configuration panel is still checking the passcode length (copied and pasted from the non-SSL APRS-IS port configuration panel, since a valid passcode is required to enable port transmitting on a non-SSL connection), but of course a passcode is never entered for the SSL port type. This will be fixed in the next build.

Note that this shouldn't prevent you from using the port with that filter expression; it's just very annoying. If it does prevent you, please get back to me.

Now another question is, while I'm fixing this, should I have the port configuration panel confirm you have already loaded your LotW certificate and private key? :-)

Andrew, KA2DDO
author of YAAC

________________________________________
From: Phil Pacier - AD6NH <ad6nh@...>
Sent: Tuesday, January 28, 2020 1:06 PM
To: Andrew P.
Subject: Re: YAAC SSL

Thank you for your quick response. Your reply would make perfect sense if not for the fact that the beacon is indeed turned on, as shown in the screenshot. Unless there is another beacon setting somewhere else, I'm not sure what else needs to be set, as I don't have to do anything else with the non-ssl port. Thank you!

[cid:part1.9FE2B021.38829628@...]

--

73 de Phil Pacier, AD6NH
APRS Tier2 Network Coordinator

D-Star Administrator: W6HRO & REF070

On 1/28/2020 10:01 AM, Andrew P. wrote:

Hi, Phil.

Good to know that the SSL servers are coming back.

The problem you are having has nothing to do with SSL; you'd have the same problem with a passcode APRS-IS port. The issue is that the 'm' filter you are using tells the APRS-IS server to send packets for all stations within a certain radius of your beaconed position. However, your beacon is turned off, so the APRS-IS server will never _know_ your position to compute that radius circle and select those packets.

I've had several other people complain about this operator-error issue ("how come I'm not receiving any packets from the APRS-IS?"), so I recently added a check to YAAC to confirm that you are configured to send a beacon before you are allowed to use only an 'm' filter expression. If you don't want to beacon, I recommend using an 'r' filter expression (i.e., r/lat/lon/radius ) with your approximate decimal (N or E oriented) latitude and longitude.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: Phil Pacier - AD6NH <ad6nh@...><mailto:ad6nh@...>
Sent: Tuesday, January 28, 2020 12:51 PM
To: ka2ddo@...<mailto:ka2ddo@...>
Subject: YAAC SSL

Good day, Andrew! I hope you are doing well. We have revitalized the SSL connection to the Tier2 servers, and currently have two servers accepting connections on port 24580. The ssl.aprs2.net address has those two servers and it works fine now.

I have been trying to setup an SSL connection from YAAC but I am having difficulty. I requested an up-to-date key from ARRL and verified that it works with APRSDroid. Here are two screen shots, one of the settings, and one of the error message I get in YAAC:

[cid:part1.135C4A34.ECDA3791@...]

[cid:part2.22FBEF9B.EDC0FFE0@...]

Thank you for your assistance!

--
--

73 de Phil Pacier, AD6NH
APRS Tier2 Network Coordinator

D-Star Administrator: W6HRO & REF070


Re: YAAC SSL

 

Hi, Phil.

Good to know that the SSL servers are coming back.

The problem you are having has nothing to do with SSL; you'd have the same problem with a passcode APRS-IS port. The issue is that the 'm' filter you are using tells the APRS-IS server to send packets for all stations within a certain radius of your beaconed position. However, your beacon is turned off, so the APRS-IS server will never _know_ your position to compute that radius circle and select those packets.

I've had several other people complain about this operator-error issue ("how come I'm not receiving any packets from the APRS-IS?"), so I recently added a check to YAAC to confirm that you are configured to send a beacon before you are allowed to use only an 'm' filter expression. If you don't want to beacon, I recommend using an 'r' filter expression (i.e., r/lat/lon/radius ) with your approximate decimal (N or E oriented) latitude and longitude.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: Phil Pacier - AD6NH <ad6nh@...>
Sent: Tuesday, January 28, 2020 12:51 PM
To: ka2ddo@...
Subject: YAAC SSL

Good day, Andrew! I hope you are doing well. We have revitalized the SSL connection to the Tier2 servers, and currently have two servers accepting connections on port 24580. The ssl.aprs2.net address has those two servers and it works fine now.

I have been trying to setup an SSL connection from YAAC but I am having difficulty. I requested an up-to-date key from ARRL and verified that it works with APRSDroid. Here are two screen shots, one of the settings, and one of the error message I get in YAAC:

[cid:part1.135C4A34.ECDA3791@...]

[cid:part2.22FBEF9B.EDC0FFE0@...]

Thank you for your assistance!

--
--

73 de Phil Pacier, AD6NH
APRS Tier2 Network Coordinator

D-Star Administrator: W6HRO & REF070


Re: URDC II configuration

Ron VE8RT
 

Just got back to the house, I have Audacity on the desktop, hadn't thought about looking for a Pi version.? Data is getting to aprs.fi as my station shows up with the correct SSID.? And you're right about joining the Direwolf group, the example conf files I'm finding have issues, for example I can't use "digi" for the SSID as it returns an error, and IBEACON gives me an unrecognized command error.? Thanks for the help, I'm off to join the Direwolf group.
In the future it may be a good idea to use YAAC with a Pi and a CM108 (modified) audio dongle, I'd like to use it portable or mobile for public service events.


Re: URDC II configuration

 

If you run DireWolf from a terminal window, it should print out several lines of text describing each received packet as they come in. So, you need to confirm you're actually getting audio into the sound port you are listening to.

You might want to try installing a program called audacity. It's an audio editing package useful for musicians, theatre technicians, and others who process sound, but it's also a convenient way to ensure you're actually getting audio into your computer. Have it recording the input from the UDRC card and confirm that when you hear packets on the radio's speaker, you see the corresponding envelope growth on the Audacity oscilloscope graph. That way, you can confirm you're configuring DireWolf to listen and transmit on the correct audio port.

As for getting data to aprs.fi, that won't happen until you have an I-gate connection to the APRS-IS backbone with a valid passcode (so you're allowed to forward the packets to the APRS-IS). Either DireWolf or YAAC can do the I-gating function. You might want to join the DireWolf mailing list ([email protected]) or NW Digital Radio's udrc mailing list ([email protected]) to ask them for more information.


Re: URDC II configuration

Ron VE8RT
 

It would be nice to have the map and features of YAAC available. I had trying running Direwolf alone, but it wasn't apparent that anything was being decoded.? I could hear the local WX station in the TM-V71A audio but it wasn't showing up on aprs.fi? My own station was showing up on aprs.fi though.? It was getting pretty late and I set things aside to get some sleep.? I'd be happy to get the configuration right for Direwolf and at least get something working as an Igate for now, until the local one is back in service.? YAAC would be a big bonus in the (hopefully near) future.


Re: URDC II configuration

 

YAAC does not have any TNC modem capability built into it; it expects you to provide some external implementation (in hardware or software). Given you're using a Raspberry Pi with UDRC-II, your best option would be to use DireWolf as your software TNC. As such, you wouldn't even need to use YAAC as a digipeater or I-gate, as DireWolf has that capability all by itself (and it would be more efficient at it too, because DireWolf isn't trying to update all the graphical screens YAAC has), although you could choose to not enable DireWolf's digipeating and I-gating capability and use YAAC to do so for the logging.

Even if you use DireWolf as a stand-alone digipeater and/or I-gate, you could still run YAAC and connect it to the KISS or AGWPE ports on the DireWolf process so you could watch what DireWolf was processing.

Andrew, KA2DDO
author of YAAC


URDC II configuration

Ron VE8RT
 

Hi,

? I'm new here, I've spent a few hours with a Raspberry Pi and a URDC II interface trying to set up an Igate/Digipeater.? Our local Igate has failed.? Getting to the point, I wanted to use YAAC with the raspberry pi URDC II interface combination.? Things were going along well until I came to the configure ports page of the set-up wizard.? Some help with this would be appreciated, its my hope that someone has already done this, but then maybe not as the URDC II uses the GPIO pins of the pi rather than a USB port.

?? Ron, Yellowknife, NT, Canada? VE8RT VE8TEA


Re: next beta build#147 of YAAC

 

Thanks Andrew :)

On 1/23/2020 1:19 PM, Andrew P. wrote:
next beta build#147 of YAAC ("Yet Another APRS Client"), created 2020-Jan-23

downloadable from
or

changes and updates include:
1. fill in missing information in the Javadocs for the YAAC source code.
2. fix the built-in help index merging. This required changing all of
the plugins that had help extensions, as the old format would actually
cause help generation to fail when sort-merging the index.
3. implement and document command-line options to support limited
configuration setting, suitable for use by third-party installation
scripts.
4. eliminate excessive digits after the decimal point for QRU maximum
range.
5. add user-selectable new formats for logging GPS track data, including
the existing format of whatever YAAC is receiving, and per-source
(local and remote) logging in NMEA-0183 sentences, GPSD JSON
structures, GPX (GPs eXchange) XML, and CSV format.
6. fix error in time-limiting the playback of a GPS log file.
7. fix memory and CPU leak when closing raw packet view.
8. fix spurious NullPointerException when setting up map windows.
9. add safety check to make user confirm they really want to change
their Mic-E status to the Emergency setting before actually doing
it.
10. copy the latest version of Hessu's tocalls.dense.json file.
11. normalize the entries on the View menu to not say "View" or
"Show" redundantly.
12. add one-touch changing of Mic-E status to the small screen plugin.
--
Michael Cozzi
cozzicon@...
kd8tut@...
269-519-2389


next beta build#147 of YAAC

 

next beta build#147 of YAAC ("Yet Another APRS Client"), created 2020-Jan-23

downloadable from
or

changes and updates include:
1. fill in missing information in the Javadocs for the YAAC source code.
2. fix the built-in help index merging. This required changing all of
the plugins that had help extensions, as the old format would actually
cause help generation to fail when sort-merging the index.
3. implement and document command-line options to support limited
configuration setting, suitable for use by third-party installation
scripts.
4. eliminate excessive digits after the decimal point for QRU maximum
range.
5. add user-selectable new formats for logging GPS track data, including
the existing format of whatever YAAC is receiving, and per-source
(local and remote) logging in NMEA-0183 sentences, GPSD JSON
structures, GPX (GPs eXchange) XML, and CSV format.
6. fix error in time-limiting the playback of a GPS log file.
7. fix memory and CPU leak when closing raw packet view.
8. fix spurious NullPointerException when setting up map windows.
9. add safety check to make user confirm they really want to change
their Mic-E status to the Emergency setting before actually doing
it.
10. copy the latest version of Hessu's tocalls.dense.json file.
11. normalize the entries on the View menu to not say "View" or
"Show" redundantly.
12. add one-touch changing of Mic-E status to the small screen plugin.


Re: Open street maps local serve support

 

I understand... A member has already rendered vector & raster data for our geografical area. I would like to point to that over the mesh network.?

Mathison


On Wed, Jan 22, 2020, 11:51 AM Andrew P. <andrewemt@...> wrote:
It's not the same kind of tile server in YAAC as with the main OpenStreetMap tile server.

The "tiles" in YAAC are not raster images. They are geographically segmented pieces of the raw vector data, so that the YAAC real-time map renderer doesn't have to read through the entire planet's worth of data to render raster images of the streets in one small area. As such, YAAC doesn't have multiple "tiles" for different screen zoom levels; the raw vector data is rendered at whatever zoom level the user wants. This keeps the "tile" cache much smaller than for systems that cache different raster image tiles for each zoom level of the covered area. That's also why YAAC's street maps don't look like the tile-based web maps on OpenStreetMap or Google; my renderer isn't as good because it strives for speed rather than beauty for less powerful rendering machines, and it still has a few bugs in it.

I should mention that YAAC was deliberately designed to only operate off a local disk copy of the map data, specifically so it would still operate in installations without Internet service for downloading tiles. So the only way for it to operate without map files on a Pi is to not display maps.

You don't have to use my server to get updated "tiles" of segmented vector data. You can get a copy of the OpenStreetMap vector data (a database dump in .osm.bz2 or .osm.pbf format) and import it yourself. However, due to YAAC rearranging the data for more efficient rendering (so constant database lookups in different tables aren't needed), the importer is an enormous burden on the host computer; you need at least 150GB of free disk space to handle the import, and it takes hours (when I do the whole planet.osm.pbf file on my dedicated gaming server, it takes over 15 hours). A Raspberry Pi simply doesn't have the muscle to do it. But you can do it on a big enough machine to handle the burden, then zip or tar up the tile directory hierarchy on that system and restore it on each of your Pi computers.

The "tile" downloading feature in YAAC simply makes it easier for a given computer to only get the tiles it needs without having to waste disk space on other squares of the map, nor on manually figuring out which files to download.

The topographic layer of the map operates similarly, in that it stores the raw elevation data from the USGS in 1-degree-square files, and renders it at the desired zoom level on demand.

Hope this helps you understand my design philosophy.

Andrew, KA2DDO
author of YAAC


Re: Open street maps local serve support

 

It's not the same kind of tile server in YAAC as with the main OpenStreetMap tile server.

The "tiles" in YAAC are not raster images. They are geographically segmented pieces of the raw vector data, so that the YAAC real-time map renderer doesn't have to read through the entire planet's worth of data to render raster images of the streets in one small area. As such, YAAC doesn't have multiple "tiles" for different screen zoom levels; the raw vector data is rendered at whatever zoom level the user wants. This keeps the "tile" cache much smaller than for systems that cache different raster image tiles for each zoom level of the covered area. That's also why YAAC's street maps don't look like the tile-based web maps on OpenStreetMap or Google; my renderer isn't as good because it strives for speed rather than beauty for less powerful rendering machines, and it still has a few bugs in it.

I should mention that YAAC was deliberately designed to only operate off a local disk copy of the map data, specifically so it would still operate in installations without Internet service for downloading tiles. So the only way for it to operate without map files on a Pi is to not display maps.

You don't have to use my server to get updated "tiles" of segmented vector data. You can get a copy of the OpenStreetMap vector data (a database dump in .osm.bz2 or .osm.pbf format) and import it yourself. However, due to YAAC rearranging the data for more efficient rendering (so constant database lookups in different tables aren't needed), the importer is an enormous burden on the host computer; you need at least 150GB of free disk space to handle the import, and it takes hours (when I do the whole planet.osm.pbf file on my dedicated gaming server, it takes over 15 hours). A Raspberry Pi simply doesn't have the muscle to do it. But you can do it on a big enough machine to handle the burden, then zip or tar up the tile directory hierarchy on that system and restore it on each of your Pi computers.

The "tile" downloading feature in YAAC simply makes it easier for a given computer to only get the tiles it needs without having to waste disk space on other squares of the map, nor on manually figuring out which files to download.

The topographic layer of the map operates similarly, in that it stores the raw elevation data from the USGS in 1-degree-square files, and renders it at the desired zoom level on demand.

Hope this helps you understand my design philosophy.

Andrew, KA2DDO
author of YAAC


Open street maps local serve support

 

Our local mesh group is running a server to distribute map tiles. Im reading thru the documentation and it looks like you have hard coded your personal tile server into the program. might it be possible to bring the option to set the server out into the gui? I dont know if the back-end of YAAC will pull tiles from the server the same way we do for our mapping program or not? Dose YAAC support the pointing as follows?in our php ini file we define a server with?inetTileServer['Topographic'] = "//{s}.tile.opentopomap.org/{z}/{x}/{y}.png"

I would like to not cash the tiles on the RPI.

For reference:?


Thanks for the Program 73 Mathison KJ6DZB


Re: Icon of YAAC on Raspberry Pi Desktop

 

Yea, I had that Exec all wrong. It was my first try. LOL


Re: Icon of YAAC on Raspberry Pi Desktop

 

It worked perfectly, thank you.


Re: Icon of YAAC on Raspberry Pi Desktop

 

Here is my desktop file (my desktop, not an RPi) that seems to work just fine.

$ cat Desktop/YAAC.desktop
[Desktop Entry]
Name=YAAC
Exec=java -jar /home/michael/YAAC/YAAC.jar
Comment=
Terminal=false
Icon=/home/michael/YAAC/images/yaaclogo64.ico
Type=Application


I'm thinking your problem may lie in your EXEC statement. You have your PATH before the java command. Try putting it in front of the YAAC.jar file. It should also be the full path. i.e.

Exec=java -jar /home/pi/YACC/YAAC.jar

HTH,

Michael WA7SKG



Keith Kaiser wrote on 1/20/20 1:09 PM:

I'd like to have an icon I can use to launch YAAC, I'd also like to add it to the menu system.
For the desktop, I right clicked on the desktop and created YAAC.desktop. Then using sudo I entered;
[Desktop Entry]
Name=YAAC
Comment=Launch YAAC
Icon=/usr/share/pixmaps/yaac.xpm
Exec=/YAAC java -jar YAAC.jar
Type=Application
Encoding=UTF-8
Terminal=false
Categories=Network;HamRadio;
Then rebooted:
After:
Double clicking it only returns:
"Invalid desktop entry file.'/home/pi/Desktop/YAAC.desktop'"
I've Googled for how to do this (generically, not just for YAAC) but none of the sites makes it any more clear than what I did. Can someone point out where to find this information or help me get it working?
_._,_._,_


Re: Icon of YAAC on Raspberry Pi Desktop

 

Greetings.

2 different sized icons are provided in the YAAC distribution for just this purpose (and are documented in the index for YAAC built-in help under the topic "desktop shortcuts"), but they are .ico files for use on Microsoft Windows. However, the Raspbian desktop manager will accept these files (they are used in the NW Digital Radio SD card image for their DRAWS hat).

Look for <yaacInstallDirectory>/images/yaaclogo*.ico and pick one of the appropriate resolution (NWDigitalRadio used yaaclogo64.ico).

Note that I'm not sure why the Exec= string in your desktop file starts with /YAAC; you can specify the YAAC.jar file with a directory prefix and YAAC will find its auxiliary files by reverse-engineering the location of the YAAC.jar file.

For example,

Exec=java -jar /home/pi/YAAC/YAAC.jar

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Monday, January 20, 2020 4:09 PM
To: [email protected]
Subject: [yaac-users] Icon of YAAC on Raspberry Pi Desktop

I'd like to have an icon I can use to launch YAAC, I'd also like to add it to the menu system.

For the desktop, I right clicked on the desktop and created YAAC.desktop. Then using sudo I entered;
[Desktop Entry]
Name=YAAC
Comment=Launch YAAC
Icon=/usr/share/pixmaps/yaac.xpm
Exec=/YAAC java -jar YAAC.jar
Type=Application
Encoding=UTF-8
Terminal=false
Categories=Network;HamRadio;

Then rebooted:

After:
Double clicking it only returns:
"Invalid desktop entry file.'/home/pi/Desktop/YAAC.desktop'"

I've Googled for how to do this (generically, not just for YAAC) but none of the sites makes it any more clear than what I did. Can someone point out where to find this information or help me get it working?


Icon of YAAC on Raspberry Pi Desktop

 

I'd like to have an icon I can use to launch YAAC, I'd also like to add it to the menu system.

For the desktop, I right clicked on the desktop and created YAAC.desktop. Then using sudo I entered;
[Desktop Entry]
Name=YAAC
Comment=Launch YAAC
Icon=/usr/share/pixmaps/yaac.xpm
Exec=/YAAC java -jar YAAC.jar
Type=Application
Encoding=UTF-8
Terminal=false
Categories=Network;HamRadio;

Then rebooted:

After:
Double clicking it only returns:
"Invalid desktop entry file.'/home/pi/Desktop/YAAC.desktop'"

I've Googled for how to do this (generically, not just for YAAC) but none of the sites makes it any more clear than what I did. Can someone point out where to find this information or help me get it working?


Re: Email client output rework

Ronny Julian
 

? Will be joining you on that soon Nate.? New Linux box is here but not yet built.? Thanks guys!??

On Sat, Jan 18, 2020 at 9:08 PM Nate Bargmann <n0nb@...> wrote:
No issues here as I'm reading it in Mutt in Gnome Terminal and all the
messages use the same font.? ;-)

73, Nate

--

"The optimist proclaims that we live in the best of all
possible worlds.? The pessimist fears this is true."

Web:
Projects:
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819





Re: Email client output rework

 

No issues here as I'm reading it in Mutt in Gnome Terminal and all the
messages use the same font. ;-)

73, Nate

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Web:
Projects:
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819