Hello,
im new to CQRLOG and try to setup my rig. I have been connecting my KX3 via CAT to CQRLOG and and it looks like communication is established.
But as I try to key CW I recocniced some timing issues. CQRLOG leaves some "blanks" between single letters where no blanks should be.
As interface I used the CAT /usr/bin/rigctrld on port ttyUSB0 with the default values for speed, databits, stop bits, pariy and so on.
Could you give me a int how to solve the issue?
Best 73 Thomas, DL3NGN
Hi Thomas!
You did not specify your cqrlog version.
Hamlib keyer is not the best one for HSCW. But speeds less than 30 WPM should work fair well. How ever there may be differences between rig models and brands.
As there is no proper way to get feedback from rig about it's CW buffer state strings that have less than 10 characters are pushed to rig as one command.
If strings are longer they are sent to rig letter by letter. That way rigctld can either accept letter or deny it and it is the only way to know is the rig's internal buffer full or not.
Now I am talking about latest (source compiled) versions of cqrlog. This fix has been made Jan. 2020.
So if you are using version original release 2.4.0.(001) there is old hamlib keyer and one of it's bugs was that it was sending every CW command in form "b A" where "b" is rigctld send morse command and "A" is the letter to send. It always added space between command and first letter and that space is counted as part of string to send. Proper command to send "A" is "bA"
Unless you have not compiled latest version from Git hub source, or tried my ready compiled binary you should try either one for better hamlib CW support
https://cqrlog.com/node/2984
https://cqrlog.com/node/2998
https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
--
Saku
OH1KH
Hi,
thanks for your answer. My Version is Cqrlog Ver:2.4.0 (001) Date:2019-10-27. And as far as I understood I use the hamlib interface and I'm normaly not above 25-28 wpm.
Maybe another Idea how to come to popper CW - I have a self build parallel port interface with a single R and T combination. It works for years with Windows logging SW. The interface is visible as tttyUSB1 (e.g.).
Is it possible to use it with CQRLOG?
(BTW: I took part in the CQ WW and used Wine and UCXlog and the combination did not have any issues up to 200bpm - what is the differents?)
BR Thomas
Thomas, DL3NGN
www.dl3ngn.de
HI Thomas!
I recommend to compile latest cqrlog from source. Links to messages clearing it out are in my last message. It is not rocket science and gives so many bug fixes that it is worth of try.
Your interface could work with program called cwdaemon that is supported by cqrlog. It is very old program and may have issues with modern computers.
Many arduino microcontroller based keyers support winkeyer usb connection, and so does cqrlog. That is the most recommended external cw keyer.
I do not know program UCXlog and can not comment about that.
--
Saku
OH1KH