Installation along the X64 Version works ufb. Just unzipping VLC 32bit in the "default" folder doesn't. Probably we should start a topic if there isn't one for this.
WB beacon video decoding with VLC still ok. But more OM´s have problem to decode with MiniTioune this time. Maybe a problem in the video protocol for the Microsoft decoder which MiniTioune uses
Scan&Tioune for Beta Tester postby F6DZP today, Mon 6 Apr 2020 18:39 here the link for download "http://www.vivadatv.org/viewtopic.php?f=60&t=767" 
Attention: are you unintentionally send CW on .530 kHz using „Morse News 4.3“? Please check your transmitter!
Revised Wideband Transponder bandplan just published: Revised QO-100 DATV Bandplan - Please Read
Unfortunately it is also confirmed in the official manual:
Remarks:
• Scan & Tioune only works with MiniTiounerPro or MiniTiouner V2 have a NIM Serit FTS4334 and
FTS4335. ( The MiniTiouner Express does not conform are cases will be seen perhaps later.)
Regarding Scan&Tioune look into the manual. Now there is an english version available:
done, link to drive via email
new version Minitioune V0.9.9.1
http://vivadatv.org/viewtopic.…f0587d259e6e89de899#p3211
and Scan&Tioune for Beta Tester which unfortunately does not work with my hardware
http://vivadatv.org/viewtopic.…44977ef0587d259e6e89de899
tnx to
Jean-Pierre F6DZP
Display MoreThis is not what AMSAT recommends and how the Link budget for QO-100/Es'hail-2 was designed
A 60cm should be the minimum for receive...
A 40cm dish might be sufficient for portable operation, but only if all components of your receive system are fully optimized and you are in the center/middle regions of the QO-100 footprint..
Anyhow, we should always improve hearing performance and not become a crocodile...
Of course I know the Amsat recommendations. The purpose of my comment was to encourage new users not to be frightened by thinking large antennas are needed. Certainly not for the transponder NB.
My way to verify different equipments is to take a look at the ground noise
...
On my 1,8m PF with OCAGON OTLSO Twin LNB (26 MHz GPSDO) i can see a transponder noise 9 dB over ground noise.
What do you think about?
excellent, but let's say that for the NB transponder antennas greater than 100 cm are excessive. We say it for any new users who maybe worry, they think a big effort is required. For the NB transponder, a 40 cm antenna is sufficient for good activity. I repeat it only for new users.
Hello Nicholas,
I believe that with a correctly pointed 80cm antenna and reasonable receive system you should be able to see the transponder noise floor ...
73 Chris G4SDG
I also agree because the other measures are influenced by many factors. This is what I see with a 100 cm dish. They are more or less 6 dB.
Antenna 100 cm unmodified Octagon OTSLO Twin LNB
Forgive me but maybe there is a basic misunderstanding.
I don't know the details of your experiment. I don't know how you organized it. I am talking about JT digital systems in general and how they try to decode a message. I tried and tried again to delete that blessed archive file and the various programs, not only that of K1Jt but also the derivatives, become more "deaf" without that file. It is an experiment that anyone can replicate. And if after deleting that file, disconnect the Internet as well, you will have other surprises.
be patient and look for this file, however it is called. ALLCALL.TXT OR ALL.TXT, CALL3.TXT
try to delete the file "ALL.TXT" and you will see the differences.
Display More....
But i have no idea about the different decoding levels and the performance of WSJTX also on different days ....normaly the same signals on the transponder must reach the same SNR level if you have enough ground noise of the transponder.
Maybe there are some other influences in the signal path of the propagation and maybe also in the satellite hardware?
BTW: an very interesting test ....
73 for now
Michael dg0opk
The problem is known and lies in the operation of the program. In the directory C:\users\user\AppData\Local\WSJT-X\ there is an file: "ALL.TXT".
This file contains all the calls and messages previously received.
The first time the program decodes a signal it must necessarily receive the whole message correctly. Let's say the signal is at -20 dB. Subsequently, the program is able to receive a lower signal from the same station since the part of the message that possibly did not receive well reconstructs it thanks to the local archive contained, in fact, in the file: "ALL.TXT"
Example:
200324_115645 10489.540 Rx FT8 -20 0.9 1401 CQ PY4ZBZ GH70
Subsequently PY4ZBZ reduces its signal by 3 dB but the program correctly receives only the blue part of the message.
200324_115645 10489.540 Rx FT8 -24 0.9 1401 CQ PY4ZBZ GH70
Here the program goes fishing in the archive and tries to reconstruct the missing part of the message. The same was used 30 years ago with QSOs via EME. You knew in advance who was on the other side and it was enough to receive only a few characters to consider the QSO valid.
Delete the file "ALL.TXT" and you will see the -24, -23 etc disappear
Here in JN61FQ with 100 cm dish, octagon twin LNB, MER = 11.1 dB, +2dB compared to before.
not bad...
PY1SAN -20 in JN61FQ
Of course. For this reason we discuss to understand if the problem is ours or is of a different nature.
In recent days I confirm a variation of 1 dB compared to the past but at this moment everything has returned to normal.
100 cm off-set dish
There are still small variations but little stuff.
update:
... the information provided was accurate at the time it was written.
Now things have changed and Serge sends to Italy through his website.
Received the RX QO-100 RX Converter today.
I was talking about the coaxial cable between FT818 and transverter. Double check the cable or adapters if there are any. Difficult to damage the internal attenuator with only (maximum) six watts. So it is very likely that the problem is the coaxial cable or any adapters.
hi Rudi,
a trivial question:
there is a cable between your FT818 and the transverter.
Is the cable ok?
Or, you've probably sent too much power to the input (432 MHz) of the transverter damaging the internal attenuator.
One of the two hypotheses is the right one.
Somehow my entry from September disapeared, so I post it again :
...
73s
Armin DF1QE
do you refer to this thread?
