Re: [wsjt-devel] Subprocess Error

[John C. Westmoreland, P.E.]

Hello Claude,

I was wondering the same thing when this happened.

And, I was observing other aberrant behavior before this happened - after a
contact was made, 73's exchanged, it would get stuck and keep sending the
73's.  I checked my set-up then, and it all looked OK.

I'm running the latest build (1.9.1), Windows 10 in test mode, v. 1804.
I'll check the set-up again, but the program was doing some things like the
73's before the error occurred.  This is the first time I've seen that on
this machine since putting in the new motherboard/OS.

73's,
John
AJ6BC


On Wed, Aug 22, 2018 at 8:33 AM Claude Frantz 
wrote:

> On 08/22/2018 11:47 AM, John C. Westmoreland, P.E. wrote:
>
> Hi John,
>
> > OK - when I searched the list I searched for process error vs.
> > subprocess error...
> >
> > Maybe the Win 10 1804 update has something to do with this?
>
> Are you sure that you are not on FT8 DXpedition mode as fox ? Please
> verify your config.
>
> Best wishes,
> Claude (DJ0OT)
>
>
> --
> 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

[wsjt-devel] Subprocess Error

[John C. Westmoreland, P.E.]

Hello All,

WSJT-X running - just receiving - was on another computer and heard the
windows ding - looked on the screen and found this:  (I can attach a screen
shot but only for those that need/want to see it):

Subprocess Error

Subprocess failed with exit code 2

In the text box:
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a
C:\Users\john\AppData\Local\WSJT-X -t
C:\Users\john\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\john\AppData\Local\Temp\WSJT-X/houndcallers.txt': No such file or
directory

I had just been trying to see if RI1ANL could read me, stepped away for
about 5 min - and this happened.

73's,
John
AJ6BC
--
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

[John C. Westmoreland, P.E.]

OK - when I searched the list I searched for process error vs. subprocess
error...

Maybe the Win 10 1804 update has something to do with this?

73's,
John
AJ6BC


On Wed, Aug 22, 2018 at 2:45 AM John C. Westmoreland, P.E. <
j...@westmorelandengineering.com> wrote:

> Hello All,
>
> WSJT-X running - just receiving - was on another computer and heard the
> windows ding - looked on the screen and found this:  (I can attach a screen
> shot but only for those that need/want to see it):
>
> Subprocess Error
>
> Subprocess failed with exit code 2
>
> In the text box:
> Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a
> C:\Users\john\AppData\Local\WSJT-X -t
> C:\Users\john\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\john\AppData\Local\Temp\WSJT-X/houndcallers.txt': No such file or
> directory
>
> I had just been trying to see if RI1ANL could read me, stepped away for
> about 5 min - and this happened.
>
> 73's,
> John
> AJ6BC
>
>
--
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] no decode

[John C. Westmoreland, P.E.]

To All,

My rig did the same thing - checked timing with WWV - was exact, and still
no decode.

I'm using VAC's with my current rig - reset those - and wham!  Works.

So, the ONLY reason this may not work IS NOT timing.   Even if your timing
is off a bit you'll still see some decodes usually on 40m provided it's busy
and it usually is.

Check VAC's.  Everything looks ok - but I tore down and then remade my VACs
and everything worked again.  I agree it's a little strange.
(Note for those that could be wondering, I've retired my venerable Vista-64
motherboard.)

73's,
John
AJ6BC


On Tue, Aug 7, 2018 at 11:21 AM, John L. Broughton <2silverhon...@gmail.com>
wrote:

> Dimension 4 works just fine with Windows 10. I've been on Windows 10 for
> quite some time and have no problem with Dimension 4. I'm running version
> 5.31.331.0.
>
> John, WB9VGJ
>
> John L. Broughtonwww.wb9vgj.uswb9vgj@arrl.net2silverhon...@gmail.com
>
> On 8/7/2018 7:52 AM, harold deitz via wsjt-devel wrote:
>
> Chris,
>
> I have been using "Dimension 4" for time sync.  Recently upgraded my OS to
> Windows 10.  Found out that Dimension 4 won't work with Windows 10.  How do
> I get Meinberg?
>
> Hal W5GHZ
>
>
>
> Sent from Yahoo Mail. Get the app 
>
>
> On ‎Tuesday‎, ‎August‎ ‎7‎, ‎2018‎ ‎01‎:‎53‎:‎46‎ ‎PM‎ ‎GMT, Chris Getman
>   wrote:
>
>
> I had a very similar problem.
>
>
>
> The time looked OK, but when I did a manual Time Sync everything started
> working
>
>
>
> Michael had me switch time sync programs to Meinberg and I haven’t had an
> issue since.
>
>
>
> It’s worth a try and might fix your issue also.
>
>
>
> Chris  -  N3PLM
>
>
>
> *From:* Black Michael via wsjt-devel [mailto:wsjt-devel@lists.
> sourceforge.net ]
> *Sent:* Tuesday, August 7, 2018 9:38 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Cc:* Black Michael  
> *Subject:* Re: [wsjt-devel] no decode
>
>
>
> Hmmm hamspots.net doesn't show any transmissions from you for the last 16
> hours so you may not be transmitting as you think.
>
>
>
> You say your time is good but what does http://time.is tell you?
>
>
>
> de Mike W9MDB
>
>
>
>
>
>
>
>
>
> On Tuesday, August 7, 2018, 8:21:08 AM CDT, seaka...@juno.com <
> seaka...@juno.com> wrote:
>
>
>
>
>
> I've been using this software flawlessly for a while.  I'm using it on a
> Mac machine with Signalink and ICOM 735.  This morning when I turned on the
> computer and ran the program it was not decoding.  The waterfall shows lots
> of very strong signals.  Time is exact between software and computer.  When
> I look at the mac sound settings all is normal.  The software DOES
> transmit.  Just no decoding of signals.   I was using it yesterday before I
> shut the computer down perfectly.  No indication of trouble.  I also
> deleted the program and re installed a new download.  All perimeters stayed
> the same upon re install.  Again it does transmit.  Just no decode..
>
> Any ideas???
>
>
>
> Mike M
>
> AC1DV
>
>
>
>
>
>
>
>
> "All good things are wild and free."
>
> ~ Henry David Thoreau
>
>
>
> 
> *How To Remove Eye Bags & Lip Lines Fast (Watch)*
> Fit Mom Daily
> 
> http://thirdpartyoffers.juno.com/TGL3132/5b699b793d36a1b7944b9st02vuc
> [image: SponsoredBy Content.Ad]
>
> 
> --
> 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
>
>
> 
>  Virus-free.
> www.avg.com
> 
> <#m_-4362295290346306729_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>
> --
> 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 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, 

Re: [wsjt-devel] A strange signal seen on the air

[John C. Westmoreland, P.E.]

To All,

It's great to see all of the posts reviewing how to set audio correctly.

I was wondering if there's a published spec on the FT8 signal definition; I
think I may be seeing spurs and want to make sure that isn't actually part
of the fundamental.

73's,
John
AJ6BC

On Wed, Aug 1, 2018, 11:42 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Good instructions for the analog world.
>
> There's one more way that works on most any computer these days
> Even people with direct USB connections to their rigs are having problems.
>
> I would add this...and it should work on most any rig setup
>
> #1 Set WSJT-X to minimum power
> #2 Set audio devices (record/playback) to 0dB
> #3 Rig to 50% of rated power for CW (some rigs can do full power on CW,
> some can't)
> #4 Rig gain to zero (MIC gain if you're input is the MIC, or USB gain if
> USB, or Data gain if one of the DIN connectors)
> #5 Click Tune on WSJT-X
> #6 Bring up WSJT-X power SLOWLY to max...you should still see no power or
> very low output on your rig (assuming rig gain is at zero).
> #6 Bring rig gain up SLOWLY until you get 5W or so of power.  If you don't
> see power coming up then you have the wrong gain control.  Then look at
> your ALC meter.  Whatever your ALC meter shows at this stage is where it
> should stay as you bring up the rig gain. Some rigs show 1 bar of ALC (e.g.
> IC-7100), some show 30-50% (eg IC-7300/7410), some show no ALC at all.
> #7 Bring rig gain up and eventually you will see the ALC start
> risingback it down to the level you had at 5W.  What ever transmit
> power % you have at that point is all you will be able to transmit without
> ALC kicking in.  It will probably be 80-90% of your rated CW power.
> #8 Bring up rig power to full CW power level and the ALC should stay
> constant. You can now adjust your transmit power either from WSJT-X or the
> rig.
>
> de Mike W9MDB
>
>
>
> On Wednesday, August 1, 2018, 12:51:38 PM CDT, Jim Brown <
> k...@audiosystemsgroup.com> wrote:
>
>
> On 8/1/2018 9:50 AM, Black Michael via wsjt-devel wrote:
> > IMHO better if ops learn how to set up their rigs properly though.
>
> Exactly right. The last page of this link has detailed instructions for
> setting audio levels that avoids distortion.
>
> http://k9yc.com/USB_Interfaces.pdf
>
> 73, Jim K9YC
>
>
>
> --
> 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
>
--
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] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Hello Saku,

Thanks for the info - and I will try what you have pointed out.

My shack PC has been running Vista-64 for a while - I have too much stuff
on it and I'll use it as long as it will last - but yes, it is getting
dated.  I did look up some of the USB drivers today - circa 2013 - so I'm
pretty sure the WSJT-X code could not have been tested with those drivers.
And I don't think those drivers will be updateable either; so it's just a
matter of time now until they
are incompatible.

One way I've temporarily gotten around the issue is just to stop the
program; tune; and the start again - that seems to be working pretty well -
been working a lot of stations in Japan this evening too BTW.  Worked a
station in Korea and New Zealand also.  Saw one from China but they didn't
come back.

73's,
John
AJ6BC




On Thu, Jun 7, 2018 at 12:23 AM, Saku  wrote:

> John C. Westmoreland, P.E. kirjoitti 06.06.2018 klo 21:42:
>
> After operating and changing bands; I will use my tuner; and the program
> will either hang or will pop up a window saying the rig has become
> unresponsive.  I can click 'retry' sometimes and it'll be ok - but a
> consistent issue that will happen is it will either become completely
> unresponsive - with TX stuck; or I will get an error message saying hamlib
> I/O has suffered an error, and TX is stuck.
>
>
> Hi!
>
> I have IC706 with LDG Z-100Plus. Auto tuning is set from rig's menu and
> control cable exists between rig and LDG. So it will start tuning process
> every time on first TX when band is changed. Normally that 1st TX is
> pressing "tune" button of wsjt-x after band change.
>
> It is completely normal getting wsjt-x prompt "rig not responding" 99% of
> the time.
>
> That is because rigctld does run to timeout because rig is not responding
> to cat commands during tuning. And LDG has (according to manual) 1,5 sec
> tail after the best match is set. Said according to manual, as sometimes I
> feel that the delay from LDG led showing ok to time it drops TX feels much
> longer.
>
> Answering "Retry" *after LDG has dropped rig's TX* will continue normal
> operation.
>
> That could, maybe, be fixed by setting rigctld timeout bigger. But that
> cannot be done via wsjt-x radio setup. Then rigctld must be started as
> separate command line process to get wanted parameters in use, and after
> that open the wsjt-x with setting radio/Hamlib Net rigctl/localhost:4532 to
> get access to rigctld.
>
> I have been too lazy to test this longer timeout, just accepted that I
> need to press "retry" after every tuning session.
>
> Os here is Fedora 27 linux.
> With my little experience from past years I wonder how you can stand
> Vista? Slowest OS I have never seen. I'm sure that it makes also a part of
> your problems. Not everything is coming from RF leaks as suspected here.
>
>
> --
> Saku
> OH1KH
>
>
>
>
> 
> --
> 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

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Are you running Vista-64?

There are vast differences in these operating systems.

This thread reminds me of the saying when someone only has a hammer in
their toolbox.

Again, the OP should be read, understood, and answered.

I think some here think software is perfect; and all platforms produce
identical results.

I've posted a bug; plain and simple.



On Wed, Jun 6, 2018, 8:19 PM Neil Zampella  wrote:

> Can you prove that its not RF in the shack?   If you can verify that RF is
> not causing it then its a bug, otherwise, there is no issues with the
> software in your case.
>
> Neil, KN3ILZ
>
> On 6/6/2018 5:27 PM, John C. Westmoreland, P.E. wrote:
>
> OK, so we're 100% clear - and I want this bug report to be that:
>
> RF is causing the WSJT-X thread to hang in such a way it cannot be killed
> on my Vista-64 machine?
>
> Is that the claim?
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 2:01 PM, Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Nobody is claiming hamlib is bug-free.  But the problem you are reporting
>> has occurred to LOTS of people and the problem is almost always the
>> same...RF in the shack and on the lines.
>>
>> You'll find your problem is band-specific.  Transmitting 0W never fails.
>> Transmitting into a dummy load never fails.  All of that will prove it is
>> RF.
>>
>> As Jim said, grounding can be an issue too.  Many ops have improper
>> grounding (namely a rod stuck in the ground outside their shack which is
>> not bonded to the house ground).
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, June 6, 2018, 3:53:11 PM CDT, John C. Westmoreland, P.E. <
>> j...@westmorelandengineering.com> wrote:
>>
>>
>> Jim,
>>
>> OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
>> Vista-64?  I'm very skeptical about that; the most obvious issue and
>> nothing mentioned thus
>> far obviates this.
>>
>> I'm looking into the obvious first.  If my rig was so poorly configured;
>> how in the world did I make a contact with Argentina?
>>
>> And, I've made a lot of other contacts.  Including Virginia, North
>> Carolina, New York, and North Dakota not to mention Japan.  And Arizona,
>> and California, and
>> Oregon, and Washington...
>>
>> Since the thread running WSJT-X can't be killed; I'm looking into that
>> first; and the cause of that.
>>
>> The next obvious step for me is to make builds myself and look into the
>> source code.
>>
>> 73's,
>> John
>> AJ6BC
>>
>>
>> On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown 
>> wrote:
>>
>> On 6/6/2018 12:36 PM, John C. Westmoreland, P.E. wrote:
>>
>> That's an interesting hypothesis.  Since USB is differential signaling -
>> it has some noise immunity; but I will definitely check into this.
>>
>>
>> Hum/buzz gets into our systems as a result of failure to implement proper
>> bonding between interconnected equipment, combined with improper
>> termination of shields within equipment by their designers. Study my
>> tutorial on this, which goes through both circuit analysis of the problem
>> and details good engineering practice.
>>
>> http://k9yc.com/GroundingAndAu dio.pdf
>> <http://k9yc.com/GroundingAndAudio.pdf>
>>
>> Or study N0AX's new ARRL book on the topic, which was inspired by my
>> tutorial, and to which I made many contributions.
>>
>> 73, Jim K9YC
>>
>>
>> -- --
>> --
>> 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.n et 
>> https://lists.sourceforge.net/ lists/listinfo/wsjt-devel
>> <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
>>
>>
>> --
>> Check out the vibrant tech com

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Please read the OP.



On Wed, Jun 6, 2018, 8:19 PM Neil Zampella  wrote:

> Can you prove that its not RF in the shack?   If you can verify that RF is
> not causing it then its a bug, otherwise, there is no issues with the
> software in your case.
>
> Neil, KN3ILZ
>
> On 6/6/2018 5:27 PM, John C. Westmoreland, P.E. wrote:
>
> OK, so we're 100% clear - and I want this bug report to be that:
>
> RF is causing the WSJT-X thread to hang in such a way it cannot be killed
> on my Vista-64 machine?
>
> Is that the claim?
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 2:01 PM, Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Nobody is claiming hamlib is bug-free.  But the problem you are reporting
>> has occurred to LOTS of people and the problem is almost always the
>> same...RF in the shack and on the lines.
>>
>> You'll find your problem is band-specific.  Transmitting 0W never fails.
>> Transmitting into a dummy load never fails.  All of that will prove it is
>> RF.
>>
>> As Jim said, grounding can be an issue too.  Many ops have improper
>> grounding (namely a rod stuck in the ground outside their shack which is
>> not bonded to the house ground).
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, June 6, 2018, 3:53:11 PM CDT, John C. Westmoreland, P.E. <
>> j...@westmorelandengineering.com> wrote:
>>
>>
>> Jim,
>>
>> OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
>> Vista-64?  I'm very skeptical about that; the most obvious issue and
>> nothing mentioned thus
>> far obviates this.
>>
>> I'm looking into the obvious first.  If my rig was so poorly configured;
>> how in the world did I make a contact with Argentina?
>>
>> And, I've made a lot of other contacts.  Including Virginia, North
>> Carolina, New York, and North Dakota not to mention Japan.  And Arizona,
>> and California, and
>> Oregon, and Washington...
>>
>> Since the thread running WSJT-X can't be killed; I'm looking into that
>> first; and the cause of that.
>>
>> The next obvious step for me is to make builds myself and look into the
>> source code.
>>
>> 73's,
>> John
>> AJ6BC
>>
>>
>> On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown 
>> wrote:
>>
>> On 6/6/2018 12:36 PM, John C. Westmoreland, P.E. wrote:
>>
>> That's an interesting hypothesis.  Since USB is differential signaling -
>> it has some noise immunity; but I will definitely check into this.
>>
>>
>> Hum/buzz gets into our systems as a result of failure to implement proper
>> bonding between interconnected equipment, combined with improper
>> termination of shields within equipment by their designers. Study my
>> tutorial on this, which goes through both circuit analysis of the problem
>> and details good engineering practice.
>>
>> http://k9yc.com/GroundingAndAu dio.pdf
>> <http://k9yc.com/GroundingAndAudio.pdf>
>>
>> Or study N0AX's new ARRL book on the topic, which was inspired by my
>> tutorial, and to which I made many contributions.
>>
>> 73, Jim K9YC
>>
>>
>> -- --
>> --
>> 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.n et 
>> https://lists.sourceforge.net/ lists/listinfo/wsjt-devel
>> <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
>>
>>
>> --
>> 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
>
--
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] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Interesting, but I'll stick to the OP.

Can someone answer something else - when you operate - for the people that
have had the RFI issue - how long did you operate before you saw the issue?
Is it deterministic?

Did WSJT-X ever lock up in a way that you had to reboot?

Has WSJT-X been proven to be 1000% free of memory leaks?  How long can the
log windows build up before there is a problem?  Has this been tested; and
if so, where is the documentation
regarding the test procedures and results.

Is there a config issue (like you were tuning to 160m when things failed)
that could get stuck in a config file across boots so it would jump in the
same location when the program was
restarted?

I'll stick to the point in the OP.

Windows has been, and probably always will be, somewhat notorious for
memory leaks.  Since I seriously doubt this program has been verified to be
memory leak free; again, I will consider
the obvious issues since if RFI was the only issue here; I don't see how I
could be making contacts that are +6.7 K miles from here.

Once you've implemented your RFI fix, does the program NEVER fail?

Thanks,
John W.
AJ6BC


On Wed, Jun 6, 2018 at 3:17 PM, Black Michael  wrote:

> Building on Vista won't change anything.  The build environment (JTSDK) is
> the same on all Windows platforms and the binary will be exactly the same.
>
> Just buy a shielded USB cable, ensure your ground system is correct,
> replace all your ethernet cables with shielded, and I'll bet your problem
> disappears.
> https://www.amazon.com/Tripp-Lite-Hi-Speed-Ferrite-U023-
> 006/dp/B003MQ29B2/ref=sr_1_3?ie=UTF8=1528323322=8-3&
> keywords=shielded+usb+cable
> https://www.amazon.com/Cable-Matters-Snagless-Shielded-
> Ethernet/dp/B00BIPTPAM/ref=sr_1_1_sspa?s=electronics=
> UTF8=1528323382=1-1-spons=shielded+ethernet+cable=1
>
> de Mike W9MDB
>
>
>
> On Wednesday, June 6, 2018, 4:56:43 PM CDT, John C. Westmoreland, P.E. <
> j...@westmorelandengineering.com> wrote:
>
>
> Mike,
>
> When I look here:
>
> https://sourceforge.net/p/wsjt/mailman/search/?q=VISTA_list=all
>
> I'm getting 77 hits on the term Vista - that includes this thread; I
> haven't looked through all of those yet.
>
> JT9.exe was what I was missing - referring back to the OP.  Good to get
> back to the OP here.
>
> If no one is actually using/building with Vista-64 here; then I should set
> up a build environment and give that a go; and that could be the
> root cause possibly of what I'm seeing; plus maybe less than optimal USB
> drivers.  People apparently are running with Vista - it's unclear
> if that's 32-bit or 64-bit versions right now.
>
> I'll report back what I find - that could take a little while.
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 2:36 PM, Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> If you lose the USB connection all bets are off.
> When you kill the process are you killing wsjtx.exe and jt9.exe?
> You should not need a reboot but perhaps Vista is a bit pickier about USB
> devices that disappear and is causing the lockup.
> You can test that idea by just pulling the USB while it's running. You
> should get an error and be able to quit politely on the CAT control.  But
> if the sound disappears that might be different.
> I haven't heard of any Vista systems on this list so you are kind of
> on-your-own there.  I see XP, Windows 7, and Windows 10, but no Windows
> Vista or 8.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 4:28:00 PM CDT, John C. Westmoreland, P.E. 
>  com > wrote:
>
>
> OK, so we're 100% clear - and I want this bug report to be that:
>
> RF is causing the WSJT-X thread to hang in such a way it cannot be killed
> on my Vista-64 machine?
>
> Is that the claim?
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 2:01 PM, Black Michael via wsjt-devel 
>  net > wrote:
>
> Nobody is claiming hamlib is bug-free.  But the problem you are reporting
> has occurred to LOTS of people and the problem is almost always the
> same...RF in the shack and on the lines.
>
> You'll find your problem is band-specific.  Transmitting 0W never fails.
> Transmitting into a dummy load never fails.  All of that will prove it is
> RF.
>
> As Jim said, grounding can be an issue too.  Many ops have improper
> grounding (namely a rod stuck in the ground outside their shack which is
> not bonded to the house ground).
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 3:53:11 PM CDT, John C. Westmoreland, P.E. 
>  com > wrote:
>
>
> Jim,
>
> OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
> Vista-64?  I'm very skeptical about that

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Mike,

When I look here:

https://sourceforge.net/p/wsjt/mailman/search/?q=VISTA_list=all

I'm getting 77 hits on the term Vista - that includes this thread; I
haven't looked through all of those yet.

JT9.exe was what I was missing - referring back to the OP.  Good to get
back to the OP here.

If no one is actually using/building with Vista-64 here; then I should set
up a build environment and give that a go; and that could be the
root cause possibly of what I'm seeing; plus maybe less than optimal USB
drivers.  People apparently are running with Vista - it's unclear
if that's 32-bit or 64-bit versions right now.

I'll report back what I find - that could take a little while.

73's,
John
AJ6BC


On Wed, Jun 6, 2018 at 2:36 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> If you lose the USB connection all bets are off.
> When you kill the process are you killing wsjtx.exe and jt9.exe?
> You should not need a reboot but perhaps Vista is a bit pickier about USB
> devices that disappear and is causing the lockup.
> You can test that idea by just pulling the USB while it's running. You
> should get an error and be able to quit politely on the CAT control.  But
> if the sound disappears that might be different.
> I haven't heard of any Vista systems on this list so you are kind of
> on-your-own there.  I see XP, Windows 7, and Windows 10, but no Windows
> Vista or 8.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 4:28:00 PM CDT, John C. Westmoreland, P.E. <
> j...@westmorelandengineering.com> wrote:
>
>
> OK, so we're 100% clear - and I want this bug report to be that:
>
> RF is causing the WSJT-X thread to hang in such a way it cannot be killed
> on my Vista-64 machine?
>
> Is that the claim?
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 2:01 PM, Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Nobody is claiming hamlib is bug-free.  But the problem you are reporting
> has occurred to LOTS of people and the problem is almost always the
> same...RF in the shack and on the lines.
>
> You'll find your problem is band-specific.  Transmitting 0W never fails.
> Transmitting into a dummy load never fails.  All of that will prove it is
> RF.
>
> As Jim said, grounding can be an issue too.  Many ops have improper
> grounding (namely a rod stuck in the ground outside their shack which is
> not bonded to the house ground).
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 3:53:11 PM CDT, John C. Westmoreland, P.E. 
>  com > wrote:
>
>
> Jim,
>
> OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
> Vista-64?  I'm very skeptical about that; the most obvious issue and
> nothing mentioned thus
> far obviates this.
>
> I'm looking into the obvious first.  If my rig was so poorly configured;
> how in the world did I make a contact with Argentina?
>
> And, I've made a lot of other contacts.  Including Virginia, North
> Carolina, New York, and North Dakota not to mention Japan.  And Arizona,
> and California, and
> Oregon, and Washington...
>
> Since the thread running WSJT-X can't be killed; I'm looking into that
> first; and the cause of that.
>
> The next obvious step for me is to make builds myself and look into the
> source code.
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown 
> wrote:
>
> On 6/6/2018 12:36 PM, John C. Westmoreland, P.E. wrote:
>
> That's an interesting hypothesis.  Since USB is differential signaling -
> it has some noise immunity; but I will definitely check into this.
>
>
> Hum/buzz gets into our systems as a result of failure to implement proper
> bonding between interconnected equipment, combined with improper
> termination of shields within equipment by their designers. Study my
> tutorial on this, which goes through both circuit analysis of the problem
> and details good engineering practice.
>
> http://k9yc.com/GroundingAndAu dio.pdf
> <http://k9yc.com/GroundingAndAudio.pdf>
>
> Or study N0AX's new ARRL book on the topic, which was inspired by my
> tutorial, and to which I made many contributions.
>
> 73, Jim K9YC
>
>
> -- --
> --
> 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.n et 
> https://lists.sourceforge.net/ lists/listinfo/wsjt-devel
> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>
>
> -

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

OK, so we're 100% clear - and I want this bug report to be that:

RF is causing the WSJT-X thread to hang in such a way it cannot be killed
on my Vista-64 machine?

Is that the claim?

73's,
John
AJ6BC


On Wed, Jun 6, 2018 at 2:01 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Nobody is claiming hamlib is bug-free.  But the problem you are reporting
> has occurred to LOTS of people and the problem is almost always the
> same...RF in the shack and on the lines.
>
> You'll find your problem is band-specific.  Transmitting 0W never fails.
> Transmitting into a dummy load never fails.  All of that will prove it is
> RF.
>
> As Jim said, grounding can be an issue too.  Many ops have improper
> grounding (namely a rod stuck in the ground outside their shack which is
> not bonded to the house ground).
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 3:53:11 PM CDT, John C. Westmoreland, P.E. <
> j...@westmorelandengineering.com> wrote:
>
>
> Jim,
>
> OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
> Vista-64?  I'm very skeptical about that; the most obvious issue and
> nothing mentioned thus
> far obviates this.
>
> I'm looking into the obvious first.  If my rig was so poorly configured;
> how in the world did I make a contact with Argentina?
>
> And, I've made a lot of other contacts.  Including Virginia, North
> Carolina, New York, and North Dakota not to mention Japan.  And Arizona,
> and California, and
> Oregon, and Washington...
>
> Since the thread running WSJT-X can't be killed; I'm looking into that
> first; and the cause of that.
>
> The next obvious step for me is to make builds myself and look into the
> source code.
>
> 73's,
> John
> AJ6BC
>
>
> On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown 
> wrote:
>
> On 6/6/2018 12:36 PM, John C. Westmoreland, P.E. wrote:
>
> That's an interesting hypothesis.  Since USB is differential signaling -
> it has some noise immunity; but I will definitely check into this.
>
>
> Hum/buzz gets into our systems as a result of failure to implement proper
> bonding between interconnected equipment, combined with improper
> termination of shields within equipment by their designers. Study my
> tutorial on this, which goes through both circuit analysis of the problem
> and details good engineering practice.
>
> http://k9yc.com/GroundingAndAu dio.pdf
> <http://k9yc.com/GroundingAndAudio.pdf>
>
> Or study N0AX's new ARRL book on the topic, which was inspired by my
> tutorial, and to which I made many contributions.
>
> 73, Jim K9YC
>
>
> -- --
> --
> 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.n et 
> https://lists.sourceforge.net/ lists/listinfo/wsjt-devel
> <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
>
> 
> --
> 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

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Jim,

OK - so the claim I'm reading here is Hamlib is 1000% bug-free regarding
Vista-64?  I'm very skeptical about that; the most obvious issue and
nothing mentioned thus
far obviates this.

I'm looking into the obvious first.  If my rig was so poorly configured;
how in the world did I make a contact with Argentina?

And, I've made a lot of other contacts.  Including Virginia, North
Carolina, New York, and North Dakota not to mention Japan.  And Arizona,
and California, and
Oregon, and Washington...

Since the thread running WSJT-X can't be killed; I'm looking into that
first; and the cause of that.

The next obvious step for me is to make builds myself and look into the
source code.

73's,
John
AJ6BC


On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown 
wrote:

> On 6/6/2018 12:36 PM, John C. Westmoreland, P.E. wrote:
>
>> That's an interesting hypothesis.  Since USB is differential signaling -
>> it has some noise immunity; but I will definitely check into this.
>>
>
> Hum/buzz gets into our systems as a result of failure to implement proper
> bonding between interconnected equipment, combined with improper
> termination of shields within equipment by their designers. Study my
> tutorial on this, which goes through both circuit analysis of the problem
> and details good engineering practice.
>
> http://k9yc.com/GroundingAndAudio.pdf
>
> Or study N0AX's new ARRL book on the topic, which was inspired by my
> tutorial, and to which I made many contributions.
>
> 73, Jim K9YC
>
>
> 
> --
> 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

Re: [wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Mike/Richard,

That's an interesting hypothesis.  Since USB is differential signaling - it
has some noise immunity; but I will definitely check into this.

Since my machine is an older Vista-64 machine; I thought that may have more
to do with it.  Also, I didn't think I was putting out the power necessary
to cause this type of issue.

I was thinking it's more of a Hamlib/Vista-64 issue; but I will look into
this.

I am running a lot of other things in the shack; got a GPS project;
definitely not seeing the noise I would think that's necessary to cause a
problem like this; but again, thanks for the info and I will check into
it.  I have a decent frequency sniffer and not seeing anything on the bands
in use for FT8 to cause such an issue, but I'll do another sweep.

Even if what I'm seeing is being caused by something else; it's interesting
the symptoms seem to be the same.  By any chance is your rig PC running
Vista-64?
RigBlaster has short USB from PC; the CAT control I'm using is USB to
serial plugging into the LDG.

73's,
John
AJ6BC





On Wed, Jun 6, 2018 at 12:15 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> You've got RF interference on your USB cable(s).
> I guess you have a USB cable for CAT control too as that sounds like the
> one having the problem.
>
> You can try shielded USB cables with torroids to help. That has worked for
> everybody I know that has such a problem.  You can find them on Amazon for
> example.
>
> However, there can be other noise sources causing problems too so that may
> not the only thing that needs fixing.  Ethernet cables (get shielded ones)
> are another source of RF interference for example.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, June 6, 2018, 2:08:26 PM CDT, John C. Westmoreland, P.E. <
> j...@westmorelandengineering.com> wrote:
>
>
> Hello WSJT-DEVEL Group,
>
> First, kudos on such a great program.
>
> I wanted to pass on what I'm seeing with the latest released revision -
> 1.9.1 - I didn't see a bug database on sourceforge - if there is one
> someplace I can post to a bug database as appropriate.
>
> The OS I'm using is Vista-64 - it's the current computer I use in the
> shack - so maybe this could be part of the issue I'm seeing.
>
> I have a Yaesu FT-450D and am using a RigBlaster with it - some of the
> posted configs don't exactly match what I'm seeing to make things work
> (made a contact with Argentina last night) - and I also am using and LDG
> tuner with a vertical.
>
> I'm able to repeat this bug as well -
>
> After operating and changing bands; I will use my tuner; and the program
> will either hang or will pop up a window saying the rig has become
> unresponsive.  I can click 'retry' sometimes and it'll be ok - but a
> consistent issue that will happen is it will either become completely
> unresponsive - with TX stuck; or I will get an error message saying hamlib
> I/O has suffered an error, and TX is stuck.
>
> When the issue happens, TX is always stuck.
>
> I stop the program, but I can still see it running with Task Manager; and
> I can't kill it.  I have to reboot the computer (Vista-64) to reset things;
> of course I have to power the Rig off.
>
> I am not sure right now how to kill a process that is using Hamlib I/O - I
> haven't found a specific process thread for that other than the WSJT-X
> program; which I can't kill.  Of course I have full admin rights on my
> shack computer.
>
> This is probably a known issue; and if there is a bug database I can post
> or add to that with this info.
>
> Thanks!
>
> 73's,
> John Westmoreland
> AJ6BC
>
> 
> --
> 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
>
>
--
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

[wsjt-devel] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Hello WSJT-DEVEL Group,

First, kudos on such a great program.

I wanted to pass on what I'm seeing with the latest released revision -
1.9.1 - I didn't see a bug database on sourceforge - if there is one
someplace I can post to a bug database as appropriate.

The OS I'm using is Vista-64 - it's the current computer I use in the shack
- so maybe this could be part of the issue I'm seeing.

I have a Yaesu FT-450D and am using a RigBlaster with it - some of the
posted configs don't exactly match what I'm seeing to make things work
(made a contact with Argentina last night) - and I also am using and LDG
tuner with a vertical.

I'm able to repeat this bug as well -

After operating and changing bands; I will use my tuner; and the program
will either hang or will pop up a window saying the rig has become
unresponsive.  I can click 'retry' sometimes and it'll be ok - but a
consistent issue that will happen is it will either become completely
unresponsive - with TX stuck; or I will get an error message saying hamlib
I/O has suffered an error, and TX is stuck.

When the issue happens, TX is always stuck.

I stop the program, but I can still see it running with Task Manager; and I
can't kill it.  I have to reboot the computer (Vista-64) to reset things;
of course I have to power the Rig off.

I am not sure right now how to kill a process that is using Hamlib I/O - I
haven't found a specific process thread for that other than the WSJT-X
program; which I can't kill.  Of course I have full admin rights on my
shack computer.

This is probably a known issue; and if there is a bug database I can post
or add to that with this info.

Thanks!

73's,
John Westmoreland
AJ6BC
--
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] Bug Report: Version 1.9.1

[John C. Westmoreland, P.E.]

Hello Again,

The bug just happened again - didn't even use the tuner yet - so apparently
it isn't related to the tuning process.  I had been using 40m and was
trying 160m and it got stuck - I had previously tuned to 160m (meaning
using the tuner) outside of the program.

Had to reboot to get it back to normal operation.

73's,
John W.
AJ6BC


On Wed, Jun 6, 2018 at 11:42 AM, John C. Westmoreland, P.E. <
j...@westmorelandengineering.com> wrote:

> Hello WSJT-DEVEL Group,
>
> First, kudos on such a great program.
>
> I wanted to pass on what I'm seeing with the latest released revision -
> 1.9.1 - I didn't see a bug database on sourceforge - if there is one
> someplace I can post to a bug database as appropriate.
>
> The OS I'm using is Vista-64 - it's the current computer I use in the
> shack - so maybe this could be part of the issue I'm seeing.
>
> I have a Yaesu FT-450D and am using a RigBlaster with it - some of the
> posted configs don't exactly match what I'm seeing to make things work
> (made a contact with Argentina last night) - and I also am using and LDG
> tuner with a vertical.
>
> I'm able to repeat this bug as well -
>
> After operating and changing bands; I will use my tuner; and the program
> will either hang or will pop up a window saying the rig has become
> unresponsive.  I can click 'retry' sometimes and it'll be ok - but a
> consistent issue that will happen is it will either become completely
> unresponsive - with TX stuck; or I will get an error message saying hamlib
> I/O has suffered an error, and TX is stuck.
>
> When the issue happens, TX is always stuck.
>
> I stop the program, but I can still see it running with Task Manager; and
> I can't kill it.  I have to reboot the computer (Vista-64) to reset things;
> of course I have to power the Rig off.
>
> I am not sure right now how to kill a process that is using Hamlib I/O - I
> haven't found a specific process thread for that other than the WSJT-X
> program; which I can't kill.  Of course I have full admin rights on my
> shack computer.
>
> This is probably a known issue; and if there is a bug database I can post
> or add to that with this info.
>
> Thanks!
>
> 73's,
> John Westmoreland
> AJ6BC
>
>
--
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