Date   
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

Re: No Receive in WinWarbler

Dave AA6YQ
 

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

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?

If, as repeatedly recommended, you have directed the Launcher to save your working WinWarbler settings to a Workspace, then restore WinWarbler settings from that saved Workspace:
<http://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace>

Otherwise, compare your settings to the those recommended here and correct any discrepancies:
<http://www.dxlabsuite.com/dxlabwiki/Multimode_Setup>

73,

Dave, AA6YQ

Re: New WAZ Functionality potential errors

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 8:47 AM
To: dxlab@...
Subject: RE: [dxlab] New WAZ Functionality potential errors

By curious I mean odd, strange, huh? Why only one on 6, why not all? Why one on 12? I have lots more on 12.

For Mixed WAZ, DXKeeper's submission generator will pick the most recent confirmed QSO for a zone.
The WAZ band/mode selection is SSB, CW and bands 80, 40, 20, 15, 10.

I will try it again only this time using the 5 band WAZ option.

After selecting just the 5BWAZ option, with no mode selected (which should then be mixed based on the options) and just lotw
selected, I get 210 selected. Again, with some duplicates and a 12 meter QSO.

There should not be any duplicates of a zone. It would be like submitting duplicate countries for DXCC.

For 5BWAZ, there should be 5 QSOs submitted for each zone.
With your 5BWAZ submission still intact, please place your log file in a zip archive, attach the archive to an email message, and
send it to me via

aa6yq (at) ambersoft.com

so I can see what's going on.
73,

Dave, AA6YQ

No Receive in WinWarbler

Alan Swinger
 

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: SmartSDR V2 and DXLabs on remote client

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, December 19, 2017 9:50 AM
To: dxlab@...
Subject: Re: [dxlab] SmartSDR V2 and DXLabs on remote client

If you have a working SmartLink configuration when being remote from your 6000 series you should be able to have DXlabs working. Keep in mind without DAX being a part of SmartLink you will be limited to Phone and CW (only CWX possibly).

With SmartCAT connected via SmartLink you are presented with your CAT ports, So it should be as simple as configuring Commander for those ports you have configured.

I have tested this configuration utilizing my Dad’s (N6XT) 6500 in Southern California with me being in Northern Colorado. Please feel free to drop me a line off-list for details.

Thanks for the testing and report, Ron!
John, step-by-step instructions are here:
<http://www.dxlabsuite.com/dxlabwiki/FlexSignature>

73,

Dave, AA6YQ

Trying to ID a signal that is always there

Gilbert Baron W0MN
 

On 40 Meters I see a double peak in the spectrum that looks a lot like it is RTTY, but it is not. It is a double peak at 7037.95 and 7037.78 or very close to that. Has anyone else seen this and if so knows what it is. I cannot decode anything with FT8, RTTY, or PSK31

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

Printer settings - QSL card size

Ignacio Martinez
 

Hi to all,

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

How can I define a custom size? 
Can use the option “user-defined” to get it? How can I set it up?


Thanks in advance ;-)


73 de Ignacio, EA4OR

Re: SmartSDR V2 and DXLabs on remote client

Ron Rosson
 

John,

If you have a working SmartLink configuration when being remote from your 6000 series you should be able to have DXlabs working. Keep in mind without DAX being a part of SmartLink you will be limited to Phone and CW (only CWX possibly).

With SmartCAT connected via SmartLink you are presented with your CAT ports, So it should be as simple as configuring Commander for those ports you have configured. 

I have tested this configuration utilizing my Dad’s (N6XT) 6500 in Southern California with me being in Northern Colorado. Please feel free to drop me a line off-list for details.

--
73 de KF5JRA
Ron
kf5jra at oneinsane dot org‌

On Dec 19, 2017, at 7:07 AM, runner57us@... [dxlab] <dxlab@...> wrote:

Dave


I have tried different options to get it to work with the SmartSDR V2 - Smartlink and cannot get it to recognize the remote Flex transceiver.

V2 software was released by Flex about 6 months ago.  In addition to other enhancement and fixes it primarily allows Flex owners to operate the Flex 6XXX series tranceivers remotely over the internet without the need for any other software like remote desktops or VPN's.  The SmartSDR software looks and operates the same regardless of the connection being local on your LAN or remote from across the globe using the WAN.  Most Flex users have waited a long time for this functionality and have upgraded the SmartSDR software as a result.

IF you would like additional information and someone to test any beta versions I would be glad to assist.  You can contact me via my email and then if need we can speak live over the telphone.

John K3MA


Re: SmartSDR V2 and DXLabs on remote client

Steve McMullin
 

Dave

I have tried different options to get it to work with the SmartSDR V2 - Smartlink and cannot get it to recognize the remote Flex transceiver.

V2 software was released by Flex about 6 months ago.  In addition to other enhancement and fixes it primarily allows Flex owners to operate the Flex 6XXX series tranceivers remotely over the internet without the need for any other software like remote desktops or VPN's.  The SmartSDR software looks and operates the same regardless of the connection being local on your LAN or remote from across the globe using the WAN.  Most Flex users have waited a long time for this functionality and have upgraded the SmartSDR software as a result.

IF you would like additional information and someone to test any beta versions I would be glad to assist.  You can contact me via my email and then if need we can speak live over the telphone.

John K3MA

Re: New WAZ Functionality potential errors

Pete W1RM
 

By curious I mean odd, strange, huh?  Why only one on 6, why not all?  Why one on 12?  I have lots more on 12.

 

The WAZ band/mode selection is SSB, CW and bands 80, 40, 20, 15, 10.

 

I will try it again only this time using the 5 band WAZ option.

 

After selecting just the 5BWAZ option, with no mode selected (which should then be mixed based on the options) and just lotw selected, I get 210 selected.  Again, with some duplicates and a 12 meter QSO.

 

There should not be any duplicates of a zone.  It would be like submitting duplicate countries for DXCC.

 

I can see this if there is some question about the validity of a QSL but given the option is only lotw there should be no question about the validity.

 

 

Pete, W1RM

W1RM@...

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, December 18, 2017 4:59 PM
To: dxlab@...
Subject: RE: [dxlab] New WAZ Functionality potential errors

 

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, December 18, 2017 9:42 AM
To: dxlab@...
Subject: [dxlab] New WAZ Functionality potential errors

I tried going through the steps of a WAZ submission using just LoTW in anticipation of the release of that by ARRL.

When I run the create submission report, I get some curious entries. For example, the overall report says 211 entries. One on 6,
one on 12,

>>>I don't understand what's curious about "One on 6, one on 12". Please explain.

duplication of a zone on a band, one phone, one cw.

>>>The WAZ family of awards includes zone-band-mode combinations; if you've enabled pursuit of these, then submitting confirmed QSOs
for the same band with different modes would be appropriate.

>>>What boxes are checked in the "WAZ Bands & Modes" panel on the Configuration window's Awards tab?

73,

Dave, AA6YQ