No, you're not crying wolf. The log file you sent me showed me what the problem was. You never saved the default beacon record (after presumably creating and saving a second beacon record). The Beacon editing tab starts up by displaying the default beacon. Since you didn't have one (and a default one wasn't created at YAAC startup because you had other saved beacon records), the Beacon tab failed when it insisted on accessing the default beacon record.

I'll have to decide how to fix this, either by ensuring there is always a default beacon record at startup, or starting out with the first beacon record (whatever it happens to be named, and whether it's the default one or not). YAAC has to have at least one beacon record, because all transmit-capable APRS stations need to be able to transmit their station identification to comply with the law.

Note that the default beacon record controls where your station is plotted on the map, including whether or not GPS data is used to reposition you per the GPS fix.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of daniel boggiano via groups.io <dboggny@...>
Sent: Sunday, February 14, 2021 10:02 AM
To: [email protected]
Subject: Re: [yaac-users] Beacon tab dissapears

I attempted to recreate the problem this morning. I started YAAC -clean. So far, I am unable to reproduce the issue.

sorry for crying wolf.

best
danny

I attempted to recreate the problem this morning. I started YAAC -clean. So far, I am unable to reproduce the issue.?

sorry for crying wolf.?

best
danny

Here it is.?

开云体育

Sounds like you managed to find a bug that only appears when creating the Beacon tab after making certain settings. In which case, there should be a stack trace in the YAAC.out file reporting why the Beacon tab couldn't be created. Please email your YAAC.out file from right after causing the problem and then exiting YAAC (so the file is forced to disk storage).

________________________________________
From: [email protected] <[email protected]> on behalf of daniel boggiano via groups.io <dboggny@...>
Sent: Saturday, February 13, 2021 7:44 PM
To: [email protected]
Subject: [yaac-users] Beacon tab dissapears

I made a new Buster card for my pi 400. I have pretty much done everything as before with the depenancies and installing yaac. After install and configuratiom with the expert editor, the next time i used it, beacons was gone from the expert editor. I am using beta 163 on a pi 400 with a card i flashed today. Any ideas?
thanks
Danny B

I made a new Buster card for my pi 400. I have pretty much done everything as before with the depenancies and installing yaac. After install and configuratiom with the expert editor, the next time i used it, beacons was gone from the expert editor. I am using beta 163 on a pi 400 with a card i flashed today. Any ideas?
thanks?
Danny B

开云体育

Make sure that you add it in your fstab file so that it remounts on reboot. Otherwise you will have to remember to manually mount it every time...

Thanks Guys,?

Yes I did just mount the share to a new folder YAAC/share and its now working properly.

Thank you,
Mike
W8GMC

开云体育

Did you mount the share on the YAAC Pi?

Can you access the file from a command shell using a simple 'cat' command? YAAC does not understand network paths. It has to be a file on a filesystem mounted on the computer where YAAC is running. It can be a network filesystem, but it still has to be mounted so it is visible to non-network-file-system-aware applications (like YAAC).

________________________________________
From: [email protected] <[email protected]> on behalf of W8GMC <Michael_MSN@...>
Sent: Wednesday, February 10, 2021 12:55 AM
To: [email protected]
Subject: [yaac-users] wxnow.txt question

Im running CumulusMX and YAAC on a separate 3B+ Raspberry Pi's, Ive set up samba on the Cumulus pi and have the wxnow.txt located in that share. I can access the wxnow file from my YAAC file manager and also from a windows machine but i dont believe YAAC is recognizing the path as it remains red. Perhaps im simply not qualifying the path correctly.
Could someone please provide some guidance on this. The path is as follows:
//weatherpi.local/share

Thank you in advance,
Mike
W8GMC

Im running CumulusMX and YAAC on a separate 3B+ Raspberry Pi's, Ive set up samba on the Cumulus pi and have the wxnow.txt located in that share. I can access the wxnow file from my YAAC file manager and also from a windows machine but i dont believe YAAC is recognizing the path as it remains red. Perhaps im simply not qualifying the path correctly.?
Could someone please provide some guidance on this. The path is as follows:
//weatherpi.local/share

Thank you in advance,?
Mike
W8GMC

开云体育

开云体育

I'm running it with good results on a 3B+.? It's sluggish in responding to interactions, but as a kiosk-type setup where it's mostly just to sit back and watch in awe, it's fine.? It's okay for interactive if you're patient.

I can imagine that a Pi0 would be a challenge.

73, David, ky7dr

Hi Danny,

Did you check this out where your getting your JSSC from?

During the startup in terminal there will be a line like this?
(JSSC found at /home/pi/YAAC/YAAC/lib/jssc-2.9.2.jar)

I might add that your problem running YAAC on a pi zero may be that it is underpowered. You would have a better experience with a pi 3B+ or a 4B

I once loaded the full pi OS on a pi zero, I could not use the graphical interface. I just slowed to a crawl.

I would recommend the more powerful pi. If you absolutely must stay with the pi zero there are other APRS interfaces that do not need the desktop.

The legacy RXTX plugin is for users on a platform where the JSSC library (the replacement for the RXTX library) is not available but RXTX is, so it allows using the RXTX library instead. It doesn't have anything to do with the Java runtime not supporting the lesser-capable ARM processor on the Pi Zero.

The JSSC distro bundled with YAAC only handles 32-bit and 64-bit Microsoft Windows, 32-bit and 64-bit Linux on Intel processors, 32-bit and 64-bit on Solaris (commercial Unix derivative), 32-bit and 64-bit Linux on ARMv7+ processors (i.e., Raspberry Pi 2 and up), and 64-bit Mac OS X on Intel processors. The RXTX library that used to be bundled with YAAC and is now bundled with the legacy plugin only handles the same list minus the ARM processors. However, YAAC and the legacy plugin are set up to search for an O/S distro provided copy of their native library to handle other operating systems and processors if the bundled library doesn't support the platform. For example, if you were running Linux on a Motorola 68000 processor, you could build RXTX on that system, install it, and then the legacy plugin would allow you access to serial ports using the 68000 native library you built. RXTX can be built for many more obscure CPU architectures than JSSC is set up for.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of daniel boggiano via groups.io <dboggny@...>
Sent: Friday, February 5, 2021 9:05 AM
To: [email protected]
Subject: [yaac-users] Plug-in Question

What is the legacy RXTX plugin? Will it help with getting pi0 working? I still can’t figure that out.

thanks
danny

What is the?legacy RXTX plugin? Will it help with getting pi0 working? I still can’t figure that out.

thanks
danny

The hop path lines I see are all green, even after going through a digi, and all appear to be the same length dash. Do I have a setting messed up somewhere?

Thanks,
You explained it quite well. That's kinda what I thought.
Jim Q