Date   
Re: Merry Christmas and Happy Hanukkah to all who celebrate

Ed Douglass
 

And we owe you a tone of thanks for an excellent suite of programs and an outstanding level of support!  Do you ever sleep?


On Mon, Dec 23, 2019, 1:47 PM Dave AA6YQ <aa6yq@...> wrote:
I wish you a 2020 full of happiness, excellent health, and good DX!

I could not be happier with the way this discussion group works; your continuing contribution to its friendliness, responsiveness,
and accuracy are greatly appreciated!

        73,

              Dave, AA6YQ






Re: Merry Christmas and Happy Hanukkah to all who celebrate

ray cathode
 

Dave,


It's your continued patience and knowledge that helps keep this group friendly and a pleasure to be a apart of.

We all make mistakes and have questions but there is always someone to guide us..



73's to all

es Happy Holidays.


Kudos


W9RF - Joe






On Monday, December 23, 2019, 1:47:54 PM CST, Dave AA6YQ <aa6yq@...> wrote:


I wish you a 2020 full of happiness, excellent health, and good DX!

I could not be happier with the way this discussion group works; your continuing contribution to its friendliness, responsiveness,
and accuracy are greatly appreciated!

        73,

              Dave, AA6YQ

       




Re: Sending Real CW

Mark Robinson
 

Thank you for the information

Looking at my WW configuration

All I have set in the CW  Keying Section is

PTT port (com8)    DTR


So maybe it is defaulting to CAT control ?   It works well.

My Icom control ports are Com 7 and Com 8



73 Mark N1UK

On 23-Dec-19 2:42 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration. I will take a closer look at the my configuration.

+ See step 1.f in

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

+ Transceivers that can be directed to transmit CW by sending them CAT commands are listed in step 5.b of

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

+ Commander can be directed to transmit text in CW by conveying it to a capable transceiver via CAT commands, but I don't know of any applications other than WinWarbler that are exploiting this capability.

73,

Dave, AA6YQ



Merry Christmas and Happy Hanukkah to all who celebrate

Dave AA6YQ
 

I wish you a 2020 full of happiness, excellent health, and good DX!

I could not be happier with the way this discussion group works; your continuing contribution to its friendliness, responsiveness,
and accuracy are greatly appreciated!

73,

Dave, AA6YQ

Re: Sending Real CW

Dave AA6YQ
 

+ AA6YQ comments below

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration. I will take a closer look at the my configuration.

+ See step 1.f in

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

+ Transceivers that can be directed to transmit CW by sending them CAT commands are listed in step 5.b of

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

+ Commander can be directed to transmit text in CW by conveying it to a capable transceiver via CAT commands, but I don't know of any applications other than WinWarbler that are exploiting this capability.

73,

Dave, AA6YQ

Re: Sending Real CW

Mark Robinson
 

I am not sure what I configured in WW but it certainly works well...it was a painlesss configuration.  I will take a closer look at the my configuration.

73 Mark N1UK

On 23-Dec-19 2:25 PM, Andrew OBrien wrote:
When I send CW via my 7610 and Winwarbler and Commander I am using CAT command.

Andy K3UK


On Dec 23, 2019, at 2:22 PM, Mark Robinson <markrob@...> wrote:

Hi Dave,

I am running an Icom IC7610 with Win4Icom. Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode. How is it doing it? If I understood what was happening maybe it would help me to configure the other two programs. MultiPSK uses Commander for rig control.


73 Mark N1UK


Re: Sending Real CW

Andrew OBrien
 

When I send CW via my 7610 and Winwarbler and Commander I am using CAT command.

Andy K3UK

On Dec 23, 2019, at 2:22 PM, Mark Robinson <markrob@...> wrote:

Hi Dave,

I am running an Icom IC7610 with Win4Icom. Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode. How is it doing it? If I understood what was happening maybe it would help me to configure the other two programs. MultiPSK uses Commander for rig control.


73 Mark N1UK


Sending Real CW

Mark Robinson
 

Hi Dave,

I am running an Icom IC7610 with Win4Icom.  Commander is connected to the Icom through Win4Icom with no issues


I have been trying to get Fldigi and MultiPSK to send real cw with the rig in the CW mode but have had no luck at all

Winwarbler of course transmits perfect cw with the radio in the cw mode.  How is it doing it?  If I understood what was happening maybe it would help me to configure the other two programs.     MultiPSK uses Commander for rig control.


73 Mark N1UK

Re: DX Keeper not showing confermations

Dave AA6YQ
 

I had a hard drive crash and had to reinstall DX Lab. I imported the ADI file from LOTW but they do not show up as being confirmed. Is there a way that I can get the program to Query LOTW again to get the confirmation in DX Keeper?

+ Re the title of your post: DXKeeper cannot display information not present in your logged QSOs.

+ The ADIF file generated by LoTW when directed to report all submitted QSOs contains relatively little information; see

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

+ If you didn't configure DXKeeper to backup your log after every operating session, and you didn't deploy one of the free backup applications that automatically copy your critical files to the cloud to protect against local disasters, then the ADIF file generated by LoTW is the best you can do.

+ To update your logged QSOs to reflect their acceptance by LoTW and their confirmation by LoTW,

1. On the Main window's "Log QSOs" tab

1a. Click the Filter panel's X button

1b. click the Adv button to display the "Advanced Sorts, Filters, and Modifeers" window

2. On the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" panel

2a. set the "Item name" selector to APP_DXKEEPER_LOTW_QSL_SENT

2b. set the "Item new value" textbox to Y

2c. click the Mod button

3. on the Main window's QSL tab:

3a. set the "QSL Via" panel to LoTW

3b. depress the CTRL key while clicking the "Sync LoTW QS

+ Depending upon how many QSOs you have confirmed in LoTW, step 3b. can take a long while. Consider invoking it before retiring for the evening.

+ When you're finished, read this article:

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

73,

Dave, AA6YQ

Re: SC not showing spots

Dave AA6YQ
 

+ AA6YQ comments below

I currently have NC7J, VE7CC and W7JD spot sources connected to SC. Looking at SC display, it only shows spots from NC7J and every so often from W7JD. I have double checked to make sure VE7CC is connected and it is. (Using 127.0.0.1 and port 7300) If I open VE7CC window, it shows connected and if I double click on one of the entries there, my transceiver QSYs to that frequency, and the Spot Source Status buttons show connected.

If I filter in SC for one of the entries (CALL) that appear in VE7CC window, nothing will display in SC. So it looks like the spot never made it to the SC database.

I have also double checked the filters that I have set in SC Config to make sure I am not excluding anything that way.

Suggestions please.

+ Assuming that a spot arrives from one of SpotCollector's connected Spot Sources, there are several reasons why it might not be used to update your Spot Database -- either by creating a first Spot Database Entry for the spotted station (on the spotted band in the spotted mode) or by updating an existing Spot Database Entry for that station (on the spotted band in the spotted mode):

1. the spot is "too old"

1a. check the "Maximum Age of incoming spots" setting on the Configuration window's "Spot Database" tab; I recommend 60 (minutes)

1b. check that your computer's time and time zone have been set correctly (often the root cause of "no spot database entries" disease after installing SpotCollector on a new computer)

2. the spotted callsign is listed in SpotCollector's "Special Callsign" list with no tag (meaning "ignore incoming spots of this callsign")

3. the callsign of the station that generated the spot is listed in SpotCollector's "Special Callsign" list with a "badsource" tag (meaning "ignore incoming spots generated by this callsign")


+ If an incoming spot does create or update an entry in the Spot Database, its visibility in the Spot Database Display is governed by your filter settings, as described in

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


+ Unless the caption of the Filter panel at the bottom of SpotCollector's Main window is "Filter: None", your view of the Spot Database is being filtered.

+ To remove all filtering from the Spot Database Display, depress the CTRL key while clicking the Filter panel's X button.


+ For more information, see

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

73,

Dave, AA6YQ

DXView and USAP issue

Al Bailey (K8SIX)
 

I got these both resolved. Pays to keep the programs up to date. 😊

 

AND Dave thanks for all the help this year. Like one said, I don’t know when you sleep. Merry Christmas and Happy New Year.

Re: SC not showing spots

Ed Pflueger <ab4iq@...>
 

I kind of have the same problem with 127.0.0.1:7300 on one of my PC’s.  One of mine works fine and the other one doesn’t.  The one that doesn’t work works fine into EI7MRE and the other two.

 

Ed.. AB4IQ

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Rod Greene via Groups.Io
Sent: Monday, December 23, 2019 8:39 AM
To: DXLab Reflector <dxlab@groups.io>
Subject: [DXLab] SC not showing spots

 

I currently have NC7J, VE7CC and W7JD spot sources connected to SC. Looking at SC display, it only shows spots from NC7J and every so often from W7JD. I have double checked to make sure VE7CC is connected and it is. (Using 127.0.0.1 and port 7300) If I open VE7CC window, it shows connected and if I double click on one of the entries there, my transceiver QSYs to that frequency, and the Spot Source Status buttons show connected.

 

If I filter in SC for one of the entries (CALL) that appear in VE7CC window, nothing will display in SC. So it looks like the spot never made it to the SC database.

 

I have also double checked the filters that I have set in SC Config to make sure I am not excluding anything that way.

 

Suggestions please. TIA and 73, Rod/w7zrc

 

Re: SC not showing spots

Ron KU7Y
 

Morning Rod,

 

I use port 23 and address of ve7cc.net and it's working fine for me.

 

OK, back in my hole,

 

Ron, KU7Y

Mountain Home, ID  DN23dc

CW Ops #1211

SKCC #4904

QRP ARCI #8829

SOC #2

Idaho DX Association

Ron@...

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Rod Greene via Groups.Io
Sent: Monday, December 23, 2019 7:39 AM
To: DXLab Reflector
Subject: [DXLab] SC not showing spots

 

I currently have NC7J, VE7CC and W7JD spot sources connected to SC. Looking at SC display, it only shows spots from NC7J and every so often from W7JD. I have double checked to make sure VE7CC is connected and it is. (Using 127.0.0.1 and port 7300) If I open VE7CC window, it shows connected and if I double click on one of the entries there, my transceiver QSYs to that frequency, and the Spot Source Status buttons show connected.

 

If I filter in SC for one of the entries (CALL) that appear in VE7CC window, nothing will display in SC. So it looks like the spot never made it to the SC database.

 

I have also double checked the filters that I have set in SC Config to make sure I am not excluding anything that way.

 

Suggestions please. TIA and 73, Rod/w7zrc

 

 

Virus-free. www.avg.com

DX Keeper not showing confermations

Arthur Gibson
 

I had a hard drive crash and had to reinstall DX Lab. I imported the ADI file from LOTW but they do not show up as being confirmed. Is there a way that I can get the program to Query LOTW again to get the confirmation in DX Keeper?

SC not showing spots

Rod Greene
 

I currently have NC7J, VE7CC and W7JD spot sources connected to SC. Looking at SC display, it only shows spots from NC7J and every so often from W7JD. I have double checked to make sure VE7CC is connected and it is. (Using 127.0.0.1 and port 7300) If I open VE7CC window, it shows connected and if I double click on one of the entries there, my transceiver QSYs to that frequency, and the Spot Source Status buttons show connected.

If I filter in SC for one of the entries (CALL) that appear in VE7CC window, nothing will display in SC. So it looks like the spot never made it to the SC database.

I have also double checked the filters that I have set in SC Config to make sure I am not excluding anything that way.

Suggestions please. TIA and 73, Rod/w7zrc

Re: The end is coming soon

Pit
 

Hi ALL !

În lun., 23 dec. 2019 la 12:13, eddy on5jk <Eddy_on5jk@...> a scris:

Hoi everyone,

I take this moment to thank and congratulate Dave for all the support he
braught to us in 2019 and far before.

Merry Xmas, happy Newyear and please, stay healthy to continue
supporting the most beautifull DXLab program.

To all worldwide users of the splendid program, also best wishes for 2020.

Eddy ON5JK




The end is coming soon

eddy on5jk
 

Hoi everyone,

I take this moment to thank and congratulate Dave for all the support he braught to us in 2019 and far before.

Merry Xmas, happy Newyear and please, stay healthy to continue supporting the most beautifull DXLab program.

To all worldwide users of the splendid program, also best wishes for 2020.

Eddy ON5JK

Re: Update issue?

Dave AA6YQ
 

+ AA6YQ comments below

I notice there are two USAP files in the DXView directory so should I blow one away maybe?

+ I suggest the following procedure

1. reboot Windows

2. in DXView's Databases folder, delete the files USAP.mdb and USAP.ldb (the latter may or may not exist)

3. start the Launcher

4. direct the Launcher to start DXView

5. on the Databases tab of DXView's Configuration window, direct DXView to install the USAP database

73,

Dave, AA6YQ

Re: WW switches from RTTY to CW upon SC click

Dave AA6YQ
 

+ AA6YQ comments below

Andy K3UK

Dave , thanks for your prompt attention to this matter . The revised SC version that you made available has resolved the matter .

+ Thanks for the testing and the report, Andy.

73,

Dave, AA6YQ

Update issue?

Al Bailey (K8SIX)
 

I notice there are two USAP files in the DXView directory so should I blow one away maybe?

 

Thanks

Al Bailey