Hi Dave, When I right-click on a Spot Collector spot and ‘Copy to Windows Clipboard’ the resulting string looks like this: VU2MB on 14074.0 in FT8 at 25 1441Z (VU: India) Might it be

You can not limit yourself to WK3. There are significant issues in maintaining backward compatibility with WK 1 and WK 2. Study the documentation on *ALL THREE* versions to understand the full

I'm trying to understand the documentation for WK3 but obviously I'm failing. I'll see if I can find any source code for some programs to try to understand it all better! Thank you for your

+ AA6YQ comments below+ Please review the step-by-step instructions in <https://www.dxlabsuite.com/dxlabwiki/QSOPlottingDXAtlas> + If those don't get you going, let me know. 73,

After installing a Windows 10 update, when I click “plot” in DXKeeper, the only QSO that populates on DXAtlas is the QSO currently selected. In the past, all my QSO’s appeared. I imagine that

Presumably your code is not responding to some command in the way that WinWarbler expects, but WK3demo does not use that particular command (or doesn't care that you're not responding properly). To

+ AA6YQ comments below + That's not correct. If you are emulating a WinKey, you must support the WinKey specification, not just one particular WinKey application. 73, Dave, AA6YQ

Winwarbler sends a close before opening for compatibility with the original WinKeyer IC. The original WinKeyer did not automatically close the serial mode when the serial port was closed. Other than

Yes WinWarbler sends close before as you describe which the WK3 demo does not! What does WinWarbler want after opening that the WK3 demo does not seem to need! My thought is where does it work against

+ AA6YQ comments below I get it when WinWarbler connects for opening and also when closing to WinKey + My question was "From where are you receiving this string?" + What you are reporting doesn't

This works now (<NeedFilter> and <BandFilter> and <ModeFilter> and <ContFilter> and <OriginFilter> and <AgeFilter> and (DXCCPrefix <> 'P5')) OR Tags like '*foc*' Pete, W1RM W1RM@...

1) You should use the "like" operator, not "=" 2) Use of square brackets is not valid 3) Use of "or" is not valid either Replace: [Tags = <foc> or <foc-*>] with: Tags like '*foc*' as I

This expression alone results in an error [Tags = <foc> or <foc-*>] Pete, W1RM W1RM@...

By itself the (tags = <foc> or <foc-*>) works. However, when I add it to this SQL it doesn't (<NeedFilter> and <BandFilter> and <ModeFilter> and <ContFilter> and <OriginFilter> and <AgeFilter>

Using WK III (and WK3 Demo), the only difference between what WinWarbler sends when initializing a WinKeyer and what WK3 Demo sends is that WinWarbler does a Host Close before the Echo Test (00 04 55)

I get it when WinWarbler connects for opening and also when closing to WinKey

Tags like '*xx*' The field is "Tags" and the *'s are important incase more than one tag gets applied to a database entry. 73, ~iain / N6ML

I’m trying to add an expression for tag to a SQL expression that I already have but I can’t find the right syntax. I’ve tried Tag = <xx> and tag like ‘xx’ but neither work. Pete,

+ AA6YQ comments below I use a self-developed client for Elecraft K2. In this I have a winkey server that I have tested against K1EL WKdemo with excellent results. When I try with WinWarbler the

Hey! I use a self-developed client for Elecraft K2. In this I have a winkey server that I have tested against K1EL WKdemo with excellent results. When I try with WinWarbler the opening goes well but I