FTM-100DR Serial Port

1

So I cant seem to get the serial port working with the FTM-100 DR. The radio appears to NOT receive data from PC

I have a Digirig Mobile that i configured for RS232. I am using a Windows PC with Windows 11.
The Cable is the Audio +CAT cable for FTM

Audio +PTT work fine as expected ( testing with FLDIGI)

The serial port ( for Programming and Wires-X) does not work. If I use the SCU-20 from Yeasu both programming and Wires-X work.
Serial port setting are 9600 Baud, 8 bits 1 Stop, No Parity, No flow control

This is is what 'Ive tried so far: Using DigiRIg + Cable

  1. Loopback between pins 7 & 8 on the 10 Pin DIN echo characters in putty.
  2. GPS Data from Radio is received using Putty. So data on RIG_TXD ( Pin 7) is functioning
  3. Signal on RIG_TXD ( R1 on TRRS Green) is +/- 5V
  4. Signal on Pin 8 of 10 pin DIN is +/- 6.5v when characters are typed in Putty

SCU-20 Pin 8 on 10 pin DIN , Signal is +/-6v

Signals measured with O-Scope, with 10X probe.

Everything seems within spec, 'Im wondering about RTS/CTS flow control Since those are looped back in the DigiRIG cable

Or is there something else I am missing ?

2

I do not have this transceiver, but SCU-20 means it is a proprietary interface, right?

blob
blob500×100 1.78 KB

3

It’s a possibility that the software you are using wants to use RTS/CTS lines for their original purpose, but in that case I would expect the radio to key up when the software activates RTS. Another possibility is that the software checks for the device ID of the UART and refuses to talk unless it’s Yaesu’s. That would be a shame.

4

Denis, Thanks for the reply,

You have done a nice job with the DigiRIg product. I have another one I use with the Chicom HTs and it works great.

It wouldn’t surprise me if the second case was true. I’m not real impressed with Yeasu’s Human interface and their proprietary PC Control interface.

It does not key up when I run their Wires-x or ADMS software.

1 Like
5

It appears to be just a Prolific USB to RS232 converter. The problem is that Windows 11 no longer supports this particular Prolific chip, So everytime Windows does an update, I have go in and manually install an older driver. Maybe I should have bought an ICOM !