Better yet, is there a good way to make a deb file for Pi once we've gotten the compile to work? I was able to build no problem, but it takes more than the binary to work, right? I'd be glad to throw a .deb file for PI somewhere if I can make one.
I have planned to buy new PI some day later in autumn. Just to see how it compiles with cqrlog source.
Making a .deb was not in my mind.
Instead if you can compile my alpha version https://github.com/OH1KH/cqrlog/tree/loc_testing/
And put only the binary "cqrlog" to zip file it might be possible to use same update script also for PI as found from https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
You can try it.
Zip the PI's binary to file:
zip -j cqr5.zip src/cqrlog
Then place cqr5.zip to PI's /tmp and download also help.tgz and updateCqrlog.sh.zip to /tmp folder.
Next start it
and see does it work with PI.
Check README.md for further instructions and maybe it is best to duplicate your SD card before testing.
If it works it should update cqrlog over previous install and no .deb is needed.
Also if it works you could zip again binary, lets say cqrPI.zip and then I could fix the script to accept that (and maybe so some PI specific modifications if needed).
I could then add your cqrPI.zip to GitHub for PI updates until I get a PI of my own.
That way we could keep PI users also up to date.
It actually does not need anything else than the binary to update!
Of course up to date Help is also useful :-)
Anybody have this file cqr240JTDX.zip?
Select suitable zip from these. They all have JTDX fix (+ plus lot of other fixes)
Thank you. Very much appreciated.
I can try that, sure.
But I also took the initiative and was able to build a DEB file that I was then able to install on my Pi. I used the HEAD of the master branch from Petr's github repo for this one, but I'm sure I can do the same with your sources, too. The only thing that didn't quite work was that for some reason it's wanting to gpg sign something with Petr's key, and that's not going to work for obvious reasons on anything of mine...
He's got a "deb" target in the main makefile, so all you really need to do is "make deb" to get started.
... for that matter, I wouldn't mind giving you SSH access to my PI if you wanted to use it for this stuff while you're waiting on getting your own. My email is good on QRZ (and probably hamqth, too).
I am now with ubuntu 20.04.01 and i have no reprt send to cqlog in ft8 mode.
jtdx 151 have report on prompt qso but no send to cqrlog ?
Sorry but i don't remember for solution
ps: sorry for my bad english....hi
Fix was to load version that had that reporting fixed. That one does any exist any more.
Update to latest alpha version. Or compile cqrlog by yourself from Petr's GitHub source. Ubuntu package holds so old version.
Alpha with instal script and instructions: https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
Petr's source (official) @ GitHub: https://github.com/ok2cqr/cqrlog
Greetings Saku et al.
Debian 10.5 64 bit updated and upgraded to date.
MadiaDB 10.4 database server is running on my server.
Compiled and installed CQRLog downloaded from Github repository.
On the attached picture, in one of top lines there is "rxfreq" field.
But I do not see such field in edit window. QSO's imported form *.adi file
contain RX frequency data which is displayed in QSO List window.
Whilst exporting to HTML or to ADIF, on "Choose field to export" window,
in left bottom corner there is "Most recent entries on top" button.
When this box is ticked, QSO's are exactly in reverse order,
most recent are at the bottom.
CQRLog seem not receiving data from my JTDX rc152_1
Noticed on this forum that you mentioned patch to solve JTDX issue.
Looked here and there but didn't found such patch.
Do you mind to share it, please?
Tom - SP2L
"rxfreq" This is optional. If you go preferences/NewQSO and enable "satellite mode" you will see the column in bottom TAB "Satellite". It is used to save the rxfreq in cases of cross band qsos as satellite qsos are.
Preferences/visible columns should have checkbox for showing that in "QSO list"
You are right. Thanks for bug report.
If "Most recent" is checked oldest qsos are on top. (I have to either fix the source or fix the text to "oldest on top" that will be faster , hi. )
JTDX. Now I finally found a package for Fedora, I'm too lazy to compile because I am not using it and not planning to use it either.
There is no patch, unless you do dig it from old commits from Petr's official GitHub source.
How ever if you compile the latest source from Petr's official GitHub you will get it. And many more fixes too.
Source is at https://github.com/ok2cqr/cqrlog
To see how many fixes and additions have done after 2.4.0(001) look commits down to #220 (2020-11-02) at:
It is pity that package maintainers do not make new packages against current source. But I understand that because version number has not changed.
If you can not compile easily you can try to update your cqrlog to ready compiled alpha test version ( 2.4.0(122) ). It is actually just copying file /usr/bin/cqrlog, but there is an update script that will do it and also help file update and all backups before upgrade. See the README.md from:
Hello Saku et al.
I appreciate your detailed response.
In regard "rxfreq" it was so called easy-peasy job... :))
It's exactly the same like in Log4OM2 which I use for quite a while - thank you,
I noticed this option in CQRLog, but to be candid, it didn't rang the bell, Hi!
I compiled & installed CQRLog from Petr's Github.com repository,
so I assume I have the latest source available,
hopefully including JTDX fix. Am I right?
CQRLog is very fresh experience to me, therefore it is possible
that i am not familiar with other CQRLog features, yet.
I prefer to compile myself, as I am well versed with Linux, in general.
On my multi-boot desktop PC I do have big stud of various natively
installed Linux distros: Debian 9.13, Debian 10,5, Ubuntu 18.04,
Ubuntu 20.04, Fedora 31, 32 & 33, Knoppix-8.1
and some other, less popular vanillas - all 64 bit.
I am very active JTDX project supporter.
For JTDX community I make JTDX installation
packages for Debian-10.5, Fedora-31 and Slackware-14.2
That said, I may offer building CQRLog *.deb, and *.rpm installation
packages for operating systems that I have on my desktop PC.
Then you do not have any problems with source. And yes, the JTDX fix is there.
There is one "hanging" pull request as you may see, It causes propagation mode to be "TR" (tropo) when logging from wsjtx/JTDX but that does not make very big problem.
I recommend to install also folder "help" from master to /usr/share/cqrlog if you compiled and installed just the binary file as update.
make / make install (that I do not use by myself. I use just Lazarus GUI) might install that too (never tested, hi)
Today been fiddling a lot to "convince" CQRLog to cooperate with JTDX-2.2.0-rc152_2
Unfortunatelly to no avail.
Last attempt I did setting in both, CQRLog and JTDX, multicast IP addresses.
Made QSO with PA0NKK prepared myslef to save everything I can catch.
After QSO completion JTDX sends proper adif message directed
to multicast IP address 126.96.36.199 on port 2237;
see attached combined picture, in particular blueish one showing this.
QSO particulars are stored in wsjtx_log.adi and wsjtx.log files.
But for unknown reason CQRLog did not stored these details.
Excerpt from wsjtx.log file:
Excerpt from wsjtx_log.adi on attached picture.
From my point of view, source code which I downloaded from Pert's repository
do not contain jtdx patch mentioned earlier or... may be I overlooked something else, Hi!
Do not know where to look for possible troublemaker.
All suggestions will be very much appreciated.
In normal case (wsjt-remote) cqrlog does not use ADIF for logging. Instead it uses the logging message #5 (binary). There is no need to check "Enable sending logged QSO ADIF data" but it does not matter (just tested)
The JTDX PR is : https://github.com/ok2cqr/cqrlog/commit/6a3ea4fffd984a09fab853eae2a7a335... and it is found from fNewQSO.pas, line 2945
There is no matter if you use localhost or multicast address.
if you run from console you can track what is decoded:
if dmData.DebugLevel>=1 then frmMonWsjtx.BufDebug('Log data',Buf);
to fNewQSO.pas line 2784 will show you the binary data debug from JTDX when logging is done. You can compare results to debug lines that follow that "log data" debug line to see what cqrlog decodes from binary.
If you do not need CQ monitor, or WsjtMap, you can use "N1MM remote" instead of "wsjt remote" for just logging qsos to cqrlog.
Then set JTDX "Send logged QSO ADIF data" check "Enable sending to secondary UDP server". Keep 127.0.0.1 and port 2333
(just tested and it works)
I suggest you uncheck "Enable automatic logging" and check "Prompt me to log QSO" instead. At least while testing logging.
With N1MM remote you can not see logging happen unless you set preferences/NewQSO/Refresh data after save qso checked and keep "QSL list" window open.
Using picture settings you can use either wsjt-remote or N1MM remote to log qsos.
As a last resort you can try to compile my alpha https://github.com/OH1KH/cqrlog/tree/loc_testing (that I used for testing with JTDX this morning) but there should be no difference in wsjt logging code compared to Petr's official source.
Thank you very much for detailed response, indeed!
Need to go over this step by step.
But first of all I'm going to compare "Fix for JTDX logging"
with source code I downloaded.
BTW, what is the meaning of "PR" in "The JTDX PR is :" phrase?
For the sake of experiments and to gather experience with CQRLog
compiled CQRLog from your repository on my Ubuntu 20.04.
Additionally I compiled afresh and build my own installation package
(JTDX testing version rc152_1 with libgfortran > 5, precisely 9.3.0)
Whilst using "N1MM remote" with "Prompt me to log QSO"
and "Refresh data after save QSO", completed QSO got logged.
But this is not I'm seeking for: fully automatic logging on Linux...
Saved to file some data from "cqrlog debug=1" command.
Will inspect them later on.
What's left now, is to compare "Fix for JTDX logging"
with downloaded CQRLog source code.
Will keep you posted accordingly.
Unless... you have other suggestions and/or ideas, Hi!
Verified that "Fix for JTDX logging" is present in your source code - thank you!
Now I'm going to fire my Debian 10.5 and perform some tests here.
When you get it working with "prompt me to log" then try again without that check. It should work, but I have no tested because I always want to check data before logging in.
BTW I tried to send email to you (yesterday) but got "service temporary unavailable". I suspect that makes warning also when sending forum message.
O.K. will monitor this intently.
While ago I sent message to your QRZ.com e-mail address.
When running JTDX/WSJT-X on Windows systems
as a rig I use Kenwood TS-480 emulation,
because I do have SunSDR2Pro TRCVR.
I am not familiar with CAT protocols details therefore my question:
what will/should be nearest usable item from CQRLog dropdown menu?
I do have installed Hamlib library that is used by JTDX software.
Forget my question - overlooked: 2028 Kenwood TS-480!
Compiled and launched CQRLog 2.4.0 (001) on Fedora 31 64 bit
which is using MariaDB CQRLog database running on my server.
At the moment can't check cooperation with JTDX/WSJT-X
because, for unknown reason, both do not see "Virtual Audio Cables",
whereas on Debian 10.5 and Ubuntu 18.04/20.04 JTDX and WSJT-X
are listing all necessary VAC's. Need some more time to investigate.
Apparently, with "Enable automatic logging"
CQRLog doesn't log QSO on Debian 10.5...
"Virtual audio cables" mean that you transfer audio from radio PC to server? (Pulse audio via network?).
Cqrlog can run remotes via net (local or internet) so that wsjt-x/jtdx is at radio PC and cqrlog is in PC @somewhere else. Set cqrlog listen address to 0.0.0.0 or specify radio PC's IP address. Open firewalls for both ends for remote port.
I have to check the enable automatic logging. Nobody ever have said it does not work or that it works. Neither one.
I always thought that automatic logging is the same as "prompt me to log qso" in means that when logging screen appears wsjt/JTDX "presses" immediately OK button. Actually so that the logging window does not even show up to user at all, but function is same same like user had pressed OK at logging window.
Well, I have to check that with both wsjt-x and jtdx.
I do have SunSDR2Pro TRCVR operated by ExpertSDR2 software
which to work with JTDX/WSJT-X requires so called Virtual Audio Cables:
ExpertSDR2 software <<== 2 pairs of VAC's ==>> JTDX/WSJT-X application(s)
So, VAC's only mimics physical audio connections
between two programs (applications).
TRCVR is connected to computer _ONLY_ with ethernet cable.
That will be all on this subject, I think.
BTW, did you received my yesterdays message
that I sent to your QRZ.com e-mail address?
Wsjt-x allows automatic logging only in contest mode (not tested). Prompt me to log qso opens logging window automtic when qso ends. When unchecked one must first press "log qso" button to open logging window and then OK at logging window to log qso.
JTDX logs qso automatic when "enable automatic logging of" is cheked. This happens when rr73 or 73 is send.
It logs nicely to cqrlog either with wsjt-remote or N1MM+ remote. Both work.
There are two things to note:
Qso data call, name etc. will remain to NewQSO window even when qso is logged. That happens because JTDX is still sending last period and there comes UDP status message that carries all qso info (like at first transmit of qso).
NewQSo is cleared when another qso is initiated, or F4 pressed to clear DXCall. Or if settings/reporting "clear dx call after qso" is checked.
This should be checked to see that qso was logged. But works properly with JTDX only if "Prompt me to log qso" is checked.
With N1MM+ remote:
Only way to see that qso is automatic logged is to open "QSO list" and check preferences/NewQSO/Refresh data after save qso".
Then new qso appears visible to QSO list after logging.
This can be used also with wsjt-remote.
So I can not see any problem with JTDX automatic login and cqrlog.
Arguing over this subject will not do any good
and will be only time wasting for both of us.
It is very nice that it works for you, undoubtedly!
But it would be even more nice if I can get it working for me.
Therefore your supportive and understanding
attitude will be extremely appreciated.
Let's both of us install AnyDesk software,
free for personal usage, available for Windows,
Linux and Android as well.
Then you, working remotely on my desktop PC,
will have one of a kind opportunity to set it working for me.
What you say, please?
Hi Tom !
I have sent some email to you but I always get bounce:
This is the mail system at host fgw21-4.mail.saunalahti.fi.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
421 service temporarily unavailable
I have used teamviever for remote help. Works over proxies and is free.
On cqrlog.com I changed my email address to:
It is on my own small amateur server.
There will NOT be "421 service temporarily unavailable".
Let's see how this one will perform, Hi!
In regard Teamviewer, it _WAS_ free. Used it long time with pleasure.
But they changed their policy starting making problems.
Two years ago I conducted long e-mail "discussion" with them.
Making long story short story - I do not use Teamviewer any more.
That's why I proposed AnyDesk...
Here is debug sample if you add the "logged data" debug line to start of #5 logging source code
Thank you very much for this file.
Will compare it to what I'll be seeing.
It seems that you do not have e-mail adderss set or it has a typo because answering to your forum message causes always
"Unable to send e-mail. Contact the site administrator if the problem persists."
I think this is because it tries to send an e-mail notification (send notification is set) to you for new forum message arrived.
Good morning Saku.
I do have email address SP2L@wp.pl set in my account details.
Till this very moment I had enabled comment notification.
While ago disabled this feature (Receive comment follow-up notification e-mails).
Wonder, whether now you'll not see "Unable..." message.
Do not recollect whether I saw this before :))
But while ago I was presented:
hello, i return to 18.04 ubuntu but same problem, no report save in the cqrlog and send by jtdx.
for info, wsjt-x is ok with report.................but i love jtdx....hi.........
tks Saku for your help,
return to 18.04 and good solution for me:
hope for the next 20.04 ubuntu.
There is currently 1 user online.