YAAC Launch Problem and Not Remembering Configuration

#157

I'm setting up YAAC on a Raspberry Pi and have run into two issues
(so far).

1. I created a desktop launcher for YAAC, identical to what is on my Mint machine. When I double click on it, I get a window saying something like "This is an executable file, what do you want to do?" then gives options of Execute, Execute in Terminal, Open, Cancel. I do not get this on my Mint machine. Anyway around this?

2. When I open YAAC, it takes me into the configuration page. It does not remember my call or SSID choice. After entering that and moving to the next screen, it does remember my icon choice and pretty much everything after that. Any ideas what that problem might be? Again, this did not happen on my Mint machine for my base station, only the Raspberry Pi.

tnx es 73,
Michael WA7SKG

#158

Regarding your two questions:

1. Bear in mind that the Raspberry Pi desktop manager is not the Cinnamon desktop manager typical of Linux Mint, so its desktop shortcut files are likely to be different. You'll need to check with how desktop files are created on the Pi. For example, this is the contents of the yaac.desktop file provided by NW Digital Radio on their DRAWS image of Raspbian (which pre-installs DireWolf, Xastir, and YAAC):

[Desktop Entry]
Name=YAAC
Exec=/usr/bin/java -jar /home/pi/YAAC/YAAC.jar -gui:small
Comment=Yet Another APRS Client
Icon=/home/pi/YAAC/images/yaaclogo64.ico
Path=/home/pi/YAAC
Terminal=true
Type=Application
Categories=HamRadio
Keywords=Ham Radio;APRS Client;KISS;AGWPE;AX.25

2. Your callsign and SSID are stored on your individual ports in YAAC that send and receive AX.25 packets (or the APRS-IS equivalent). This is because cross-band digipeaters are required to have a unique callsign-SSID for each RF port of the same station, to support packet routing. (Note that it is expected that your APRS-IS port callsign-SSID will be the same as your primary RF port on an I-gate station.) As such, if you don't have any such packet-exchanging ports, your callsign won't be remembered.  So, does your configuration contain any ports of type Serial_TNC, AGWPE, KISSoverTCP, Bluetooth_TNC, Kenwood, Yaesu, File_TNC, APRS-IS, or SSL-APRS-IS? If it doesn't, then you are not storing your callsign-SSID anywhere. And, since YAAC is an APRS application, it considers your configuration to be incomplete if you don't have at least one of those port types configured (as in, how are you going to display APRS data if you don't have anyplace to get packets from?).

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
Sent: Saturday, February 22, 2020 12:05 PM
To: [email protected]
Subject: [yaac-users] YAAC Launch Problem and Not Remembering Configuration

I'm setting up YAAC on a Raspberry Pi and have run into two issues
(so far).

1. I created a desktop launcher for YAAC, identical to what is on my
Mint machine. When I double click on it, I get a window saying something
like "This is an executable file, what do you want to do?" then gives
options of Execute, Execute in Terminal, Open, Cancel. I do not get this
on my Mint machine. Anyway around this?

2. When I open YAAC, it takes me into the configuration page. It does
not remember my call or SSID choice. After entering that and moving to
the next screen, it does remember my icon choice and pretty much
everything after that. Any ideas what that problem might be? Again, this
did not happen on my Mint machine for my base station, only the
Raspberry Pi.

tnx es 73,
Michael WA7SKG

#159

Andrew, as always, you are my hero. I can't get to the Desktop file right now, but I do know your sample has more lines than mine, so that will probably fix it.

The explanation of the ports storing that data makes sense. And, yes, at the time I had not yet created the radio port as I was still researching how to configure that for the TNC-Pi. Of course after I did set the port up, when I hooked up my handheld to test things, its RF got into the RPi and scrambled the SD card so now I must start over from scratch.

I should have made notes when I set up the SD card before. Now I've got to find all those configuration steps for the different boards, etc. This CRS thing is a pain.

Thanks again,
Michael WA7SKG

Andrew P. wrote on 2/22/20 9:40 AM:

Show quoted text

Regarding your two questions:
1. Bear in mind that the Raspberry Pi desktop manager is not the Cinnamon desktop manager typical of Linux Mint, so its desktop shortcut files are likely to be different. You'll need to check with how desktop files are created on the Pi. For example, this is the contents of the yaac.desktop file provided by NW Digital Radio on their DRAWS image of Raspbian (which pre-installs DireWolf, Xastir, and YAAC):
[Desktop Entry]
Name=YAAC
Exec=/usr/bin/java -jar /home/pi/YAAC/YAAC.jar -gui:small
Comment=Yet Another APRS Client
Icon=/home/pi/YAAC/images/yaaclogo64.ico
Path=/home/pi/YAAC
Terminal=true
Type=Application
Categories=HamRadio
Keywords=Ham Radio;APRS Client;KISS;AGWPE;AX.25
2. Your callsign and SSID are stored on your individual ports in YAAC that send and receive AX.25 packets (or the APRS-IS equivalent). This is because cross-band digipeaters are required to have a unique callsign-SSID for each RF port of the same station, to support packet routing. (Note that it is expected that your APRS-IS port callsign-SSID will be the same as your primary RF port on an I-gate station.) As such, if you don't have any such packet-exchanging ports, your callsign won't be remembered.  So, does your configuration contain any ports of type Serial_TNC, AGWPE, KISSoverTCP, Bluetooth_TNC, Kenwood, Yaesu, File_TNC, APRS-IS, or SSL-APRS-IS? If it doesn't, then you are not storing your callsign-SSID anywhere. And, since YAAC is an APRS application, it considers your configuration to be incomplete if you don't have at least one of those port types configured (as in, how are you going to display APRS data if you don't have anyplace to get packets from?).
Hope this helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
Sent: Saturday, February 22, 2020 12:05 PM
To: [email protected]
Subject: [yaac-users] YAAC Launch Problem and Not Remembering Configuration
I'm setting up YAAC on a Raspberry Pi and have run into two issues
(so far).
1. I created a desktop launcher for YAAC, identical to what is on my
Mint machine. When I double click on it, I get a window saying something
like "This is an executable file, what do you want to do?" then gives
options of Execute, Execute in Terminal, Open, Cancel. I do not get this
on my Mint machine. Anyway around this?
2. When I open YAAC, it takes me into the configuration page. It does
not remember my call or SSID choice. After entering that and moving to
the next screen, it does remember my icon choice and pretty much
everything after that. Any ideas what that problem might be? Again, this
did not happen on my Mint machine for my base station, only the
Raspberry Pi.
tnx es 73,
Michael WA7SKG

开云体育

YAAC Launch Problem and Not Remembering Configuration