CTY-3434 Country Files - 27 September 2024
The Country (CTY) Files were updated on 27 September 2024:
For installation instructions, start at:
Hover your mouse over the word Contest in the menu, then select the
software you are using.
To install the file, follow the link to your software at the top of the page.
If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:
Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.
As a reminder, there is an RSS feed of the latest country file announcements:
Here are the release notes:
27 September 2024 (CTY-3434)
VER20240927, Version entity is East Malaysia, 9M6
Added/changed Entities/Prefixes/Callsigns:
* 9M67M is West Malaysia, 9M2
* 9M67MQ and 9M67MS are both East Malaysia, 9M6
* BG2LTC/0 is China, BY in CQ zone 23
* VP8ADE is Antarctica, CE9 in ITU zone 73
* E51D is North Cook Islands, E5/n in ITU zone 63
* EA6XQ/P and EA9PD are both Spain, EA
* GB2ZL is Scotland, GM
* IK7YTQ/LNX is Italy, I
* IR0ROLB is Sardinia, IS
* KL0S and KL0SS are both United States, K in CQ zone 5, ITU zone 8
* K1JHR is Hawaii, KH6
* R50DSN, R8FF/6 and RA9ULL/6 are all European Russia, UA
* UA9XK/1 is European Russia, UA in ITU zone 19
* RI42SP is European Russia, UA in CQ zone 40
* RV1CC/2 is Kaliningrad, UA2
* RA9WU/P is Asiatic Russia, UA9 in CQ zone 16
* R2CC/0 and RX3AMI/0 are both Asiatic Russia, UA9 in CQ zone 19, ITU zone 34
Removed Entities/Prefixes/Callsigns:
* BD4QB/0 in China, BY
* EA5IYX/6 in Balearic Islands, EA6
* TO973FY in French Guiana, FY
* GB2OWM in Scotland, GM
* GB5VAS in Guernsey, GU
* GB0CAS and GB0ESM in Wales, GW
* IO0C in Sardinia, IS
* KM6RJA and WB4JTT in Hawaii, KH6
* K7WJH, KE0WDR and KG7GSU in Alaska, KL
* LU4ERM/D in Argentina, LU
* R0AD/3/P, R1641AZ, R8FF, RA9WU/P, RI0POL and UB5O/1 in European Russia, UA
* R0FBA/9, R5GA/9, R95MAG, RA/EA8RM/P, RW0CE/9, UA5B/0 and UA9CTT/P
in Asiatic Russia, UA9
Though I am subscribed to this reflector so that I can make these
announcements, I do not see most messages posted to it. If you have
any comments or corrections to the country file, please contact me
directly.
73 - Jim AD1C
--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>,
|
Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)
I had it working once after my rigpi had a corrupted card. If i remember correctly the pi serial 0 device is tied to a login terminal by default. And you have to use the config program to disable the login terminal serial so it will be available for the keyer board to use.
|
Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)
No, RigPi uses a K1EL WinKeyer 3 IC. Steve K1EL?
toggle quoted message
Show quoted text
On Sep 27, 2024, at 8:29?AM, GW0WZL via groups.io <gowzel@...> wrote:
? I should have added I think it uses the K3NG arduino software on an AVR microcontroller chip
|
Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)
I should have added I think it uses the K3NG arduino software on an AVR microcontroller chip
|
Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)
I have a rigpi3, but as the software used on it now is so out of date ie wsjtx and the pi os I have set up another sd card with bookworm, and have installed flrig as a radio control and wsjtx 2,70 rc6 flrig jscall etc.
I can use fldigi on all its modes including cw just using the usb cat port on my ftdx3000. But I would like to use the keyer board on the rigpi. It is based on the Winkeyer 3 IC and according to the rigpi manual is on serial port /devttyS0 at 1200 baud, but I have so far failed to get it to work on Fldigi apart from very occasional dits and dahs from the rigpi's speaker which were non reproducable.
Has anyone any idea or better still had it working without rigp os.
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
Steve,
I read through the CAT pages for the FT-890 and I think this is
what you want for the mode/width code:
enum {FT_LSB, FT_USB, FT_CWW, FT_CWN, FT_AMW, FT_AMN, FT_FM};
static std::vector<std::string>FT890modes_;
static const char *vFT890modes_[] = {
?? ???? "LSB", "USB", "CW-W", "CW-N", "AM-W", "AM-N", "FM" };
static const int FT890_mode_val[] =? { 0, 1, 2, 3, 4, 5, 6 };
...
?? ???? switch (replystr[6] & 0x07) {
?? ???? ??? case 0: A.imode = FT_LSB; break;
?? ???? ??? case 1: A.imode = FT_USB; break;
?? ???? ??? case 2: case 3: A.imode = ((replystr[8] & 0x80)
== 0x80) ? FT_CWN : FT_CWW; break;
?? ???? ??? case 4: case 5: A.imode = ((replystr[8] & 0x40)
== 0x40) ? FT_AMN : FT_AMW; break;
?? ???? ??? case 6: case 7: A.imode = FT_FM;
?? ???? }
?? ???? B.iBW = (replystr[9] & 1);
?? ???? B.freq = 10 * ((((replystr[10] & 0xFF) * 256 +
?? ???? ??? ??? ?? (replystr[11] & 0xFF) ) * 256 +
?? ???? ??? ??? ?? (replystr[12] & 0xFF) ) );
?? ???? switch (replystr[15] & 0x07) {
?? ???? ??? default:
?? ???? ??? case 0: B.imode = FT_LSB; break;
?? ???? ??? case 1: B.imode = FT_USB; break;
?? ???? ??? case 2: case 3: B.imode = ((replystr[17] & 0x80)
== 0x80) ? FT_CWN : FT_CWW; break;
?? ???? ??? case 4: case 5: B.imode = ((replystr[17] & 0x40)
== 0x40) ? FT_AMN : FT_AMW; break;
?? ???? ??? case 6: case 7: B.imode = FT_FM;
?? ???? }
see attached.
David, W1HKJ
On 9/24/24 19:55, Steve, KB5AW wrote:
toggle quoted message
Show quoted text
Thanks for looking at this.
?
Yes, those are the changes that I made.
I don't understand your menu system and all that are in
these statements, so you should review approve them.
The changes do not take into consideration the filter
bandwidth, so something needs to be done about that. There
should be something for CW-N and AM-N. I don't think that FM-N
exists.
It all comes from the mode information is different between
the reading and writing of it.
?
|
Re: For all you RTTY / Teletype fans out there..
I am thankful that the Air Force kept me as a TTY tech. for 20
years, because I had no problem finding a job in my retirement.
Msgt Donald Casillo USAF (ret)
On 9/25/24 08:21, Bo, W4GHV wrote:
toggle quoted message
Show quoted text
Interesting bio! I think doing a single specialty for a long
time would be great if you loved it. I had 4 in the USAF since
they love to shuffle you around about the time you love a
skill/job. USAF '58-'78
|
Re: For all you RTTY / Teletype fans out there..
Interesting bio! I think doing a single specialty for a long time would be great if you loved it. I had 4 in the USAF since they love to shuffle you around about the time you love a skill/job. USAF '58-'78
|
Re: Guide to New Rig backend creation?
Thanks Dave.
?
I'll see how I get on.
?
No doubt I'll be back here again at somepoint soon.
?
All the best.
?
Dave G0WBX.
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
Thanks for looking at this.
?
Yes, those are the changes that I made.
I don't understand your menu system and all that are in these statements, so you should review approve them.
The changes do not take into consideration the filter bandwidth, so something needs to be done about that. There should be something for CW-N and AM-N. I don't think that FM-N exists.
It all comes from the mode information is different between the reading and writing of it.
?
|
Re: For all you RTTY / Teletype fans out there..
I was for 20 years five months and eight days a Teletype Tech. in
the Air Force. Models 15, 19, 28s. I worked for Teletype Corp.
(three years) after military retirement working on Models 33, 35,
I also worked on Model 40 and 43s (eletronic? type). I also worked
for the FAA for 24 years on flight strip printers and lots of
eletronic gadgets. Msgt Donald Casillo USAF (ret) ?
On 9/22/24 22:45, Paul Simon wrote:
toggle quoted message
Show quoted text
Very interesting, David.? I have a model 15
which I acquired around 1968 and used for many years here prior
to the ubiquity of PC's.? The machine in the video described as
a model 14 is not.? The model 14 was a typing reperforator
usually with a rotary TD attached to transmit.. Because the
paper tape was also used to transmit it needed holes, but if you
had holes you could not read the print.? The solution was to
punch "toilet lids."? The chad was attached to the paper tape by
being punched almost all the way around.? I had one and let it
go many years ago.
I will be happy to share any and all, as well a few stories
about using the model 15 and it's quirks.
On 9/22/2024 7:55 PM, David Ranch,
KI6ZHD via groups.io wrote:
For all you RTTY / Teletype fans out there, this is a fantastic
video taking the viewer through how a teletype unity actual
works including details into Baudot 45, a full teardown and
rebuild of both a typewriter style and ticker-tape style
teletype, etc.? Great stuff and well worth your time:
??
This video comes from "Usagi Electric" who has made a lot of
other great videos on building his own vacuum tube based 1bit
computer, restoring various tube and legacy Mini computers,
etc.?
--David
KI6ZHD
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
Thank you Steve.? Please
confirm that these are the changes you implemented:
diff src/rigs/yaesu/FT890.cxx FT890.cxx
251,253c251,254
< ??? ??? ??? case 1: A.imode = ((replystr[6] & 0x40) ==
0x40) ? 3 : 2; break;
< ??? ??? ??? case 2: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 5 : 4; break;
< ??? ??? ??? case 3: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 7 : 6; break;
---
> ??? ??? ??? case 1: A.imode = ((replystr[6] & 0x40) ==
0x40) ? 3 : 1; break;
> ??? ??? ??? case 2: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 5 : 2; break;
> ??? ??? ??? case 3: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 7 : 4; break;
> ??? ??? ??? case 4: A.imode = ((replystr[6] & 0x80) ==
0x80) ? 9 : 6; break;
268,270c269,272
< ??? ??? ??? case 1: B.imode = ((replystr[15] & 0x40) ==
0x40) ? 3 : 2; break;
< ??? ??? ??? case 2: B.imode = ((replystr[15] & 0x80) ==
0x80) ? 5 : 4; break;
< ??? ??? ??? case 3: B.imode = ((replystr[15] & 0x80) ==
0x80) ? 7 : 6; break;
---
> ??? ??? ??? case 1: B.imode = ((replystr[15] & 0x40) ==
0x40) ? 3 : 1; break;
> ??? ??? ??? case 2: B.imode = ((replystr[15] & 0x80) ==
0x80) ? 5 : 2; break;
> ??? ??? ??? case 3: B.imode = ((replystr[15] & 0x80) ==
0x80) ? 7 : 4; break;
> ??? ??? ??? case 4: B.imode = ((replystr[15] & 0x80) ==
0x80) ? 9 : 6; break;
364c366
< ??? cmd[3] = FT890_mode_val[val] | 0x80;
---
> ??? cmd[3] = FT890_mode_val[val];
73, David, W1HKJ
On 9/24/24 18:38, Steve, KB5AW wrote:
toggle quoted message
Show quoted text
I wanted to see about fixing the Yaesu FT-890 rig in flrig,
so I looked at the code and did some hacking.
I suggest that you look at the code for correctness.
I used flrig-2.0.05.75
I got the modes selection menu to basically work, but more
changes are needed.
Here is what I did by modifying the attached
src/rigs/yaesu/FT890.cxx
?
vfoA and vfoB worked differently.
- Line 341 for set_modeA is:
? ? cmd[3] = FT890_mode_val[val];
?
- Line 366 for set_modeB is different. I changed it to be
like line 341.
? ? cmd[3] = FT890_mode_val[val] | 0x80;
Now: cmd[3] = FT890_mode_val[val];
?
Now both vfos work the same for mode.
-----
I worked with with the switch statement on line 249. Added
case 4 for FM mode.
The changes I made work for the base modes, but the menu does
not track wide/narrow. My rig does not seem to have FM narrow
and I don't see it in the manual.
Note that only modes which have 2 bandwidths are incremented by
2.
A.iBW? on line 244 seems to be the filter bandwidth, but isn't
used anywhere.
Note that for setting Mode, values are: LSB=0, USB=1, CW-wide=2,
CW-nar=3, AM-wide=4, AM-nar=5, FM=6 or 7.
For reading Mode, the values are: 0=LSB, 1=USB, 2=CW, 3=AM,
4=FM. BPF selection is indicated by byte 0.
?
|
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
I wanted to see about fixing the Yaesu FT-890 rig in flrig, so I looked at the code and did some hacking.
I suggest that you look at the code for correctness.
I used flrig-2.0.05.75
I got the modes selection menu to basically work, but more changes are needed.
Here is what I did by modifying the attached src/rigs/yaesu/FT890.cxx
?
vfoA and vfoB worked differently.
- Line 341 for set_modeA is:
? ? cmd[3] = FT890_mode_val[val];
?
- Line 366 for set_modeB is different. I changed it to be like line 341.
? ? cmd[3] = FT890_mode_val[val] | 0x80;
Now: cmd[3] = FT890_mode_val[val];
?
Now both vfos work the same for mode.
-----
I worked with with the switch statement on line 249. Added case 4 for FM mode.
The changes I made work for the base modes, but the menu does not track wide/narrow. My rig does not seem to have FM narrow and I don't see it in the manual.
Note that only modes which have 2 bandwidths are incremented by 2.
A.iBW? on line 244 seems to be the filter bandwidth, but isn't used anywhere.
Note that for setting Mode, values are: LSB=0, USB=1, CW-wide=2, CW-nar=3, AM-wide=4, AM-nar=5, FM=6 or 7.
For reading Mode, the values are: 0=LSB, 1=USB, 2=CW, 3=AM, 4=FM. BPF selection is indicated by byte 0.
?
|
Re: For all you RTTY / Teletype fans out there..
Well if we¡¯re waxing nostalgic I was army signal corp when I got my first ham license. Bit later than you two, 2003. Ended up being a physician instead so can¡¯t say the signal corp stuck with me, tho I still ride the waves!
KD7YJW
Teletype repair was one of the school choices that the Army offered me in 1976. ? Glad I declined that one.? Nike Test Equipment Repair (22L) provided a lot more opportunities over the years.
Davee W2IJL
On Tue, Sep 24, 2024 at 2:11?PM Donald, KD5UGY via <dcasillo= [email protected]> wrote:
I was an Air Force Teletypewriter Tech. for 20 years, five
months, eight days, Nov. 1958 to Dec. 1978. Msgt Donald Casillo
USAF (ret)?
On 9/24/24 11:02, Bo, W4GHV wrote:
Nice! I had 2 Model 15s.?
My troubleshooting skills:?
Look at working one, fix broken model.
Monkey see, monkey do
Where's my 35 minute paper tape of the X O . pinup girl on a
stool?
73 Bo W4GHV for SEVENTY YEARS?
|
Re: For all you RTTY / Teletype fans out there..
Teletype repair was one of the school choices that the Army offered me in 1976. ? Glad I declined that one.? Nike Test Equipment Repair (22L) provided a lot more opportunities over the years.
Davee W2IJL
On Tue, Sep 24, 2024 at 2:11?PM Donald, KD5UGY via <dcasillo= [email protected]> wrote:
I was an Air Force Teletypewriter Tech. for 20 years, five
months, eight days, Nov. 1958 to Dec. 1978. Msgt Donald Casillo
USAF (ret)?
On 9/24/24 11:02, Bo, W4GHV wrote:
Nice! I had 2 Model 15s.?
My troubleshooting skills:?
Look at working one, fix broken model.
Monkey see, monkey do
Where's my 35 minute paper tape of the X O . pinup girl on a
stool?
73 Bo W4GHV for SEVENTY YEARS?
|
Re: For all you RTTY / Teletype fans out there..
I was an Air Force Teletypewriter Tech. for 20 years, five
months, eight days, Nov. 1958 to Dec. 1978. Msgt Donald Casillo
USAF (ret)?
On 9/24/24 11:02, Bo, W4GHV wrote:
toggle quoted message
Show quoted text
Nice! I had 2 Model 15s.?
My troubleshooting skills:?
Look at working one, fix broken model.
Monkey see, monkey do
Where's my 35 minute paper tape of the X O . pinup girl on a
stool?
73 Bo W4GHV for SEVENTY YEARS?
|
Re: For all you RTTY / Teletype fans out there..
Nice! I had 2 Model 15s.?
My troubleshooting skills:?
Look at working one, fix broken model.
Monkey see, monkey do
Where's my 35 minute paper tape of the X O . pinup girl on a stool?
73 Bo W4GHV for SEVENTY YEARS?
|
Re: Guide to New Rig backend creation?
How to add a new transceiver
to flrig
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Suggest using an existing rig (.cxx, .h) files as a template for
the new rig.? Choose a file that will use similar CAT commands.
After the new files have been added and the three files updated
you will need to recreate the build scripts.? From the top level
flrig directory:
? $ autoreconf
? $ ./configure
? $ make
David
On 9/23/24 12:00, Dave, G?WBX via
groups.io wrote:
toggle quoted message
Show quoted text
Afternoon
All...? (From a wet day in the UK.)
Some time ago (back in the day of Linux Mint 15!), I helped "flesh
out" a new(ish) backend for the Kenwood TS870.? Receiving much
welcome help and hints from Dave and Ed via this list.
Sometime later (years.) ? ISTR there was mention of (or proposal
for) a documented guide for a "How to" showing the correct way to
create a new radio backend for Flrig, doing that either based on
an existing similar rig, or new "from scratch".
I also seem to recall, Dave 'HKJ sent me something around the same
time, but can I find that, anywhere?? Of course not.? Even if I
could, I suspect things have changed within Flrig since then...??
I can't see anything in the wiki area either.
So, is there an up-to-date document anywhere, describing how to
create and integrate a new radio backend these days?
Only ask as I have acquired an Icom IC-R9000 for the shack, and
would like to "integrate it into the fold" as it were.
(Hamlib knows of the radio, but that's not entirely complete, and
is very buggy too, though it proves that the USB<>CIV device
and radio work OK together.)
Any info re the above welcome.
73.
Dave G0WBX.
Currently running LMDE 6 (Faye) & able to build Fldigi and
friends from source without issues.
|
FLRIG with Windows, Linux and the MAC
Howdy all,
?
First post here!
?
I've been a Linux user since the mid 1990's starting with Redhat 7.x, 8.0 and 9.x when they switched to Fedora.
?
I then switched to SuSE Linux at around version 9.0 and have stayed with OpenSuSE to this day using Leap 15.5 on my 6-core AMD desktop and Leap 15.6 on my Mid 2012 MacBook Pro (Core i7)
?
I have had FLRIG and FLDIGI working on Winblows, and many earlier versions of OpenSuSE? (even KDE Neon) and it has always worked well!
?
Interesting problem now though.
?
I cannot get the FLRIG S-meter, power, SWR etc (except Voltage display) to work now using the Linux version on the MACBook Pro nor can I get it to work on my other (newer early 2015) MacBook Pro (running MAC OS Monterey)
?
All the above operating systems are connected to an ICOM IC-705 (not at the same time!!)
?
Anyone know what obvious problem I have that I cannot see?
?
Thanks,
?
?
--
-----------------------------------
73/Rick
W4XA
Western? Wa
|
Flrig TS870 TX power control.
Hi.
As part of warming up the grey cell, I pulled the latest Flrig Alpha (2.0.05.75).
With my TS870s.??? I noticed the "Power" slider was able to go down to 0.? (The rig's control ability only goes down to 10W.)
So..? I tweaked the code in TS870s.h
From line 82...
//? int? get_swr();
??? int? get_power_out();
?? ?double get_power_control();
Is now...
//? int? get_swr();
??? int? get_power_out();
??? double get_power_control();
//? void get_pc_min_max_step(double &, double &, double &) {
?? ?void get_pc_min_max_step(double &min, double &max, double &step) {
?? ???? min = 10; max = 100; step = 1; }? // wbx4
??? void set_power_control(double val);? // relocated from original line 94 wbx4
It builds without error, and the resulting "Pwr" control on the UI, is now scaled 10 to 100W and behaves well.
Hopefully, the TS870s.h file is not referenced by any other backend.
( That is something I've yet to figure out, how to trace what other code might call what I'm looking at / working on.
I don't think even Doxygen can help with that, at least asking vastly more experienced coders in the past hasn't been fruitful.
Tracing forward call's is easy of course, but backwards across multiple source files?? Anyone know? )
Anyway...? Bouquets or Brickbats welcome.
73
Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Mike, K6GTE
Steve, K1EL
Dave, W1HKJ
Bo, W4GHV