ICOM IC-7000 problems connecting

I have an IC-7000 ,digirig, a " Yaesu MiniDin10 9600-baud Data and CAT Cable for Digirig Mobile", a " Icom IC-706 cords for Digirig Mobile". which show to be compatable with my IC-7000. I also have several os’s and machines to try on but so far the Win10 machine sees the audio device but has a problem that is unresolved, possibly keeping it from working. Linux Ubuntu 21.10 seems to have the audio figured out but cannot find the control side. wsjtx takes much longer to not find the device than does if I point it to an incorrect device. I guess vox does not work on the minidin or the large data din or at least not on mine. anyone with a IC-7000 care to tell me how yours is coming along.

                            Thnx KD5NSK

You have a diverse bunch of options there. Let’s focus on one setup at a time. Please pick one OS, one radio and one digital modes software. Describe a specific issue and we’ll take care of that first.

I broken it down to ubuntu 21.10, my ic-7000 and the DigiRig… I found out after some time that my ubuntu is seeing the device as 10c4:ea60 Silicon Labs CP210x UART Bridge and puts it at a tty/usb

Computer says it know this about the device

Bus 001 Device 014: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10c4 Silicon Labs
idProduct 0xea60 CP210x UART Bridge
bcdDevice 1.00
iManufacturer 1 Silicon Labs
iProduct 2 CP2102N USB to UART Bridge Controller
iSerial 3 42e4e612fda3ec11af14e789a29c855c
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

WsjtX says

Hamlib error: Communication timed out
rig_get_freq(2171): freqMainA=0, modeMainA=, widthMainA=0
rig_get_freq(2171): freqMainB=0, modeMainB=, widthMainB=0
rig.c(2173):rig_get_freq return(-5) while getting current frequency

Is this of any help?

Let’s first check the interface configuration. For CAT to work Digirig has to be set for CI-V. I’m not finding your order for the interface so I can’t check on my end. The solder jumpers should be like this:

Next we’ll look at the cables connections. The CI-V cord should have the straight TRRS end in Digirig’s socket labeled “serial” and angled TRS end with green molding in ICOM’s remote socket:


It is soldered at the green and no other pads are shorted…the civ remote connects with the 3.5mm to the trrs DigiRig serial side to trs ic-7000 civ port… when I plug in each one of the two DIN audio cables the transmitter keys up.

Looks like this may be a problem with the wsjtx app or my hamlib more than else… When the audio is plugged in with wsjtx running the PTT is transmitting continuously. When I kill wsjtx or change the rig back to NONE the PTT opens again for receive.

In WSJT-X please set PTT to RTS over Digirig’s COM port

Thats was it…Appreciate it very much

1 Like

I have an IC7000, Win 11, home brew cables in the mini din format. Snap on ferrites on all cables. Runs 100 watts just fine. I have even done JS8 on 2M and 440 as is.
Internal attenuator is connected. Audio right on the edge with this ASUS Laptop. No known issues. Soon to switch my IC756PIII.

Alan WA1AR

1 Like

I have an IC-7000 and recently purchased the DigiRig (CiV) and cables for the IC-7000. The Digirig powers up and my PC (running Windows 10) sees the com port (com 9) and the Sound card. I’m going through the configuration in WSJT everything seems normal. I set it for 9600 baud on com 9 and the PTT to RTS (com 9). The CAT test works and so does the PTT test. But when I try to call CQ the radio stops transmitting about 10 seconds in and I get a configuration error.
Any help would be appreciated.
73 de AB6UI

You’re dealing with RFI. Please refer to “sticky PTT” section in the troubleshooting guide.

Hi all,
I have an IC-7000 with the AH-4 tuner, a 22m long wire antenna, well earthed at both the tuner and the rig.
I have a 20m feed line with a shielded control line (4 core screened).
So far I have had no end of issues with hamlib errors in WSJT-X.
I have tried clamp on ferrites on all cables except the feed line as it is thick.
Lower TX power work fine, which indicates common mode current interfering in the shack.
Sometimes I can get high power (50-100W) and sometimes I cant, not sure why there is so much variability here. I would be happy to just FT8 DX on 10 to 20W but it is so inconsistent. Some bands I cant even use 1W.
I have tried counterpoise wires running away from the tuner.
Hopefully someone has some specific experience with this setup, as the only option I have left is an UNUN at the tuner end, but this is expensive and disruptive (the AH-4 is hard to open and close back up), and from what I can glean from searching the internet, the AH-4 should not need one (even some confirmation on this would be a great start).
Thanks in advance,

Do you only receive errors during transmit?
Can you share the screenshots of the error messages and CAT settings?

Hi Denis.
The issue is only on TX.
The error is this old chestnut:
"Hamlib error: Communications timed out while getting current VFO frequency.“ amongst the various similar errors you see riddling the forums.
This is clearly stray RF but I am struggling to find the best way of mitigating it.

Are there any slower baud rates you can try for CI-V? Different stop bit settings?

Tried all speed settings, haven’t tried stop bit etc.
I am thinking this is more an RF mitigation problem than trying to find a software workaround?

It is, but it sounds like you picked low hanging fruit and there may be some options to make communication less vulnerable to the interference.

I have a similar problem. I have an IC-7000 with a digirig CI-V configuration. The controlling system runs linux mint 21. The connection to the radio is via the “green 9600 baud cable”, (Yaesu, Icom, Kenwood 9600 baud MiniDin6 audio cable for Digirig Mobile – digirig) , while CAT is over a separate CI-V cable (FTDI). I have no problem with receive audio into direwolf 1.7, but the apps dependent on direwolf do not transmit. For example, YAAC connects to direwolf via AGWPE; stations are received and displayed but I cannot beacon my location. Direwolf controls the PTT. I have hamlib installed. Direwolf is compiled with hamlib support. The digirig device is /dev/tty-digrig.
If I enable PTT with the command “PTT /dev/tty-CAT RTS” the xmtr is NOT keyed. I do not hear audio using headphones attached to the audio jack on the digirig. If I use a hamlib command in direwolf.conf (PTT RIG 3060 /dev/tty-CAT) to key the rig on a different usb device (the FTDI), the rig keys but still no xmtr audio. Any help with this would be appreciated.
73, John, NX2I

here’s an update:
if I specify “PTT /dev/tty-digirig RTS” instead of “PTT /dev/tty-CAT RTS” in direwolf.conf, the rig is keyed, but still no transmit audio.

You can check if the audio is present on Digirig’s port by plugging in regular headphones into the audio port. That will tell you if the issue on the software side or on the radio’s side: