Hi,
tried searching the forum and saw someone complaining about this already but without any resolution.
I have a FT-5DE and wanted to have my location forwarded to APRS backbone - no go. No matter what I do and how I try to set it up, there is no indication that anything related to APRS is happening.

I tried simply transmitting in both DN and VW modes.
I tried enabling GM, which chirps position periodically. And while it is heard and acknowledged, nothing gets decoded and forwarded.
I made sure Location sending is enabled on the radio.
I made sure APRS is enabled and working in OS3 (I can send test messages to the net).
I read through the Yaesu manuals (again) in case I am mising something.

Is there a trick to this or is it just broken? I don't have another C4FM radio to make sure it is working unfortunately, I just know it works with analog APRS, but sadly this is one of the reasons I got OS3...

Here is a log, the first two calls are regular DN calls with location reporting enabled. The rest from 20:27:22 is GM chirping.

Let me know if I can help debug it somehow...

Thanks
20:27:01 c4fmcalltracker: got header 20:27:01 c4fmpacket: header 20:27:01 dst: *****RDCTD src: C4LSGN-7 20:27:01 dl: ul: 20:27:01 c4fmcalltracker: voice call started, dst: *****RDCTD dgid: 0 src: C4LSGN-7 id: 02da9e5ccad262fe 20:27:01 nvmm-csd: ignoring special callsign *****RDCTD 20:27:01 nvmm-csd: callsign C4LSGN-7 not found 20:27:01 srfipconn-c4fm: call started 20:27:02 batt: stat: done/100mA, 100% (new) (4136mV 31C) 20:27:06 c4fmcalltracker: got terminator 20:27:06 c4fmpacket: header 20:27:06 dst: *****RDCTD src: C4LSGN-7 20:27:06 dl: ul: 20:27:06 c4fmcalltracker: call ended, dur 4.1s ber 0.1% loss 0.0% rssi -46 20:27:06 srfipconn-c4fm: call stopped 20:27:11 c4fmcalltracker: got header 20:27:11 c4fmpacket: header 20:27:11 dst: *****RDCTD src: C4LSGN-7 20:27:11 dl: ul: 20:27:11 c4fmcalltracker: voice call started, dst: *****RDCTD dgid: 0 src: C4LSGN-7 id: 62a2cc1092525c2a 20:27:11 nvmm-csd: ignoring special callsign *****RDCTD 20:27:11 nvmm-csd: callsign C4LSGN-7 not found 20:27:11 srfipconn-c4fm: call started 20:27:12 batt: stat: done/100mA, 100% (new) (4140mV 31C) 20:27:14 c4fmcalltracker: got terminator 20:27:14 c4fmpacket: header 20:27:14 dst: *****RDCTD src: C4LSGN-7 20:27:14 dl: ul: 20:27:14 c4fmcalltracker: call ended, dur 3.2s ber 0.2% loss 0.0% rssi -46 20:27:14 srfipconn-c4fm: call stopped 20:27:20 srfipconn-client: ping sent 20:27:20 srfipconn-client: got pong 20:27:22 c4fmcalltracker: got header 20:27:22 c4fmpacket: header 20:27:22 dst: *****RDCTD src: C4LSGN-7 20:27:22 dl: ul: 20:27:22 c4fmcalltracker: data call started, dst: *****RDCTD dgid: 0 src: C4LSGN-7 id: a0d08cb82acc40f6 20:27:22 nvmm-csd: ignoring special callsign *****RDCTD 20:27:22 nvmm-csd: callsign C4LSGN-7 not found 20:27:22 wiresxtracker: received cmd unknown format 20:27:22 c4fmcalltracker: got terminator 20:27:22 c4fmpacket: header 20:27:22 dst: *****RDCTD src: C4LSGN-7 20:27:22 dl: ul: 20:27:22 c4fmcalltracker: call ended, dur 0.3s ber 0.0% loss 0.0% rssi -41 20:27:22 batt: stat: done/100mA, 100% (new) (4134mV 31C) 20:27:27 srfipconn-client: ping sent 20:27:27 srfipconn-client: got pong 20:27:32 batt: stat: done/100mA, 100% (new) (4134mV 31C) 20:27:34 srfipconn-client: ping sent 20:27:34 srfipconn-client: got pong 20:27:39 c4fmcalltracker: got header 20:27:39 c4fmpacket: header 20:27:39 dst: *****RDCTD src: C4LSGN-7 20:27:39 dl: ul: 20:27:39 c4fmcalltracker: data call started, dst: *****RDCTD dgid: 0 src: C4LSGN-7 id: 5624ce769a2a14b8 20:27:39 nvmm-csd: ignoring special callsign *****RDCTD 20:27:39 nvmm-csd: callsign C4LSGN-7 not found 20:27:39 wiresxtracker: received cmd unknown format 20:27:39 c4fmcalltracker: got terminator 20:27:39 c4fmpacket: header 20:27:39 dst: *****RDCTD src: C4LSGN-7 20:27:39 dl: ul: 20:27:39 c4fmcalltracker: call ended, dur 0.3s ber 0.0% loss 0.0% rssi -41 20:27:40 srfipconn-client: ping sent 20:27:40 srfipconn-client: got pong