Hi,

if you move a longer bandmap with the scrollbar to the beginning of the band or an upper Band segment, the bandmap stays in this position.

If a call is now selected, the bandmap jumps back to the end of the band.

From my point of view it would be better if the bandmap would remain in the once selected position (band start or band section), because otherwise you have to move the bandmap up again and again, if you want to select after an QSO several calls from the selected area one after the other.

73, Wolfgang
DL2KI

When i work QO-100 and make a spot, i check "Use RX frequency for DX spots"
I set the RX freq to 10489.500 MHz. but the spot that is uploaded appears as "489000KHz"

I found a bug in CQRLOG. It's probably not common but here it goes:
In 1995 I lived in El Salvador and I was YS1ZV. My US Call is WC4H and my CQRLOG db is only for WC4H.

Forward to today:
I downloaded the LoTW confirmations (for WC4H) and received the message that 2 QSOs were not in my log but were in LoTW.

The two QSOs were in 1995 so I was very suspicious.

I went to LoTW and saw that the 2 QSOs were for YS1ZV and were indeed confirmed on the date the error message said.

Using the following configuration:

CQRLog Version: CQRLog 2.5.2(001) 2021-09-19
Hamlib Version: rigctl Hamlib 4.4~git Thu Nov 11 23:10:57 2021 +0000 SHA=8b5685
Rig: Yaesu FTDX-101D

Using the following command string to start rigctld:
/usr/local/bin/rigctld -m 1040 -r /dev/$ftdx -s 38400 --set-conf=dtr_state=OFF &

Hello,

If eQSL qso has a Time_on = 0000,
t_eQSL_min = t_eQSL_max = 01:00:00

so the eQsl is not imported.

Debug trace :
Call: G4xxx
Band: 40M
Mode: CW
Submode:
QSO_date: 20050826
Time_on: 0000
QSLR:
------------------------------------------------
select id_cqrlog_main,eqsl_qsl_rcvd,time_on from cqrlog_main where (qsodate ='2005-08-26') and ((mode = 'CW') or (mode = '')) and (band = '40M') and (callsign = 'G4xxx')

Hello,

Is there a solution to avoid importing field like locator from LoTW ?
For example, I would like to keep locator empty field (or with existing data), but not replaced by value coming from LoTW.

I don't see (in source files) the rule of which fields are replaced or not from import.

Thanks a lot,

73's

Herve F8EHJ

Is it just me or has anyone else noticed that after the last update, see Wish List-Skipping Data Fields, the cursor does not return to the call input field after a contact is logged?

ins not posible to install on mint 20.3 una ?
gretings marcelo notenboom pa1mar

Wonder if another option could be made available 0ther than hamqth and QRZ? I am finding information on hamqth is outdated and QRZ doesn't provide all the data since I do not pay them for it.
Other options? Not sure what is out there. I was researching buckmaster and free account looks like it would fill the qth information fields and it lists many log programs as using their site. Of course those are all windows log programs. Not that familiar with other log programs and options they are using.

73
Jon

When exporting the EDI file there are sometimes a minor error in the distance calculation. The reason is that the function used do a round of the QRB calculation.

According to IARU-R1 VHF Handbook chapter 5.9.1, page 165, "For the amateur bands up to 10 GHz inclusive, points will be scored on the basis of one point per kilometre, i.e. the calculated distance in kilometres will be truncated to an integer value and 1 km will be added."

Wonder if anyone is using the new SDR++ software yet along with rig control.
The setup I was using with Cubic SDR that K4VBB came up with doesn't seem to work with this software.
What I found was rigctrld cannot be running or SDR++ won't connect to it. It wants to start the server.

Letting it start the server I then can connect to CQRLog but now SDR++ is acting as the radio. My actual radio (Ten Tec Orion) is now out of the loop and I can't find a way to get it back in the loop.