remote mode for fldigi

11 posts / 0 new
Last post
MM0AMV
remote mode for fldigi

I use CQRLog v 1.5.1 with fldigi v 3.21.50 under Kubuntu 12.04.
Normally I have "remote mode for fldigi" activated, and all works fine apart from one small problem.
It seems that CQRLog picks up only the END TIME from fldigi and enters it into both the START TIME and END TIME fields, and so both fields have the same time.
Anyone have any thoughts?

Kind regards

Wallace

k8wdx
This is a bug in CQRlog. This

This is a bug in CQRlog. This is also a problem when stating a qso 2 min before UTC then logging after UTC will use the date when you logged not started the qso, which messes up the qso date, have to watch out for that, hopefully Peter can correct this..Tom K8WDX

Tom K8WDX

MM0AMV
remote mode for fldigi

Thanks for the info Tom. Guess I will have to live with it meantime. Apart from this, CQRLog runs flawlessly on 64 bit Kubuntu. Great piece of software for us hams.

Wallace

m0dcm
Thanks for the heads up on

Thanks for the heads up on the bug, I had re-installed Ubuntu 10.04LTS on my Sony Vaio thinking it was my fault! I use FLDigi and CQRLog a lot.
If Peter needs another beta tester, I don't mind testing the next version..

M0DCM Dave
PC - Sony Vaio VGC-V2M & Acer Aspire One AO751h
OS - Ubuntu 10.04LTS & Ubuntu 12.04LTS
RIG - Yaesu FT-817ND

k8wdx
Here is what I do, First off

Here is what I do, First off I have 2 monitors in the shack so this makes it easy, however with Ubuntu or Linux you have sevaral desktops so you can have Fldigi on one desktop and CQRlog on the other and just simply switch back and forth, or just use the Minimize function, Here is what I do, I have CQRlog runing on the left monitor, and Fldigi on the right, I have both set to have rig control, so Fldigi changes with the VFO and so does Cqrlog, I do not put CQRlog in fldigi mode, I turn off or click on auto to remove the check mark, then I put CQRlog in psk31 or RTTY, or what ever mode I am using, then as I work stations I simply put the call in CQRlog and hit tab, put in 599 or the report at the start, you can then see the qso clock start, this also pulls up all kinds of info, like the details box ect. at the end of the qso i hit save qso, and all is good. It really is just one extra step but totaly worth it, because of the info that comes accross CRQlog like how many times I have worked that station before ect. This is really good If you use the club log function, seems there are a bunch of clubs on the digi side, so you can see where your detail funtion would be nice while working stations, if you use this.. If I get into a contest like RTTY where the exchange is super fast, then I put CQRlog in Fldigi mode and log that way for speed. Here is how to get CQRlog and Fldigi with rig control at the same time:
There is a way how to have trx control both fldigi and cqrlog. Set the TRX control in CQRLOG and in fldigi preferences use Hamlib NET rigctl (Beta) asi rig and Device set to localhost:4532
It will work both in CQRLOG and FLDIGI.
HTH Tom K8WDX

Tom K8WDX

k8wdx
Hopefully one day Peter can

Hopefully one day Peter can get fligi to trigger CQRlog to do the lookup and start the qso when fldigi does and logs the way it currently does. and yes I agree, that this is one of the best Logging progams available, Linux or Windows. Believe me I have tried them all...Tom K8WDX

TU Peter, for the FB logging program..

Tom K8WDX

WB4ES
I noticed this bug this

I noticed this bug this evening.  For a short QSO it doesn't matter all that much, but with a long ragchew it can mean the difference between LoTW QSLs working or not working. Unfortunately, with a netbook, switching between the programs mid-QSO doesn't work so well.
 
This definitely needs to be fixed.

ok2cqr
ok2cqr's picture
Re:I noticed this bug this

Interesting, I just tried it. I entered the callsign to fldigi at 2007 and wait for one minute. QSO was saved with Start time at 20:07 and endtime at 20:08.
Could you please try it and send me the console output? CQRLOG writes to console what gets from fldigi. Thank you!
 
73 Petr, OK2CQR

WB4ES
It's on its way.

It's on its way.

WB4ES
Looks like Petr's found the

Looks like Petr's found the problem... somewhere between FLdigi 3.21.38 (what he's using) and 3.21.68 (what I'm using) there was a slight change in the log format that CQRlog wasn't prepared for. Fortunately, it should be an easy fix.

ok2cqr
ok2cqr's picture
Re: Looks like Petr's found the

Yes, it was very easy. I fixed it a few minutes ago and pushed to repository. 
Here is the fix:
 https://github.com/ok2cqr/cqrlog/commit/86f5d5477ecdc7f6fde909c1bf7c311878193139
 
New version will be released soon. Thanks to Brian, WB4ES and Mirek, OM2MS for their help!