Hi All,
1. I use CQ-monitor everyday, but I am missing the information if caller is LoTW user (via additional color option on the right click).
2. IMHO the monitor could show not only CQ but also RR73, 73 strings (with the consequence that the utility's name becomes a bit wrong hihi)
Best 73 to everybody de Zilvis LY2SS
Hi Zilvis!
Yes LoTW information is missing. Would you like to work only LoTW users?
As soon as you answer to CQ you will see it from NewQSO as usual as the station information is there after your first transmit.
You get better information by checking "Map" in CQ monitor. When checked the window should be high and narrow like bandmap window. You have to adjust that for fist time.
From there you can see all band traffic. If that is too much you can check "Dx" and you see only stations from other continents than you.
There a plain line with call and locator is station calling CQ
If callsign and locator are in parentheses it means station is answering to someone else's CQ
If callsign is in parentheses without locator it is having qso with someone
If callsign is in parentheses where the closing one is replaced with asterisk station sends RR73 or 73 (ends his qso)
All this is color coded by the entries of your log against heard callsigns.
But sorry, LoTW, eQSL and club memberships are missing.
I use the Map mode almost every time as it tells so much information.
--
Saku
OH1KH
I am familiar with LoTW/etc membership on New QSO window but as you said - the information is provided only once CQ is answered.
It's not ok.
Maybe there are some 3rd party software - for this purpose, but why use it when cqrlog is _almost_ there.
So that's why I put that feature on wish list.
73!
OK Zilvis!
If you double click CQ calling callsign on CQ monitor, or in Map mode, yes the TX is fired and callbook information is fetch.
Second later you can put TX off and the caller never knows that you were answering.
If you double click callsign in parentheses (in map mode) the callbook information is fetch and WSJT messages populated but TX is not fired. That is nearly what you are looking for.
Getting eQSL/LoTW information for every call heard could be based on files in "~/.config/cqrlog/ctyfiles" but it can not be produced with internet callbook search. It is too slow.
Seeking every callsign from those files in every decode period is also too slow.
Maybe using same kind of idea that I have used with US states (in my test version) could work.
In other case LoTW/eQSL users should be put to database and let mysql do the search.
--
Saku
OH1KH
Time flies....
Saku, maybe it would be more reasonable to compare call against contents of the fetched in advance (f.e. once per month, or manually like it is done in wsjtx) to the disk/memory file from https://lotw.arrl.org/lotw-user-activity.csv instead of querying them every time call is decoded.
Hi Zilvis!
If you look at ~/.config/cqrlog/ctryfiles folder you see that there are two files eqsl.txt and lotw1.txt holding all callsigns of users.
There are ready subroutines UsesLotw(call) and UsesEqsl(call) that are used in RBNmonitor using those files.
So it is not very big thing to use them, but redesign of CQ-monitor, adding grid for that, is bigger job.
Perhaps addling letters L,E,and LE in beginning of last field
I.E.:
L:AS:New mode country!!
E:AS:New mode country!!
LE:AS:New mode country!!
Maybe also "show lotw/eqsl users " checkbox in preferences/fldigi/wasjt interface should be added.
What do you think?
--
Saku
OH1KH
IMHO I think this would be fine.
BTW: I checked the directory you've mentioned:
2023 Feb 20 19:55 lotw1.txt which contains 184455 calls
While the latest file as of 5th May contains 188018 calls
And I checked lotw1.txt from cqrlog github site:
May 1 2022 134350 calls
So there's a need to update that file somehow too?
Hi!
Both files in my system are 2023-05-04 and I have not manually updated them.
If you have DXCC and QSL manager auto updates on I think they are coming via that. (have not checked the source)
L, E in CQ-monitor has been in my Alpha version since 2.6.0(113) (now (115) compiled, (116) source are available)
--
Saku
OH1KH
Hi Saku!
You are right - once I clicked DXCC/QSL manager update, the lotw1.txt file updated.
I upgraded to 116 version but can't find how to make L, E labeling in CQ-monitor to work.
I attached my view. What did I miss to click?
File:
It was there, just hidden below other items.
Fixed now in 116 source code.
--
Saku
OH1KH
Hi!
Ooops!
preferences/fldigi-wsjtx seems to be broken in 116.
There should be checkbox "Show LoTW, eQSL usage in CQ-monitor" by help.
As I have set it once I have it in my configuration and do not notice it is missing from preferences.
I'll fix that soon as time permits.
--
Saku
OH1KH
Hi Saku!
It's working! THANK you very much! I don't have experience to compare to other logging suites (there are too few for linux) but I find it useful time saving feature!