Return-Path: X-Spam-DCC: paranoid 1233; Body=3 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id t7S9lTHK005394 for ; Fri, 28 Aug 2015 11:47:29 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ZVGCT-00038B-Jo for rs_out_1@blacksheep.org; Fri, 28 Aug 2015 10:43:57 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ZVGCT-000382-7q for rsgb_lf_group@blacksheep.org; Fri, 28 Aug 2015 10:43:57 +0100 Received: from omr-m015e.mx.aol.com ([204.29.186.15] helo=omr-m015.mx.aol.com) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1ZVGBR-0003nV-9R for rsgb_lf_group@blacksheep.org; Fri, 28 Aug 2015 10:43:56 +0100 Received: from mtaout-aao01.mx.aol.com (mtaout-aao01.mx.aol.com [172.27.21.13]) by omr-m015.mx.aol.com (Outbound Mail Relay) with ESMTP id 16A9D38000A6; Fri, 28 Aug 2015 05:42:36 -0400 (EDT) Received: from White (ipb21bed2d.dynamic.kabel-deutschland.de [178.27.237.45]) by mtaout-aao01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id D641138000089; Fri, 28 Aug 2015 05:42:31 -0400 (EDT) Message-ID: <8FF119CE94CA487D9E930B9141356586@White> From: "Markus Vester" To: , "Markus Vester" Cc: , References: <55D9089A.1000908@verizon.net> <8D2AE31396F2FAB-FD8-35F1EE@webmail-vd011.sysops.aol.com> Date: Fri, 28 Aug 2015 11:42:40 +0200 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 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1440754956; bh=kAxLQC/BEnCGAoTz4kXkS5yPQ+vcwhJD3x+67o97v1A=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=mnog/tJ6E7LnXpksnB6B8rmpax+pfWnKqtE/723/b2LwWqZrIpEqmVCCrl8EtsKsP eh6RU/0yjH/ihhSYXAdT4SF1Xoe0Jsq+hQITATGYPW4dGjHFvb7kAL42jiOcZJbWEp Ugc7Qxh+2xYcuic0no0xWzLY8kMWWgjzgRwpS0Dg= x-aol-sid: 3039ac1b150d55e02d0716ea X-AOL-IP: 178.27.237.45 X-HELO-Warning: Remote host 204.29.186.15 (omr-m015e.mx.aol.com) used invalid HELO/EHLO omr-m015.mx.aol.com - verification failed X-Scan-Signature: 62fc2827c05a630837daa4729d9cda83 Subject: Re: LF: Wildwood (USA) eLoran Transmitter Operations Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01D0E186.A4FE7070" 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-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 4000 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0015_01D0E186.A4FE7070 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The reason why Wildwood had not appeared on my monitor was a subtle = deviation in the absolute timing of the currently ongoing transmission. = This placed the received pulses outside of my narrow one-millisecond = monitoring slot. During the second night I ran an extended full-GRI = monitor, showing that Wildwood was emitting 43 ms behind the nominal = Loran time frame. Steve Bartlett from UrsaNav confirmed that the = transmitter timing and control system had actually been replaced a week = ago. Last night, the extra delay was incorporated in our LoranView = monitors, resulting in good traces both in Tasmania = (https://dl.dropboxusercontent.com/u/101251787/Loran%20C/LoranView.htm) = and in Nuernberg (http://www.df6nm.de/LoranView/LoranGrabber.htm). The time offset has no effect on the quality of Loran time difference = measurements, it becomes apparent only when comparing between different = Loran GRI's or versus GPS. I'm wondering if anyone in the time-nuts = group has noticed it... Best 73, Markus (DF6NM) From: Markus Vester=20 Sent: Wednesday, August 26, 2015 6:13 PM To: rsgb_lf_group@blacksheep.org=20 Cc: stanw1le@verizon.net ; stephen.bartlett@ursanav.com=20 Subject: Re: LF: Wildwood (USA) eLoran Transmitter Operations Last night no signal was received in Nuernberg on GRI 8970. Did anyone = in the US hear it yet? Best 73, Markus (DF6NM) -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Stan W1LE An: rsgb_lf_group ; FMT-nuts = ; Lowfer Verschickt: So, 23 Aug 2015 1:44 am Betreff: LF: Wildwood (USA) eLoran Transmitter Operations Hello The Net: For those with a LF interest,=20 For those that use LORAN to generate their reference frequencies, Wildwood, New Jersey, USA, will be transmitting next week for = experimentation. Stan, W1LE Cape Cod FN41sr -------- Forwarded Message --------=20 Subject: Wildwood eLoran Transmitter Operations=20 Date: Fri, 21 Aug 2015 20:44:19 +0000=20 From: Stephen Bartlett =20 To: Stephen Bartlett =20 The Wildwood eLoran transmitter will be continuously broadcasting from = 0900 (EDT) on 25 August 2015 through 1800 (EDT) on 28 August 2015. = Wildwood will be broadcasting as 8970 Master and Secondary. Regards, Steve Bartlett Vice President, LF Operations UrsaNav, Inc. 85 Rangeway Road Building 3 Suite 110 North Billerica, MA. 01862 =20 ------=_NextPart_000_0015_01D0E186.A4FE7070 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
The = reason=20 why Wildwood had not appeared on my monitor was a subtle = deviation in=20 the absolute timing of the currently ongoing transmission. = This placed=20 the received pulses outside of my narrow one-millisecond = monitoring slot.=20 During the second night I ran an extended full-GRI=20 monitor, showing that Wildwood was emitting 43 ms behind the = nominal=20 Loran time frame. Steve Bartlett from UrsaNav confirmed that the = transmitter=20 timing and control system had actually been replaced a week ago. Last = night, the=20 extra delay was incorporated in our LoranView monitors, resulting = in good=20 traces both in Tasmania (https://dl.dropboxusercontent.com/u/101251787/Loran%20C/LoranView.h= tm)=20 and in Nuernberg (http://www.df6nm.= de/LoranView/LoranGrabber.htm).
 
The time offset has no effect on the = quality of=20 Loran time difference measurements, it becomes apparent only when = comparing=20 between different Loran GRI's or versus GPS. I'm wondering if anyone in = the=20 time-nuts group has noticed it...
 
Best 73,
Markus (DF6NM)
 
 

From:=20 Markus Vester
Sent: Wednesday, August = 26, 2015 6:13=20 PM
To: rsgb_lf_group@blacksheep.org
Cc: stanw1le@verizon.net ;=20 stephen.bartlett@ursanav.com
Subject: Re: LF: Wildwood = (USA) eLoran=20 Transmitter Operations

 
Last night no signal was = received in=20 Nuernberg on GRI 8970. Did anyone in the US hear it yet?
 
Best 73,
Markus (DF6NM)

-----Urspr=C3=BCngliche Mitteilung----- =
Von: Stan=20 W1LE <stanw1le@verizon.net>
An:=20 rsgb_lf_group <rsgb_lf_group@blacksheep.org>; FMT-nuts <FMT-nuts@yahoogroups.com>;=20 Lowfer <Lowfer@mailman.qth.net>
Verschickt: So, 23 Aug 2015 1:44 am
Betreff: LF: = Wildwood=20 (USA) eLoran Transmitter Operations

Hello The Net:

For those with a LF interest,
For = those=20 that use LORAN to generate their reference frequencies,
Wildwood, New = Jersey,=20 USA,  will be transmitting next week for = experimentation.

Stan,=20 W1LE    Cape Cod   FN41sr


-------- = Forwarded Message=20 --------
Subject:
Wildwood eLoran Transmitter=20 Operations
Date:
Fri, 21 Aug 2015 20:44:19=20 +0000
From:
Stephen Bartlett <Stephen.Bartlett@ursanav.com>
To:
Stephen Bartlett <Stephen.Bartlett@ursanav.com>


The Wildwood = eLoran=20 transmitter will be continuously broadcasting from 0900 (EDT) on 25 = August 2015=20 through 1800 (EDT) on 28 August 2015. Wildwood will be broadcasting as = 8970=20 Master and Secondary.
 
 
 
Regards,
Steve Bartlett
Vice President, LF Operations
 
UrsaNav, Inc.
85 Rangeway Road
Building 3
Suite 110
North Billerica,=20 MA. 01862
 
      


------=_NextPart_000_0015_01D0E186.A4FE7070--