|
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 |
