My country_user file is no longer taken into account :
I'm trying to fix some small issues with CQ and ITU zones.
For this from the country.xml file I create a file that I name country_user.xml
For example : OA4SER is in locator: FM48mv (See QRZ.com)
but FF48mv corresponds to ITU 14 and CQ 12 contrary to what is indicated on QRZ.com (ITU 12 CQ 10)
so I modify my country_user file by adding CQ 12 and ITU 14 :
<Country>
<ArrlPrefix>OA</ArrlPrefix>
<Comment />
<Continent>SA</Continent>
<CountryName>Peru</CountryName>
<CqZone>10</CqZone>
<CqZoneList>
<int>10</int>
<int>12</int>
</CqZoneList>
<Dxcc>136</Dxcc>
<ItuZone>12</ItuZone>
<IaruRegion>2</IaruRegion>
<ItuZoneList>
<int>12</int>
<int>14</int>
</ItuZoneList>
...
I quit Log4om and I restart it so that it takes into account my modified file.
Well, I don't, Log4om doesn't take my new data into account.
I do the same manipulation but this time directly in the country.xml file (I previously saved this original file of course) and there Log4om takes it into account.
I did these manipulations with different callsigns and it's always the same, the country_user.xml file is not taken into account
Do you have to do another manipulation for Log4OM to take into account a _user.xml file?
Thank you
country_user file is no longer taken into account
country_user file is no longer taken into account
Dan - F6FLU
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
Re: country_user file is no longer taken into account
I forgot to specify (I don't know if it's important) but I'm "OFF-LINE" I don't have a transceiver connected with Log4OM ...
Dan - F6FLU
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: country_user file is no longer taken into account
I dont recall us making a country user file recognisable it is restricted to those files listed in the Resources Editor!
73 Terry G4POP
Re: country_user file is no longer taken into account
thank you Terry, I understand better...
73
73
Dan - F6FLU
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
Log4OM V2.32.1.0 - Windows 11 - i9-11900K - SSD 512Go - 32 Go
FTdx101D - Hexbeam - Wired dipole 40-30M
https://F6FLU.org
Re: country_user file is no longer taken into account
Dan,
The grid square listed on QRZ for OA4SER is incorrect. FF48 isn't even in Peru. This web site shows OA4SER is in FH17mv.
https://www.levinecentral.com/ham/grid_square.php
The zones listed in QRZ are correct. He is in CQ 10 and ITU 12
Also, if you go to his QRZ page, on the detail tab, and look at the map, it shows he is in Chile, which is where FF48mv is located. I'm guessing that QRZ uses the incorrect grid square to show his location on the map. At any rate, if he is using an OA call, he is in Peru, not Chile.
73,
Jim N6VH
The grid square listed on QRZ for OA4SER is incorrect. FF48 isn't even in Peru. This web site shows OA4SER is in FH17mv.
https://www.levinecentral.com/ham/grid_square.php
The zones listed in QRZ are correct. He is in CQ 10 and ITU 12
Also, if you go to his QRZ page, on the detail tab, and look at the map, it shows he is in Chile, which is where FF48mv is located. I'm guessing that QRZ uses the incorrect grid square to show his location on the map. At any rate, if he is using an OA call, he is in Peru, not Chile.
73,
Jim N6VH
Re: country_user file is no longer taken into account
"Also, if you go to his QRZ page, on the detail tab, and look at the map, it shows he is in Chile, which is where FF48mv is located. I'm guessing that QRZ uses the incorrect grid square to show his location on the map. At any rate, if he is using an OA call, he is in Peru, not Chile."
Jim, I don't know if you can trust the OA call - when you look at his QRZ details page it shows he won't even be born for another 389 years! (And, let's face it, if he is from the future no real telling where he is transmitting from! )
Sorry for the humor interruption, now back to our scheduled programming.
73 de Larry N1FG
Jim, I don't know if you can trust the OA call - when you look at his QRZ details page it shows he won't even be born for another 389 years! (And, let's face it, if he is from the future no real telling where he is transmitting from! )
Sorry for the humor interruption, now back to our scheduled programming.
73 de Larry N1FG
Re: country_user file is no longer taken into account
This is confusing for me, because I asked this same question in July 2020 and received the following response:
- Attachments
-
- Country file question.png (31.57 KiB) Viewed 1468 times
Win10 64b v21H2 Log4OM v2.21.1.0
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: country_user file is no longer taken into account
HI Dick,
That was a question about Log4OM V1. The V2 is completely different.
That was a question about Log4OM V1. The V2 is completely different.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: country_user file is no longer taken into account
Hi Jürgen,
Sorry, but at that time I was running version 2.8.0.0
anyway, It did not work for me in Version 2, At the time of my question at July 2020 I was under the assumption that I made a mistake.
73, Dick
Sorry, but at that time I was running version 2.8.0.0
anyway, It did not work for me in Version 2, At the time of my question at July 2020 I was under the assumption that I made a mistake.
73, Dick
Win10 64b v21H2 Log4OM v2.21.1.0
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5