I tried a filter to see what I could come up with on the DXCC entities I've worked and sent a QSL to but haven't received one back. With the goal being to re-work the ones I need in order to get closer to making Challenge.
What column/field in cqrlog_main is dxcc_ref? I tried this from the SQL console and it fails since there is no column/field named dxcc_ref
select qsodate,time_on,callsign,band, dxcc_ref, lotw_qsls, lotw_qslr from cqrlog_main where lotw_qslr=""
Since last upgrade to 2.3.0(100) on Linux Mint 18.
On launch, I get an error report Q: Field not Found "RXFreq".
On exit I get an error report ...Database upgrade crashed with this error:
TMySQL57Connection : Error executing query: Duplicate column name 'rxfreq'
Was all working fine before the upgrade.
regards Wallace
same error as on raspbian.
in rasbian deleting the file called lotw solves the problem ( until cqrlog creates that map again )....
sadly in debian 8 it looks that cqrlog on startup first recreates the map i delete and then servers me the same error again...
seems this software is all but happy to run on more than one linux distro.
if it stays as unstable i guess i will be better using a maybe not that complete software that is multiplatform ready or at least is willing to run decent on debian as i am no hero with linux and shure not a programmer.
How do I check to see if MySQL server is properly installed? I get a "Database Problem" error asking me to check if MySQL is installed properly.
I have pasted the last 20+ lines of my myqsl.err file as well.
Thanks in advance for any help!
Harm - VE4HAZ
I am using Slackware64-Current. I tried to compile carlog, 2.3.0, &, even though I had all the listed dependencies, the make died very quickly. I then repackaged your binary into a Slackware package & it seemed to work fine. But when I used it in remote mode for wsjtx, & it imported a contact, a window appeared announcing that the date was not formatted correctly. When I pressed the OK button in the warning window, the contact was erased from cqrlog, without giving the opportunity to fix the date. Packaging 2.2.0 & "upgrading" 2.3.0 with it solved the problem.
Hi,
up to version 2.1.0 everything worked fine. Since version 2.2.0 I always get a "crash" if I use the "page down" key to
"jump" to the last 1000 QSOs (2nd page). A little empty window appears in the middle of the screen and I can't do
anything except "killing" cqrlog.
If someone has an idea...
vy 73
Olaf, DL4DZ
Hello everyone.
I tried to update version 2.3 on 2.1 my raspberry pi 2B but the result has been catastrophic.
When trying to reinstall version 2.1, I no longer recognize the database or allow me to start the program.
Does anyone have a solution?
cqrlog --debug=1
**** DEBUG LEVEL 1 ****
SSL libraries:
HI!
Just noticed that Window/QSO list/Filter/SQL console has again double key syndrome.
Every keypress produces 2 characters to console: hheellpp!!
At least when cqrlog is run with Fedora 28/LXDE
Quickly tested some other inputs, but did not find any other place than SQL console with this bug.
This is not the first time and playing with "input mode selector" and Ibus solved this last time. Now I just have to dig out what was done at that time.
Any other distro having same issue?
I would like to make a new log that covers just this month, June. So this is what I did.
I'm seeing QSL needed in the WSJT-X CQ monitor and I have that band worked and confirmed on LoTW for the DXCC country. So I wondered what logic is use to determine a QSL is needed? I have "include LoTW and eQSL confirmed countries in DXCC" and "use LoTW and eQSL confirmed countries for new country or new band country etc info" checked.
I'm running what I think is the latest version of CQRLOG that I built from source. But it shows version 2.2.0 as the version.
73
Stan
KM4HQE
Hi Petr!
I state that i use debian "buster".
With the previous version 2.2.0-1 the remote mode for wsjt worked well with CQRLog. With the new version 2.3.0-1, when I register the QSO in FT8 a pop-up of CQRLog opens with the warning of an access violation and I have two options: "CANCEL" or "SAVE". if I click on "SAVE" I run the risk of corrupting my data, if I click on "CANCEL" CQRLog disappears and only WSJT-X (1.9.1) remains active, however the contact is registered on CQRLog, as well as automatically it is uploaded on CLUB LOG and HAMQTH.
I would like the ability to reset the worked-before status for all grid locations on a monthly basis.
With this change the new coloring of the CQ's in WSJT-X will work great to make it easier to pounce on the grids that you need.
Thanks for a great program!
-Kirk
In case anybody is upgrading to Fedora 28:
I'm running CQRLOG on Fedora 28. It's working great now, but I had to add an extra package, mariadb-connector-c-devel to get it working. Without that devel package, CQRLOG gives this error:
. . . . Can not load default MySQL library ("libmysqlclient.so.16" or "libmysqlclient.so").
Installing that devel package provides the libmysqlclient.so library, and happiness ensues.
Please add the option for a "Confirm Exit" dialog when you click the close (X) button of a window.
Normally I am used to loggers with the main window being the list (Log4OM) and when I want the new QSO window to go away I naturally close it. This exits the whole program. An optional Confirm Exit dialog would relieve this.
-Kirk
CQRLOG ONLINE LOG UPDATE TAKES A LONG TIME TO UPLOAD HALF A DOZEN NEW QSOS TO CLUBLOG . IT UPLOADS A CALL, THEN LATER DELETES IT AND THEN DOES AN UPDATED UPLOAD FOR SAME CALL. IT UPLOADS EACH CALL TWICE AND DELETES EACH CALL ONCE. ANYONE KNOW IF THIS IS CORRECT BEHAVIOUR? IS DELETING ANYTHING CORRECT? A MANUAL UPLOAD TO CLUBLOG WITH AN ADIF FILE SEEMS TO WORK MUCH FASTER.
A RECENT UPDATE WITH THE ONLILNE LOG FEATURE OF CQRLOG GAVE THE FOLLOWING RESULT IN THE STATUS BOX. ALL THIS FOR NINE QSOS.
just installed the debian 9.4 on a pc previous on the windows 10 monster.
was looking for the cqrlog in software to install but seems it's not in the list??
any tips?
Dear all,
I have installed the CQRLOG version 1.8.2 and work with this successful.
But now I will change to the newest version 2.2.0-1 and get during the installation try following error message:
libmariadbclient-dev dependence error.
Ok I removed the mysql packet and installing the mariadbclient.
After that the CQRLOG 1.8.2 is again fine working, but during the next installation try from CQRLOG 2.2.0-1, I get the same message as before.
What can or must I do to upgrade the CQRLOG to the version 2.2.0-1?
I have CQRLOG working with WSJT-X and rigctld to control my Omni VI and log QSOs. But, I noticed 14.076 is the frequency used for the FT8 QSO on 20 meters. I expected to see 14.074 Why is the logged QSO record showing 14.076 for the frequency? I haven't checked other bands to see how far off they are.
What do the different colors in the WSJT-X cq monitor mean? That's a pretty neat window. Would be nicer if it showed LoTW users and eQSL users. Perhaps that's what the colors mean?
73
Stan
KM4HQE
ClubLog: Uploading WB6BEE ... OK
ClubLog: Uploading AE4DT ... OK
ClubLog: Uploading AF5WS ... OK
ClubLog: Deleting original WB6BEE ... OK
ClubLog: Uploading updated WB6BEE ... OK
ClubLog: Deleting original AE4DT ... OK
ClubLog: Uploading updated AE4DT ... OK
ClubLog: Deleting original AF5WS ... OK
ClubLog: Uploading updated AF5WS ... OK
ClubLog: Deleting original WB6BEE ... OK
ClubLog: Uploading updated WB6BEE ... OK
ClubLog: Deleting original AE4DT ... OK
ClubLog: Uploading updated AE4DT ... OK
Dear all, I'm a first time Raspi user and first time Cqrlog user, with minimum experience in Raspian so please bear with me, as probably I'm asking a dumb question.
I've been enjoying my Raspberry 3 Pi with Cqrlog for a couple of days now and so far so good with just one exception: uploading and downloading from Lotw. Whenever I try to download from Lotw I get the following message:
NOT Logged
Error: -2
Error:
Error: ssl_openssl
And when I try to export to Lotw I get the following message (the adi file is created and signed correctly):
Hello,
I just installed cqrlog 2.2.0(001) on a fresh Kubuntu 18.04 and notice a small cursor bug which I didn't see on my old 16.04 install:
If I use the TAB key to go to the "RST sent" field in CW mode, cqrlog fills in a 599 with the S field highlighted. That's fine. But if I enter an S value, say "5", it updates the "T" field, so the report becomes 595 instead of the expected 559.
Anybody noticed this bug too?
Regards,
Wolf, DK7OB
I am trying to run CQRLOG on my Raspberry Pi 3 B+. I have installed the beta version and when I run it I get a misaligned data access error.
What can I do to fix this?
Here is the debug file from the testing method:
**** DEBUG LEVEL 1 ****
Is there a way to change the mode the New QSO window defaults to when one double clicks on a spot in DXCluster? For example, I double click on a spot in DXCluster that's 14.074, which would "normally" be FT8, but the New QSO window defaults to RTTY when Auto is checked. So, is there a way to define what range of frequencies are "normally" used for a given mode?
73
Stan
KM4HQE
Hi!
Just happened to get error popup "Data too long for column county" when logging FT8. Right answer is "OK" then fix county field and save qso again.
County information was fetch from Hamqth.com that has data as "County: KDR#1130 EPC#23109 RDRC#393" there for that callsign.
Should we protect "county" field so that it would cut string from first space, or take only length that database field can hold ?
In that case there should maybe be similar protect for all NewQso fields. (bigger job...)
Hello
I'am using CQRLOG version 1.8.2 on my Raspberry Pi 3, I would like to use a higher version but I do not found where I can download it.
Thanks for the information where i can download it
regards
vy73
Christoph
Recent comments