OK, I ran your log of the collected messages through, and found several errors in the Yaesu port driver. I have fixes for all of those issues now, so the playback appears to work.

However, I'm wondering about the actual contents of the log. I can tell you didn't get them from the Yaesu debug log feature already in YAAC, but I'm trying to determine if the huge amount of excess whitespace in some of the packets was actually there, or whether that was an artifact from how you captured the data.

Anyway, the fix will be in the next build of YAAC, coming "real soon now".

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of ke7kus@... <ke7kus@...>
Sent: Wednesday, May 13, 2020 9:47 PM
To: [email protected]
Subject: Re: [yaac-users] FTM-400XDR and YaesuConnector

Andrew,

Thanks for your quick response. I've tested build #150 over the past two days and incoming packets from the FTM-400 are still not displaying on the YAAC map or registering as received packets. Here is a sample of the serial string I'm getting out of the data port on the radio:

KF6RAL-12>APRS,JACKPK,CABALL,BENRDG*,WIDE2 [20/13/05 10:29:56] <UI>:
!3201.04N/10919.24W_NWS Tucson Sugarloaf
KF6RAL-12>APRS,JACKPK,CABALL,LRIDGE*,WIDE2 [20/13/05 10:29:58] <UI>:
!3201.04N/10919.24W_NWS Tucson Sugarloaf
KE7KUS>APRX29,BENRDG*,WIDE2-1 [20/13/05 10:30:14] <UI>:
!3255.35NI10549.08W#/W3,NMn/
KE7KUS>APRX29,BENRDG,LRIDGE*,WIDE2 [20/13/05 10:30:16] <UI>:
!3255.35NI10549.08W#/W3,NMn/
AI0OK-9>SQ4WTR,ELPASO,BENRDG*,WIDE2 [20/13/05 10:30:22] <UI R>:
`r:Vl|\>/]"A!}=

None of the above packets (or any others received) processed in YAAC. Running YAAC from the command line with a uBlox GPS puck attached, I got a JSON parsing error for the GPS data, but no other indications. Disconnecting the USB GPS, I ran YAAC from the command line and got the following output:

pi@ke7kus-m:~/Downloads/YAAC $ java -jar YAAC.jar
os.name=Linux
os.version=4.19.97-v7l+
os.arch=arm
java.version=1.8.0_212
java.class.version=52.0
JVM: Oracle Corporation OpenJDK Client VM 25.212-b01
java.class.path=YAAC.jar
raw boot URL: jar:file:/home/pi/Downloads/YAAC/YAAC.jar!/org/ka2ddo/yaac/bootstrap/YAACBootstrap.class
boot URL: file:/home/pi/Downloads/YAAC/YAAC.jar
*** no Linux subdirectory
#1: file:/home/pi/Downloads/YAAC/YAAC.jar
*** already tried this directory
searching /usr/lib/jni
searching /usr/lib/jni/librxtxSerial.so
searching /lib
searching /usr/lib
searching /usr/local/lib
made java.library.path=/usr/lib/jni
Wed May 13 18:11:53 MDT 2020: starting YAAC....
Wed May 13 18:11:53 MDT 2020: YAAC initializing on Linux 4.19.97-v7l+ with Java 1.8.0_212
Wed May 13 18:11:53 MDT 2020: YAAC raising splash screen....
Wed May 13 18:11:54 MDT 2020: load cached preferences....
Wed May 13 18:11:54 MDT 2020: load beacon definitions....
Wed May 13 18:11:54 MDT 2020: load status definition....
Wed May 13 18:11:54 MDT 2020: set up raw packet data model....
Wed May 13 18:11:54 MDT 2020: YAAC finding installation directory....
Wed May 13 18:11:54 MDT 2020: YAAC checking if upgrader needs moving....
Wed May 13 18:11:54 MDT 2020: YAAC loading CoreProvider....
loading plugin --core-- name YAAC version 1.0-beta150(11-May-2020)
Wed May 13 18:11:54 MDT 2020: creating SymAttr objects for 1.0.1...
Wed May 13 18:11:54 MDT 2020: filling in text for 1.0.1 symbols...
Wed May 13 18:11:54 MDT 2020: YAAC loading plugins....
scanning plugin JAR file /home/pi/Downloads/YAAC/plugins/sampleplugin.jar
attempting to load provider class org.ka2ddo.yaac.SamplePluginProvider
loading plugin /home/pi/Downloads/YAAC/plugins/sampleplugin.jar name YAAC Sample Plug-in version V0.0
Wed May 13 18:11:54 MDT 2020: starting web server...
Wed May 13 18:11:54 MDT 2020: YAAC starting main GUI....
Wed May 13 18:11:54 MDT 2020: YAAC removing splash screen....
Wed May 13 18:11:54 MDT 2020: setting up common GUI table models...
Wed May 13 18:11:54 MDT 2020: starting bulletin board monitor...
Wed May 13 18:11:54 MDT 2020: starting firstWindow=map
OpenMap(tm) Version 5.0
Copyright (C) BBNT Solutions LLC. All rights reserved.
See for details.

Wed May 13 18:11:54 MDT 2020: creating top map toolbar...
Wed May 13 18:11:54 MDT 2020: 1589415114980: starting to load symbol images...
1589415115316: finished loading 1.0.1 basic symbol images...
Wed May 13 18:11:55 MDT 2020: 1589415115316: done loading symbols.
Wed May 13 18:11:55 MDT 2020: adding map scale widget...
Wed May 13 18:11:55 MDT 2020: adding blinkenlight panel...
Wed May 13 18:11:55 MDT 2020: creating map footer...
Wed May 13 18:11:55 MDT 2020: setting up map hot-keys...
Wed May 13 18:11:55 MDT 2020: sizing main map window...
Wed May 13 18:11:55 MDT 2020: YAAC: GUI instantiated, now setting up GUI....
Wed May 13 18:11:55 MDT 2020: YAAC starting digipeater....
Wed May 13 18:11:55 MDT 2020: YAAC opening ports....
Wed May 13 18:11:55 MDT 2020: waiting for I/O starter for Port1:GPSD to finish
opening port PortConfig[Port1>GPSD,localhost,2947,]
opening port PortConfig[Port2>Yaesu,/dev/ttyUSB0,9600,KE7KUS-9]
old socket rcvBuf=65536
Wed May 13 18:11:56 MDT 2020: opening socket to GPSD @ localhost/127.0.0.1:2947
updated socket rcvBuf=65536
Wed May 13 18:11:56 MDT 2020: waiting for I/O starter for Port2:Yaesu to finish
Wed May 13 18:11:56 MDT 2020: initializing local station KE7KUS-9
Wed May 13 18:11:56 MDT 2020: YAAC starting beacon and persistent objects....
Wed May 13 18:11:56 MDT 2020: YAAC creating main menu bar....
Wed May 13 18:11:56 MDT 2020: about to create RasterMapOverlay layer...
renderCurrentMap[#2]: ABORT 0(0)/0 ways(0ur), 0/0 nodes, 0 signs, 0 files(1 new,0 missing) in 38msec @ zoom=620125.44 [32.869373,-105.728355]
Wed May 13 18:11:56 MDT 2020: about to create StationRenderer layer...
renderCurrentMap[#2]: ABORT 2(193)/426 ways(0ur), 0/0 nodes, 0 signs, 1 files(1 new,0 missing) in 95msec @ zoom=620125.44 [32.869373,-105.728355]
renderCurrentMap[#2]: ABORT 4(217)/2546 ways(0ur), 0/0 nodes, 0 signs, 1 files(0 new,0 missing) in 20msec @ zoom=620125.44 [32.869373,-105.728355]
Wed May 13 18:11:56 MDT 2020: creating bookmark menu...
Wed May 13 18:11:56 MDT 2020: YAAC startup completed.
renderCurrentMap[#2]: 294(5536)/65699 ways(0ur), 2/18706 nodes, 6 signs, 12 files(12 new,0 missing) in 707msec @ zoom=620125.44 [32.869373,-105.728355]
1589415122840: PortEditor: starting to create editor
1589415122841: PortEditor: starting to create per-driver cards
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists1589415122865: PortEditor: loading editor class for Yaesu
1589415122867: PortEditor: creating card for Yaesu
1589415122930: PortEditor: creating card selector
updateHelpTag() from card org.ka2ddo.yaac.gui.io.YaesuPortEditor[,0,0,0x0,invalid,layout=java.awt.GridBagLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=], help tag=configure.ports.Yaesu
1589415123042: PortEditor: selected appropriate default card Yaesu
1589415123042: PortEditor: created.
updateHelpTag() from card org.ka2ddo.yaac.gui.io.YaesuPortEditor[,0,0,560x91,layout=java.awt.GridBagLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=], help tag=configure.ports.Yaesu
Wed May 13 18:12:10 MDT 2020: opening test port for Yaesu port /dev/ttyUSB0
Wed May 13 18:14:48 MDT 2020: closing test port for Yaesu port /dev/ttyUSB0

When run this way, the program initializes with no problems. Opening the Configure Port dialog for the Yaesu port, everything appears normal. Running the "Test Port" option on the config dialog brings up the small terminal window and the packets are displayed in the format denoted above.

I observed the same response regardless of the incoming packet rate. The rate at which packets were displayed in the YAAC Test Port window was the same as the rate packets were displayed when running minicom pointed at the USB port. The attached screenshot was from a run with build #145, but the runs with build #150 looked the same. The attached text files are the full capture of a string of received packets (not displayed) and the CLI output noted above.

Andrew,

Thanks for your quick response.? I've tested build #150 over the past two days and incoming packets from the FTM-400 are still not displaying on the YAAC map or registering as received packets.? Here is a sample of the serial string I'm getting out of the data port on the radio:

KF6RAL-12>APRS,JACKPK,CABALL,BENRDG*,WIDE2 [20/13/05 10:29:56] <UI>:
!3201.04N/10919.24W_NWS Tucson Sugarloaf
KF6RAL-12>APRS,JACKPK,CABALL,LRIDGE*,WIDE2 [20/13/05 10:29:58] <UI>:
!3201.04N/10919.24W_NWS Tucson Sugarloaf
KE7KUS>APRX29,BENRDG*,WIDE2-1 [20/13/05 10:30:14] <UI>:
!3255.35NI10549.08W#/W3,NMn/
KE7KUS>APRX29,BENRDG,LRIDGE*,WIDE2 [20/13/05 10:30:16] <UI>:
!3255.35NI10549.08W#/W3,NMn/
AI0OK-9>SQ4WTR,ELPASO,BENRDG*,WIDE2 [20/13/05 10:30:22] <UI R>:???????????????
`r:Vl|\>/]"A!}=

None of the above packets (or any others received) processed in YAAC.? Running YAAC from the command line with a uBlox GPS puck attached, I got a JSON parsing error for the GPS data, but no other indications.? Disconnecting the USB GPS, I ran YAAC from the command line and got the following output:

pi@ke7kus-m:~/Downloads/YAAC $ java -jar YAAC.jar
os.name=Linux
os.version=4.19.97-v7l+
os.arch=arm
java.version=1.8.0_212
java.class.version=52.0
JVM: Oracle Corporation OpenJDK Client VM 25.212-b01
java.class.path=YAAC.jar
raw boot URL: jar:file:/home/pi/Downloads/YAAC/YAAC.jar!/org/ka2ddo/yaac/bootstrap/YAACBootstrap.class
boot URL: file:/home/pi/Downloads/YAAC/YAAC.jar
*** no Linux subdirectory
#1: file:/home/pi/Downloads/YAAC/YAAC.jar
*** already tried this directory
?? searching /usr/lib/jni
?? searching /usr/lib/jni/librxtxSerial.so
?? searching /lib
?? searching /usr/lib
?? searching /usr/local/lib
made java.library.path=/usr/lib/jni
Wed May 13 18:11:53 MDT 2020: starting YAAC....
Wed May 13 18:11:53 MDT 2020: YAAC initializing on Linux 4.19.97-v7l+ with Java 1.8.0_212
Wed May 13 18:11:53 MDT 2020: YAAC raising splash screen....
Wed May 13 18:11:54 MDT 2020: load cached preferences....
Wed May 13 18:11:54 MDT 2020: load beacon definitions....
Wed May 13 18:11:54 MDT 2020: load status definition....
Wed May 13 18:11:54 MDT 2020: set up raw packet data model....
Wed May 13 18:11:54 MDT 2020: YAAC finding installation directory....
Wed May 13 18:11:54 MDT 2020: YAAC checking if upgrader needs moving....
Wed May 13 18:11:54 MDT 2020: YAAC loading CoreProvider....
loading plugin --core-- name YAAC version 1.0-beta150(11-May-2020)
Wed May 13 18:11:54 MDT 2020: creating SymAttr objects for 1.0.1...
Wed May 13 18:11:54 MDT 2020: filling in text for 1.0.1 symbols...
Wed May 13 18:11:54 MDT 2020: YAAC loading plugins....
scanning plugin JAR file /home/pi/Downloads/YAAC/plugins/sampleplugin.jar
attempting to load provider class org.ka2ddo.yaac.SamplePluginProvider
loading plugin /home/pi/Downloads/YAAC/plugins/sampleplugin.jar name YAAC Sample Plug-in version V0.0
Wed May 13 18:11:54 MDT 2020: starting web server...
Wed May 13 18:11:54 MDT 2020: YAAC starting main GUI....
Wed May 13 18:11:54 MDT 2020: YAAC removing splash screen....
Wed May 13 18:11:54 MDT 2020: setting up common GUI table models...
Wed May 13 18:11:54 MDT 2020: starting bulletin board monitor...
Wed May 13 18:11:54 MDT 2020: starting firstWindow=map
OpenMap(tm) Version 5.0
? Copyright (C) BBNT Solutions LLC.? All rights reserved.
? See http://openmap.bbn.com/ for details.

Wed May 13 18:11:54 MDT 2020: creating top map toolbar...
Wed May 13 18:11:54 MDT 2020: 1589415114980: starting to load symbol images...
1589415115316: finished loading 1.0.1 basic symbol images...
Wed May 13 18:11:55 MDT 2020: 1589415115316: done loading symbols.
Wed May 13 18:11:55 MDT 2020: adding map scale widget...
Wed May 13 18:11:55 MDT 2020: adding blinkenlight panel...
Wed May 13 18:11:55 MDT 2020: creating map footer...
Wed May 13 18:11:55 MDT 2020: setting up map hot-keys...
Wed May 13 18:11:55 MDT 2020: sizing main map window...
Wed May 13 18:11:55 MDT 2020: YAAC: GUI instantiated, now setting up GUI....
Wed May 13 18:11:55 MDT 2020: YAAC starting digipeater....
Wed May 13 18:11:55 MDT 2020: YAAC opening ports....
Wed May 13 18:11:55 MDT 2020: waiting for I/O starter for Port1:GPSD to finish
?? opening port PortConfig[Port1>GPSD,localhost,2947,]
?? opening port PortConfig[Port2>Yaesu,/dev/ttyUSB0,9600,KE7KUS-9]
old socket rcvBuf=65536
Wed May 13 18:11:56 MDT 2020: opening socket to GPSD @ localhost/127.0.0.1:2947
updated socket rcvBuf=65536
Wed May 13 18:11:56 MDT 2020: waiting for I/O starter for Port2:Yaesu to finish
Wed May 13 18:11:56 MDT 2020: initializing local station KE7KUS-9
Wed May 13 18:11:56 MDT 2020: YAAC starting beacon and persistent objects....
Wed May 13 18:11:56 MDT 2020: YAAC creating main menu bar....
Wed May 13 18:11:56 MDT 2020: about to create RasterMapOverlay layer...
renderCurrentMap[#2]: ABORT 0(0)/0 ways(0ur), 0/0 nodes, 0 signs, 0 files(1 new,0 missing) in 38msec @ zoom=620125.44 [32.869373,-105.728355]
Wed May 13 18:11:56 MDT 2020: about to create StationRenderer layer...
renderCurrentMap[#2]: ABORT 2(193)/426 ways(0ur), 0/0 nodes, 0 signs, 1 files(1 new,0 missing) in 95msec @ zoom=620125.44 [32.869373,-105.728355]
renderCurrentMap[#2]: ABORT 4(217)/2546 ways(0ur), 0/0 nodes, 0 signs, 1 files(0 new,0 missing) in 20msec @ zoom=620125.44 [32.869373,-105.728355]
Wed May 13 18:11:56 MDT 2020: creating bookmark menu...
Wed May 13 18:11:56 MDT 2020: YAAC startup completed.
renderCurrentMap[#2]: 294(5536)/65699 ways(0ur), 2/18706 nodes, 6 signs, 12 files(12 new,0 missing) in 707msec @ zoom=620125.44 [32.869373,-105.728355]
1589415122840: PortEditor: starting to create editor
1589415122841: PortEditor: starting to create per-driver cards
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: File exists1589415122865: PortEditor: loading editor class for Yaesu
1589415122867: PortEditor: creating card for Yaesu
1589415122930: PortEditor: creating card selector
updateHelpTag() from card org.ka2ddo.yaac.gui.io.YaesuPortEditor[,0,0,0x0,invalid,layout=java.awt.GridBagLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=], help tag=configure.ports.Yaesu
1589415123042: PortEditor: selected appropriate default card Yaesu
1589415123042: PortEditor: created.
updateHelpTag() from card org.ka2ddo.yaac.gui.io.YaesuPortEditor[,0,0,560x91,layout=java.awt.GridBagLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=], help tag=configure.ports.Yaesu
Wed May 13 18:12:10 MDT 2020: opening test port for Yaesu port /dev/ttyUSB0
Wed May 13 18:14:48 MDT 2020: closing test port for Yaesu port /dev/ttyUSB0

When run this way, the program initializes with no problems.? Opening the Configure Port dialog for the Yaesu port, everything appears normal.? Running the "Test Port" option on the config dialog brings up the small terminal window and the packets are displayed in the format denoted above.

I observed the same response regardless of the incoming packet rate.? The rate at which packets were displayed in the YAAC Test Port window was the same as the rate packets were displayed when running minicom pointed at the USB port.? The attached screenshot was from a run with build #145, but the runs with build #150 looked the same.? The attached text files are the full capture of a string of received packets (not displayed) and the CLI output noted above.

Yes, any software TNC program you want to use has to be running and available before YAAC tries to connect to it. Unlike Internet connections to APRS-IS, YAAC won't keep retrying to find the local software TNC, as said program generally won't fix itself without local human intervention (in which case, the local human can subsequently re-enable the YAAC port to the software TNC process).

I never knew YAAC would fail completely if the graphical desktop UI was too small. It can definitely be unusable (hence why the smallscreen plugin was developed), but it should keep trying to work with a somewhat munged UI.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Patrick KA9PDK <patrick.mcgillan@...>
Sent: Wednesday, May 13, 2020 9:17 AM
To: [email protected]
Subject: Re: [yaac-users] New User

OK, so I am using a remote connection to a raspberry pi. So far no problem. On the other hand, to save screen, I was shrinking down the window to see around it. That was the problem as the program was starting up. So after logging in several times, I made the screen full size and when running the program, everything started working. Now working through the setup screens. Does direwolf need to start before starting YAAC?

OK, so I am using a remote connection to a raspberry pi. So far no problem. On the other hand, to save screen, I was shrinking down the window to see around it. That was the problem as the program was starting up. So after logging in several times, I made the screen full size and when running the program, everything started working. Now working through the setup screens. Does direwolf need to start before starting YAAC?

Did you start YAAC from a command prompt (as opposed to clicking on the YAAC.jar file in a graphical file manager)? If so, then YAAC should print out what it is doing to the terminal window. Capture that output and email it to me or the list, and we'll see what the issue is.

Andrew, KA2DDO
author of YAAC

I followed instructions on the web page and only difference I see is that I have version 11 of java stuff. Whne I run the main program, the last few lines say something about starting, but config screen never comes up. Where do I look.

Patrick - KA9PDK

Now update is correctly working

Thank you

Franco Spinelli
IW2DHW

No, it just means that I forgot to update the build label and release notes files, so the code was up-to-date, but the update logic couldn't tell there was a new build. This is fixed now.

Thank you for reminding me.

Andrew, KA2DDO

I have build #149 on Linux Ubuntu 18.04 64 bit and message in checking update say :

?Your copy of YACC is up-to-date: no new download needed

Is build #150 not available for update?

Regards

Franco Spinelli
IW2DHW

next beta build#150 of YAAC ("Yet Another APRS Client"), created 2020-May-11

downloadable from
or

changes and updates include:
1. add support for Peet Bros weather stations' "complete record" protocol
for sending weather data to computers.
2. add support for manual-only beaconing, on a per-beacon definition basis,
so that a system working cross-band VHF and HF (on a band where automatic
transmissions are prohibited) can beacon automatically on VHF and
comply with regulations on the HF band. Add a more obvious control
(the BCN button) to trigger manual beacon transmissions, with a visual
indication whether it is "reasonable" to force another beacon.
3. fix proportional path editing logic in case user deletes all paths;
this then assumes that the user meant only the direct (no digipeat)
path.
4. make some UI adjustments to prevent sudden widening of lists and
text fields because the widget doesn't have any text entries to
figure the necessary width of the widget.
5. fix NullPointerException when viewing the health monitor for weather
stations that have only sent one packet since YAAC has started.
6. stop drawing street names upside down; name flipping should only occur
for borderlines (such as province or national boundaries) where the
side of the line the name occurs on matters.
7. try to fix parsing for the Yaesu port driver.
8. fix weird case in OpenStreetMap importers where a Relation for a body
of water has only one Way in the shoreline, and no labelling tags
on the Way (only on the Relation). In such cases, the unlabelled
Way is dropped, and the multipolygon element of the Relation gets
dropped because it doesn't merge multiple Ways together.
9. some cleanup of online help documentation.

Hmmm... The existing Yaesu port driver should "almost" work, but not quite. There are two issues:

1. Because of the possibility of some dingbat sending a packet with a line break (carriage return and/or linefeed) embedded in the middle of the text, there is code that won't pass the packet on to the rest of YAAC until the next packet is received (so the first line of the next packet triggers the flush). This would obviously be very annoying when there is low traffic volume, so I'm adding a timer to push the packets through within a "reasonable" time instead of waiting for the next packet to start.

2. There was a problem in parsing the digipeat list of a packet (although that shouldn't have broken the packets without digipeat paths).

In any case, both these issues will be fixed in the next build. When you get build#150, tell me if you still have issues.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of ke7kus@... <ke7kus@...>
Sent: Monday, May 11, 2020 1:01 AM
To: [email protected]
Subject: [yaac-users] FTM-400XDR and YaesuConnector

I've recently attempted to configure YAAC to receive serial output from a Yaesu FTM-400XDR radio. With the FTM-400 set in "PACKET" data output mode, I get serial port output which resembles TNC-2 formatted packets with some extraneous Yaesu-provided injects which corrupt an otherwise standardized packet format. (Thank you Yaesu.) In the YAAC Javadoc, I noted the existence of a YaesuConnector class, and in Build #148 there is a configuration option for a "Yaesu" port where one defines the serial port, baud rate, and station callsign for the port. I configured this port in YAAC, but received packets do not display on the YAAC graphical map as packets come in. When I run the "Test Port" utility in the Port configuration dialog, I get output similar to the following:

W5NGU-3>APRX28 [08/13/16 00:26:22] <UI>:
;W5NGU-VHF*111111z3313.66N/09707.60WrW5NGU 146.920 pl 110.9 -0.6
W5NGU-3>APRX28 [08/13/16 00:26:23] <UI>:
;W5FKN-VHF*111111z3307.84N/09706.00WrW5NGU 145.17 pl 110.9 +5MHz
W5NGU-3>APRX28 [08/13/16 00:26:25] <UI>:
;WA5LIE/F *111111z3313.75N/09707.64WrWA5LIE/F Fusion 443.525 pl 118.8 +5MHz
N0FIB-7>SRTX6T,K5FTW-5*,WIDE2 [08/13/16 00:26:35] <UI R>:
`}5Wlp [/`"60}_$

Here it is easy to see the "customized" Yaesu serial string format which has been implemented instead of a standard TNC-2 formatted packet. This also indicates that the serial port is receiving packets from the FTM-400 radio.

In reading the YaesuConnector Javadoc, it appears the YaesuConnector class may have been designed to perform some basic string handling and remove the Yaesu injects to return the packets back to TNC-2 format and display them in YAAC; however, I was unable to trace the string handling method for the incoming serial event in the code documentation. I suspect that either the FTM-400 is outputting packets in a format slightly different from what the YaesuConnector was designed to process, or I need to configure the Yaesu radio to output packets in a different format (i.e. using the "GPS" or "WAYPOINT" modes in the FTM-400 data configuration menus.)

Has anyone had success with getting FTM-400XDR packets to import into YAAC and display on the map? If so, can you please post your FTM-400 and YAAC settings? If not, if someone could point me to the code section which executes serial string handling, I'll be happy to write some code to attempt to fix the incoming packets to make them usable for YAAC display.

73,
Kurt
KE7KUS

I've recently attempted to configure YAAC to receive serial output from a Yaesu FTM-400XDR radio.? With the FTM-400 set in "PACKET" data output mode, I get serial port output which resembles TNC-2 formatted packets with some extraneous Yaesu-provided injects which corrupt an otherwise standardized packet format.? (Thank you Yaesu.)? In the YAAC Javadoc, I noted the existence of a YaesuConnector class, and in Build #148 there is a configuration option for a "Yaesu" port where one defines the serial port, baud rate, and station callsign for the port.? I configured this port in YAAC, but received packets do not display on the YAAC graphical map as packets come in.? When I run the "Test Port" utility in the Port configuration dialog, I get output similar to the following:

W5NGU-3>APRX28 [08/13/16 00:26:22] <UI>:
;W5NGU-VHF*111111z3313.66N/09707.60WrW5NGU 146.920 pl 110.9 -0.6
W5NGU-3>APRX28 [08/13/16 00:26:23] <UI>:
;W5FKN-VHF*111111z3307.84N/09706.00WrW5NGU 145.17 pl 110.9 +5MHz
W5NGU-3>APRX28 [08/13/16 00:26:25] <UI>:
;WA5LIE/F *111111z3313.75N/09707.64WrWA5LIE/F Fusion 443.525 pl 118.8 +5MHz
N0FIB-7>SRTX6T,K5FTW-5*,WIDE2 [08/13/16 00:26:35] <UI R>:
`}5Wlp [/`"60}_$

Here it is easy to see the "customized" Yaesu serial string format which has been implemented instead of a standard TNC-2 formatted packet.? This also indicates that the serial port is receiving packets from the FTM-400 radio.

In reading the YaesuConnector Javadoc, it appears the YaesuConnector class may have been designed to perform some basic string handling and remove the Yaesu injects to return the packets back to TNC-2 format and display them in YAAC; however, I was unable to trace the string handling method for the incoming serial event in the code documentation.? I suspect that either the FTM-400 is outputting packets in a format slightly different from what the YaesuConnector was designed to process, or I need to configure the Yaesu radio to output packets in a different format (i.e. using the "GPS" or "WAYPOINT" modes in the FTM-400 data configuration menus.)

Has anyone had success with getting FTM-400XDR packets to import into YAAC and display on the map?? If so, can you please post your FTM-400 and YAAC settings?? If not, if someone could point me to the code section which executes serial string handling, I'll be happy to write some code to attempt to fix the incoming packets to make them usable for YAAC display.

73,
Kurt
KE7KUS

Hi Andrew

Thanks for recognizing my ability as a? bug crasher!!!? I did not know I had such ability.? Glad that my lake has now received honourable mention in the annals of YAAC.? Yay for the small guys!? I look forward to the next build.

Joe VA3JLF

开云体育

It may take a while before I add tweeting support. I need to find out if there is a freely licensed or public domain means of automatically sending tweets.

Hi, Joe.

Ouch! You found a _very_ obscure bug in the OSM importer. Due to the peculiar methodology used to enter East Lake into OpenStreetMap, as one unlabeled way for the shoreline and one unlabeled way for the small island within the lake, plus a relation with the labelling tying the two ways together, YAAC made the false assumption that everything needed for the outer shoreline was in the original way. This was not the case; all the details (name, type of area, etc.) were on the relation. But YAAC discarded the relation with all the details as being a point-for-point duplicate of the unlabeled way, and YAAC doesn't render ways without labelling information.

This will be fixed in the next build, but I'll have to wait for the next weekly OSM snapshot to be available before I start the all-day import of the planet again. No point in doing it on the current snapshot that will be outdated in a few days.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Joseph LaFerla <joe@...>
Sent: Sunday, May 10, 2020 4:51 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#149 of YAAC, created 2020-May-09

Hi Andrew

Thanks for the new build. The rendering of the mapping in my area around Lake Ontario and Prince Edward County more generally is perfect, as far as I can tell. The shoreline rendering is so good now that small creeks and rivers can easily be discerned even at higher levels of zoom. However, the small (relative to Lake Ontario) lake in front of my house called East Lake is still missing. While the shoreline is there, the area of the map where the lake is is not coloured blue but is still white. The coordinates of the lake are 43.9189 N and 77.2003 W. For reference, there are two weather stations, (mine VA3JLF-1 and VE3EP-1 Ian) on the south east shore of what should be the lake.

Please let me know if I can provide you with any further information to enable you to locate the lake. As I mentioned to you earlier, the lake is found on the OpenStreetMap original mapping.

Thanks again for your efforts. From what you have said before, this map rendering is not for the faint of heart!
Your support of your software is also very much appreciated.

Joe VA3JLF

Hi Andrew

Thanks for the new build.? The rendering of the mapping in my area around Lake Ontario and Prince Edward County more generally is perfect, as far as I can tell.? The shoreline rendering is so good now that small creeks and rivers can easily be discerned even at higher levels of zoom.? However, the small (relative to Lake Ontario) lake in front of my house called East Lake is still missing. While the shoreline is there, the area of the map where the lake is is not coloured blue but is still white. ? The coordinates of the lake are 43.9189 N and 77.2003 W.? For reference, there are two weather stations, (mine VA3JLF-1 and VE3EP-1 Ian) on the south east shore of what should be the lake.

Please let me know if I can provide you with any further information to enable you to locate the lake.? As I mentioned to you earlier, the lake is found on the OpenStreetMap original mapping.?

Thanks again for your efforts.? From what you have said before, this map rendering is not for the faint of heart!
? Your support of your software is also very much appreciated.?

Joe VA3JLF

This is good news. Thanks!

I'll set up a test station this week to check out 13 and 14.

I'm excited about 25, and especially for parsing remote data. If the next version could send tweets it would be perfect, as weather reporters in our state use Twitter.

next beta build#149 of YAAC ("Yet Another APRS Client"), created 2020-May-09

downloadable from
or

changes and updates include:
1. yet more improvements and bugfixes in OpenStreetMap importer, including
support for coastline shapefiles and actually fixing tiling of large
bodies of water, and adjusting default assumptions for incomplete OSM
records to account for cases where the assumptions didn't apply (such
as assuming a riverbank is a closed area of a section of the river
[both banks] rather than potentially only one shoreline).
2. fix errors in the Maven pom.xml files provided for an alternate means
of building YAAC. Note that the Ant build.xml files are still the
supported means of building YAAC and its plugins.
3. clean up Javadocs and fill in more missing Javadocs.
4. eliminate incorrect identification of TCPXX as a digipeater alias.
5. more minor performance enhancements.
6. add ability to parse time intervals (Ages) as well as display them.
7. fix up display of the YAAC Help->About dialog, ensuring that it
can't grow excessively large from installing many plugins and increasing
the font size.
8. allow quad-sized icons so if all icons are displayed in double-size
then more significant stations/objects can still be displayed in
a larger size on the map.
9. fix displaying weather stations as old-style weather map symbols
so that the temperature and dew point are in the configured
temperature units instead of fixed at Fahrenheit.
10. fix beacon configuration to ensure any modified beacon record has
the chance to be saved when switching to another beacon record,
and ensure the controls for setting beacon-specific rates are
properly set to the last values for that beacon instance instead
of always to the APRS defaults. Also add sanity check to beacon
free-text comment in case user puts the word EMERGENCY in the
text, just to validate that they really want to announce a real
emergency to listening stations.
11. fix configuration wizard to propagate callsign-SSID changes to
existing ports rather than only to any new ones (which might not
be created when the callsign is changed).
12. add to list of standard APRS-IS backbone rotator domain names, the
CWOP rotator (which contains traffic from non-amateur-radio
Citizen's Weather Observation Program stations)
13. for the WxNow.TXT port driver, supplement support for the 2-line
Cumulus file format with chooseable support for the 1-line
Weathercat (TNC2 command-mode frame) format, and allow freely
typing the model code of the weather sensor as an alternative
to the canned list of model codes.
14. add transmit slowdown to radio ports to try to ensure TNC has time
to get the last packet out before pushing a new packet into the
TNC, as some TNCs don't have the buffer space for more packets
from the computer when the last one hasn't finished going to the
radio yet. Was already there for Serial_TNC port type, added for
other TNC port types.
15. update the list of referred websites for obtaining OpenStreetMap
dataset downloads.
16. restructure the email composition method in the Telemetry Alarm
plugin so it can be accessible from other plugins.
17. properly handle weather data in APRS packets when the field is
provided but filled with "..." to indicate the sending station
does not actually have that data parameter.
18. reduce JVM heap thrashing by replacing calls to
StringBuilder.append(s.substring(start,end)) with
StringBuilder.append(s, start, end).
19. add more support in core YAAC for inter-plugin data sharing.
20. eliminate spurious re-render of the OpenStreetMap layer just
because a new station was heard.
21. refactor MADIS weather data quality check so it can be used
elsewhere than just in the Health Monitor view, including in
the new Weather Alert plugin (more about this later).
22. fix issue reported on APRSSIG mailing list 8 May 2020 about
I-gating packets with embedded carriage return and line feed
characters.
23. (provided by James Palmer AG5VQ) fix bugs in the CallsignDB
plugin to support multiple licenses/callsigns per individual
licensee.
24. fix duplicate speaking of the degree portion of a longitude
in the sounds plugin.
25. add new Weather Alert plugin, which reports when certain conditions
are detected in local or remote weather data, by verbal speech,
email, SMS, highlighting the station on the map, and sending
APRS text messages.

I sent my initial message twice because the first time I did not see any
indication that it had been sent.
The second time, I noticed the header about moderator approval.