CQRLOG - open discusion

[How to] Callsign alert

Submitted by SV2RCK on

If you want to be alert when a desired callsign appears in cluster, add this command (Linux) in Preferences -> DXCluster.
You should install zenity first.

zenity --info --text='Callsign $CALLSIGN detected at $FREQ $MODE' --title=Info

Also you may set display duration in 5 seconds (Thanks DL2KI). After the window closes automatically.
KDE
kdialog --title=Spot-Info --passivepopup "Callsign $CALLSIGN detected at $FREQ $MODE" 5

Forums: 

Strange behaviour while overwriting RST, Call etc.

Submitted by ok1rr on

As a very anoying "feature" after upgrade of my Ubuntu to 17.04 (zesty) appeared a new bug - when I want to overwrite the default RST 599 to, say, 579 I get 597 instead. Usually the S value is highlighted, ready to be overwritten with a single keystroke (if needed to give 579, normally is enough to press "7" key). Now it seems that overwritten is not the highlighted character but the following one. This bug applies not to RST fields only but in all fields, no matter whether "Use spacebar to move between fields" option is checked or not.

Forums: 

[SOLVED] CQRLOg unstable with FT2000

Submitted by G8FXM on

I have had intermittent problems in getting CRQLog to talk to my FT2000 for quite some time now, it's always been a battle. I have periods of it working then periods when it wont.

I have recently rebuilt my PC and now run Linux Mind KDE.
Reinstalling CQRLOg onto my new environment saw a brief period where CQRLog would talk to my FT2000, but now it persistently refuses.

I recently installed TR4W contesting software on my KDE PC and even though its running under WINE, per performs flawlessly connecting to my FT2000 every time!

Forums: 

How to save a cqrlog from crashed cqrlog version 1.7.4 to version 2.0.5

Submitted by SA0BXI on

I have a problem with my cqrlog version 1.7.4 making it unwilling to start as you can see from the terminal listing below.

Can anyone advise how I can save the database and move it to the latest cqrlog version 2.0.5?

bjorn@sa0bxi:~$ cqrlog

**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Segmentation fault (core dumped)
bjorn@sa0bxi:~$ cqrlog

**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Segmentation fault (core dumped)
bjorn@sa0bxi:~$

Forums: 

Wsjt-x new mode FT8

Submitted by oh1kh on

During last week a new mode FT8 is introduced as a part of wsjt-x. FT8 is faster. TX periods only 15sec, but also that's why it is a bit less sensitive mode mainly planned for ES openings on 6m and up, but it is usable also in HF. too. It is a bit wider than JT9, but narrower than JT65.
You can get this wsjt-x 1.7.1-devel only by compile it from source at the moment.
There was some growing activity yesterday on 14.079Mhz .

Forums: 

Winkeyer_server Error

Submitted by kv5y on

System is Ubuntu 16.04, CQRLOG and rigctld to my FT1000MP MKV seems to be working.

The issue I have is with the winkeyer_server interface.

The winkeyer_server is running, but when I attempt to open the keyer I receive the following error:

Winkeyer USB
port 6789
/dev/ttyUSB0
------------------------------------------
Keyer is NOT online
Error: (9) Bad file number

I found this error in an earlier post here and grabbed the bash shell script devcheck.sh output enclosed:

Forums: 

Cannot connect to database after a reinstall

Submitted by OZ1PIF on

I've done it again - and this time without a recent ADIF back-up Grrrr.
I have the ~/.config/cqrlog folder with all content up to date, but when I try to start cqrlog I get:

Error during connection to database:
TMySQL57Connection: Server connect failed

Any way to fix this with creating a new database?

Running Mint 64-bit 18.1 Cinnamon for the record.
I was "just" reinstalling the system to clean up a couple of unrelated problems, did a full back-up of my "home" folder, and plain forgot this problem which I've run into before.

Forums: 

Error when uploading: "When uploading a QSO, at least qso_date, time_on....."

Submitted by VE3YDK on

I'm getting errors trying to upload a contact to HamQTH. I ran cqrlog with a --debug=1, and here's what I got. Any help would be appreciated. I expect I have invalid data, but I'm not sure what data is invalid.

============================================
data.Text:
u=VE3YDK
p=**redacted**
prg=CQRLOG
adif=201703222337WV6NSSB71672337599599ChristianWVNNFN23FL10085NCDurhamNNNAY20170621
cmd=INSERT

-----------
Response :When uploading a QSO, at least qso_date, time_on, call, band and mode fields must be specified!

Forums: 

Cannot compile

Submitted by lu8wfy on

Hi, I'm trying to build cqrlog 2.0.5 from source and i get the following error:

lazbuild --ws=gtk2 --pcp=/tmp/.lazarus src/cqrlog.lpi
SetPrimaryConfigPath NewValue="/tmp/.lazarus" -> "/tmp/.lazarus"
Error: (lazarus) invalid Lazarus directory "": directory lcl not found
Error: (lazarus) Building failed: src/cqrlog.lpi
Makefile:9: recipe for target 'cqrlog' failed
make: *** [cqrlog] Error 2

I have no experience with lazarus and I can't find the problem.
My system is running Slackware 14.2 (kernel 4.4.3.8-smp) and FPC 3.0.2.

Forums: 

Rigctld

Submitted by N0NC on

Lots of people are having problems with TRX control, Rigctld, But after 4 years of reporting bugs it still not fixed.

repost from earlier

I've been having this problem since 2013. I start rigctld at boot, it works fine with fldigi, gMFSK, and Xlog. Repeated program starts and stops have no effect, rigctld survives. With CQRLOG, the first time the program starts, it connects to rigctld, and works normally. When I close CQRLOG, rigctld crashes with the message broken pipe.

Here is a snippet from the terminal window where I ran rigctld.

Forums: 

Pages

Subscribe to RSS - CQRLOG - open discusion