Yaesu

Yaesu (native CAT)

A native backend talks to an FTDX10 / FTDX101 (and close relatives) directly over the rig's USB/serial port — no OmniRig. Pick Yaesu (USB) in Settings → CAT: COM port + baud (FTDX10/101 default 38400).

Frequency, mode, VFO A/B (MAIN/SUB on the 101), split and PTT are covered, and OpsLog follows the VFO you are actually on — the displayed frequency, the logged frequency and the VFO a cluster spot tunes. Split is worked out from which VFO transmits, so simplex on the SUB receiver is not shown as split.

The older sets: five-byte binary CAT

Modern Yaesus take ASCII commands (FA, MD0, VS). Three families do not, and OpsLog has a separate backend for each — which is why the model you pick has to be the one you own:

FT-817 / FT-857 / FT-897 — Yaesu's five-byte binary CAT.

• Set the rig's CAT RATE menu to the same speed as the setting here.
• The port opens with two stop bits, which is what these radios expect.
• Split is not read back: on these models it lives in EEPROM, and OpsLog will not guess at it.

FT-1000MP and FT-1000 / FT-1000D — the same five-byte frames, completely different commands, and the two report their frequency in different units. There is no command to ask the radio which it is, so:

Choosing the wrong one of these two reads every frequency out by a factor of 1.6. If your frequencies are wrong by roughly that much, this is why.

CAT RATE and the two stop bits apply here as well. Split can be set but is not read back.

RTTY sideband

ADIF records only RTTY, and the rig has both sidebands. OpsLog sets RTTY-L by default, the older convention; there is a switch for RTTY-U if your FSK controller or decoder wants the upper one.

The Yaesu console

With the native backend connected, a console tab (and a Main-view pane) gives:

• S / PO / SWR meters — power in watts on a curve measured against the rig's own display, SWR as the ratio itself, with peak-hold so they stay readable between CW words or SSB syllables.

• Band and mode buttons — CW, RTTY, DIGI and PSK show their sideband; click the active button again to switch it.

• AF / RF / squelch, AGC, IPO–AMP1–AMP2, 6/12/18 dB attenuator, NB, DNR, narrow filter, power, mic gain, VOX, split and ATU tune.

• SPLIT places the transmit VFO up 1 kHz on CW/data, up 5 kHz on phone.

• In CW the mic gain and VOX give way to a CW card: keyer speed, break-in and ZIN (zero-in).

• MONITOR with its level — hearing your own transmit audio, which is how you notice the mic gain is clipping before somebody tells you on the air.

• NB level, in the rig's own 0-10 rather than a percentage.

• DNF (automatic notch) and NOTCH (the manual one, with its frequency), CONTOUR with its frequency, and in CW the APF with its offset, -250 to +250 Hz around your pitch.

• Roofing filter — 12 kHz / 3 kHz / 500 Hz / 300 Hz, whichever your rig has fitted. This is the one that keeps a strong neighbour out of the receiver rather than merely out of the audio.

• IF width, as the rig's own index 0-23.

  The index and not a figure in hertz, deliberately: what bandwidth each step means depends on the mode and on the roofing filter fitted, and the radio shows it on its own display. Putting a number here that might not be the one the radio means would be worse than none.

Sliders only respond to the mouse wheel after you click them, so scrolling the panel can't change the transmit power by accident.

CW with the rig's own keyer

A CW engine sends your macros with the radio's internal keyer (CAT KY) — no WinKeyer, no second cable. Pick Yaesu (rig keyer) in Settings → CW keyer.

• Works on the FTDX101 / FT-991A / FT-710 family.
• An FTDX10 does not accept it (KY is refused, DAKY doesn't help) — OpsLog says so and points to the serial DTR keyer on the rig's second COM port (the Serial port CW engine), which works. See Audio and Keyers.
• CW speed is one setting everywhere: the console slider, the CW panel and the rig's front panel stay in agreement.

Notes

• A Yaesu that is switched off is reported as such (opening the port is not "connected").
• If your interface goes into transmit the moment OpsLog connects, enable the lower DTR/RTS on connect option — see CAT Control.