#36 Cannot send message to some APRS Destinations

[Stewart Wilkinson]

I have recently install YAAC and find it annoying that I have to wait for it to hear some traffic from a stations before it will allow me to send a message to that station. I have a APRS based server running on a remote server that connects to the APRS-IS network and found that having installed YACC I cannot send a message to my remote server usign either of the 2 message aliases it uses, but I can sent one to the Callsign-SSID but I have to wait for my server to send a message using that Callsign-SSID.

Am I missing something ?

Also how do I change or add Digipeat paths as it does not seem to let me do that.

Stewart
G0LGS

[Andrew Pavlin]

You don't have to wait to hear from a station to send a message to it. The drop-down list of all heard stations can be ignored; you can just hand-type the callsign-SSID into the recipient field in any of the places where you send a message without clicking on a station ID first (the Message->Station menu choice or the fields at the bottom of the main map window).

Similarly, if the default set of digipeat aliases is not suitable, you can hand-type a digipeat path instead of picking from the list for the Via field. Also, any digipeat alias you add to the list of supported aliases in the expert-mode Configuration dialog (Digipeat tab) will be added to the default set (unfortunately only by itself, not as a combination like WIDE1-1,WIDE2-1).

[Stewart Wilkinson]

If I type some callsign-SSID combination that has not been heard in the To: box it just clears when I move over to the Via: or Message area boxes, so for me that does not appear to work.

I still do not undestand how the Digipeat settings are supposed to be conifigured. Is there a demo somewhere ?

[Andrew Pavlin]

That is very strange. When I am manually entering callsigns in the fields at the bottom of the map window, I can just tab from field to field and the data remains there. It does get automatically upper-cased if I typed the callsign in lowercase.

What operating system are you using, what version of Java (type the command "java -version" in a command window to find out what you have installed), and what build of YAAC (latest release is 1.0beta221)? Sounds like you either have an old buggy version of YAAC or a strange platform interaction.

[Stewart Wilkinson]

I am using Ubuntu 24.04 with YAAC 1.0bea221
openjdk 21.0.8 2025-07-15
OpenJDK Runtime Environment (build 21.0.8+9-Ubuntu-0ubuntu124.04.1)
OpenJDK 64-Bit Server VM (build 21.0.8+9-Ubuntu-0ubuntu124.04.1, mixed mode, sharing)

[Andrew Pavlin]

Hmmm... which window manager/desktop are you using on Ubuntu? KDE, Gnome, Cinnamon, Mate, etc? There have been certain "features" with Java's interactions with some window managers when trying to fully emulate the window manager's look & feel which don't happen with other window managers.

You might want to try using the Java "Metal" OS/desktop-independent look & feel. When you start YAAC, use the "-metal" command line option, for example,

java -jar YAAC.jar -metal

The YAAC windows won't look quite like the other windows on your desktop, but they might behave better.

[Stewart Wilkinson]

I am using the default 'Ubuntu' desktop.

adding -metal made no difference.

I also tried Cinnamon desktop and it is still the same.