This is the info that came up after the upload of the many qsos I referred to: TQSL Version 2.5.1 [v2.5.1] Signing using Callsign N0AN, DXCC Entity UNITED STATES OF AMERICA Error: Invalid amateur CALL

Dave, did #1 Got a VERY large list of potential uploads...I mean hundreds and hundreds. I told it to upload them to LoTW and it seemed to work. Then ran that same sequence again and the same qsos show

Thanks Dave, will study. Hasan

I have had this happen twice in the last 3 days: I am set for auto-upload to LoTW. LoTW on their end went down Error msg in DXK asking try again or not? I say yes, and it does same (as they were down

Yep, I agree, it would have to be done in a very judicious manner and probably not worth the effort. If Laurie gets v3 of JTA working with shared UDP, then we will have what we want. In the mean time,

Hi DAve, I recall that, but I was confused by this comment: + SpotCollector does not provide a way to automatically route the information it collects to a DX Cluster. You can of course generate outgoi

When I'm running WSJT-X connected to SpotCollector, I see all my decoded stations on FT8 show up in SpotCollector with a Network of WSJTX, which makes sense. My question: are these locally generated s

To Simplify: I have separate WSJT-X configurations for each mode: If I change my WSJT-X configuration from MSK144 to FT8, everything decoded in X shows up in SpotCollector with network WSJTX As soon a

Now that I have WSJT-X directly directly connected to SpotCollector and it is working. I want my Band Activity Calls (while monitoring 6 meter MSK144 with WSJT-X) to automatically be uploaded to N6WS.

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

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

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 t

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,

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

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 clic

this is a *.png of the error message I'm getting. https://drive.google.com/open?id=1XowhcJQy3mF7XCdUgvn51Z12o1_aayPo Dave, (or anyone), please see this link to my google drive. It has a picture of the

Tnx Dave, very informative. Hard to get used to a new way of thinking. I have gone to the PropView approach. Much more powerful ...and I have been searching/reading as much as I can, but the docs are

Call: VP8SJ Filter: Band and Origin and Call=VP8PJ Band Filter: All HF (and a few select others 6m) Origin Filter: NA-E NA-M and NA-W Why are spots from: EA3AGQ F4HAU Showing up in the SpotCollector T

Bill, Thanks! That was it. I assume I leave WSJT-X Enable unchecked in SpotCollector Config? Now if I can just get an audio alert from SpotCollector whenever VP8PJ is spotted from North America on any

Forest for the Trees Problem I'm using WSJT-X . I do not want it's decoded stations as spot sources for the Spot Collector Display. I only want to see spots sourced from N6WS I have gone into : SpotCo