Hi, thanks for the great app. Loving it, especially, the LOTW support.
There seems to be a bug with the new QSLR field introduced in 1.3.1.
The field is not updated for received LOTW QSLs for some reason. Please see the screenshot: http://goo.gl/BWAbd
Thanks,
Paul VA3PAW
Hello,
Sorry for my bad english, i hope that you can understand this message....hi.....
news ideas for futurs versions of CQRLOG:
1) management of QSO SAT
2) management of contests (i have see a friend of mine using UCX LOG in good conditions)
3) when i write the call (new qso) it is necessary for me to go in a new windows if i want to see that it is or not a new station........
my best 73's and congratulations for this very good job !
didier F1MXE
I had to do this just now and I thought I would document it (at least for myself) and maybe it will help others.
This probably isn't all the things everyone might have to do but it works for how I use CQRLOG
I use Fedora 16 x86_64
I use the binary release of CQRLOG "Complete application directory"
I mostly just use CQRLOG to log my contacts and upload them to LoTW, nothing else (so far)
I use CQRLOG 1.3.0
Install dependencies
yum install openssl-devel (needed for LoTW upload support)
yum install hamlib
I have been trying to get my system up and running again. I just installed Mint Linux 12. The install and etc has gone well. So fart I like Mint Linux.
On to the issue. I have a Hamgadgets MasterKeyer MK-1. This unit emulates the WinKey. I have tested this in Windows and works fine. I have also followed the documentation on testing it in Linux.
Here is what they have you do:
1.) Open a Terminal window.
2.) Type the command: screen /dev/ttyxxxx 9600 (use the serial port name you discovered earlier).
I just upgraded to 1.3.0 and after have imported my adif log, the window "show qso list" shows only the qsos i've did in the last 3 yrs. Statistic and "search" instead works, and shows, all the qso i've loaded. Is there any check box to activate the "shows ALL the qso"?
Hello,
I've updated to version 1.3 (64bit) on Suse 11.3.
Currently I've two situations, where cqrlog crashes.
1. Normal program termination (clicking the 'Quit Program' btoon on the QSO-window), the programms seems to exit normally, but I#am always getting the following error messages (when I start it from a console):
Saving ini file to database
Closing BandMap window
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Closing dData
/home/cfjh/.config/cqrlog/database/bastau.pid
Command:
kill 9922
Hi to all!
When I export my logs from ADIF files or into "Remote mode to fldigi", the value into the field RST_SENT it appears in "His RST" and RST_RCVD value into "My RST".
It's ok?
I think the "His RST" is how I receive to the other station and "My RST" is how the other station receive me. And then, RST_RCVD should be the value of "His RST" and RST_SENT should be the value of "My RST"
Thanks and i sorry for my English.
73!
Federico, LW3ESH
It would be a great feature to export only selected QSO`s to ADIF. For example, this would make the GlobalQSL handling much easier.
vy 73 and gd DX de Mario, DK5VQ
I searched around a little bit, but couldn't find any answers about the program development.
I was wondering if there was a way for those who are willing to help out with the development? I am not a long time user, I just recently became a ham but I am a long time linux user and I enjoy contributing to various OSS projects.
I did find the tarballs but sending a patch based off the latest tarball sounds painful especially if that increased the authors workload to merge it in.
If I make more than one QSO in the same minute then often they will appear in my log-book in the wrong order. Exporting to ADIF I notice that there is no seconds field in time-on so I'm guessing CQRLOG logs with just hours and mins and QSOs with a duplicate timestamp are sorted alphabetically or something.
Have I missed a 'preference' to allow seconds to be logged in the time? Although CQRLOG is not a contest logger I use it for casual contesting and have a little code that converts the ADIF into CAB format so, once I manually score the log I can submit it.
Hi all. Long time user of CQRLOG, was using it on Debian and Fedora but switched to Slackware a few years ago. Has anyone been able to get CQRLOG or TQSL working on Slackware64?
Thank you
Richard
My 897 seems to talk one way with CQRLog.
The software can read from the radio, but it can't do things like change frequency and mode.
If I open TRX control and click on a band the radio doesn't change frequency and CQRLOG stops reading from the radio. When I close TRX control and select Refresh TRX control from the file menu CQRLOG starts reading from the radio again.
Any ideas?
Paul
M0PGX
Hi,
Trying to figure out why my image folders in the QSO list are greyed out?
Ubuntu 11.10
cqrlog 1.3.0
Thanks in advance
Dave KB9MNM
Hello,
I'm very sorry that I didnt send any response to this forum for so long time. I have my right hand in palster and it is very painful to type on keyborad. Please be patient, I will answer to all questions but it will take some time.
73 Petr, OK2CQR
Hi all,
I've read a lot about cqrlog and would really like to use it. Unfortunately I'm not having much luck on my 64-bit Fedora 16. After some time spent ldd-ing the hamlib executable and duly installing the missing dependencies, there's only one final hurdle I can't overcame: hamlib.
As far as I can see cqrlog is generally linked with 32-bit shared libraries (most of which I could install without any problems). However, hamlib comes with a couple of executables whose path is identical in its 32-bit and 64-bit incarnations, when I try to install the 32-bit hamlib, yum dies with:
Hi, First of all thank you for all the hard work on CQRLog. It really is great software.
I am using CQRLog 1.3.0 from the prebuilt binary on the website. I am on Fedora 16 x86_64 and using TrustedQSL packages from Fedora (not the ones built by Petr). I am able to upload logs successfully both manually (export logs from CQRlog and sign using tqsl) and by uploading the tq8 file generated/signed by CQRLog directly to the arrl lotw site. What I'm saying there is that I can take the tq8 files from /home/john/.config/cqrlog/lotw and go to arrl's lotw site and attach them and they work fine.
Thanks to Petr and Martin for all their hard work and long hours !
Just put up CQRlog 1.3.0-1_amd64.deb on peppermint os 2 and all looks good feeding two K3's.
I have downloaded LOTW and EQSL and look forward to integrating all my data in CQRLOG.
Best 73/TKS, Howie N4AF
I was using Fedora 14 32-bit (hamlib from repo) with cqrlog_1.2.2_i386 and had succeeded in getting rig control to work via rigctld. Hurrah!
I recently upgraded to Fedora 16 64-bit and with cqrlog_1.2.2_amd64 it no longer works, with identical settings.
With rigctld running I can do "nc localhost 4532", type f and I get the rig frequency OK. On the face of it this says there's nothing wrong with hamlib and its TCP socket.
Running cqrlog from the terminal and clicking "Refresh TRX control" I get:
In inicializerig
Model:2
Port:localhost:4532
Baudrate:4800
Databits:8
StopBits:1
Hi
Made mistake, loaded into log old log and now I have all qsos twice
in log. How can I remove dupes? One by one? I have tried to look filter,
but can't figure how to do with that. There is not sorting meganism for
dupes? Terrible job to do one by one.
I have received and sent a lotw qsl which show the date in lotw_qslrdate and in lote_qslsdate but there is no "L" in the qslr field. It seems to have happened only for qso's after 1st jan 2012 but that may be due to my downloading via carlog rather than importing the adif from dxkeeper as I was doing.
2nd bug is after downloading from eqsl.cc I do not get any fields updated. Inspecting the 2012-01-28_11-21-52.adi file from my latest download shows some qso's which do not update in CQRLOG. Perhaps I need another step to import from the .adi file and I am simply just not doing it correctly.
I just installed CQRlog, and got my log imported. I have run into a few problems. First, rig control will not work with my FT-897D. I have it set up at 38400, 8N2. No handshake. It works fine under Grig. device is /dev/ttyUSB0. Also, every now and then I get an "access violation". It says "press OK to ignore and risk data corruption, or cancel to quit program", or something to that effect. I can close CQRlog, open Grig, and the rig control is fine. Any ideas on these problems?
Thanks es 73's,
Jeff
K4LMP
Hi
When I try upload log into eqsl, popup window asks QTH NICKNAME.
I have not set it in eqsl. I can't leave empty, because cqrlog
needs it. And haven't found, how to modify my account in eqsl.
Anyone else seen this?
Jarmo
I need a way to set the starting point of QSO entries not yet uploaded. I've manually uploaded QSO entries so far (many thousand) but the new utility insists on uploading the entire log - and the proceeds to hang indefinitely!
Hi All,
I am one of the developers of QtRadio which is a software defined radio programme able to interface with many of the popular SDR's like Softrock, HPSDR, Perseus etc. and it runs under Linux. To set the radio to interface with CQRLOG, set your preferences/TRX control as follows ...
Radio one/two desc: as you prefer (I use QtRadio)
Device: to 127.0.0.1:19090
RIG ID model: to 2
Poll Rate: to 500
To operate a software defined radio with its spectrum view and frequency versatility coupled with an excellent logging program is a huge operating convenience and advantage.
I have installed v1.3 and when I start it, i get this message. How do I work around this? I have run the script, like it asks me to, still nothing.
"It looks like apparmor is running in your system. CQRLOG needs to add this :
@{HOME}/.config/cqrlog/database/** rwk,
into /etc/apparmor.d/usr.sbin.mysqld
You can do that by running /usr/share/cqrlog/cqrlog-apparmor-fix or you can add the line and restart apparmor manually.
Click OK to continue (program may not work correctly) or Cancel and modify the file first."
Recent comments