Advanced Forum Search

An invalid vocabulary is selected. Please change it in the options.
Dx-cluster window

Hi

Updated to latest version 1.2.2 and noticed, that dxclusterwin. somehow
stops receiving spots after random time. If I give to cluster
forinstance sh/u command, I get reply, but spots sill stays away?

With 1.2.1 version this didn't happen. Anyone else noticed? During
cqww contest had to restart cqrlog several times, getting spots
working again. Disconnecting and reconnecting didn't help.
And I compared, if our cluster (OH1RCF) had some
troubles, by connecting there with another client, I got spots ok
with that. Using Fedora 15.

LOTW user info

I recently upgraded from 0.9.6 to 1.2.2. Nice job!

Notice that LOTW user info is missing from new LOG form (The "L" lower right corner). I do have this function checked.

Noticed that the new DATA folders does not have LOTW file,the 0.9.6 does. Where can I get it from? I can't find it on website at all. The old in 0.9.6 is dated April so is pretty old.

Thanks Dan KC2STA

Shutdown fails on Debian Sid

Sometime in the past few weeks an upgrade to Debian Sid seems to have broken GTK in some way that CQRlog cannot shut down. I've not been able to pinpoint the issue but with the help of Kamal, KA6MAL, I have some terminal output that may be of use. I first noticed this with CQRlog 1.2.1 and it persists with your 1.2.2 .deb installed.

Here is the crash output from 1.2.1 with my databases and configuration:

http://pastebin.com/mHHkxxUr

and 1.2.1 with a clean configuration and new databases:

http://pastebin.com/ubVZAn9N

finally, 1.2.2 with my configuration and databases:

LoTW station location selection

As one with multiple QTH profiles and also multiple station locations in TQSL, I've been mulling over the following enhancement for CQRlog. As TQSL stores the station location names in ~/.tqsl/station_data, a somewhat XML related formatted file, it seems as though it could be parsed and the station names provided as a drop-down menu instead of having to type in the name each time.

73, de Nate >>

Database access

Does anybody how I can open the cqrlog database outside cqrlog. My understanding is that the database is based on mysql which has a wide support.

Aim is to be able to extract eg last 50 qso or so to web applications.

73 de LA3RK Olaf

Qrz.com query the locator

Hello,
I don't know if it's possible an automatic query of the locator from qrz.com.
The purpose it's to populate the database with the locators and then convert the adif into a kml file and then watch it on Google Hearth.
73's de IV3IDP - Daniele

Problem with the scroll bar?

I don't seem to be able to scroll down through my "show qsl list" to the end, but only as far back as the last year or so. If I do a search for a qso going much further back, it does come up so I am sure my complete log is in there somewhere. Is this to do with the scroll bar? I have run the script mentioned in another post to disable the scrollbar, but this distro can't find it. I am running Mint 11. Any ideas?

Grant VK4JAZ

Importing my log into Linux Mint

I have just given up on Ubuntu and gone over to Mint. I have installed cqrlog and imported my entire log from my backup. Seems to have worked fine except I have lots of errors for qso's made on FM. Here is an example of the message I have received.

Functions not working on Ubuntu 11.10

Hi, Yesterday I upgraded to Ubuntu 11.10 from 11.04 and find a few snags with my logger. When I hit 'show qso list' the list opens OK but the buttons at the bottom of the page no longer work. If I select a qso to view, I highlight the qso in question, then when I hit 'view qso' the highlight shift to the last one on the screen and that's it. I don't get the qso to view. Similarly, I tried to edit a previously entered qso and the 'edit qso' button didn't work either. Any ideas?

after ubuntu upgrade 11.04 -->11.10

Hi
cqrlog won't open any of my logs .just log01 can be opened.

anyone have an idea

73,Jorge

export logg

Hello
I have a short question.
How do I export the logg ( to my usb memory)
My cqrlog version is 1.2.1

TRX Control and Elecraft K3

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

Rigctl and Kenwood ts-440

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

Propagation mode field in database

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

Import ADIF: QSO comments go in wrong field

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!

CQRLOG and rigctld (daemon)

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

Greyline Offset

What would be the offset for the greyline? My sunrise is -4 and not sure what the greyline offset would be for that?

thanks

Club membership files must be installed to /usr/share/cqrlog/members (Debian package)

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.

3D2R

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

Executable no found Mysqld

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

Export freq to LoTW

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 >>

DX-cluster login phrase

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

Some Ideas

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.

LoTW-user as visible column

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

Name not updated if callsign is edited

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

Pages