开云体育

Rien

I am not sure I understand your problem.? ?I have run DXLab with CW skimmer for many years.

Is your problem the time it takes for the programs to start or clicking on a call in CW Skimmer and having DXKeeper recognize the call.

What program do you use to link CW skimmer and DX keeper

Don
WB6BEE

On Sat, Mar 7, 2020 at 03:23 PM, Joe Subich, W4TV wrote:

Have you checked "Realtime Award Progress" in DXKeeper -> Config ->
WAZ Bands & Modes?

Yes, in the WAZ Bands & Modes panel I have checked:
- Digi
- All bands from 80M to 10M
- Realtime Award Progress"

But nothing else.

Hello,?
I using for a long time DXLab with my CWSkimmer? with Com0Com software.
Neve has any problem
Till last? 2 weeks When I start te launcher and also CWSkimmer than it take more than 40 sec if? dxkeeper is start.
when I search a call in DXKeeper it takes 30 sec.
If I close CWSkimmer than it is 7 sec and the call is found in DXKeeper.
Are there more users of DXLab and CWSkimmer who have problems with this?
I'm know that? it is easy to say than CWSkimmer is not good but i have Alex also send a mail with this same issue.
but I hope there is? some one who have a idea? to fix this problem?
Using Win10 64 bite?
16 GB Ram I7 Proccesor
Much enough i.m.o to work with dxlab
When I try is with a other program FLDigi, MixW cwskimmer just works fine.
So there is a connection between CWSkimmer and DXLab that is bad.

Tnx?
Rien, PA7RA?

+ AA6YQ comments below

I was a little too quick on the trigger with my last post. I just had a satellite come over and set up to track it and discovered that the mode being sent from the Secondary Port to SDR Console is the mode of "VFO A", which in this case is the uplink rather than the downlink mode; LSB rather than USB in this case due to the inverting transponders of the linear satellites. Everything else seems to be just fine.

+ Enabling the Secondary CAT port to track the IC-9700's VFO B will require a further extension to Commander that I will not implement until I return home and have access to a radio.

73,

Dave, AA6YQ

Here’s the message in the file containing the information reported by LoTW when you directed DXKeeper to invoke its “Sync LoTW QSLs” operation:

“You must have been issued a certificate before you can log on to the LoTW site.”

See

<>

73,

Dave, AA6YQ

Thank you both Dave & Mike for the info and help.? ??
--
73, de ed -K0iL
Omaha, NE

+ AA6YQ comments below

Also, which way to create an override list is the least risk to my existing logbook data?
Club Log would make it easy, but would it possibly change any of my existing data in my log book?

+ Overrides have no impact on already-logged QSOs. DXKeeper only consults the override list when logging a new QSO, or when importing QSOs (with the appropriate import option enabled).

73,

Dave, AA6YQ

+ AA6YQ comments below

Sounds like temporary Override should work in the DXK log.

+ DXView's Override list is consulted by SpotCollector, DXKeeper, and DXView.

How often do we need to press the recompute button on the Spot Collector for it to get it's info from the override as well? Just once?

+ Directing SpotCollector to "recompute" once is sufficient after you download new overrides or modify existing overrides.

73,

Dave, AA6YQ

+ AA6YQ comments below

Just got back and loaded up Commander test file 14.4.4 and tested it with SatPC32 and SDR Console 3.0.20 and it works perfectly! SDR Console follows either the uplink or downlink and doppler updates as selected in Commanders Ports tab.

For anyone wanting to do this, I used Com0Com to create a pair of virtual ports and assigned one of them to SDR Console by checking the appropriate Com port in the CAT Port Selection menu. The other port of the pair goes to Commanders secondary CAT Serial Port section. SDR Console uses Kenwood protocol so that is selected in Commanders Seondary CAT Protocol window. I use 57600 baud as this is what SDR Console wants and then enable the secondary port and you should be working. Just select which of the frequencies you want SDR Console to track; uplink or downlink.

+ Thanks for the testing, Joe. Note: this is not yet a public release, as there is more regression testing to do when I return home and regain access to a radio; if anyone else would like to try it, please send email via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

Hi Dave,

I was a little too quick on the trigger with my last post.? I just had a satellite come over and set up to track it and discovered that the mode being sent from the Secondary Port to SDR Console is the mode of "VFO A", which in this case is the uplink rather than the downlink mode; LSB rather than USB in this case due to the inverting transponders of the linear satellites.? Everything else seems to be just fine.

Joe W4WT

Also, which way to create an override list is the least risk to my existing logbook data???
Club Log would make it easy, but would it possibly change any of my existing data in my log book???

--
73, de ed -K0iL
Omaha, NE

Thanks Dave!??

Sounds like temporary Override should work in the DXK log.

How often do we need to press the recompute button on the Spot Collector for it to get it's info from the override as well?? Just once???

I'll use override on the next ambiguous DXpedition callsign I am chasing.??
--
73, de ed -K0iL
Omaha, NE

Hi Dave,

Just got back and loaded up Commander test file 14.4.4 and tested it with SatPC32 and SDR Console 3.0.20 and it works perfectly!? SDR Console follows either the uplink or downlink and doppler updates as selected in Commanders Ports tab.

For anyone wanting to do this once the public version becomes available, I used Com0Com to create a pair of virtual ports and assigned one of them to SDR Console by checking the appropriate Com port in the CAT Port Selection menu.? The other port of the pair goes to Commanders secondary CAT Serial Port section.? SDR Console uses Kenwood protocol so that is selected in Commanders Seondary CAT Protocol window.? I use 57600 baud as this is what SDR Console wants and then enable the secondary port and you should be working.? Just select which of the frequencies you want SDR Console to track; uplink or downlink.

Dave, thanks a lot for your quick enhancement to a great program!

73,

Joe W4WT

Hi Dave,

Just saw this and downloaded the modified version of Commander.? I have a couple of errands to do before I can test it but will check it out this afternoon and provide feedback here.

Thanks,

Joe W4WT

+ AA6YQ comments below

I have a new problem. It started with trying to sync LOTW QSL's in DXKeeper. It was working fine and then I started getting a message that the program was not responding.

+ The words "not responding" in a Main window's title bar are Windows-speak for "waiting for input or output"; they do not necessarily mean that there's a problem.

I am not sure what happened then but now it says LOTW responded but not with qsl data.

+ That error message typically means that the LoTW username and/or password specified on the "QSL Configuration" window's LoTW tab are incorrect, so LoTW responded with a "can't login" message instead of with the expected QSL information.

I have a box that ask that I check my account name and password in LOTW QSL configuration. I had checked and that information is correct.

+ In DXKeeper's Databases folder, there is a file named

LoTW_QSLs_ADI.txt

+ So that I can see what's going on, please attach this file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

On 2020-03-07 4:30 AM, Markku SM5FLM wrote:

As the title says, new CQ/WAZ zones are not shown as "Needed" in SC.
(New DXCC entities are shown ok).
I have tried to look at settings but I can't see what is wrong.

Have you checked "Realtime Award Progress" in DXKeeper -> Config ->
WAZ Bands & Modes?

What bands/modes are checked in DXKeeper-> Config -> WAS Bands & Modes?


73,

... Joe, W4TV

On 2020-03-07 8:10 AM, n4qwf . wrote:

I have a new problem. It started with trying to sync LOTW QSL's in
DXKeeper. It was working fine and then I started getting a message
that the program was not responding. I am not sure what happened then
but now it says LOTW responded but not with qsl data.

This is typically the case when the login to LotW fails.

I can log a QSO with WSJT or the capture window and it is saved to
DXKeeper and uploaded to LOTW as usual.

The upload does not require a log-in.

To save Dave, AA6YQ a response:

1) is an Errorlog.txt file present in your DKeeper directory? If so,
rename it errorlog.old

2) In Config -> General check the "Log debugging information" box

3) Attempt a "Sync LotW QSLs" operation

4) Uncheck the "Log debugging information" box

5) Send the new Errorlog.txt file *to DAVE at aa6yq@...*

73,

... Joe, W4TV


On 2020-03-07 8:10 AM, n4qwf . wrote:

I have a new problem. It started with trying to sync LOTW QSL's in DXKeeper. It was working fine and then I started getting a message that the program was not responding. I am not sure what happened then but now it says LOTW responded but not with qsl data. I have a box that ask that I check my account name and password in LOTW QSL configuration. I had checked and that information is correct. All other functions of DXKeeper seem to be working all OK. I can log a QSO with WSJT or the capture window and it is saved to DXKeeper and uploaded to LOTW as usual. I tried rebooting the computer with no luck. I tried to boot in safe mode but it seems that when the Windows 10 PRO operating system was installed in my PC there was a bit code established and since it was done by someone else I can't access it. Why does Windows always seem to fight you when you have a problem?
Any ideas greatly appreciated. <<John

+ AA6YQ comments below

As the title says, new CQ/WAZ zones are not shown as "Needed" in SC.
(New DXCC entities are shown ok).
I have tried to look at settings but I can't see what is wrong.

+ Please make a screen shot showing the Awards tab of DXKeeper's Configuration window, attach the screen shot to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ