Ubuntu 18.04
CQRLOG 2.3.0 (001)
WSJT-X 2.0.0-rc2
The good news: Everything seems to work with the new WSJT-X v2.0.0-rc2 except one thing.
The bad news: I can no longer click on a callsign in the "Wsjt-x CQ-Monitor" window and have it automatically populate WSJT-X and start transmitting like it did with the previous version of WSJT-X (1.9.1).
All the settings are identical between using the two different versions.
-David, N9KT
Confirming this, but let's wait, Saku may not have taken this RC canditates
in use yet.
<p>Jarmo</p>
Hi,
i am using cqrlog Version 2.3.0 (104) and also testing it with 2.3.0 (103) and the behavior is like before.
doubleclick in wsjtx cq monitor start transmission in wsjtx with the selected callsign.
wsjtx is version 2.0.0 rc2
Maybe you should update to the newest developer version from cqrlog.
I checked the release notes from the last develop versions, but there are no changes to this topic mentioned.
http://www.saunalahti.fi/sakny/bin/cqrlog2/
Bye Andreas, DL7OAP
please verifiy that this option is enabled (extract from documentation of wsjt-x cq monitor):
Yes they are ok, I have been probably first one, using cq-window with wsjtx/cqrlog.
Been betatester for Saku, so this kind of errors are out of qestion :)
Worked with wsjtx 1.9.2 beta, self compiled, as well as 1.9.1 version.
Discussed with Saku of this and he's going to look it, but does nothing, before
GA version of wsjtx.
<p>Jarmo</p>
I have latest all and does not work. Yes I know Sakus site, he lives very near
me :)
Using Fedora 28 and wsjtx 2.0.0-rc2 installed from rpm package...
<p>Jarmo</p>
Hi,
i have, too, since 2017 the freshest nightly buildes here from Saku. (Developer 103 and since today Version 104) and with Ubuntu 18.04 cqrlog 2.0.3 (104) is working without problems here with wsjtx 2.0 rc2.
i just using it on 20m and 40 with FT8 :-)
i think, the have to check if they lost the udp option during the update of wsjtx.
or maybe it dependents from the used linux distribution?
Bye Andreas (dl7oap)
As there in wsjtx-devel list, they have noticed same problem with jtalert.
solution for now, is disable wsjtx settings---general---Show dxcc,grid and
worked before status.
I disable that and now I can double-click station from cq-monitor window.
<p>Jarmo</p>
ok, that will explain why it works for me.
because i use the build in dxcc, grid and worked before features of the wsjtx-cq-monitor i never enabled this option in wsjt-x.
my adi log file in wsjtx is not complete so wsjt-x is for me only the "ft8 signal generation plugin".
73 de dl7oap
Hi,
i have, too, since 2017 the freshest nightly buildes here from Saku. (Developer 103 and since today Version 104) and with Ubuntu 18.04 cqrlog 2.0.3 (104) is working without problems here with wsjtx 2.0 rc2.
i just using it on 20m and 40 with FT8 :-)
i think, the have to check if they lost the udp option during the update of wsjtx.
or maybe it dependents from the used linux distribution?
Bye Andreas (dl7oap)
Tested wsjtx rc2 today.
Strange:
At first run I was able to initiate qso from CQ monitor 2 times. Not after that, ever !!
When using Wsjtx Map:
- Clicking a call that calls CQ, does nothing, ever. I.E. UDP request to initiate qso is going to bit heaven. Should initiate qso as in v1.x.x
- Clicking a callsign "in qso" does load his call to std messages, but not fire the TX. That is what should happen, and has been so with 1.9.x
But very strange thing is that *sometimes* clicking a callsign "in qso" loads his call to std messages and fires TX!
It seems somehow to be related in callsign as when you find a call that fires TX that way it will fire TX also on second decode period and so on.
- Colorback UDP requests seems to work as they did in v1.9.x
I have sent a question about this UDP request behavior. It might that it is OFF in purpose, or there are still bugs in that part of rc2.
It is best to wait now for full version before doing anything to cqrlog.
--
Saku
OH1KH
Ubuntu 18.10
CQRLOG V2.3.0 (001)
WSJT-X v2.0.0-rc3
WSJT-X RC3 works once again with clicking in the CQ-monitor!