From f6fvy at free.fr  Sun May  2 17:35:34 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Sun, 2 May 2021 17:35:34 +0200
Subject: [WT-support] Modification of the Italian Provinces list
Message-ID: <f6aa3a23-d702-4f83-2960-c514ece8f68e@free.fr>

Hi all

If you took part in the ARI DX contest this week-end, you probably 
noticed that the provinces list has been slightly modified since the 
last update of this contest in Win-Test. Several provinces abbreviations 
are no longer in use, while others has appeared.

I released a dev version - build 829 - in the nightly builds repository 
that takes these modificattions into account, so your log should be flag 
mults as "?" anymore, and your score will be correctly computed.

Thanks to Ben DL6RAI and Pierre HB9AMO for their reports.

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From jjreisert at alum.mit.edu  Tue May  4 03:55:41 2021
From: jjreisert at alum.mit.edu (Jim Reisert AD1C)
Date: Mon, 03 May 2021 19:55:41 -0600
Subject: [WT-support] CTY-3111 Country Files - 04 May 2021
Message-ID: <20210504015600.88C26208013@mx.glou.fr>

The Country (CTY) Files were updated on 04 May 2021:

    https://www.country-files.com/cty-3111-04-may-2021/

For installation instructions, start at:

    https://www.country-files.com/

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:

   https://www.country-files.com/big-cty-04-may-2021/

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:

   https://www.country-files.com/feed/

Here are the release notes:

    4 May 2021 (CTY-3111)
    VER20210504, Version entity is Indonesia, YB

    Added/changed Entities/Prefixes/Callsigns:

	* GB0SI is Shetland Islands, *GM/s
	* B3CRA is China, BY in CQ zone 23, ITU zone 33
	* B9CRA is China, BY in CQ zone 23, ITU zone 43
	* GB0ME and GB0SI are both Scotland, GM
	* AH6JS, AH6SU, KH6GK and W9CF are all United States, K in CQ zone 3, ITU zone 6
	* WA9JBR is United States, K in CQ zone 4, ITU zone 7
	* AA2MA, AH2AV and K7ZYV are all United States, K in CQ zone 4, ITU zone 8
	* KP3U and NL7FJ are both United States, K in CQ zone 5, ITU zone 8
	* K6K, KF7QMX and WL7CSW/H are all Hawaii, KH6
	* K4WGX, KD5KVP and WB8BRU are all Alaska, KL
	* KP4PRE/EVNT and N5YIZ are both Puerto Rico, KP4
	* R9OM/6, RA2FDX/3, UA8CAD/3 and UA9QCP/3 are all European Russia, UA
	* RZ5D/9 is in ITU zone 30, not ITU zone 32
	* RZ5D/9 is in CQ zone 17, not CQ zone 18
	* RM9T/P and UB8S/P are both Asiatic Russia, UA9 in CQ zone 16
	* VK6SJ/4 is Australia, VK in ITU zone 55
	* VK2BYF/9 is Lord Howe Island, VK9L

    Removed Entities/Prefixes/Callsigns:

	* EA6LU/P in Spain, EA
	* GB8STM in Northern Ireland, GI
	* GB2CR in Scotland, GM
	* AB4EJ, AJ6T, K0AU, K2DSW, K6BFL, K9MWM, N7NG, NZ6T, W1DGL, W6DVS,
	  W9PL and WU0B in United States, K
	* KB3HXI, KD4GVR and KJ7UOI in Hawaii, KH6
	* KC2GRZ in Puerto Rico, KP4
	* LU1AAC/D, LU1IG/I, LU1QAC/H, LU5EPB/D, LU7ARS/D, LU7CC/E, LU8AJM/D,
	  LU9CHL/D and LW2ETF/D in Argentina, LU
	* R0AI/3, R21BLIN, R21GDB, R90PAR, RA9UEZ/6, RA9UUY/6, RJ4P, RK4P,
	  RM9T/P, RP76SFL, RP76VD, RP76VP, RP76VZ, RU9SO/6, UA0QNE/3 and UB8S/P
	  in European Russia, UA
	* RP76MW in Kaliningrad, UA2
	* R8MZ/9, RP76AM and RT8T in Asiatic Russia, UA9
	* VY0AA in Canada, VE
	* VI100AF and VK100AF in Australia, VK

73 - Jim AD1C

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://www.ad1c.us




From dl2alf at arcor.de  Tue May  4 06:56:09 2021
From: dl2alf at arcor.de (dl2alf)
Date: Tue, 4 May 2021 06:56:09 +0200
Subject: [WT-support] OmniRig & CW keying
Message-ID: <000b01d740a1$cc4fc090$64ef41b0$@de>

Hi all,

 

after running the May VHF contest here with new setup I am facing some new
problems.

My aimed setup is as follows:

 

-          IC-9700

-          CAT via OmniRig (mandatory due to multiple access from different
applications to rig needed) 

-          Win-Test V4.30

 

The only significant difference to previous setup is the connection via
OmniRig instead of a plain serial connection.

Everything went well until I tried to use the CW keyer from Win-Test
(Traditionally, CW keying was done via RTS/DTR status lines).

This function completely fails, so that I had to switch back to traditional
setup.

Meanwhile, I did some investigations on this topic.

 

I see two ways to get CW keying via OmniRig working:

 

#1: Use OmniRig status lines similar to serial connection

- feature is available at the OmniRig ActiveX interface
- is not supported by Win-Test so far
- may cause timing problems

#2: Use CW send text command supported by ICOM

- possible to send any text via CI-V
- I modified the great IcomScripts collection by Bob, N6TV, to get this
working (add IC-9700 as device, add some code for escape handling)

I?d prefer #2 BUT:

 

If I define a new F1 command script for CQ, I was not able to access the
standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text
in the script.

Not the best choice. Furthermore, I was not able to send it repeatedly as a
CQ loop does.

 

The best solution I came up with so far is to redefine CW standard texts
into ?#ICOMPLAY(?
CQ
CQ
 DE
?) which runs the ICOM send text script with the
original text message.

Works but is also not the best choice as the defines seem to be stored
contest-specific in the *.wt4 files.

 

Any ideas?

 

73 de Frank, DL2ALF

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210504/12b1b5d4/attachment.html>

From n6tv at arrl.net  Tue May  4 07:12:44 2021
From: n6tv at arrl.net (Bob Wilson, N6TV)
Date: Mon, 3 May 2021 22:12:44 -0700
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <000b01d740a1$cc4fc090$64ef41b0$@de>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
Message-ID: <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>

Frank,

There's a much easier solution.

The IC-9700 defines *two* virtual serial ports.  Let's say they are
assigned to COM5 (A) and COM6 (B).  You can find out which is A and which
is B by looking at the Windows Device Manager, Ports, COM5, Properties,
Details, Device Instance Path.  The last letter indicates which is COM A
(rig control) and which is COM B (can be used for CW / PTT via DTR and
RTS).  For screenshots see my recently updated presentation:
https://bit.ly/USBserial2021 .

Assign COM5 to OmniRig Rig 1, Radio:  IC-9700.

In Win-Test set *Radio 1* type to *OmniRig*.
Do not select *COM5*.
Set *COM6* to "Other Interface" in Win-Test, with *DTR=CW*, *RTS=PTT*

In the IC-9700 menu:

SET > Connectors > *USB Send/Keying*
Set *USB SEND* to *USB(B) RTS*
Set USB *Keying(CW)* to *USB (B) DTR*


Now OmniRig uses COM5 for rig control and Win-Test uses COM6 for CW and PTT
with DTR and RTS keying.  Connect paddle into radio for hand sending.  I've
just updated my IcomScripts to support the IC-9700 scope and other
controls.  Still testing.  Will send you off list.

73,
Bob, N6TV


On Mon, May 3, 2021 at 9:56 PM dl2alf <dl2alf at arcor.de> wrote:

> Hi all,
>
>
>
> after running the May VHF contest here with new setup I am facing some new
> problems.
>
> My aimed setup is as follows:
>
>
>
> -          IC-9700
>
> -          CAT via OmniRig (mandatory due to multiple access from
> different applications to rig needed)
>
> -          Win-Test V4.30
>
>
>
> The only significant difference to previous setup is the connection via
> OmniRig instead of a plain serial connection.
>
> Everything went well until I tried to use the CW keyer from Win-Test
> (Traditionally, CW keying was done via RTS/DTR status lines).
>
> This function completely fails, so that I had to switch back to
> traditional setup.
>
> Meanwhile, I did some investigations on this topic.
>
>
>
> I see two ways to get CW keying via OmniRig working:
>
>
>
> #1: Use OmniRig status lines similar to serial connection
>
> - feature is available at the OmniRig ActiveX interface
> - is not supported by Win-Test so far
> - may cause timing problems
>
> #2: Use CW send text command supported by ICOM
>
> - possible to send any text via CI-V
> - I modified the great IcomScripts collection by Bob, N6TV, to get this
> working (add IC-9700 as device, add some code for escape handling)
>
> I?d prefer #2 BUT:
>
>
>
> If I define a new F1 command script for CQ, I was not able to access the
> standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text
> in the script.
>
> Not the best choice. Furthermore, I was not able to send it repeatedly as
> a CQ loop does.
>
>
>
> The best solution I came up with so far is to redefine CW standard texts
> into ?#ICOMPLAY(??CQ?CQ? DE??) which runs the ICOM send text script with
> the original text message.
>
> Works but is also not the best choice as the defines seem to be stored
> contest-specific in the *.wt4 files.
>
>
>
> Any ideas?
>
>
>
> 73 de Frank, DL2ALF
>
>
>
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210503/b1374171/attachment-0001.html>

From dl2alf at arcor.de  Tue May  4 17:43:31 2021
From: dl2alf at arcor.de (dl2alf)
Date: Tue, 4 May 2021 17:43:31 +0200
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
Message-ID: <002a01d740fc$3c013f90$b403beb0$@de>

Hi Bob,

 

Thank you for your quick response (scripts also arrived meanwhile, tnx). I?ll go and check them asap.

I remember that I?ve struggled quite a while with the COM interfaces of the IC-9700 to get it working in general but we will see.

 

I forgot to mention that I?m facing similar issues with OmniRig & IC-7300 + Elecraft KX-3 in our contest setup?

 

73 de Frank, DL2ALF

 

 

Von: support-bounces at win-test.com [mailto:support-bounces at win-test.com] Im Auftrag von Bob Wilson, N6TV
Gesendet: Dienstag, 4. Mai 2021 07:13
An: Win-Test Reflector
Betreff: Re: [WT-support] OmniRig & CW keying

 

Frank,

 

There's a much easier solution.

 

The IC-9700 defines two virtual serial ports.  Let's say they are assigned to COM5 (A) and COM6 (B).  You can find out which is A and which is B by looking at the Windows Device Manager, Ports, COM5, Properties, Details, Device Instance Path.  The last letter indicates which is COM A (rig control) and which is COM B (can be used for CW / PTT via DTR and RTS).  For screenshots see my recently updated presentation:  https://bit.ly/USBserial2021 .

 

Assign COM5 to OmniRig Rig 1, Radio:  IC-9700.

 

In Win-Test set Radio 1 type to OmniRig.

Do not select COM5.

Set COM6 to "Other Interface" in Win-Test, with DTR=CW, RTS=PTT

 

In the IC-9700 menu:

 

SET > Connectors > USB Send/Keying

Set USB SEND to USB(B) RTS

Set USB Keying(CW) to USB (B) DTR

 

Now OmniRig uses COM5 for rig control and Win-Test uses COM6 for CW and PTT with DTR and RTS keying.  Connect paddle into radio for hand sending.  I've just updated my IcomScripts to support the IC-9700 scope and other controls.  Still testing.  Will send you off list.

 

73,

Bob, N6TV

 

 

On Mon, May 3, 2021 at 9:56 PM dl2alf <dl2alf at arcor.de> wrote:

Hi all,

 

after running the May VHF contest here with new setup I am facing some new problems.

My aimed setup is as follows:

 

-          IC-9700

-          CAT via OmniRig (mandatory due to multiple access from different applications to rig needed) 

-          Win-Test V4.30

 

The only significant difference to previous setup is the connection via OmniRig instead of a plain serial connection.

Everything went well until I tried to use the CW keyer from Win-Test (Traditionally, CW keying was done via RTS/DTR status lines).

This function completely fails, so that I had to switch back to traditional setup.

Meanwhile, I did some investigations on this topic.

 

I see two ways to get CW keying via OmniRig working:

 

#1: Use OmniRig status lines similar to serial connection

- feature is available at the OmniRig ActiveX interface
- is not supported by Win-Test so far
- may cause timing problems

#2: Use CW send text command supported by ICOM

- possible to send any text via CI-V
- I modified the great IcomScripts collection by Bob, N6TV, to get this working (add IC-9700 as device, add some code for escape handling)

I?d prefer #2 BUT:

 

If I define a new F1 command script for CQ, I was not able to access the standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text in the script.

Not the best choice. Furthermore, I was not able to send it repeatedly as a CQ loop does.

 

The best solution I came up with so far is to redefine CW standard texts into ?#ICOMPLAY(??CQ?CQ? DE??) which runs the ICOM send text script with the original text message.

Works but is also not the best choice as the defines seem to be stored contest-specific in the *.wt4 files.

 

Any ideas?

 

73 de Frank, DL2ALF

 

 

_______________________________________________
Support mailing list
support at win-test.com
http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210504/ae00a7ee/attachment.html>

From n6tv at arrl.net  Tue May  4 18:29:31 2021
From: n6tv at arrl.net (Bob Wilson, N6TV)
Date: Tue, 4 May 2021 09:29:31 -0700
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <002a01d740fc$3c013f90$b403beb0$@de>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
 <002a01d740fc$3c013f90$b403beb0$@de>
Message-ID: <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>

There should be no need to struggle with COM interfaces of the IC-9700.
Just install the driver well before you connect the USB cable.

Everything you need to know, including how to recover from connection
problems, is covered in my presentation (https://bit.ly/USBserial2021).  If
you can't figure something out, install TeamViewer and I'll help you
remotely.

Note that if you move the rig's USB cable to a different USB port, it may
end up on a different internal "USB hub", so it will be assigned new COM
port numbers.

For simultaneous rig control and DTR/RTS keying of the IC-7300 when using
OmniRig, the most economical solution is to buy an FTDI to CI-V cable
(CT-17 equivalent), use that new connection for rig control via the REMOTE
(CI-V) jack, and use the ONE virtual serial port provided by the IC-7300
USB connector for CW and PTT keying via DTR and RTS, and sound card.

For the KX3, I'd recommend my Serial Box USB which provides the CW and PTT
keying circuits, plus a KXUSB for rig control, or use an S-BOX-USB-2 which
provides two independent serial ports, one for rig control, one for DTR/RTS
keying, so no need for the KXUSB cable.

https://www.kkn.net/~n6tv/S-BOX/Features.html#KeyingExampleKX3  (shows one
port being used for both, but there are many other configurations
available).

73,
Bob, N6TV
https://bit.ly/S-BOX


On Tue, May 4, 2021 at 8:44 AM dl2alf <dl2alf at arcor.de> wrote:

> Hi Bob,
>
>
>
> Thank you for your quick response (scripts also arrived meanwhile, tnx).
> I?ll go and check them asap.
>
> I remember that I?ve struggled quite a while with the COM interfaces of
> the IC-9700 to get it working in general but we will see.
>
>
>
> I forgot to mention that I?m facing similar issues with OmniRig & IC-7300
> + Elecraft KX-3 in our contest setup?
>
>
>
> 73 de Frank, DL2ALF
>
>
>
>
>
> *Von:* support-bounces at win-test.com [mailto:support-bounces at win-test.com] *Im
> Auftrag von *Bob Wilson, N6TV
> *Gesendet:* Dienstag, 4. Mai 2021 07:13
> *An:* Win-Test Reflector
> *Betreff:* Re: [WT-support] OmniRig & CW keying
>
>
>
> Frank,
>
>
>
> There's a much easier solution.
>
>
>
> The IC-9700 defines *two* virtual serial ports.  Let's say they are
> assigned to COM5 (A) and COM6 (B).  You can find out which is A and which
> is B by looking at the Windows Device Manager, Ports, COM5, Properties,
> Details, Device Instance Path.  The last letter indicates which is COM A
> (rig control) and which is COM B (can be used for CW / PTT via DTR and
> RTS).  For screenshots see my recently updated presentation:
> https://bit.ly/USBserial2021 .
>
>
>
> Assign COM5 to OmniRig Rig 1, Radio:  IC-9700.
>
>
>
> In Win-Test set *Radio 1* type to *OmniRig*.
>
> Do not select *COM5*.
>
> Set *COM6* to "Other Interface" in Win-Test, with *DTR=CW*, *RTS=PTT*
>
>
>
> In the IC-9700 menu:
>
>
>
> SET > Connectors > *USB Send/Keying*
>
> Set *USB SEND* to *USB(B) RTS*
>
> Set USB *Keying(CW)* to *USB (B) DTR*
>
>
>
> Now OmniRig uses COM5 for rig control and Win-Test uses COM6 for CW and
> PTT with DTR and RTS keying.  Connect paddle into radio for hand sending.
> I've just updated my IcomScripts to support the IC-9700 scope and other
> controls.  Still testing.  Will send you off list.
>
>
>
> 73,
>
> Bob, N6TV
>
>
>
>
>
> On Mon, May 3, 2021 at 9:56 PM dl2alf <dl2alf at arcor.de> wrote:
>
> Hi all,
>
>
>
> after running the May VHF contest here with new setup I am facing some new
> problems.
>
> My aimed setup is as follows:
>
>
>
> -          IC-9700
>
> -          CAT via OmniRig (mandatory due to multiple access from
> different applications to rig needed)
>
> -          Win-Test V4.30
>
>
>
> The only significant difference to previous setup is the connection via
> OmniRig instead of a plain serial connection.
>
> Everything went well until I tried to use the CW keyer from Win-Test
> (Traditionally, CW keying was done via RTS/DTR status lines).
>
> This function completely fails, so that I had to switch back to
> traditional setup.
>
> Meanwhile, I did some investigations on this topic.
>
>
>
> I see two ways to get CW keying via OmniRig working:
>
>
>
> #1: Use OmniRig status lines similar to serial connection
>
> - feature is available at the OmniRig ActiveX interface
> - is not supported by Win-Test so far
> - may cause timing problems
>
> #2: Use CW send text command supported by ICOM
>
> - possible to send any text via CI-V
> - I modified the great IcomScripts collection by Bob, N6TV, to get this
> working (add IC-9700 as device, add some code for escape handling)
>
> I?d prefer #2 BUT:
>
>
>
> If I define a new F1 command script for CQ, I was not able to access the
> standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text
> in the script.
>
> Not the best choice. Furthermore, I was not able to send it repeatedly as
> a CQ loop does.
>
>
>
> The best solution I came up with so far is to redefine CW standard texts
> into ?#ICOMPLAY(??CQ?CQ? DE??) which runs the ICOM send text script with
> the original text message.
>
> Works but is also not the best choice as the defines seem to be stored
> contest-specific in the *.wt4 files.
>
>
>
> Any ideas?
>
>
>
> 73 de Frank, DL2ALF
>
>
>
>
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210504/ca60a651/attachment-0001.html>

From f6fvy at free.fr  Tue May  4 18:54:33 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Tue, 4 May 2021 18:54:33 +0200
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
 <002a01d740fc$3c013f90$b403beb0$@de>
 <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
Message-ID: <eeeb2062-51bf-7584-1b34-d62cc63e7048@free.fr>

Hi all

Le 04/05/2021 ? 18:29, Bob Wilson, N6TV a ?crit?:

> Everything you need to know, including how to recover from connection 
> problems, is covered in my presentation (https://bit.ly/USBserial2021 
> <https://bit.ly/USBserial2021>). 

I strongly recommend this presentation for everyone. Lots of 
information, tips and tricks regarding the "USB serial" connections.

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From dl2alf at arcor.de  Wed May  5 17:02:35 2021
From: dl2alf at arcor.de (dl2alf)
Date: Wed, 5 May 2021 17:02:35 +0200
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
 <002a01d740fc$3c013f90$b403beb0$@de>
 <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
Message-ID: <004a01d741bf$ae7633a0$0b629ae0$@de>

Hi Bob & Larry,

 

Thanks for the feedback & hints. (@Bob: Nice presentation BTW)

I?m quite familiar with these things?

 

Using a second COM only for keying is an option. At least I had to cope with limited space and few USB ports in our 19? contest rack.

With all these (free of charge) port emulators and routers I didn?t get happy in the past.

I?ve programmed an own COM router with com0com a while ago but this was for ICOM devices only.

All those solutions a not very handy?

 

Currently, I?ve done a full port of OmniRig sourc code to managed .NET running on Windows & Linux/Mono for the use with AirScout (without the ActiveX COM interface).

Therefore I know that OmniRig does support setting/resetting of status lines via ActiveX interface. But I didn?t check the timing behavior so far.

All of this would not help because Win-Test does not support keying via OmniRig so far.

 

@Larry: 

 

The OmniRig ActiveX object gives you a ?PortBits? interface which allows read/write access to the RTS and DTR line (and read access to the others)

Is it worth to give a try implementing this in Win-Test? 

 

If not, I can live with above mentioned solution, tnx.

 

73 de Frank, DL2ALF

 

Von: support-bounces at win-test.com [mailto:support-bounces at win-test.com] Im Auftrag von Bob Wilson, N6TV
Gesendet: Dienstag, 4. Mai 2021 18:30
An: Win-Test Reflector
Betreff: Re: [WT-support] OmniRig & CW keying

 

There should be no need to struggle with COM interfaces of the IC-9700.  Just install the driver well before you connect the USB cable.

 

Everything you need to know, including how to recover from connection problems, is covered in my presentation (https://bit.ly/USBserial2021).  If you can't figure something out, install TeamViewer and I'll help you remotely.

 

Note that if you move the rig's USB cable to a different USB port, it may end up on a different internal "USB hub", so it will be assigned new COM port numbers.

 

For simultaneous rig control and DTR/RTS keying of the IC-7300 when using OmniRig, the most economical solution is to buy an FTDI to CI-V cable (CT-17 equivalent), use that new connection for rig control via the REMOTE (CI-V) jack, and use the ONE virtual serial port provided by the IC-7300 USB connector for CW and PTT keying via DTR and RTS, and sound card.

 

For the KX3, I'd recommend my Serial Box USB which provides the CW and PTT keying circuits, plus a KXUSB for rig control, or use an S-BOX-USB-2 which provides two independent serial ports, one for rig control, one for DTR/RTS keying, so no need for the KXUSB cable.

 

https://www.kkn.net/~n6tv/S-BOX/Features.html#KeyingExampleKX3  (shows one port being used for both, but there are many other configurations available).




73,

Bob, N6TV

https://bit.ly/S-BOX

 

 

On Tue, May 4, 2021 at 8:44 AM dl2alf <dl2alf at arcor.de> wrote:

Hi Bob,

 

Thank you for your quick response (scripts also arrived meanwhile, tnx). I?ll go and check them asap.

I remember that I?ve struggled quite a while with the COM interfaces of the IC-9700 to get it working in general but we will see.

 

I forgot to mention that I?m facing similar issues with OmniRig & IC-7300 + Elecraft KX-3 in our contest setup?

 

73 de Frank, DL2ALF

 

 

Von: support-bounces at win-test.com [mailto:support-bounces at win-test.com] Im Auftrag von Bob Wilson, N6TV
Gesendet: Dienstag, 4. Mai 2021 07:13
An: Win-Test Reflector
Betreff: Re: [WT-support] OmniRig & CW keying

 

Frank,

 

There's a much easier solution.

 

The IC-9700 defines two virtual serial ports.  Let's say they are assigned to COM5 (A) and COM6 (B).  You can find out which is A and which is B by looking at the Windows Device Manager, Ports, COM5, Properties, Details, Device Instance Path.  The last letter indicates which is COM A (rig control) and which is COM B (can be used for CW / PTT via DTR and RTS).  For screenshots see my recently updated presentation:  https://bit.ly/USBserial2021 .

 

Assign COM5 to OmniRig Rig 1, Radio:  IC-9700.

 

In Win-Test set Radio 1 type to OmniRig.

Do not select COM5.

Set COM6 to "Other Interface" in Win-Test, with DTR=CW, RTS=PTT

 

In the IC-9700 menu:

 

SET > Connectors > USB Send/Keying

Set USB SEND to USB(B) RTS

Set USB Keying(CW) to USB (B) DTR

 

Now OmniRig uses COM5 for rig control and Win-Test uses COM6 for CW and PTT with DTR and RTS keying.  Connect paddle into radio for hand sending.  I've just updated my IcomScripts to support the IC-9700 scope and other controls.  Still testing.  Will send you off list.

 

73,

Bob, N6TV

 

 

On Mon, May 3, 2021 at 9:56 PM dl2alf <dl2alf at arcor.de> wrote:

Hi all,

 

after running the May VHF contest here with new setup I am facing some new problems.

My aimed setup is as follows:

 

-          IC-9700

-          CAT via OmniRig (mandatory due to multiple access from different applications to rig needed) 

-          Win-Test V4.30

 

The only significant difference to previous setup is the connection via OmniRig instead of a plain serial connection.

Everything went well until I tried to use the CW keyer from Win-Test (Traditionally, CW keying was done via RTS/DTR status lines).

This function completely fails, so that I had to switch back to traditional setup.

Meanwhile, I did some investigations on this topic.

 

I see two ways to get CW keying via OmniRig working:

 

#1: Use OmniRig status lines similar to serial connection

- feature is available at the OmniRig ActiveX interface
- is not supported by Win-Test so far
- may cause timing problems

#2: Use CW send text command supported by ICOM

- possible to send any text via CI-V
- I modified the great IcomScripts collection by Bob, N6TV, to get this working (add IC-9700 as device, add some code for escape handling)

I?d prefer #2 BUT:

 

If I define a new F1 command script for CQ, I was not able to access the standard CW messages defined as $F1 .. $F8 so I must hardcode a new CQ text in the script.

Not the best choice. Furthermore, I was not able to send it repeatedly as a CQ loop does.

 

The best solution I came up with so far is to redefine CW standard texts into ?#ICOMPLAY(??CQ?CQ? DE??) which runs the ICOM send text script with the original text message.

Works but is also not the best choice as the defines seem to be stored contest-specific in the *.wt4 files.

 

Any ideas?

 

73 de Frank, DL2ALF

 

 

_______________________________________________
Support mailing list
support at win-test.com
http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support

_______________________________________________
Support mailing list
support at win-test.com
http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210505/413bc67a/attachment-0001.html>

From f6fvy at free.fr  Thu May  6 12:49:15 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Thu, 6 May 2021 12:49:15 +0200
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <004a01d741bf$ae7633a0$0b629ae0$@de>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
 <002a01d740fc$3c013f90$b403beb0$@de>
 <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
 <004a01d741bf$ae7633a0$0b629ae0$@de>
Message-ID: <f6f713f2-1acd-b6a9-9791-5bc28160a828@free.fr>

Hi Franck et al.

Le 05/05/2021 ? 17:02, dl2alf a ?crit?:

> The OmniRig ActiveX object gives you a ?PortBits? interface which allows 
> read/write access to the RTS and DTR line (and read access to the others)
> 
> Is it worth to give a try implementing this in Win-Test?
> 
> If not, I can live with above mentioned solution, tnx.

Thanks for the info. I will take a look, but as the source code related 
to Omnirig hasn't been touched since 2009, I clearly need some time to 
refresh my memory to dig into ;-)  I'm currently busy on other topics 
right now, but I add it to my TODO.

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From dl2alf at arcor.de  Thu May  6 15:10:20 2021
From: dl2alf at arcor.de (dl2alf)
Date: Thu, 6 May 2021 15:10:20 +0200
Subject: [WT-support] OmniRig & CW keying
In-Reply-To: <f6f713f2-1acd-b6a9-9791-5bc28160a828@free.fr>
References: <000b01d740a1$cc4fc090$64ef41b0$@de>
 <CAOmNKGJewWZkH=LmpwH-sd8_Cw3Yk93ityW36XNB2gTFwd9AGA@mail.gmail.com>
 <002a01d740fc$3c013f90$b403beb0$@de>
 <CAOmNKG+Nv0_PgVjA_YXVqF88VjWSyDiBt_3Nwvi-rDrSMKC-8g@mail.gmail.com>
 <004a01d741bf$ae7633a0$0b629ae0$@de>
 <f6f713f2-1acd-b6a9-9791-5bc28160a828@free.fr>
Message-ID: <007d01d74279$2abb8f50$8032adf0$@de>

Hi Larry,

tnx, your effords are always appreciated.

73 de Frank, DL2ALF

> -----Urspr?ngliche Nachricht-----
> Von: support-bounces at win-test.com [mailto:support-bounces at win-test.com] Im
> Auftrag von Laurent HAAS - F6FVY
> Gesendet: Donnerstag, 6. Mai 2021 12:49
> An: support at win-test.com
> Betreff: Re: [WT-support] OmniRig & CW keying
> 
> Hi Franck et al.
> 
> Le 05/05/2021 ? 17:02, dl2alf a ?crit :
> 
> > The OmniRig ActiveX object gives you a ?PortBits? interface which allows
> > read/write access to the RTS and DTR line (and read access to the others)
> >
> > Is it worth to give a try implementing this in Win-Test?
> >
> > If not, I can live with above mentioned solution, tnx.
> 
> Thanks for the info. I will take a look, but as the source code related
> to Omnirig hasn't been touched since 2009, I clearly need some time to
> refresh my memory to dig into ;-)  I'm currently busy on other topics
> right now, but I add it to my TODO.
> 
> 73
> 
> Larry - F6FVY
> 
> --
> 
> All of humanity's problems stem from man's inability
> to sit quietly in a room alone.
> 
> Blaise Pascal, Pens?es
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support


From f6fvy at free.fr  Fri May  7 19:12:44 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Fri, 7 May 2021 19:12:44 +0200
Subject: [WT-support] CQ-M Scoring
Message-ID: <46a18237-98bb-0489-3c84-140624fb5ba2@free.fr>

Hi

The CQ-M scoring has silently been modified

http://cqm.srr.ru/en-rules-2/

It makes a difference for intra-entity points that are the same as 
working the same continent (2 pts instead of 1), and EU and AS are now 
considered as a single continent (Eurasia).

I just build a dev version (build #831) that takes this new scoring into 
account.

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From rifattultak2 at gmail.com  Sun May  9 05:07:45 2021
From: rifattultak2 at gmail.com (RIFAT TULTAK)
Date: Sun, 9 May 2021 06:07:45 +0300
Subject: [WT-support] cw problem
Message-ID: <CAAne76MUFmydKgefG+ojVrPoH28nEKvJ_W7B7rOfO5JYMVWRdw@mail.gmail.com>

Hello,

The rates of cw code signal sent from the software are not good. Point 1,
Line 3 rate is not good. Line short. How can i fix this. Thanks for the
answer.
73

TA2SE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210509/38244108/attachment.html>

From n6tv at arrl.net  Sun May  9 05:16:34 2021
From: n6tv at arrl.net (Bob Wilson, N6TV)
Date: Sat, 8 May 2021 20:16:34 -0700
Subject: [WT-support] cw problem
In-Reply-To: <CAAne76MUFmydKgefG+ojVrPoH28nEKvJ_W7B7rOfO5JYMVWRdw@mail.gmail.com>
References: <CAAne76MUFmydKgefG+ojVrPoH28nEKvJ_W7B7rOfO5JYMVWRdw@mail.gmail.com>
Message-ID: <CAOmNKGKpy1nWdpxr72h2n36FCNnr8jqW5WdN=_z3bzB_rSX8Mw@mail.gmail.com>

Use the text command WEIGHT in the logging window to adjust dot/dash ratio.

Use SETUP command to increase Keying Compensation if every element is too
short by fixed amount of milliseconds.

Set Windows 10 Control Panel, Power Options to "High Performance" if needed.

73,
Bob, N6TV

On Sat, May 8, 2021, 8:08 PM RIFAT TULTAK <rifattultak2 at gmail.com> wrote:

> Hello,
>
> The rates of cw code signal sent from the software are not good. Point 1,
> Line 3 rate is not good. Line short. How can i fix this. Thanks for the
> answer.
> 73
>
> TA2SE
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210508/bb6090d0/attachment.html>

From rifattultak2 at gmail.com  Sun May  9 05:46:23 2021
From: rifattultak2 at gmail.com (RIFAT TULTAK)
Date: Sun, 9 May 2021 06:46:23 +0300
Subject: [WT-support] cw problem
In-Reply-To: <CAOmNKGKpy1nWdpxr72h2n36FCNnr8jqW5WdN=_z3bzB_rSX8Mw@mail.gmail.com>
References: <CAAne76MUFmydKgefG+ojVrPoH28nEKvJ_W7B7rOfO5JYMVWRdw@mail.gmail.com>
 <CAOmNKGKpy1nWdpxr72h2n36FCNnr8jqW5WdN=_z3bzB_rSX8Mw@mail.gmail.com>
Message-ID: <CAAne76PnsTFhMNn2JtY4bGiB__UWTayXH_SBS0tuoCORPphwRw@mail.gmail.com>

Tnx  Bob,

Problem solved.
Commands > cw weight ''3''  (my setup ''2'')

73 GL
TA2SE

Bob Wilson, N6TV <n6tv at arrl.net>, 9 May 2021 Paz, 06:16 tarihinde ?unu
yazd?:

> Use the text command WEIGHT in the logging window to adjust dot/dash ratio.
>
> Use SETUP command to increase Keying Compensation if every element is too
> short by fixed amount of milliseconds.
>
> Set Windows 10 Control Panel, Power Options to "High Performance" if
> needed.
>
> 73,
> Bob, N6TV
>
> On Sat, May 8, 2021, 8:08 PM RIFAT TULTAK <rifattultak2 at gmail.com> wrote:
>
>> Hello,
>>
>> The rates of cw code signal sent from the software are not good. Point 1,
>> Line 3 rate is not good. Line short. How can i fix this. Thanks for the
>> answer.
>> 73
>>
>> TA2SE
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210509/e1d60eaa/attachment.html>

From f6fvy at free.fr  Sat May 15 13:36:56 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Sat, 15 May 2021 13:36:56 +0200
Subject: [WT-support] FTDX101
In-Reply-To: <006801d7305b$6356d070$2a047150$@gmail.com>
References: <001201d7303f$e9279fc0$bb76df40$@gmail.com>
 <08a3a643-8bfb-4b90-5f90-bb3ea77f703b@free.fr>
 <CAOmNKGLRyd4QV5v1DPCy0tNvjq-yQZfb0E2tTmbsyp8o6xrQHg@mail.gmail.com>
 <006801d7305b$6356d070$2a047150$@gmail.com>
Message-ID: <b88bed41-bd89-288a-7f31-71d4dac4d25f@free.fr>

Hi Don and FTDX101 users

Le 13/04/2021 ? 13:51, Don Beattie a ?crit?:

> Thanks Bob ? it looks like the truly broke it. Not a good way to release 
> F/W.

FYI, Yaesu has released a newer version labelled 202105 that solves this 
issue and fixes the CAT incompatibility with Win-Test (and others).

Tnx F6CEL for information.

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From jjreisert at alum.mit.edu  Mon May 17 02:51:51 2021
From: jjreisert at alum.mit.edu (Jim Reisert AD1C)
Date: Sun, 16 May 2021 18:51:51 -0600
Subject: [WT-support] CTY-3112 Country Files - 17 May 2021
Message-ID: <20210517005208.D04A1208053@mx.glou.fr>

The Country (CTY) Files were updated on 17 May 2021:

    https://www.country-files.com/cty-3112-17-may-2021/

For installation instructions, start at:

    https://www.country-files.com/

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:

   https://www.country-files.com/big-cty-17-may-2021/

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:

   https://www.country-files.com/feed/

Here are the release notes:

    17 May 2021 (CTY-3112)
    VER20210517, Version entity is Uruguay, CX

    Added/changed Entities/Prefixes/Callsigns:

	* GB2QM is Shetland Islands, *GM/s
	* EA8CPU/DE is Canary Islands, EA8
	* GB2IOM is Isle of Man, GD
	* GB0GLS and GB1TMD are both Northern Ireland, GI
	* GB0SLB, GB0TTC and GB2QM are all Scotland, GM
	* GB6RNLI is Wales, GW
	* K9IG is United States, K in CQ zone 4, ITU zone 7
	* KD6APH and WL7CSW are both Hawaii, KH6
	* N4AKO is Puerto Rico, KP4
	* LU1FMS/F, LU1HYW/H, LU1LTL/L, LU4LBU/L, LU6FLZ/F, LU7FKK/F and LW3EMP/L
	  are all Argentina, LU
	* LU2WA/W and LU9ESD/XO are both Argentina, LU in ITU zone 16
	* R0AI/3, R115MUSA, R65KZI, R75TKS, R800AN, R800ANG, R800ANL, R800ANN,
	  R800ANV, R800RAN, RO10RT, RV1CC/1 and UA5B/4 are all European Russia, UA
	* R100KOMI and R8MB/1 are both European Russia, UA in CQ zone 17, ITU zone 20
	* R1PN/8 and UB5O/9 are both Asiatic Russia, UA9

    Removed Entities/Prefixes/Callsigns:

	* MM0MOL/P in Shetland Islands, *GM/s
	* RI01ANT in Antarctica, CE9
	* EA5ZD/URE in Spain, EA
	* EA8VK/URE in Canary Islands, EA8
	* MM0MOL/P in Scotland, GM
	* IT9PQJ/0 in Italy, I
	* II0ICV in Sardinia, IS
	* KE4YSP in Guam, KH2
	* KB5OXR and N0VYO in Hawaii, KH6
	* K5RD, K7BUF and KE5WGZ in Alaska, KL
	* KC5FWS in Puerto Rico, KP4
	* LU1AW/D, LU1XZ/H, LU2HA/H, LU3DVN/X, LU6DK/D and LU7DZV/D in Argentina, LU
	* R105IA, R125PR, R2014RK, R2014SE, R41WCMB, RK0HWW/1, RT9K/6, RV1CC/P
	  and UA3LMR/P in European Russia, UA

73 - Jim AD1C

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://www.ad1c.us




From n6tv at arrl.net  Wed May 19 08:38:01 2021
From: n6tv at arrl.net (Bob Wilson, N6TV)
Date: Tue, 18 May 2021 23:38:01 -0700
Subject: [WT-support] Win-Test extensions for Icom radios updated -- new LUA
	scripts
Message-ID: <CAOmNKG++tidFBWMd8482nGo1Pi7EECNED=PS+UmcBY0Wcb1UsQ@mail.gmail.com>

I've just updated IcomScripts.zip (download from https://bit.ly/wtscripts)
to support the newest Icom radios and new features available in the
latest Icom firmware updates, including SCROLL-F mode (an improved Fixed
mode that scrolls one "page" instead of allowing the MAIN VFO cursor to
fall off the edge of the screen).

Updating the Icom firmware is recommended, otherwise the scope SPAN scripts
may not automatically select FIXED mode as they did before, and you'll have
to select FIXED mode manually (or you can change the FIXEDMODE variable
inside the IcomSetSpan.wts from '03' to '01' if you want to stick with the
old Icom firmware and use the new scripts).

Be sure to update Win-Test to a newer version if your Icom rig is not
listed as supported, and change the Icom CI-V address to the default for
your model if you're using something else.

Change log:

   - Added IC-705, IC-9700 support
   - Added IcomSetNegScope to set reference level via REF text command
   - Added IcomClearRITOFF assigned to Shift Right-Arrow
   - Added IcomPowerOn and IcomPowerOff scripts
   - SPAN commands now select SCROLL-F FIXED mode where supported
   -            (requires new Icom firmware, see below)


More details in the Readme_IcomScripts.txt file included inside
IcomScripts.zip.

Many thanks to K6KLY and W6XU for the IC-9700 testing and to DL4LAM for the
IC-705 testing.

73,
Bob, N6TV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210518/d45c167e/attachment.html>

From bjorn at ekelund.nu  Wed May 19 09:54:51 2021
From: bjorn at ekelund.nu (=?UTF-8?Q?Bj=C3=B6rn_Ekelund?=)
Date: Wed, 19 May 2021 09:54:51 +0200
Subject: [WT-support] Win-Test extensions for Icom radios updated -- new
 LUA scripts
In-Reply-To: <CAOmNKG++tidFBWMd8482nGo1Pi7EECNED=PS+UmcBY0Wcb1UsQ@mail.gmail.com>
References: <CAOmNKG++tidFBWMd8482nGo1Pi7EECNED=PS+UmcBY0Wcb1UsQ@mail.gmail.com>
Message-ID: <CABmD_KSHVeP6oVWBoc5n6xe8hwow57r374kdEaobM4Q6sB78uA@mail.gmail.com>

Excellent, much appreciated, Bob.

If you need testing assistance in the future, I own most of the supported
ICOM models.

Bj?rn SM7IUN

Den ons 19 maj 2021 kl 08:39 skrev Bob Wilson, N6TV <n6tv at arrl.net>:

> I've just updated IcomScripts.zip (download from https://bit.ly/wtscripts)
> to support the newest Icom radios and new features available in the
> latest Icom firmware updates, including SCROLL-F mode (an improved Fixed
> mode that scrolls one "page" instead of allowing the MAIN VFO cursor to
> fall off the edge of the screen).
>
> Updating the Icom firmware is recommended, otherwise the scope SPAN
> scripts may not automatically select FIXED mode as they did before, and
> you'll have to select FIXED mode manually (or you can change the FIXEDMODE
> variable inside the IcomSetSpan.wts from '03' to '01' if you want to stick
> with the old Icom firmware and use the new scripts).
>
> Be sure to update Win-Test to a newer version if your Icom rig is not
> listed as supported, and change the Icom CI-V address to the default for
> your model if you're using something else.
>
> Change log:
>
>    - Added IC-705, IC-9700 support
>    - Added IcomSetNegScope to set reference level via REF text command
>    - Added IcomClearRITOFF assigned to Shift Right-Arrow
>    - Added IcomPowerOn and IcomPowerOff scripts
>    - SPAN commands now select SCROLL-F FIXED mode where supported
>    -            (requires new Icom firmware, see below)
>
>
> More details in the Readme_IcomScripts.txt file included inside
> IcomScripts.zip.
>
> Many thanks to K6KLY and W6XU for the IC-9700 testing and to DL4LAM for
> the IC-705 testing.
>
> 73,
> Bob, N6TV
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210519/68fc9b46/attachment.html>

From f6fvy at free.fr  Thu May 20 13:32:01 2021
From: f6fvy at free.fr (Laurent HAAS - F6FVY)
Date: Thu, 20 May 2021 13:32:01 +0200
Subject: [WT-support] Win-Test 4.36.0 released
Message-ID: <a0eb37b0-e85b-1882-afc2-65b8ff8a82cb@free.fr>

Hi

Win-Test version 4.36.0 is now available for download:

http://download.win-test.com/v4/bin/wt-4.36.0.exe [full, 14 MB]
http://download.win-test.com/v4/bin/wt-4.36.0-update.exe [update, 6.5 MB]

The update download is also available from Win-Test by using the Help / 
Check for Win-Test updates... menu item.

As usual, use your login / password to access the download area.

Please find below the release file

----------------------------------------------------------

4.36.0 (May 19, 2021)

- CQ-M : Scoring is now updated and follows the rules 2021.

- IARU HF : In M/S (Mixed only) category, the 10-min status timer now
   takes into account mode changes. Tnx HA6OI.

- HA DX : The Cabrillo output file now includes the RUN/MULT indicator
   for the M/S entrants. Tnx HA6OI.

- YOTA (Youngsters On The Air) contest implemented.

- ARI DX / ARI 40-80 : Provinces list and exchange equivalence file
   (ARIPROV.DAT) updated. Tnx HB9AMO, DL6RAI.

- Bugfix : In Phone, when entering a (very) long exchange, the cursor
   might insert a ghost space character at the end of the field.

- City, State/Prov, Postal Code and Country separate fields added to
   the contest settings dialog to improve the compatibility with
   the Cabrillo v3 header fields. These fields are assembled together to
   maintain the back compatibility with the Cabrillo v2 format if needed.
   If is highly recommended to edit your saved profiles (if any) by
   loading, editing and saving them one by one in the dialog.

- CQMM DX implemented.

- All file dialogs are now resizable.

- YUDX : LCR view added.

- LCR viewer : Column order unified.

- Bugfix : VHF+ contests : Under some circumstances, when the
   automatic exchange (grid) guessing was set, the Check Partial wnd
   wasn't updated anymore after the field was automatically filled.

- OK/OM Contest SSB : This contest was not listed when the contests
   of the month checkbox (in April) was selected. Tnx F1HAR.

- OK/OM contest : You can now directly download your LCR in Win-Test
   from the "rejected" link in the final results and preliminary
   results page.

--------------------------------------------------

73

Larry - F6FVY

-- 

All of humanity's problems stem from man's inability
to sit quietly in a room alone.

Blaise Pascal, Pens?es

From jjreisert at alum.mit.edu  Wed May 26 15:54:51 2021
From: jjreisert at alum.mit.edu (Jim Reisert AD1C)
Date: Wed, 26 May 2021 07:54:51 -0600
Subject: [WT-support] CTY-3113 Country Files - 26 May 2021
Message-ID: <20210526135501.A6D3D20800F@mx.glou.fr>

The Country (CTY) Files were updated on 26 May 2021:

    https://www.country-files.com/cty-3113-26-may-2021/

For installation instructions, start at:

    https://www.country-files.com/

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:

   https://www.country-files.com/big-cty-26-may-2021/

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:

   https://www.country-files.com/feed/

Here are the release notes:

    26 May 2021 (CTY-3113)
    VER20210526, Version entity is Cameroon, TJ

    Added/changed Entities/Prefixes/Callsigns:

	* EA1BPC/DE and EA1FDD/DE are both Spain, EA
	* GB0BPM is Northern Ireland, GI
	* 4U29MAY is Italy, I
	* WL7M is Hawaii, KH6
	* K5VOR, KD2NPD and W6SMA are all Alaska, KL
	* KV4BT is US Virgin Islands, KP2
	* LU1IG/I and LU4AAO/D are both Argentina, LU
	* R103PW, R116MS, R90WTA, RO36MS, RT9K/6 and UE36MS are all European Russia, UA
	* RK4P and RT36MS are both European Russia, UA in ITU zone 30
	* UE90WTA is Kaliningrad, UA2
	* R103PS, R18J, R18UGRA, RO6C/8/P, RX3Q/8 and UB5O/8 are all Asiatic Russia, UA9

    Removed Entities/Prefixes/Callsigns:

	* BG9XD/5 in China, BY
	* TO1K in St. Martin, FS
	* 2I0NGM/NHS in Northern Ireland, GI
	* GH5DX/NHS in Jersey, GJ
	* GM3YDN/NHS, GM4SQM/NHS, GM4SQN/NHS, GM6JNJ/NHS, MM3AWD/NHS, MM3DDQ/NHS
	  and MM7WAB/NHS in Scotland, GM
	* GB1004FTS, GB100FTS and GB4FTS in Wales, GW
	* K9OM in United States, K
	* K4XV, KG4TZD, KJ6CQT and WL7CSW/H in Hawaii, KH6
	* K1TMT and KC1LVR in Alaska, KL
	* K5KUB in US Virgin Islands, KP2
	* LU2IV/I, LU3YLF/Y, LU4DQ/D, LU4ETJ/D, LU5YEC/Y, LU7EMP/D, LU7IRS/I,
	  LU7YG/Y, LU9IAE/I, LU9IAL/I and LW1DUQ/D in Argentina, LU
	* R800ANP in European Russia, UA
	* RV7B/9 and UD6AOP/0 in Asiatic Russia, UA9

73 - Jim AD1C

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://www.ad1c.us