Re: Odd Propview Behavior with WSJT-X
Hasan Schiers N0AN
toggle quoted messageShow quoted text
All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%
Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. I have checked DXV config and "Generate Propagation Forecast" is checked. I have rebooted.
I was running the checks below because of the intermittent performance of DXView and now I'm quite stuck. If we get this working, then what follows is relevant.
BTW, Dave, it does not pick it up reliably. I frequently have to try multiple times of clicking (in X) on a station before Propview picks it up and then hit the SP button. There is often a substantial delay (up to 10 seconds) after double clicking on a call in WSJT-X , before it is picked up by DXView and ultimately fed to Propview, so I can hit the PropView SP button and get a prediction.
I do have all of DXLabs folder excluded from Virus Detection. No MalWare Bytes installed.
For testing: I have the following windows so I can see them:
WSJT-X (referred to as X); JTAlert is running but mimimized
DXView (no map)
Propview (parameter tab, so I can see if it has gotten new DX call from X
Now: double click on callsign:
X populates for calling EA5RT (in TX1 - TX5)
DXView did NOT accept the new call. Sitting on W1YRC where it was
Propview: Still shows United States in Parm Tab
4 sec later, DXView populates
Propview populates as soon as DXview populated
Propview executes proper Prediction upon hitting SP button.
Another try: (only watching DXV to see if it populates)
I6RGQ: 6 seconds to populate DXView
EB3RT: 6 sec
EA4DB: Failed to populate, stayed with EB3RT
CO7MLS: 6 sec
WO1X: Failed to populate
NP4BM: 5 sec
YO9HP: 6 sec
So, X always populates. DXView does not....and if DXView doesn't then Propview can't update. (at least that's how it looks to me)
It seems if I double click on a call, very late in the reply cycle, even though it populates X, it does not Populate DXView:
Just tested W0BLE at 10 sec into the seq where I should be tx'ing. it did not "take", but it did show in X TX1 - TX5
At 5 sec it 'took' (by that I mean the call was forwarded successfully to DXV)
At 7 sec it 'took'
Best info I can generate:
The earlier in the reply sequence (immediately after a decode), that I double-click on a call, the more likely it is to populate DXView. It always populates X, no matter how late in the reply sequence I choose to double-click.
Went to 20m (very busy) and now double clicking on X does nothing for DXView. ....and 20m has stopped decoding ...shutting down X, and DXLab, restarting, (not rebooting, that comes next)
Went back to 17m after restarting both programs.
X decodes, DXV doesn't populate. Rebooting.
Now DXView does not populate from WSJT-X double click callsign, no matter what I do. (Go back to top of this message)
On Fri, Feb 28, 2020 at 9:38 AM Dave AA6YQ <aa6yq@...> wrote:
* more AA6YQ comments below