|
locked
WSJTx not decoding, and problem with saved files
#IssueReport
#Q65
Situation: 23 cm EME WSJTx in Q65-60c mode failed to decode strong clear signals.
These same signals simultaneously decoded fine in Map65 v3.0, Q65-60C The saved files do not decode and in the Wide Graph appear to be too wide for Q65-60C. They do not decode on a different computer with either v2.4 or 2.5-RC1 Computer : AMD FX-6300 Six core 3.5 ghz 8.00 GB Ram Windows 10 home 64 bit. Generic USB audio device WSJT-x v2.5.0-RC1 Q65-60C Max Drift = 0 (but increasing this does not help to decode) Aggressive decoding level =10 USB Sound device set for 48000hz, 16 bit mono. Three examples attached. I have relevant .iq files if needed. I also attached an earlier saved file from the same computer that decoded and saved just fine (210607_1206)
|
|
|
|
Bill Parris
Jim .... it is easy to conclude there is no activity. But look at the vertical bar on the left side of the screen. Adjust it down where it is not stuck at the top. When it is swinging from 60 to 80, the band will come alive. I use a 7300 and the RF knob adjusts it easily.
Good luck. Bill, AA4R
|
|
|
|
locked
Re: Subprocess Failed with Exit Code 2 on WSJT-X v2.2.2
Niece KA1ULN <ka1uln1@...>
me too getting the same error, running windows 10.
i have received the same error with 2.3, 2.4 and 2.5 all the same subprocess error code 2. any suggestions?
|
|
|
|
Bob McGraw - K4TAX <rmcgraw@...>
Your radio perhaps hasn't selected a dummy load or no antenna for that band has it? There is lots of FT-8 activity on 7.074.
73 Bob, K4TAX
|
|
|
|
locked
Re: Version 2.4.0 ate my adi file
#IssueReport
#logging
Panos
Hi, wsjtx_log file is already an adif file 73
|
|
|
|
locked
Re: Version 2.4.0 ate my adi file
#IssueReport
#logging
OK Paul I will email it to you.
73, Julian KR5J
|
|
|
|
Joe Subich, W4TV
Old habits. I have lots of cables with 13 pin and lots of 13 pinAccording to the manual, SSB-D works with the ACC (13 pin DIN) connector. 73, ... Joe, W4TV On 2021-06-11 9:10 AM, Don Melcher wrote: On Thu, Jun 10, 2021 at 06:11 PM, Joe Subich, W4TV wrote:Old habits. I have lots of cables with 13 pin and lots of 13 pin connectors on hand from my days selling SCS modems. They’re a lot easier to solder to then Mini-DIN.
|
|
|
|
Robert Newell <coffeecanuck@...>
The ICOM 703+ is now on the air and talking nicely with my Lenovo laptop -
All the advice was perfect - needed a couple of tweaks in my settings and I was good to go. Many thank you's to all the folks that jumped in so quickly. Colin - VA7WWV - CN88
|
|
|
|
locked
Re: WSJT-X and N1MM and GridTracker-can they all work together?
John
Or you could try "com-0-com". John VE7KKQ
|
|
|
|
locked
Re: 2.5 RC1
#wsjt-x-crashing
Hi Joe - hope u are well...yes of course I suspected some local problem here -- uninstalled all versions of WSJT and did fresh install of 2.5.0 rc1 and problem seems to have been resolved. At the time of the repeated crashes i was running 2 programs of WSJT simultaneously and transmitting on 1296 ft8. Problem was not there on 2m so I now suspect 1296 RF was getting into my computer (running 200w to antenna directly over my shack)...have not been able to duplicate it again...hope I cant hihi....Thanx for all your work on WSJT over the years- it sure has transformed ham radio, especially on the VHF/UHF bands.
73 - stay safe -- jay ny2ny
|
|
|
|
Steve Kavanagh
Hi Peter
Yes, I saw your posting earlier...an interesting thread. I am not sure I understand what the reasons are for the ramp up and down. My interest in Q65 is really for VHF and up, where Class D and E amps are mostly impractical (though getting closer over time as technology improves), but running a Class C amp (or class A or AB in hard saturation) is easy. I'm guessing there would be no equivalent issue with the ramps in this case, though I suppose there might be a momentary increase in dissipation. But it would be helpful to know the waveform and what one gives up by eliminating the ramps. 74, Steve VE3SMA
|
|
|
|
On 11/06/2021 12:24, James Quick wrote:
Hi Jim, please put the attached file into your WSJT-X configuration files directory (on macOS that is ~/Library/Preferences), then restart WSJT-X and do a minimal test that demonstrates the issue. In this case that would seem to be merely a band change using the WSJT-X band selection drop-down list. Then quit WSJT-X. It will have created a file on your Desktop called WSJT-X_RigControl.log , send me that file for analysis please (g4wjs <at> classdesign <dot> com). Once you have sent the log file you can delete it from your Desktop and also delete the log configuration file to revert to normal operation. 73
|
|
|
|
Don Melcher
On Thu, Jun 10, 2021 at 06:11 PM, Joe Subich, W4TV wrote:
If you would use SSB-D you would not need to remove the mic (Note:Old habits. I have lots of cables with 13 pin and lots of 13 pin connectors on hand from my days selling SCS modems. They’re a lot easier to solder to then Mini-DIN. -- Don W6CZ/W6ZB DM07bk
|
|
|
|
Derek Brown
Hi Bill Here's the info for the three PC's I use IC756 - Intel(R) Core(TM)2 Duo CPU E7400 2.80Ghz IC7610 - Intel(R) Core(TM) i5 CPU @3.20Ghz IC9700 - Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz 2.80 GHz OS on all Win10 73 Derek G8ECI
On Wednesday, 9 June 2021, 00:37:35 BST, Bill Somerville <g4wjs@...> wrote:
Hi all WSJT-X users, we are looking into some performance enhancements that will take advantage of some parallel processing features of modern CPU architectures. In order to gauge how much backwards compatibility for older CPUs we will have to implement it would help to know who is using such older processors. Please don't turn this thread in to a mine is better than yours conversation, all I need to know is who or how many of you are using the older CPU architectures. Note that this applies to MS Windows, Intel Linux, and Intel macOS users, it is about CPUs not operating systems. The technology we will use is called AVX and that is present on all Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is also present on AMD CPUs since the Jaguar or Puma based CPU models (some late Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa 2013 to present. Notably Intel CPUs branded Celeron, Pentium, or Atom do not support the AVX technology. So in summary, look up your CPU and if it **does not support AVX** (https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) then let me know. 73 Bill G4WJS.
|
|
|
|
James Quick
I am going to try this again, I am running a MacOS Big Sur, IC-7300, with WSJT-X. I can start WSJT-X v2.3.1 and everything is ok. If change bands on WSJT-X 2.3.1 the 7300 changes bands. I close v2.3.1 and start v2.5.0 rc1 it starts as it should but if I try to change bands it will not change on the program or the 7300. I can manually change bands on the 7300 and it will change the band on WSJT-X. None of the updates after v2.3.1 will work. I am at a complete loss as to what to do. I have uninstalled the program, deleted the INI file, and reinstalled the program with no luck. Any help would be a big help. 73 Jim Quick / N4ULE / Ex KA4BEG Sent with Shift
|
|
|
|
Hello Steve,
I was the poster who raised the issue with the FST4(W) waveforms in this forum and in the RSGB LF group. You can see the later part of the discussion here: https://wsjtx.groups.io/g/main/topic/79269122#20188 The problem arises because, at some point in the chain, the analog drive signal has to be converted to digital form, preferably with as little jitter as possible. Typical squaring circuits have a dead or indeterminate band - however tiny - and, with very slow envelopes, produce erratic pulse drive to the (very widely used) Class D or E PAs, the designs of which typically requires a well-tempered pulse train. As you see from the previous discussion there are several solutions possible, the most satisfactory being the setting of the environment variable as outlined by Bill. I haven't tried Q65 yet but can do so in the next week. Whether there's a problem will depend on the how slow the envelope rise and fall is. I agree it'd be handy to have some descriptions or, better yet, sketches of the various WSJT mode signals. 73, Peter.
|
|
|
|
Hi Rick,
my apologies, you are correct, the Core
i3-370M does not support AVX:
73
Bill G4WJS.
On 11/06/2021 11:26, Rick Chapman
wrote:
|
|
|
|
Rick Chapman
Hi Bill Thanks for the response. However, I'm unable to see AVX mentioned under the Core I3-370M processor column in the attachment. The second column which does include AVX is for a different
processor - Core I7-2600. I extracted the data on the two processors I use for wsjt-x, the I3 is in the shack laptop and the I7 is in a desktop in another building, which I often use to run wsjt-x remotely by piping the audio to and from the shack laptop over the lan. I'd be happy if the laptop I3 does support AVX but i don't think
so. Cheers Rick (GM4JIB)
On 09/06/2021 11:23, Bill Somerville
wrote:
|
|
|
|
neil_zampella
There's no 'bug' in JTAlert ... the problem that's being referred
to recently is the issue with the MS .NET update causing sound
problems.
On 6/11/2021 12:44 AM, Chris Levingston
wrote:
Hi, Bill - thanks for the quick response.
|
|
|
|
neil_zampella
I would report this to the HAMAPPS support list on groups.io,
WSJT-X has nothing to do with these function keys.
On 6/11/2021 2:46 AM, Chris Levingston
wrote:
I can't get any of these to work clicking on them in the View window or using the Function keys.
|
|
|