Date   
Commander and ParData?

Daniel Brown
 

Apologies if this shows up twice - tried to post using the Yahoo
groups interface and didn't see it come through, so I'm resending.


Is there any way for Commander to control pins other than just Data
7-0 or Pin 9-2 on the parallel / LPT port?

Why?

I'm using DXLab Commander with an Elecraft K3 and an Icom AH-4 tuner.
I need to command the radio to send 15w RF signal and then trigger
tuner to start its tuning cycle. I tried using the 'Digiout1' line on
the radio itself, but, since that is a k3 menu item, trying to set
that, while having the radio do the tuning cycle at the same time
appears impossible. The radio stops sending the "TUN" signal as soon
as Commander goes into the menu command to set the DIGOUT1 on. I've
moved to using the LPT port on the computer to trigger the tuner, and
have a working solution, but am looking for something a bit more
elegant.

I'm using this board purchased from Amazon -
https://www.amazon.com/gp/product/B07486S17P

It is intended for use with 5 axis CNC machines. It breaks out the
parallel port lines, includes buffers, screw terminals and a relay,
all for less than $20. The rub here is that the relay, which I'd like
to use to trigger the tuner, is on pin 14, which is outside of what
Commander can set. I've added some circuity and an outboard relay, so
I can use one of the data 7-0 lines, which the board intends for X/Y/Z
positioning, but would prefer to do this with fewer parts - like just
the off the shelf board - if possible, if the software is able to
support it.



Thanks.
73,
N8YSZ.




--
Dan Brown
brown@...

Commander pardata question

Daniel Brown
 


Is there a way in Commander to control pins other than just 9-2 (bit 7-0) on a parallel / LPT port? 


Why? 


Buffered Parallel port CNC breakout boards with screw terminals seem to be fairly common and relatively inexpensive. They seem to typically use the data pins for X/Y/Z positioning, but use some of the other pins other functions. I have a board, purchased for <$20 off of Amazon that includes a relay, but that relay is activated by pin 14, which is outside of what Commander can control currently. 


Board is this: 


https://www.amazon.com/gp/product/B07486S17P


I'm currently using the board with Commander talking to an Elecraft K3 to trigger an ICOM AH-4 auto-tuner. I have it working, but needed to add a few bits of extra circuitry to invert the signal to small relay board which manages the 12v signal lines on the tuner. I use one of the Commander buttons to first set the K3 TUN power out to 15w, then to click the K3's TUN mode on, then <ParData 255> to click the tuning start. Yes, setting all 8 bits is overkill, I was being lazy since this is all I have connected currently. I watch the SWR drop (Elecraft W2) and then click the button again to turn off the K3 and end the tuning cycle. It seems to work well - I'm just hoping to do this with an off the shelf board and a few less parts, if the Commander software could support it. The documentation doesn't seem to indicate that it does currently. 


Thanks,

73! 



Re: WW and JT modes

llibsch
 

Dave,

    I would strongly support your extending WinWarbler to directly interoperate with WSJT-X so that a "Broadband Decode" window showing all active JT-mode stations could be presented, color-coded by need and LoTW/eQSL participation. DX and DXpedition operation on FT-8 is already significant and growing rapidly. Integration of WSJT-X into WinWarbler would be a great addition to your outstanding DXLab Suite.
                                      
                                                                                 Larry, K4KGG

IC-7610 Support

Richard Kile
 

Hi Dave,

Santa delivered an early present last week. My new IC-7610 arrived from HRO Denver. I'm moving from a 12 year old workhorse IC-765 Pro III that used a micro Keyer II interface to DXLabs, to a single USB cable interface from laptop to radio.

When I downloaded and installed the latest ICOM USB drivers and plugged in the IC-7610, two comm ports were established. Since the IC-7610 is not yet in the list of ICOM radios in Commander I set up initially using the IC-7851 and have been working to make sure everything is working correctly. I've been through the radio settings several times to get basic radio functions and CW and SSB modes working the way I like. WSJT-X with JTAlert-X are working with DXKeeper. CWGet and the CWGtoWW bridge to WinWarbler are also working as is PSK in WinWarbler.

Two questions for you. Do you have a anticipated date for adding the IC-7610 to the list of radios in Commander? And more importantly, will DXLabs be configured to support both comm ports over the single USB cable? I ask because that would allow FSK RTTY with just the one cable using WinWarbler.

As an experiment I followed the setup in a K0PIR YouTube video and set up N1MM Logger+ with the MMTTY Engine and got FSK RTTY to work with just the one cable using both ports. Not my software of choice though for everyday DXing.

If I am missing something in the Wiki on how to configure two comm ports for a single radio a pointer to the "how to" would be greatly appreciated.

Thanks for all you do to bring us this great software product.

73 and best wishes for the holidays!

Rick WA7BNG



Re: No Receive in WinWarbler

Joe Subich, W4TV
 

With a single sound card, it is very likely that Windows has selected
the "microphone" input as its default device while WW is trying to use
the "Line" input. What happens is that WW opens the Line input ...
Windows then realizes that something has switched the active input and
switches back to the microphone input.

With a single sound card you really need to set both the Windows Default
(Recording) Device and the Default Communications Device to the same
(endpoint) input as you will be using for WW (MMTTY and PSKcore) so
that all applications and Windows are pointed to the same input.

It is still a bad idea to use a single sound card - particularly due to
the chance of "Windows noises," streaming audio *AND* SpotCollector's
announcements ("Joe DX") reaching the transceiver's audio input and
going out "on the air".

73,

... Joe, W4TV

On 12/19/2017 8:58 PM, Alan Swinger awswinger@... [dxlab] wrote:
Joe - Many thanks, but this is a New problem with a Win 7 system on which WW has
worked all OK for yrs w/ the one and only sound card that came w/ this Dell
laptop. Agree that Windows or something (no new apps installed lately) is muting
the external input to the card, and that is what I am trying to solve . . . w/o
adding another sound card.
Just want to restore the system to where it was and not have this receive muting
issue.
Best regards - Alan
-----Original Message-----
From: "'Joe Subich, W4TV' lists@... [dxlab]"
Sent: Dec 19, 2017 7:43 PM
To: dxlab@...
Subject: Re: [dxlab] Re: No Receive in WinWarbler

> As I told Dave separately, I can make the Soundcard and WW connect
> and see RTTY correctly for a brief period .. . so I know the sound
> card is working and that the info is getting from the K3 (as it
> always has until this glitch!?). However, the connection w/ the
> soundcard, WW, and the radio drops out after 15 seconds or so.
This is typically due to Windows or another application muting the
sound card you are using for WinWarbler?
Are you attempting to use the sound card on the motherboard of your
computer or do you have a second sound card for amateur use? The
best solution *under any circumstances* is to have a second sound
card dedicated to amateur software and configure Windows (Sound Control
Panel) to use the motherboard sound card as both the Default Device
(Windows recording device) and the Default Communications Device (Skype
and Cortana). In addition, configure Windows to use the speaker of
the motherboard sound card as the Default (playback) Device (the
"Windows noises") so Windows sounds and streaming audio are never sent
to the transceiver (on the air).
73,
.... Joe, W4TV
On 12/19/2017 5:25 PM, Alan Swinger awswinger@... [dxlab] wrote:
>
>
> Rich - Tks for responding and Merry Christmas to all.
>
> As I told Dave separately, I can make the Soundcard and WW connect and
see RTTY
> correctly for a brief period .. . so I know the sound card is working and
that
> the info is getting from the K3 (as it always has until this glitch!?).
However,
> the connection w/ the soundcard, WW, and the radio drops out after 15
seconds or
> so.
>
> BTW, I can listen to any other audio thru the soundcard all OK . . . so I
am now
> in the process of starting from scratch w/ WW & RTTY/Dig SetUp.
>
> However, I find this very annoying and am hoping someone on this grp can
help.
>
> Tks and 73 - Alan
>
> -----Original Message-----
> From: "ve3iay@... [dxlab]"
> Sent: Dec 19, 2017 3:53 PM
> To: dxlab@...
> Subject: [dxlab] Re: No Receive in WinWarbler
>
> If there is audio coming out of the radio on the connector that normally
> goes to the sound card, but the software is not seeing anything, that
> suggests that either the software is using the wrong sound card input or the
> sound card level setting is too low. If you have plugged in or unplugged a
> sound card input or output (even on an unrelated device) or connected or
> disconnected an external sound card device, Windows may have played games
> with your sound card settings.
>
>
> 73,
> Rich VE3KI
>
>
>
> ---In dxlab@..., <awswinger@...> wrote :
>
> Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard
> Input) and I hear RTTY signals all OK. I also changed to a different cable
> and still no Receive indications on WW except for a dot in the middle of the
> circular screen in the RTTY Receive section of WW.
> It looks as if something is turned off but don't recall changing any
settings.
> Thoughts? - alan K9MBQ
>
> -----Original Message-----
>
> >From: Dave AA6YQ <aa6yq@...>
> >Sent: Dec 18, 2017 7:24 PM
> >To: 'Alan Swinger' <awswinger@...>
> >Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
> >Subject: RE: RTTY Receive issue
> >
> >Try listening to the soundcard inputs with a pair of headphones or an
active speaker.
> >
> > Dave
> >
> >-----Original Message-----
> >From: Alan Swinger [mailto:awswinger@...]
> >Sent: Monday, December 18, 2017 5:58 PM
> >To: Dave AA6YQ
> >Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
> >Subject: RE: RTTY Receive issue
> >
> >Would appreciate any suggestions how best to do that.
> >Thanks - Alan
> >
> >
> >-----Original Message-----
> >>From: Dave AA6YQ <aa6yq@...>
> >>Sent: Dec 18, 2017 5:53 PM
> >>To: 'Alan Swinger' <awswinger@...>
> >>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
> >>Subject: RE: RTTY Receive issue
> >>
> >>>>>AA6YQ comments below
>
> >>-----Original Message-----
> >>From: Alan Swinger [mailto:awswinger@...]
> >>Sent: Monday, December 18, 2017 5:27 PM
> >>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
> >>Subject: RTTY Receive issue
> >>
> >>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but
today for reasons unknown signals are not showing on the screen of DXLAB
WinWarbler (WW). I can transmit all OK using WW. I checked the cables from
my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and
gain is at 20 where it has been.
> >>
> >>I have not changed configurations and problem is on all bands . . . not
seeing or decoding RTTY or PSK (if there were any since FT8 seems to have
displaced them)!? Pls advise.
> >>
> >>Dave - Seems like I have seen some updates to DXLAB recently. Could
those be the cause? Any suggestions?
> >>
> >>>>>There has not been a recent update of WinWarbler.
> >>
> >>>>>The usual cause of this is a Windows Update that scrambles your
soundcard settings so that WinWarbler doesn't see any signals, but first
verify that audio output from your K3 is present at your soundcard inputs.
> >>
> >> 73,
> >>
> >> Dave, AA6YQ
> >>
> >
>
>
>
>
>

Re: DXKeeper 14.3.6 is available

Dave AA6YQ
 

Thanks for sending me the errorlog and your log file, Merv. They exposed two defects in DXKeeper 14.3.6:

1. the DXCC Progress Report function doesn't tolerate a QSO with an invalid date

2. when the DXCC Progress Report function encounters an error (like a QSO with an invalid date), it doesn't gracefully recover,
requiring the user to restart DXKeeper

Both of these defects are corrected in the next version of DXKeeper, which will ignore any QSO with an invalid date.

Your log contains two QSOs, all of whose items are blank. These are what triggered the defects described above. To find them, filter
the Log Page Display with the SQL expression

call=''

(those are two back-to-back single apostrophes)

To do that,

1. paste the above SQL expression into the textbox in the Filter panel at the bottom of the Main window's "Log QSOs" tab

2. with the mouse cursor in the Filter panel textbox, depress the CTRL key while striking the S key

The first of your empty QSOs will be selected. Delete it by clicking Delete button above the Log Page Display. Then click in the
other empty QSO and click the Delete button to remove it.

You'll now be able to run the DXCC Progress Report function.

Stephan NN4X, your errorlog indicates a similar problem, though the QSOs in question may have invalid as opposed to "empty" dates as
Merv's did. Click the Filter panel's Broke button to find them.

Merv, you can't use the Filter panel's Broke button to find your two broken QSOs because DXKeeper considers most of your QSOs to be
broken. Why? Because you have a "My QTH" defined, but most of your QSOs don't specify a "My QTH ID". You can update them all "en
masse" using the "Modify QSOs" panel at the bottom of the Main window's "Log QSOs" tab; be sure to backup your log before you do
that!

Since the defects in DXKeeper 14.3.6 are relatively easy to work around, I will wait another day or two to see if any additional
defects are reported before making a public release bearing the defect corrections. If this is problematic for anyone, let me know
and I will immediately make a corrected version of DXKeeper available to you.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 4:37 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper 14.3.6 is available

Dave:

Downloaded the new version,  all went fine,  DXkeeper ran ok,  until I tried to do "Check Progress"  "progress DXCC"  and it locks
up, have to shut down DXkeeper.
Restart and it works fine except it locks up on trying to do DXCC progress, It will run "real time DXCC" ok.
Have rebooted etc to try and clean out everything,  no change.

Also noticed I randomly get errors when running WSJT-X / JT-Alert, the error mentions it cannot log the QSO,  but after a short time
if I check the log the QSO has been logged.

I reverted back to the previous version of DXKeeper and all is fine again.
Perhaps its just my computer or some setting I have wrong.
Thought I would mention it as it just started after the update.
Thanks 73 Merv K9FD


------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links




---
This email has been checked for viruses by AVG.
http://www.avg.com

Re: No Receive in WinWarbler

Alan Swinger
 

Joe - Many thanks, but this is a New problem with a Win 7 system on which WW has worked all OK for yrs w/ the one and only sound card that came w/ this Dell laptop. Agree that Windows or something (no new apps installed lately) is muting the external input to the card, and that is what I am trying to solve . . . w/o adding another sound card.

Just want to restore the system to where it was and not have this receive muting issue.

Best regards - Alan

-----Original Message-----
From: "'Joe Subich, W4TV' lists@... [dxlab]"
Sent: Dec 19, 2017 7:43 PM
To: dxlab@...
Subject: Re: [dxlab] Re: No Receive in WinWarbler

 


> As I told Dave separately, I can make the Soundcard and WW connect
> and see RTTY correctly for a brief period .. . so I know the sound
> card is working and that the info is getting from the K3 (as it
> always has until this glitch!?). However, the connection w/ the
> soundcard, WW, and the radio drops out after 15 seconds or so.
This is typically due to Windows or another application muting the
sound card you are using for WinWarbler?

Are you attempting to use the sound card on the motherboard of your
computer or do you have a second sound card for amateur use? The
best solution *under any circumstances* is to have a second sound
card dedicated to amateur software and configure Windows (Sound Control
Panel) to use the motherboard sound card as both the Default Device
(Windows recording device) and the Default Communications Device (Skype
and Cortana). In addition, configure Windows to use the speaker of
the motherboard sound card as the Default (playback) Device (the
"Windows noises") so Windows sounds and streaming audio are never sent
to the transceiver (on the air).

73,

.... Joe, W4TV

On 12/19/2017 5:25 PM, Alan Swinger awswinger@... [dxlab] wrote:
>
>
> Rich - Tks for responding and Merry Christmas to all.
>
> As I told Dave separately, I can make the Soundcard and WW connect and see RTTY
> correctly for a brief period .. . so I know the sound card is working and that
> the info is getting from the K3 (as it always has until this glitch!?). However,
> the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or
> so.
>
> BTW, I can listen to any other audio thru the soundcard all OK . . . so I am now
> in the process of starting from scratch w/ WW & RTTY/Dig SetUp.
>
> However, I find this very annoying and am hoping someone on this grp can help.
>
> Tks and 73 - Alan
>
> -----Original Message-----
> From: "ve3iay@... [dxlab]"
> Sent: Dec 19, 2017 3:53 PM
> To: dxlab@...
> Subject: [dxlab] Re: No Receive in WinWarbler
>
> If there is audio coming out of the radio on the connector that normally
> goes to the sound card, but the software is not seeing anything, that
> suggests that either the software is using the wrong sound card input or the
> sound card level setting is too low. If you have plugged in or unplugged a
> sound card input or output (even on an unrelated device) or connected or
> disconnected an external sound card device, Windows may have played games
> with your sound card settings.
>
>
> 73,
> Rich VE3KI
>
>
>
> ---In dxlab@..., wrote :
>
> Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard
> Input) and I hear RTTY signals all OK. I also changed to a different cable
> and still no Receive indications on WW except for a dot in the middle of the
> circular screen in the RTTY Receive section of WW.
> It looks as if something is turned off but don't recall changing any settings.
> Thoughts? - alan K9MBQ
>
> -----Original Message-----
>
> >From: Dave AA6YQ
> >Sent: Dec 18, 2017 7:24 PM
> >To: 'Alan Swinger'
> >Cc: 'Elecraft Support' , 'Dale Farmer - Elecraft'
> >Subject: RE: RTTY Receive issue
> >
> >Try listening to the soundcard inputs with a pair of headphones or an active speaker.
> >
> > Dave
> >
> >-----Original Message-----
> >From: Alan Swinger [mailto:awswinger@...]
> >Sent: Monday, December 18, 2017 5:58 PM
> >To: Dave AA6YQ
> >Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
> >Subject: RE: RTTY Receive issue
> >
> >Would appreciate any suggestions how best to do that.
> >Thanks - Alan
> >
> >
> >-----Original Message-----
> >>From: Dave AA6YQ
> >>Sent: Dec 18, 2017 5:53 PM
> >>To: 'Alan Swinger'
> >>Cc: 'Elecraft Support' , 'Dale Farmer - Elecraft'
> >>Subject: RE: RTTY Receive issue
> >>
> >>>>>AA6YQ comments below
>
> >>-----Original Message-----
> >>From: Alan Swinger [mailto:awswinger@...]
> >>Sent: Monday, December 18, 2017 5:27 PM
> >>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
> >>Subject: RTTY Receive issue
> >>
> >>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but today for reasons unknown signals are not showing on the screen of DXLAB WinWarbler (WW). I can transmit all OK using WW. I checked the cables from my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and gain is at 20 where it has been.
> >>
> >>I have not changed configurations and problem is on all bands . . . not seeing or decoding RTTY or PSK (if there were any since FT8 seems to have displaced them)!? Pls advise.
> >>
> >>Dave - Seems like I have seen some updates to DXLAB recently. Could those be the cause? Any suggestions?
> >>
> >>>>>There has not been a recent update of WinWarbler.
> >>
> >>>>>The usual cause of this is a Windows Update that scrambles your soundcard settings so that WinWarbler doesn't see any signals, but first verify that audio output from your K3 is present at your soundcard inputs.
> >>
> >> 73,
> >>
> >> Dave, AA6YQ
> >>
> >
>
>
>
>
>

Re: DX Keeper Crashing when Checking Progress

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 7:38 PM
To: dxlab@...
Subject: Re: [dxlab] DX Keeper Crashing when Checking Progress

I know this does not help those who are having problems, but all DXLab apps that I use are working normally after the latest upgrade. This is on an i7 with 16gb of ram and Win 10.

The errorlog that Merv K9FD sent me shows the presence of a data-dependent defect in the DXCC Progress Report generator, which I recently extended to include "Satellite DXCC" stats. I have asked him to send me his log file so I can track this down and correct it.
73,

Dave, AA6YQ

Re: No Receive in WinWarbler

Joe Subich, W4TV
 

As I told Dave separately, I can make the Soundcard and WW connect and see RTTY correctly for a brief period .. . so I know the sound card is working and that the info is getting from the K3 (as it always has until this glitch!?). However, the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or so.
This is typically due to Windows or another application muting the
sound card you are using for WinWarbler?

Are you attempting to use the sound card on the motherboard of your
computer or do you have a second sound card for amateur use? The
best solution *under any circumstances* is to have a second sound
card dedicated to amateur software and configure Windows (Sound Control
Panel) to use the motherboard sound card as both the Default Device
(Windows recording device) and the Default Communications Device (Skype
and Cortana). In addition, configure Windows to use the speaker of
the motherboard sound card as the Default (playback) Device (the
"Windows noises") so Windows sounds and streaming audio are never sent
to the transceiver (on the air).


73,

... Joe, W4TV


On 12/19/2017 5:25 PM, Alan Swinger awswinger@... [dxlab] wrote:
Rich - Tks for responding and Merry Christmas to all.
As I told Dave separately, I can make the Soundcard and WW connect and see RTTY
correctly for a brief period .. . so I know the sound card is working and that
the info is getting from the K3 (as it always has until this glitch!?). However,
the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or
so.
BTW, I can listen to any other audio thru the soundcard all OK . . . so I am now
in the process of starting from scratch w/ WW & RTTY/Dig SetUp.
However, I find this very annoying and am hoping someone on this grp can help.
Tks and 73 - Alan
-----Original Message-----
From: "ve3iay@... [dxlab]"
Sent: Dec 19, 2017 3:53 PM
To: dxlab@...
Subject: [dxlab] Re: No Receive in WinWarbler
If there is audio coming out of the radio on the connector that normally
goes to the sound card, but the software is not seeing anything, that
suggests that either the software is using the wrong sound card input or the
sound card level setting is too low. If you have plugged in or unplugged a
sound card input or output (even on an unrelated device) or connected or
disconnected an external sound card device, Windows may have played games
with your sound card settings.
73,
Rich VE3KI
---In dxlab@..., <awswinger@...> wrote :
Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard
Input) and I hear RTTY signals all OK. I also changed to a different cable
and still no Receive indications on WW except for a dot in the middle of the
circular screen in the RTTY Receive section of WW.
It looks as if something is turned off but don't recall changing any settings.
Thoughts? - alan K9MBQ
-----Original Message-----

>From: Dave AA6YQ <aa6yq@...>
>Sent: Dec 18, 2017 7:24 PM
>To: 'Alan Swinger' <awswinger@...>
>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>Subject: RE: RTTY Receive issue
>
>Try listening to the soundcard inputs with a pair of headphones or an active speaker.
>
> Dave
>
>-----Original Message-----
>From: Alan Swinger [mailto:awswinger@...]
>Sent: Monday, December 18, 2017 5:58 PM
>To: Dave AA6YQ
>Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
>Subject: RE: RTTY Receive issue
>
>Would appreciate any suggestions how best to do that.
>Thanks - Alan
>
>
>-----Original Message-----
>>From: Dave AA6YQ <aa6yq@...>
>>Sent: Dec 18, 2017 5:53 PM
>>To: 'Alan Swinger' <awswinger@...>
>>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>>Subject: RE: RTTY Receive issue
>>
>>>>>AA6YQ comments below

>>-----Original Message-----
>>From: Alan Swinger [mailto:awswinger@...]
>>Sent: Monday, December 18, 2017 5:27 PM
>>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
>>Subject: RTTY Receive issue
>>
>>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but today for reasons unknown signals are not showing on the screen of DXLAB WinWarbler (WW). I can transmit all OK using WW. I checked the cables from my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and gain is at 20 where it has been.
>>
>>I have not changed configurations and problem is on all bands . . . not seeing or decoding RTTY or PSK (if there were any since FT8 seems to have displaced them)!? Pls advise.
>>
>>Dave - Seems like I have seen some updates to DXLAB recently. Could those be the cause? Any suggestions?
>>
>>>>>There has not been a recent update of WinWarbler.
>>
>>>>>The usual cause of this is a Windows Update that scrambles your soundcard settings so that WinWarbler doesn't see any signals, but first verify that audio output from your K3 is present at your soundcard inputs.
>>
>> 73,
>>
>> Dave, AA6YQ
>>
>

Re: DX Keeper Crashing when Checking Progress

Dave AA6YQ
 

Attachments are not conveyed by this Yahoo Group.

Please attach a copy of the Message Box and your errorlog.txt file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 7:34 PM
To: dxlab@...
Subject: [dxlab] DX Keeper Crashing when Checking Progress



When I attempt to check my DXCC Progress, this message box is displayed:





Here's the relevant section of Errorlog.txt:





<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: DX Keeper Crashing when Checking Progress

David Bunte
 

I know this does not help those who are having problems, but all DXLab apps that I use are working normally after the latest upgrade. This is on an i7 with 16gb of ram and Win 10.

Good luck to those experiencing problems.

Dave - K9FN

On Tue, Dec 19, 2017 at 7:33 PM, nn4x@... [dxlab] <dxlab@...> wrote:
 

When I attempt to check my DXCC Progress, this message box is displayed:


Here's the relevant section of Errorlog.txt:


19-Dec-2017 23:10:18 > DXKeeper version 14.3.6
19-Dec-2017 23:10:18 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:10:18 > App.exe           : DXKeeper
19-Dec-2017 23:10:18 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:10:18 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:10:18 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:10:18 > ANSI CodePage     : 1252
19-Dec-2017 23:10:18 > OEM CodePage      : 437
19-Dec-2017 23:10:18 > Country           : United States
19-Dec-2017 23:10:18 > Language          : English
19-Dec-2017 23:10:18 > DecimalSeparator  : .
19-Dec-2017 23:10:18 > ThousandSeparator : ,
19-Dec-2017 23:10:18 > DXLab Apps        : [CC,DXV]
19-Dec-2017 23:10:33 > Monitors          : 2
19-Dec-2017 23:10:33 > Monitor 1
19-Dec-2017 23:10:33 >    width          : 1920
19-Dec-2017 23:10:33 >    height         : 1200
19-Dec-2017 23:10:33 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:10:33 > Monitor 2
19-Dec-2017 23:10:33 >    width          : 1680
19-Dec-2017 23:10:33 >    height         : 1050
19-Dec-2017 23:10:33 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:10:33 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:10:33 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:10:56 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:11:03 > DXKeeper version 14.3.6
19-Dec-2017 23:11:03 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:11:03 > App.exe           : DXKeeper
19-Dec-2017 23:11:03 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:11:03 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:11:03 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:11:03 > ANSI CodePage     : 1252
19-Dec-2017 23:11:03 > OEM CodePage      : 437
19-Dec-2017 23:11:03 > Country           : United States
19-Dec-2017 23:11:03 > Language          : English
19-Dec-2017 23:11:03 > DecimalSeparator  : .
19-Dec-2017 23:11:03 > ThousandSeparator : ,
19-Dec-2017 23:11:03 > DXLab Apps        : [CC,DXV]
19-Dec-2017 23:15:34 > Monitors          : 2
19-Dec-2017 23:15:34 > Monitor 1
19-Dec-2017 23:15:34 >    width          : 1920
19-Dec-2017 23:15:34 >    height         : 1200
19-Dec-2017 23:15:34 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:15:34 > Monitor 2
19-Dec-2017 23:15:34 >    width          : 1680
19-Dec-2017 23:15:34 >    height         : 1050
19-Dec-2017 23:15:34 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:15:34 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:15:34 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:20:22 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:37:30 > DXKeeper version 14.3.6
19-Dec-2017 23:37:30 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:37:30 > App.exe           : DXKeeper
19-Dec-2017 23:37:30 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:37:30 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:37:30 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:37:30 > ANSI CodePage     : 1252
19-Dec-2017 23:37:30 > OEM CodePage      : 437
19-Dec-2017 23:37:30 > Country           : United States
19-Dec-2017 23:37:30 > Language          : English
19-Dec-2017 23:37:30 > DecimalSeparator  : .
19-Dec-2017 23:37:30 > ThousandSeparator : ,
19-Dec-2017 23:37:30 > DXLab Apps        : [CC]
19-Dec-2017 23:37:55 > Monitors          : 2
19-Dec-2017 23:37:55 > Monitor 1
19-Dec-2017 23:37:55 >    width          : 1920
19-Dec-2017 23:37:55 >    height         : 1200
19-Dec-2017 23:37:55 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:37:55 > Monitor 2
19-Dec-2017 23:37:55 >    width          : 1680
19-Dec-2017 23:37:55 >    height         : 1050
19-Dec-2017 23:37:55 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:37:55 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:37:55 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:38:08 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:38:11 > DXKeeper version 14.3.6
19-Dec-2017 23:38:11 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:38:11 > App.exe           : DXKeeper
19-Dec-2017 23:38:11 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:38:11 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:38:11 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:38:11 > ANSI CodePage     : 1252
19-Dec-2017 23:38:11 > OEM CodePage      : 437
19-Dec-2017 23:38:11 > Country           : United States
19-Dec-2017 23:38:11 > Language          : English
19-Dec-2017 23:38:11 > DecimalSeparator  : .
19-Dec-2017 23:38:11 > ThousandSeparator : ,
19-Dec-2017 23:38:11 > DXLab Apps        : [CC]
20-Dec-2017 00:26:45 > Monitors          : 2
20-Dec-2017 00:26:45 > Monitor 1
20-Dec-2017 00:26:45 >    width          : 1920
20-Dec-2017 00:26:45 >    height         : 1200
20-Dec-2017 00:26:45 >    dimensions     : (0, 0)-(1920, 1200)
20-Dec-2017 00:26:45 > Monitor 2
20-Dec-2017 00:26:45 >    width          : 1680
20-Dec-2017 00:26:45 >    height         : 1050
20-Dec-2017 00:26:45 >    dimensions     : (-1680, 0)-(0, 1050)
20-Dec-2017 00:26:45 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
20-Dec-2017 00:26:45 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set



73,

Steve

NN4X


DX Keeper Crashing when Checking Progress

nn4x@...
 

When I attempt to check my DXCC Progress, this message box is displayed:


Here's the relevant section of Errorlog.txt:


19-Dec-2017 23:10:18 > DXKeeper version 14.3.6
19-Dec-2017 23:10:18 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:10:18 > App.exe           : DXKeeper
19-Dec-2017 23:10:18 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:10:18 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:10:18 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:10:18 > ANSI CodePage     : 1252
19-Dec-2017 23:10:18 > OEM CodePage      : 437
19-Dec-2017 23:10:18 > Country           : United States
19-Dec-2017 23:10:18 > Language          : English
19-Dec-2017 23:10:18 > DecimalSeparator  : .
19-Dec-2017 23:10:18 > ThousandSeparator : ,
19-Dec-2017 23:10:18 > DXLab Apps        : [CC,DXV]
19-Dec-2017 23:10:33 > Monitors          : 2
19-Dec-2017 23:10:33 > Monitor 1
19-Dec-2017 23:10:33 >    width          : 1920
19-Dec-2017 23:10:33 >    height         : 1200
19-Dec-2017 23:10:33 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:10:33 > Monitor 2
19-Dec-2017 23:10:33 >    width          : 1680
19-Dec-2017 23:10:33 >    height         : 1050
19-Dec-2017 23:10:33 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:10:33 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:10:33 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:10:56 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:11:03 > DXKeeper version 14.3.6
19-Dec-2017 23:11:03 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:11:03 > App.exe           : DXKeeper
19-Dec-2017 23:11:03 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:11:03 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:11:03 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:11:03 > ANSI CodePage     : 1252
19-Dec-2017 23:11:03 > OEM CodePage      : 437
19-Dec-2017 23:11:03 > Country           : United States
19-Dec-2017 23:11:03 > Language          : English
19-Dec-2017 23:11:03 > DecimalSeparator  : .
19-Dec-2017 23:11:03 > ThousandSeparator : ,
19-Dec-2017 23:11:03 > DXLab Apps        : [CC,DXV]
19-Dec-2017 23:15:34 > Monitors          : 2
19-Dec-2017 23:15:34 > Monitor 1
19-Dec-2017 23:15:34 >    width          : 1920
19-Dec-2017 23:15:34 >    height         : 1200
19-Dec-2017 23:15:34 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:15:34 > Monitor 2
19-Dec-2017 23:15:34 >    width          : 1680
19-Dec-2017 23:15:34 >    height         : 1050
19-Dec-2017 23:15:34 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:15:34 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:15:34 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:20:22 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:37:30 > DXKeeper version 14.3.6
19-Dec-2017 23:37:30 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:37:30 > App.exe           : DXKeeper
19-Dec-2017 23:37:30 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:37:30 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:37:30 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:37:30 > ANSI CodePage     : 1252
19-Dec-2017 23:37:30 > OEM CodePage      : 437
19-Dec-2017 23:37:30 > Country           : United States
19-Dec-2017 23:37:30 > Language          : English
19-Dec-2017 23:37:30 > DecimalSeparator  : .
19-Dec-2017 23:37:30 > ThousandSeparator : ,
19-Dec-2017 23:37:30 > DXLab Apps        : [CC]
19-Dec-2017 23:37:55 > Monitors          : 2
19-Dec-2017 23:37:55 > Monitor 1
19-Dec-2017 23:37:55 >    width          : 1920
19-Dec-2017 23:37:55 >    height         : 1200
19-Dec-2017 23:37:55 >    dimensions     : (0, 0)-(1920, 1200)
19-Dec-2017 23:37:55 > Monitor 2
19-Dec-2017 23:37:55 >    width          : 1680
19-Dec-2017 23:37:55 >    height         : 1050
19-Dec-2017 23:37:55 >    dimensions     : (-1680, 0)-(0, 1050)
19-Dec-2017 23:37:55 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
19-Dec-2017 23:37:55 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set
19-Dec-2017 23:38:08 > Common.Terminate: DXKeeper shutdown

19-Dec-2017 23:38:11 > DXKeeper version 14.3.6
19-Dec-2017 23:38:11 > App.Path          : C:\DXLab\DXKeeper
19-Dec-2017 23:38:11 > App.exe           : DXKeeper
19-Dec-2017 23:38:11 > Module            : C:\DXLab\DXKeeper\DXKeeper.exe
19-Dec-2017 23:38:11 > Operating System  : Windows 10 Home (64-bit) build 16299
19-Dec-2017 23:38:11 > Locale ID         : 1033 (0x409)
19-Dec-2017 23:38:11 > ANSI CodePage     : 1252
19-Dec-2017 23:38:11 > OEM CodePage      : 437
19-Dec-2017 23:38:11 > Country           : United States
19-Dec-2017 23:38:11 > Language          : English
19-Dec-2017 23:38:11 > DecimalSeparator  : .
19-Dec-2017 23:38:11 > ThousandSeparator : ,
19-Dec-2017 23:38:11 > DXLab Apps        : [CC]
20-Dec-2017 00:26:45 > Monitors          : 2
20-Dec-2017 00:26:45 > Monitor 1
20-Dec-2017 00:26:45 >    width          : 1920
20-Dec-2017 00:26:45 >    height         : 1200
20-Dec-2017 00:26:45 >    dimensions     : (0, 0)-(1920, 1200)
20-Dec-2017 00:26:45 > Monitor 2
20-Dec-2017 00:26:45 >    width          : 1680
20-Dec-2017 00:26:45 >    height         : 1050
20-Dec-2017 00:26:45 >    dimensions     : (-1680, 0)-(0, 1050)
20-Dec-2017 00:26:45 > program error 13 in module DXLogModule.GenerateLogProgressReport: Type mismatch
20-Dec-2017 00:26:45 > program error 91 in module DXLogMain.DXCCProgressReportCmd_Click: Object variable or With block variable not set



73,

Steve

NN4X

Re: No Receive in WinWarbler

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 5:26 PM
To: dxlab@...; dxlab@...
Subject: Re: [dxlab] Re: No Receive in WinWarbler

Rich - Tks for responding and Merry Christmas to all.

As I told Dave separately, I can make the Soundcard and WW connect and see RTTY correctly for a brief period .. . so I know the sound card is working and that the info is getting from the K3 (as it always has until this glitch!?). However, the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or so.

BTW, I can listen to any other audio thru the soundcard all OK . . . so I am now in the process of starting from scratch w/ WW & RTTY/Dig SetUp.

There is no setting in WinWarbler that would result in an audio dropout after 15 seconds. That sounds like a soundcard driver or Windows issue.
73,

Dave, AA6YQ

Re: No Receive in WinWarbler

ve3ki
 

There is a good chance the problem is in Windows, not in any of the DXLab Suite settings. Take a look at <http://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown> to see if following the instructions there stops your connections from dropping out.

73,
Rich VE3KI



---In dxlab@..., <awswinger@...> wrote :

Rich - Tks for responding and Merry Christmas to all.

As I told Dave separately, I can make the Soundcard and WW connect and see RTTY correctly for a brief period .. . so I know the sound card is working and that the info is getting from the K3 (as it always has until this glitch!?). However, the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or so.

 

BTW, I can listen to any other audio thru the soundcard all OK . . . so I am now in the process of starting from scratch w/ WW & RTTY/Dig SetUp.

 

However, I find this very annoying and am hoping someone on this grp can help.

 

Tks and 73 - Alan

-----Original Message-----
From: "ve3iay@... [dxlab]"
Sent: Dec 19, 2017 3:53 PM
To: dxlab@...
Subject: [dxlab] Re: No Receive in WinWarbler

 

If there is audio coming out of the radio on the connector that normally goes to the sound card, but the software is not seeing anything, that suggests that either the software is using the wrong sound card input or the sound card level setting is too low. If you have plugged in or unplugged a sound card input or output (even on an unrelated device) or connected or disconnected an external sound card device, Windows may have played games with your sound card settings.


73,
Rich VE3KI



---In dxlab@..., <awswinger@...> wrote :

Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard Input) and I hear RTTY signals all OK. I also changed to a different cable and still no Receive indications on WW except for a dot in the middle of the circular screen in the RTTY Receive section of WW.
It looks as if something is turned off but don't recall changing any settings.
Thoughts? - alan K9MBQ

-----Original Message-----

>From: Dave AA6YQ <aa6yq@...>
>Sent: Dec 18, 2017 7:24 PM
>To: 'Alan Swinger' <awswinger@...>
>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>Subject: RE: RTTY Receive issue
>
>Try listening to the soundcard inputs with a pair of headphones or an active speaker.
>
>     Dave
>
>-----Original Message-----
>From: Alan Swinger [mailto:awswinger@...]
>Sent: Monday, December 18, 2017 5:58 PM
>To: Dave AA6YQ
>Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
>Subject: RE: RTTY Receive issue
>
>Would appreciate any suggestions how best to do that.
>Thanks - Alan
>
>
>-----Original Message-----
>>From: Dave AA6YQ <aa6yq@...>
>>Sent: Dec 18, 2017 5:53 PM
>>To: 'Alan Swinger' <awswinger@...>
>>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>>Subject: RE: RTTY Receive issue
>>
>>>>>AA6YQ comments below

>>-----Original Message-----
>>From: Alan Swinger [mailto:awswinger@...]
>>Sent: Monday, December 18, 2017 5:27 PM
>>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
>>Subject: RTTY Receive issue
>>
>>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but today for reasons unknown signals are not showing on the screen of DXLAB WinWarbler (WW). I can transmit all OK using WW. I checked the cables from my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and gain is at 20 where it has been.
>>
>>I have not changed configurations and problem is on all bands . . . not seeing or decoding RTTY or PSK (if there were any since FT8 seems to have displaced them)!? Pls advise.
>>
>>Dave - Seems like I have seen some updates to DXLAB recently. Could those be the cause? Any suggestions?
>>
>>>>>There has not been a recent update of WinWarbler.
>>
>>>>>The usual cause of this is a Windows Update that scrambles your soundcard settings so that WinWarbler doesn't see any signals, but first verify that audio output from your K3 is present at your soundcard inputs.
>> 
>>       73,
>>
>>             Dave, AA6YQ
>>
>

Re: DXKeeper 14.3.6 is available

Björn SM7IUN
 

Merv,

the bogus logging errors in JTAlert can occur if you use auto-upload to e.g. ClubLog and/or eQSL in DXKeeper and the servers are down or under heavy load.
ClubLog has been down several times the last few days.

The default time-out in JTAlert for the check if the log entry was successful is somewhat short (2 seconds)
Try increasing it to e.g. 5  seconds. You will find the setting in JTAlert Settings -> Miscellaneous -> Performance

73,

Björn SM7IUN



2017-12-19 22:37 GMT+01:00 K9FD merv.k9fd@... [dxlab] <dxlab@...>:

Dave:

Downloaded the new version,  all went fine,  DXkeeper ran ok,  until
I tried to do "Check Progress"  "progress DXCC"  and it locks up, have
to shut down DXkeeper.
Restart and it works fine except it locks up on trying to do DXCC progress,
It will run "real time DXCC" ok.
Have rebooted etc to try and clean out everything,  no change.

Also noticed I randomly get errors when running WSJT-X / JT-Alert, the error
mentions it cannot log the QSO,  but after a short time if I check the log
the QSO has been logged.

I reverted back to the previous version of DXKeeper and all is fine again.
Perhaps its just my computer or some setting I have wrong.
Thought I would mention it as it just started after the update.
Thanks 73 Merv K9FD


------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/dxlab/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/dxlab/join
    (Yahoo! ID required)

<*> To change settings via email:
    dxlab-digest@...
    dxlab-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    dxlab-unsubscribe@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/


Re: No Receive in WinWarbler

Alan Swinger
 

Rich - Tks for responding and Merry Christmas to all.

As I told Dave separately, I can make the Soundcard and WW connect and see RTTY correctly for a brief period .. . so I know the sound card is working and that the info is getting from the K3 (as it always has until this glitch!?). However, the connection w/ the soundcard, WW, and the radio drops out after 15 seconds or so.

 

BTW, I can listen to any other audio thru the soundcard all OK . . . so I am now in the process of starting from scratch w/ WW & RTTY/Dig SetUp.

 

However, I find this very annoying and am hoping someone on this grp can help.

 

Tks and 73 - Alan

-----Original Message-----
From: "ve3iay@... [dxlab]"
Sent: Dec 19, 2017 3:53 PM
To: dxlab@...
Subject: [dxlab] Re: No Receive in WinWarbler

 

If there is audio coming out of the radio on the connector that normally goes to the sound card, but the software is not seeing anything, that suggests that either the software is using the wrong sound card input or the sound card level setting is too low. If you have plugged in or unplugged a sound card input or output (even on an unrelated device) or connected or disconnected an external sound card device, Windows may have played games with your sound card settings.


73,
Rich VE3KI



---In dxlab@..., wrote :

Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard Input) and I hear RTTY signals all OK. I also changed to a different cable and still no Receive indications on WW except for a dot in the middle of the circular screen in the RTTY Receive section of WW.
It looks as if something is turned off but don't recall changing any settings.
Thoughts? - alan K9MBQ

-----Original Message-----

>From: Dave AA6YQ
>Sent: Dec 18, 2017 7:24 PM
>To: 'Alan Swinger'
>Cc: 'Elecraft Support' , 'Dale Farmer - Elecraft'
>Subject: RE: RTTY Receive issue
>
>Try listening to the soundcard inputs with a pair of headphones or an active speaker.
>
>     Dave
>
>-----Original Message-----
>From: Alan Swinger [mailto:awswinger@...]
>Sent: Monday, December 18, 2017 5:58 PM
>To: Dave AA6YQ
>Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
>Subject: RE: RTTY Receive issue
>
>Would appreciate any suggestions how best to do that.
>Thanks - Alan
>
>
>-----Original Message-----
>>From: Dave AA6YQ
>>Sent: Dec 18, 2017 5:53 PM
>>To: 'Alan Swinger'
>>Cc: 'Elecraft Support' , 'Dale Farmer - Elecraft'
>>Subject: RE: RTTY Receive issue
>>
>>>>>AA6YQ comments below

>>-----Original Message-----
>>From: Alan Swinger [mailto:awswinger@...]
>>Sent: Monday, December 18, 2017 5:27 PM
>>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
>>Subject: RTTY Receive issue
>>
>>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but today for reasons unknown signals are not showing on the screen of DXLAB WinWarbler (WW). I can transmit all OK using WW. I checked the cables from my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and gain is at 20 where it has been.
>>
>>I have not changed configurations and problem is on all bands . . . not seeing or decoding RTTY or PSK (if there were any since FT8 seems to have displaced them)!? Pls advise.
>>
>>Dave - Seems like I have seen some updates to DXLAB recently. Could those be the cause? Any suggestions?
>>
>>>>>There has not been a recent update of WinWarbler.
>>
>>>>>The usual cause of this is a Windows Update that scrambles your soundcard settings so that WinWarbler doesn't see any signals, but first verify that audio output from your K3 is present at your soundcard inputs.
>> 
>>       73,
>>
>>             Dave, AA6YQ
>>
>

Re: DXKeeper 14.3.6 is available

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 4:37 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper 14.3.6 is available

Downloaded the new version,  all went fine,  DXkeeper ran ok,  until I tried to do "Check Progress"  "progress DXCC"  and it locks
up, have to shut down DXkeeper.
Restart and it works fine except it locks up on trying to do DXCC progress, It will run "real time DXCC" ok.
Have rebooted etc to try and clean out everything,  no change.

Please do the following:
1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. on the Main window's "Check Progress" tab, click the DXCC panel's Progress button

5. when DXKeeper "locks up", terminate it

6. start DXKeeper

7. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

8. attach the errorlog.txt file from your DXKeeper folder to an email message, and send it to me via

aa6yq (at) ambersoft.com


Also noticed I randomly get errors when running WSJT-X / JT-Alert, the error mentions it cannot log the QSO,  but after a short time
if I check the log the QSO has been logged.

Did you update your firewall and anti-malware applications to consider DXKeeper 14.3.6 to be "safe"?
73,

Dave, AA6YQ

Re: DXKeeper 14.3.6 is available

K9FD
 

Dave:

Downloaded the new version,� all went fine,� DXkeeper ran ok,� until
I tried to do "Check Progress"� "progress DXCC"� and it locks up, have
to shut down DXkeeper.
Restart and it works fine except it locks up on trying to do DXCC progress,
It will run "real time DXCC" ok.
Have rebooted etc to try and clean out everything,� no change.

Also noticed I randomly get errors when running WSJT-X / JT-Alert, the error
mentions it cannot log the QSO,� but after a short time if I check the log
the QSO has been logged.

I reverted back to the previous version of DXKeeper and all is fine again.
Perhaps its just my computer or some setting I have wrong.
Thought I would mention it as it just started after the update.
Thanks 73 Merv K9FD

Re: No Receive in WinWarbler

ve3ki
 

If there is audio coming out of the radio on the connector that normally goes to the sound card, but the software is not seeing anything, that suggests that either the software is using the wrong sound card input or the sound card level setting is too low. If you have plugged in or unplugged a sound card input or output (even on an unrelated device) or connected or disconnected an external sound card device, Windows may have played games with your sound card settings.

73,
Rich VE3KI



---In dxlab@..., <awswinger@...> wrote :

Dave - Hooked headphone to the K3 Line Out (goes to Computer Soundcard Input) and I hear RTTY signals all OK. I also changed to a different cable and still no Receive indications on WW except for a dot in the middle of the circular screen in the RTTY Receive section of WW.
It looks as if something is turned off but don't recall changing any settings.
Thoughts? - alan K9MBQ


-----Original Message-----

>From: Dave AA6YQ <aa6yq@...>
>Sent: Dec 18, 2017 7:24 PM
>To: 'Alan Swinger' <awswinger@...>
>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>Subject: RE: RTTY Receive issue
>
>Try listening to the soundcard inputs with a pair of headphones or an active speaker.
>
>     Dave
>
>-----Original Message-----
>From: Alan Swinger [mailto:awswinger@...]
>Sent: Monday, December 18, 2017 5:58 PM
>To: Dave AA6YQ
>Cc: 'Elecraft Support'; 'Dale Farmer - Elecraft'
>Subject: RE: RTTY Receive issue
>
>Would appreciate any suggestions how best to do that.
>Thanks - Alan
>
>
>-----Original Message-----
>>From: Dave AA6YQ <aa6yq@...>
>>Sent: Dec 18, 2017 5:53 PM
>>To: 'Alan Swinger' <awswinger@...>
>>Cc: 'Elecraft Support' <support@...>, 'Dale Farmer - Elecraft' <dale@...>
>>Subject: RE: RTTY Receive issue
>>
>>>>>AA6YQ comments below

>>-----Original Message-----
>>From: Alan Swinger [mailto:awswinger@...]
>>Sent: Monday, December 18, 2017 5:27 PM
>>To: Elecraft Support; Dale Farmer - Elecraft; aa6yq@...
>>Subject: RTTY Receive issue
>>
>>Elecraft - Have used my K3 w/o problems for yrs on Digital modes, but today for reasons unknown signals are not showing on the screen of DXLAB WinWarbler (WW). I can transmit all OK using WW. I checked the cables from my computer to the K3 and continuity is all OK. MIC SEL I on LINE IN and gain is at 20 where it has been.
>>
>>I have not changed configurations and problem is on all bands . . . not seeing or decoding RTTY or PSK (if there were any since FT8 seems to have displaced them)!? Pls advise.
>>
>>Dave - Seems like I have seen some updates to DXLAB recently. Could those be the cause? Any suggestions?
>>
>>>>>There has not been a recent update of WinWarbler.
>>
>>>>>The usual cause of this is a Windows Update that scrambles your soundcard settings so that WinWarbler doesn't see any signals, but first verify that audio output from your K3 is present at your soundcard inputs.
>> 
>>       73,
>>
>>             Dave, AA6YQ
>>
>

Re: Printer settings - QSL card size

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 12:49 PM
To: dxlab@...
Subject: [dxlab] Printer settings - QSL card size

I am trying to print QSL cards with size 140x90 mm

How can I define a custom size?

See
<http://www.dxlabsuite.com/dxkeeper/Help/QSLConfiguration.htm#QSL Cards Tab>

and

<http://www.dxlabsuite.com/dxkeeper/Help/QSLMedia.htm>

73,

Dave, AA6YQ