Recently somebody talked me into high altitude balloon (HAB) tracking.
It appeared more than once I was the only station in the northern
hemisphere to decode 30m WSPR traces originating from balloons floating
in the southern hemisphere.
In order to assist this HAB community I needed to install a patched
version of WSJT-X.
This version runs in JT9 mode and allows HAB telemetry packets
to be uploaded to tracker.habhub.org. Two checkboxes have been
added in the main window, 'Telemetry' and 'Location'.
I also checked the 'Enable PSK Reporter Spotting' box in 'Preferences'.
PSKreporter.info identifies this version as 'WSJT-X v1.6.0-devel r5825-dirty'.
(yes, I know, the latter subversion option may be already nomen est omen ;-)
For WSPR usage I submissively use the 'full release' v1.6.0.
On my (Win7_64) laptop now two instances (and two versions) of WSJT-X are
running, each instance started with different --rig-name(s).
The contraption ran OK for a while but as of yesterday I discovered
'loosing' WSPR spots because my uniq score dropped drastically while
performance of the receiver hardware was identical (as verified with
my QRSS grabber).
B.t.w., timing is/seems correct.
Because the very sensitive receiving contraption is located at a
quiet remote site it took a while before I could visit the receiver,
which I did today.
It appeared the WSPR instance was running, i.e. not crashed.
In the waterfall I saw -properly timed- clear traces but no decodes.
Restarting this instance delivered loads of decodes afterwards.
However, after some time I saw 'gaps' in the sequence of time slots.
E.g. in the 14.20z slot I had 10 displayed WSPR decodes, then
a few slots no decodes (although the waterfall displayed beautiful
traces), and 'suddenly' decodes appeared for some time and then
stopped.
I can't recognise/determine a pattern yet.
Suspecting the resources of my laptop I started a third
WSJT-X (1.6.0 release) instance in JT65 mode. Here I lost no
JT65 (and JT9) traces while the WSPR instance showed the same
phenomenon: 'decode gaps'.
It's not my intention to start a thread concerning this just
described phenomenon as I'm already suspect running a 'dirty'
instance, so my 'defense is weak' ;-)
Staring at the screen, having three instances of WSJT-X 'running',
I thought to myself: "Why is it necessary to run instances
for each mode while only receiving and trying to serve the weak
signal community with a sensitive receiver to somewhat
level the ratio TX vs. RX (WSPR) MEPTs?"
Wouldn't it be nice to have a 'Full Monty' button decoding
-AND- properly disseminating all integrated modes (subsequently)
(WSPR2, JT9, JT65, JT4) present in the (audio) pass band?
Remco PA3FYM
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
