Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Jonathan Naylor <jonathan.naylor@ggaweb.ch>
To: Jason Flynn G7OCD <jason.flynn@btinternet.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: JT44 on Linux
Date: Fri, 16 Aug 2002 09:13:58 +0200	[thread overview]
Message-ID: <0208160913580C.00798@g4klx> (raw)
In-Reply-To: <3D5C9B60.4000405@btinternet.com>

Hi Jason

>  We've been doing similar tests here, trying all the 'new' data
>  and weak signal modes. They're designed for EME or MS etc, and
>  don't cope very well with scintilations introduded by long
>  atmospheric distortion. They work, but if you do a waterfall,
>  you can see the signal spread is at least one tone wide so a
>  system for tropo would probably work better with less tones.

I remember reading that JT44 was designed for 2m (and lower) and that 
any others bands it worked on were a bonus. I know that it has been 
used on 23cms EME by a very marginal station, but I doubt it would work 
on 3cms EME where the spreading is rather large.

I think that going to 1 minute periods would also be a good step and as 
you mention going for less tones with wider spacing. To do a proper 
implementation, it would be good to have some data from the 3cms EME 
ops on what spreading is like, quantitative rather than qualitative.

>  So we're thinking about a new system specifically for tropo
>  contacts, your ideas would be appreciated...

My first priority is to get my JT44 program working, and then maybe 
FSK441 for MS work. I do think that my work could be the basis of 
better things as it uses a C++ framework that is rather flexible. I 
also make use of external libraries such as FFTW and libaudiofile to 
enable me to get round the tedious bits. BTW I am active on 6cms and 
3cms tropo work with quite an effective system.

My JT44 TX program made its first noises last night ! The timings are 
right (PTT, sound start and end, etc), but I would like a wav file of 
real JT44 sending Z's and/or 0's for me to compare. I don't have real 
JT44 here (no Windows) so I am working a little in the dark.

Just shout if you want a snapshot of the code.

>  	Jason

Jonathan  HB9DRD/G4KLX

      reply	other threads:[~2002-08-16  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  8:55 JT44 on Linux Jonathan Naylor
2002-08-14 11:57 ` Bob Nielsen
2002-08-14 12:24 ` Tomi Manninen OH2BNS
2002-08-14 13:05   ` Jonathan Naylor
2002-08-16  6:27     ` Jason Flynn G7OCD
2002-08-16  7:13       ` Jonathan Naylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0208160913580C.00798@g4klx \
    --to=jonathan.naylor@ggaweb.ch \
    --cc=g4klx@qsl.net \
    --cc=jason.flynn@btinternet.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox