OS X Fldigi and Timewave Navigator CAT problem

[[e-mail] [linuxham]]

Hi,

I’m trying to set up a new Navigator to work with FLDIGI.

I use MacLoggerDX on OS X for my logging program, and have that working fine
 the CAT control will successfully talk to my IC-756PROIII via an Icom CT-17. The ProIII also successfully talks to an IC-PW1 via the CT-17.

If I shut down MLDX and start FLDIGI I get the audio on the waterfall, so I know that audio is working, and PTT via Navigator is working fine.

My problem is that I don’t get CAT connection to show the frequency from FLDIGI to the PROIII, even when plugged directly to the radio.

Anyone using my configuration able to give me their settings or any other troubleshooting ideas?


I've previously posted this on the Navigator forum, but have not gotten any real answers there.

Thanks & 73,

David, WA1OUI

[kk5vd-/[e-mail] [linuxham]]

May or may not have any effect, verify baud rate, parity, stop bits, Check if hardware or software flow control is need or disabled.

Using RT Systems USB to the Yaesu 879D and 817ND here and it was would not work until hardware flow control was turned off. The computer here is a MacOSX system.


This connection is set to 4800 Baud, 8N1 with flow control disabled. Between the radio and FLDIGI.


Robert

[[e-mail] [linuxham]]

I'm still struggling to get Fldigi to talk to my PROIII over CAT. In talking to the Navigator Support, I realized that each radio has an address, but I don't see anywhere in the Fldigi program GUI OR the Icom756PROIII.xml rig file that will tell the program what address to use over the CAT line.

I've been crossposting this on the Navigator forum as well, but still no luck.


David, WA1OUI

[Ed [e-mail] [linuxham]]

Post by dhkaplan-***@public.gmane.org [linuxham]
I'm still struggling to get Fldigi to talk to my PROIII over CAT. In
talking to the Navigator Support, I realized that each radio has an
address, but I don't see anywhere in the Fldigi program GUI OR the
Icom756PROIII.xml rig file that will tell the program what address to
use over the CAT line.
I've been crossposting this on the Navigator forum as well, but still no luck.
David, WA1OUI

Read the manual for the rig and make sure the address is set to the
default. Turn off auto-baud, and transceive. This will all be in the
rigs menu.

Consider using flrig as this will provide more of the rigs features.

As long as you use the default address it all just works.

Ed W3NR


------------------------------------
Posted by: Ed <autek-***@public.gmane.org>
------------------------------------

[[e-mail] [linuxham]]

Thanks, Ed. You nailed it. Long ago I got instructions from Icom on how to connect the 756ProIII and IC-PW1 via CAT, for automatic tuning. For some reason they had me set the exciter CAT address to something that I now find is apparently non-standard, since Fldigi is expecting something else. Flrig DOES have a place to change the CAT address and when I changed it from what it was expecting to what my radio was set to it started working immediately. I changed the exciter back to supposed default, reset the PW-1 so it would talk to the ProIII again, and I'm finally up and running after several days of pulling my hair out. Now I can go back to operating, instead of troubleshooting!

Thanks again and 73,


David, WA1OUI

[Larry Levesque [e-mail] [linuxham]]

Open a terminal and type the following:
*lsusb

*This should give you a list of recognized usb devices such as this:

*[***@user ~]$ lsusb
Bus 003 Device 005: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 003 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial
adapter
Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 06a3:80c0 Saitek PLC Pro Gamer Command Unit
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04a9:1904 Canon, Inc. CanoScan LiDE 100
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio
Controller
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 046d:c51b Logitech, Inc. V220 Cordless Optical
Mouse for Notebooks
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
*
Notice the 2nd line down is my USB-Serial adapter.
This is my cat cable for my TS-850S.
Yours should be different but still indicate it is a USB-Serial adapter.

The important things to note here are that the info after the *ID* is
the manufacturer and device identification.

*Some* versions of Linux recognize these adapters correctly and install
the needed module (windows equivelent of a driver) autmatically.

If it was installed correctly, you should have a */dev/ttyUSB#* port
installed and available from fldigi:

fldigi settings image

or flrig:

flrig settings

Your /dev/ttyUSB# could be differrent depending on how many devices are
recognized and even depending on which order/port they are plugged into.

There is a way to set this up so they are always the same by creating a
udev rule.

As you can see, this is not as simple as Windows but it is much more
flexible.
Google is your friend here.

Search for the adapter name that shows up in the lsusb command and
keywords such as:
*HL-340 USB Linux configure

*If it was not recognized correctly, you might have to do some more
work, again, Google!*

*I know it might seem overwhelming at first but you will gain a lot of
confidence on your new operating system once you complete a task such as
this.

If the images do not show, you can see this info here:

http://digitalhamradio.org/index.php/ham-radio/linux-usb-rig-control-setup

Post by dhkaplan-***@public.gmane.org [linuxham]
I'm still struggling to get Fldigi to talk to my PROIII over CAT. In
talking to the Navigator Support, I realized that each radio has an
address, but I don't see anywhere in the Fldigi program GUI OR the
Icom756PROIII.xml rig file that will tell the program what address to
use over the CAT line.
I've been crossposting this on the Navigator forum as well, but still no luck.
David, WA1OUI

[mitchwinkle-/[e-mail] [linuxham]]

The following link is my explanation of keeping USB port names fixed for Linux installations. This works on Ubuntu flavors for certain. I have heard reports of others working as well. Symbolic links make this work and also make your head hurt less. The explanation is for BPQ32 but the concept is the same for any program needing to reference a USB serial port consistently. As long as you are allowed to specify the port directly by typing it in, you are good to go. Otherwise, if the GUI requires you to select from a list of "found" serial ports, you may have to edit the config file manually, but only once!


I too looked into udev rules. This is much easier.


Short version: make a symbolic link in the directory of your choice to the L-O-N-G name of the USB device as found in /dev/serial/by-id . If you run FLDIGI or FLRIG with your login id, put it into your home directory.


https://groups.yahoo.com/neo/groups/BPQ32/conversations/messages/14420 https://groups.yahoo.com/neo/groups/BPQ32/conversations/messages/14420

[mitchwinkle-/[e-mail] [linuxham]]

I call the link to my USB TNC "tnc" and I created it in the /usr/local/bin/linbpq directory. For FLDIGI, I doubt it makes any difference where you create the link, but just supply the full path of the LINK in the configuration screen. Using your home directory makes that easy, a la "/home/mitch/cat".