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

The invalid fich message suggests that you have a frequency offset, I would suggest trying adjustments of 100Hz increments on the OS3's receiver frequency.

You might be able to check the mobile radio's frequency and adjust the reference frequency oscillator if it allows that and your output frequency is in error.

The inner deviation of C4FM is only about 650Hz so small frequency errors can cause a significant bit error rate.

How would I do that? Honestly, this device is a complete mystery to me beyond doing precisely what I'm instructed with it. Are you suggesting modifying the RF receive frequency? I'm using 446.7875, so what should I enter, and where should I enter it? I'm guessing 446.7876, 7877, etc, and lower 7870,7071, etc?? Or are you referring to something else. I don't have a super-accurate frequency counter, just something good to about 50 kHz at best, and is many years old.

    Peter W2IRT Yes, the changes you mention is exactly what I mean, just change the modem's frequency on the OS3.

    You might be able to use the Autocal connector, but it doesn't work for everyone so manually changing in 100Hz increments may be better for you.

    The frequency accuracy needed in these devices is greater than reasonably priced TCXOs can achieve and with subsequent ageing and temperature drift combined (in both radio and OS3) can be enough to cause problems. The FICH field in the C4FM frame doesn't have any error correction applied to it I believe, so if it is decoded incorrectly then the protocol breaks.

    Make sure the Half Deviation setting is turned off in your transceiver, and use plain C4FM modem mode on the openSPOT. If there's no such setting in your transceiver's menu, or you can't turn it off, then you have to use C4FM Half Deviation modem mode. In this case, run C4FM Half Deviation AutoCal, or manually adjust the RX offset on the Modem page in +-100Hz steps from -500Hz to +500Hz for the lowest BER. You can verify settings using the openSPOT's built-in local echo service.

    If AutoCal does not work for you then the RX offset between the transceiver and the openSPOT is greater than 500Hz. What you can do is to switch frequencies on the openSPOT, but keep the transceiver's frequency. For example, if the transceiver is on 433.900MHz, then test by setting the openSPOT to the following frequencies:

    433900500 Hz
    433900600 Hz
    433900700 Hz
    ...
    433899500 Hz
    433899400 Hz
    433899300 Hz
    ...

    You can use the built-in local echo service to test your own voice.

    If the openSPOT's status LED does not blink green when you press PTT even after adjusting the RX offset, then try setting the deviation DU menu to 177, the default value is 150.

    If you use a Yaesu FT-70D, then try changing setting #62 Transmit Modulation Level to: [WIDE] and use plain C4FM modem mode. AutoCal is not needed in this case.

      HA2NON

      How do I use the local echo service? I see many references to it, but I don't know what buttons to push or commands to send to invoke it. I am using a Yaesu FTM-400xdr mobile transceiver.

      And similarly, where do I find the half-deviation controls and auto-cal settings? My only interface to change settings in the OS3 is my Android mobile phone browser. I don't have a way to connect everything to a regular computer since the radio in question is mounted permanently in my vehicle.

      https://manuals.sharkrf.com/openspot4/en/control-calls.html#local-echo-service

      https://manuals.sharkrf.com/openspot4/en/autocal-connector.html#page-top

      The other settings are in the FTM-400XDR menus, not sure if it has a half-deviation setting for C4FM that is usually only applicable to NFM where peak deviation is reduced to 2.5kHz on 12.5kHz channels.

      All the OS4's internal web server pages are accessible from a phone browser via the menus from the front page, remember to use the advanced menu setting to enable access to everything.

        Tyrbiter
        I have the OS3 and not the OS4. Does the OS3 support local-echo? The manual doesn't tell me how to access it. It only says "call DGID is set to 99." I have no clue what those words mean or how to invoke them.

        I don't think the FTM-400 has half-deviation. Remember, too, that nothing had changed from the last time this OS3 worked together with this FTM-400 in my old vehicle. Both the radio and the OpenSpot just sat in a box in my shack for a few weeks.

        As for the frequency issue, I used a frequency counter and it was showing my TX frequency was a tiny bit high (438.7880 to 7881, and not 7875). I changed the Modem RX frequency accordingly and it didn't register at all - it wasn't even receiving. I set it down to 438.787200 and it did appear to receive a signal, and it didn't show any invalid fich lines in the log, but still unable to contact anybody on the AmericaLink reflector. I have no clue about how to program any other talkgroups in YSF to test there, nor, as I said, what I have to do to access the local echo. I don't know what a DGID is or how to set it up.

          The openSPOT3 also supports local echo. You can find the TX/RX DGID setting in your transceiver's menu. If you don't see a Half Deviation setting then your transceiver is using half deviation.

          Peter W2IRT My mistake, you will be able to find the same entries in the OS3 online manual starting here:

          https://manuals.sharkrf.com/openspot3/en/

          I think you are going to have problems if your frequency counter is only good to 50kHz or so and is old enough for the internal reference to have drifted or aged over time.

          As for the DG-ID it will be in the FTM-400 manual, also ensure that you have updated the firmware in the radio to the recent version found here:

          https://www.yaesu.com/downloadFile.cfm?FileID=17483&FileCatID=267&FileName=FTM%2D400XD%5FUSA%5FFirmware%5FUpdate%5F2020%5F12.zip&FileContentType=application%2Fx%2Dzip%2Dcompressed

          I would suggest spending some time reading the relevant parts of the latest manuals for the FTM-400, I don't have one so cannot advise in any more detail but Yaesu do provide updated manuals for the latest radio firmware features and that will help you get the best out of your equipment.