Wow, there was a lot of activity for CQ WW RTTY! 20M and 15M were filled completely between 080-150kc above band edge, The "bottom ends" of the band were particularly crowded. I used 3 decoders simul
Tim wrote: "The frequency resolution and accuracy seems to have improved in the skimmers in the past few years and often times I would click on a spot and be tuned within 10Hz, that is great!" Yes, i
Don, I ran Alex Skimmer Server on a local QS1R in the WPX earlier this year and the results were hard to believe. Performance was exceptional. And the benefit is that 100% of the spots are workable b
Tim Interesting comments. I wonder which decoder or was it decoders you were using in 2Tone? They are there for a purpose. I normally run two 2Tones per DI one with selective decoder and the other wi
One potential step toward improved RTTY Skimserv results is to use the CT1BOH "skimquality" filters available through AR Cluster V6. See <http://reversebeacon.blogspot.com/2013/12/a-new-tutorial-on-u
-- Original Message -- Tim You were implying that something is wrong with my node's default filtering. Your own filtering at the VE7CC-1 cluster node was last updated Dec 14, 2014. Your country filte
Jeff, I'd be interested to know to what you attribute the reduction in the number of S&P mis-spots. Is it simply because with many Skimmers spotting this year, the chance of someone mistakenly spotti
Wow, thanks for all the responses! Most especially to Lee VE7CC himself, who helped me figure out how to reset a filter I had apparently applied over a year ago (probably by clicking on the "NE ONLY"
What I think usually happens is the skimmer cannot tell the difference between who is who.....so since most people now append their CQ message with CQ, it goes like this.... CQ AA5AU AA5AU CQ and the
Quick fix. Don't send the 'DE' before your call. It is absolutely unnecessary! Gary AL9A Sent from my Kindle HDX What I think usually happens is the skimmer cannot tell the difference between who is
Jamie How sending this. "{enter}WW3S WW3S ". Maybe this would break the association between the CQ from AA5AU and you better and not spot you. I seem to rarely get spotted during S&P and this is what
Oops .... Correction I meant to say: How about sending this. "{enter}WW3S WW3S ". etc -- Original Message -- Jamie How sending this. "{enter}WW3S WW3S ". Maybe this would break the association betwee
'T would not be a problem if you started your DE WW3S WW3S message with <CR><LF> The skimmers would then see two different calls/stations 73, ... Joe, W4TV On 9/29/2015 6:57 PM, WW3S wrote: What I th
The last time I rewrote my collection of RTTY contest macros (about a year ago?), I thought that the consensus on best practice was to use CRLF's sparingly, only at the start of a CQ, in order to be
Pete, Sorry for the confusion. Let me expand a bit... I dont' have much battle-experience running assisted; just the one time WPX 2014 run. I ran my local skimmer server setup here fed by my antenna
Not only is it a waste of time, DE can be a source of error. More than once last weekend the state did not decode and the DE did, leading me to believe that the station I was working was in Delaware.
According to Pete's (N4ZR) post today, "{enter}WW3S WW3S" is suppose to break the association from the CQ but it doesn't appear to be true in some cases. Putting a C/R L/F {enter} in front of nearly
One way of eliminating the problem is to analyse the previous text. So if received was CQ M7T M7T CQ AA5AU AA5AU there is sufficient information to parse the text to realise the CQ is by M7T and the
I use spaces exclusively. Beginning and end of every macro. I wish everyone did. You won't read DTEGJW4UKEW5 when I sign my call, _and_ your print won't scroll up. Jerry W4UK At 11:45 PM 9/29/2015, M
It's interesting that in my original post, I said I wanted as little filtering on skimmed spots as possible - something VE7CC was quick to help me with. When my run rate slows down, I do not mind cli