Files
OpsLog/wiki/Yaesu.md
T
2026-08-02 06:40:10 +02:00

48 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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 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, IPOAMP1AMP2, 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).
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]].