Hi
I use Cqrlog & JTDX (or sometimes WSJTX). I prefer JTDX because decodes much more contacts.
I installed GridTracker but I can not manage to get them working. Ports seem to be properly configured (127.0.0.1:2237, same on JTDX and GridTracker but nothing happens on GridTracker).
I use ufw as firewall and I also tried with the fireall disabled, with no result.
Any help, please?
Regards
Hi!
Tried to find some information about GridTracker but most of manual pages seems to be empty (?!?).
I think most of its duty can be reach with combination of cqrlog's CQ monitor (displays worked/unworked Grids and does alerts) and Pskreporter web page (displays activity of own station rx and tx and also public activity by bands).
I think the problem exists with UDP port sharing.
If you like to use cqrlog's wsjt-x remote with WSJT-X or JTDX and another program that needs UDP messages from those you have to use multicast UDP addressing.
Otherwise cqrlog or the other program (ex. GridTracker) will "eat" all UDP frames depending what program is started first.
Using multicast UDP removes this problem. You have to use multicast IP address for all, wsjtx/jtdx + cqrlog + other program. For example 239.255.0.0.
How ever if you have from package installed cqrlog it does not usually support UDP multicast (package is too old), you must compile newer version from current GitHub source.
Easy way to check multicast support is to look at cqrlog help: "NewQSO/Help/Help index/Quick start/wsjt-x interface" if you find there a chapter that talks about multicast then cqrlog supports it.
Of course your other program (ex. GridTracker) must also support UDP multicast.
--
Saku
OH1KH
Hi,
for now I have solved it like this.
1. wsjt-x is set default to "Accept UDP requests" localhost port 2237
2. Gridtacker is set to "forward UDP" localhost 2238
3. cqrlog set to "wsjt port:" localhost port 2238
wsjt -> Gridtracker -> cqrlog
I have not tested Gridtracker multicast.
I hope I understood the problem and this helps.
73
/T
Hi !
Thanks for telling this feature of GridTracker!
If cqrlog is older that current source version there is no multicast support and this "relaying" of UDP frames via GridTracker is a good solution.
It would be nice to know is this relaying working for two directions?
If not, in that case user is not able to initiate new qso from cqrlog/Cq-monitor by double clicking a decoded callsign line.
Also other similar things, like stop TX if someone else gets qso with called station or "colorback" to wsjt-x display by cqrlog's worked qsos, do not work then.
--
Saku
OH1KH
Hi Saku!
I'm fairly new to cqrlog, could yo describe how to try the "other direction" this by an example or a reference?
73
/T
Hi!
"Other direction" is that cqrlog can command wsjt-x (jtdx).
You need at least "accept UDP requests" in wxjt-x settings.
Then in cqrlog select NewQSO/file/remote for wsjt. If CQ-monitor window is not open open it from NewQSO/Window/WSJTX monitor. You can not see this selection unless "remote for wsjt" is active.
Now when wsjt-x(jtdx) will decode a period you will see all CQs in CQ-monitor colored by your log information (right click on CQ-monitor opens color settings).
When you see a wanted station calling CQ you can double left click on that line on CQ-monitor. That will start wsjt-x calling that station. That needs the UDP frame going to reverse direction from cqrlog to wsjtx.
Other example: When CQ-monitor is open check the Map checkbox. CQ monior will turn to map mode where all decoded messages are colored by your log information. At the botton of window there is ColorBackCQs if that is checked cqrlog will send the same color information to wsjtx so that all CQ lines at "Band activity" window of wsjtx are colored same way as in CQ-monitor. This also needs the UDP frames going to reverse direction.
More about these things:
NewQSO/(top menu left)Help/Help index opens help file to web browser.
There Operation/digital modes: wsjt-x will tell more about these things.
--
Saku
OH1KH
It worked!!! Thanks