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
Hi!
During last week I made one more extension to cqrlog's wsjt-x connection. Friday's ES opening was perfect place to test it with 92 qsos that about 90% of them were made by answering to CQ.
As we know wsjt-x stops TX if answer to CQ is done at same frequency as CQ calling and answer does not come to us.
But if we answer to CQ using split frequency our TX stays on even when CQ caller answers to someone else.
Hi
I have one request. In my log, station with /MM comming like unknown country.
No problems with /M or /P callsigns.
Also maybe /AM same trouble, I not try yet.
Thanks in advance
Best Regards YO4FZV Laur.
I accidentally hit the update when I started CQRLOG and puff access violation. I can't find my log db to back it up just in case and can't figure how to fix it. This is what debug gives me.
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
Country is listed as Marion island ZS8. It should be South Africa.
Call seen on 17m FT8.
Hello,
how can I filter out FT8 connections on the DX cluster? I only do cw and the FT8 entries bother me a lot.
Many Thanks.
Frank
DD2NU
I had Cqrlog working on mint 18.2 then switched to Ubuntu 18.04 bionic beaver to see if I could correct another problem and reloaded Cqrlog and my data just fine. I could not get digital working with fldigi for some reason so went to go back to mint and seemed ok but it won't let me open Cqrlog and the pop up says it can't connect to DB and to put last 20 lines of the err file here. Any ideas what I am missing ? thanks for any help, and feel free to email me direct too. Tom WD0BFO@WD0BFO.COM
Hi,
I did install the cqrlog to my debian 9.4. And it works but there are some issues. It does give me probs. I need to apt --fix broken though.
Is there a way to install this the right way? The .deb file which is downloaded from youre site is not compatible.
What to do so i can use cqrlog under 9.4 Debian?
Kindly regards,
Berrie
PD8B
I somehow ended up in a situation where upload stopped working and cqrlog complains
Clublog: All QSO already uploaded
I tried the old trick uploading an adif; but when I try to mark All qso's uploaded, I got another complaint. See attachment.
Hi Petr, I have a request. I have checked the commands that are being send to the Icom 7300, you send the mode with a filter/bandwith
But this makes the Icom 7300 use LSB/USB but always with Filter3, but that is a DX very small filter.
I normally use filter 1.
You send something like M USB 2200 as rigctrl command, but I like to send M USB 2700 as default.
Is there a way you let me choose and bandwidth setting instead of your default so I can choose the filter I want to have.
I have seen several reports here of instability, mainly with Yaesu rigs. My problem is with Kenwood but the symptoms are nearly identical. Let me also state right here that FLDIGI operates flawlessly with my rigs. I have
* TS-140S with IF-10C and IF-232C
* TS-440SAT with IC-10 and IF-232C
* Computer is i5 with 8GB RAM
* OS is Xubuntu 16.04.03LTS
* CQRLOG version 2.2.0 (001)
* Hamlib v3.1
If is possible to add in the search menu also from frequency, now is working from callsign/qso date/date/name/qth.
Thanks in advance.
73 de YO4FZV Laur.
Hello dear
since a short time the follwo massage given uploadwindow :
Error: No match on APP_EQSL_QTH_NICKNAME: ******
dont know why???
the login eqsl direct form my browser all is ok with the same logindata.
thanks for infos.
vy 73 de Hans DL1GZW
As a very elderly absolute newby to Linux, I would appreciate some help.
I am running Linux Mint 17.3 - 64bit version.with all updates installed. I have installed the latest version of Cqrlog and am trying to configure my Icom 746 com ports. I have tried all the sugestions made in the help files without success. Could someone please advise me how to setup the above. Any assistance would be appreciated.
Thanks in advance - Bill
When I save a QSO I get this message even though I have deleted the W7CPA QSO.
HamQTH: Uploading W7CPA
HamQTH: When uploading a QSO, at least qso_date, time_on, call, band and mode fields must be specified!
I found these errors in the data base error log.
Hello,
I have CQRLOG 2.2.0 and WSJT-X 1.9.0-rc3 working well together on Ubuntu 16.04.
Let's say I see a particular call sign appear on the WSJT-X decode list and I'm interested in working him. Before I do that I want to check my log to see if I've worked him before. Because CQRLOG is in Offline mode for wsjt remote operation, I can't enter the call sign in the New QSO window and press Tab to see what appears in the table above.
Is there another way to search previous QSOs in this scenario?
Radio control does not work.
Error message:
Database upgrade crashed with this error:
TMySQL56Connection : Error executing query: Duplicate column name 'rxfreq'
from my terminal:
martin@martin:~$ mc
martin@martin:/usr/bin$ ./cqrlog
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
2018-04-24 9:42:10 140572636926528 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 4876 ...
Recent comments