Hello
I have a short question.
How do I export the logg ( to my usb memory)
My cqrlog version is 1.2.1
Advanced Forum Search
All, I have an Elecraft K3 I'm trying to get functioning with CQRLog. I have it connected to my computer via RS232 port, and think I have everything set up correctly in CQRLog, but can't seem to get rig control working. My system is set up for 38400 baud connection, 8 data bits, 1 stop bit, no parity or rig control. I use, per the CQRLog tables, rig model ID 229. However, CQRLog doesn't even seem to know my rig is present. Can anyone point me in the right direction as to what I'm doing wrong? I'm also new to Linux, so please be gentle with me. :-)
Thanks and 73,
Ian Kahn, AK4IK
Hi, just struggling with TRXcontrol with my 440. No worky.
In inicializerig
Model:202
Port:/dev/ttyUSB0
Baudrate:4800
Databits:8
StopBits:2
Handshake:None
Parity:None
DTR:OFF
RTS:OFF
Poll:250
RIG_RESULT1: in tRig.Close
TRX control thread terminated
I know, that hamlib works. I can command rig with rigctl and in Jlog controlling works. Suggested handshaking "hardware" does not work with rigctl, has to be "none".
I had troubles with Jlog, because of lockfile, had to set /var/lock user writable.
I'm using Fedora15 and hamlib-1.2.12-3.fc15.i686
I'm not sure whether this issue has been raised before or not. I'm very active on VHF, and one of the things you want to keep track of
(if it can be determined) is propagation mode, many possible modes exist depending on band:
MS = Meteor Scatter
ES = Sporadic E
F2 = We all know that one!
RS = Rain Scatter
AS = Airplane Scatter
AU = Aurora
EME = Earth-Moon-Earth aka Moonbounce
FAI = I've forgotten what it stands for (only usable in low latitudes)
And probably some more.
Best regards
OZ1PIF, Peter
Hi,
I'm just getting started using CQRLog (still using fldigi in parallel, as I haven't gotten used to it yet)..
One thing I noticed, (and there are more, will post more reports), when I imported my ADIF from fldigi, the comments for each QSO have been put in the "Comment to callsign" field instead of in the "Comment to QSO" field, this means that where there are more than 1 QSO they don't get saved and also that if I have a new QSO with someone the comments from the previous QSO gets overwritten.
Please fix it so it gets imported into the right field!
I am trying to connect CQRLOG to the rigctld (daemon).
I have got the daemon working, see screen output using nc to query/control rig:
olaf@D610:~$ nc localhost 4532
f
7023030
F 7024000
RPRT 0
Command f reads rig ok, and command F sets rig as requested, ie all in working order.
I then fire up CQRLOG where control has been set to localhost:4532 (has also tried localhost 4532 and only 4532). No contact with radio. Starting CQRLOG from console yields:
In inicializerig
Model:229
Port:localhost 4532
Baudrate:19200
Databits:8
StopBits:1
Handshake:None
Parity:None
DTR:OFF
What would be the offset for the greyline? My sunrise is -4 and not sure what the greyline offset would be for that?
thanks
Hi Petr and Martin.
I have discovered that CQRlog 1.2.1 in Debian Sid must have the club membership file--skcc.txt in my case--copied to the system directory of /usr/share/cqrlog/members for it to be loaded. I tried creating ~/.config/cqrlog/members as it did not exist and copying skcc.txt there. Looking at the club1 table showed that the newest members were not added. Once logged in as root I copied skcc.txt to /usr/share/cqrlog/members and the table was updated as expected.
I don't think this is a Debian packaging bug which is why I'm reporting it here.
Hi everybody,
I'm running the release 1.2.1 but the 3D2R is shown as Fiji instead Rotuma.
DXCC tables are set to check the updates every startup and the program does it regularly.
I've also tried to force it by downloading and installing the latest cqrlog-cty110912.tar.gz, but, after restart, it keeps on reading the wrong country.
Any clue?
73 de IK3SWB, Enzo
Greetings, everyone, I tried the version 0.96 and runs perfect, but the version 1.21 to run out a sign that says not found Executable mysqld, my system is 5.28 linux puppy 'm not very expert in linux I'm starting puppy recently thanks help 73 de Felix yv5grv
I notice that the frequency is not exported in the ADIF file that is created when exporting to LoTW for upload. I did not find a setting for this as I presume the LoTW export is fixed at the essential fields. I'd appreciate it if this were added in a future version since LoTW accepts the frequency.
73, de Nate >>
I have discovered telnet.reversebeacon.net:7000 (RBN) as a nice source for spotting DX.
This source seem to have a different login phrase than ordinary clusters:
"login:" (CC Cluster software)
vs
"Please enter your callsign:" (telnet.reversebeacon.net).
I have to manually log in to RBN.
Is it possible to add support for expected login phrase to the DX-cluster-setting ?
Also,
Is it be possible to have more than one source for bandmap ?
i.e both la7q.shacknet.nu:9000 and telnet.reversebeacon.net:7000
Hallo,
here are some ideas for cqrlog.
1.
One or two buttons placed in the window "TRX-Control", which store the current setting (band, mode, freq). A click could save the settings and reset the trx later on these values.
This would be good to save a current settings to then scan the band with the vfo of the TRX .
2.
If a callsign is selected in the window "Band map", the callsign is entered in the "New QSO" Window.
When changing the band, the Call is no longer required. Therefore, it would be perhaps good to reset the window "New QSO".
3.
The program imports the ~/.config/cqrlog/lotw1.txt on startup.
Is it possible to add this into one of the tables also ?
The usage would be to go through the log and look for LoTW-users that have not responded by LoTW yet.
73 de Børge / LA4VGA
If You enter a callsign and press TAB, the program will lookup name and QTH.
But if You edit the callsign (i.e one letter), and the press TAB, the name and QTH field is not updated.
You can see the callbook window updating
This has to be done by dobble-ESC, and the enter correct call.
73 de Børge / LA4VGA
Where can I get the source for CQRLOG? I'll happily package it up for Fedora and EPEL (in RPM) for users of those operating systems.
73,
Eric W4OTN
I was trying to import from LOTW, but the file downloaded was actually an html file, and not a real .adif file.
I could go to the website and manually retreive, but not from the Download From Website button...
I hate to add to your already long TODO list. ;-) I have several databases, each for a specific callsign I've used and am using QTH profiles to manage my operating locations. So far, so good.
I have found that when I open CQRlog anew and select a DB, work in it a while, and then select 'File|Open or Create New Log' that after opening the second DB (or any subsequent DB) the profiles remain from the first DB open. Closing CQRlog and then selecting the desired DB at the program's start results in the proper QTH profiles being available.
Hello! Recently installed CQRlog 1.2.1 and try it. There are a few questions.
In the CwFxkeys fails to sign key F9 and F10. For example, the settings stored - F9-AGN, F10-QRZ, but the buttons still remain F9 and F10. When you press the button (F1-F10) in the window, there is no manipulation. When I press them on the keyboard, everything is OK.
A number of contest loggers generate the STX and SRX ADIF fields for sent and received serial numbers. Having this information makes it easier to find a specific QSO when the numbers are known. I know this would most likely require a change to the database schema and require an import of log data but would be highly useful for maintaining a separate contest database in CQRlog.
BTW, nice work on adding multiple databases, I find this feature very useful.
73, de Nate >>
I'm importing the logs from the 0.9.x installations (yeah, I'm late) into 1.2.1 on Debian Sid. In one log I have four frequency errors I cannot resolve. I noticed that all four of the frequencies are in the upper part of the 2m band which is legal here in the USA. I went into the preferences adjusted the band limits for Region 2, USA. I tried the import of the four errors (after edting out the ERROR: lines) and received rejection of all four records.
Since CQRLOG 1.x, only the first few hundred QSO's or so are shown in the QSO list instead of all QSO's. Is there a way to show all QSO's again?
It's troublesome because of this issue: When i click on "Export for label printing", only those QSO's that can be seen in the QSO list are exported, but not the complete logbook.
First, thank you for offering HamQTH as an alternative to QRZ. As I agree with the fundamentals of Open Source, I appreciate your efforts. However, since HamQTH is still new I'm finding that I still must rely on QRZ when HamQTH does not have complete references. Presently, on the "New QSO" window there is a button for QRZ and one for HamQTH linking to the appropriate web page. Would it be possible to also assign buttons to select whether to use QRZ or HamQTH to fill in information?
Every third program start or so the TRX control shows the frequency 0.0000 and CAT does not seem to work.
I'm using Ubuntu 10.04 with a Yaesu FT-847 and CQRLOG 1.2.1.
Here is the console output when TRX does not work:
test@shack:~$ cqrlog
Loading libssl: /usr/lib64/libssl.so
Loading libcrypto: /usr/lib64/libcrypto.so.0.9.8
Loading libmysqlclient: /usr/lib64/libmysqlclient.so.16
*
User home directory: /home/test/
Program home directory: /home/test/.config/cqrlog/
Data directory: /home/test/.config/cqrlog/database/
For unknown reasons, sometimes cqrlog corrupts the dxclusters table. After that happens, clicking the "Select" button in the dx cluster window results in a "Operation cannot be performed on an inactive dataset." pop-up, asking me to either kill cqrlog or risk data corruption.
Other windows still work fine, for example the QSO list.
Running myisamchk -r on the dxclusters table (after quitting cqrlog!) does not seem to fix the issue...
Recent comments