I just reinstalled my Yaesu FTM-400xdr into a new vehicle. I am no longer able to get my OS3 to work properly with it. I have it configured to use Profile 1 in C4FM, connected to the YSF "AmericaLink" reflector. I am able to receive fine. The OS3 is transmitting to the radio and the recovered audio is good. I am not able to transmit back through the OS3 no matter what I do. I must have messed up a setting somewhere but I can't figure out what's wrong.
Is there any way to initiate a Parrot-like group/etc from the Yaesu? Is there maybe something messed up on the Yaesu? I don't have another YSF-capable radio. I know it's transmitting on the correct frequency (I can hear the digital noise when I listen on an analog radio).
How can I troubleshoot this?
This is an excerpt from the log from when I'm transmitting on the Yaesu:
12:25:22 homebrew: ping sent
12:25:22 homebrew: pong received
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: missing callsigns for late entry
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: invalid fich
12:25:23 batt: stat: discharge, 67% (new) (3744mV 28C est. 6h42m)
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: invalid fich
12:25:23 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 nvmm: net check
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 nvmm: net check ok (40 ms)
12:25:24 nvmm: net ip report
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:24 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: got header
12:25:25 c4fmpacket: header
12:25:25 c4fmcalltracker: invalid fich
12:25:25 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: missing callsigns for late entry
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:26 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:27 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:28 c4fmcalltracker: invalid fich
12:25:29 httpcln: max. content length is 0, abort
12:25:29 nvmm: net ip address report retry 2/10
12:25:29 homebrew: ping sent
12:25:29 homebrew: pong received