Speaking of speed demons.
I'd just love to see one of the logging program developers, have their
program automatically change the sending speed to match what it is
hearing as the receiving speed.
Not bother to do the actual decoding. just monitor the speed being heard
and automatically adjust the transmit speed to match it.
So when you come along to one of those 50 wpm speed demons the program
automatically responds to them going 50 wpm.
They can't bitch about it. the replies are coming back at the speed they
are sending right? Isn't it common Amateur to send only as fast as you
can copy?
Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 12/16/2014 2:04 PM, Dale Putnam wrote:
How about if you only want to rx full numbers... then don't call anyone that is
using cut numbers, while S&P,
and.. oh yes... and.. if you are running.. then send only full numbers and
don't qsl any cut numbers...
That being the standard to follow.. no one should have an issue with the "nil"
when sending cut numbers in
response to full numbers from the run station.
However.. whoa be to the run station that can't copy the full numbers at
exactly the same speed he sends them...
he may only get one chance....
and after a page of nils.. seen in the log reports.. maybe the op would get the
idea that even tho he has a big signal..
and can run all day.. requiring full numbers and sending faster than being able to rx...
will cause "nil" to arrive quickly.
Have a great day,
--... ...--
Dale - WC7S in Wy
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|