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.2 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_50_60,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 u11KfnIM001717 for ; Mon, 1 Feb 2016 21:41:49 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1aQLFJ-0002XC-3V for rs_out_1@blacksheep.org; Mon, 01 Feb 2016 20:38:49 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1aQLFI-0002X3-PX for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 20:38:48 +0000 Received: from mail-wm0-f47.google.com ([74.125.82.47]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from ) id 1aQLEO-0005ub-GR for rsgb_lf_group@blacksheep.org; Mon, 01 Feb 2016 20:38:47 +0000 Received: by mail-wm0-f47.google.com with SMTP id l66so89423070wml.0 for ; Mon, 01 Feb 2016 12:37:39 -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=xy/h7TCPZ9nx94mUZrGukY8OMDLuNWUSeA2X/CkejA8=; b=HVWFDST23fLZtjo0gIMZlcJ5p16qAfkVez93hdQiukBAVyaRnPTr4i+nON/t5p5yuU EdA8DnMvWpSGlxX2PDVt/TP/VQtmBfNu0+vZE1P7gAZl6mxSCN6oci2pAcRBMUOAvvCH ztjT7/+n+/78JFPDPXrZy9bXKlr/tjQYU8lr0GFUZo9myw+RLZDHp+3IHHQHfqQTDyZs TUcB3ejbCSU/m+UmFxhu0HUF0JogTawq8gbH+yclxeWaktPJ5oFZGWcMD/wMeH1z5go2 dVIfITsIihUwJCUZsYv+W6hg3Y4Hy9fcuXd0MBT25lIGNsB9uJ8KP5OZlcdjUr6GYnH/ X8Vg== 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=xy/h7TCPZ9nx94mUZrGukY8OMDLuNWUSeA2X/CkejA8=; b=AJhHo8Yw4tuVVImbx9+SxPRe378kLz2+7Up8dsLSQp1EZAlicXH+CA+HHE1sH9FH6w G2aFjJVbsfq7+W9T4+gHCuB3PsSwg/1ylgk/Qv6jZiHVEjeih7kH3k6ISJBSfJ0Hc/yK 2KrJRpKqF4woIKDVCYKi0CeLLz6eCZhJJbRP4IJZiynUv/J4PQpzHWocwtpLTaq5l5Ox o0cjnAS719GHKao0580sOssBNyG5NBFgpmwzWZRBtIqToqafkhaTVhiCQV5C43CDFzVI C+lCbE1zlOIZEsQBbGUqqEFZcG5263MTKYJeUcJe2MNJlsdLTUL2eARRPnwD99J27Mgr 6zsQ== X-Gm-Message-State: AG10YOQ2R8tsWGhQBasYbVA0e41vTU6ByqfwtEkMVFuCh6a9//0jUpB2we4v7ruZ+WyttAEJ/ovUipGdRfVa1w== MIME-Version: 1.0 X-Received: by 10.194.142.135 with SMTP id rw7mr20284281wjb.42.1454359013215; Mon, 01 Feb 2016 12:36:53 -0800 (PST) Received: by 10.28.187.67 with HTTP; Mon, 1 Feb 2016 12:36:53 -0800 (PST) In-Reply-To: References: <56AFA07E.4040001@charter.net> Date: Mon, 1 Feb 2016 20:36:53 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org X-Scan-Signature: ad8e5dd63f7497fd9d71d15044db2e2b Subject: Re: LF: JT9 Coding? Content-Type: multipart/alternative; boundary=089e013a1de05be104052abb58da 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: 6612 --089e013a1de05be104052abb58da Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 > > > --089e013a1de05be104052abb58da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There is a separate utility called JT9CODE, downloadable f= rom the WSJT website
There is a similar one for JT65

They are a bit convoluted to use, so I wrote wrappers for them to in= tercept the output to screen and send to formatted files for including with= in PIC .assembler files

Andy =C2=A0G4JNT
<= br>

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 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 program (ddswspr.exe), which feeds a= n AD9850 DDS module through the serial port.

= =C2=A0

Does anyone know whether a simi= lar encoding option exists for JT9?

=C2=A0=

Best 73,

Markus= (DF6NM)

=C2=A0


Von: <= /b>John Andrews<= br>Gesendet: Montag, 1. Februar 2016 19:17
An: rsgb_lf_group@blacks= heep.org
Betreff: Re: LF: WOLF Coding

=E2=80=A6

=C2=A0

"If you have a BPSK-capable beacon which uses an EEPR= OM to store its

message, WOLF can generate a bin= ary file suitable for programming the

device.

=E2=80=A6

=C2=A0<= u>


--089e013a1de05be104052abb58da--