I just upgraded from Ubuntu 10.04 to 12.04 and with the upgrade from cqrlog 1.3.1 to 1.5.2.  Rig control was working fine in the old installation.  I've set all my TRX parameters to default, and when I run cqrlog from a terminal I get the following:
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 221 -r /dev/ttyS0 -t 4532  
RunRigCtld: TRUE
RigDevice:  /dev/ttyS0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll:    500
RigSendCWR: FALSE
RigId:      221
 

Hi, i collect WAZ zones to WAZ award.

I have QSO with HK0NA - this QSO are confirmed via LoTW and eQSL.

In field "qslr" i have "LE", but when i go to: Statistics -> WAZ -> select eQSL only (zone 7 is not confirmed "X")

When i change filter to "LoTW only" QSO are confirmed and again "Lotw and eQSL" also confirmed, but only "eQSL only" are not.

This is bug?

73! Pawel SQ5LTL

Hello all,
I do not send out QSL cards self-motivated, but I answer every QSL which comes in. So my basic procedure is:
CTRL-F (for finding the callsign in the log)
CTRL-R (for marking as received QSL)
CTRL-W (for sending out QSL via bureau)

My question is if the CTRL-R and CTRL-W could be combined in one shortcut, maybe CTRL-B (for 'bureau in/out') or an F-key or whatever. Not being a top of the line but average contester, I have to answer abt 1000 QSL cards every year. I'd love to avoid some of the 2000 CTRL-something monkey grips ;-)

Hi, how to use this line in the configuration:
"Do not show spots for this countries ...."
Please example.
---
Proposal to add option:
Do not show spots from this continent -s.
 
Thank you 73!
Pawel SQ5LTL

I'm attempting to import an ADIF written from ACLOG (logger written by N3FJP for Windows).  In all of my records that have a "Y" in the QSL_SENT field, CQRLOG defaults to "B" for BURO.  Also in the QSL_RCVD field, a "Y" defaults to "Q" whatever that means (I couldn't find it in the documentation-help).  While I appreciate the extra flexibility built into this field by CQRLOG, it would help if it would at least recognize the more basic approach of other logging programs when importing.  Can anyone help me with this?  Or maybe tell me a way around it without having to go in and manually chang

Clublog now supports the QSL Verified feature of the ADIF Standard.. To quote G7VJR:
"..there are actually three QSL states defined in ADIF:
 
Worked (QSL_RCVD = N)
Confirmed (QSL_RCVD = Y)
Verified (QSL_RCVD = V)
 
Up to now, Club Log has only supported worked or confirmed (a paper QSL or LOTW QSL is sufficient). However, while we were chatting at the RSGB Convention, Alan 5B4AHJ proposed that it would be helpful if Club Log also supported the verified state, which is set when you have your QSL accepted and awarded by ARRL."

I noticed today, after setting the TX power in fldigi for logging, that that piece of information isn't imported as part of CQRLog's remote mode.  It would be great if it were, because otherwise I have to go back and change it manually.  Along those lines, are there any other things in the fldigi log (state, notes, etc.) that are ignored by CQRLog in that mode?

When I attempt to run CQRLog in remote mode, with fldigi logging I can't use the results.
This is what I am seeing:
 
* The following are copied from the last QSO in the database prior to going into remote mode:  qsodate, time_on, time_off, callsign, freq, mode, rst_s, rst_r, name, QTH, loc, state.
* pwr is not copied, and it uses the default value.  (Probably because fldigi is not providing a power value.)
 

I just migrated to CQRLog from Xlog, and I'm loving the power of this tool.  After import, I realized that my adif file had reversed the RST values, so that the valued I'd reported out was in the column for values coming in.  No problem:

UPDATE view_cqrlog_main_by_qsodate SET rst_r=rst_s, rst_s=@temp WHERE (@temp:=rst_r) IS NOT NULL;

and all of my RST values were swapped.  I would have had to have to swap the values for each QSO using my old logging program.  Very pleased.

Is there a get started tutorial for cqrlog and indeed logging in general?

Anyone know how to export the frequency instead of the default band when exporting QSL's for printing?