Anyone have cat control working? I called DigiRig and was told to order the 9600 baud cable set and RS-232 configuration. Audio in/out and PTT work but no CAT. When I try to access CAT my radio switches to transmit and gets stuck.
In below thread @David_Barkes succeeded with the CAT control setup on FTM rig after resolving some issues.
From what Iām finding online FTM-300 has a some CAT capabilities. Another potential source for configuration specifics is the user group for this transceiver model:
I have digirig mobile v 1.1 and have cat control issues with my ftm-300. My digirig board has 3 solder blobs on the row nearest the rs232 label and there are 3 open square copper pads near the cmos label.
Iām not sure whether I have a logic or rs232 setup- the video for modifying has a slightly different look (ver 1.9) than my 1.1
Please let me know how to proceed.
Thanks!
It sounds like your Digirig Mobile is in RS-232 configuration so as far as electric levels are concerned, your unit should be able to communicate with the transceiver.
Please refer to the radioās user manual to see what functions are supported via the serial port.
I ordered another digirig and a new 9600 dr cable, the new digirig mobile is configured for rs232. It sort of works meaning that it will do everything except read and change frequencies on the ftm-300d.
Is there a way to configure to do frequency control? Iām using it with the DigiPi program on a raspberry pi. I have looked at all the relevant forum and Yaesu manual information but have come up empty handed.
VFO synchronization with computer is a function of CAT control. Were you able to confirm in the user manual for the transceiver that serial CAT control is supported feature? From what I remember Yaesu FTM transceivers use the serial port for things like memory programming, GPS output, read-only TNC, but offer no CAT control.
You are exactly correct. Hardware/Protocol Limitation: The FTM-300DRās rear DATA jack (6-pin MiniDIN) supports RS-232 serial at up to 9,600 baud, but itās configured for one-way data output only (e.g., GPS NMEA sentences, APRS packet streams, or memory dumps). There is no documented bidirectional CAT protocolāno Yaesu command set (e.g., opcodes like āFAā for frequency set/read) exists for this model. Attempting to send CAT commands typically results in the radio interpreting the input as a PTT assertion, causing it to transmit unexpectedly instead of tuning.