O

Bill yes I have spent  a lot of time looking at the colors in WSJTX, I tried several schemes to get it to match JTAlert colors but i gave up. i just found it too confusing, and as i said before, i could not keep the different colors straight, I'm sure its me, I'm sure others find it very useful. 

also I apologize for saying the colors are not band specific, as they are. 

Dan KC2STA

On Wed, Oct 28, 2020 at 7:25 AM Bill Somerville <g4wjs@...> wrote:

On 28/10/2020 11:12, d_ziolkowski wrote:

I do not believe the colors in wsjtx are band specific, in jtalert they are. 

Dan KC2STA

Dan,

have you even bothered to look at the "Settings->Colors" panel in WSJT-X?

73
Bill
G4WJS.

--

Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX

--
73 Phil GM3ZZA

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of John (na0a)
Sent: Wednesday, October 28, 2020 12:57 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] Trouble setting up CAT path to FlexRadio #WSJTX_config

I have a FlexRadio 6600M and trying to install wstj. In the wsjt Setting -> Radio menu I have entered the IP address of my computer xxx.xxx.x.x:5011.  Then set the Flex SmartSDR CAT to the 5011 port and click on the "Test CAT" button. The button turns red and I get the following error message "Hamlib error: IO error while opening connection to rig"  which is not very informative. 

Any thought on why this is happening and possible solutions?

On Oct 17, 2020, at 4:07 PM, Russ Ravella <rus5@...> wrote:

Thanks Bill and Bruce,

 

I see it now.  microsoft apparently decided to re-hide my system files during the last update and “AppData” wasn’t showing or being included in searches.  Fixed now.

 

I happened to actually be in the no-decode state when I saw Ed’s post and your response.  The program controls are still responsive when this happens but the waterfall and input meter are frozen and of course no decodes come in.  I’m running a Flex 6700 (SDR 3.1.12, Win10 2004) and DAX is responsive while WSJT-X decodes are frozen.  Restarting DAX anyway doesn’t help.

 

So I set “Save all” for a few progress bar cycles and checked but out of a zillion files there were none covering that period.  Obviously the file doesn’t get generated when decodes are frozen and “Save” was off (somehow?) when it happened this time.  I’ve stopped and relaunched WSJT-X, it’s un-frozen again, and I’ve got “Save All” re-enabled.  So when it happens again I’ll grab the latest file and send it to you.

 

Thanks for the help !

Russ KR6W

On Oct 17, 2020, at 3:31 PM, Bruce N7XGR <n7xgr1@...> wrote:

Russ,  Here it is located,  C:\Users\YourName\AppData\Local\WSJT-X\save

 

Bruce  N7XGR

On Sat, Oct 17, 2020 at 6:25 PM Russ Ravella via groups.io <rus5=me.com@groups.io> wrote:

Hi Bill,

I have often had this problem too and have reported it.  In my case, sometimes restarting WSJT-X does fix it though often only for a few minutes.  I also don’t believe it has anything to do with my computer h/w (it’s now happened with three totally different computers) and I don’t believe it’s my radio (I’ve had five during the period I’ve had the problem) or how its configured or connected (again, there have been many cases).  I would like to also send you my saved.WAV file but I can’t find a file named “saved.WAV” anywhere on my computer after checking Menu>Save>Save all” from which to pick a good non-decode period.  Could you please elaborate just slightly ?

Thanks,
Russ KR6W

> On Oct 17, 2020, at 12:25 PM, Bill Somerville <g4wjs@...> wrote:
> 
> On 17/10/2020 20:22, lmeeny wrote:
>> Hello,
>> 
>> I've been off the air for 5 days now with a problem vexing many members of the group, WSJT-X stops decoding after working properly for months on end.
>> 
>> The following conditions are true:
>> 
>> My computer clock is properly synced every 40 minutes. I've used two different NTP time sync programs and both check fine against time.is. When working properly WSJT-X displays dt values varying +/- 0.2 sec around 0.0 sec.
>> 
>> Signals are displayed on the waterfall and amplitude on the main window vertical tape display varies reflecting waterfall signal strengths. Waterfall signals can be saved to .wav files and listened to but not decoded when opened by using the file menu. Stored examples can be decoded.
>> 
>> Measured latency values cluster around 1000  usec, (is this too long?) with occasional peaks well above 5000 usec. but the times between spikes are much longer than, for instance, the duration of a FT4 or FT8 received transmission. On FT8 these spikes I believe are responsible for the occasional "0 decode" count. Repeated cycling between STOP and MONITOR or Powering off and restarting / rebooting the PC have no affect.
>> 
>> Repeatedly closing and opening WSJT-X has no affect. CPU usage, according to Task Manager, varies around 5%.
>> 
>> USB ports are not put to sleep.
>> 
>> The cause or causes appears to be independent of computer OS, hardware or WSJT-X version.  That this failure happens to so many people seems significant.  Is there a single cause or many? What can we do collectively to help fix this! Can the WSJT-X programmers add temporary hooks in the software to flag where the failure(s) occurs?
>> 
>> 73,
>> 
>> Ed W2GHD
> 
> Hi Ed,
> 
> if you check the "Menu->Save->Save all" option then pick a good example of a non-decode period and send us the saved .WAV file for analysis please?
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> 

Two quick questions. One, are colors band specific? Two, is there any toggle that will let you see the state and not just USA. Ok, maybe one more question: Anything I'm not finding that will highlight needed states, like in JAlert? JAlert still makes me search all the CQs on WSJT-X to find a highlighted needed state. Thank you.