I got the same error.?

error occurred during initialization of VM
server VM is only supported on ARMv7+ VFP

Interesting. That implies that the Java runtime included with Raspbian won't work on the ARM chip the Pi Zero has on board.

Just for chuckles, in a command window on the Pi, enter the following commands:

arch
java -client -version


________________________________________
From: [email protected] <[email protected]> on behalf of daniel boggiano via Groups.Io <dboggny@...>
Sent: Thursday, January 16, 2020 7:15 PM
To: [email protected]
Subject: Re: [yaac-users] Pi 0?

The error is:
error occurred during initialization of VM
server VM is only supported on ARMv7+ VFP.

with regards to your other instructions, I have not yet tried the Bluetooth plug in as you suggest but bind the kenwood kiss tnc and create a port in Yaac. Only because that’s how I learned to do it and so I keep doing that way. I will try the Bluetooth plugin however as I continue to learn this program.

thanks

The error is:
error occurred during initialization of VM
server VM is only supported on ARMv7+ VFP.?

with regards to your other instructions, I have not yet tried the Bluetooth plug in as you suggest but bind the kenwood kiss tnc and create a port in Yaac. Only because that’s how I learned to do it and so I keep doing that way. I will try the Bluetooth plugin however as I continue to learn this program.?

thanks

开云体育

-------- Original message --------
From: "Andrew P." <andrewemt@...>
Date: 1/16/20 16:10 (GMT-05:00)
To: "daniel boggiano via Groups.Io" <dboggny@...>
Subject: Re: [yaac-users] Pi 0?



-------- Original message --------
From: "daniel boggiano via Groups.Io" <dboggny@...>
Date: 1/16/20 15:41 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] Pi 0?

Last time I tried to run it, it gave me an error on the 0. I will try again and write down exactly what it said. As far as interface etc, VNC from iPhone/iPad as my screen keyboard as well as a Bluetooth keyboard. My desire was just to use the kenwood port Bluetooth with my HT for aprs.?

Last time I tried to run it, it gave me an error on the 0. I will try again and write down exactly what it said. As far as interface etc, VNC from iPhone/iPad as my screen keyboard as well as a Bluetooth keyboard. My desire was just to use the kenwood port Bluetooth with my HT for aprs.?

There's no reason why YAAC _shouldn't_ run on a Pi Zero, other than response time (it ran on a Pi 1B). But what are you going to display the output on? If you have to drag an HDMI monitor around to see the results, you're not really saving much in terms of weight/bulk/power consumption. Also, a Pi Zero is a bit skimpy on CPU power and RAM, so you might have trouble fitting YAAC onto it with reasonable responsiveness (it was sluggish on the Pi 1B). And what are you going to use for human user input to YAAC (touchscreen, Bluetooth keyboard/glidepad, etc.)?

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of daniel boggiano via Groups.Io <dboggny@...>
Sent: Thursday, January 16, 2020 11:07 AM
To: [email protected]
Subject: [yaac-users] Pi 0?

Is there any way to get YAAC to run on a Pi 0. I would like to use it as a “screen” or data viewer for my kenwood HT via Bluetooth.
Thanks

Thank you for the quick reply.
I verified librxtx-java was installed. Went through the expert mode configuration. Could not see anything wrong with it. Verified call sign passcode.
Just for the fun of it I logged out and back in as root. Started YAAC and it ran the configuration. After configuration YAAC runs flawlessly. If I log out as root and back in as a user, it will not function again. The configuration appears to be identical. Logging back in as root and it functions well. It’s got me bewildered. All I can think of is maybe a corrupt configuration file. Not sure where to go from here.
Thank you for the assistance
Alan N2ZVN

That's odd. You should have been getting that error all along unless you did some upgrade to Raspbian that uninstalled the librxtx-java package (the library that implements hardware serial port access for YAAC). Ensure it is installed by issuing the following command at a LXTerminal prompt:

sudo apt-get install librxtx-java

As for no longer showing up on aprs.fi, since you reconfigured your system, my guess is that you either:

1. disabled the beacon from being transmitted;
2. changed the definition of your APRS-IS port to Transmit Disabled; or
3. didn't enter your APRS-IS server passcode correctly so the backbone server won't accept your transmitted traffic.

So, _don't_ use the configuration wizard. Instead, use File->Configure->Expert Mode, and check that the Beacon tab shows your beacon is enabled, and the Ports tab, when you click on your APRS-IS port in the table and click the Edit button, shows that the port is Transmit Enabled and make sure you have the correct passcode entered.

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Alan Bartkowiak <N2ZVN.AE@...>
Sent: Tuesday, January 14, 2020 5:31 PM
To: [email protected]
Subject: [yaac-users] RXTX native library not found

Good afternoon Andrew,
Not sure where to begin here. First of all I am very new to Linux so everything I do with it has to be looked up from commands to syntax.
I am using a raspberry Pi 4b with raspbian buster. I had YAAC running flawlessly for about 2 weeks in a APRS-IS fashion. Will be adding digi and Igate in the very near future through direwolf. The problem is it worked fine till I installed the last version of YAAC 20200110. When YAAC was restarted, I got the error RXTX native library not found. After clicking OK I was taken to the configuration wizard. I reconfigured and now all I get is receive packets. My node no longer shows up on APRS.fi and can no longer send messages. The error message no longer shows up on a restart however can not TX.
I followed the help file for install Librxtx-java
But got a file not found error.
Thank you for any assistance in advance,
Alan N2ZVN

Good afternoon Andrew,
Not sure where to begin here. First of all I am very new to Linux so everything I do with it has to be looked up from commands to syntax.
I am using a raspberry Pi 4b with raspbian buster. I had YAAC running flawlessly for about 2 weeks in a APRS-IS fashion. Will be adding digi and Igate in the very near future through direwolf. The problem is it worked fine till I installed the last version of YAAC 20200110. When YAAC was restarted, I got the error RXTX native library not found. After clicking OK I was taken to the configuration wizard. I reconfigured and now all I get is receive packets. My node no longer shows up on APRS.fi and can no longer send messages. The error message no longer shows up on a restart however can not TX.
I followed the help file for install Librxtx-java
But got a file not found error.
Thank you for any assistance in advance,
Alan N2ZVN

THANK YOU Andrew :-) Your reply to my question has enabled me to now understand the core concepts of APRS and cleared up the mystery I have been trying to unravel for quite some time!

Greetings, Nigel.

This will be a rather long and rambling treatise to cover your questions.

The important thing to know about APRS is that it was designed for local tactical information over low-bandwidth radio links, not global messaging over the Internet. The APRS-IS Internet backbone is a useful extension to APRS, but it is merely a cool extra feature; it is by no means an essential part of APRS.

As such, it is perfectly expected that APRS networks will be entirely on RF over a contiguous geographical region. For example, a local charity bicycle ride event I work covers about 4 counties and uses APRS entirely over RF on a non-standard frequency (partially because they don't want ambulance-chasing lawyers and mass-media reporters heading to any problems that might occur, but mostly so they don't have to wade through irrelevant [to them] users of APRS to find their information or lose their information due to channel congestion). This radio network has no Internet connection at all. Similarly, our county ARES group runs APRS weather stations all over the county to provide micro-climate data to county Emergency Management. It runs entirely over RF to get the data to the county offices, and then over their in-building intranet to get to their GIS systems from our co-located I-gate.

Similarly, there is no "global server" in APRS. Like almost every other mode in amateur radio, there is no central control managing the field stations, unlike, for example, cellular telephones managed by the regional central switching office that also controls the cell tower base stations. APRS is an arbitrary peer-to-peer network, rather than a star-topology hub-to-leaf-nodes network. Some people have implemented specific services on APRS (such as the ANSRVR, WHO-IS, and EMAIL-2 pseudo-stations), but they are just other callsign-identified arbitrary points on the network that just happen to be located on the Internet backbone so they can be reached globally.

An RF-only station can easily set up a service, but it would only be reachable by stations within RF contact (directly or via digipeater), or via a Tx I-gate from more distant locations. For example, the APRS QRU service is deliberately intended to be a local RF service, not an Internet service. It is intended that a local RF user can send a text message to QRU with an information request (ex.: RP2M to find a list of local 2-meter analog repeaters), and any nearby stations that support QRU service and have this information will respond. The local RF user initiating the request has no need for a QRU response from the opposite side of the globe (and such a response would be totally useless anyway).

Most of the information in APRS is collected directly from the originators, not from central servers. Referring to the bicycle event again, the consumers (both redundant Net Control stations) receive the position reports from each support vehicle mobile station directly or via digipeater; the data isn't routed through a global server on the Internet. As such, each local peer in the APRS network is not only capable of sending its traffic via undirected multicast to all nearby stations, but can hear all other nearby stations (and digipeater relays for more distant stations) directly and use the pieces of information it hears as it chooses without needing to get the data via some central gate-keeping (and Single Point Of Failure) server.

Note that I specifically designed my YAAC software to function in the "off the Internet" mode. That is why it carries its own local copy of the map data instead of downloading it constantly from an Internet server. Yes, it can connect to the APRS-IS Internet backbone and use some other Internet-based services, but it is fully capable of functioning without them (and most other APRS client programs are, too).

When you hear the term "digipeater", it refers exactly to the "parrot type simplex repeater" you asked about in your message, although they are somewhat smarter than a dumb relay so as to avoid unnecessary retransmissions of packets (see Bob Bruninga's explanation of the New-N paradigm for digipeating to understand why). There are many different implementations of digipeaters available, either using commercially manufactured TNCs with alternate firmware, to software TNCs with digipeater capabilities, to conventional TNCs with custom applications behind them to perform the digipeating operations. The only thing they have in common is having a radio transceiver attached to them. Of course, such automated relay stations require appropriate authorizations from your national governmental authority (what authorizations are required vary with the jurisdiction).

aprs.fi is an Internet-based consumer of APRS packet data. It does not produce anything back to the APRS network (not an APRS data source); rather, it is a data assembler, combining received historical APRS packet data with Google Maps and several other data sources to provide a composite display. But any good APRS client does the same job to some extent.

So, if you want to provide an APRS data "service", you need to define what that service is going to provide and how clients are going to ask for it (such as the WHO-IS service accepting a callsign as input and responding with the name, licensing jurisdiction, and license class of the callsign holder), and then have your APRS software be prepared to recognize service requests when they come in and answer them, just as the QRU service does. And it shouldn't matter what path your clients use to request the service, just as it doesn't matter on the Internet what kind of technology your Internet service provider used to link you to the rest of the Internet.

I hope this helps explain APRS and remove some of the misconceptions about it being an Internet-dependent system (which it is not).

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Nigel <zs6rn@...>
Sent: Sunday, January 12, 2020 3:43 AM
To: [email protected]
Subject: [yaac-users] Stand alone (no internet) field APRS 'service'

Hello from sunny South Africa :-)
Recently I posted a question on another APRS forum and unfortunately have received only one response and regrettably that reply has not fully answered my query (as an aside it was as a P.M. so it seems that none of the forum members willing to share their knowledge). Am now asking here (YAAC users) in the hope that someone will be able to respond so that I can better understand what is required for a stand alone APRS 'service'.

Advance apologies for showing my ignorance but I figure that if I do not ask the question, then I will remain in the dark regarding how APRS works overall...

1st my current understanding of 'how APRS works':
When using an APRS client e.g. APRSDroid, YAAC or similar, data packets are exchanged with a global server via the Internet via whatever transport medium is enabled e.g. RF and an IGate, Data via the cellular network or even audio from a recording (how I plan on experimenting <smile>) and then to the Internet or perhaps using an Internet connection at a home base.
These data packets convey the information necessary to enable the plotting of objects / stations / whatever on a map positioned according to the appropriate location co-ordinates derived via GPS or entered manually. Other traffic such as messaging is also carried by the data packets and the resulting 'text' displayed in the appropriate 'fields'.
So far so good (I hope).
Now the part I would like to better understand / specific question. What is / are the 'service(s)' being provided at the 'server' end of the APRS infrastructure e.g. and how can a 'standalone' (no internet available / required) service utilising only RF be facilitated so that LOCAL participants can track and be tracked using APRS features e.g. During a local event remote from cellular / data services.
I can visualise a scenario with there being an RF IGate assuming that there is some path to an Internet connection from said gateway, but if there is no Internet available and local tracking of resources and text messaging between stations is required?
Would a RF 'relay' of whatever received (a parrot type simplex 'repeater') provide desired functionality and if yes, what software could be used to implement (Linux preferred)?
Again my apologies for taking up bandwidth with what is probably considered something that is known by even the newest of newcomers to APRS, but I want to learn (and one day implement a portable standalone RF based APRS 'server') so hence the post and exposing my ignorance.
BIG thanks in advance for any and all feedback.
73 Nigel ZS6RN ex G8DEV

Hi, Gerold.

Thank you for your feedback. I was afraid of something like this, as Google is not the greatest translation dictionary in the world (not surprising, with the limited context it gets). I was never particularly fluent in sprecht Deutsch (two years in high school as a foreign language and then never using it again for 30+ years is not a good foundation), but I did the best I could. I would appreciate you reporting any corrections that need to be made, so I can fix the German translation file.

To change the display language in YAAC, you need to change the locale that YAAC is running in; the language is picked based on the operating system locale.

On Linux, it's easy. You can change the LANG environment variable from its default to en or en_US easily:

LANG=en_US java -jar YAAC.jar

On any platform, you can also override the locale for the Java virtual machine running YAAC with a Java system property:

java -Duser.language=en -jar YAAC.jar

But, please, tell me where I screwed up in the translations, so I can fix them.

Andrew, KA2DDO
author of YAAC

________________________________________
From: Gerold Kiesslich <gerold.kiesslich@...>
Sent: Saturday, January 11, 2020 7:51 AM
To: Andrew P.
Subject: Language in YAAC

Hi Andrew,

I have a question regarding the language adjustment in YAAC: I want to
change it from German back English, since the german terms are somehow
misleading. How can I do this?

Do I have to do a new installation?

73 gero DL5KLX

FYI, some newer Linux distributions have dropped ifconfig in favor of
ip. Some of the same output can be seen with:

ip address

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

Greetings.

Yes, the aprsisserver plugin will more or less do what you want. All you need to do on the server-side instance of YAAC is add the plugin.

On the client side, you need to create a port of type APRS-IS and specify the host name as the IP address of your server system by typing it in (instead of picking a standard hostname from the list), and use the default port number 14580. Basically, the plugin on the "server" makes it act (sort of) like a Tier 2 backbone server (like the ones you would get with the noam.aprs2.net hostname), so other systems can connect to it the way they would connect to the Tier 2 backbone.

If you don't know what the IP address of your "server" system is, create a command prompt window on the "server" and type "ifconfig -a" (on a Linux system) or "ipconfig" (on a Microsoft Windows system). This should display your system's numeric IP address (a group of 4 numbers typically like 192.168.1.100, and the periods between them are important).

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Rob Doar <robdoar@...>
Sent: Friday, January 10, 2020 6:08 PM
To: [email protected]
Subject: [yaac-users] aprsisserver help

I have YAAC set up on a raspberry pi, and I'd like to use YAAC on another machine to view the data. It looks like the aprsisserver plugin will achieve this. I've installed it but can't find any config options or information on how to connect the client machine to the server.

What am I missing?

Thanks!

I have YAAC set up on a raspberry pi, and I'd like to use YAAC on another machine to view the data. It looks like the?aprsisserver plugin will achieve this. I've installed it but can't find any config options or information on how to connect the client machine to the server.?

What am I missing?

Thanks!

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

downloadable from
or

changes and updates include:
1. properly identify scope of Object/Item reports received over RF
by scanning the digipeater list for RFONLY and NOGATE aliases.
2. better calculate the transmit time for AX.25 frames for traffic
analysis.
3. fix infinite loop in processing OpenTRAC sequence number elements.
4. fix incorrect RF-transmitting station identification and tocall
for a Tx I-gate YAAC station.
5. log traffic forwarded by a Tx I-gate to the I-gate station as well
as to the originating station (i.e., how much local RF traffic is
the I-gate creating?).
6. fix bug where popup menus launched from the popup station information
window (launched by left-clicking or touchscreen touching a station
on the map) show selections suitable for a textual table display
rather than for a map.
7. minor optimizations to the OpenStreetMap PBF-format importer.
8. add built-in help to the Small Screen plugin.
9. add piped command support to the Sounds plugin in case the
text-to-speech synthesizer program needs its output piped to
another program to reach the correct sound card and speakers.