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=-1.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE,NO_REAL_NAME 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 u11MD985001971 for ; Mon, 1 Feb 2016 23:13:10 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aQMfZ-0004Td-SG for rs_out_1@blacksheep.org; Mon, 01 Feb 2016 22:10:01 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aQMfZ-0004TO-Gi for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 22:10:01 +0000 Received: from omr-m005e.mx.aol.com ([204.29.186.5]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1aQMeZ-0006Qn-CA for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 22:10:00 +0000 Received: from mtaout-aaf02.mx.aol.com (unknown [172.26.127.98]) by omr-m005e.mx.aol.com (Outbound Mail Relay) with ESMTP id 71077380006E for ; Mon, 1 Feb 2016 17:08:41 -0500 (EST) Received: from [IPv6:::ffff:192.168.0.14] (ipbcc05f3c.dynamic.kabel-deutschland.de [188.192.95.60]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mtaout-aaf02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 95E2E38000085 for ; Mon, 1 Feb 2016 17:08:40 -0500 (EST) MIME-Version: 1.0 To: "rsgb_lf_group@blacksheep.org" From: Date: Mon, 1 Feb 2016 23:08:40 +0100 Importance: normal X-Priority: 3 In-Reply-To: References: <56AFA07E.4040001@charter.net> x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1454364521; bh=LaEGxrSlJp7LZJ7DtCni0j4/V3QD0eAXXNtosh/EAlA=; h=From:To:Subject:Date:MIME-Version:Content-Type; b=sYGxPHqeWn74dGE8FFCq0iFty2fDq+mtS8e0F53nNB2Omo2mnkVsiM4E728L6m1zq qIkY09W8bs1m9CYrKly8cw/iu/HjhYy4mLUpPXNAjp0xARC8LhUm/7XAMDjAQEfwS1 JfdnBBH031qAkYj3G9f4E+DNXxFk/JQhjmoYtQOY= x-aol-sid: 3039ac1a7f6256afd7682932 X-AOL-IP: 188.192.95.60 X-Scan-Signature: 9d611a03c0c7539fa2f53ebf8cdeb3a5 Message-Id: Subject: AW: LF: JT9 Coding? Content-Type: multipart/alternative; boundary="_B86A26B6-998A-4487-BAD1-C23A0B3CDDBF_" 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: 6625 --_B86A26B6-998A-4487-BAD1-C23A0B3CDDBF_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" =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 th= ree 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. 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 around = 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 =C2=A0 Interestingly, =E2=80=9Ei have a cat=E2=80=9C throws an error but =E2=80=9E= i_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 inacc= urate 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 Coding? =C2=A0 There is a separate utility called JT9CODE, downloadable from the WSJT webs= ite There is a similar one for JT65 =C2=A0 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 =C2=A0 Andy =C2=A0G4JNT =C2=A0 =C2=A0 On 1 February 2016 at 20:22, wrote: While we=E2=80=99re at it=E2=80=A6=C2=A0 I recently missed the JT9 activity= 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 option= ) to encode a message to a file. This is then read by a little homemade pro= gram (ddswspr.exe), which feeds an AD9850 DDS module through the serial por= t.=20 =C2=A0 Does anyone know whether a similar encoding option exists for JT9? =C2=A0 Best 73, Markus (DF6NM)=20 =C2=A0 Von: John Andrews Gesendet: Montag, 1. Februar 2016 19:17 An: rsgb_lf_group@blacksheep.org Betreff: Re: LF: WOLF Coding =E2=80=A6 =C2=A0 "If you have a BPSK-capable beacon which uses an EEPROM to store its=20 message, WOLF can generate a binary file suitable for programming the=20 device.=20 =E2=80=A6 =C2=A0 =C2=A0 =C2=A0 --_B86A26B6-998A-4487-BAD1-C23A0B3CDDBF_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

=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.

 

73, Markus

 


Von: A= ndy Talbot
Gesendet: Montag, 1. Februar 2016 22:58
An: = rsgb_lf_group@blackshee= p.org
Betreff: Re: LF: JT9 Coding?

 

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

 

'jnt

 

 

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

Thanks a lot Andy, that=E2=80=99s exactly what I was looki= ng 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.

 <= /p>

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

 

Best 73,

Markus

 

 


Von: Andy Talbot
Ge= sendet: Montag, 1. Februar 2016 21:39
An: rsgb_lf_group@blacksheep.org=
Betreff: Re: LF: JT9 Coding?

<= span style=3D'font-size:12.0pt;font-family:"Times New Roman",serif'> <= /span>

There is a separate utility called JT9CODE, d= ownloadable from the WSJT website

There is a = similar one for JT65

 

=

They are a bit convoluted to use, so I wrote wrap= pers for them to intercept the output to screen and send to formatted files= for including within PIC .assembler files

 

Andy  G4JNT

<= div>

 

&= nbsp;

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

While w= e=E2=80=99re at it=E2=80=A6  I recently missed the JT9 activity 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 option) to enco= de a message to a file. This is then read by a little homemade program (dds= wspr.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)

<= p class=3DMsoNormal> 


Von: John AndrewsGesendet: Montag, 1. Februar 2016 19:17
An: rsgb_lf_group@blacksh= eep.org
Betreff: Re: LF: WOLF Coding

=E2=80=A6

 

&quo= t;If you have a BPSK-capable beacon which uses an EEPROM to store its

<= p class=3DMsoNormal>message, WOLF can generate a binary file suitable for p= rogramming the

device.

= =E2=80=A6

 

=

 

 

=

 

 

= --_B86A26B6-998A-4487-BAD1-C23A0B3CDDBF_--