Date   
Re: WinKeyer + WinWarbler = No WinKey Message Buttons

Gilbert Baron W0MN
 

It is true. Buttons are not available when connected to a PC. I think it is a huge lack of function myself although I would likely use the macros 99% of the time it would be nice to have this available. It is on MFJ-464.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 12, 2017 18:05
To: DXLab
Subject: Re: [dxlab] WinKeyer + WinWarbler = No WinKey Message Buttons

 

 

Roger Ian.  I just sent a similar email.  My bad.  I was not aware also that the newer version of WnKeyer will alllow buttons in host mode.  That would be a nice feature in WinWarbler.


-----------------
73,

Tom - KQ5S

 

On Sun, Nov 12, 2017 at 6:02 PM, iain macdonnell - N6ML ar@... [dxlab] <dxlab@...> wrote:

 

That's not really accurate. There is no Windows involvement in
standalone operation of a WinKeyer. You can completely disconnect it
from the PC and run it standalone. Traditionally the WinKeyer operates
in on of two modes - standalone or host - see page 3 of:

http://k1el.tripod.com/files/WK3_Datasheet_v1.2.pdf

According to the next page of that document, it is actually possible,
as of version 2.0, to enable the buttons while in host mode, but
WinWarbler would need to send the prescribed Mode command.

I imagine that most WinWarbler users would utilise WinWarbler macros
instead of the WK buttons, so maybe this feature has not been
requested/justified....

73,

~iain / N6ML

On Sun, Nov 12, 2017 at 3:27 PM, Tom-KQ5S kq5stom@... [dxlab]
<dxlab@...> wrote:
>
>
>
> This is because you have WinWarbler set to use the WinKeyer and assigned the WinKeyer comport to WinWarbler. WinWarbler then takes over the comport that the WinKeyer is attached to. The WinKeyer (Windows) can not share the comport hence the buttons do not work while WinWarbler has control.
>
> -----------------
> 73,
> Tom - KQ5S
>
> On Sun, Nov 12, 2017 at 4:51 PM, kevin@... [dxlab] <dxlab@...> wrote:
>>
>>
>>
>> I have a WinKeyer USB 3.0. I've set up a few messages on the top buttons. They seem to work just fine when standalone but once I start WinWarbler the top buttons no longer function. Quit WW and the message buttons are working again.
>>
>>
>> Is this by design or maybe a setting I'm missing?
>>
>>
>> 73,
>>
>> Kev K4VD
>
>
>

 

Re: DXKeeper: Want to remove log page filter after logging a QSO wit

Tom N4NW
 

Same situation here with my setup. Seems the "Clear DXKeeper CallsSign Filter after logging QSO is not working, no matter what is checked.

Tom, N4NW

Thu Nov 9, 2017 8:07 am (PST) . Posted by:


"John Pelham" w1ja

Thanks Laurie. Your suggestion does what I asked. But what I asked for was incomplete.

Ideally when calling or working a station I'd like to see DXCC statistics for the entity and previous QSOs with the callsign. This means the callsign must be sent to both DXView and DXKeeper. I tried many combinations of the 'DXKeeper' and 'Pathfinder option checkboxes in 'Settings > Applications > DXLab Suite', and nothing worked to give me the statistics and the previous QSOs, and clearing the DXKeeper callsign filter after the end of the QSO. It appears that if DXKeeper performs a callsign lookup, the callsign filter isn't cleared after logging the QSO even though the 'Clear DXKeeper Callsign Filter after Logging QSO' checkbox is checked.

Is there a way around this issue?

73,
John, W1JA

Re: DXKeeper: Want to remove log page filter after logging a QSO wit

Tom N4NW
 

Laurie,

Like John, I am experiencing the same problem with the filter not being cleared. Also like John, I do not use Capture to log the QSO but wait for the log QSO windo to pop-up in WSJT-x znc click OK. In a second JTAlert advises the call has been logged, then drops off screen.

Using you latest settings suggested the ASO file is NOT cleared in DXK.

73's
Tom, N4NW


John,

I only asked about using the Capture window because there have been
users in the past that insisted in using the Capture and complained that
JTAlert was out-of-sync when reporting B4s and other anomalous
behaviour. You can ignore my Capture query.

Rather than set the single JTAlert "DXKeeper/DXView/PathFinder Lookup on
a new DX Call" option, there are individual options for DXKeeper, DXView
and PathFinder to perform their respective lookups. Just enable the
"DXView Lookup on new DX Call" setting.

de Laurie VK3AMA

Re: Progress data wrong after edit qso

Dave AA6YQ
 

*** More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 10:39 AM
To: dxlab
Subject: Re: [dxlab] Progress data wrong after edit qso


You changed a QSO's DXCC DXCC entity from "Norfolk Island" to "Australia". Having the "Automatically recompute realtime award tracking" box checked caused DXKeeper to automatically recompute the progress for "Norfolk Island", but it will not automatically recompute the progress for Australia. When you change a logged QSO's DXCC entity, you must invoke the Recompute function.
Is there any reason it couldn't automatically recompute both? Aside from the user needing to know to do it, the down-side is that (AFAIK) there's no way for a user to invoke recompute for a single entity, so they'd have to do a full recompute (entire log) which can take some time....

*** My statement above is incorrect; DXKeeper does recompute the progress both the old and new DXCC entities. The defect is that DXView's progress display is not immediately updated. I am investigating...

73,

Dave, AA6YQ

Re: LOTW

Jeff WB9DAR
 

Dave & Ian
Thanks you for your input. Mission accomplished. 
My LoTW log is now in DXKeeper and backed up. 
Much appreciated. 
Jeff WB9DAR


Sent by Jeff

On Nov 13, 2017, at 8:55 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 7:28 PM
To: dxlab@...
Subject: Re: [dxlab] LOTW

Thanks for getting back to me. Let me be a little clearer. I have no QSOs in dxkeeper. I have no other sources of my previous logs other than LoTW.

>>>What did you use to record your QSOs in order to be able to submit them to LoTW?

I want to populate (Import) dxkeeper with the QSOs in LoTW. After I populate the QSOs from LoTW I can then back them up on disk etc. I just need to how to import them into dxkeeper from LoTW. I hope that helps.

>>>It does. I see that Ian N6ML has already pointed you at the instructions for accomplishing your objective. You can leave "duplicate checking" disabled, as you have no QSOs in your log.

73,

Dave, AA6YQ

Re: LOTW

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 7:28 PM
To: dxlab@...
Subject: Re: [dxlab] LOTW

Thanks for getting back to me. Let me be a little clearer. I have no QSOs in dxkeeper. I have no other sources of my previous logs other than LoTW.

What did you use to record your QSOs in order to be able to submit them to LoTW?
I want to populate (Import) dxkeeper with the QSOs in LoTW. After I populate the QSOs from LoTW I can then back them up on disk etc. I just need to how to import them into dxkeeper from LoTW. I hope that helps.

It does. I see that Ian N6ML has already pointed you at the instructions for accomplishing your objective. You can leave "duplicate checking" disabled, as you have no QSOs in your log.
73,

Dave, AA6YQ

Re: LOTW

iain macdonnell - N6ML
 

Hi Jeff,

See: http://www.dxlabsuite.com/dxlabwiki/LotWRecoveringLostQSOs

This is generally not recommended, but if it's the only log you have...........

73,

~iain / N6ML



On Mon, Nov 13, 2017 at 4:28 PM, jeff5544@... [dxlab]
<dxlab@...> wrote:



Dave

Thanks for getting back to me. Let me be a little clearer. I have no QSOs in dxkeeper. I have no other sources of my previous logs other than LoTW. I want to populate (Import) dxkeeper with the QSOs in LoTW. After I populate the QSOs from LoTW I can then back them up on disk etc. I just need to how to import them into dxkeeper from LoTW. I hope that helps.
Thanks
Jeff WB9DAR


Sent by Jeff

On Nov 13, 2017, at 4:00 PM, 'Dave AA6YQ' @AA6YQ [dxlab] <dxlab@...> wrote:



AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 4:51 PM
To: dxlab@...
Subject: [dxlab] LOTW

I successfully installed my LoTW certificate. What I�m trying to do is import into dxkeeper log QSOs that are already in LoTW.

Why would you want to do that? Aren't your QSOs already present in your DXKeeper log?
If your goal is to update your logged QSOs to reflect their acceptance and confirmation by LoTW, then "Import" is not the appropriate operation. "Import" means "Add additional QSOs to what's already present". "Importing" QSOs from LoTW to DXKeeper would create duplicate QSOs. The right way to accomplish this goal is to read this topic:
<http://www.dxlabsuite.com/dxlabwiki/QSOsAlreadyUploadedLotW>

If your DXKeeper log is empty, and your goal is to populate it with QSOs imported from LoTW, then my question is "don't you have a better source of your QSOs than LoTW"? LoTW retains only a small amount of information about each QSO -- callsign, date, time, frequency, band, mode, station callsign, propagation mode. It doesn't know your QSO partner's name or address, signal reports, QSL card status, etc. For "recovering" lost QSOs, LoTW is the court of last resort.
73,

Dave, AA6YQ

Re: LOTW

Jeff WB9DAR
 

Dave
Thanks for getting back to me. Let me be a little clearer. I have no QSOs in dxkeeper. I have no other sources of my previous logs other than LoTW. I want to populate (Import) dxkeeper with the QSOs in LoTW. After I populate the QSOs from LoTW I can then back them up on disk etc.  I just need to how to import them into dxkeeper from LoTW. I hope that helps. 
Thanks
Jeff WB9DAR


Sent by Jeff

On Nov 13, 2017, at 4:00 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 4:51 PM
To: dxlab@...
Subject: [dxlab] LOTW

I successfully installed my LoTW certificate. What I�m trying to do is import into dxkeeper log QSOs that are already in LoTW.

>>>Why would you want to do that? Aren't your QSOs already present in your DXKeeper log?

>>>If your goal is to update your logged QSOs to reflect their acceptance and confirmation by LoTW, then "Import" is not the appropriate operation. "Import" means "Add additional QSOs to what's already present". "Importing" QSOs from LoTW to DXKeeper would create duplicate QSOs. The right way to accomplish this goal is to read this topic:

<http://www.dxlabsuite.com/dxlabwiki/QSOsAlreadyUploadedLotW>

>>>If your DXKeeper log is empty, and your goal is to populate it with QSOs imported from LoTW, then my question is "don't you have a better source of your QSOs than LoTW"? LoTW retains only a small amount of information about each QSO -- callsign, date, time, frequency, band, mode, station callsign, propagation mode. It doesn't know your QSO partner's name or address, signal reports, QSL card status, etc. For "recovering" lost QSOs, LoTW is the court of last resort.

73,

Dave, AA6YQ

Re: RTTY Receive WW Soundcard

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 8:30 AM
To: DXLab forum
Subject: Re: [dxlab] RTTY Receive WW Soundcard

This is by design. I have found Winwarbler's waterfall much more sensitive on RTTY than PSK. With the Windows mixer at mid scale I have to set my IC-7300 USB Audio level to 1-2% to get a good looking waterfall.

My IC-7300's "ACC/USB AF Output Level" menu item is set to 33%, as suggested in
<http://www.dxlabsuite.com/dxlabwiki/ConnectingIcom72007600>

In Windows 7, the Levels tab on the "Microphone Properties" window is set to 100%
On WinWarbler's Configuration window, the PSK tab's "Waterfall gain" is set to 6", and the RTTY tab's "Tuning Display gain" is set to 2". This yield equivalent Waterfall densities when operating in PSK or RTTY.
73,

Dave, AA6YQ

Re: LOTW

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 4:51 PM
To: dxlab@...
Subject: [dxlab] LOTW

I successfully installed my LoTW certificate. What I�m trying to do is import into dxkeeper log QSOs that are already in LoTW.

Why would you want to do that? Aren't your QSOs already present in your DXKeeper log?
If your goal is to update your logged QSOs to reflect their acceptance and confirmation by LoTW, then "Import" is not the appropriate operation. "Import" means "Add additional QSOs to what's already present". "Importing" QSOs from LoTW to DXKeeper would create duplicate QSOs. The right way to accomplish this goal is to read this topic:
<http://www.dxlabsuite.com/dxlabwiki/QSOsAlreadyUploadedLotW>

If your DXKeeper log is empty, and your goal is to populate it with QSOs imported from LoTW, then my question is "don't you have a better source of your QSOs than LoTW"? LoTW retains only a small amount of information about each QSO -- callsign, date, time, frequency, band, mode, station callsign, propagation mode. It doesn't know your QSO partner's name or address, signal reports, QSL card status, etc. For "recovering" lost QSOs, LoTW is the court of last resort.
73,

Dave, AA6YQ

Re: SpotCollector

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 4:41 PM
To: dxlab@...
Subject: [dxlab] SpotCollector


After moving DXlabs to a different computer have not been able to get SpotCollector working.

The following comes up. Have VE7CC set for the spot source.

Winsock Error # 11001 - Authoritative answer: Host not found @ 11/13/2017 2136

Either you’ve specified an incorrect host address and/or port number for VE7CC, or you haven't configured your firewall or anti-malware applications to consider SpotCollector to be "safe".
73,

Dave, AA6YQ

LOTW

Jeff WB9DAR
 

Hi all
I successfully installed my LoTW certificate. What I’m trying to do is import into dxkeeper log QSOs that are already in LoTW. I ALSO configured dxkeeper according to the documentation. When I importth I get a list of QSOs downloaded to notepad. I think it’s a simple fix and have gone thru the documentation to no avail. If you could pleas help it would be much appreciated.
Thanks
Jeff WB9DAR

SpotCollector

n7bv@...
 

After moving DXlabs to a different computer have not been able to get SpotCollector working.

The following comes up.  Have VE7CC set for the spot source.

Winsock Error # 11001 - Authoritative answer: Host not found @ 11/13/2017 2136


N1mm works correctly.


Tks, 73, Chuck N7BV

Re: Progress data wrong after edit qso

iain macdonnell - N6ML
 

On Sun, Nov 12, 2017 at 10:28 PM, 'Dave AA6YQ' @AA6YQ
[dxlab] <dxlab@...> wrote:



+++ more AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 12:31 AM
To: dxlab@...
Subject: RE: [dxlab] Progress data wrong after edit qso

Dave

Did DXKeeper automatically recompute award progress after you changed the QSO's DXCC prefix?
Yes
I replayed the whole sequence and the recompute-popup comes up.

After that the DXV-progress table is wrong

+++As described in

<http://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Awards Tab>

" The Automatically recompute realtime award tracking checkbox determines whether DXKeeper will automatically update realtime award tracking information when you delete a QSO or indicate a regression in the QSO's progress, e.g. demoting its status from confirmed to worked, or from worked to unworked. If this box is unchecked, DXKeeper will not direct SpotCollector to initiate progress recomputations."

You changed a QSO's DXCC DXCC entity from "Norfolk Island" to "Australia". Having the "Automatically recompute realtime award tracking" box checked caused DXKeeper to automatically recompute the progress for "Norfolk Island", but it will not automatically recompute the progress for Australia. When you change a logged QSO's DXCC entity, you must invoke the Recompute function.
Is there any reason it couldn't automatically recompute both? Aside
from the user needing to know to do it, the down-side is that (AFAIK)
there's no way for a user to invoke recompute for a single entity, so
they'd have to do a full recompute (entire log) which can take some
time....

73,

~iain / N6ML

Re: RTTY Receive WW Soundcard

Björn Ekelund, SM7IUN
 

This is by design. I have found Winwarbler's waterfall much more sensitive on RTTY than PSK. With the Windows mixer
at mid scale I have to set my IC-7300 USB Audio level to 1-2% to get a good looking waterfall. 

73,

Björn SM7IUN

2017-11-12 23:26 GMT+01:00 'Gilbert Baron' w0mn00@... [dxlab] <dxlab@...>:

 

Thanks. It was set a bit high but the real problem was that I was not tuning an RTTY signal. Been so long I forgot how it sounded. Waterfall is more sensitive on RTTY than PSK so I set it a bit lower (1) but I think I should adjust the Signalink so that I can use a bit higher setting on GAIN without overload at such a low level. Thanks a lot and it is decoding RTTY now. I have also set COM to none as Signalink does the PTT.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 12, 2017 15:48
To: dxlab@...
Subject: RE: [dxlab] RTTY Receive WW Soundcard

 

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 12, 2017 4:14 PM
To: dxlab@...
Subject: [dxlab] RTTY Receive WW Soundcard

I am using Signalink USB soundcard. I went through the setup from the documentation but maybe I missed something.

Transmit seems to work, I get the Warble that sounds like RTTY has always sounded to me. On receive the waterfall is White nearly
the full width of the screen plus at times two Stripes close together and if I select that area the Squelch goes beyond the squelch
line looking like I am getting data. It is wider than a PSK display and may actually be RTTY but I get nothing or I get random
characters. It is of course possible that there is no RTTY on the air but it sounds like it. The White waterfall nearly the screen
width is confusing. What might I be missing here?

>>>A white waterfall implies that the signal level from the radio is too high. See

<http://www.dxlabsuite.com/dxlabwiki/SettingRTTYAudioInputLevelV78Ten>

73,

Dave, AA6YQ


Re: Progress data wrong after edit qso

Dave AA6YQ
 

+++ more AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 12:31 AM
To: dxlab@...
Subject: RE: [dxlab] Progress data wrong after edit qso

Dave

Did DXKeeper automatically recompute award progress after you changed the QSO's DXCC prefix?
Yes
I replayed the whole sequence and the recompute-popup comes up.

After that the DXV-progress table is wrong

+++As described in

<http://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Awards Tab>

" The Automatically recompute realtime award tracking checkbox determines whether DXKeeper will automatically update realtime award tracking information when you delete a QSO or indicate a regression in the QSO's progress, e.g. demoting its status from confirmed to worked, or from worked to unworked. If this box is unchecked, DXKeeper will not direct SpotCollector to initiate progress recomputations."

You changed a QSO's DXCC DXCC entity from "Norfolk Island" to "Australia". Having the "Automatically recompute realtime award tracking" box checked caused DXKeeper to automatically recompute the progress for "Norfolk Island", but it will not automatically recompute the progress for Australia. When you change a logged QSO's DXCC entity, you must invoke the Recompute function.
73,

Dave, AA6YQ

Re: Progress data wrong after edit qso

aart wedemeijer PA3C
 

Dave

>>>Did DXKeeper automatically recompute award progress after you changed the QSO's DXCC prefix?

Yes
I replayed the whole sequence and the recompute-popup comes up.
After that the DXV-progress table is wrong (link)

73

Aart
I'll send the errorlog direct



 

Re: WinKeyer + WinWarbler = No WinKey Message Buttons

Gilbert Baron W0MN
 

The MFJ464 by MSJ buttons do work while connected to the computer. They work on DXLABS. The buttons (as they should be) are independent of being connected to a computer application. I hope my USB version which arrives tomorrow does not have that problem. I will be unhappy and would have to connect my 464 in parallel to use its buttons instead or just depend on the macros.

 

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 12, 2017 19:07
To: dxlab@...
Subject: Re: [dxlab] WinKeyer + WinWarbler = No WinKey Message Buttons

 

 


> Is this by design or maybe a setting I'm missing?

The WinKey "top buttons" do not work in "Host mode" (when connected to
a computer). That is by design. The computer control software (e.g.,
WinWarbler) *could* implement support for those buttons but the software
has to be programmed specifically to *read the key press* and *send the*
*appropriate command back to the WinKey chip*.

I do not know of *any* logging software that includes support for the
WinKey "buttons" as most software has separate macro capabilities.

73,

... Joe, W4TV

On 11/12/2017 5:51 PM, kevin@... [dxlab] wrote:
> I have a WinKeyer USB 3.0. I've set up a few messages on the top buttons. They seem to work just fine when standalone but once I start WinWarbler the top buttons no longer function. Quit WW and the message buttons are working again.
>
>
> Is this by design or maybe a setting I'm missing?
>
>
> 73,
> Kev K4VD
>

Re: WinKeyer + WinWarbler = No WinKey Message Buttons

Joe Subich, W4TV
 

Is this by design or maybe a setting I'm missing?
The WinKey "top buttons" do not work in "Host mode" (when connected to
a computer). That is by design. The computer control software (e.g.,
WinWarbler) *could* implement support for those buttons but the software
has to be programmed specifically to *read the key press* and *send the*
*appropriate command back to the WinKey chip*.

I do not know of *any* logging software that includes support for the
WinKey "buttons" as most software has separate macro capabilities.

73,

... Joe, W4TV


On 11/12/2017 5:51 PM, kevin@... [dxlab] wrote:
I have a WinKeyer USB 3.0. I've set up a few messages on the top buttons. They seem to work just fine when standalone but once I start WinWarbler the top buttons no longer function. Quit WW and the message buttons are working again.
Is this by design or maybe a setting I'm missing?
73,
Kev K4VD

Re: WinKeyer + WinWarbler = No WinKey Message Buttons

Tom-KQ5S <kq5stom@...>
 

Roger Ian.  I just sent a similar email.  My bad.  I was not aware also that the newer version of WnKeyer will alllow buttons in host mode.  That would be a nice feature in WinWarbler.

-----------------
73,
Tom - KQ5S

On Sun, Nov 12, 2017 at 6:02 PM, iain macdonnell - N6ML ar@... [dxlab] <dxlab@...> wrote:
 

That's not really accurate. There is no Windows involvement in
standalone operation of a WinKeyer. You can completely disconnect it
from the PC and run it standalone. Traditionally the WinKeyer operates
in on of two modes - standalone or host - see page 3 of:

http://k1el.tripod.com/files/WK3_Datasheet_v1.2.pdf

According to the next page of that document, it is actually possible,
as of version 2.0, to enable the buttons while in host mode, but
WinWarbler would need to send the prescribed Mode command.

I imagine that most WinWarbler users would utilise WinWarbler macros
instead of the WK buttons, so maybe this feature has not been
requested/justified....

73,

~iain / N6ML

On Sun, Nov 12, 2017 at 3:27 PM, Tom-KQ5S kq5stom@... [dxlab]
<dxlab@...> wrote:
>
>
>
> This is because you have WinWarbler set to use the WinKeyer and assigned the WinKeyer comport to WinWarbler. WinWarbler then takes over the comport that the WinKeyer is attached to. The WinKeyer (Windows) can not share the comport hence the buttons do not work while WinWarbler has control.
>
> -----------------
> 73,
> Tom - KQ5S
>
> On Sun, Nov 12, 2017 at 4:51 PM, kevin@... [dxlab] <dxlab@...> wrote:
>>
>>
>>
>> I have a WinKeyer USB 3.0. I've set up a few messages on the top buttons. They seem to work just fine when standalone but once I start WinWarbler the top buttons no longer function. Quit WW and the message buttons are working again.
>>
>>
>> Is this by design or maybe a setting I'm missing?
>>
>>
>> 73,
>>
>> Kev K4VD
>
>
>