38/5000 I have a problem with cqrlog support with wsjtx

18 posts / 0 new
Last post
sp5smy
sp5smy's picture
38/5000 I have a problem with cqrlog support with wsjtx

Dear friends! I'm in the CQRLOG configuration stage. I have a problem with cqrlog Support wsjtx. Both versions of the latest software. Problem with CAT cable. For Ubuntu 16.04. I GIVEN SET OF SCREEN brochure for both programs. Cqrlog works well with the latest Fldigi. Please help. Paul SP5SMYY

CQRLOG

 

sp5smy
sp5smy's picture
<p>Dear friends! I'm in the

<p>Dear friends! I'm in the CQRLOG configuration stage. I have a
problem with cqrlog Support wsjtx. Both versions of the latest
software. Problem with CAT cable. For Ubuntu 16.04. I GIVEN SET OF
SCREEN brochure for both programs. Cqrlog works well with the latest
Fldigi. Please help. Paul SP5SMY</p>
<table
 style="width: 100px; text-align: left; margin-left: auto; margin-right: auto;"
 border="0" cellpadding="0" cellspacing="0">
  <tbody>
    <tr>
      <td style="font-weight: bold;">
      <p><span
 style="letter-spacing: 0.266667px; word-spacing: 1.46667px;"><span><span><span><span>CQRLOG</span></span></span></span></span><span
 style="letter-spacing: 0.266667px; word-spacing: 1.46667px;">&nbsp;</span></p>
      </td>
      <td><span><span>&nbsp;<span><span><span><span><span
 style="font-weight: bold;">WSJTX</span>&nbsp;</span></span></span></span></span></span></td>
    </tr>
    <tr>
      <td><span><span><img
 src="http://pawel.sp5smy.cba.pl/pki/1.png" alt=""
 height="547" width="800"></span></span></td>
      <td>
      <p><span><span><img
 style="width: 764px; height: 543px;"
 src="http://pawel.sp5smy.cba.pl/pki/2.png" alt=""></span></span></p>
      </td>
    </tr>
  </tbody>
</table>
<p><span
 style="letter-spacing: 0.266667px; word-spacing: 1.46667px;"><span><span><span><span></span></span></span></span></span><span
 style="letter-spacing: 0.266667px; word-spacing: 1.46667px;"></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span><span><span><span><span></span></span></span></span></span></span></p>
<p><span><span></span></span></p>

oh1mrr
If you set rigctl in CQRlog,

If you set rigctl in CQRlog, and run wsjtx remote from there, you MUST NOT set rigctl same time in WSJT.
In wsjt you set RADIO NONE.
Depens, what interface you have, most of them, ptt works with RTS, so in ptt section you set /dev/tty what you find
and RTS. It "should" work... And ofcourse in radio menu right settings...

Jarmo

oh1kh
38/5000 I have a problem with cqrlog support with wsjtx

Hi!
Once you have cqrlog working with your rig you can not use same serial port again on other program.
Cqrlog runs 'rigctld' on background and that daemon can serve several programs at same time with same rig on same serial port.

So instead setting wsjtx with same settings as cqrlog you should use "Hamlib NET rigctl" with wsjtx.
Then you can control your rig with wsjtx while also cqrlog is using same rig.

Other option is use rig "none" at wsjtx as Jarmo said, but I think this is not what you want.

--
73 Saku
OH1KH

File: 

--
Saku
OH1KH

sp5smy
sp5smy's picture
re: I have a problem with cqrlog support with wsjtx

Welcome. Wsjtx you sent me on the forum wsjtx does not want to work with CAT cable.
In attachment print scrin
Pawel SP5SMY

File: 

oh1kh
Cat

Understood that your cqrlog works with rig as expected.
Then after starting first cqrlog start wsjtx after that. It should now work also.

With "hamlib net rigcrld" used at wsjtx it requires that cqrlog is started before wsjtx because cqrlog starts the needed rigctld program on background.
Same way you can set fldigi to use net rigctld but also then cqrlog must run before fldigi. And this is the right way as fldigi seems to work together with cqrlog when both uses /dev/ttyUSBx but sooner or later there will be serial port conflict.

If your cqrlog does not work with your rig even alone then you have another problem. But as said I assume cqrlog alone works ok.

Saku
Oh1kh

--
Saku
OH1KH

sp5smy
sp5smy's picture
I run it this way. First,

I run it this way. First, CQRLOG files> Remote mode wsjtx And I get this wsjtx error.

oh1kh
cat

First change "localhost" to "127.0.0.1" at cqrlog/preferences/radio 1. Localhost sometimes does mysterious things if you have IPv6 enabled.

Then confirm that cqrlog shows your rig frequency and changes it when you turn vfo knob.

If that is OK start wsjtx and co to settigs/radio. See that "Hamlib NET rigctld" is selected and press "test cat". Should turn green.

If not open terminal and type telnet 127.0.0.1 4532 (enter). If you have telnet installed you should see similar as my picture shows. Type f enter and you should get rig's frequency.

If you get it ok. But wsjtx does not work then
Remove wsjtx installation and after it check that folder /home/saku/.local/share/WSJT-X is removed. If not delete it.
NOTE instead of "saku" at path you should see your username.

After deleteing install latest wsjtx again and do settings again.

Should work!

Try also settings of fldigi. See my picture how to do setup. You can run it same time with all other programs if you just start cqrlog as first program.

If cqrlog works all others should work, too

File: 

--
Saku
OH1KH

oh1kh
cat

This is the idea of system

File: 

--
Saku
OH1KH

sp5smy
sp5smy's picture
re:CQRLOG and WSJTX

Connected telnet
pawel@pawel-System-Product-Name:~$ telnet 127.0.0.1 4532
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
f
14230050

rigctld=radio QSL OK

sp5smy
sp5smy's picture
re: I have a problem with cqrlog support with wsjtx

wsjtx 1.7 64bit web page autors https://www.cqrlog.com/comment/reply/1797

Are these settings ok? In attached file.

File: 

sp5smy
sp5smy's picture
re: I have a problem with cqrlog support with wsjtx

I did as you wrote. I have uninstalled wsjtx a new version from the author. I deleted the entries in /home/pawel/.local/share/wsjtx. I installed a new version. And when I run from the console, I still do not want to mess around
Pawel @ pawel-System-Product-Name: ~ $ wsjtx
17-05-04T14: 19: 08.134Z: Hamlib: Failed to connect to 127.0.0.1:4532

oh1kh
cat

Hi!
I lost 2 times a long answer that I typed there.
3rd time, now typing only shortly.

Try to remove autostarting of wsjtx (and fldigi) from cqrlog setup. I do not use them. If cqrlog dies it pulls down child processes with it. If started separately you can continue qso even when cqrlog suddenly dies.

Start wsjtx manually after cqrlog is runnig. Does it help?

As your telnet works I am confused.

Try to open 2 terminals. First start "rigctld -m 1" second start "telnet 127.0.0.1 4532" (see picture)
give "f" answer of dummy rig is 145MHz.
Then start wsjtx.
Should show 145MHz, too
Telnet type F14076000(enter) should change wsjtx to 20m(14.076MHz)

If this does not work at wsjtx settings/radio set "Network server" to 127.0.0.1 this should work as empty, but with IPnumber it works as well(I tested) and perhps solves your problem.

When you change wsjtx "rig" or "network server" close settings and restart wsjtx. I noticed that many changes for these parameters halts wsjtx and latest setting starts to work only after program restart.

--
Saku
OH1KH

File: 

--
Saku
OH1KH

oh1kh
cat

Good morning.
Just came in to my mind that normally wsjtx install installs also the very latest fixes of hamlib.
You should have "rigctld-wsjtx" also in /usr/bin.

You could also try to use /usr/bin/rigctld-wsjtx instead of /usr/bin/rigctld in cqrlog config and see if that changes something.

--
Saku
OH1KH

--
Saku
OH1KH

oh1kh
cat

Next thing coming in to my mind is:

At cqrlog settings drop poll rate from 500 to 1500 and wsjt-x set poll 2s. Your serial line is bit slow (4800) and many polls may overload rigctld's serial requests.

Finally, if nothing else works remove selection "run rigctld at cqrlog start". Before that, when cqrlog is still running and shows rig frequency, open terminal and type
ps ax | grep rig
You should see rigctld process with all used parametes. Write them down (copy to clipboard).

Then close cqrlog with unset "run rigctld at cqrlog start" setting.

At terminal start manually rigctld with parameters copied (paste) but insert one new parameter to start
rigctld -vvvvv (then rest of correct parameters for your rig).
Then start cqrlog and after that start wsjt-x.

You should now see all debugging information what happens with rigctld from terminal window.
If wsjt-x gives hamlib I/O error what comes to terminal ?

--
Saku
OH1KH

sp5smy
sp5smy's picture
re: I have a problem with cqrlog support with wsjtx

Dear friends, there is some progress with wsjtx. It already matches the configuration with hamlib. Wsjtx probably does not start "rigctld" and therefore did not want to run the configuration. Just like the console sake pise, everything is ok.
Pawel @ pawel-System-Product-Name: ~ $ telnet 127.0.0.1 4532
Trying 127.0.0.1 ...
Connected to 127.0.0.1.
Escape character is '^]'.
f
145000000
F
14076000
The frequency in wsjtx is changing and I am very happy here
If it were not for the radio to be on a different frequency. Than that which gives the command f
Saku great thanks;)

File: 

sp5smy
sp5smy's picture
re: I have a problem with cqrlog support with wsjtx

oh1kh
Nice to see that you have

Nice to see that you have some progress.

As I notice you are active with fldigi you could try my latest release that is not yet taken to official beta.
Look at this message https://www.cqrlog.com/node/1792

I think you like to see your fldigi qso partners information right before qso even starts.
It also has WSJT-X CQ-monitor so you can easy pick up missing DXCCs and locators.

- -
Saku
OH1KH

--
Saku
OH1KH