It's not always deterministic although in some instances it is. 50W on 40M for
example crashes but 0W on 40M works. Once you find a setting that causes it
then it will usually repeat pretty regularly at that setting but 0W should
never crash.
It's unlikely to happen on all bands. I had one guy who found if he held is
hand at the top of the monitor it would crash. Another found his antenna rotor
caused it. Another found the USB connector on one side of his laptop was OK
but the other side caused problems (ribbon cable to the other side). All were
solved with proper grounding and shielded cables.You're definitely not alone
with this problem.
de Mike W9MDB
On Wednesday, June 6, 2018, 5:27:53 PM CDT, John C. Westmoreland, P.E.
<j...@westmorelandengineering.com> wrote:
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 documentationregarding 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 wasrestarted?
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 considerthe 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 <mdblac...@yahoo.com> 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&qid=1528323322&sr=8-3&
keywords=shielded+usb+cablehttps://www.amazon.com/Cable-
Matters-Snagless-Shielded- Ethernet/dp/B00BIPTPAM/ref=sr_
1_1_sspa?s=electronics&ie= UTF8&qid=1528323382&sr=1-1- spons&keywords=shielded+
ethernet+cable&psc=1
de Mike W9MDB
On Wednesday, June 6, 2018, 4:56:43 PM CDT, John C. Westmoreland, P.E.
<john@westmorelandengineering. com> wrote:
Mike,
When I look here:
https://sourceforge.net/p/ wsjt/mailman/search/?q=VISTA& mail_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 theroot cause possibly
of what I'm seeing; plus maybe less than optimal USB drivers. People
apparently are running with Vista - it's unclearif 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,JohnAJ6BC
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.
<john@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,JohnAJ6BC
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.
<john@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 thusfar 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,JohnAJ6BC
On Wed, Jun 6, 2018 at 12:59 PM, Jim Brown <k...@audiosystemsgroup.com> 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
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
------------------------------ ------------------------------ ------------------
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
