[Skimmertalk] RTTYserv and Russian beacon

[Pete Smith N4ZR]

It is somewhat more complicated in RTTY SkimServ.  There is a second 
.ini file that contains expected CQ patterns and their relative 
probability, both for normal operation and for specific contests.  I 
presume that RTTY SkimServ is more skeptical if it copies a 
low-probability pattern - that is, it requires more repetitions or other 
confirmatory information before identifying that transmission as a CQ.

73, Pete N4ZR
Check out the Reverse Beacon Network at
http://reversebeacon.net,
blog at reversebeacon.blogspot.com.
For spots, please go to your favorite
ARC V6 or VE7CC DX cluster node.

On 3/3/2015 8:14 AM, Larry - K1UO wrote:
> Is there a CQ  or TEST qualifier also in RTTY Mode that needs to be 
> met within the RTTY Skimmer software before the callsign is reported?
>
> -----Original Message----- From: Dai NAGAKURA
> Sent: Tuesday, March 03, 2015 7:58 AM
> To: skimmertalk at contesting.com
> Subject: Re: [Skimmertalk] RTTYserv and Russian beacon
>
> Thnak you Pete and Wes
> Well,It's interesting phenomenon that RTTYSkimmer decodes
> morse code as callsign.
>
> Here I notice again JA's new band plan from Apr.2015
> http://www.jarl.org/English/6_Band_Plan/JapaneseAmateurBandplans20150105.pdf 
>
> Unfortunately,80m's complex hashed band will never be solved.
> There are for JA's air forces
>
> Best wishes
>
> Dai JF2IWL
>
> On Tue, 03 Mar 2015 06:23:31 -0500
> Pete Smith N4ZR <n4zr at contesting.com> wrote:
>
>> Hi Dai - and thank you for a thought-provoking report.  It's interesting
>> to me that these beacons are being decoded by RTTY Skimserv - I wonder
>> what is causing that.  I had understood that stations in ITU Region 2
>> were not using RTTY on 40M below 7040.  If that is correct, then maybe a
>> solution for this would be to set a 40M RTTY segment's lower limit at no
>> lower than 7040 unless you wanted to see thise beacons.  This is just a
>> first thought.
>>
>> 73, Pete N4ZR
>> Check out the Reverse Beacon Network at
>> http://reversebeacon.net,
>> blog at reversebeacon.blogspot.com.
>> For spots, please go to your favorite
>> ARC V6 or VE7CC DX cluster node.
>>
>> On 3/3/2015 5:36 AM, Dai NAGAKURA wrote:
>> > Dear members,, de JF2IWL
>> >
>> > About the subject.
>> > I and N7TR ,9V1RM JK4USW catch well known "Russian beacon"as 
>> callsigin,
>> > OU5TK, OA5TU ,etc by RTTYSkimserv on 40mb.
>> > This is a report of OU5TK on RBN
>> > http://www.reversebeacon.net/dxsd1/dxsd1.php?f=0&c=ou5tk&t=dx
>> >
>> > Here is a frequency sheet of Russian beacon in amateur bands
>> > (article is written in Japanese but you can read sheet)
>> > http://jq1yda.org/topics/russiansbeacon/index.html
>> >
>> >   We catchs Vladivostok's consecutive morse code "F"
>> > as amateur callsign OU5TK etc
>> >
>> > I have talked with WZ7I Wes about this the other day.
>> > He agreed my opinion leave these be a good beacon of
>> > low band propagation.
>> >
>> > However, it happens frequently day by day and
>> > callsign variety increases TU5TA,TU9TU and so on.
>> > This shall make trouble now.
>> >
>> > Then I decided  I will put all these to BadCal.txt when find,
>> > refering to QRZ.com
>> > Please allow when strange callsingn is listed on 7039.2
>> >
>> > Dai JF2IWL
>> >
>>
>> _______________________________________________
>> Skimmertalk mailing list
>> Skimmertalk at contesting.com
>> http://dayton.contesting.com/mailman/listinfo/skimmertalk
>