Wfview 2.03 IC7300 cannot connect under linux Mint 22

Usage Questions
1

I uninstalled the package for wfview 1.64 from linux mint 22. it had worked perfectly. I installed wfview 2.03 using the script on the download page. I did not see any errors during the install but now I cannot connect. Checked the Icom 7300 settings on the radio and they are what is recommended. I can use wfview 2.03 on this same computer dual booting into windows 11. It appears when I use lsusb that the Silicone Labs diver is loaded as “Bus 001 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge”.
I have tried connecting using auto, /dev/ttyUSB0 and 1 but no success. Here is the log file link https://termbin.com/wtci

2

you probably don’t reference the right serial port. what /dev/ttyUSBx ports do you see?

also di you use udev rules for the rig?

3 
ls -l /dev/ttyUSB*
4

ls -l /dev/ttyUSB* responds with:
crw-rw---- 1 root dialout 188, 0 Jan 30 09:55 /dev/ttyUSB0

5

I have not yet created any udev rules as I did not need them for the previous version of wfview.

6

…and I did try to add my user to the dialout group, the response was that my username was already a part of that group.

7

Just for grins, try owning the device:

sudo chown USERNAME /dev/ttyUSB0

(replace USERNAME with your username)

If that works, then we’re on track.

–E
de W6EL

8

That was successful! What could cause that?

9

Well, it is a permissions issue.

I have no idea why or how it worked for you in the past, but I can say that wfview of any version cannot open a port it doesn’t have permission to open.

You can mess with udev to put in a rule to always own the port to your username. Personally I do this:

eliggett@genesis:/etc/udev/rules.d$ cat 10-serialports.rules
KERNEL=="ttyUSB[0-9]*",MODE="0660", OWNER="eliggett"
KERNEL=="ttyS[0-9]*",MODE="0660", OWNER="eliggett"

As you see, that file (created as the root user of courser) causes ANY serial port to be owned by my username (eliggett). You can create a similar one if you replace eliggett with your username and then reboot (or reload and retrigger udev if you know how to do that).

–E
de W6EL

1 Like
10

Thanks for your support Elliot. I was suspicious of the way that the package manager removed the previous version but I guess we will never know for sure. Just happy that this issue has been resolved.