¿ªÔÆÌåÓý

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

java heap error message on rasp pi 3 when trying to download maps

 

java heap error message on rasp pi 3 when trying to download maps


anyone else encounter this, what did they do to fix the issue?


Re: Java 8_261 on Microsoft Windows breaks YAAC!

 

¿ªÔÆÌåÓý

Basically, yes. The actual gory details are here:

https://www.oracle.com/java/technologies/javase/8u261-relnotes.html

Note that the first issue in the release notes (after exhorting everyone to keep up on their security patches) is identifying that they've changed runtime libraries and the tools they've used to compile their Java virtual machine native code for Microsoft Windows. There's a file, msvcr100.dll, that is in the \Program Files\Java\jreversionnum\bin directory, that is used by both the Java runtime and the JSSC and RXTX native code DLLs on Windows. However, it has been replaced with a newer version in Java runtime 8_261 and later, so it's not there for JSSC or RXTX to use. Windows users using later releases of Java (9 through 14) will find similar issues if they take a patch update, if not now, in October when the next quarterly Critical Patch Update comes out from Oracle.

Note, of course, that there are different versions of msvcr100.dll, depending on whether you are in "Program Files" or "Program Files (x86)" (64-bit or 32-bit variant), so you can't just grab one randomly and drop it into your Windows installation of Java (if that is even allowed by your local system administrators). And I don't know if it's safe or possible to mix versions in the same running program.

So, my present plan is to:
  1. Get myself a copy of Visual Studio 2017.
  2. Recompile the native code in JSSC for Microsoft Windows using the 2017 runtime.
  3. Build an alternate version of the JSSC jar file with the recompiled Windows DLLs.
  4. Add code to YAAC to conditionally select the correct variant of the JSSC jar file based on the Java runtime version being used, for every release of Java from 8 to 14. I will assume that anyone still on Java 7 is using the old library version, and anyone on Java 15 or later will have only the new version. This will require researching Oracle's release notes to find which patch of each release is the transition point.
Hopefully, this will get everyone operating again.

I hope to have build 157 of YAAC out the door with these changes real soon.

Andrew, KA2DDO
________________________________________
From: [email protected] <[email protected]> on behalf of Ronny Julian <k4rjjradio@...>
Sent: Friday, July 24, 2020 3:54 PM
Subject: Re: [yaac-users] Java 8_261 on Microsoft Windows breaks YAAC!

Andrew is this it? ?Not a programmer so I'm googling. ?If there is a cost a Go Fund Me would be a great idea.

https://visualstudio.microsoft.com/vs/whatsnew/

On Fri, Jul 24, 2020 at 3:01 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
I've found out what the problem is.

Oracle (the owner of Java) has decided that it's time to use a newer version of Microsoft Visual Studio (2017) to compile the Windows version of the Java runtime native code. This, unfortunately, breaks all other native code invoked by Java (such as RXTX and JSSC) that depended on the older Visual Studio's runtime library.

It would have been nice if they'd sent out advance notice about this, so users of JNI (Java Native Interface) libraries also compiled with older versions of Visual Studio could have gotten ready in advance. No such luck, though. It looks like I'll be buying a new version of Visual Studio myself to handle recompiling the JSSC native code for Windows and patching the jssc.jar file so I don't have to wait for the author of JSSC to do it.

I'm thinking about how to handle users of older versions of the Java runtime on Windows, because (of course) Visual Studio is never backwards compatible. Are there any YAAC users on Microsoft Windows who aren't taking the latest version of the Java runtime (or of Windows) for any reason? I don't care why you're staying back, I just need to know if you are.

Note this doesn't affect Linux users. I'm not sure how it's going to affect Macintosh users.

Getting ready to spend money......

Andrew, KA2DDO
author of YAAC




Re: Java 8_261 on Microsoft Windows breaks YAAC!

Ronny Julian
 

Andrew is this it?? Not a programmer so I'm googling.? If there is a cost a Go Fund Me would be a great idea.

??


On Fri, Jul 24, 2020 at 3:01 PM Andrew P. <andrewemt@...> wrote:
I've found out what the problem is.

Oracle (the owner of Java) has decided that it's time to use a newer version of Microsoft Visual Studio (2017) to compile the Windows version of the Java runtime native code. This, unfortunately, breaks all other native code invoked by Java (such as RXTX and JSSC) that depended on the older Visual Studio's runtime library.

It would have been nice if they'd sent out advance notice about this, so users of JNI (Java Native Interface) libraries also compiled with older versions of Visual Studio could have gotten ready in advance. No such luck, though. It looks like I'll be buying a new version of Visual Studio myself to handle recompiling the JSSC native code for Windows and patching the jssc.jar file so I don't have to wait for the author of JSSC to do it.

I'm thinking about how to handle users of older versions of the Java runtime on Windows, because (of course) Visual Studio is never backwards compatible. Are there any YAAC users on Microsoft Windows who aren't taking the latest version of the Java runtime (or of Windows) for any reason? I don't care why you're staying back, I just need to know if you are.

Note this doesn't affect Linux users. I'm not sure how it's going to affect Macintosh users.

Getting ready to spend money......

Andrew, KA2DDO
author of YAAC



Java 8_261 on Microsoft Windows breaks YAAC!

 

I've found out what the problem is.

Oracle (the owner of Java) has decided that it's time to use a newer version of Microsoft Visual Studio (2017) to compile the Windows version of the Java runtime native code. This, unfortunately, breaks all other native code invoked by Java (such as RXTX and JSSC) that depended on the older Visual Studio's runtime library.

It would have been nice if they'd sent out advance notice about this, so users of JNI (Java Native Interface) libraries also compiled with older versions of Visual Studio could have gotten ready in advance. No such luck, though. It looks like I'll be buying a new version of Visual Studio myself to handle recompiling the JSSC native code for Windows and patching the jssc.jar file so I don't have to wait for the author of JSSC to do it.

I'm thinking about how to handle users of older versions of the Java runtime on Windows, because (of course) Visual Studio is never backwards compatible. Are there any YAAC users on Microsoft Windows who aren't taking the latest version of the Java runtime (or of Windows) for any reason? I don't care why you're staying back, I just need to know if you are.

Note this doesn't affect Linux users. I'm not sure how it's going to affect Macintosh users.

Getting ready to spend money......

Andrew, KA2DDO
author of YAAC


Re: Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

 

Andrew,

?I guess it is installed.. Just noticing it says it won't install if I click the button that says "Install" in plugins.. But all of the files are there.. It unzips them, but does not show as installed in the plugins.

As far as versions go, I am runing Raspbian Version 10 {buster}

Mike
AC0VP


Re: Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

 

Arrgh! They probably renamed the library package to something else. Gotta keep these Linux distros inconsistent..... :-( Which release of Raspbian are you using? Jessie? Wheezy? Or something else?

Unfortunately, the Bluecove library won't report the reason _why_ the library can't be activated.

By the way, what do you mean by "installing" the plugin? All you do to install a YAAC plugin is unzip the zip file into the plugins directory (or just drop the .jar file in the plugins directory if the plugin is distributed as only a single JAR file). As long as you have the operating system prerequisites also installed, that's all there is to it.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Michael LeComte <mike.lecomte@...>
Sent: Friday, July 24, 2020 12:52 PM
To: [email protected]
Subject: Re: [yaac-users] Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

Andrew,

bluetoothport.jar
bluecove-2.1.0.jar
bluecove-gpl-2.1.0.jar

Are all in the YAAC/Plugins Directory. But I noticed in YAAC, that if I actually try to install the plugin, it fails to install, another error related to Bluecove not being installed.

I have tried doing sudo apt-get install libbluetooth libbluetooth-dev and I get E: Unable to locate package libbluetooth, been trying to figure out what is causing that.. I know the actual bluetooth on the pi works fine, I can see and pair with devices.restart

I get a message stating Bluecove Library bluecove not available. When trying to install the plugin in YAAC. So not sure what is going on with this thing, have tried everything I can think of to get the Bluecove installed, but never seems to be detected.

Mike
AC0VP


Re: Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

 

Andrew,

bluetoothport.jar
bluecove-2.1.0.jar
bluecove-gpl-2.1.0.jar

Are all in the YAAC/Plugins Directory. But I noticed in YAAC, that if I actually try to install the plugin, it fails to install, another error related to Bluecove not being installed.

I have tried doing
sudo apt-get install libbluetooth libbluetooth-dev and I get E: Unable to locate package libbluetooth, been trying to figure out what is causing that.. I know the actual bluetooth on the pi works fine, I can see and pair with devices.restart

I get a message stating Bluecove Library bluecove not available. When trying to install the plugin in YAAC. So not sure what is going on with this thing, have tried everything I can think of to get the Bluecove installed, but never seems to be detected.

Mike
AC0VP


Re: Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

 

Looks like I need to make a fix to not loading YAAC plugins if there is an installation problem to at least let users read the help pages for the plugin, even if the rest of that plugin doesn't work.

For the Bluetooth plugin on Linux systems, you need to have the native Bluetooth user-mode libraries installed so the Java code can call them. On a Raspberry Pi (or other Debian/Ubuntu variants), issue the command

sudo apt-get install libbluetooth libbluetooth-dev

On Red Hat, Fedora Core, etc., issue the command

sudo dnf install bluez-libs

Also, verify that you have all three of the following JAR files in your YAAC/plugins directory:

bluetoothport.jar
bluecove-2.1.0.jar
bluecove-gpl-2.1.0.jar

All three should have been installed if you properly installed the plugin from the bluetoothport.zip distro file.

There may be an issue that the native stub library included with bluecove for ARM processors is named libbluecove_armv5tel.so, which may not jive with the CPU architecture model on the Raspberry Pi. If it doesn't work after confirming the JAR files and native Linux distro packages are installed, get back to me, and I'll see about improving the plugin distribution with a suitable native stub for Raspbian.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Michael LeComte <mike.lecomte@...>
Sent: Friday, July 24, 2020 11:53 AM
To: [email protected]
Subject: [yaac-users] Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

Hello all,

I have been trying to get my bluetooth stuff set up to work with YAAC on a new Raspberry Pi 4. I want to use this mobile with a TT4BT Serial Bluetooth device and a TT4 that I have in the Truck. I currently use a phone with aprsdroid to talk to the device, but would prefer to use YAAC on a raspberry pi with a 7" touch screen that I have set up.

I have gone through every tutorial that I can find, and nothing seems to work getting Bluecove installed.

I get the following error in YAAC {Newest Version}
Unable to access operating system Bluetooth stack: javax.bluetooth.BluetoothStateException: BlueCove library bluecove not available.
Decent instructions on Bluecove seem few and far between or are only for older versions of Raspbian.

Any help would be appreciated.

Mike
AC0VP


Anyone have a good Guide for Bluecove on a Raspberry Pi 4b

 

Hello all,

?I have been trying to get my bluetooth stuff set up to work with YAAC on a new Raspberry Pi 4. I want to use this mobile with a TT4BT Serial Bluetooth device and a TT4 that I have in the Truck. I currently use a phone with aprsdroid to talk to the device, but would prefer to use YAAC on a raspberry pi with a 7" touch screen that I have set up.

I have gone through every tutorial that I can find, and nothing seems to work getting Bluecove installed.?

?I get the following error in YAAC {Newest Version}
Unable to access operating system Bluetooth stack: javax.bluetooth.BluetoothStateException: BlueCove library bluecove not available.
Decent instructions on Bluecove seem few and far between or are only for older versions of Raspbian.

Any help would be appreciated.

Mike
AC0VP


Re: next beta build#155 of YAAC, created 2020-Jul-13

 

Does the new build work for you? You may have to manually download it and unzip over the existing installation to get the update, since you may not be able to start YAAC, even if you use the -clearPorts option to keep YAAC from opening any serial ports with the old RXTX library.

________________________________________
From: [email protected] <[email protected]> on behalf of Jerald Meadows - NOAA Federal via groups.io <jerald.meadows@...>
Sent: Thursday, July 23, 2020 11:46 AM
To: [email protected]
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Awesome. We don't say it enough but you sir are a rockstar! Thank you for everything you do.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
Weather.gov/Hanford<> | Twitter<> | Facebook<>



On Thu, Jul 23, 2020 at 8:19 AM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io<>" <jerald.meadows@...<mailto:[email protected]>>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]<mailto:[email protected]>
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
Weather.gov/Hanford<> | Twitter<> | Facebook<>



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
position report messages that have the absolute bare minimum amount
of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
sentences as an alternate-DeviceID KISS "frame" in the serial
connection to YAAC, when the GKRELAY command is properly configured.
This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
the sentence boundaries aren't caught correctly, causing spurious
errors that can't be read because of the embedded carriage return
characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
little more.
8. add generic ability for PortConnectors to report asynchronous status
changes not already handled by PortStatusListener, PortMgmtListener,
or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
PortConnector, as it will never work unless the TinyTrak4 is
rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
window close button behaves the same as the Cancel button in the
upgrader's UI.
18. augment upgrader to support plugins that include native libraries
(in preparation for deprecating use of RXTX library).


Re: Water not rendering, again... kind of.

 

I downloaded the Southeastern US PBF from Geofabrik. So, with the ocean not being included the Chesapeake Bay is also not being rendered because of an incomplete coastline. That seems to make sense.

Thanks,
Eric WG3K

©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\

On Thursday, July 23, 2020 6:20 PM, Andrew P. <andrewemt@...> wrote:

Is it the complete planet data, or just the local area? Oceans don't get processed properly unless the entire planet is processed to extract the ocean boundaries (a relatively new feature in YAAC) and both the ocean shapefile and the PBF are present for processing.

I recommend getting the maps by downloading pre-imported tiles.

Andrew, KA2DDO
author of YAAC

From: [email protected] [email protected] on behalf of Eric H. Christensen via groups.io eric@...
Sent: Tuesday, July 21, 2020 12:13 PM
To: [email protected]
Subject: Re: [yaac-users] Water not rendering, again... kind of.

©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Thursday, July 16, 2020 9:40 PM, Andrew P. andrewemt@... wrote:

What build of YAAC are you using, and what snapshot of OpenStreetMap data? The latter can be seen by going to File->OpenStreetMap->Download Pre-Imported Map Tiles, and (when the dialog window finally comes up after scanning your map directories) looking in the Old Tile Version text box (lower left corner). I only got it fixed for the most recent import I did of the data (2020-05-11T00:00:01Z), because it is an import issue, not a rendering issue.
Okay, interesting... I'm using a downloaded PBF directly from an OSM mirror which gives me the most recent changes to the cartographic data.

This is in Beta 155.

73,
Eric WG3K


Re: Water not rendering, again... kind of.

 

Is it the complete planet data, or just the local area? Oceans don't get processed properly unless the entire planet is processed to extract the ocean boundaries (a relatively new feature in YAAC) and both the ocean shapefile and the PBF are present for processing.

I recommend getting the maps by downloading pre-imported tiles.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Eric H. Christensen via groups.io <eric@...>
Sent: Tuesday, July 21, 2020 12:13 PM
To: [email protected]
Subject: Re: [yaac-users] Water not rendering, again... kind of.

©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Thursday, July 16, 2020 9:40 PM, Andrew P. <andrewemt@...> wrote:

What build of YAAC are you using, and what snapshot of OpenStreetMap data? The latter can be seen by going to File->OpenStreetMap->Download Pre-Imported Map Tiles, and (when the dialog window finally comes up after scanning your map directories) looking in the Old Tile Version text box (lower left corner). I only got it fixed for the most recent import I did of the data (2020-05-11T00:00:01Z), because it is an import issue, not a rendering issue.
Okay, interesting... I'm using a downloaded PBF directly from an OSM mirror which gives me the most recent changes to the cartographic data.

This is in Beta 155.

73,
Eric WG3K


new beta build#156 of YAAC, created 2020-Jul-23

 

Note that there is an outage at SourceForge, so this hasn't been uploaded there yet. It is
available at
----------------------------------------------------------------------------------------------

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

downloadable from
or

changes and updates include:
1. replace obsolete RXTX serial port library with newer JSSC library.
Note this adds built-in support for Solaris x86 and Linux on ARM
processors, but may make use on platforms without built-in support
more difficult than it was for RXTX. This also removes the user
account requirement to have write access to the system lock
directory, as JSSC uses kernel locking instead of old-style
lock files.
2. provide plugin to restore use of RXTX instead of JSSC (for platforms
that aren't supported on JSSC).
3. add support for submit-only UDP port to APRS-IS servers. Note this
may be unreliable, as not all APRS-IS servers support UDP submissions
and it is unlikely that your computer will be informed if such service
doesn't exist on the selected server.
4. minor performance improvements and documentation fixes.
5. update repeater finder plugin to also use JSSC instead of RXTX.


Re: Bluetooth error

 

Note that's the documentation for the Bluetooth plugin, not for core YAAC. :-)

________________________________________
From: [email protected] <[email protected]> on behalf of Steve Black via groups.io <kb1chu@...>
Sent: Thursday, July 23, 2020 4:11 PM
To: [email protected]
Subject: Re: [yaac-users] Bluetooth error

This is what happens when you get thinking you already read the instructions. My bad. I'll try that this evening. I use windows a lot. But like the form factor of the Raspi. I'm making a backpack radio setup and need a light weight computer to tag long. It works great with YAAC.Thank you Steve kb1chu

On 7/23/2020 3:55 PM, Andrew P. wrote:

Per the documentation, you need to install the Bluetooth native client library for YAAC to call on your Raspberry Pi.

sudo apt-get install libbluetooth libbluetooth-dev

Then the Bluetooth plugin should work.

Thanks for finding the typo on my website; it has been fixed.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected]<mailto:[email protected]> <[email protected]><mailto:[email protected]> on behalf of Steve Black via groups.io <kb1chu@...><mailto:kb1chu@...>
Sent: Thursday, July 23, 2020 3:20 PM
To: [email protected]<mailto:[email protected]>
Subject: [yaac-users] Bluetooth error

I noticed a minor error in the instructions to install YAAC on a Raspberry Pi. I believe it should be downloads instead of download. I am still a novice with Linux. Also the Bluetooth does not seem to load correctly on Arm chips. I tried to download the Bluetooth add on and if I do upon startup I get an error telling me the Bluetooth lib did not load. As i don't use Bluetooth but plan to in the future I deleted YAAC and then reinstalled it with out enabling the Bluetooth add on installed. Thanks Steve kb1chu

On 7/23/2020 11:10 AM, Andrew P. wrote:
I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io" <jerald.meadows@...><mailto:jerald.meadows@...><mailto:jerald.meadows@...><mailto:jerald.meadows@...>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
Weather.gov/Hanford<><> | Twitter<><> | Facebook<><>



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...<mailto:andrewemt@...><mailto:andrewemt@...><mailto:andrewemt@...>> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
position report messages that have the absolute bare minimum amount
of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
sentences as an alternate-DeviceID KISS "frame" in the serial
connection to YAAC, when the GKRELAY command is properly configured.
This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
the sentence boundaries aren't caught correctly, causing spurious
errors that can't be read because of the embedded carriage return
characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
little more.
8. add generic ability for PortConnectors to report asynchronous status
changes not already handled by PortStatusListener, PortMgmtListener,
or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
PortConnector, as it will never work unless the TinyTrak4 is
rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
window close button behaves the same as the Cancel button in the
upgrader's UI.
18. augment upgrader to support plugins that include native libraries
(in preparation for deprecating use of RXTX library).


Re: Bluetooth error

 

¿ªÔÆÌåÓý

This is what happens when you get thinking you already read the instructions. My bad. I'll try that this evening. I use windows a lot. But like the form factor of the Raspi. I'm making a backpack radio setup and need a light weight computer to tag long. It works great with YAAC.Thank you Steve kb1chu

On 7/23/2020 3:55 PM, Andrew P. wrote:

Per the documentation, you need to install the Bluetooth native client library for YAAC to call on your Raspberry Pi. 

sudo apt-get install libbluetooth libbluetooth-dev

Then the Bluetooth plugin should work.

Thanks for finding the typo on my website; it has been fixed.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Steve Black via groups.io <kb1chu@...>
Sent: Thursday, July 23, 2020 3:20 PM
To: [email protected]
Subject: [yaac-users] Bluetooth error

I noticed a minor error in the instructions to install YAAC on a Raspberry Pi. I believe it should be downloads instead of download. I am still a novice with Linux. Also the Bluetooth does not seem to load correctly on Arm chips. I tried to download the Bluetooth add on and if I do upon startup I get an error telling me the Bluetooth lib did not load. As i don't use Bluetooth but plan to in the future I deleted YAAC and then reinstalled it with out enabling the Bluetooth add on installed. Thanks Steve kb1chu

On 7/23/2020 11:10 AM, Andrew P. wrote:
I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io" <jerald.meadows@...><mailto:jerald.meadows@...>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]<mailto:[email protected]>
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
Weather.gov/Hanford | Twitter | Facebook



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from 
               or 

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
    position report messages that have the absolute bare minimum amount
    of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
    packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
    sentences as an alternate-DeviceID KISS "frame" in the serial
    connection to YAAC, when the GKRELAY command is properly configured.
    This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
    drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
    map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
    the sentence boundaries aren't caught correctly, causing spurious
    errors that can't be read because of the embedded carriage return
    characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
    little more.
8. add generic ability for PortConnectors to report asynchronous status
    changes not already handled by PortStatusListener, PortMgmtListener,
    or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
    PortConnector, as it will never work unless the TinyTrak4 is
    rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
     Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
     when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
     Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
     still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
     window close button behaves the same as the Cancel button in the
     upgrader's UI.
18. augment upgrader to support plugins that include native libraries
     (in preparation for deprecating use of RXTX library).







Re: Bluetooth error

 

Per the documentation, you need to install the Bluetooth native client library for YAAC to call on your Raspberry Pi.

sudo apt-get install libbluetooth libbluetooth-dev

Then the Bluetooth plugin should work.

Thanks for finding the typo on my website; it has been fixed.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Steve Black via groups.io <kb1chu@...>
Sent: Thursday, July 23, 2020 3:20 PM
To: [email protected]
Subject: [yaac-users] Bluetooth error

I noticed a minor error in the instructions to install YAAC on a Raspberry Pi. I believe it should be downloads instead of download. I am still a novice with Linux. Also the Bluetooth does not seem to load correctly on Arm chips. I tried to download the Bluetooth add on and if I do upon startup I get an error telling me the Bluetooth lib did not load. As i don't use Bluetooth but plan to in the future I deleted YAAC and then reinstalled it with out enabling the Bluetooth add on installed. Thanks Steve kb1chu

On 7/23/2020 11:10 AM, Andrew P. wrote:
I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io" <jerald.meadows@...><mailto:jerald.meadows@...>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]<mailto:[email protected]>
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
Weather.gov/Hanford<> | Twitter<> | Facebook<>



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...<mailto:andrewemt@...>> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
position report messages that have the absolute bare minimum amount
of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
sentences as an alternate-DeviceID KISS "frame" in the serial
connection to YAAC, when the GKRELAY command is properly configured.
This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
the sentence boundaries aren't caught correctly, causing spurious
errors that can't be read because of the embedded carriage return
characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
little more.
8. add generic ability for PortConnectors to report asynchronous status
changes not already handled by PortStatusListener, PortMgmtListener,
or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
PortConnector, as it will never work unless the TinyTrak4 is
rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
window close button behaves the same as the Cancel button in the
upgrader's UI.
18. augment upgrader to support plugins that include native libraries
(in preparation for deprecating use of RXTX library).


Bluetooth error

 

¿ªÔÆÌåÓý

I noticed a minor error in the instructions to install YAAC on a Raspberry Pi. I believe it should be downloads instead of download. I am still a novice with Linux. Also the Bluetooth does not seem to load correctly on Arm chips. I tried to download the Bluetooth add on and if I do upon startup I get an error telling me the Bluetooth lib did not load. As i don't use Bluetooth but plan to in the future I deleted YAAC and then reinstalled it with out enabling the Bluetooth add on installed. Thanks Steve kb1chu

On 7/23/2020 11:10 AM, Andrew P. wrote:

I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io" <jerald.meadows@...>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
?|??|?



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
? ? ? ? ? ? ? ?or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
? ? position report messages that have the absolute bare minimum amount
? ? of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
? ? packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
? ? sentences as an alternate-DeviceID KISS "frame" in the serial
? ? connection to YAAC, when the GKRELAY command is properly configured.
? ? This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
? ? drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
? ? map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
? ? the sentence boundaries aren't caught correctly, causing spurious
? ? errors that can't be read because of the embedded carriage return
? ? characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
? ? little more.
8. add generic ability for PortConnectors to report asynchronous status
? ? changes not already handled by PortStatusListener, PortMgmtListener,
? ? or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
? ? PortConnector, as it will never work unless the TinyTrak4 is
? ? rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
? ? ?Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
? ? ?when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
? ? ?Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
? ? ?still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
? ? ?window close button behaves the same as the Cancel button in the
? ? ?upgrader's UI.
18. augment upgrader to support plugins that include native libraries
? ? ?(in preparation for deprecating use of RXTX library).



Re: next beta build#155 of YAAC, created 2020-Jul-13

Jerald Meadows - NOAA Federal
 

Awesome. We don't say it enough but you sir are a rockstar! Thank you for everything you do.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
?|??|?



On Thu, Jul 23, 2020 at 8:19 AM Andrew P. <andrewemt@...> wrote:
I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via " <jerald.meadows=[email protected]>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
?|??|?



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
? ? ? ? ? ? ? ?or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
? ? position report messages that have the absolute bare minimum amount
? ? of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
? ? packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
? ? sentences as an alternate-DeviceID KISS "frame" in the serial
? ? connection to YAAC, when the GKRELAY command is properly configured.
? ? This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
? ? drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
? ? map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
? ? the sentence boundaries aren't caught correctly, causing spurious
? ? errors that can't be read because of the embedded carriage return
? ? characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
? ? little more.
8. add generic ability for PortConnectors to report asynchronous status
? ? changes not already handled by PortStatusListener, PortMgmtListener,
? ? or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
? ? PortConnector, as it will never work unless the TinyTrak4 is
? ? rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
? ? ?Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
? ? ?when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
? ? ?Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
? ? ?still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
? ? ?window close button behaves the same as the Cancel button in the
? ? ?upgrader's UI.
18. augment upgrader to support plugins that include native libraries
? ? ?(in preparation for deprecating use of RXTX library).



Re: next beta build#155 of YAAC, created 2020-Jul-13

 

¿ªÔÆÌåÓý

I am preparing to release a new build of YAAC that no longer uses the obsolete RXTX library to access serial ports, but a newer library called JSSC. It should be out later today.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Jerald Meadows - NOAA Federal via groups.io" <jerald.meadows@...>
Date: 7/23/20 09:58 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] next beta build#155 of YAAC, created 2020-Jul-13

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
?|??|?



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
? ? ? ? ? ? ? ?or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
? ? position report messages that have the absolute bare minimum amount
? ? of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
? ? packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
? ? sentences as an alternate-DeviceID KISS "frame" in the serial
? ? connection to YAAC, when the GKRELAY command is properly configured.
? ? This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
? ? drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
? ? map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
? ? the sentence boundaries aren't caught correctly, causing spurious
? ? errors that can't be read because of the embedded carriage return
? ? characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
? ? little more.
8. add generic ability for PortConnectors to report asynchronous status
? ? changes not already handled by PortStatusListener, PortMgmtListener,
? ? or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
? ? PortConnector, as it will never work unless the TinyTrak4 is
? ? rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
? ? ?Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
? ? ?when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
? ? ?Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
? ? ?still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
? ? ?window close button behaves the same as the Cancel button in the
? ? ?upgrader's UI.
18. augment upgrader to support plugins that include native libraries
? ? ?(in preparation for deprecating use of RXTX library).



Re: next beta build#155 of YAAC, created 2020-Jul-13

 

Howdy YAAC community,

We (NWS Hanford) recently updated our JRE for security reasons. This has caused an issue with YAAC. The program no longer opens completely. I am told it tries but then crashes. I have attached the error log entry we have. Any assistance would be greatly appreciated.

Jerald Meadows
Warning Coordination Meteorologist
San Joaquin Valley/Hanford Weather Forecast Office
P: 559.584.0583 X 223
?|??|?



On Mon, Jul 13, 2020 at 2:09 PM Andrew P. <andrewemt@...> wrote:
next beta build#155 of YAAC ("Yet Another APRS Client"), created 2020-Jul-13

downloadable from
? ? ? ? ? ? ? ?or

changes and updates include:
1. fix spurious ArrayIndexOutOfBoundsExceptions from parsing Mic-E and
? ? position report messages that have the absolute bare minimum amount
? ? of text and have no optional fields appended.
2. fix progress dialog percentage report when importing CSV-format
? ? packet logs.
3. add support for the Byonics TinyTrak4's ability to pass through GPS
? ? sentences as an alternate-DeviceID KISS "frame" in the serial
? ? connection to YAAC, when the GKRELAY command is properly configured.
? ? This updates the Serial_TNC, KISS-over-TCP, and Bluetooth_TNC port
? ? drivers (Bluetooth plugin).
4. regularize size of map zoom buttons, fix sizing and scaling of
? ? map scale to always be a round multiple of 2, 5, or 10.
5. properly handle seamark beacons with an unspecified color.
6. fix problem with AX.25 ports that feed through GPS sentences when
? ? the sentence boundaries aren't caught correctly, causing spurious
? ? errors that can't be read because of the embedded carriage return
? ? characters.
7. try to optimize reading UTF-8 strings and OSM objects from files a
? ? little more.
8. add generic ability for PortConnectors to report asynchronous status
? ? changes not already handled by PortStatusListener, PortMgmtListener,
? ? or PortEventListener.
9. remove support for Byonics TT4 prompt catching in Serial_TNC
? ? PortConnector, as it will never work unless the TinyTrak4 is
? ? rebooted just as YAAC opens the port.
10. fix naming of AIS decoder plugin in website "store".
11. fix parsing errors in AIS decoder, add support for DGNSS and
? ? ?Aid-to-Navigation messages.
12. add identification of vessel nation-of-registry in AIS decoder.
13. remove spurious debugging print statements in repeater finder plugin.
14. improve error reporting and documentation in repeater finder plugin
? ? ?when rig control serial ports can't be found.
15. add support to repeater finder plugin to recognize Yaesu System
? ? ?Fusion (C4FM) repeater objects.
16. add Java Activation library to telemetry alarm plugin so email will
? ? ?still work on Java runtime version 9 and above.
17. improve screen appearance of upgrade utility, ensure O/S-provided
? ? ?window close button behaves the same as the Cancel button in the
? ? ?upgrader's UI.
18. augment upgrader to support plugins that include native libraries
? ? ?(in preparation for deprecating use of RXTX library).