Date: Sat, 10 Nov 2018 15:37:14 +0000 (UTC)
From: Markus Vester <markusvester@aol.com>
To: rsgb_lf_group@blacksheep.org
Message-ID: <1320399704.180352.1541864234370@mail.yahoo.com>
MIME-Version: 1.0
References: <1320399704.180352.1541864234370.ref@mail.yahoo.com>
Subject: Re: LF: SlowJT9: 1st QSO and 2nd bug found
Content-Type: multipart/alternative; 
	boundary="----=_Part_180351_1132360762.1541864234369"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

------=_Part_180351_1132360762.1541864234369
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Rik,=20

thanks for the great work on this nice piece of software!

Comments / questions from this end:

1. My LF equipment has a fixed 135.5 kHz LO, so audio=C2=A0will need to be =
around 1800 Hz or so. Such TX and RX frequencies can apparently be be set (=
albeit red), but the clickable spectrogram=C2=A0range ends=C2=A0hard at 140=
0 Hz. Would it be possible to=C2=A0allow a user defined spectrogram shift? =
The alternative is external frequency conversion using SpecLab and=C2=A0vir=
tual cables, but I'd rather avoid that due to extra latencies.

2. In the past I often found myself=C2=A0just missing the start of the next=
 transmit slot (particularly when entering free text). Is it possible to st=
art a transmission a few seconds=C2=A0late into the=C2=A0timeslot, or even =
change the message on the fly?=C2=A0I think=C2=A0the SNR penalty of loosing=
 a few symbols at the beginning may not be too severe.

3. The software seems to be fairly stable. Clicking=C2=A0the "save any work=
 done on this computer" disclamer may not be necessary on every=C2=A0startu=
p.

Best 73,
Markus (DF6NM)


-----Urspr=C3=BCngliche Mitteilung-----
Von: Rik Strobbe <rik.strobbe@kuleuven.be>
An: rsgb_lf_group@blacksheep.org <rsgb_lf_group@blacksheep.org>; rsgb_lf_gr=
oup@yahoogroups.co.uk <rsgb_lf_group@yahoogroups.co.uk>
Verschickt: Fr, 9. Nov. 2018 23:27
Betreff:=C2=A0 LF: SlowJT9: 1st QSO and 2nd bug found

Dear all,

I just completed a JT9-2 QSO with Marco, DD7PC:

2141 -11=C2=A0 0.1 1104 2=C2=A0 OR7T DD7PC JN49=C2=A0 =C2=A0 =C2=A0 =C2=A0
2145 -10=C2=A0 0.1 1106 2=C2=A0 OR7T DD7PC JN49=C2=A0 =C2=A0 =C2=A0 =C2=A0
2153 -16=C2=A0 0.0 1105 2=C2=A0 OR7T DD7PC R-13=C2=A0 =C2=A0 =C2=A0 =C2=A0
2157 -12=C2=A0 0.0 1105 2=C2=A0 OR7T DD7PC 73=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0
2201 -16=C2=A0 0.1 1106 2=C2=A0 UFB RIK

During this QSO I discovered a 2nd bug:=C2=A0

As can be seen above the time (UTC) is given at odd minutes (eg. Marco's 21=
:40 - 21-42 transmission is reported 2141). This because the time is taken =
at the moment of decode.=C2=A0

For JT9(-1) this is not an issue, because decoding is in the same minute as=
 the start of transmission, but for JT9-2 and JT9-5 it is because it result=
s in a wrong calculation of the cycle (1st or 2nd). As the wrong cycle is g=
iven SlowJT9 will transmit in at the same cycle as the station you received=
, very inconvenient!

I will fix this big after the weekend (sorry, to many other obligations on =
Saturday and Sunday).

For the time being the workaround is rather easy: if=C2=A0you get a decode =
you want to reply to (by double clicking on the call) just=C2=A0change the =
cycle manually (click once on=C2=A0the "TX 1st cycle" checkbox). The good t=
hing is you have plenty of time to do so as there are 20 seconds between th=
e end of a transmission and the start of the next cycle.=C2=A0

To end with a positive note: during Marco's 2152-2154 transmission there wa=
s very deep QSB and=C2=A0his signal dissapeared from the waterfall display =
for almost 1 minute. But despite that still a good decode, just some dB wea=
ker.

73, Rik=C2=A0 ON7YD - OR7T


------=_Part_180351_1132360762.1541864234369
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-size:10pt;font-family:arial,helvetica,sans-serif;color:b=
lack;"><div id=3D"yiv6546166731"><div style=3D"color: black; font-family: a=
rial, helvetica, sans-serif; font-size: 10pt;"><div id=3D"yiv6546166731"><d=
iv style=3D"color: black; font-family: arial, helvetica, sans-serif; font-s=
ize: 10pt;"><div style=3D"color: black; font-family: arial, helvetica, sans=
-serif; font-size: 10pt;">Hi Rik, <br><br>thanks for the great work on this=
 nice piece of software!<br><br>Comments / questions from this end:<br><br>=
1. My LF equipment has a fixed 135.5 kHz LO, so audio&nbsp;will need to be =
around 1800 Hz or so. Such TX and RX frequencies can apparently be be set (=
albeit red), but the clickable spectrogram&nbsp;range ends&nbsp;hard at 140=
0 Hz. Would it be possible to&nbsp;allow a user defined spectrogram shift? =
The alternative is external frequency conversion using SpecLab and&nbsp;vir=
tual cables, but I'd rather avoid that due to extra latencies.<br><br>2. In=
 the past I often found myself&nbsp;just missing the start of the next tran=
smit slot (particularly when entering free text). Is it possible to start a=
 transmission a few seconds&nbsp;late into the&nbsp;timeslot, or even chang=
e the message on the fly?&nbsp;I think&nbsp;the SNR penalty of loosing a fe=
w symbols at the beginning may not be too severe.<br><br>3. The software se=
ems to be fairly stable. Clicking&nbsp;the "save any work done on this comp=
uter" disclamer may not be necessary on every&nbsp;startup.<br><br>Best 73,=
<br>Markus (DF6NM)<br><br><br><br>-----Urspr=C3=BCngliche Mitteilung-----<b=
r>Von: Rik Strobbe &lt;rik.strobbe@kuleuven.be&gt;<br>An: rsgb_lf_group@bla=
cksheep.org &lt;rsgb_lf_group@blacksheep.org&gt;; rsgb_lf_group@yahoogroups=
.co.uk &lt;rsgb_lf_group@yahoogroups.co.uk&gt;<br>Verschickt: Fr, 9. Nov. 2=
018 23:27<br>Betreff:&nbsp; LF: SlowJT9: 1st QSO and 2nd bug found<br></div=
><div id=3D"yiv6546166731"><div dir=3D"ltr">
<p>Dear all,<br><br clear=3D"none">
I just completed a JT9-2 QSO with Marco, DD7PC:</p>
<p>2141 -11&nbsp; 0.1 1104 2&nbsp; OR7T DD7PC JN49&nbsp; &nbsp; &nbsp; &nbs=
p;<br clear=3D"none">
2145 -10&nbsp; 0.1 1106 2&nbsp; OR7T DD7PC JN49&nbsp; &nbsp; &nbsp; &nbsp;<=
br clear=3D"none">
2153 -16&nbsp; 0.0 1105 2&nbsp; OR7T DD7PC R-13&nbsp; &nbsp; &nbsp; &nbsp;<=
br clear=3D"none">
2157 -12&nbsp; 0.0 1105 2&nbsp; OR7T DD7PC 73&nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;<br clear=3D"none">
2201 -16&nbsp; 0.1 1106 2&nbsp; UFB RIK
<br><br>During this QSO I discovered a 2nd bug:&nbsp;
<br><br>As can be seen above the time (UTC) is given at odd minutes (eg. Ma=
rco's 21:40 - 21-42 transmission is reported 2141). This because the time i=
s taken at the moment of decode.&nbsp;<br><br clear=3D"none">
For JT9(-1) this is not an issue, because decoding is in the same minute as=
 the start of transmission, but for JT9-2 and JT9-5 it is because it result=
s in a wrong calculation of the cycle (1st or 2nd). As the wrong cycle is g=
iven SlowJT9 will transmit in
 at the same cycle as the station you received, very inconvenient!<br>
<br clear=3D"none">
I will fix this big after the weekend (sorry, to many other obligations on =
Saturday and Sunday).<br><br clear=3D"none">
For the time being the workaround is rather easy: if&nbsp;you get a decode =
you want to reply to (by double clicking on the call) just&nbsp;change the =
cycle manually (click once on&nbsp;the "TX 1st cycle" checkbox). The good t=
hing is you have plenty of time to do so as
 there are 20 seconds between the end of a transmission and the start of th=
e next cycle.&nbsp;<br>
<br clear=3D"none">
To end with a positive note: during Marco's 2152-2154 transmission there wa=
s very deep QSB and&nbsp;his signal dissapeared from the waterfall display =
for almost 1 minute. But despite that still a good decode, just some dB wea=
ker.<br clear=3D"none">
<br clear=3D"none">
73, Rik&nbsp; ON7YD - OR7T<br><br clear=3D"none">
<br clear=3D"none">
</p></div></div></div></div></div></div></div>
------=_Part_180351_1132360762.1541864234369--