FTdx5000 Help

[WC2L]

I have been looking at the manual and trying to setup RRC-1258 MkII: Control and RRC-1258 MkII: Radio. I have the latest firmware. The two devices are talking in the status window. I have the radio connected to Com2 and I have the computer connected to the control on Com2.

I have straight through cables built with pins 2,3,5,7 & 8 connected (on both devices). On the RRC-1258 MkII: Radio  I am not seeing the radio connect. The radio is set for 38400 and RTS is disabled.

I am not sure what I am missing. Can someone help? Give me pointers??
Eventually it would be nice to hook up the Navigator and have it all work.

TNX Will WC2L

[dj0qn]

Will,

You didn't provide the most important information: where are you trying to get it working, within
the home network first? It may be a network issue. If so, drop me a mail at dj0qn (at) darc.de
and I will send you my networking checklist to help walk you through the installation.

73,
Mitch DJ0QN / K7DX

[WC2L]

I don' think it is a network issue. I can hear audio on the control side. I did mention that I have connectivity from the control to the radio side. I am local to everything (radio, computer, both units).  I will send you the info.

Will WC2L

[dj0qn]

It may not be, but sometimes people forget to forward a UDP port correctly that can cause problems.

What error message are you receiving on each RRC (in the status menu) after attempting a connect?

73,
Mitch DJ0QN / K7DX

[WC2L]

no error, just no radio status on either side:
Connection status OK
SIP status Connected/transfering
Last SIP error None
RTP status Excellent(60)
UDP cmd status OK(44)


Will WC2L

[NM0EJ]

I had precisely the same problem as Will.  After getting help from Mitch and doing some research I learned that (at least some) Yaesu radios require 2 stop bits for serial communication. 

I had changed my baud rate on the FTDX-5000MP to 38,400 and had turned off RTS.  Since my radio is at the remote site, I modified the below instructions from Mitch to 38,400 baud, 2 stop bits.  Using Ham Radio Deluxe at 38,400 and RTS and DTS unchecked, it connected instantly!

Below are the instructions from Mitch.  Remember to make sure all your baud rate settings are consistent, and select 2 stop bits. 

CAT CHECKLIST
---------------------
IMPORTANT: In both scenarios, you MUST first install a standard serial cable between the TS-480 body and COM2 of the radio RRC!

USING A STANDARD SERIAL CABLE
============================
1) Change the CAT rate on the TS-480 to 4800 baud (menu 56). This rate keeps traffic over the internet to a minimum and faster is not necessary for CAT.

2) Change the COM2 serial settings of the radio-RRC to mode-4, 4800 baud, data bits 8, stop bits 1 and submit/apply changes.

3) Change the COM2 serial settings of the control-RRC to mode-4, 4800 baud, data bits 8, stop bits 1 and submit/apply changes.

4) Plug a serial cable in between your PC and the control-RRC COM2

5) Set your software to use the correct COM port on your PC at 4800-8-1-N

USING A USB CABLE
=================
1) Change the CAT rate on the TS-480 to 4800 baud (menu 56). This rate keeps traffic over the internet to a minimum and faster is not necessary for CAT.

2) Change the COM2 serial settings of the radio-RRC to mode-4, 4800 baud, data bits 8, stop bits 1 and submit/apply changes.

3) Install the Microbit Setup Manager if you already haven't. You don't need the problem for this, but this installs the correct drivers on your PC.

4) Change the COM2 serial settings of the control-RRC to mode-4, 4800 baud, data bits 8, stop bits 1, "use USB Com Port as COM2" to "Yes" and submit/apply changes.

5) Plug a USB cable between your PC and control-RRC. Make sure you do NOT do his before step 3 above!

6) Find out the correct port in your Windows Device Manager to use by looking for the "Microbit RRC Virtual COM Port (COM2)"

7) Set your software to use the this COM port on your PC at 4800-8-1-N.

Thanks again, Mitch!

[dj0qn]

My pleasure, but note that I have a separate CAT checklist for a "Twin" configuration.

I just noticed that I never answered Will, since I was on vacation that week and missed that posting somehow.

You are correct that it is not a network issue. To be able to identify what the issue is, we would need to know what
kind of rig you are using, as well as if this is a "Twin", remote panel or a pure software control using an RRC (which is
what NM0EJ was doing). If this is software control only using a Yaesu rig, then his suggestion may solve your problem.

73,
Mitch DJ0QN / K7DX