I use CQRLOG almost exclusively in "Remote mode for wsjt". I think I have it set to import data from QRZ.com, but all I get is the Name, & most of the time the Name goes into the next QSO instead of the current one. Also: the Mode is correct but it also is in the "RST sent" field; RST received is in "PWR"; & power is in "Comment to QSO". I have a screenshot of the before I've made any edits, but cannot figure out how to attach it here. This doesn't make the program unusable, but I only make a handful of contacts a day. Any more & I would be editing longer than I am on the air.
73,
Bill
Sat, 2017-10-07 22:48
#1
K5TTF
CQRLOG does not put data in proper fields
Hi !
Have you tried hamqth.com instead of qrz.com ?
Make login account set it to cqrlog/preferences instead of qrz.com an give a try. Normally you will get more data from that source.
Do not choose "start wsjtx-x when remote". Start cqrlog by own and wsjt-x manually after that (this does not effect log information, but has proved to be better way: if cqrlog crashes you can still finish qso and log it ok after restarted cqrlog).
Do not care what you get to "NewQSO" window during your JT/FT qso. When qso finishes do logging with wsjt-x log sheet. Fill power and remarks if needed to that sheet.
Either let it auto-popup when 73 is sent (from settings) or manually press log qso from wsjtx main screen.
This way logging information gets correct to cqrlog that will add the information that it has from qrz.com (only name) or hamqth.com (name qth locator by 6 chr..etc) to data wsjt-x logging process will give.
If you still get information, but to wrong places you could try to make a new fresh log to cqrlog and see if logging goes ok then.
Report what you have found trying these.
--
Saku
OH1KH
--
Saku
OH1KH
Thanks. I am away from home now, but will do the above when I get back.
73,
Bill - K5TTF
I have tried all your suggestions, but have found no improvement. I did switch to HamQTH, & when manually entering a call in the New QSO form & hitting , several fields are added, but this does not happen when in "remote mode for wsjt". All of the data is in the proper fields when I save it to the wsjt log, but later, when I look at the QSO list in cqrlog, the data is scrambled as described above. After trying a new log, which didn't work, I removed cqrlog completely, then replaced it. That didn't work either. Any other suggestions?
Thanks & 73,
Bill - K5TTF
Hi!
" several fields are added, but this does not happen when in "remote mode for wsjt". " Sounds strange.
First:
Does NewQSO/Call that now has "Wsjt-x remote" text, when remote is selected, change its color about 15sec periods when just let programs run (even on empty frequency)?
If it does not your UDP connection does not work. Check settings using picture of this message https://www.cqrlog.com/comment/5757#comment-5757
if that works then:
When you reply to someone's CQ, or someone who replied your cq gets his report, at the point when you send report to him does his call appear then to NewQSO/Call (that has "Wsjt-x remote #X" text)?
It should happen if the first thing with UDP link works.
If call appears also hamqth/qrz data should appear if it does so with ordinary qsos when leaving call-field.
If it does not, but UDP seem to work (text changes color) I'm confused.
You have installed cqrlog again with no help. Is it sure version 2.1.0(001) ? There have been discussions that the ppa does not contain latest version. https://www.cqrlog.com/node/1878
If the version is 2.0.5 you could try to install from tgz in "Complete application directory for other distributions:" as I have tested x86_64 there is version 2.1.0(001).
If you try it again make save copy of your /home/username/.config/cqrlog directory with all it's files and folders. After tested that your copy has them all delete whole directory /home/username/.config/cqrlog to get absolutely clean reinstall.
Cqrlog MAY NOT BE RUNNING DURING COPY.
!!!NOTE YOUR LOGS ARE THERE, BE SURE THE SAVED FOLDER STRUCTURE CAN BE RESTORED !!!
If you then have clean and sure 2.1.0(001) version running and it still does not work proper way I would like to see a dump of debug during one complete wsjtx qso.
For doing that open console and type:
cqrlog debug=1 > /tmp/mydebug.txt
After qso is done close cqrlog and send the file to me as PM oh1kh a-t sral d-o-t fi
If you like try more testing when fresh install is done you could try add my last test binary (for x86_64) see http://www.saunalahti.fi/sakny/bin/cqrlog2/ ZIP that includes just the binary that can be copied over exisiting 2.1.0 binary (usually /usr/bin/cqrlog).
But maybe it is better to try to get the official version work first.
Let me know results!
--
Saku
OH1KH
--
Saku
OH1KH
Hi, Saku.
It appears that I have been causing CQRLOG to mess up. I do not use either CQRLOG or WSJT-X to control my transceiver. So, I would start the control program I have for my rig, then WSJT-X, then CQRLOG. I would immediately put CQRLOG in "remote mode", then minimize it. When I was through with my contacts, I would restore CQRLOG & open the QSO list, which would have scrambled data in it. Tonight, when I was following your instructions, I left CQRLOG on the desktop, alongside WSJT-X, & everything worked a treat. Data was imported from HamQTH, & all data was in the proper fields(& stayed there). There might be something wrong with CQRLOG that causes it not to work properly when minimized, but I won't be using it that way any time soon. Thanks for your help & I'm sorry I wasted your time.
73,
Bill - K5TTF
Hi Bill!
Nice to know that you find the reason. I was wondering what could be this kind of reason causing that fault.
Now I know and I have to test a bit as myself to see what happens when cqrlog is minimized. I have never used it that way.
So your control program initiates rigctld then, I assume. After that all other programs can access it also via localhost as cqrlog and wsjtx need rig information, too.
If you do not like to see cqrlog during qsos have you considered to put it to another desktop but keep it open if it does not work minimized?
I myself have 4 desktops (Fedora 26/LXDE) and one is populated (dual display) full with cqrlog and wsjtx windows. Others (3) are used for other purposes, Web browsing, mail, Lazarus/Arduino GUIs and what ever.
Switching between and also dracking individual programs from desktop to another is so fast that I can not imagine living with only one desktop.
No wasted time! All feedback is valuable !
You just point out that also minimized usage should be taken account of.
I like to help as much as I'm able.
--
Saku
OH1KH
--
Saku
OH1KH