Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

RE: LF: JT9 Activity right now

To: "[email protected]" <[email protected]>
Subject: RE: LF: JT9 Activity right now
From: Rik Strobbe <[email protected]>
Date: Sun, 20 Mar 2016 10:27:27 +0000
Accept-language: nl-BE, en-GB, en-US
In-reply-to: <[email protected]>
References: <[email protected]>,<[email protected]>
Reply-to: [email protected]
Sender: [email protected]
Thread-index: AQHRgigo3lAXLPCLW0WPSjJ8bVatMp9iEOKAgAAOa7E=
Thread-topic: LF: JT9 Activity right now

Hello Marcus, Vinny, all,

 

it was indeed a remarkable evening.

When I came in the shack at about 19 UTC the activity was already going on and despite the fact that I had some other things to do (rushing in and out the shack) I managed to work 10 stations:

OM1II, G4GIR, DL6II (of course), DF6NM, DG3LV, LA8AV, SV8CS, DG0RG, DK6XY and SP9DNO.

Also seen with good signal: SV3DVO and IW4DXW.

 

I am looking forward to part 2, this evening. Maybe last night activity will trigger some ùore participants (missing SM, OH, 9H, EA last night?)

 

73, Rik  ON7YD - OR7T

 


Van: [email protected] [[email protected]] namens Markus Vester [[email protected]]
Verzonden: zondag 20 maart 2016 10:22
Aan: [email protected]
Onderwerp: Re: LF: JT9 Activity right now

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)
 
Sent: Saturday, March 19, 2016 10:38 PM
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
<Prev in Thread] Current Thread [Next in Thread>