Return-Path: X-Spam-DCC: paranoid 1233; Body=2 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 u11MS1CX001997 for ; Mon, 1 Feb 2016 23:28:01 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aQMtB-0004hw-ML for rs_out_1@blacksheep.org; Mon, 01 Feb 2016 22:24:05 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aQMtB-0004hn-9Z for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 22:24:05 +0000 Received: from mail-wm0-f45.google.com ([74.125.82.45]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aQMsB-0006Wa-D4 for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 22:24:04 +0000 Received: by mail-wm0-f45.google.com with SMTP id p63so92675464wmp.1 for ; Mon, 01 Feb 2016 14:22:48 -0800 (PST) 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=svpLtgnO6uy1KOscgwzk9E7lEqmjN17mZSe1Kd6PO5E=; b=UL103k4xJ/rkcPapQ3lEOKYQjv/wLPOqz1iu01k7pHotwBxF/fgoIBGE3G4WPmBNIQ JEJ704G0qxk8t+MZkqoJfhuJJk9sFHTfeO0otXIXn8OLh2UP2owxgp70cR0MBId4R3ev bJU6NcbpTKfOW7HwE7kxFzegClG4wlVAFfCIl3Zg0W0OxqjItNgOQpxqygLBFmDL1u+l A4r/QMr8xTPmPjtFic28/UWlIFp+OIOZ4YFsUiLctK2cSkthvWD+QX6ZOwPRllFTMyvi Z/bSy7RFwXxhO5bGPxuouNhcM2RHiYKlLsvzGvbOwZrBxnE6GTR7mTD4YqEfEhYkD9v/ FUdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=svpLtgnO6uy1KOscgwzk9E7lEqmjN17mZSe1Kd6PO5E=; b=H6z7qifiVxzXcyFeEQMnAj7RkJSijMtZ7NtOzd3BDfqk/L0tkTV9ZfmNTIm7nneDKU f3+sy/BFl8P2I1kLN9zZr3ZreYY71XEL86+KZS/6KkzVUjgoO/HqPNAIHFlKYScBi39e vt6QGmuYf2gbh7Mu7ZU8pnpaeSbCm1pLD5X9dcoS9wzWKCXtR3fTL7gJdNIALLHzdfBx EFvo/CxKkNoVmouR30RCAe27KC9xe3gQdVuAXAXb8Khfev757iLBfzL/uQwRVnGoTAYd 6ZjTf4j0OWCXy4M+INXr8TVlLD1/4XnyBhptv6vP8vXaZAgQBz+ZRJGepc0FZm08oW5c sulw== X-Gm-Message-State: AG10YOSuuAEpEPP1kNOmatyt+k9AzS4SWPejCRH1kzs0JrGinKzc55PvZM79VujjOCGRs1ADjPcbYNom4gDLHQ== MIME-Version: 1.0 X-Received: by 10.194.142.135 with SMTP id rw7mr20635627wjb.42.1454365322870; Mon, 01 Feb 2016 14:22:02 -0800 (PST) Received: by 10.28.187.67 with HTTP; Mon, 1 Feb 2016 14:22:02 -0800 (PST) In-Reply-To: References: <56AFA07E.4040001@charter.net> Date: Mon, 1 Feb 2016 22:22:02 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org X-Scan-Signature: 29f1b43ee9e13e220716185d38bfb88c Subject: Re: LF: JT9 Coding? Content-Type: multipart/alternative; boundary=089e013a1de071897e052abcd0a5 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: 6626 --089e013a1de071897e052abcd0a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh yes, so it does. "i have a dog" also fails. as do quite a lot of variants on that Could it be trying to recognise the string as a callsign or QSO message, and trying to compress it using the different technique that entails. Then getting things wrong because the text fails as a valid callsign? 'jnt On 1 February 2016 at 22:08, wrote: > =E2=80=A6 I did so. jt9code =E2=80=9C1 2 3 4 5=E2=80=9C and =E2=80=9Ci ha= ve acat=E2=80=9C etc. worked fine, but =E2=80=9Ci > have a cat=E2=80=9C with three spaces resulted in a mysterious =E2=80=9CI= nternal Error: EOF > condition not handled-- END=3D tag needed=E2=80=9C. Never mind, easy to w= ork around. > > > > 73, Markus > > > > > *Von: *Andy Talbot > *Gesendet: *Montag, 1. Februar 2016 22:58 > *An: *rsgb_lf_group@blacksheep.org > *Betreff: *Re: LF: JT9 Coding? > > > > If your message has spaces in it, you need to place quotation marks aroun= d > the message. > > > > 'jnt > > > > > > On 1 February 2016 at 21:35, wrote: > > Thanks a lot Andy, that=E2=80=99s exactly what I was looking for. It=E2= =80=99s not obvious > on the website but the download URL is > > http://physics.princeton.edu/pulsar/K1JT/jt9code.exe > > > > Interestingly, =E2=80=9Ei have a cat=E2=80=9C throws an error but =E2=80= =9Ei_have_a_cat=E2=80=9C did what > I wanted. > > > > Rik, Vinny, my term =E2=80=9Elinear transmitter=E2=80=9C was probably ina= ccurate wording, > I just meant an SSB mixer from audio to RF. > > > > Best 73, > > Markus > > > > > > > *Von: *Andy Talbot > *Gesendet: *Montag, 1. Februar 2016 21:39 > *An: *rsgb_lf_group@blacksheep.org > *Betreff: *Re: LF: JT9 Coding? > > > > There is a separate utility called JT9CODE, downloadable from the WSJT > website > > There is a similar one for JT65 > > > > They are a bit convoluted to use, so I wrote wrappers for them to > intercept the output to screen and send to formatted files for including > within PIC .assembler files > > > > Andy G4JNT > > > > > > On 1 February 2016 at 20:22, wrote: > > While we=E2=80=99re at it=E2=80=A6 I recently missed the JT9 activity ni= ght, mostly due > to the lack of a linear MF transmitter. For WSPR, I=E2=80=99ve used a com= mandline > tool (wsprcode.exe, or wspr.exe with -tx option) to encode a message to a > file. This is then read by a little homemade program (ddswspr.exe), which > feeds an AD9850 DDS module through the serial port. > > > > Does anyone know whether a similar encoding option exists for JT9? > > > > Best 73, > > Markus (DF6NM) > > > > > *Von: *John Andrews > *Gesendet: *Montag, 1. Februar 2016 19:17 > *An: *rsgb_lf_group@blacksheep.org > *Betreff: *Re: LF: WOLF Coding > > =E2=80=A6 > > > > "If you have a BPSK-capable beacon which uses an EEPROM to store its > > message, WOLF can generate a binary file suitable for programming the > > device. > > =E2=80=A6 > > > > > > > > > > > --089e013a1de071897e052abcd0a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Oh yes, so it does. =C2=A0 "i have a dog" =C2=A0= also fails.=C2=A0
as do quite a lot of variants on that

=
Could it be trying to recognise the string as a callsign or QSO = message, and trying to compress it using the different technique that entai= ls.=C2=A0 Then getting things wrong because the text fails as a valid calls= ign?

'jnt


On 1 February 2016 at 22:08= , <markusvester@aol.com> wrote:

=E2=80=A6 I did so. jt9code =E2=80=9C1 2 3 4 5=E2=80=9C and =E2= =80=9Ci have acat=E2=80=9C etc. worked fine, but =E2=80=9Ci have a cat=E2= =80=9C with three spaces resulted in a mysterious =E2=80=9CInternal Error: = EOF condition not handled-- END=3D tag needed=E2=80=9C. Never mind, easy to= work around.

=C2=A0<= /p>

73, Markus

= =C2=A0


Von: Andy Talbot
Gesendet: Montag, 1. Februar 2016 2= 2:58
An: rsgb_lf_group@blacksheep.org
Betreff: Re: LF: JT9= Coding?

=C2=A0

If your message has spaces in it, you need= to place quotation marks around the message.

=C2=A0

=

'jnt

=C2=A0

=C2=A0

On 1 February 2016 at 21:35, <markusvester@aol.com> wrote:=

Thanks a lot Andy, that=E2=80=99s exactly what I was l= ooking for. It=E2=80=99s not obvious on the website but the download URL is=

http://physics.princeton.e= du/pulsar/K1JT/jt9code.exe

=C2=A0

Interestingly, =E2=80=9Ei have a cat=E2=80=9C throws an erro= r but =E2=80=9Ei_have_a_cat=E2=80=9C did what I wanted.

=C2=A0

Rik, Vinny, my term =E2=80=9Elinear= transmitter=E2=80=9C was probably inaccurate wording, I just meant an SSB = mixer from audio to RF.

=C2=A0

Best 73,

Markus

=C2=A0

=C2=A0


Von: Andy Talbot
Gesendet: Montag, 1. Februar 2016 21:= 39
An: rsgb_lf_group@blacksheep.org
Betreff: Re: LF: JT9 Cod= ing?

=C2=A0

There is a separate utility called JT9CODE, downloadable fro= m the WSJT website

There is a sim= ilar one for JT65

=C2=A0<= /span>

They are a bit convoluted t= o use, so I wrote wrappers for them to intercept the output to screen and s= end to formatted files for including within PIC .assembler files

=

=C2=A0

Andy =C2=A0G4JNT

<= span style=3D"font-size:12.0pt;font-family:"Times New Roman",seri= f">=C2=A0

=C2= =A0

On 1 February 2016 at 20:22, = <markusvester@= aol.com> wrote:

While we=E2=80=99re at it=E2=80=A6=C2=A0 I recently missed the JT9 act= ivity night, mostly due to the lack of a linear MF transmitter. For WSPR, I= =E2=80=99ve used a commandline tool (wsprcode.exe, or wspr.exe with -tx opt= ion) to encode a message to a file. This is then read by a little homemade = program (ddswspr.exe), which feeds an AD9850 DDS module through the serial = port.

=C2=A0

Does anyo= ne know whether a similar encoding option exists for JT9?

=C2=A0

Best 73,

Markus (DF6NM)

=C2=A0

<= p class=3D"MsoNormal">
Von: John Andrews
Gesendet: Montag, 1. Februar 2= 016 19:17
An: rsgb_lf_group@blacksheep.org
Betreff: Re: LF: = WOLF Coding

=E2=80=A6

=C2=A0

"If you have a BPSK-capable beac= on which uses an EEPROM to store its

message, WO= LF can generate a binary file suitable for programming the

device.

=E2=80=A6

=C2=A0

=C2=A0

=C2=A0

=C2=A0

=C2=A0


--089e013a1de071897e052abcd0a5--