To: rsgb_lf_group@blacksheep.org
References: <qwj6bpbckuaxcv5f1473mq2w.1458423524045@email.android.com>
 <A6D9E8AA0A5B4DFEA935CB192D3E4F69@White>
From: Tobias DG3LV <DG3LV@gmx.net>
Message-ID: <56EF29D9.9060902@gmx.net>
Date: Sun, 20 Mar 2016 23:53:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <A6D9E8AA0A5B4DFEA935CB192D3E4F69@White>
Subject: Re: Re: LF: JT9 Activity right now
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Hi Markus !

reading this, thank you for a truly handmade JT9-QSO !

I think this is what they call a "long delayed echo" on shortwave : your 
CQ at 22:03h and 22:05h, my anweres at 22:04h and 22:06h, then "some 
seconds later" your absolute perfect sequence of answers at 22:18h to 
22:24h. I suppose our radiowaves had been travelling to the sun and 
beeing bounced back by the outer skirts of the sun-halo, isn't it ?

But it had worked out, and that is what counts. So thank you for a 
somewhat special QSO at this fine weekend party !

(BTW : DL3NDR had written a fine modification article for a simple 
softrock RxTx at 475kHz. It does work very well.)

73 de dg3lv Tobias

Am 20.03.2016 um 10:22 schrieb Markus Vester:
> Thank you Vinny, for the nice idea and the invitation to the party!
> For me, it sure was a lot of fun, and resulted in a number of JT9 QSO's
> with OR7T, DG0RG, SV8CS, SV3DVO, DL6II, DD2UJ, IW4DXW, LA8AV, F6CNI, and
> DK7FC. Most signals were promptly decodable (except for my report from
> DL6II which was lost due to temporary drift). A copy of my receive log
> is at http://df6nm.bplaced.net/MF/jt9_party_160319.txt .
> But operating workflow was not easy for me. I don't have an MF SSB
> transmitter available here, just an AD8950 DDS-board with a three-wire
> serial interface. So I decided to modify my homemade WSPR software, such
> that it reads a message from the command line, converts it to tone
> numbers by calling Joe's JT9CODE.EXE, and plays it at the beginning of
> the next minute. Lacking the "late-start feature", the text had to be
> typed and ready on time, and it was practically impossible to
> immediately reply to a decoded message. This was further exacerbated by
> the lack of automatic message generation ("three click QSO"),
> and some uncertainties of shorthand versus free-text length. I'm sorry
> if I have been taxing the patience of my QSO partners!
> Regarding the receive software, if I had two free wishes this is what I
> would suggest:
> - Show decodes as spectrogram labels:
> Coming from visual QRSS, I like to "see" who I work. With many stations
> in the spectrogram, it can be challenging to keep an oversight on who is
> who, and on which frequency. It would be nice to see the decoded
> messages as labels near or on the traces in a wide horizontal
> spectrogram. replying by clicking on colour-highlighted labels would
> seem more intuitive than clicking in the separate text decode window.
> - Show partial decodes:
> When the signal is not too weak, the software could already attempt to
> decode a message before it has been completely received. Decoding zero
> padded audio (e.g. two extra times after 30 and 40 seconds) would give
> the operator significantly more time to think up an
> appropriate (non-automatic) response.
> Best 73,
> Markus (DF6NM)
> *From:* Vincent Stallbaum <mailto:info@vsas.de>
> *Sent:* Saturday, March 19, 2016 10:38 PM
> *To:* rsgb_lf_group@blacksheep.org <mailto:rsgb_lf_group@blacksheep.org>
> *Subject:* LF: JT9 Activity right now
>
> Ufb activity right now with a few new stations in JT9 mode. Feel free to
> join the QSO party!
>
> 73
> Vincent, DL6II