开云体育

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

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

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.

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,

The test packet file I attached was captured via:

cat /dev/ttyUSB0 > capturefile.txt

In looking at the real-time output, the only "extra" white-space I noted was that Mic-E packets seem to have two newlines after a packet.? Some weather station packets also had an additional newline, so I suspect that may be a source radio/software/client-unique addition...some have it...some don't.? It did seem consistent across stations (i.e. if a station has the extra newline, it always has the extra newline) so I don't think it's from the Yaesu firmware.? Additional white-space may have come from my transferring the file via copy/paste to get a reasonably sized excerpt.

Last night I opened up the source code on YaesuConnector.java...great work in there.? I haven't done a lot of Java coding...I didn't realize how complex string handling is with Java.? The code for indexing through a received packet is very well thought-out, and I appreciate your copious documentation in the source.? Thanks for putting in the time to chase this down.? Greatly appreciated.? If I can help in any way, please let me know.

Kurt
KE7KUS

Andrew,

Installed and ran Build #151 and Yaesu FTM-400 packets are now coming across FB.? I'll monitor for the next few days and see if anything funny comes up, but I ran it for an hour tonight and everything seems to parse and display correctly.? Thanks very much for the help with this.

73,
Kurt
KE7KUS

Just make sure the clock is set correctly on your Yaesu radio. The Yaesu port driver in YAAC uses the timestamp the radio puts on each packet as the receive time, so if your radio's clock is off, so will your packet times in YAAC.

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

Andrew,

Installed and ran Build #151 and Yaesu FTM-400 packets are now coming across FB. I'll monitor for the next few days and see if anything funny comes up, but I ran it for an hour tonight and everything seems to parse and display correctly. Thanks very much for the help with this.

73,
Kurt
KE7KUS