I did a quick review of the manual for the SCU-56 and did not see any mention of PTT.
The DX Engineering website (where I download the SCU-56 manual) implies it has CAT control, so the function may be a serial command, not a physical pin.

Next I searched the FTM-200DE manual.? Page 31 does not show any connections to pin 3 (PSK PTT), but does show CTS and RTS pins as "data communication control".? I would take that to mean hardware handshaking of serial data, not the PTT.? If that is the case, you cannot use those pins for both functions.

After searching those documents, the connector has the PTT pin, but it does not appear to give the computer the function.
I believe the USB interface of the FTM-200DE can only be used for programming memories and updating firmware.?
I do not believe this radio has the PTT function though that interface.?

-------
Rob KB8RCO

开云体育

Hello Mikel,

Though you say a COM port shows up, did you check in the Device control panel and it doesn't show an exclamation point?? You might consider installing the *Yaesu supplied* Prolific driver as they have made these adapters proprietary with custom USB VID:PIDs:

??


Next up, Yaesu mobile radios do NOT supported standard CAT control for rig control (their HF radios do) and instead, have their own proprietary signalling protocol.? That said, they do support some external signals like PTT, SQL, etc.? The SCU-56 cable is really intended for Wires-X digital communications (PDN or HRI mode) and NOT necessarily for packet communications.? Per the FTM-200 manual, page 33 says to use the CT-164 or CT-163 cables;

??

You mentioned in your email, you weren't having success with settings like:

Did you also try settings like:

?? PTT COM16 -RTS
?? PTT COM16 - RTS DTR


If those don't work, maybe you can use a volt meter to see what's on Pin 3 coming out of the SCU-56 cable is for PTT??? You can download a Windows tool such as this one to assert the various RS232 signals:

??

which will let you assert either the RTS or DTR pins to test if things are working properly.

--David
KI6ZHD

Hi Mikel,

I don't have the Yaesu FTM-200DE but I do have a Yaesu FTM-100DR which is the predecessor version for the North American market (I believe the DE versions are for Europe).
Looking at the manual for both FTM-100DE/DR and FTM-200DE/DR it appears that both physical connections (Mini-Din 10-pin) and menu settings are the same (or very much alike) for both models.

Forget any ideas about using USB or Serial interface to utilize the internal TNC within the Yaesu radios. Yaesu made absolutely certain that they cannot be used for standard AX.25 communication (despite implementing the full AX.25 protocol in their firmware). You can receive AX.25 packet headers and payload but there is no way to transmit anything (as far as I can tell) from an external source. All transmissions from the internal TNC are based on position data and internal configurations (beacons, automatic responses).

However the radio works fine with DIrewolf (or any external TNC) with the internal TNC turned off and using the Rx/Tx/PTT signals on the MiniDin-10 Data Connector. Note that there are pins for 1200 baud packet and 9600 baud packet and therefore two ways you can wire the interface cable! If you want to use 1200 baud packet you can use either way of wiring, just make sure that the Data Speed setting in the menus matches the wiring of the interface cable (regardless of the actual data rate used for communication). When using 9600 baud packet the interface cable must be wired to use the 9600 baud pins to ensure that FM pre-emphasis and de-emphasis are bypassed.

If you don't feel like making your own interface cable, there are companies that make custom interface cables. To avoid soldering the tiny Mini-Din connector pins you can use the Yaesu CT-167 cable (which is what I did). That cable has the Mini-Din 10 connector on one end and allows you to add the connector(s) of your choice on the other end.

You can also use the Yaesu CT-163 or CT-164 as an adapter from the proprietary Mini-Din 10 to standard Mini-Din 6 (common pinout for most VHF/UHF radios with this type of Data Connector).

As already mentioned in prior posts, the Yaesu SCU-## cables are for Wires-X and of no use.

73,
Thomas
KK6FPP

Thomas - you state?
>>?However the radio works fine with DIrewolf (or any external TNC) with the internal TNC turned off and using the Rx/Tx/PTT signals on the MiniDin-10 Data Connector.
I think the question at hand is "When using Direwolf as an external TNC, how do/did you connect pin 3 (PTT)?"

The previous comments are to say that CAT PTT (like: PTT RIG 2 localhost:4532) is not available - or is it?
RTS/DTS of the Virtual COMM port (like: PTT COM16 -DTR) are not connected to PTT - or are they?

Or (my assumption), you need to use the sound card PTT (like: PTT CM108 -3)?
-------
Rob KB8RCO

Hi Rob,

I'm not aware of rig control for the FTM-100/FTM-200 radios (it may exist, but if so it is not documented).

I'm supplying PTT to the radio's Data Connector from a C-Media CM-108/109/119 based USB Soundcard (GPIO pin 3) but other methods of producing PTT supported by Direwolf are equally possible (such as using RTS or DTR from a serial port).
I used home-made soundcard interfaces as well as a DRA-30 from Masters Communications.

To use the FTM-100/FTM-200 radio with Direwolf and avoid any custom wiring or soldering, consider this:
Yaesu Radio FTM-100/FTM-200
Yaesu Adapter CT-163 or CT-164
Standard straight-through Mini-DIN 6 male to Mini-DIN 6 male cable
Masters Communications model DRA-36 or Kits for Hams model DINAH (both of those USB sound interfaces have MiniDIN-6 connectors and are based on the C-Media chips; both products are available as kits or fully assembled)

Thanks
Thomas
KK6FPP

Just to be clear - the question(s) was the original post from Mikel EA2CW.

Mikel EA2CW
So, just to confirm:
There doesn't appear to be a way to cause the radio to PTT through the SCU-56 cable.
??? a) Not through a CAT command
??? b) Not using the built in virtual COMM port DTR ot RTS lines
For digital interfaces using the data port, the PTT is controlled by Pin 3 of the data port, so option would be:
??? 1. CM108 GPIO (like DRA-36 or DINAH interfaces)
??? 2. separate (from SCU-56) COM interface such as a FTDI or CP210x type interface with exposed control pin
??? 3. some other external PTT circuit that can be configured through Direwolf
-------
Rob KB8RCO

Thank you for your clever answers and help, I will read all of them slowly and check the different options shown.

By the moment, I am using a FT-817ND (which is the one I like to free for SOTA) and found the equivalence between the 2 rigs' data connector pins.

The FT-817 is working now for several years with an "U5 Link box for Yaesu" and I am currently waiting for the 10pin connector to arrive.In the meantime, I'll try your options.

If all works ok, that's the way it will remain. Otherwise, I'll try another solutions. I'll tell you how it all goes.

Actually, the final goal is to have Direwolf running as now is, on ver 1.6 under Debian 10 on an I5 PC. (I prefer much this than having it running under Windoze)

Thanks all you again!

73, Mikel EA2CW