Cannot connect to fldigi using KISS-over-TCP
Greetings,
I've got fldigi configured to listen on port 8001, TCP/IP, Listen/Bind, Auto Connect/Retry.
In YAAC, I configure a KISS-over-TCP port, localhost, 8001. Sometimes when I save the port it doesn't actually save properly. I'll go back in and my callsign would be missing and, when I was using a port other than 8001, the port number would be missing. Every time I try to enable the port I get the following error:
1702507944738: PortEditor: starting to create editor
1702507944739: PortEditor: starting to create per-driver cards
1702507944739: PortEditor: loading editor class for KISS-over-TCP
1702507944739: PortEditor: creating card for KISS-over-TCP
1702507944803: PortEditor: creating card selector
1702507944812: PortEditor: selected appropriate default card KISS-over-TCP
1702507944812: PortEditor: created.
Wed Dec 13 17:52:29 EST 2023: opening TCP socket to KISS TNC at localhost/127.0.0.1:8001
Error Opening Port; Discard This Port?: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.ka2ddo.yaac.io.KissOverTcpConnector.configure(KissOverTcpConnector.java:277)
at org.ka2ddo.yaac.gui.BlinkenLight$1.itemStateChanged(BlinkenLight.java:262)
at java.desktop/javax.swing.AbstractButton.fireItemStateChanged(AbstractButton.java:2000)
at java.desktop/javax.swing.AbstractButton$Handler.itemStateChanged(AbstractButton.java:2320)
at java.desktop/javax.swing.DefaultButtonModel.fireItemStateChanged(DefaultButtonModel.java:458)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setSelected(JToggleButton.java:374)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:392)
at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
at java.desktop/java.awt.Component.processMouseEvent(Component.java:6626)
at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3389)
at java.desktop/java.awt.Component.processEvent(Component.java:6391)
at java.desktop/java.awt.Container.processEvent(Container.java:2266)
at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5001)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948)
at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4575)
at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2780)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:775)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:720)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:714)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:747)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:744)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
I had it working once but then fldigi froze up and wouldn't respond. Any ideas?
73,
Eric WG3K
|
Re: Help me understand... RX only I-gate showing on map when filtered to RF only
Vicinity plotting isn't disabled on a per-station basis after-the-fact. It is part of the before-the-fact overall configuration of your YAAC station (and is a saved part of the configuration so you don't have to do it again every
time you start YAAC).
If your operational mode is to not view stations without positions on the map, then turn off vicinity plotting before you start collecting data.
Vicinity plotting is enabled by default because it was recommended by Bob Bruninga WB4APR himself.
Note that, if you turn off vicinity plotting, positionless stations will still appear on the map. Their location will be latitude zero, longitude zero, also known as the Coast of Africa point, in the Atlantic Ocean far off the
shore of Nigeria. Even if you have vicinity plotting on, some stations may end up at the Coast of Africa because they don't have any associated station to use for vicinity plotting guesses.
The button on the map toolbar with the bolded 0 icon will pan the map to the Coast of Africa point. You can use the home button on the map to jump back to your station's position.
Note that, just because you choose not to view positionless stations doesn't stop those stations from sending packets without positions.
Andrew, KA2DDO
author of YAAC
Sent: Wednesday, December 13, 2023 2:29:49 PM
Andrew,?
I would rather they not show unless a position was received. Having to tick something in configuration after the fact is a step or two I don't feel the used needs to have to do.
Chris
--------------------
From: "Andrew P." <andrewemt@...>
Sent: Wed, Dec 13 2023 01:18 PM
Actually, the digipeater symbol with a red question mark on it has a different meaning. This indicates a "stealth" digipeater (or I-gate) which has not (as far as YAAC is concerned) sent a position report with the digipeater's own position and symbol
code, so YAAC is guessing the digipeater's location based on the reported positions of all the stations who were reported as using that digi or I-gate as the first relay station.
?
This explains why the I-gate is in the wrong place (YAAC hasn't been told where it is yet) and the non-standard symbol.
?
You can take those off the map by disabling the stealth digi symbol on the filter dialog's Symbol tab.
?
You can also disable guesstimating station locations (called "vicinity plotting") entirely by opening the expert-mode Configuration dialog and unchecking vicinity plotting on the Behavior tab.
?
Note that vicinity plotting also applies to real stations who have sent only APRS packets other than position reports, so we know the station exists but we don't know where. In that case, if we have a good location for the first digipeater or I-gate
that heard it, we will guess the station location as near that I-gate or digi.
?
Vicinity plotting locations are always replaced with real locations once YAAC hears a real location for the station.
?
Hope this helps.
?
Andrew, KA2DDO
author of YAAC
|
Re: Help me understand... RX only I-gate showing on map when filtered to RF only
Andrew,?
I would rather they not show unless a position was received. Having to tick something in configuration after the fact is a step or two I don't feel the used needs to have to do.
Chris -------------------- From: "Andrew P." <andrewemt@...> Reply-To: < [email protected]> To: < [email protected]> Sent: Wed, Dec 13 2023 01:18 PM Subject: Re: [yaac-users] Help me understand... RX only I-gate showing on map when filtered to RF only Actually, the digipeater symbol with a red question mark on it has a different meaning. This indicates a "stealth" digipeater (or I-gate) which has not (as far as YAAC is concerned) sent a position report with the digipeater's own position and symbol code, so YAAC is guessing the digipeater's location based on the reported positions of all the stations who were reported as using that digi or I-gate as the first relay station.
?
This explains why the I-gate is in the wrong place (YAAC hasn't been told where it is yet) and the non-standard symbol.
?
You can take those off the map by disabling the stealth digi symbol on the filter dialog's Symbol tab.
?
You can also disable guesstimating station locations (called "vicinity plotting") entirely by opening the expert-mode Configuration dialog and unchecking vicinity plotting on the Behavior tab.
?
Note that vicinity plotting also applies to real stations who have sent only APRS packets other than position reports, so we know the station exists but we don't know where. In that case, if we have a good location for the first digipeater or I-gate that heard it, we will guess the station location as near that I-gate or digi.
?
Vicinity plotting locations are always replaced with real locations once YAAC hears a real location for the station.
?
Hope this helps.
?
Andrew, KA2DDO
author of YAAC
I treat question marks in the star icon usually as a corrupted report. When I see them they usually are not where they are supposed to be and I delete the station manually. I see them all the time. I don't pay attention to how they report(via rf or tcip) as I recognize the call signs and know they aren't in their correct location.
Chris -------------------- From: "Mike W7MVG" <mike@...> Reply-To: < [email protected]> To: < [email protected]> Sent: Wed, Dec 13 2023 12:33 PM Subject: [yaac-users] Help me understand... RX only I-gate showing on map when filtered to RF only Can someone please help me understand what I'm seeing here? I have my filter set to only show stations from KISS-over-TCP. I see no incoming packets in the raw packet sniffer, yet N7LF-10 has shown up on my map. When I go look at N7LF-10 on aprs.fi it says it's an RX only I-gate and shows it's location about 60 miles east of me. But in YAAC, it's showing up about 20 miles south of me. So, my question is, without any packets showing up in the packet sniffer, and with the filter set to RF only, how did this station show up? And why is it's location so far off from aprs.fi? Bad decode? Thanks. Just trying to figure this all out. ![]() ?
|
Re: Help me understand... RX only I-gate showing on map when filtered to RF only
Actually, the digipeater symbol with a red question mark on it has a different meaning. This indicates a "stealth" digipeater (or I-gate) which has not (as far as YAAC is concerned) sent a position report with the digipeater's
own position and symbol code, so YAAC is guessing the digipeater's location based on the reported positions of all the stations who were reported as using that digi or I-gate as the first relay station.
This explains why the I-gate is in the wrong place (YAAC hasn't been told where it is yet) and the non-standard symbol.
You can take those off the map by disabling the stealth digi symbol on the filter dialog's Symbol tab.
You can also disable guesstimating station locations (called "vicinity plotting") entirely by opening the expert-mode Configuration dialog and unchecking vicinity plotting on the Behavior tab.
Note that vicinity plotting also applies to real stations who have sent only APRS packets other than position reports, so we know the station exists but we don't know where. In that case, if we have a good location for the first
digipeater or I-gate that heard it, we will guess the station location as near that I-gate or digi.
Vicinity plotting locations are always replaced with real locations once YAAC hears a real location for the station.
Hope this helps.
Andrew, KA2DDO
author of YAAC
toggle quoted message
Show quoted text
I treat question marks in the star icon usually as a corrupted report. When I see them they usually are not where they are supposed to be and I delete the station manually. I see them all the time. I don't pay attention to how they report(via rf or tcip)
as I recognize the call signs and know they aren't in their correct location.
Chris
--------------------
From: "Mike W7MVG" <mike@...>
Reply-To: < [email protected]>
To: < [email protected]>
Sent: Wed, Dec 13 2023 12:33 PM
Subject: [yaac-users] Help me understand... RX only I-gate showing on map when filtered to RF only
Can someone please help me understand what I'm seeing here? I have my filter set to only show stations from KISS-over-TCP. I see no incoming packets in the raw packet sniffer, yet N7LF-10 has shown up on my map. When I go look at N7LF-10 on aprs.fi it says
it's an RX only I-gate and shows it's location about 60 miles east of me. But in YAAC, it's showing up about 20 miles south of me.
So, my question is, without any packets showing up in the packet sniffer, and with the filter set to RF only, how did this station show up? And why is it's location so far off from aprs.fi? Bad decode?
Thanks. Just trying to figure this all out.
|
Re: Help me understand... RX only I-gate showing on map when filtered to RF only
I treat question marks in the star icon usually as a corrupted report. When I see them they usually are not where they are supposed to be and I delete the station manually. I see them all the time. I don't pay attention to how they report(via rf or tcip) as I recognize the call signs and know they aren't in their correct location.
Chris -------------------- From: "Mike W7MVG" <mike@...> Reply-To: < [email protected]> To: < [email protected]> Sent: Wed, Dec 13 2023 12:33 PM Subject: [yaac-users] Help me understand... RX only I-gate showing on map when filtered to RF only Can someone please help me understand what I'm seeing here? I have my filter set to only show stations from KISS-over-TCP. I see no incoming packets in the raw packet sniffer, yet N7LF-10 has shown up on my map. When I go look at N7LF-10 on aprs.fi it says it's an RX only I-gate and shows it's location about 60 miles east of me. But in YAAC, it's showing up about 20 miles south of me. So, my question is, without any packets showing up in the packet sniffer, and with the filter set to RF only, how did this station show up? And why is it's location so far off from aprs.fi? Bad decode? Thanks. Just trying to figure this all out. 
|
Help me understand... RX only I-gate showing on map when filtered to RF only
Can someone please help me understand what I'm seeing here? I have my filter set to only show stations from KISS-over-TCP. I see no incoming packets in the raw packet sniffer, yet N7LF-10 has shown up on my map. When I go look at N7LF-10 on aprs.fi it says it's an RX only I-gate and shows it's location about 60 miles east of me. But in YAAC, it's showing up about 20 miles south of me. So, my question is, without any packets showing up in the packet sniffer, and with the filter set to RF only, how did this station show up? And why is it's location so far off from aprs.fi? Bad decode? Thanks. Just trying to figure this all out. 
|
Re: Center map on last station Heard ?
Greetings.
Alas, there is no such functionality in YAAC. Given the cost of re-rendering the background street and/or terrain layers of the map, and how spastic it would make the map look on a high-traffic channel, I never even considered
such an option.
I'm not sure I would want to make this a standard YAAC feature, but I could see making it a plugin for the edge-case users like yourself that would have a need for it.
Andrew, KA2DDO
author of YAAC
Sent: Monday, December 11, 2023 11:32:36 AM
Hi All,
??????? I'm currently testing Yaac with Robust Packet on HF, and it would be most useful to be able to Center automatically to the last station heard.on the RF port.
I've looked in the documents / FAQ and can see there's an option to center on a tracked station, but i cannot see how to zoom to last station heard.
does this option exist or have i missed the instructions on how to achieve this ?
regards Paul? G4HDS
|
Center map on last station Heard ?
Hi All,
??????? I'm currently testing Yaac with Robust Packet on HF, and it would be most useful to be able to Center automatically to the last station heard.on the RF port.
I've looked in the documents / FAQ and can see there's an option to center on a tracked station, but i cannot see how to zoom to last station heard.
does this option exist or have i missed the instructions on how to achieve this ?
regards Paul? G4HDS
|
It looks like all is ok now, doe you agree?
?
Joe
?
?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]>
On Behalf Of Ian Morrison
Sent: December 9, 2023 11:39
To: [email protected]
Subject: Re: [yaac-users] YAAC wont digipeat
?
Thanks Andrew. That was the problem.? Too much data in this old head and sometimes it gets lost.
On your RF port (AGWPE or Serial_TNC), which digipeat aliases did you choose to be used on that port? Digipeating doesn't happen automatically on every RF port; it has to be configured on a port-by-port basis.
For example, you wouldn't want everything coming in from 2 meters with a WIDE2-2 path to be dumped to an HF port at 300 baud.
The Digipeat tab is control across all of YAAC, but you also have to set up digipeating on each RF port individually, to properly handle cross-band digipeating and related services.
Hope this helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Ian Morrison <Ianm3920@...>
Sent: Friday, December 8, 2023 11:28 AM
To: [email protected]
Subject: [yaac-users] YAAC wont digipeat
I must have changed something, but I don't know what.
The following is set under the digipeat tab:
ALIAS ??????WIDE 1-1? checked
????????????WIDE 2-2? checked
SELECTED DIGIPEAT PATHS?WIDE2-2
All else blank.
The systems is working fine tracking my car, reporting weather, sending beacons and status.
Thanks ,
VE3EP?Ian
________________________________
|
Thanks Andrew. That was the problem.? Too much data in this old head and sometimes it gets lost.
73, de Ian
VE3EP
toggle quoted message
Show quoted text
On your RF port (AGWPE or Serial_TNC), which digipeat aliases did you choose to be used on that port? Digipeating doesn't happen automatically on every RF port; it has to be configured on a port-by-port basis. For example,
you wouldn't want everything coming in from 2 meters with a WIDE2-2 path to be dumped to an HF port at 300 baud.
The Digipeat tab is control across all of YAAC, but you also have to set up digipeating on each RF port individually, to properly handle cross-band digipeating and related services.
Hope this helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Ian Morrison <Ianm3920@...>
Sent: Friday, December 8, 2023 11:28 AM
To: [email protected]
Subject: [yaac-users] YAAC wont digipeat
I must have changed something, but I don't know what.
The following is set under the digipeat tab:
ALIAS ??????WIDE 1-1? checked
????????????WIDE 2-2? checked
SELECTED DIGIPEAT PATHS?WIDE2-2
All else blank.
The systems is working fine tracking my car, reporting weather, sending beacons and status.
Thanks ,
VE3EP?Ian
________________________________
|
On your RF port (AGWPE or Serial_TNC), which digipeat aliases did you choose to be used on that port? Digipeating doesn't happen automatically on every RF port; it has to be configured on a port-by-port basis. For example, you wouldn't want everything coming in from 2 meters with a WIDE2-2 path to be dumped to an HF port at 300 baud. The Digipeat tab is control across all of YAAC, but you also have to set up digipeating on each RF port individually, to properly handle cross-band digipeating and related services. Hope this helps. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Ian Morrison <Ianm3920@...> Sent: Friday, December 8, 2023 11:28 AM To: [email protected]Subject: [yaac-users] YAAC wont digipeat I must have changed something, but I don't know what. The following is set under the digipeat tab: ALIAS ??????WIDE 1-1 checked ????????????WIDE 2-2 checked SELECTED DIGIPEAT PATHS?WIDE2-2 All else blank. The systems is working fine tracking my car, reporting weather, sending beacons and status. Thanks , VE3EP?Ian ________________________________ From: [email protected] < [email protected]> on behalf of Rusty Travis <rusytravis19@...> Sent: December 5, 2023 2:31 PM To: [email protected] < [email protected]> Subject: Re: [yaac-users] YAAC won't run on RPi Error messages can sometimes be rather arcane, but they are always indicative of the problem. On 12/4/23 21:20, Michael WA7SKG wrote: ... My apologies if you found this somehow distressing and ask forgiveness that this old man with rapidly slipping memory has not achieved your apparent higher level of enlightenment.
|
Re: E: Unable to locate package openjdk-8-jre
I googled it and found I could easily install JRE with
$ sudo apt update
$ sudo apt install default-jdk
I checked that all was OK with
$ java --version
-- -- Bill AA6BD
|
I must have changed something, but I don't know what.
The following is set under the digipeat tab:
ALIAS ??????WIDE 1-1? checked
????????????WIDE 2-2? checked
SELECTED DIGIPEAT PATHS?WIDE2-2
All else blank.
The systems is working fine tracking my car, reporting weather, sending beacons and status.
Thanks ,
VE3EP?Ian
toggle quoted message
Show quoted text
Error messages can sometimes be rather arcane, but they are always indicative of the problem.
On 12/4/23 21:20, Michael WA7SKG wrote:
...
My apologies if you found this somehow distressing and ask forgiveness that this old man with rapidly slipping memory has not achieved your apparent higher level of enlightenment.
|
Re: YAAC won't run on RPi
And you notice both of you said "Raspberry Pi 3B+", not "Pi 1A" or "Pi Zero". That was an annoying "feature" that the Raspberry Pi Foundation (or whoever manages the Raspbian distro) built the newer Java runtimes to only work on the larger CPU architectures and didn't tell anybody they were going to make that limitation. I wonder how many other packages in the Raspbian distro have that "feature". Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Jerry Rector - K4OAM <kb4oam@...> Sent: Tuesday, December 5, 2023 4:14 PM To: [email protected]Subject: Re: [yaac-users] YAAC won't run on RPi Compiled perfectly here also on Raspberry Pi 3B+ running Bookworm 64: uname -m aarch64 Jerry On Tue, Dec 5, 2023 at 5:40?PM Rusty Travis <rusytravis19@...<mailto:rusytravis19@...>> wrote: On 12/5/23 06:50, Dave_G0WBX via groups.io<> wrote: Michael. Your experience and findings are indeed valuable. I suspect many will, if not have already, hit that issue, and many will just give up. I for one appreciate you documenting your struggle. Works fine on an RPi 3B+ with Debian 12 here: $ uname -m armv7l $ wget --2023-12-05 12:26:31-- Resolving www.ka2ddo.org<> (www.ka2ddo.org<>)... 71.162.157.26 Connecting to www.ka2ddo.org<> (www.ka2ddo.org<>)|71.162.157.26|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 22957539 (22M) [application/zip] Saving to: ‘YAAC.zip’ YAAC.zip 100%[=============================================>] 21.89M 1.31MB/s in 16s 2023-12-05 12:26:48 (1.37 MB/s) - ‘YAAC.zip’ saved [22957539/22957539] $ mkdir YAAC && cd YAAC && unzip ../YAAC.zip ... inflating: YAAC.jar inflating: YAACMain.jar inflating: upgrade.jar inflating: cleaner.jar $ which java /usr/bin/java $ java --version openjdk 11.0.18 2023-01-17 OpenJDK Runtime Environment (build 11.0.18+10-post-Raspbian-1deb11u1) OpenJDK Server VM (build 11.0.18+10-post-Raspbian-1deb11u1, mixed mode) $ java -jar YAAC.jar Tue Dec 05 12:34:31 PST 2023: YAACBootstrap starting... os.name<>=Linux os.version=6.1.21-v7+ os.arch=arm locale=en_GB java.version=11.0.18 java.class.version=55.0 JVM: Raspbian OpenJDK Server VM 11.0.18+10-post-Raspbian-1deb11u1 java.class.path=YAAC.jar Tue Dec 05 12:34:32 PST 2023: YAACBootstrap finding installation directory.... JSSC found at /usr/share/java/jssc-2.8.0.jar Tue Dec 05 12:34:32 PST 2023: starting YAAC.... ...
|
Re: YAAC won't run on RPi
Compiled perfectly here also on Raspberry Pi 3B+ running Bookworm 64:
uname -m aarch64
Jerry
On 12/5/23 06:50, Dave_G0WBX via wrote:
Michael.
Your experience and findings are indeed valuable.? I suspect many
will, if not have already, hit that issue, and many will just give
up.
I for one appreciate you documenting your struggle.
Works fine on an RPi 3B+ with Debian 12 here:
$ uname -m
armv7l
$ wget
--2023-12-05 12:26:31--?
Resolving ()... 71.162.157.26
Connecting to ()|71.162.157.26|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 22957539 (22M) [application/zip]
Saving to: ‘YAAC.zip’
YAAC.zip????????????????????
100%[=============================================>]? 21.89M?
1.31MB/s??? in 16s??? ?
2023-12-05 12:26:48 (1.37 MB/s) - ‘YAAC.zip’ saved
[22957539/22957539]
$ mkdir YAAC && cd YAAC && unzip ../YAAC.zip
...
? inflating: YAAC.jar?????????????? ?
? inflating: YAACMain.jar?????????? ?
? inflating: upgrade.jar??????????? ?
? inflating: cleaner.jar??????????? ?
$ which java
/usr/bin/java
$ java --version
openjdk 11.0.18 2023-01-17
OpenJDK Runtime Environment (build
11.0.18+10-post-Raspbian-1deb11u1)
OpenJDK Server VM (build 11.0.18+10-post-Raspbian-1deb11u1, mixed
mode)
$ java -jar YAAC.jar
Tue Dec 05 12:34:31 PST 2023: YAACBootstrap starting...
=Linux
os.version=6.1.21-v7+
os.arch=arm
locale=en_GB
java.version=11.0.18
java.class.version=55.0
JVM: Raspbian OpenJDK Server VM 11.0.18+10-post-Raspbian-1deb11u1
java.class.path=YAAC.jar
Tue Dec 05 12:34:32 PST 2023: YAACBootstrap finding installation
directory....
JSSC found at /usr/share/java/jssc-2.8.0.jar
Tue Dec 05 12:34:32 PST 2023: starting YAAC....
...
|
Re: YAAC won't run on RPi
On 12/5/23 06:50, Dave_G0WBX via groups.io wrote:
Michael.
Your experience and findings are indeed valuable.? I suspect many
will, if not have already, hit that issue, and many will just give
up.
I for one appreciate you documenting your struggle.
Works fine on an RPi 3B+ with Debian 12 here:
$ uname -m
armv7l
$ wget
--2023-12-05 12:26:31--?
Resolving ()... 71.162.157.26
Connecting to ()|71.162.157.26|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 22957539 (22M) [application/zip]
Saving to: ‘YAAC.zip’
YAAC.zip????????????????????
100%[=============================================>]? 21.89M?
1.31MB/s??? in 16s??? ?
2023-12-05 12:26:48 (1.37 MB/s) - ‘YAAC.zip’ saved
[22957539/22957539]
$ mkdir YAAC && cd YAAC && unzip ../YAAC.zip
...
? inflating: YAAC.jar?????????????? ?
? inflating: YAACMain.jar?????????? ?
? inflating: upgrade.jar??????????? ?
? inflating: cleaner.jar??????????? ?
$ which java
/usr/bin/java
$ java --version
openjdk 11.0.18 2023-01-17
OpenJDK Runtime Environment (build
11.0.18+10-post-Raspbian-1deb11u1)
OpenJDK Server VM (build 11.0.18+10-post-Raspbian-1deb11u1, mixed
mode)
$ java -jar YAAC.jar
Tue Dec 05 12:34:31 PST 2023: YAACBootstrap starting...
os.name=Linux
os.version=6.1.21-v7+
os.arch=arm
locale=en_GB
java.version=11.0.18
java.class.version=55.0
JVM: Raspbian OpenJDK Server VM 11.0.18+10-post-Raspbian-1deb11u1
java.class.path=YAAC.jar
Tue Dec 05 12:34:32 PST 2023: YAACBootstrap finding installation
directory....
JSSC found at /usr/share/java/jssc-2.8.0.jar
Tue Dec 05 12:34:32 PST 2023: starting YAAC....
...
|
Re: YAAC won't run on RPi
Error messages can sometimes be rather arcane, but they are always
indicative of the problem.
On 12/4/23 21:20, Michael WA7SKG wrote:
toggle quoted message
Show quoted text
...
My apologies if you found this somehow distressing and ask
forgiveness that this old man with rapidly slipping memory has not
achieved your apparent higher level of enlightenment.
|
Re: YAAC won't run on RPi
Michael.
Your experience and findings are indeed valuable.? I suspect many will, if not have already, hit that issue, and many will just give up.
I for one appreciate you documenting your struggle.
73.
Dave G8KBV.
--
Sent from a MicroSoft free zone:
|
Re: YAAC won't run on RPi
I was setting this up on an existing RPi system. At the time, when I started, I was unaware of specifically which model of RPi I was using. It was in a case that was difficult, and, at the time, deemed unnecessary to disassemble. I wanted to add APRS capability to this particular device. Honestly, I was unaware there were different processors. It was an educational experience. As I proceeded, I learned of the ARM6/ARM7 issue (full disclosure, I honestly did not initially understand what ARM7 meant), I learned of the Openjdk8 vs Openjdk11 issues. I discovered a version on Openjdk11 that would run on an ARM6 processor.
For some, apparently misguided, reason, I believed sharing my experience might be found useful or at least interesting to some users of this forum. It was a journey that, eventually resulted in arriving at the goal.
My apologies if you found this somehow distressing and ask forgiveness that this old man with rapidly slipping memory has not achieved your apparent higher level of enlightenment.
I guess this is not the correct venue for sharing experiences.
Michael WA7SKG
Rusty Travis wrote on 12/4/23 7:55 PM:
toggle quoted message
Show quoted text
So why do you expect results on armv6l,when it "clearly" states that armv7l is required? I'll agree that the case insensitivity may cause confusion.
On 12/4/23 17:34, Michael WA7SKG wrote:
As mentioned in the original post.
pi:~ $ uname -m
armv6l
Michael
Rusty Travis wrote on 12/4/23 4:35 PM:
On 12/4/23 16:27, Michael WA7SKG wrote:
michael@trailer-pi:~/YAAC $ java -jar YAAC.jar
Error occurred during initialization of VM
Server VM is only supported on *_ARMv7+_* VFP
I must have goofed somewhere, not sure where. What does "uname -m" return, compared to what's *_boldened_* above?
|
Re: YAAC won't run on RPi
So why do you expect results on armv6l,when it "clearly" states that
armv7l is required? I'll agree that the case insensitivity may cause
confusion.
On 12/4/23 17:34, Michael WA7SKG wrote:
toggle quoted message
Show quoted text
As
mentioned in the original post.
pi:~ $ uname -m
armv6l
Michael
Rusty Travis wrote on 12/4/23 4:35 PM:
On 12/4/23 16:27, Michael WA7SKG wrote:
michael@trailer-pi:~/YAAC $ java -jar
YAAC.jar
Error occurred during initialization of VM
Server VM is only supported on *_ARMv7+_* VFP
I must have goofed somewhere, not sure where.
What does "uname -m" return, compared to what's *_boldened_*
above?
_._,_._,_
|
Michael WA7SKG