TS 570D HamLib 4.3.1 Response

3 posts / 0 new
Last post
TS 570D HamLib 4.3.1 Response


For 2 days I have been trying to reply. I can upload as a new topic but not as a reply.
All seems fine, I enter the text, click to say I am not a robot and then click upload.
Timer appears, no errors but the timer disappears far too fast and my reply is not uploaded.

This is a reply to TS 570D HamLib 4.3.1

Thanks for all the replies. Here is where I have got to.
I still have the original problem but I am at least starting to track the problem down.

my user name is djcleckie on my Linux (Ubuntu 22.04 box)

djcleckie@NDS-8:~$ ls /dev/ttyUSB*

That seems OK so I removed the lead and /dev/ttyUSB0 disappeared
Tried a different USB port and /dev/ttyUSB1 appeared.
Tried that no success so back to original USB Port USB0

djcleckie@NDS-8:~$ ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Jul 14 10:20 /dev/ttyUSB0

djcleckie@NDS-8:~$ sudo groups djcleckie
[sudo] password for djcleckie: Trying
Connected to localhost.

djcleckie : djcleckie adm dialout cdrom sudo dip plugdev lpadmin sambashare

That seems to be OK. djcleckie is a member of dialout group

Next I tried the settings suggested by Dave N1KX.
Changed menu 35 on the TS 570 to 576-1
Then entered the N1KX suggested settings.

Still no communication between TS 570 and Linux computer when running CQRLog.

Back to OH1KH 2nd email.

Tried this

djcleckie@NDS-8:~$ ps ax | grep rig
743 ? Ss 0:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
5566 pts/0 S+ 0:00 grep --color=auto rig

Now this does not seem correct?

So I tried
djcleckie@NDS-8:~$ telnet localhost 4532
telnet: Unable to connect to remote host: Connection refused

Now we are getting somewhere.

tried ping worked fine
tried ping local host worked fine so TCP/IP seems fine.

tried the standard telnet port
djcleckie@NDS-8:~$ telnet localhost 22
Connected to localhost.

so that's working

So I now need to have a "good think" and ask for any advice.



TS 570D HamLib 4.3.1 Response

Hi Dave!
If you do not see "rigctld" and your Cqrlog is running when issuing "ps ax | grep rig" it means that Cqrlog has failed to start rigctld.

Then open Cqrlog, preferences and select TRXControl. At bottom of tab there is checkbox " show communication with trx in console". Check that.
Close Cqrlog and open command terminal. Type command
Now you shoud see if rigctld starts and how it polls rig when Cqrlog starts and runs.

If rigctld fails check preferences/trxcontrol that path to rigctld is valid.
Let us know what happens.

To know rigctld path use command
Whereis -b rigctld
You should see only one path. If there is two then you have either compiled Hamlib with default path /usr/local and have a package installed Hamlib in path /usr . Same may have happen with faulty update of one Ubuntu, it also duplicates Hamlib. There may be only one, otherwise the library part of Hamlib is ok ony to other rigctld.

If you find only one you can make simple test with two command consoles.
#1) command
rigctld -m1 -vvvvv
That starts dummy rig in 1st console with full debug. If you know parameters for your rig you can try next with them instead of "-m1"
You can also put same full path in front of rigctld that is used in preferences trxcontrol to test that full path is ok.

#2) command
telnet localhost 4532
While rigctld is still running at 1st console you should get conneted to it with telnet. Then give f (enter) and you should see frequency of default rig 145MHz
You can use also instead of "localhost"

One hint more for device.
Instead of using /dev/ttyUSB0 you can use long path. Yiu can put it to preferences trxcontrol device, the box will scroll with longer device names.

Find /dev/serial/by-id folder with console or file manager.
In that folder you shouls see a filename when serial lead is connected. Name disppears when you disconnect lead. Just like ttyUSB0.
When you put path /dev/serial/by-id/ and the filename together you get device name.
Benefit is that this device name is always same. No matter what socket you use for lead. Name does not change like ttyUSB0 changes to ttyUSlB1 etc.


TS 570D HamLib 4.3.1 Response

Sorry for typos.
"Whereis -b" is fatal
There should not be caps.
'whereis -b" is ok