Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk04.r1000.mx.aol.com (Internet Inbound) with ESMTP id E9CC93800008D; Sun, 28 Oct 2012 17:34:29 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSaS2-0000Xd-78 for rs_out_1@blacksheep.org; Sun, 28 Oct 2012 21:31:22 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSaS1-0000XU-Fd for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 21:31:21 +0000 Received: from mail-bk0-f43.google.com ([209.85.214.43]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1TSaRy-0003be-Ab for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 21:31:20 +0000 Received: by mail-bk0-f43.google.com with SMTP id w5so1797358bku.16 for ; Sun, 28 Oct 2012 14:31:17 -0700 (PDT) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=FqLYRxdzKZcmREqUKUdEaL5OPe2cBbaMf0/DjMjMgMg=; b=T8a4qjf+QnR/q3FwRhnGvmf5zGg6kCBxc+zdR65RBXqEA9sewLkZKC0L5pvd/5Ih9M 6A53H72+5//h6O1eqTpz992GyrY3ktw3po8RfmNR14YuGWVMcl/ZYfLy8/huVmM4PLRu Gkktb9kZKNDUOT8znCEt4JDu0JTEgRLUSKr87m/a/S2oP2P2zA14Ay6zm6trznKnAMk8 1njMx2cnnefA0IcVTawe3h0KSNFzedNRS3/MwdeEBKgS6BSV1KGEkx/b9mhGgh237L0O mQWWKDKyDd+sdOxf/Z1Ypx3RcfifaED+uKjyegEzqjMFquwzHfpOcyVoF9hSbfq9vuiu 78bg== MIME-Version: 1.0 Received: by 10.204.5.204 with SMTP id 12mr8827318bkw.89.1351459877058; Sun, 28 Oct 2012 14:31:17 -0700 (PDT) Received: by 10.205.40.197 with HTTP; Sun, 28 Oct 2012 14:31:16 -0700 (PDT) In-Reply-To: <508D92BE.2040500@broadpark.no> References: <508D86B7.1030001@princeton.edu> <508D92BE.2040500@broadpark.no> Date: Sun, 28 Oct 2012 21:31:16 +0000 Message-ID: From: Roger Lapthorn To: rsgb_lf_group@blacksheep.org, rsgb_lf_group@yahoogroups.co.uk X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Joe (et al), In the end I deleted and reinstalled the r2695 version (the one on the WSPRnet page http://wsprnet.org/drupal/) and it appears to be stable here now. If there are later versions I guess the link from the WSPRnet page should be updated regularly. [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [209.85.214.43 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rogerlapthorn[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 479f887a0af49374011bd47f9dfa3263 Subject: Re: LF: JT9 buggy issues Content-Type: multipart/alternative; boundary=00151758b1f4e6771204cd2545c3 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE 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-AUTHENTICATION: mtain-mk04.r1000.mx.aol.com ; domain : gmail.com DKIM : pass x-aol-sid: 3039ac1d6188508da4e50d79 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none --00151758b1f4e6771204cd2545c3 Content-Type: text/plain; charset=ISO-8859-1 Joe (et al), In the end I deleted and reinstalled the r2695 version (the one on the WSPRnet page http://wsprnet.org/drupal/) and it appears to be stable here now. If there are later versions I guess the link from the WSPRnet page should be updated regularly. Is it possible to develop the JT9 mode to allow both QSO and beacon modes to co-exist? One of the issues currently is there are, arguably, too many different weak signal modes. If JT9-x could provide both QSO modes and beacon modes (with internet database linking), there is a likelihood that this would become the *de-facto* digital mode (other than CW) for all MF/LF purposes. BTW, G3XIZ was a good signal on 500kHz JT9-2 here sending G3XIZ TEST earlier. We hope to have a QSO very soon. 73s Roger G3XBM On 28 October 2012 20:17, Steinar Aanesland wrote: > Roger , I think the latest ver is r2698 > http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.exe > > Here is from Joe, K1JT earlier today > > ---- > > > "Many thanks for all the early feedback on WSJT-X, both on- and off-list. > > A number of users have reported that PTT is not being properly released > when as transmission is finished. I have not yet found a computer that > exhibits this problem... and needless to say, it did not arise for any > of us who made the first on-the-air tests. For this reason, running > this bug down has not been easy. > > If you have experienced this problem, please try replacing the wsjtx.exe > that you got with the download with one I have posted at > http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.exe > > Depending on the nature of the problem, this one might issue an error > message when it fails to turn off the PTT successfully. Or it might > solve your problem, as it did for W7IUV. > > One important note went out to the first testers, but was not in my more > open announcement. This early program version may not properly > re-initialize all parameters when you change between JT9 submodes. To > be sure, it's probably best to restart the program after changing modes. > This will be fixed soon! > > I see that despite these early teething problems, a number of QSOs are > being made tonight with JT9. I look forward to hearing summaries of > your experiences! > > -- 73, Joe, K1JT > > > > > > > > > > > > > > > > > > > > > > > > > > > LA5VNA Steinar > loc:JO59jq > Mal and spam filtering: STRONG > www.opera.no > > Den 28.10.2012 20:58, skrev Roger Lapthorn: > > Joe, > > > > Can you confirm the latest version is 01r2695.exe please? > > > > 73s > > Roger G3XBM > > > > On 28 October 2012 19:25, Joe Taylor wrote: > > > >> Hi Roger, > >> > >> > >> After about 1 minute or so, the program just closes itself and > disappears > >>> from the PC screen. > >>> > >> > >> Please open a command-prompt window and start the program from there. > For > >> example, > >> > >> C:\> cd \wsjtx > >> C:\> wsjtx > >> > >> When the program dies, send me any error message left in the > >> command-prompt window. > >> > >> > >> I am using a SignalLink VOX controlled sound card interface that I use > for > >>> WSPR. Also, when I reload the program I have to reload my callsign, > grid > >>> etc.every time. > >>> > >> > >> This makes it sound like you may have ignored the installation advice in > >> the Quick-Start Guide: "Under Vista or Windows 7 be sure to install > WSJT-X > >> into its own directory (the suggested default is c:\wsjtx) rather than > >> C:\Program Files\wsjtx." Please confirm. > >> > >> > >> Although I very much hope to use the mode for QSOs please do not > >>> underestimate the value of a weak signal beaconing function with an > >>> internet database. This has proved extremely valuable on WSPR as people > >>> sometimes leave a RX and PC running to monitor when they are busy and > not > >>> available for QSOs. There will be far more people able to receive and > >>> report than TX on MF/LF. This is especially true on 136kHz. > >>> > >> > >> Yes, I understand these points, and beacons have their place. WSPR > would > >> not be there if I did not believe this. > >> > >> The question in my mind is the degree to which beacon-like features > should > >> be mixed with a mode designed for making QSOs. If beaconing behavior is > >> desired, why not use WSPR? If it's important to have, say, 10 dB better > >> sensitivity than WSPR, then maybe a "slow WSPR" mode should be developed > >> and used, rather than JT9. > >> > >> -- 73, Joe, K1JT > >> > >> > > > > > > > -- http://g3xbm-qrp.blogspot.com/ http://www.g3xbm.co.uk https://sites.google.com/site/sub9khz/ http://qss2.blogspot.com/ --00151758b1f4e6771204cd2545c3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Joe (et al),

In the end I deleted and reinstalled the r2695 version = (the one on the WSPRnet page http://= wsprnet.org/drupal/) and it appears to be stable here now.=A0 If there = are later versions I guess the link from the WSPRnet page should be updated= regularly.

Is it possible to develop the JT9 mode to allow both QSO and beacon mod= es to co-exist? One of the issues currently is there are, arguably, too man= y different weak signal modes. If JT9-x could provide both QSO modes and be= acon modes (with internet database linking), there is a likelihood that thi= s would become the de-facto digital mode (other than CW) for all MF/= LF purposes.

BTW, G3XIZ was a good signal on 500kHz JT9-2 here sending G3XIZ TEST ea= rlier. We hope to have a QSO very soon.

73s
Roger G3XBM


On 28 October 2012 20:17, Steinar Aaneslan= d <saanes@broadpark.no> wrote:
Roger , I think the latest ver is r2698
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.exe

Here is from Joe, K1JT earlier today

----


"Many thanks for all the early feedback on WSJT-X, both on- and off-li= st.

A number of users have reported that PTT is not being properly released
when as transmission is finished. =A0I have not yet found a computer that exhibits this problem... and needless to say, it did not arise for any
of us who made the first on-the-air tests. =A0For this reason, running
this bug down has not been easy.

If you have experienced this problem, please try replacing the wsjtx.exe that you got with the download with one I have posted at
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.exe

Depending on the nature of the problem, this one might issue an error
message when it fails to turn off the PTT successfully. =A0Or it might
solve your problem, as it did for W7IUV.

One important note went out to the first testers, but was not in my more open announcement. =A0This early program version may not properly
re-initialize all parameters when you change between JT9 submodes. =A0To be sure, it's probably best to restart the program after changing modes= .
=A0This will be fixed soon!

I see that despite these early teething problems, a number of QSOs are
being made tonight with JT9. =A0I look forward to hearing summaries of
your experiences!

=A0 =A0 -- 73, Joe, K1JT


























LA5VNA Steinar
loc:JO59jq
Mal and spam filtering: STRONG
www.opera.no

Den 28.10.2012 20:58, skrev Roger Lapthorn:
> Joe,
>
> Can you confirm the latest version is 01r2695.exe please?
>
> 73s
> Roger G3XBM
>
> On 28 October 2012 19:25, Joe Taylor <joe@princeton.edu> wrote:
>
>> Hi Roger,
>>
>>
>> =A0After about 1 minute or so, the program just closes itself and = disappears
>>> from the PC screen.
>>>
>>
>> Please open a command-prompt window and start the program from the= re. For
>> example,
>>
>> C:\> cd \wsjtx
>> C:\> wsjtx
>>
>> When the program dies, send me any error message left in the
>> command-prompt window.
>>
>>
>> =A0I am using a SignalLink VOX controlled sound card interface tha= t I use for
>>> WSPR. Also, when I reload the program I have to reload my call= sign, grid
>>> etc.every time.
>>>
>>
>> This makes it sound like you may have ignored the installation adv= ice in
>> the Quick-Start Guide: "Under Vista or Windows 7 be sure to i= nstall WSJT-X
>> into its own directory (the suggested default is c:\wsjtx) rather = than
>> C:\Program Files\wsjtx." =A0Please confirm.
>>
>>
>> =A0Although I very much hope to use the mode for QSOs please do no= t
>>> underestimate the value of a weak signal beaconing function wi= th an
>>> internet database. This has proved extremely valuable on WSPR = as people
>>> sometimes leave a RX and PC running to monitor when they are b= usy and not
>>> available for QSOs. There will be far more people able to rece= ive and
>>> report than TX on MF/LF. This is especially true on 136kHz. >>>
>>
>> Yes, I understand these points, and beacons have their place. =A0W= SPR would
>> not be there if I did not believe this.
>>
>> The question in my mind is the degree to which beacon-like feature= s should
>> be mixed with a mode designed for making QSOs. =A0If beaconing beh= avior is
>> desired, why not use WSPR? =A0If it's important to have, say, = 10 dB better
>> sensitivity than WSPR, then maybe a "slow WSPR" mode sho= uld be developed
>> and used, rather than JT9.
>>
>> =A0 =A0 =A0 =A0 -- 73, Joe, K1JT
>>
>>
>
>





--
=A0http://g3xbm-qrp.blogspot.com/
<= a href=3D"http://www.g3xbm.co.uk">http://www.g3xbm.co.uk
https://sites.google.com/site/sub9k= hz/
http://qss2.blogspot.com/

=
--00151758b1f4e6771204cd2545c3--