Where the misterious cqrlog.ini file is located?

10 posts / 0 new
Last post
PY1ZRJ
Where the misterious cqrlog.ini file is located?

This is a really dumb question but I've not been able to find the .INI file of my CQRLOG!
Where it is supposed to be saved?

Funniest story because I created a new database since I decided to stop each log at 1000 QSO max. limit and I noticed that new DB has not any of my saved settings then I closed it and run the Utils import function to import the ini file of old DB but then despite searching several time I have not found such file on my system!

Thanks and 73

PY1ZRJ

oh1kh
Where the misterious cqrlog.ini file is located?

Hi!

If you want to use same settings to another log you must export settings. Open the old log. Then go NewQSQ/File/Open or create new log.
There is button Utils and when pressing that you get Configuration and Export.
That will do the ini file.

During runtime you can find settings file named by number of open log from ~/.cqnfig/cqrlog, but once you close cqrlog it is deleted and settings are saved to mysql database table from where they are fetched at new startup back to file. That is not recommended to use as copy as it might not have all latest changes applied (file is still open in memory)

When you have another log that you want to have same settings do not open it. Just select it from Database Open window at startup or if you are running cqrlog already from NewQSQ/File/Open or create new log. This case remember that currently open log is not the log you want to do Utils/confiquration/Import.

Importing to open log does not lead to expected results.

--
Saku
OH1KH

PY1ZRJ
Where the misterious cqrlog.ini file is located?

Dear Saku,

I've been able to do this export/import of the settings before reading your reply.

Everything get smooth but there is still some points which need further insights.

One of these is the fact that by creating a new log you miss all the DXCC/ZONE scores you collected so far on previous log because these data is restarted from scratch creating a new log.

IMHO, CQRLOG should offer to the user the option to update DXCC/ZONE score collected and merge it on the new log.

The good to create separated logs is that in case you have to do some export/import of the ADIF file you can handle such data more easily with smaller file size, using for example 1000 QSO per log maximum, as I decided to do with my logs management.

Thanks Saku and take care!

73 de PY1ZRJ

oh1kh
Where the misterious cqrlog.ini file is located?

Hi !

I understand your point.
How ever cqrlog is designed to make totally different logs without any connection to others.
DXCC/ZONE information is build against qsos in log, so it can not be transferred to empty log.

My suggestion is that you keep those max 1000 logs but make one log called to ALL. Then add all filled small logs to that and you can have DXCC total from the ALL log.
Unfortunately you can not get missing DXCC info unless you have log ALL open.

Another idea (but untested) is that you create new qth profiles and add only 1000 qsos per one profile still having all qsos in one log.
Using QSO list/filter(by qth profile) before ADIF export/label printing etc. limits your operations only to that profile's qsos.

--
Saku
OH1KH

PY1ZRJ
Where the misterious cqrlog.ini file is located?

Hello Saku,

Thanks again for your feedback, it looks like the main developers of CQRLOG are not "so responsive so far"...

The workarounds you explained above are not looking to be much practical to me then I prefer to keep on this, let's say, limitation, hoping that next CQRLOG release could include all the features requests submitted so far by the users, including mine regarding DXCC merging when creating a new log.

Wish to you all the very best!

Marco, PY1ZRJ

PY1ZRJ
CQRLOG get "isolated" if internet connection drops and backs.

Hello,

In addition to the several enhancement features which are being periodically added into CQRLOG (mostly by OH1KH, I should say), I would like it could be resolved the following issue I noticed on all the versions of the LOG program, including the newer GIT ones:

Let's see you start the program normally connected to INTERNET with your default WiFi network, in this scenario you can manage all the functions which are depending by remote connection to work:

Upload and Download QSL, LOG, Propagation, DX-Cluster and so on...

Then suddenly the main network connection drops due some faults so you switch for a "spare Hotspot" but from this point over, CQRLOG stops to communicate with INTERNET completely!

Or better told, CQRLOG is unable to refresh itself to the new network and you need to restart the program itself.

Then I kindly request to review this issue in order CQRLOG could make a sort of auto-verification (discovery check) to be able to switch to new network connection in case the main - or better the previous - drops to avoid the necessity to reboot the program.

Hope to have been clear enough in my description.

Thanks for your attention and many 73s de PY1ZRJ Marco.

oh1kh
CQRLOG get "isolated" if internet connection drops and backs.

HI Marco!

I'm not sure what you mean, but I have two wifi networks: oh1kh, and OH1KH using different equipments, channels and antennas.. The first one works better in ham shack, but both are usable.
If I start cqrlog when connected to OH1KH and everything from internet works I can switch to oh1kh and everything still works. Even DXCluster connection keeps on all the time.

First I would ask is your spare network in same subnet as your main network? It must be.
Otherwise your PC's IP address changes and your arp tables are not valid any more. Cqrlog and most other programs can not stand this kind of event.

If spare and main networks use same subnet and main network fails it might lead to IP retry timers to get so big waiting value before next retry (it is increasing during every false retry) that when network returns, or swithes to spare, it might take so long time to recover that you like to issue PC reboot before that.
Remember that also the internet side server might give up if your PC disappears in the middle of ongoing transfer.

Cqrlog network connections are tied to properties that the developing tools, mostly FreePascal lNet and in some cases Ararat Synapse, are offering.

--
Saku
OH1KH

PY1ZRJ
CQRLOG get "isolated" if internet connection drops and backs.

Hi Saku,

Thanks for your prompt reply!

Yes I mean that if my network connection drops CQRLOG stops to communicate over the INTERNET also if I try to switch to a different connection.

I'm using Linux openSUSE Tumbleweed with DHCP enabled.

The two networks are totally different: the main is a fiber-optic connection coming from the street line, while the spare connection is realized over the cellphone hotspot.

In my opinion CQRLOG must be transparent to any changes that can occur on the user network connection:

1) Connected on main fiber-optic --->CQRLOG online!
2) Connected on spare cellphone hotspot --->CQRLOG online!

I bet that if you simulate a failure on "OH1KH" while CQRLOG is connected to it and then you manually switch to oh1kh, you will see CQRLOG get isolated and unable to communicate over the INTERNET.

Hope to have clarified the issue now.

Regards,

PY1ZRJ (former IK5BCU)

oh1kh
CQRLOG get "isolated" if internet connection drops and backs.

Sorry!

"I bet that if you simulate a failure on "OH1KH" while CQRLOG is connected to it and then you manually switch to oh1kh, you will see CQRLOG get isolated and unable to communicate over the INTERNET."

Check this video. You just lost your bet: https://drive.google.com/file/d/1ZejPhDO37Lif8eYrv_o6XbdxBRZvPBIX/view?u...

In you cases #1 and #2 it is impossible for cqrlog, and the server connected at the other end to know what happened.
Lets say #1 connection gives IP 12.34.56.78 for you. You connect to DXCluster. When new spot arrives it knows it must send this spot to address 12.34.56.78. It will do so.
After a while your fiber connection breaks and you switch to cellphone hotspot that gives IP 87.65.43.21 for you. You did not close DXCluster connection so when next spot comes it will push it to 12.34.56.78 but there is nobody. How in the world it could know that you are in 87.65.43.21 address now!?

Same at cqrlog's side it was connected to DXCluster with 12.34.56.78. Your PC's TCP stack knows that gateway to outside world goes via 11.22.33.44 that is address of your fiber ISP provider's router. So it will push your commands to dxcluster to that router.
Suddenly you have changed to cellphone nerwork that has router 44.55.66.77 to outside world. Your PC's TCP stack still has established connect from cqrlog via router 11.22.33.44 and that it will use, but there is nobody any more.

You need your own router that is connected all the time to both of your ISPs and choose always better connection. Then you PC connects to your router that leads you to outside internet using connection that is better at that time.
In real world routers do switch networks between them all the time. That is ok and needed to keep data flowing via fastest routes. But routers have their own protocol to do that and it does not show up to private customers and organization's servers at the other end. All that both of them have to know is the nearest gateway address to outside world.

In my case it works, as seen in video, because my both WiFis are using same subnet address space, have same gateway and dhcp server (that is my local server, not ISP's one)
If I had two WiFi's named with same SSID both to oh1kh (or OH1KH) it cold be possible to have auto roaming. How ever I do not need that, I just want two WiFi sites with physically separated radio networks.

When I was still working I made a roaming WiFi network to one long and narrow warehouse. All WiFi stations had same SSID and they were connected to same subnet (with same router and dhcp). When truck was moving in warehouse it could use it's mobile PC all the time without breaks and without knowing what WiFi station it was connected to. But the key is that subnet must be the same all the time.

--
Saku
OH1KH

PY1ZRJ
Hi Saku,

Hi Saku,

Your video is not representing at all what happens in my case. I'm talking about an internet connection failure and not a voluntary switching as you perform in your video. I see you also are using Linux and if you simulate a failure on your network, I.E. unplug the power cord or disconnect the fiber from the input port of the router you should face same issue as I face.

What you say regarding I need to setup all my connections "ad-hoc" in order to use same subnets, sorry but doesn't make sense to me!

Otherwise all other applications which depend by Internet (Web browser, Email client, SkyPe, etc.) would stop to work whenever main connection fails, but as you know this do not happens! You have simply to switch to a different connection and everything back to work seamlessly as it should do CQRLOG as well, but it does not.

Anyway it is not a crucial problem and when my connection fails I simply close CQRLOG, resume my internet then restart CQRLOG, thats is it.

Thanks for your support.

Best regards,

Marco, PY1ZRJ