Date   
NS RTTY this Thursday

Ken K6MR
 

Greetings Diddlers:

A good group last week with some great scores.  Welcome to KA6BIM who dropped by and added to the mix.

The only RTTY test I see on the list is the SARL Digital.  So if you need to tune up the station or just need a RTTY fix, please join us Thursday evening and get your weekly diddle fix. 

 

The details for our little get together this week:

Friday,  21 Feb 2020, 0145Z - 0215Z (Thursday, 20 Feb  in NA)
-- 1745 - 1815 PST
-- 2045 - 2115 EST
-- (others in-between those two)
-- 160: Around 1805  (Last two to five minutes seem to be popular…)
-- 80/40/20/15 +84 kHz up from the band edge   <--NOTE
-- Same band dupes ok after 1 intervening Q.
-- 1 kHz QSY rule, otherwise standard Sprint rules
-- Mults per band.
-- 100W power limit

Please visit http://www.ncccsprint.com/rttyns.html for complete rules and links to other info. If you find any problems with the web pages, please let me know so we can get them fixed.

If you would like to receive all the latest info about NS as well as a have a place for comments and questions, sign up for the NS mailing list:  https://groups.io/g/nccc-blue

Contestonlinescore.com has a slot set up for us if you’d like to make sure your logger is talking to the world.  Select NCCC NA RTTY Sprint.

Report scores to 3830scores.com, and join us at 0300Z on 3610 kHz (+/- a few for ongoing groups) for comments and questions (and dinner menus).

Diddle diddle,

Ken K6MR


CQ WPX RTTY Contest Raw Scores Posted

Ed Muns, W0YK
 

The Raw Scores are posted for the CQ WPX RTTY Contest held a week ago. Raw
scores are computed by the log checking software before any error
reductions.

https://cqwpxrtty.com/raw.htm

Send any questions to questions@...

73,
Ed W0YK

CTY-3004 Country Files - 14 February 2020

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 14 February 2020:

https://www.country-files.com/cty-3004-14-february-2020/

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-14-february-2020/

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:

14 February 2020 (CTY-3004)
VER20200214, Version entity is Fiji, 3D2

Added/changed Entities/Prefixes/Callsigns:

* 4UNR is Vienna Intl Ctr, *4U1V
* LU3DXG/D and LU6DG/D are both Argentina, LU
* LU1XA/XA is Argentina, LU in ITU zone 16
* 4UNR is Austria, OE
* R2020LS, R77RND, R89AFG and R89DRA are all European Russia, UA
* UD6AOP/0 is Asiatic Russia, UA9

Removed Entities/Prefixes/Callsigns:

* 4U1XMAS in Vienna Intl Ctr, *4U1V
* IA0/IZ1KHY/P and VP8CTR in Antarctica, CE9
* WB1BR in Alaska, KL
* 4U1XMAS in Austria, OE
* R19YOTA in European Russia, UA

73 - Jim AD1C

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

CTY-3003 Country Files - 13 February 2020

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 13 February 2020:

https://www.country-files.com/cty-3003-13-february-2020/

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-13-february-2020/

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:

13 February 2020 (CTY-3003)
VER20200213, Version entity is Spain, EA

Added/changed Entities/Prefixes/Callsigns:

* B9/BH1NGG is China, BY in ITU zone 43
* TO3Z is Guadeloupe, FG
* TO4A and TO7BP are both Martinique, FM
* GB0GLS is Northern Ireland, GI
* GB0GTD and GB2FEA are both Scotland, GM
* GB1SDD is Wales, GW
* IT9RGY/4 is Italy, I
* AB8YZ, K8FU, NP4AI and W9LHG are all United States, K in CQ zone 4, ITU zone 7
* NS2X is United States, K in CQ zone 4, ITU zone 8
* AA5JF is United States, K in CQ zone 5, ITU zone 8
* KN4IAS is Guam, KH2
* ND1A is Hawaii, KH6
* KF7ING, KN4ENR and NH2LS are all Alaska, KL
* KO4ALI is US Virgin Islands, KP2
* K4M is Puerto Rico, KP4
* LU1AW/E, LU1KCQ/D, LU1VYL/D, LU2FDA/F and LU9HMB/H are all Argentina, LU
* LU8EB/Y and LU8YD/Y are both Argentina, LU in ITU zone 16
* RU97AE and RU9MU/3 are both European Russia, UA
* R100FA is European Russia, UA in ITU zone 19
* R240S is European Russia, UA in CQ zone 17, ITU zone 20
* R100RGA and RM97AE are both Asiatic Russia, UA9
* RL3T/9 is Asiatic Russia, UA9 in CQ zone 18, ITU zone 31
* RV3DSA/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 34
* EA4FZR is South Shetland Islands, VP8/h

Removed Entities/Prefixes/Callsigns:

* IA0/DK5SQX and KC4USB in Antarctica, CE9
* TO2O in Guadeloupe, FG
* K1PQS, KA9A, KD5M, KQ9J, NA4K, NA9RB, W5HIO, W7KF, W8WEJ and WE6C
in United States, K
* K7SGA, KC5IBS, KF6IAO, N7CGC and N7DBN in Alaska, KL
* KK4DCX in Puerto Rico, KP4
* LU1AW/X, LU5KAH/K, LU5YF/D and LU7CC/E in Argentina, LU
* R105DA and R50KAMA in European Russia, UA
* RAEM, RW0CE/9, RW95WJ, RX95WN and UB5O/8 in Asiatic Russia, UA9

73 - Jim AD1C

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

NS RTTY this Thursday

Ken K6MR
 

Greetings Diddlers:

A small group last week, I’m guessing a few spent more time practicing for the WPX.  Welcome to N5KB who dropped by and made a few Qs.

 

Just a friendly reminder:  Pause just a bit after the last exchange before calling to give the ACK message (or the frantic NR?) a chance to get through.  And if the path to your QSO partner seems a bit weak, give him a fighting chance with a repeat of at least the S/N.  All the funny things that happen in the ether seem to happen at the most inopportune moments!

 

The upcoming weekend looks to be all CW all of the time with the ARRL DX CW test.  But if you still need a digital fix before the weekend, please join us Thursday evening.

 

The details for our little get together this week:

Friday,  14 Feb 2020, 0145Z - 0215Z (Thursday, 13 Feb  in NA)
-- 1745 - 1815 PST
-- 2045 - 2115 EST
-- (others in-between those two)
-- 160: Around 1805  (Last two to five minutes seem to be popular…)
-- 80/40/20/15 +84 kHz up from the band edge   <--NOTE
-- Same band dupes ok after 1 intervening Q.
-- 1 kHz QSY rule, otherwise standard Sprint rules
-- Mults per band.
-- 100W power limit

Please visit http://www.ncccsprint.com/rttyns.html for complete rules and links to other info. If you find any problems with the web pages, please let me know so we can get them fixed.

If you would like to receive all the latest info about NS as well as a have a place for comments and questions, sign up for the NS mailing list:  https://groups.io/g/nccc-blue

Contestonlinescore.com has a slot set up for us if you’d like to make sure your logger is talking to the world.  Select NCCC NA RTTY Sprint.

Report scores to 3830scores.com, and join us at 0300Z on 3610 kHz (+/- a few for ongoing groups) for comments and questions (and dinner menus).

Diddle diddle,

Ken K6MR

 

Yaesu YR 901 for RTTY

Don Hill AA5AU
 

I received a request for help.

Anyone have experience setting up the Yaesu YR 901 for RTTY with the Yaesu
FT 901 DM transceiver?

Please contact Jeffery, KA2BKG, directly at jeffjguenther@....

Thanks,
Don AA5AU

CQ WW RTTY WPX ASAP Please!

Roger Cooke
 

Hi RTTY-ers


I would like to have our comments, results, pictures, antenna problems (Ciara??) for the latest CDXCC Data column. Pictures make it a lot more interesting, but I will be grateful for whatever comes my way!

MY DEADLINE IS CLOSE SO PLEASE SEND YOUR COMMENTS ASAP!


Many thanks in advance.


73 de Roger, G3LDI 

WPX RTTY upload

G. E. Janssens - K5WW
 

I know the contest isn't over yet; but I'd like to upload the club's log.

Having some serious issues, though. It looks like there may be an error in the page's code...

73,

Erik - K5WW

GB60ATG

John Barber
 

BARTG has the special call GB60ATG to celebrate 60 years of supporting the data modes. You may have worked GB60ATG on various modes and be eligible for an award. More details can be found on our website www.bartg.org.uk.

The call is being run from different UK countries each week. This week the operator is John GW4SKA, usually seen as GW0A in contests, but using the BARTG GB60ATG call in the WPX contest. The country is Wales.

Have fun in the test!

John GW4SKA

BARTG President

 

Re: RTTY message length and Additional Receive Window Question

John Barber
 

May I add that whatever you decide is best in the macro, it will only be best in certain conditions.

Think about the strength of the signal coming in, how well your signal is being received in that part of the world, and change things around as needed.

A simple example that works well for me is sending a report which might be:

‘ G3YYD 599 001 001 ‘

If conditions are lousy and signals weak or more than one station has called me, I send the same macro twice and hit the escape key after the call is sent the second time:

‘ G3YYD 599 001 001 G3YYD ‘

If it’s really bad, send the complete macro twice.

John GW4SKA

 

From: RTTY@groups.io <RTTY@groups.io> On Behalf Of David G3YYD via Groups.Io
Sent: 04 February 2020 10:54
To: RTTY@groups.io
Cc: RTTY@groups.io
Subject: Re: [RTTY] RTTY message length and Additional Receive Window Question

 

I normally send key exchange data twice. So 599 123 123 or in BARTG 599 123 123 1223 1223. I always send my contest call twice M7T M7T but then it is so short it takes a similar time to send as one send of GM3ABC. Sending twice also takes advantage of 2Tone’s repeat string system. I use a further development of 2Tone that works on serial numbers of 2 digits and longer.

 

Above all bracketing important information with spaces is an essential. CR and LF I only use at the start of CQs.

 

73 David G3YYD/M7T

 

From: RTTY@groups.io [mailto:RTTY@groups.io] On Behalf Of David AD4TJ via Groups.Io
Sent: 03 February 2020 22:50
To: rtty@groups.io; Jeff AC0C
Cc: RTTY@groups.io
Subject: Re: [RTTY] RTTY message length and Additional Receive Window Question

 

I tend to disagree about sending the number only once. IF signals are great, and there is NO QRM or QRN( how do you know if the other guy has it, but you don't have it? ), AND you have great antennas, then once is fine. BUT if just one of those events is not present, then it is very easy to miss the number. And if asked for a repeat of the number, why limit it to only twice? Still a good chance the decode may not get read properly on the other end.

 

For example: Saturday and Sunday morning, on 20 meters, before 7 am here on the East Coast, EU is coming in weakly( at least at my location, with my TA-33 at only 20 feet ). My S&P exchange message is set to send the number 4 times; I had it set to 3, but with the weak signals was getting some requests for repeats. In RUN mode, I have it set to 3 times; got a few repeat requests, but usually if they can copy my CQ then I am strong enough that they get it at least once. A few times in S&P I had to send my NR 12 times for it to be copied on the other end.

 

On another note: I had 2 additional Rcve windows set up on MMTTY: 2Tone and Gritty. I tried to add a 3rd one, but messed it up, and could not get it back to fix it. So I just added a 4th window( a second 2Tone ) with no problem. Now when I bring up N1MM I get an error message saying " MMTTY or 2Tone could not be found in this path: Not set ". I have no idea how to fix it, unless I can find how to delete all the extra windows and start over. There must be an easy way to correct it but I have not found it. Help!

 

73, David AD4TJ

 

On Monday, February 3, 2020, 5:17:52 PM EST, Jeff AC0C <keepwalking188@...> wrote:

 

 

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0ccom
 
 

On 2/3/20 2:45 PM, Hank W6SX wrote:

The best way to limit transmit time is also the best way to operate.

 

No DE's.

 

No leading spaces or periods.

 

Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.

 

No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.

 

No excessive CR/LFs.

 

Etcetera.

 

It's a contest. Use short macros and everyone including your amplifier will be happier.

 

Contest Exuberantly,

 

Hank, W6SX

 

 

 

On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:

Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

NS RTTY this Thursday

Ken K6MR
 

Greetings Diddlers:

Great to work a number of diddlers in the original digital mode Sprint last weekend.  A wonderful tribute to Don, W4OC. Apparently many missed SC, which Don often provided to all of us.  RIP OM.

 

Our RTTY get together had just over double digit participation.  20 was a no show, but 160 had some activity.  So don’t forget to check both just in case someone is around.

 

This weekend is the CQ WPX RTTY, so take some time to tune up the diddle machine.  Not only can you join us at our normal time on Thursday, there will be two other practice sessions in normal WPX contest format.  So check them all out and make sure you are ready to make the weekend productive.


The details for our little get together this week:

Friday,  6 Feb 2020, 0145Z - 0215Z (Thursday, 5 Feb  in NA)
-- 1745 - 1815 PST
-- 2045 - 2115 EST
-- (others in-between those two)
-- 160: Around 1805  (Last two to five minutes seem to be popular…)
-- 80/40/20/15 +84 kHz up from the band edge   <--NOTE
-- Same band dupes ok after 1 intervening Q.
-- 1 kHz QSY rule, otherwise standard Sprint rules
-- Mults per band.
-- 100W power limit

Please visit http://www.ncccsprint.com/rttyns.html for complete rules and links to other info. If you find any problems with the web pages, please let me know so we can get them fixed.

If you would like to receive all the latest info about NS as well as a have a place for comments and questions, sign up for the NS mailing list:  https://groups.io/g/nccc-blue

Contestonlinescore.com has a slot set up for us if you’d like to make sure your logger is talking to the world.  Select NCCC NA RTTY Sprint.

Report scores to 3830scores.com, and join us at 0300Z on 3610 kHz (+/- a few for ongoing groups) for comments and questions (and dinner menus).

Diddle diddle,

Ken K6MR


CQ WPX RTTY Practices

Ed Muns, W0YK
 

2100-2130 UTC, Thursday, 6 February

0100-0130 UTC, Friday, 7 February (Thursday evening NA time)

 

On Thursday (NA time), let's have two 30-minute practice sessions to check out our station equipment, software and operator(s).  Both sessions are prior to the usual Thursday evening NCCC Sprints (RTTY and CW).

 

Operate just like it's the real thing that starts on Saturday 00 UTC.  Use whatever bands are open and active for you at each time slot.  You might want to have a special message prepared to respond to stations telling you that the contest hasn't yet started.

 

Yep, its CQ WPX RTTY this weekend.  Take a break from all the FT activity on the bands and dust off your legacy digital operating prowess.  Most of all, have fun over the weekend in the CQ WPX RTTY Contest.  Take some photos of your operation and send them and/or a summary of your experience to me.  It will help in writing up the contest for the July CQ magazine.

 

If you’d like to sponsor a plaque, contact Rich N1IXF (Cc above). 

 

Ed W0YK

 

Re: RTTY message length and Additional Receive Window Question

Peter N5UWY
 

On Tue, Feb 4, 2020 at 4:55 AM David G3YYD via Groups.Io
<g3yyd2=btinternet.com@groups.io> wrote:

I normally send key exchange data twice. So 599 123 123 or in BARTG 599 123 123 1223 1223. I always send my contest call twice M7T M7T but then it is so short it takes a similar time to send as one send of GM3ABC. Sending twice also takes advantage of 2Tone’s repeat string system. I use a further development of 2Tone that works on serial numbers of 2 digits and longer.

Above all bracketing important information with spaces is an essential. CR and LF I only use at the start of CQs.

I run a FULL 100 W into low, poorly tuned antennas so I do about the
same as you macro-wise. RST once if required at all, exchange twice,
and call is usually sent enough that I don't need to repeat it within
a transmission.

As has been discussed here NUMEROUS times, sending an item twice
allows error detection by the other op. Sending it 3x allows for
error correction in some high percentage of cases but at the expense
of a 50% increase in the length of that part of the message.
Detection allows the other op to ask for an AGN without the extra time
in all Qs.

If you run more than the FULL 100 W or have good antennas or
something, you can probably get away with sending once.

f you are calling CQ, you can send once, too, because presumably if
the other op CAN'T print you they aren't going to call you anyway. I
am constantly amazed at how well I can do calling CQ even with my
station as described above.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!

Re: RTTY message length and Additional Receive Window Question

David G3YYD
 

I normally send key exchange data twice. So 599 123 123 or in BARTG 599 123 123 1223 1223. I always send my contest call twice M7T M7T but then it is so short it takes a similar time to send as one send of GM3ABC. Sending twice also takes advantage of 2Tone’s repeat string system. I use a further development of 2Tone that works on serial numbers of 2 digits and longer.

 

Above all bracketing important information with spaces is an essential. CR and LF I only use at the start of CQs.

 

73 David G3YYD/M7T

 

From: RTTY@groups.io [mailto:RTTY@groups.io] On Behalf Of David AD4TJ via Groups.Io
Sent: 03 February 2020 22:50
To: rtty@groups.io; Jeff AC0C
Cc: RTTY@groups.io
Subject: Re: [RTTY] RTTY message length and Additional Receive Window Question

 

I tend to disagree about sending the number only once. IF signals are great, and there is NO QRM or QRN( how do you know if the other guy has it, but you don't have it? ), AND you have great antennas, then once is fine. BUT if just one of those events is not present, then it is very easy to miss the number. And if asked for a repeat of the number, why limit it to only twice? Still a good chance the decode may not get read properly on the other end.

 

For example: Saturday and Sunday morning, on 20 meters, before 7 am here on the East Coast, EU is coming in weakly( at least at my location, with my TA-33 at only 20 feet ). My S&P exchange message is set to send the number 4 times; I had it set to 3, but with the weak signals was getting some requests for repeats. In RUN mode, I have it set to 3 times; got a few repeat requests, but usually if they can copy my CQ then I am strong enough that they get it at least once. A few times in S&P I had to send my NR 12 times for it to be copied on the other end.

 

On another note: I had 2 additional Rcve windows set up on MMTTY: 2Tone and Gritty. I tried to add a 3rd one, but messed it up, and could not get it back to fix it. So I just added a 4th window( a second 2Tone ) with no problem. Now when I bring up N1MM I get an error message saying " MMTTY or 2Tone could not be found in this path: Not set ". I have no idea how to fix it, unless I can find how to delete all the extra windows and start over. There must be an easy way to correct it but I have not found it. Help!

 

73, David AD4TJ

 

On Monday, February 3, 2020, 5:17:52 PM EST, Jeff AC0C <keepwalking188@...> wrote:

 

 

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0ccom
 
 

On 2/3/20 2:45 PM, Hank W6SX wrote:

The best way to limit transmit time is also the best way to operate.

 

No DE's.

 

No leading spaces or periods.

 

Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.

 

No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.

 

No excessive CR/LFs.

 

Etcetera.

 

It's a contest. Use short macros and everyone including your amplifier will be happier.

 

Contest Exuberantly,

 

Hank, W6SX

 

 

 

On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:

Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

Re: RTTY message length and Additional Receive Window Question

David AD4TJ
 

Thanks, Rich! That did it. I had to deselect " Enable attached RX windows " to get there. I'll make a big note on this one!

73, David AD4TJ

On Monday, February 3, 2020, 6:44:55 PM EST, Rich VE3KI <ve3iay@...> wrote:


Re the additional receive window question: Hover your mouse over the N1MM+ icon on the Windows Task Bar. You will see several small thumbnail windows, one for the Entry window, one for the main DI window, and one for each additional RX-only window. They are titled, so you should be able to find the one for DI1 RX Window 3, if necessary by hovering the mouse over the title bar of each one in turn. Right-click on that one and choose Restore. That will open the unattached version of that RX window. If it isn't already open to the Setup page, then in the menu bar for that window choose Setup. Fix whatever is wrong in that window and minimize it to the Task Bar.

If this doesn't work, an alternative method is to uncheck the "Enable attached RX windows" sub-menu item in the DI window's setup menu. All three or four RX windows will separate from the main DI window, and you can access the Setup menu for each one individually to make whatever changes you need to. If you have four and you only want three, make sure the first three are set up correctly and then close the fourth one with the X at the top right corner. Close and reopen the main DI window and check its "Enable attached RX windows" option.

73,
Rich VE3KI


On Mon, Feb 3, 2020 at 05:50 PM, David AD4TJ wrote:
<snip>
 
On another note: I had 2 additional Rcve windows set up on MMTTY: 2Tone and Gritty. I tried to add a 3rd one, but messed it up, and could not get it back to fix it. So I just added a 4th window( a second 2Tone ) with no problem. Now when I bring up N1MM I get an error message saying " MMTTY or 2Tone could not be found in this path: Not set ". I have no idea how to fix it, unless I can find how to delete all the extra windows and start over. There must be an easy way to correct it but I have not found it. Help!
 
73, David AD4TJ
 
On Monday, February 3, 2020, 5:17:52 PM EST, Jeff AC0C <keepwalking188@...> wrote:
 
 

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 2/3/20 2:45 PM, Hank W6SX wrote:
The best way to limit transmit time is also the best way to operate.
 
No DE's.
 
No leading spaces or periods.
 
Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.
 
No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.
 
No excessive CR/LFs.
 
Etcetera.
 
It's a contest. Use short macros and everyone including your amplifier will be happier.
 
Contest Exuberantly,
 
Hank, W6SX
 
 

On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:
Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

 

Re: RTTY message length

Dave Hachadorian
 

No CR/LF’s at the end of a transmission please, use just a space.  CR/LF can cause the exchange to jump up from under the receiving operator’s mouse pointer.
 
Dave Hachadorian, K6LL
Yuma, AZ
 

From: Hank W6SX
Sent: Monday, February 3, 2020 3:52 PM
Cc: RTTY Reflector
Subject: Re: [RTTY] RTTY message length
 
Jeff is spot on of course.
 
I tried to choose my words carefully by saying leading spaces. But I wasn't careful enough.
 
It is always a good idea to start any transmission with either a single space or CR/LF. Same for end of a transmission: either a single space or CR/LF.
 
Diddle Exuberantly,
 
Hank, W6SX
 
 
On Mon, Feb 3, 2020 at 2:17 PM Jeff AC0C <keepwalking188@...> wrote:

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 2/3/20 2:45 PM, Hank W6SX wrote:
The best way to limit transmit time is also the best way to operate.
 
No DE's.
 
No leading spaces or periods.
 
Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.
 
No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.
 
No excessive CR/LFs.
 
Etcetera.
 
It's a contest. Use short macros and everyone including your amplifier will be happier.
 
Contest Exuberantly,
 
Hank, W6SX
 
 
 
On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:
Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

Re: RTTY message length and Additional Receive Window Question

Rich VE3KI
 

Re the additional receive window question: Hover your mouse over the N1MM+ icon on the Windows Task Bar. You will see several small thumbnail windows, one for the Entry window, one for the main DI window, and one for each additional RX-only window. They are titled, so you should be able to find the one for DI1 RX Window 3, if necessary by hovering the mouse over the title bar of each one in turn. Right-click on that one and choose Restore. That will open the unattached version of that RX window. If it isn't already open to the Setup page, then in the menu bar for that window choose Setup. Fix whatever is wrong in that window and minimize it to the Task Bar.

If this doesn't work, an alternative method is to uncheck the "Enable attached RX windows" sub-menu item in the DI window's setup menu. All three or four RX windows will separate from the main DI window, and you can access the Setup menu for each one individually to make whatever changes you need to. If you have four and you only want three, make sure the first three are set up correctly and then close the fourth one with the X at the top right corner. Close and reopen the main DI window and check its "Enable attached RX windows" option.

73,
Rich VE3KI


On Mon, Feb 3, 2020 at 05:50 PM, David AD4TJ wrote:
<snip>
 
On another note: I had 2 additional Rcve windows set up on MMTTY: 2Tone and Gritty. I tried to add a 3rd one, but messed it up, and could not get it back to fix it. So I just added a 4th window( a second 2Tone ) with no problem. Now when I bring up N1MM I get an error message saying " MMTTY or 2Tone could not be found in this path: Not set ". I have no idea how to fix it, unless I can find how to delete all the extra windows and start over. There must be an easy way to correct it but I have not found it. Help!
 
73, David AD4TJ
 
On Monday, February 3, 2020, 5:17:52 PM EST, Jeff AC0C <keepwalking188@...> wrote:
 
 

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 2/3/20 2:45 PM, Hank W6SX wrote:
The best way to limit transmit time is also the best way to operate.
 
No DE's.
 
No leading spaces or periods.
 
Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.
 
No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.
 
No excessive CR/LFs.
 
Etcetera.
 
It's a contest. Use short macros and everyone including your amplifier will be happier.
 
Contest Exuberantly,
 
Hank, W6SX
 
 

On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:
Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

 

Re: RTTY message length and Additional Receive Window Question

Hank W6SX
 



On Mon, Feb 3, 2020 at 2:50 PM David AD4TJ via Groups.Io <ad4tj=yahoo.com@groups.io> wrote:

I tend to disagree about sending the number only once.

It is complicated. It depends. It varies with circumstances.

See my comments below from an NCJ article a few years back.

Editors Note:  Hank, W6SX, is inspirational with his positive “Contest Exuberantly” signature on the contest reflectors.  In this guest column, he shows us how contest techniques and tactics can be dynamically optimized around the specifics of the QSO.  There is no single way to execute a QSO …

It Depends

What’s the best way to make contacts in RTTY contests? It depends.

Almost everything in contests depends. Contesting is a dynamic, situation-dependent activity. There’s no one-size-fits-all approach to making RTTY contacts. That’s what makes contests fun. The trick is to match each contact to the situation, to maximize score and fun, and to be friendly so everyone comes back for more.  

Since everything depends, what's the best approach? I suggest modularity. Create modular macros that can be sent one at a time or strung together as the situation dictates. With modularity, you have the best of many worlds—crafting each contact to the conditions.

Some ground rules. It’s a contest and a prime objective is to maximize score. It’s a contest and a prime objective is to have fun. It’s a contest and a prime objective is to help others have fun and maximize their scores. We’re all in this together, and we can all do a lot to help each other maximize score and have fun.

The Amateur is Friendly.1 What’s the best way to be friendly? It depends. My rule for contests is that completing the contact in shipshape fashion as quickly as possible is the most friendly thing I can do for the other guy and for the other guys waiting. And, it’s generally the most friendly thing you can do for me. The running station sets the tone. If the CQing station, even if he’s my best friend, sends me a standard-issue exchange, the most friendly thing is to send him a standard-issue exchange without pleasantries. If he says HI HANK, then he’s giving me the go-ahead to loosen up a (little) bit. It’s a contest—be contest friendly during the event and regular friendly afterwards.

To DE or not to DE. It depends, but mostly not. Almost all the time, who is sending is clear from sequence and timing. DE usually adds nothing to a contest exchange, and DE can be very confusing. For instance, W6SX 599 IN DE w4xxx. Ditch the DE.

What’s the best way to CQ? It depends. A good approach is to maximize your call and minimize stuff that doesn’t add value. CQ DL DX RTTY CONTEST DE w8xxx—not so good. CQ DL W6SX W6SX CQ—much better. Or CQ TEST W6SX W6SX W6SX CQ. Note that the CQ at the end is standard RTTY contest procedure and helps late tuners know that you are soliciting contacts.  

How much to send the other guy’s call? It depends.  When you’re answering a CQ, you don’t need to send the CQer’s call—he knows his call. Just drop your call once, twice, or three times depending on circumstances. How about when you’re running?

CQ TEST W6SX W6SX CQ
W0YK W0YK
W0YK 599 23 23 (W0YK)

Many routinely send the W0YK at the end of the exchange. Others never do. I suggest that it depends. If W0YK is the only station responding, there isn’t much to be gained by sending his call twice. If there is more than one caller, then sometimes, sending W0YK at the end of the exchange will avoid confusion and a time-wasting double. Note the sometimes. For instance, sometimes it pays to hesitate a bit and let multiple callers finish before responding to the first guy. In this case, I generally won't send the other guy's call at the end, but if I hear a signal just as I hit transmit, I'll add the other guy's call at the end. Even with multiple callers, often it’s still clear to everyone who is being working, and the second W0YK is not necessary. If you don’t lock yourself into always sending the second W0YK, you quickly develop a good sense of when to send it and when to skip it.

What if you’ve answered a CQ. It depends. You are sending your report to someone who certainly knows his own call. Unless there’s ambiguity, I normally don’t send the CQer’s call. But many stations routinely do, and that’s OK. For the S&P station, I don’t think there is anything to be gained by sending the CQer’s call at the end of the exchange.

(W6SX) 599 23 23
(W0YK) TU W6SX CQ

Many routinely send W0YK when confirming and concluding a QSO. Others never do. I suggest that it depends. If there is no doubt who was worked, I usually don’t send his call. But if there is any ambiguity, I’ll send it. Other times, for example, when trying to get a JA run going, I may send the other guy’s call to extend my transmit time and let other JAs know that I’m hearing them. Sometimes I’ll send the other guy’s call when I’m trying to defend a run frequency. It depends—there is no one answer.

Sending the other guy’s call at the end of an exchange and sending the other guy’s call when acknowledging a contact is like a political or religious discussion. Some people always do it one way, others always the other way. I suggest that the best bet is flexibility suited to the circumstances, but I’m not going to argue with anyone who gets the contact done.

What’s the best way to send repeats. I have one unequivocal answer. Send only what is being asked for. Don’t send his call—he knows his call. If he asks for the number, send only the number once, twice or three times. Do not send 599 33 33, and for sure don’t send 599 599 33!

Which brings us to … macros and flexible macros.  Be careful when using canned macros with your logging software. If the exchange is RST NR, then programming an F-key to send your exchange twice will yield 599 47 599 47. Never, never repeat 599. Send it once per contact and never send it again. It’s often best to hard program your F-keys instead of using your logging software macros. For instance, make F2 599 # # instead of EXCH EXCH. In many cases, you are smarter than your logging software.

Flexible macros. If someone asks for your serial number again, don’t use F2, which will send your whole exchange. Instead program another F-key with your number only. The name of the game is to program F-keys so you can send exactly what the situation requires instead of being forced to send canned, extraneous stuff that wastes everybody’s time.

What to send in your exchange? It depends. NCJ NAQP first.

AA5AU HANK CA (AA5AU)

Since I am a W6, live in California, have a decent signal, and am reasonably well known, I send HANK and CA once each. If my name were Maximilian, I’d send it twice. If I were a Six outside of California, I would definitely send my state twice. If your call makes where you live unambiguous, send your location only once. For instance, a VE3 needs to send ON only once.

Now a contest with serial numbers, for instance, CQ WPX RTTY.

K4GMH 599 328 328 (K4GMH)

Some people say send serial number once. Others say twice. Still others say three times because if you get it two out of three times, you’ll know it’s right. I normally send serial number twice, and below I show how this works well. But the real answer is it depends. If you are loud and running, people get more than one chance to figure out your serial number, and once may be good enough. Caution—this may not work if the running station is SO2R where serial numbers might not be consecutive. If conditions are particularly poor, three times might be called for. It depends, which is why having flexible macros is a plus.  

Which brings us to the question of when to ask for a repeat. When do you have enough to log a contact? It depends. You don’t have to copy a number twice to be confident that you have it right.

If I print 599 005 W6SX, the 599 and W6SX bracketing the 005 tell me it’s probably good. I’ll log it unless something else tells me to question it.

One “something” is that you can often tell by ear if an exchange printed correctly. Or, perhaps more importantly, you can often tell by ear if an exchange is corrupted.

If I print 599 005 0%&*, I’ll probably log 005.

If I print 599 005^*A, I’ll ask for a repeat.

There are lots of scenarios you can build. Contest radiosport is risk evaluation. Do I interrupt a 100-per-hour run to be 100% sure of an exchange? Or do I evaluate as above and take a chance I’ll lose a low-point QSO to log checking? Does my calculus change if it’s a new multiplier I’m not likely to find later? Of course.

For a really good discussion of contest risk taking, see “Logging Accuracy: Error Control for SS,” by ND2T.2 In a contest, adjudicated score is the final arbitrator. I take some risks. My Log Checking Reports indicate that I’ve achieved a decent balance between 100% correct and score and fun.

Finally, how do I know that the other guy has my call correct? It depends. For instance, if I’m running and I print W6RX 599 003 003, I probably won’t try to “correct” him. I send my call twice when I CQ and at least once every contact, so the other guy has had ample opportunity to get my call right. I assume that he sent my call correctly and it took a hit. Additionally, by sending 599 003 003 or TU 599 003 with or without my call, he is QSLing my call and exchange—he’s saying I have it, I have all I need. If he’s not sure of my call, he needs to ask for it. Contesting is a two-way street, and both operators have responsibility to get it right. But, it depends. If I print W6RX 599 003 003 W6RX, I’ll correct the other station.

Modularity, no unneeded stuff, flexibility, and friendliness are what make contesting fun for everyone. See you in the next contest everyone.


1. The Amateur’s Code, Paul M. Segle, W9EEA (SK)

2. Available on the Northern California Contest Club website at
http://www.nccc.cc/misc/ErrorControl-ND2T.wmv


Re: RTTY message length

Hank W6SX
 

Jeff is spot on of course.

I tried to choose my words carefully by saying leading spaces. But I wasn't careful enough.

It is always a good idea to start any transmission with either a single space or CR/LF. Same for end of a transmission: either a single space or CR/LF.

Diddle Exuberantly,

Hank, W6SX


On Mon, Feb 3, 2020 at 2:17 PM Jeff AC0C <keepwalking188@...> wrote:

Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 2/3/20 2:45 PM, Hank W6SX wrote:
The best way to limit transmit time is also the best way to operate.

No DE's.

No leading spaces or periods.

Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.

No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.

No excessive CR/LFs.

Etcetera.

It's a contest. Use short macros and everyone including your amplifier will be happier.

Contest Exuberantly,

Hank, W6SX



On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:
Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona

Re: RTTY message length and Additional Receive Window Question

David AD4TJ
 

I tend to disagree about sending the number only once. IF signals are great, and there is NO QRM or QRN( how do you know if the other guy has it, but you don't have it? ), AND you have great antennas, then once is fine. BUT if just one of those events is not present, then it is very easy to miss the number. And if asked for a repeat of the number, why limit it to only twice? Still a good chance the decode may not get read properly on the other end.

For example: Saturday and Sunday morning, on 20 meters, before 7 am here on the East Coast, EU is coming in weakly( at least at my location, with my TA-33 at only 20 feet ). My S&P exchange message is set to send the number 4 times; I had it set to 3, but with the weak signals was getting some requests for repeats. In RUN mode, I have it set to 3 times; got a few repeat requests, but usually if they can copy my CQ then I am strong enough that they get it at least once. A few times in S&P I had to send my NR 12 times for it to be copied on the other end.

On another note: I had 2 additional Rcve windows set up on MMTTY: 2Tone and Gritty. I tried to add a 3rd one, but messed it up, and could not get it back to fix it. So I just added a 4th window( a second 2Tone ) with no problem. Now when I bring up N1MM I get an error message saying " MMTTY or 2Tone could not be found in this path: Not set ". I have no idea how to fix it, unless I can find how to delete all the extra windows and start over. There must be an easy way to correct it but I have not found it. Help!

73, David AD4TJ

On Monday, February 3, 2020, 5:17:52 PM EST, Jeff AC0C <keepwalking188@...> wrote:


Hank,

I generally agree with you.  But sometimes guys with marginal signals or who are running QRP hurt themselfs by going with a minimal exchange.  Adding that leading and trailing space to the NR IS beneficial.  Every contest there seems to be a few guys that I have to ask for a repeat on, and the reply is the NR alone.  But it's not space delimited and the number is not repeated.  So I have to ask again. 

So my advice is that unless you KNOW FOR SURE you have a strong signal (which means beam + power), invest in a leading and trailing space when sending that NR two times.  Example:

"514"                --> bad

" 514 514 "       -->    good

It's my belief that this ultimately saves the sender time as well because the request for a repeat is going to be far less in the 2nd case. 

Good luck to all in the WPX!

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com


On 2/3/20 2:45 PM, Hank W6SX wrote:
The best way to limit transmit time is also the best way to operate.

No DE's.

No leading spaces or periods.

Send 599 only once per contact. If asked for a number repeat, send only number, not 599 NR.

No wordy CQ's. CQ TEST and your call are what's important. Instead of CQ DL DX RTTY CONTEST DE w8xxx, send CQ DL W6SX W6SX CQ or CQ TEST.

No excessive CR/LFs.

Etcetera.

It's a contest. Use short macros and everyone including your amplifier will be happier.

Contest Exuberantly,

Hank, W6SX



On Mon, Feb 3, 2020 at 9:34 AM Bill KO7SS via Groups.Io <ko7ss=yahoo.com@groups.io> wrote:
Since I have issues with overheating my 80/40 OCF center balun running QRO RTTY (the SWR creeps upward ), I find the following link to be very interesting:
http://dwestbrook.net/projects/ham/rtty-length/?

Less transmit time is good :) Hoping to work some DX in the WPX this weekend, not a certain thing from W7 !

73, Bill KO7SS in Arizona