APRSDroid only receiving packet when stop tracking pushed.

[itsBryantP]

Hi, I have APRSDroid connected via usb to my Yaesu FTM-400XDR. I'm attempting to just use the output from the FTM-400 and have APRSDroid display the waypoints. The issue is I'm not seeing any packets received while tracking. Once I push stop tracking, I'll receive a single packet. I've tried various settings without any luck.

COM Output: Tried both packet and waypoint 9600 bps NMEA9 Position transmission manual without periodic posting

I tried another different APRS app and it is receiving packets correctly. I tried a few different APKs including the latest. The packet that I did receive was parsed correctly, suggesting that the fix for issue #141 was present.

[ge0rg]

Can you log the data that you receive with a normal USB serial terminal app? It would help to see what exactly is arriving.

In APRSdroid's "Kenwood" mode, it should be able to parse NMEA waypoints as well as the FTM-400 custom APRS log output, so in theory it should be fine.

[N6ZZY]

I had the same issue using my FTM-350 in "Kenwood" mode. I was using a USB to serial adapter when I had the issue. I found that using a bluetooth to serial adapter with the same radio settings worked. I was using the "2016-12-02 15:16" build at the time. I concluded it was something in the USB code dealing with handshaking. I have not had time to try the latest build.

[ge0rg]

Thanks for the additional info. That indeed looks like a problem in the USB path then. As I don't have an FTM400, it is a bit harder to reconstruct the problem here. It might also be related to CR-LF line endings not matching up.

[matobler]

I can confirm this issue with the 2017-05-23 version and a Yaesu FT1XD connected by USB. Same settings as in the first post. Output: Waypoint (the FT1XD does not do packet). Once I push Stop Tracking I receive the last waypoint and it gets parsed correctly (shows on map). Here an example of the output captured in a terminal. Same setup works fine in W2APRS and I can see the data in a serial terminal on the tablet. Happy to help debugging this.

$GPWPL,3300.00,N,11700.00,W,KM6KSO*39 $GPWPL,3306.65,N,11703.87,W,AF6UA-9*66 $GPWPL,3308.90,N,11706.41,W,KK6NLW*3F $GPWPL,3300.00,N,11700.00,W,KM6KSO*39

[ge0rg]

Do you have any way to find out what exact line termination characters the FT1XD is emitting?

Internally, I'm using https://docs.oracle.com/javase/7/docs/api/java/io/BufferedReader.html#readLine() to read the individual lines:

A line is considered to be terminated by any one of a line feed ('\n'), a carriage return ('\r'), or a carriage return followed immediately by a linefeed.

Maybe the Yaesu is using something awkward like \n\n, causing APRSdroid to ignore the lines?

However, I have no idea why it comes in after pressing "stop tracking". Maybe it really is a bug in the specific USB device driver, and you should try a different USB-serial dongle instead.

[matobler]

I will try to log some data directly to a text file and post it here. I doubt that the issue is related to the USB device driver as it works fine in W2APRS and I can see all the messages in the terminal window. The USB dongle is the original one from Yaesu. They have a proprietary connector so it's not that easy to switch the dongle.

[bg1dx]

The same data cable, the same phone W2APRS app is ok, I monitor aprsdriod log， Can be received messgae ：$GPWPL,4007.00,N 11625.59,E,BG1DX-9*74 but can not decode I think it is not a data cable problem, it will be a format problem ？ Next week I try to change the data cable to bluetooth

[bg1dx]

@ge0rg i test bluetooth 2.0 and BLE4.0 but aprsdriod still not work. W2APRS and work on bluebooth 2.0

[ADDICTEDchris]

I am trying to get APRS Droid to work with a FTM400DR as well. Has anyone gotten this work? All I am trying to do is set up a IGATE for it and other mobile APRS around me.

[ge0rg]

@ADDICTEDchris have a look at #141 for generic FTM400 support. I-Gate isn't supported yet with any radio.

[jhguth]

I'm having the same issue, I have tried 2 different devices and 2 different cables. W2APRS receives packets but none for APRSDroid. Has anyone found a solution?

[ge0rg]

I've upgraded the USB library in the latest nightly APK - could you please test if this solves your problems?

[ndoolin]

Same or similar Issues on a FTM-350AR Radio Config: Waypoint NMEA 8

Aprsdroid: Kenwood NMEA

RT Systems Cable FTDI Chipset w OTG cable

When I Stop Tracking I get the last recieved APRS message successfully parsed. If I change the Radio to Packet NMEA 9 and AprsDroid to TNC mode I get data as the packets roll in however it appears they in such a way they are not usable. Anyone else have any ideas on this or the magic Config to have this working?

Thanks!

[steve500]

Same issues here. Using the Yaesu supplied USB > Serial 10 pin cable.

Tried all different kinds of NMEA, using Kenwood NMEA mode 9600bps, tried different speeds with same result. APRSdroid only populates the last received packet after stopping the tracking.

I understand that using a bluetooth serial adapter is a solution but I like the idea of being hardwired instead. I hope we can get this to work. The radio supports GPS, Packet, and Waypoint serial output modes. Only Packet mode works to populate one received packet.

[ndoolin]

Strange that this is the only change(changing to Bluetooth serial adapter) and everything works as it should. APRSISCE/32 works fine with the same USB Serial Cable and allegedly W2APRS also works without issue although I haven’t tried yet. Seems like a parsing issue with the way Yaesu outputs the data but from looking at one of the other bugs it would seem like they attempted to fix the parsing issue by creating the Kenwood NMEA option but that created the other issue with the stuck waypoint packets. Again, I can see the packets pushing through in Packet Mode NMEA 9 and Aprsdroid configured in the KISS TNC Config, but they get split into 2 lines due to the Yaesu Non-Standard output.

Out of curiosity, what Bluetooth Serial Adapter are folks using to connect these radios up to APRSdroid? I’m assuming the installable Yaesu Bluetooth module is only for Voice for RF and not for serial data output.

[steve500]

https://youtu.be/TerxrVD2FEg

This guy shows his setup working with a Bluetooth serial adapter. Specifically this one https://www.amazon.com/gp/product/B00R2N68Z4

[ndoolin]

Interesting, although the fact you need to power it with USB negates some of the benefits of the wires free idea, but w/o power being sent along the serial bus there aren’t a whole lot of options. The external battery is an interesting idea. But it just feels like a lot of clutter and other things to lose connection or break. The wired connection with an OTG Adapter just seems like the most reliable solution in most cases, but certainly for the video link you provided having less cables to the tablet in the car makes a lot of sense too. Unfortunately, purchasing another ftm-350 din -> serial cable(I have the RT Systems USB Serial) and the Bluetooth adapter starts to add up to quite the investment, just as a (hopefully) temporary workaround. I know it was suggested before by the dev but what may be interesting is comparing to see if there is any difference in the behavior between the 3 different Serial USB chipsets. The USB driver used on the tablet I believe will be the same. Steve, what USB serial cable / Chipset are you using?

[steve500]

I have my FTM400 installed in my car with the serial/usb cable hooked into an Android head unit in the dash. Permanent install with no cables in sight. It looks like Yaesu uses a prolific serial connection of some kind as far as the W2APRS app tells me, which does work perfectly with the FTM400. Though, as well as W2APRS works, I would love to have Aprsdroid work instead with the ability to see entire APRS messages as it doesn't seem like W2APRS does.

https://www.dxengineering.com/parts/ysu-scu-20?seid=dxese1&cm_mmc=pla-google-_-shopping-_-dxese1-_-yaesu&gclid=Cj0KCQjwyoHlBRCNARIsAFjKJ6AdItEDYvhOfVuBCVIiRbksHMESTCUUeCrmP68EhLrP6RbxNJcnsoYaAormEALw_wcB

[steve500]

If there is anything we can do to try and help, let us know. Maybe I could plug my FTM-400 into my computer and record the serial output of received APRS packets?

[tg9aso]

I was unable to make APRSdroid work with the FTM400 packet output. My solution .... I got a cheap and quality 10 pin din connector from console5.com, took the audio from the discriminator and let javAX25lib(AFSK) do the job on aprsdroid side. Works great for me and got rid from the clunky OTG+SCU-20 setup

[ge0rg]

It would be really great to obtain an adb log with timestamps from APRSdroid, something like adb logcat -v threadtime started before you begin the session in APRSdroid and running until you stop tracking, or at least from an app like https://play.google.com/store/apps/details?id=com.pluscubed.matlog (file -> record) - filtered by APRSdroid's PID (or sent via email to georg@aprsdroid.org to not appear in the public tracker).

[jhguth]

This email chain was sent to me spam mail for some reason, so sorry for the long delay.

I'm happy to help troubleshoot if this is still an issue. Do you still need me to log?

On Wed, May 1, 2019 at 3:52 PM Georg Lukas notifications@github.com wrote:

It would be really great to obtain an adb log with timestamps from APRSdroid, something like adb logcat -v threadtime started before you begin the session in APRSdroid and running until you stop tracking, or at least from an app like https://play.google.com/store/apps/details?id=com.pluscubed.matlog (file -> record) - filtered by APRSdroid's PID (or sent via email to georg@aprsdroid.org to not appear in the public tracker).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ge0rg/aprsdroid/issues/167#issuecomment-488395336, or mute the thread https://github.com/notifications/unsubscribe-auth/AKGTJ2C273SRSP25THG66QTPTHYHXANCNFSM4DLUE6JQ .

[t-mcmahon]

Any resolution to this issue? The bluetooth serial / FTM-400 works for me, but I am trying to help some one get set up with an in dash android solution that doesn't want to loose the ability to bluetooth connect to his phone for music and calls so USB is the only viable option with the FTM-400.