Re: Odd Propview Behavior with WSJT-X


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

Join DXLab@groups.io to automatically receive all group messages.