The PS/2 and/or FH-2 keypads attached to microHAM devices can not
be used to send commands to the operating system/computer. They
are strictly for controlling features of the microHAM interface
(e.g., motorized antenna controls or internal CW keyer messages)
of of microHAM USB Device Router (e.g., selecting operating mode
or Router's Digital Voice Keyer).

The status of the PS/2 and/or FH-2 keypads are not reported to any
application software on the "control" channel.

73,

... Joe, W4TV

Thank you Dave, I appreciate the quick response.
Guy

+ AA6YQ comments below

I worked for a while with MRP40 and the gateway to Winwarbler That works well in my opinion.
Now I run MRP40-SDR on the same PC as MRP40 only works that the MRP-DXKeeper gateway does not work so my question is does someone have the MRP-DXKeeper gateway running together with winwarbler?
if I start the MRP40 and the MRP-DXKeeper gateway is working properly I close everything and then start the MRP40-SDR together with MRP-DXKeeper gateway say the MRP-DXKeeper gateway MRP status not responding Winwarbler Connect

+ Are you saying that WinWarbler interoperates with MRP40 correctly through the MRP-DXKeeper gateway, but does not interoperate correctly with MRP40-SDR ?

+ If so, what version of MRP40-SDR are you using?

73,

Dave, AA6YQ

+ AA6YQ comments below

It would be really cool to be able to map the F key macros in Winwarbler to other keys like the number keys on a MicroHam PS-2 keypad or something similar. I know Commander also uses F keys so it may not be doable or maybe only for the F keys not used by Commander. Thoughts?

+ A user-defined command sequence in Commander can be invoked with a function key and can send directives to a capable microHam device via the SO2R command. See the description of the <SO2R text> command in

<https://www.dxlabsuite.com/commander/Help/CommandSequences.htm>

+ A WinWarbler macro can also be invoked with a function key and can direct Commander to execute a user-defined command sequence. See the description of the <xcvrsequence: sequence> command in

<https://www.dxlabsuite.com/winwarbler/Help/Macros.htm>

73,

Dave, AA6YQ

+ AA6YQ comments below

I recently moved DXLab to a new computer with W10. Everything works fine except trying to upload to LOTW where I get the following error message:Invalid PROP_MODE (INTERNET) on line 11. I corrected the error in the affected QSO's and the upload would work OK. It seems to happen on DX Q's but not on ADI imported QSO's from contests (N1MM).I think my settings are OK. How can I prevent this from happening?

+ In the next version of DXKeeper, executing the "Add Requested" function with the "QSL Via" panel set to LoTW will ignore QSOs whose "propagation mode" is set to a value other than AUE, AUR, BS, EME, ES, F2, FAI, ION, MS, RS, SAT, TEP, or TR. Release of this next version is imminent.

73,

Dave, AA6YQ

+ AA6YQ comments below

Dug through the documents, but could not explicitly find how to do something

I wish to change the modes shown in the Progress window of DXView, did I miss it in the documentation, is there a way?

+ At present, DXLab's realtime award tracking for DXCC awards includes award tracking for the PSK mode, even though the DXCC award family does not include a pSK award; PSK QSOs count towards DXCC digital awards, along with RTTY, Olivia, JT65, and FT8 QSOs. I provided the realtime PSK progress tracking because when I first began making DXLab publicly available in 2001, Peter G3PLX had just made PSK31 available and I wished to encourage DXers to experiment with it.

+ My plan is to extend DXLab to enable a user to replace PSK with a digital mode of his or her choosing, though I will begin with the objective of enabling a user to specify 4 digital modes whose DXCC progress DXLab should track. This is not imminent.

73,

Dave, AA6YQ

+ AA6YQ comments below

I believe this is a futile quest, but just in case somebody has a solution...

Am looking for a way to pause execution of a Commander command sequence. The sequence below is what I'm looking for, but of course, it doesn't work because once the ASCII command string is sent to the K3, the Commander sequence proceeds without "concern" for the K3.

+ What does "without concern for the K3" mean?

At least that's my understanding. And, the command sequence command <WAIT> waits only for the Commander "command interval." I want the LED to be red while sending the KYW message, and then turn black. Right now I have it toggling, but have to strike the FKEY twice (not the sequence shown here). Anybody have a trick or work-around?

<led red>
'KS035;KYWDXLAB;KS025;
<wait>
<led black>
<end>

+ User defined command sequences send commands to your transceiver. They are not capable of reading, interpreting, and acting upon your transceiver's state. Doing so would require extending command sequences to become a fully functional programming language, and all that entails. If Commander were so extended, you'd have to continuously send KS commands to the radio until you received a response of KS025, at which point you would execute the <led black> command. In parallel, Commander would be querying the radio for its frequency, mode, shift, S-meter, etc.

+ Note that if you have WinWarbler running and configured to transmit CW via Commander, the WPM selector on the "CW Transmit" panel will display your K3's current CW speed.

73,

Dave, AA6YQ

+ AA6YQ comments below

Dave- for the benefit of others - I did notice in Windows 10 sound settings - Playback - if you don't have your PC speakers disabled - you again get no RF out on SSDR and the 6600. So as it says in the write up in the wiki section, you just have to go back and re-enable the speakers when done with WinWabler

+ In what section of the Wiki did you find the reference to re-enabling speakers?

73,

Dave, AA6YQ

LotW does not recognize non amateur QSOs (that it any QSO not made
via RF propagation).

73,

... Joe, W4TV

is there a way?

Not at the present time.


73,

... Joe, W4TV


On 2018-11-20 1:01 PM, w7psk wrote:

Dug through the documents, but could not explicitly find how to do something
I wish to change the modes shown in the Progress window of DXView, did I miss
it in the documentation, is there a way?
Scotty W7PSK

It would be really cool to be able to map the F key macros in Winwarbler to other keys like the number keys on a MicroHam PS-2 keypad or something similar. I know Commander also uses F keys so it may not be doable or maybe only for the F keys not used by Commander. Thoughts?

Happy Thanksgiving es 73

Dale AA1QD

Dug through the documents, but could not explicitly find how to do something

I wish to change the modes shown in the Progress window of DXView, did I miss
it in the documentation, is there a way?

Scotty W7PSK

I believe this is a futile quest, but just in case somebody has a solution...

Am looking for a way to pause execution of a Commander command sequence. The sequence below is what I'm looking for, but of course, it doesn't work because once the ASCII command string is sent to the K3, the Commander sequence proceeds without "concern" for the K3. At least that's my understanding. And, the command sequence command <WAIT> waits only for the Commander "command interval." I want the LED to be red while sending the KYW message, and then turn black. Right now I have it toggling, but have to strike the FKEY twice (not the sequence shown here). Anybody have a trick or work-around? -John AC4CA

<led red>
'KS035;KYWDXLAB;KS025;
<wait>
<led black>
<end>

Dave- for the benefit of others - I did notice  in Windows 10 sound settings - Playback - if you don't have your PC speakers disabled - you again get no RF out on SSDR and the 6600. So as it says in the  write up in the wiki section, you just have to go back and re-enable the speakers when done with WinWabler

73
Paul

Dave thanks for the link. Went thru each section and made a few changes. Not sure exactly what the key change was, but the problem is fixed and I am now transmitting in Winwabler PSK with the 6600.

Thank You & 73
Paul
w2eck

I recently moved DXLab to a new computer with W10. Everything works fine except trying to upload to LOTW where I get the following error message:Invalid  PROP_MODE (INTERNET) on line 11. I corrected the error in the affected QSO's and the upload would work OK. It seems to happen on DX Q's but not on ADI imported QSO's from contests (N1MM).I think my settings are OK.  How can I prevent this from happening?
Guy
VE2BWL

+ AA6YQ comments below

On Tue, Nov 20, 2018 at 06:13 AM, w2eck wrote:

New Flex 6600 user, have used DXLab for some time. Having trouble getting Winwabler to cause the 6600 to Tx in PSK31. Using Winwabler 9.1.5, Commander 13.7.9, SSDR 2.4.9. Commander does follow the 6600 frequency. When Winwabler goes to Tx, the Red TX indicator in SSDR lights up as does the power button on the 6600, but there is no indication of RF power out or any movement in the SWR meter in SSDR. The PTT suppress button in Commander- Config-General is unchecked. I am using DAX Audio RX 1 for recieive and DAX Audio TX 1 for transmit. Any hints on where to look to fix this issue.

+ See the "DAX Configuration" and "PSK Configuration and Operation" sections of

<https://www.dxlabsuite.com/dxlabwiki/FlexSignature>

      73,

             Dave, AA6YQ