¿ªÔÆÌåÓý

Re: New Setup issues


 

¿ªÔÆÌåÓý

Hi Cassie

A swag of notes/ideas.


Yes I agree something has gone wrong. Note there is a difference between rigctld and rigctl. For testing you would start;

rigctld -m 3068 -v -r /dev/icom9100a -s 19200 -c 0x7c

in one shell window, and

rigctl -m 2

in another


If the audio is getting to/from the PC it is unlikely to be a cable issue. If not then a temporary swap out may be in order. Also worth doing a few "sudo dmesg" commands whilst wriggling the cable ends to look for any intermittent connection or dirt.


Oh also check the installed version of hamlib. From memory the ID number for the IC9100 changed a few years ago. rigctl -l | grep 9100 should show something like;

3068 Icom IC-9100 20240726.5 Stable RIG_MODEL_IC9100


So going through the rig menus;

60. CI-V Baud Rate - 19200
61. CI-V Address - 7Ch
62. CI-V Transceive - Off
I don't know if below are important but as they affect port usage set to defaults.
63. USB2/DATA1 Func - [-----]/GPS)
64. USB2/DATA1 Func - [-----/[GPS ]) (I assume there is no GPS unit attached to the rig)

I guess it was possible that during the project evolution the CI-V address has been changed on one rig to allow them to talk to? each other. Hence the check.


Apart from ensuring the user is a member of dialout, the only other possibility is something else on the PC has grabbed either the USB or hamlib interface port for their own use. Most distros IME don't install the tools to check serial ports "in use" so difficult to suggest an action here. To check if the hamlib port has been seized try a different one or check using netstat;

rigctld -m 3068 -v -r /dev/icom9100a -s 19200 -t 4534 -c 0x7c
rigctl -m 2 -r localhost:4534

To check that 4532 may be in use;
sudo netstat -tulpn | grep 4532
and
sudo netstat -n |grep 4532
When the rigctld and rigctl commands are not active

Quite often a command will include a port specification, so using ps -axww | grep USB and? ps -axww | grep serial may show something

Also possible to check if rigctl/rigctld is a permissions issue by running as root with a preceding sudo. eg
sudo rigctld -m 3068 -v -r /dev/icom9100a -s 19200 -c 0x7c
sudo rigctl -m 2


Also look into a whole rig reset, if nothing important has been saved on them.


Cheers Bob


On 27/8/24 01:00, cdres wrote:

It's good to know I'm getting closer. again, you all are much appreciated.
?
So new window with rigctld -m2? and then f to get the freq yeilds:
thinking I may have been connected to the wrong USB, I tried with both, and both get the same message.
?
So, I'm not sure where it is going wrong. I saw a few people mention adding 5 v's for debug, but I wouldn't have any idea what to do with that information.
I keep thinking I have some kind of setting wrong on the rig, so I'm going to go through with a fine tooth comb and see if I can find an outlier.
?
_._,

Join [email protected] to automatically receive all group messages.