Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-da04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 4DD3A38000082; Sat, 28 Jan 2012 02:46:35 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Rr2yJ-0005aW-CU for rs_out_1@blacksheep.org; Sat, 28 Jan 2012 07:45:15 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Rr2yI-0005aN-Ab for rsgb_lf_group@blacksheep.org; Sat, 28 Jan 2012 07:45:14 +0000 Received: from imr-da04.mx.aol.com ([205.188.105.146]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1Rr2yF-0001wX-Ly for rsgb_lf_group@blacksheep.org; Sat, 28 Jan 2012 07:45:14 +0000 Received: from mtaout-mb04.r1000.mx.aol.com (mtaout-mb04.r1000.mx.aol.com [172.29.41.68]) by imr-da04.mx.aol.com (8.14.1/8.14.1) with ESMTP id q0S7j8dQ019933 for ; Sat, 28 Jan 2012 02:45:08 -0500 Received: from White (nrbg-4dbf02d3.pool.mediaWays.net [77.191.2.211]) by mtaout-mb04.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id EA9A2E000094 for ; Sat, 28 Jan 2012 02:45:02 -0500 (EST) Message-ID: <8C097DB70AC04889AC2CD56E33E8DCA5@White> From: "Markus Vester" To: References: <3992CC59F7A14AA694628529761EC5DE@AGB> <4F1F695F.7020400@charter.net> <28E5D61E1299414C8AD335047F7EE837@White> <4F2213B0.2030107@charter.net> <4F22901C.8060503@charter.net> <7667FF6C11E54298B5CAA2280D2B436C@White> <001201ccdcf9$70fbcf60$6d01a8c0@DELL4> <1327690467.44701.YahooMailNeo@web125901.mail.ne1.yahoo.com> Date: Sat, 28 Jan 2012 08:45:00 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1327736708; bh=IWc6EGCWkj3VJlVAO2MEqjRJkDRzRLtYWgbGZLSXXS8=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=a0CPuHS6sWp7xqkFMhMOI8ehUxF7aI1Mlnsp5UN/kgcAyi+7qqXPoUcwHep+ODWLw N6Ln0n2dglw9Ps1krHDbG/69hHOeD/Ld57qYcmU76O0J+T7H0PNJNduunc9/tAPc4a NBSUfxOYepHWz1D3lbg3jByQW8F6QrOGfkulZeZU= X-AOL-SCOLL-SCORE: 0:2:459940512:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: WOLF: 135975 Hz, 10 b/s again Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CCDD99.1F27AB50" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:478367584:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m283.1 ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d404c4f23a7db7898 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0011_01CCDD99.1F27AB50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The little Wolf signal was on air from 23:05 to 07:15 this morning, with = ERP down by a dB or so because of snowfall. The phase monitor showed a = continuous steady frequency without a single glitch. Thanks again to all who have kept an eye open for me. At least we know = if we didn't succeed tonight, it was really due to suboptimal = propagation and/or insufficient ERP from my side. Best 73, and have a nice weekend Markus (DF6NM) From: Markus Vester=20 Sent: Saturday, January 28, 2012 12:01 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: WOLF: 135975 Hz, 10 b/s again Hi Andy, LF, actually there is no carrier line in the WOLF spectrum, it's BPSK with a = pseudorandom spreading code. In a spectrogram it resembles a 10 Hz wide = noise band, which will be pretty much undetectable at any DX range. = Actually a kind of spread spectrum mode, not unlike the GPS modulation = (pssst ;-). I think I have proven (and resolved) my soundcard phase-glitch problem. = The attached trace shows a local audio test, with a WOLF signal = generated on 1475 Hz. It is doubled in SpecLab's AM demodulator to = regenereate a carrier at twice the frequency, which is phase compared to = an hardware generated Rb-derived reference carrier. I have employed = SpecLab's RDF mode to display phase as colour (retarding R-B-G-R). The = first half shows the result from WOLF-Gui running on my "Grabber = Notebook", which has a number of programs running. Besides the gradual = phase roll due too a very minor frequency offset, there are jumps every = few minutes. This is a bit nasty, as Wolf will still decode such a = signal when it is strong, but not be able to go to its full sensitivity = by using long coherent integration. The right half after 21:40 shows the = practically perfect output from the Atom Netbook, the one which I have = also used during several VLF transmissions.=20 So, maybe it's worth another try. Will put the "good" WOLF signal on air = a few minutes after 23 UT, QRG 135975 Hz, 10 b/s. Best 73, Markus (DF6NM)=20 From: Andy - KU4XR=20 Sent: Friday, January 27, 2012 7:54 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: WOLF: 135975 Hz, 10 b/s My report is the same... no decodes... I wish as an after thought that I = had ran SpecLab also, to look for the carrier... maybe next time 73: =20 Andy - KU4XR - EM75xr - Friendsville, TN. USA Coordinates: N: 35=BA 43' 54" - W: 84=BA 3' 16" http://lwca.org/grabbers/ku4xr/ http://www.myspace.com/beaconxr http://ku4xr.webs.com http://lwca.org/community/YaBB.pl From: "jrusgrove@comcast.net" To: rsgb_lf_group@blacksheep.org=20 Sent: Friday, January 27, 2012 8:41 AM Subject: Re: WOLF: 135975 Hz, 10 b/s Markus No joy here either. Jay W1VD WD2XNS WE2XGR/2 ----- Original Message -----=20 From: Markus Vester=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Friday, January 27, 2012 7:50 AM Subject: Re: WOLF: 135975 Hz, 10 b/s Many thanks Andy, John and Dex for looking out for my WOLF signal. The = TX was running without interruption from 23 to 7 UT, PEP about 0.5 W = ERP.=20 One thing I still don't trust is the continuity of the soundcard = output. I guess the glitches which occasionally appear in QRSS dashes = might corrupt the long-term phase-coherence which is required for deep = WOLF decoding. Will have to look into that before the next attempt. Best 73, Markus (DF6NM) From: John Andrews=20 Sent: Friday, January 27, 2012 12:53 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: WOLF: 135975 Hz, 10 b/s Markus, No luck. Not a quiet night, and TA prop does not seem to have = recovered. John, W1TAG On 1/26/2012 10:02 PM, John Andrews wrote: > Markus, > > Nothing seen as of 0300, other than the usual infinite number of = monkeys > typing away. Will let it run overnight. > > John, W1TAG > > On 1/26/2012 5:39 PM, Markus Vester wrote: >> WOLF ... good idea! >> My TX antenna has been pushed up again tonight, and I intend to = howl for >> a couple of hours, starting 23:00 UT at 10 b/s speed. >> As CFH is still sitting smack in the middle of the band, I'll move = close >> to the lower edge, squeezing into a narrow HGA-sidebands gap on = *135975 >> Hz* (that is unless you may have other suggestions). >> Best 73, >> Markus (DF6NM) >> >> *From:* John Andrews >> *Sent:* Wednesday, January 25, 2012 3:30 AM >> *To:* rsgb_lf_group@blacksheep.org = >> *Subject:* Re: LF: WOLF DATA MODE S/N FIG ? >> >> Graham, >> >> There is no single s/n figure or specified BW in which to measure = it. >> WOLF works by building copy up over a period of time, and assuming = good >> frequency/phase stability, a half hour or more is practical. >> >> The data rate is fairly fast, 10 b/s, with a 960 bit message, so = that a >> complete frame of data is sent in 96 seconds. You get three quick >> reports in the first 96 seconds, and then decodes every 96 seconds >> after. Each message is 15 characters, with no rules about callsign >> format. >> >> Tests done some years ago show it roughly equivalent to QRSS60 in = terms >> of signal level. It does give some clues as to whether a signal has = been >> locked-in, and has the possibility of partial copy, unlike some = "all or >> nothing" modes. Fifteen characters in a half-hour is of course much >> faster than QRSS60 would permit. 2-way QSO's are fairly easy with = some >> advance agreement on what to do with the 15 characters. >> >> The downsides are the need for a linear transmitter system (as this = is >> PSK), receiver/transmitter stability and frequency accuracy. It = works at >> 600 meters, but is fairly useless at 160 meters and up. >> >> The newest version is by DL4YHF, and may be found at: >> http://www.qsl.net/d/dl4yhf//wolf/ . >> >> Note that this version has 5 b/s and 20 b/s variations. Testing has >> shown that the program tends to provide copy in the same amount of = time, >> so there's no overriding advantage to either. >> >> John, W1TAG >> >> On 1/24/2012 7:27 PM, Graham wrote: >> > WOLF DATA MODE S/N FIG ? >> > Long time since I used wolf , anyone have the >> > expected decode min s/n level ? >> > and now what s/n was ref to , as changes >> > may of taken place over time >> > Tnx -G. >> > >> > >> > >> > No virus found in this incoming message. >> > Checked by AVG - www.avg.com >> > Version: 8.5.454 / Virus Database: 271.1.1/4162 - Release Date: >> 01/23/12 19:34:00 >> > >> >> >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.454 / Virus Database: 271.1.1/4166 - Release Date: >> 01/25/12 20:07:00 >> > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.454 / Virus Database: 271.1.1/4166 - Release Date: = 01/25/12 20:07:00 > ------=_NextPart_000_0011_01CCDD99.1F27AB50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The little Wolf signal was on air from = 23:05 to=20 07:15 this morning, with ERP down by a dB or so because = of snowfall. The=20 phase monitor showed a continuous steady frequency without a=20 single glitch.
 
Thanks again to all who have kept an = eye open for=20 me. At least we know if we didn't succeed tonight, it was really = due to=20 suboptimal propagation and/or insufficient ERP from my = side.
 
Best 73, and have a = nice=20 weekend
 
Markus = (DF6NM)

Sent: Saturday, January 28, 2012 12:01 AM
Subject: Re: WOLF: 135975 Hz, 10 b/s again

Hi Andy, LF,
 
actually there is no carrier line in = the WOLF=20 spectrum, it's BPSK with a pseudorandom spreading code. In a = spectrogram=20 it resembles a 10 Hz wide noise band, which will be pretty = much=20 undetectable at any DX range. Actually a kind of spread spectrum = mode, not=20 unlike the GPS modulation (pssst ;-).
 
I think I have proven (and resolved) my = soundcard=20 phase-glitch problem. The attached trace shows a local audio test, with=20 a WOLF signal generated on 1475 Hz. It is doubled in SpecLab's AM=20 demodulator to regenereate a carrier at twice the frequency, which = is phase=20 compared to an hardware generated Rb-derived reference = carrier.=20 I have employed SpecLab's RDF mode to display phase as colour=20 (retarding R-B-G-R). The first half shows the result from WOLF-Gui = running=20 on my "Grabber Notebook", which has a number of programs=20 running. Besides the gradual phase roll due too a very minor = frequency=20 offset, there are jumps every few minutes. This is a bit = nasty,=20 as Wolf will still decode such a signal when it is strong, but not = be able=20 to go to its full sensitivity by using long coherent integration. The = right half=20 after 21:40 shows the practically perfect output from the Atom Netbook, = the one=20 which I have also used during several VLF=20 transmissions. 
 
So, maybe it's worth another try. Will = put the=20 "good" WOLF signal on air a few minutes after 23 UT, QRG 135975 Hz, = 10=20 b/s.
 
Best 73,
Markus (DF6NM) 
 
From: Andy - KU4XR
Sent: Friday, January 27, 2012 7:54 PM
Subject: Re: WOLF: 135975 Hz, 10 b/s

My report is the = same... no=20 decodes... I wish as an after thought that I had ran SpecLab also, to = look for=20 the carrier...
maybe next time
 
73:
 
Andy - KU4XR - EM75xr - Friendsville, TN. USA
Coordinates: N: = 35=BA 43'=20 54" - W: 84=BA 3' 16"
http://lwca.org/grabbers/ku4xr/<= /A>
http://www.myspace.com/beaconxr<= /A>
http://ku4xr.webs.com
http://lwca.org/community/YaBB= .pl

From: "jrusgrove@comcast.net"=20 <jrusgrove@comcast.net>
To: rsgb_lf_group@blacksheep.org=20
Sent: Friday, = January 27, 2012=20 8:41 AM
Subject: Re: = WOLF:=20 135975 Hz, 10 b/s

Markus
 
No joy here either.
 
Jay W1VD  WD2XNS  = WE2XGR/2
----- Original Message -----
From: Markus = Vester
Sent: Friday, January 27, 2012 = 7:50=20 AM
Subject: Re: WOLF: 135975 Hz, = 10=20 b/s

Many thanks Andy, John and Dex for = looking out=20 for my WOLF signal. The TX was=20 running without interruption from 23 to 7 UT, PEP about 0.5 = W=20 ERP. 
 
One thing I still don't trust is the = continuity=20 of the soundcard output. I guess the glitches=20 which occasionally appear in=20 QRSS dashes might corrupt the long-term=20 phase-coherence which is required for deep WOLF = decoding. Will=20 have to look into that before the next attempt.
 
Best 73,
Markus (DF6NM)
 
 
From: John Andrews=20
Sent: Friday, January 27, 2012 12:53 PM
Subject: Re: WOLF: 135975 Hz, 10 b/s

Markus,

No luck. Not a quiet night, and TA prop = does not=20 seem to have recovered.

John, W1TAG

On 1/26/2012 10:02 = PM, John=20 Andrews wrote:
> Markus,
>
> Nothing seen as of = 0300, other=20 than the usual infinite number of monkeys
> typing away. Will = let it run=20 overnight.
>
> John, W1TAG
>
> On 1/26/2012 = 5:39 PM,=20 Markus Vester wrote:
>> WOLF ... good idea!
>> My TX = antenna=20 has been pushed up again tonight, and I intend to howl for
>> = a=20 couple of hours, starting 23:00 UT at 10 b/s speed.
>> As CFH = is=20 still sitting smack in the middle of the band, I'll move = close
>> to=20 the lower edge, squeezing into a narrow HGA-sidebands gap on=20 *135975
>> Hz* (that is unless you may have other=20 suggestions).
>> Best 73,
>> Markus=20 (DF6NM)
>>
>> *From:* John Andrews <mailto:w1tag@charter.net>
= >>=20 *Sent:* Wednesday, January 25, 2012 3:30 AM
>> *To:* rsgb_lf_group@blacksheep.= org=20 <mailto:rsgb_lf_group@blac= ksheep.org>
>>=20 *Subject:* Re: LF: WOLF DATA MODE S/N FIG ?
>>
>>=20 Graham,
>>
>> There is no single s/n figure or = specified BW=20 in which to measure it.
>> WOLF works by building copy up = over a=20 period of time, and assuming good
>> frequency/phase = stability, a=20 half hour or more is practical.
>>
>> The data rate = is=20 fairly fast, 10 b/s, with a 960 bit message, so that a
>> = complete=20 frame of data is sent in 96 seconds. You get three quick
>> = reports=20 in the first 96 seconds, and then decodes every 96 seconds
>> = after.=20 Each message is 15 characters, with no rules about = callsign
>>=20 format.
>>
>> Tests done some years ago show it = roughly=20 equivalent to QRSS60 in terms
>> of signal level. It does = give some=20 clues as to whether a signal has been
>> locked-in, and has = the=20 possibility of partial copy, unlike some "all or
>> nothing" = modes.=20 Fifteen characters in a half-hour is of course much
>> faster = than=20 QRSS60 would permit. 2-way QSO's are fairly easy with some
>> = advance=20 agreement on what to do with the 15 = characters.
>>
>> The=20 downsides are the need for a linear transmitter system (as this = is
>>=20 PSK), receiver/transmitter stability and frequency accuracy. It works=20 at
>> 600 meters, but is fairly useless at 160 meters and=20 up.
>>
>> The newest version is by DL4YHF, and may = be found=20 at:
>> http://www.qsl.net/d/dl4yhf//wolf/ = .
>>
>>=20 Note that this version has 5 b/s and 20 b/s variations. Testing=20 has
>> shown that the program tends to provide copy in the = same=20 amount of time,
>> so there's no overriding advantage to=20 either.
>>
>> John, W1TAG
>>
>> On = 1/24/2012 7:27 PM, Graham wrote:
>> > WOLF DATA MODE S/N = FIG=20 ?
>> > Long time since I used wolf , anyone have = the
>>=20 > expected decode min s/n level ?
>> > and now what s/n = was ref=20 to , as changes
>> > may of taken place over = time
>> >=20 Tnx -G.
>> >
>> >
>> >
>> = > No=20 virus found in this incoming message.
>> > Checked by AVG = - www.avg.com=20 <http://www.avg.com>
>> > Version: 8.5.454 / Virus = Database:=20 271.1.1/4162 - Release Date:
>> 01/23/12 19:34:00
>> = >
>>
>>
>>
>>
>> No = virus=20 found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.454 / Virus = Database:=20 271.1.1/4166 - Release Date:
>> 01/25/12=20 20:07:00
>>
>
>
>
> No virus found in = this=20 incoming message.
> Checked by AVG - www.avg.com
> Version: = 8.5.454 / Virus=20 Database: 271.1.1/4166 - Release Date: 01/25/12=20 20:07:00
>



------=_NextPart_000_0011_01CCDD99.1F27AB50--