Content-Transfer-Encoding: 8bit
Message-ID: <3.0.1.16.20020117110911.30b7a52c@pb623250.kuleuven.be>
Date: Thu, 17 Jan 2002 11:09:11
To: rsgb_lf_group@blacksheep.org
From: "Rik Strobbe" <rik.strobbe@fys.kuleuven.ac.be>
Subject: Re: LF: Introducing Jason
In-reply-to: <3C44631A.942D751C@usa.net>
References: <5.1.0.14.0.20020115133352.00a65df8@gemini.herts.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Sender: <majordom@post.thorcom.com>

Hello Alberto,

I just downloaded the 'slow PC' version of Jason and will try it over the
next weekend.
Meanwhile I am still thinking about an easy (= fast & cheap) way to
transmit Jason. Simplest way is to use my existing HF tranceiver and put
the soundcard output to the mike. Since my tranceiver (and probably most
other) won't transmit at 136kHz I either have to :
- transvert a HF signal down to 136kHz
- devide the HF signal down to 136kHz (only for non-linear modes, including
Jason)
I prefer the second option for several reasons :
- dividing by 100 will increase signal stability by 100 (and reduce any PLL
jitter by 100)
- diving by 100 will allow me to tune in 0.1Hz steps (transvering would
allow only 10Hz steps)
But ... this would require a 'Jason signal' using 25.2Hz steps instead of
0.252Hz steps (producing an audio signal of 800Hz +/- 400Hz instead of
800Hz +/- 4Hz). 
I don't know how hard this it to implement ? 
I know that you are spending a lot of time on Argo, Jason etc.. so it this
takes to much time just ignore this request.

73, Rik  ON7YD

PS : 
Divide by 100 would require a 13.57 - 13.78 MHz signal, advantage = easy
frequency reading, disadvantage = out of a ham band.
Alternative would be to divide by 104, that would require a signal of
14.1128 - 14.3312 MHz (within the 20 meter band) but disadvantage =
difficult frequency reading.