[wsjt-devel] TX5T in DXpedition Mode

[John Zantek]

Just wanted to share some pleasing observations of the TX5T team’s first night 
of FT8 operation on 40M.  It’s all good.

 

The team’s published Plan was to be on 7056kHz, so I set my rig on 7056, and 
moved my antenna to the needed azimuth before going to bed.  I happened to wake 
up ~0800 UTC (old guys have a tendency to wake up in the middle of the night 
for various reasons, hi hi) but checking my screen, saw TX5T up at the TOP end 
of my waterfall, not the bottom.  On another screen (I have 3 in my shack), I 
saw that TX5T was just showing up on pskreporter.info about that time, but 
apparently on 7058kHz.  No problem, so I quickly added 7058 to my frequency 
list in WSJT-X and clicked to QSY to the new selection.

 

The waterfall was wonderfully full!  TX5T had up to 5 channels running at the 
low end of the waterfall, there was the expected empty DMZ, and then about 
20-24 stations north of the 1k mark, overwhelmingly JA and HL.  There was no 
confusion, misadventures, or DQRM.  It was very crowded, but everyone seemed to 
find a tight but clean spot to call.  A few US stations were valiantly trying 
but, initially, not getting answered, myself included.  TX5T was knocking out 
Asian stations at a rate I never saw with the Baker team last month, and they 
had only just arrived on the air.

 

Suddenly, TX5T started exclusively answering the US stations and within 4 
minutes, had cleared the whole North American queue.  Bravo, I thought, the Fox 
is paying attention to his backlog and responded directionally.  Now clear, the 
op went back to the endless hoard of JA callers.  Despite very noisy conditions 
(A-index was 16 at the time), I was seeing almost NO repeats….just dozens and 
dozens of stations being worked and logged.  

 

I’d like to think that there are many good things happening as use of 
DXpedition mode becomes more common.  First, having the docs in languages other 
than English is huge.  It was apparent the JA crowd had gotten the message and 
read the instructions this time around.  Second, the TX5T team had both 
practiced and better understood the role and management features of the Fox AND 
didn’t suffer from PC hangups as in the earlier workups of some other Foxes.  
TX5T didn’t skip a beat for two straight hours last night, and probably kept 
sailing after I went back to bed.  Finally, of course, credit to the 
development team for 1.9.2.

 

I’d really like to see those first night’s logs after they get posted.  It 
should tell a wonderful story.

 

Oh, and one other thing I thankfully DIDN’T see: monster signals at +05 and 
beyond, or harmonic signals bracketing others.  Yep, there weren’t any 
amplifiers in evidence.

 

73 John W7CD

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subprocess Error: Subprocess failed with exit code 2

[Dan Malcolm]

I hate bringing this up again, but I was unable to find a resolution on my own, 
and a search of the wsjt-devel messages didn’t reveal anything either except 
that others have this problem.  I do find the file ‘houndcallers.txt’ does 
exist while wsjt-x is running.  When the error occurs the file has been 
deleted.  A search of Win10’s Event Viewer logs had no note of that file.  It 
appears something is deleting the file.

It’s my understanding the file exists to support FT8 DXpeditions.  I haven’t 
recently participated in any, nor have I turned on the FT8 settings to 
accommodate that.

So why do I need ‘houndcallers.txt’, what is deleting it, and who is ‘bill’ 
that keeps showing up in the error text?

I am running WSJT-X v1.9.1 and not any of the beta versions.  Until about 3 
weeks ago I had only read about the error but had experienced it.

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, June 14, 2018 5:52 PM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Subprocess Error: Subprocess failed with exit code 2

Maybe your antivirus is getting in the way?
Can you put an exclusion on the directory?

de Mike W9MDBH




On Thursday, June 14, 2018, 4:54:13 PM CDT, Steve Sacco NN4X 
mailto:n...@embarqmail.com>> wrote:



Same as always.  Please let me know how I can assist.





Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a 
C:\Users\Steve\AppData\Local\WSJT-X -t C:\Users\Steve\AppData\Local\Temp\WSJT-X

At line 81 of file C:\Users\bill\src\wsjt-svn\lib\decoder.f90 (unit = 19)

Fortran runtime error: Cannot open file 
'C:\Users\Steve\AppData\Local\Temp\WSJT-X/houndcallers.txt': No such file or 
directory
[cid:image001.png@01D43572.313E7E30]





--

Steve Sacco

NN4X

Narcoossee, FL

EL98jh
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel