ad: hamshirts-1

Problem with yaesu SCU-17 and cable CT-62 (rs232)

Discussion in 'Working Different Modes' started by EA5NR, Dec 6, 2017 at 8:25 PM.

ad: L-HROutlet
ad: l-rl
ad: Subscribe
  1. EA5NR

    EA5NR Ham Member QRZ Page

    Hi friends:

    I have one cat cable for the FT897D since 2009 (zlp electronics). I recently lent it to a friend to use with the scu-17 interface and the FT817ND but I can not get it working.

    With the desktop computer, separately yes, rs232 cable to com1 port (RS232) and the interface via usb (Data).

    The problem is with the laptop, which does not carry rs232 port, only usb. If I connect the CT62 to the SCU-17 (it has two virtual ports com) and I only connect the USB to the computer, with HRDeluxe (free version) or another software (JT65, logger32,etc...) I can not detect the FT817ND (CAT). I have tried it with all possible options, and it does not work.

    Is there a difference between the original CT62 yaesu and another alternative cables (mini din cat to rs232)?

    Thanks
     
  2. KB0MNM

    KB0MNM Ham Member QRZ Page

    Here is a response that might help with the RS-232 portion of the cable ( sorry- time is short- response to other problem may not apply : ).
    Try these steps: ( Skip step 1 )
    1. Verify a minimum of 8 Volts direct current at the tip of the submini ( 2.5mm ) plug used to power the device. Note that the light-emitting devices ( LEDs ) might indicate power, yet the use of a small 9 volt battery may not be sufficient after connection is made.
    2. Set the terminal program for full-duplex and various rates- these rates are normally slow- for example, 1200 BPS or 300 BPS. In full-duplex mode, your terminal program should verify that you are typing something to the UTU. Upon power up, most older Kantronics equipment would send something to your computer for confirmation.
    3. Try using the PuTTY terminal program, Xmodem(tm), or ProComm(tm) in the older shareware version.
    4. Build a loopback for your cable. Build a female DE-9 connector with intentional short-circuit between pins 2 and 3 only. Connect this to your cable from the computer at the end where the UTU would ordinarlly reside. If you are running your terminal program at full-duplex and 'No handshaking' ( RTS/CTS and DTR off ), anything that you type on the computer should echo as double characters. Should the *only the characters typed* return, the cable or computer is improperly set up. The loopback may be moved to the back of the computer ( connected directly to the computer's serial port ) to test for a defective DE-9 cable. If the computer serial port is a DB-25 see the converter in step 6.
    5. If the loopback test above shows double characters, connect the UTU again and re-connect minimum power as in step 1. Try setting the terminal program to enable hardware handshaking ( DTR enabled ). Re-try setting different low BPS rates.
    6. Build your own serial cable or verify the one below only if your computer has a DB-25 *serial* port. Do not use this cable connected to a DB25 parallel port.
    DB-25 to De-9 Pin
    1 to 5 Protective Ground ( May not be required )
    7 to 5 Signal Ground ( Always required )
    2 to 3 Transmitted data from the PC to the UTU ( Always Required )
    3 to 2 Received data from the UTU to the PC ( Always Required )
    4 to 7 Request to Send (RTS) ( May be required from the PC to enable the UTU )
    5 to 8 Clear to Send (CTS) ( May be required from the UTU if the PC terminal program requires it )
    6 to 6 Data set Ready (DSR) ( May be required from the UTU if the PC terminal requires it )
    8 to 1 Carrier detect (CD) ( May be required from the UTU if the PC terminal requires it )
    20 to 4 Data Terminal Ready ( May be required from the PC if the UTU requires it )
    Be aware that signalling levels for RS-232 ports are between -15 VDC and +15 VDC, with negative levels representing a logical one. Commonly used voltages are -12 VDC and +12 VDC , yet you may find -5 to +5 VDC to be functional. Do not assume that because the PC can produce 12 volt levels, that this is also done by the UTU.
    7. Buy or borrow a 'break-out' box, alternately, see a qualified data repair person ( computer specialist in hardware with knowledge of terminal programs ).
     
  3. KB0MNM

    KB0MNM Ham Member QRZ Page

    Now that I have a moment, you need to be aware that your cable connects to a radio ( Not a Kantronics UTU or modem ), but a lot of the same applies. If you know which rate the other radio is supposed to talk through the RS-232 cable, that helps. If you are expecting 'full hanshake' through an RS-232 cable, that is sometimes normal. But if you are using an USB adapter to RS-232 cable- that might not work if RTS/CTS and/or DTR/DSR handshaking is needed. You will need to consider that the mini-din pin numbers probably *do not* match those of a regular RS-232 cable ( Step 4 pins will be different on the mini-din end ), but that you can work out with an ohm-meter and small probes ( RS-232 female replacement pins are great for male-mini-din testing ). If the cable is not at fault, the software for USB may just not provide the signals needed to talk to the other variety radio. The requisite signalling and levels should be in that radio's manual- which could vary from yours. BTW- "De-9" is an official manufacturer's designation of what many folks now call "DB-9". It ( DB-9 ) is incorrect, yet commonly used.
     

Share This Page