Feature #4799

Implement split MODE (e.g. RX in SSB, TX in CW) when radio supports it (e.g. Yaesu FT-857)

Added by David Behar over 5 years ago. Updated about 2 years ago.

Status:New Start date:05/07/2017
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Model affected:(All models)


Although CHIRP accommodates split frequency, it appears it does not accommodate split modes. In my Yaesu FT-857D (which has been configured for MARS operation, so acts like an FT-857), I operate mobile, and when conditions are poor I will transmit on CW and receive on SSB. (E.g., receive on 3.900 MHz LSB, and transmit on 3.8995 MHz CW.)

The radio memory accommodates split frequency and mode, but it seems that CHIRP is not reading or writing the CW transmit mode.

I'm not sure whether this should be characterized as a bug or as a feature request.


Updated by David Behar about 5 years ago

UPDATE: After some additional experimenting, I believe that the IMG file for FT-857D does in fact store any alternate MODE for transmit. Therefore (for example), a user is able to maintain split modes (e.g., listening on USB and transmitting on CW).

HOWEVER, it seems like split mode info can only be entered on the radio, and not through CHIRP. I don't see any way to enter an an alternate transmit mode through CHIRP - neither through the Import function (with a CSV file), nor through the user interface.

I think this is a limitation for all radios -- not just the Yaesu FT-857D.

This issue should therefore be characterized as a feature request, not a bug.

Updated by Bernhard Hailer about 2 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from Yaesu FT-857 -- CHIRP does not read or write a separate mode for transmit -- Version CHIRP daily-20170324 to Implement split MODE (e.g. RX in SSB, TX in CW) when radio supports it (e.g. Yaesu FT-857)
  • Target version set to chirp-daily

Also available in: Atom PDF