¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. KM4ACK-Pi
  2. Topics

Patron: Not sure if it is My radio or my FLRIG in BAP #ic-7100 #flrig

Frank Roginski W4FRR
 

I am running an IC-7100 using the USB cable direct into a new Pi 4 4GB. I have run the updates and upgrades as well as updated BAP.
When I look with lsusb I can see everything else that I have plugged into the Pi but the radio, and when I try to connect to the radio via FLRIG it is not seeing the radio nor do I have the Silicon Labs drivers available to select from the drop down.
This was working before (but took some fidgeting) on my Pi 4 2GB running BAP, but that Pi has come to it's end and has given up the ghost.
The radio is working fine and I have no issues with it other than I can't see it and control it via FLRIG so Digital is off the table.
Any suggestions? or should I just send it back to Icom to take a look at the usb port on the back of the radio?
It is still under warranty until January.
 

What do you get if you run:
ls /dev/serial/by-id

--
73, de KM4ACK
|
|

Frank Roginski W4FRR
 

Thanks for the quick reply.
This is what I am receiving when I run that command.

ls: Can not Access 'ls /dev/serial/by-id' : No such file or directory

73,
Frank W4FRR
Frank Roginski W4FRR
 

Also for full disclosure I used the Back up micro SD card that I had for the Pi 4 2GB with BAP in the new Pi 4 4GB.
Everything came up and is working great in BAP and I have even been able to use Winlink via telnet no trouble.

73,
Frank W4FRR
 

how old is the backup SD? Wondering if this is related to an upgrade of any software?

W1BAW? Bruce Wattendorf

On Wed, Sep 14, 2022 at 6:51 PM Frank Roginski W4FRR <agmec37@...> wrote:
Also for full disclosure I used the Back up micro SD card that I had for the Pi 4 2GB with BAP in the new Pi 4 4GB.
Everything came up and is working great in BAP and I have even been able to use Winlink via telnet no trouble.

73,
Frank W4FRR

Frank Roginski W4FRR
 

The backup was current in June and when I plugged it in I did all the updates and upgrades as well as run the BAP update.

Thanks 73,
Frank W4FRR
 

ok I wanted to make sure. Somebody else was having issues with a 7100 recently. Just for reference, did you upgrade your radio recently and what firmware version?? Even though like you said it might be a hardware issue.??


On Wed, Sep 14, 2022 at 7:02 PM Frank Roginski W4FRR <agmec37@...> wrote:
The backup was current in June and when I plugged it in I did all the updates and upgrades as well as run the BAP update.

Thanks 73,
Frank W4FRR

Frank Roginski W4FRR
 

I have just checked and my firmware is the latest available from Icom.
I have not had to update it since I bought it.
I purchased it new in January it came with the latest.
Which is now 8 years old though.
The CPU is M 1.11 / S 1.00 / C 1.10 and the DSP is I 1.03 / D 1.00

73,
Frank W4FRR
 

ya so it prob is not the firmware but it will be good to have the info incase.?


On Wed, Sep 14, 2022 at 7:39 PM Frank Roginski W4FRR <agmec37@...> wrote:
I have just checked and my firmware is the latest available from Icom.
I have not had to update it since I bought it.
I purchased it new in January it came with the latest.
Which is now 8 years old though.
The CPU is M 1.11 / S 1.00 / C 1.10 and the DSP is I 1.03 / D 1.00

73,
Frank W4FRR

 

On Wed, Sep 14, 2022 at 05:47 PM, Frank Roginski W4FRR wrote:
Thanks for the quick reply.
This is what I am receiving when I run that command.

ls: Can not Access 'ls /dev/serial/by-id' : No such file or directory
So that tells me that the Pi isn't correctly loading the radio when it is plugged in. A couple of things to try:
1. Reboot the Pi with the radio connected to the Pi and see if it makes a difference. Run the "ls /dev/serial/by-id" command after boot.

2. Reboot the Pi without the radio connected. After boot, connect the radio and try the ls command again.
?
--
73, de KM4ACK
|
|

 

Do you have a Windows computer?? Try installing the drivers on Windows and see if you can see the device in Device Manager as one of the COM Ports.? Mine shows as "Silicon Labs CP210X USB to UART Bridge" and as two ports, COM5 and COM6 in my case.? I can tell that it is working by disconnecting the USB cable and seeing the ports go away, then returning when I reconnect the USB cable.? This should tell you that the IC-7100 USB connection is functioning.

--
--Bill AA6BD
Frank Roginski W4FRR
 

I performed the test that you asked me to do.
On the first try I forgot to unplug my GPS dongle from the Pi so ultimately I received?two answers.
When the GPS dongle was plugged?into the Pi i received:

usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00

When it was not plugged in I received:

ls: cannot access '/dev/serial/by-id': No such file or directory


I did the same testing both with the dongle and without it.

Those tests were:

Radio on then boot up the Pi

Radio off, boot up the Pi then turn the radio on

Boot up the Pi without the UBS cable at all, turn on the radio and plug the USB into the Pi.


So all 6 scenarios resulted with no radio connection.


I don't currently have a Windows machine for the shack.

I will borrow one from my daughter and let you know how that test goes as well.


73,

Frank W4FRR



On Thu, Sep 15, 2022 at 2:13 PM Bill Dornbush <bill@...> wrote:
Do you have a Windows computer?? Try installing the drivers on Windows and see if you can see the device in Device Manager as one of the COM Ports.? Mine shows as "Silicon Labs CP210X USB to UART Bridge" and as two ports, COM5 and COM6 in my case.? I can tell that it is working by disconnecting the USB cable and seeing the ports go away, then returning when I reconnect the USB cable.? This should tell you that the IC-7100 USB connection is functioning.

--
--Bill AA6BD

 

On Thu, Sep 15, 2022 at 07:11 PM, Frank Roginski W4FRR wrote:
I performed the test that you asked me to do.
On the first try I forgot to unplug my GPS dongle from the Pi so ultimately I received?two answers.
When the GPS dongle was plugged?into the Pi i received:

usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00

When it was not plugged in I received:

ls: cannot access '/dev/serial/by-id': No such file or directory

?

I did the same testing both with the dongle and without it.

Those tests were:

Radio on then boot up the Pi

Radio off, boot up the Pi then turn the radio on

Boot up the Pi without the UBS cable at all, turn on the radio and plug the USB into the Pi.

?

So all 6 scenarios resulted with no radio connection.

?

I don't currently have a Windows machine for the shack.

I will borrow one from my daughter and let you know how that test goes as well.

?

73,

Frank W4FRR

Well shoot! I was hoping it would see the radio in one of those cases. This is a long shot but run:

cat /etc/default/gpsd

and let's take a look at your GPS configuration. Seems strange but I have seen this file for GPS interfere with Icom radios in the past. See if USBAUTO is set to true/false
USBAUTO="false"
If it is set to true, it could be creating the issue.
?
--
73, de KM4ACK
|
|

Frank Roginski W4FRR
 

Sorry for the delay in getting back to this, the day job got in the way.
Good news is that I believe that I figured it out by barrowing my daughters windows laptop and installing the drivers for the radio.

Bad news is that the radio needs to go back to Icom to have the USB port fixed.
The Windows laptop did not see the radio either.

Semi good news is that it is still under warranty.

Thanks for all the help.
73,
Frank W4FRR
 

Glad you got some resolution. Hate that it was a hardware issue instead of software.

--
73, de KM4ACK
|
|

1 - 15 of 15