Odd Propview Behavior with WSJT-X


Hasan Schiers N0AN
 

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?
Hasan


Dave AA6YQ
 

+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

73,

Dave, AA6YQ


Hasan Schiers N0AN
 

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.
Tnx, 73
Hasan


On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

        73,

                Dave, AA6YQ






Dave AA6YQ
 

* more AA6YQ comments below

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.

* As you point out below, selecting a new callsign in WSJT-X prepares PropView to generate a forecast; you must then click a PropView button to initiate either a short-path or a long-path forecast.

73,

Dave, AA6YQ

On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:


+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

73,

Dave, AA6YQ


Hasan Schiers N0AN
 

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

Trying again:
ZB2IF :
X populates
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
KC1LWH: Failed
...several successes...
K0IEA: Failed
CT1EHX: Failed
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)

73, N0AN
Hasan


On Fri, Feb 28, 2020 at 9:38 AM Dave AA6YQ <aa6yq@...> wrote:
* more AA6YQ comments below

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.

* As you point out below, selecting a new callsign in WSJT-X prepares PropView to generate a forecast; you must then click a PropView button to initiate either a short-path or a long-path forecast.

       73,

               Dave, AA6YQ
On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@...> wrote:


        + AA6YQ comments below

        When I double-click on a station in WSJT-X to begin calling them:

        Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

        Is this normal behavior?

        + Yes.

                73,

                        Dave, AA6YQ






Dave AA6YQ
 

+ AA6YQ comments below

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. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+ In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Hasan Schiers N0AN
 

Dave,.
 I will experiment. I sent you a reply with new info.
I found a way to make things work, but it requires JTAlert.
That works every time. Please read that message and let me know if you want me to *undo* my JTAlert setting, and retry the settings in your current message and create a dump file.

73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

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. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ













Hasan Schiers N0AN
 

I tried two different double-clicks and no change happened in DXView
73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

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. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ













Hasan Schiers N0AN
 

Sent to wrong place, resent to you directly with attachments
Hasan


On Fri, Feb 28, 2020 at 1:10 PM Hasan Schiers N0AN via Groups.Io <hbasri.schiers6=gmail.com@groups.io> wrote:
I tried two different double-clicks and no change happened in DXView
73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

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. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ