Rig model shows blank - what I missed ?
I today use 2023-04-24(116) by zipped archive.
Before I gitted clone and installed, but in RTX control panel rig model combobox shows blank.
I re-installed hamlib4 and mariadb just to be sure, with Synaptic.
CQRlog, of cource could not run JTDX by clicking "remote mode for wsjt".
JTDX runs, then it seems to normal, and clicked callsign will be shown in call sign box with gray color.
I feel some unconfortable.
On the official 2022-07-01(001) worked correctly.
OS Ubuntu 22.04.2
Thanks in advance, Waka, JE8VZK
Hi Waka!
If you have moved to (116) from official version you have to check preferences: Trxcontrol, Mode and CWinterface
That is because Alpha version has support for more than two rigs and when moving from official version it cannot directly read those settings (there is no conversion routine, it has to be done manually).
Reinstalling Hamlib and MariaDB is not needed.
RIg models do not show up if the "path for rigctld binary" at preferences/trxcontrol is not valid. Check spelling of that and use "whereis" command in command terminal to check where your rigctld actually is.
whereis -b rigctld
Combobox may look blank at beginning but when you click down arrow right end of combobox the rig list opens.
There is no official support of JTDX (I do not test with JTDX).
If you put path and filename of jtdx to "preferences/fldigi/wsjtx interface/Path to wsjtx" and check the checkbox "Run wsjtx after entering to remote mode for wsjt-x" it will start JTDX as well as it starts wsjtx.
I tested that now with (116) and JTDX v2.1.0-rc151
Also qso remote logging if "prompt me to log qso" checked at jtdx works with wsjtx-remote
Same as qso initiate when double click callsign at CQ-monitor or Map mode (tested that too). That needs jtdx/settings/reporting/Accept UDP requests. Also the two other checkboxes are good to keep checked.
What does not work with jtdx is that when you double click Map mode's callsign line that has parentheses. When wsjtx is used it initiates callsign to wsjtx, but not jtdx.
Also multicast UDP address works with jtdx (tested that too). Multicast with Cqrlog must have ip address that starts with "239."
So quite many things work also with jtdx.
I do run same 2.6.0(116) 2023-04-24 Alpha version from source code as you.
--
Saku
OH1KH
Yeah, Saku, kiitoksia paljon.
In my Ubuntu there exist 3 "rigctld".
And only "usr/bin/rigctld" did not work.
Any one will work, I supposed.
I have fallen into the dilemma of "/usr/bin/rigctld" as default.
Other rigctld are /usr/local/bin/rigctld and /usr/local/bin/rigctld-jtdx.
I use now /usr/local/bin/rigctld and CQRlog works very well.
I say thanks again.
Waka JE8VZK
HI Waka-san!
Nice to hear!
The reason that your /usr/bin/rigctld does not work is that your /usr/local/bin/rigctld is probably the one that has been installed (by system update, or self compile?) latest.
Hamlib has also libraries (libhamlib.so) in addition of rigctld and the library must fit to rigctld in use. Otherwise it does not start, or may do some mysterious functions time to time.
So it is very important to remove parts that do not work any more due wrong library routines.
Unfortunately a while ago Ubntu delivered a system update that did update Hamlib to /usr/local/bin and leave the old ones in /usr/bin .
This happens also when user compiles Hamlib with default root path, that is /usr/local/ and does not remove the package installed Hamlib that liuses /usr/ ar root path:
When doing compile this root path can be changed from /usr/local to /usr and then the install of compiled Hamlib does override package installed Hamlib.
Until next system update, where system update thinks there is still the old version and updates that. And that update may be older that the version user has self compiled and installed. So there are rabbit holes when using package and compile installed versions mixed.
--
Saku
OH1KH
Hi Saku, kiitoksia paljon for info.
Is it better to mv /usr/local/bin/rigctl and more /usr/bin/. ?
rigctl, rigctld, rigctlcom, rigmem rigsmetr, rigswr, rotctl and rotctld,
these are also in /usr/local/bin/ .
HI Waka-San
No. I would rather test those in /usr/bin to be sure they do not work (as it seems to be) and then remove them.
Before removing you could reset execute bit and see if any your Ham programs stop work.
chmod a-x /usr/bin/rigctld (and others)
Then if something stops to work you can change it's settings to point /usr/local/bin and test it works then (like with Cqrlog). After all works you can safely remove ones in /usr/bin or leave them as is with execute bit off.
--
Saku
OH1KH
>if any your Ham programs stop work.
I now use only JTDX and CQRlog.
I plan to use wfview, now not work normally maybe for plural rigctld, only installed.
How to reset execute bit in particular ?
Hi Waka!
As said the execute bit can be changed using command terminal:
chmod a-x filename
Type
man chmod
to see more information.
With file manager it depends of the file manger used. Usually right click on filename, then select "file properties" and then "rights" / "execute"
When execute bit is reset you cannot start the program file any more.
--
Saku
OH1KH