Date   
Spots not showing up in Spot Collector

Norman Heyen
 

Hi group,

I’m not sure what I nave managed to change but I am no longer getting spots to appear in SC. When I open the individual spot source windows, there are spots showing. But none display in the main SC window.

I’ve hit the ‘X’ button to clear things, there isn’t an entry in the call box. The only filter I have set is the Bands (boxes checked for the bands that I have an antenna for).

 

This has always worked for me in the past but haven’t been on the radio lately so not sure where I went wrong or accidentally checked or unchecked a box.

 

Running SC 7.8.8 on an old XP box. Everything else I use seems to be OK, just SC not doing its thing.

 

Any pointers or suggestions are greatly appreciated.

 

Thanks!

Norman

KC9NVN

Re: Spots not showing up in Spot Collector

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 12:44 PM
To: dxlab@...
Subject: [dxlab] Spots not showing up in Spot Collector

I'm not sure what I nave managed to change but I am no longer getting spots to appear in SC. When I open the individual spot source
windows, there are spots showing. But none display in the main SC window.

I've hit the 'X' button to clear things, there isn't an entry in the call box. The only filter I have set is the Bands (boxes
checked for the bands that I have an antenna for).

This has always worked for me in the past but haven't been on the radio lately so not sure where I went wrong or accidentally
checked or unchecked a box.

Running SC 7.8.8 on an old XP box. Everything else I use seems to be OK, just SC not doing its thing.

Any pointers or suggestions are greatly appreciated.

Take a look at
<http://www.dxlabsuite.com/dxlabwiki/EmptyDatabase>

If that doesn't get you going, please let me know.
73,

Dave, AA6YQ

Re: Spots not showing up in Spot Collector

Danny Douglas
 

Check your computer time and date.  Remember to check AM versus PM.  That catches a lot of people. 

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On February 18, 2018 at 12:43 PM "'Norman Heyen' n.heyen@... [dxlab]" <dxlab@...> wrote:

 

 

Hi group,

I’m not sure what I nave managed to change but I am no longer getting spots to appear in SC. When I open the individual spot source windows, there are spots showing. But none display in the main SC window.

I’ve hit the ‘X’ button to clear things, there isn’t an entry in the call box. The only filter I have set is the Bands (boxes checked for the bands that I have an antenna for).

 

This has always worked for me in the past but haven’t been on the radio lately so not sure where I went wrong or accidentally checked or unchecked a box.

 

Running SC 7.8.8 on an old XP box. Everything else I use seems to be OK, just SC not doing its thing.

 

Any pointers or suggestions are greatly appreciated.

 

Thanks!

Norman

KC9NVN

 


 

Re: CI-V Transceive on/off

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 6:15 AM
To: dxlab@...
Subject: [dxlab] CI-V Transceive on/off


I use IC-7300

RS-BA1 software always set "CI-V Tranceive" ON.

For commander, i need to set "CI-V Tranceive" OFF (else commander take a long time to get the real frequency, when i turn the vfo).

So, my isea is to set "CI-V Tranceive" OFF on "Initial command" on commander. Should-it be a good way ?

I look on the icom documentation about IC-V command, i did not found information to set "CI-V Tranceive" OFF.

I'm not aware of any Icom transceiver that provides a CI-V command to enable/disable the "CI-V transceiver" option.
When an Icom transceiver's "CI-V transceiver" menu setting is enabled, any change you make to the transceiver's frequency or mode via its front panel result in a CI-V message being sent to all other devices connected to the same CI-V bus. There are two problems with this:
1. Any other transceivers connected to the same CI-V bus will QSY to the same frequency and mode, which may not be what you want

2. The CI-V messages sent by the transceiver may collide with CI-V messages that Commander continuously sends, directing the radio to "report your frequency", "report your mode", "report your RX bandwidth", "report your RX/TX status", "report your S-meter reading", etc.

If you must keep "CI-V Transceive" enabled, then enable the "Verify CI-V command acceptance" option on the Configuration window's General tab. This will cause Commander to wait for a positive acknowledgement from the transceiver after sending any CI-V command to "change state", e.g. "QSY to 7011", or "change mode to RTTY", or "switch from RX to TX"; if no such acknowledgement is received because the command was damaged by a collision, Commander will re-send the command.
I cannot guarantee that the "Verify CI-V command acceptance" option will enable reliable operation with your transceiver's "CI-V Transceive" menu setting enabled. I have only tested the "Verify CI-V command acceptance" option with the few Icom transceivers that I own, and not for long periods of time. Every Icom transceiver is different, and incompletely documented. I can only assure that Commander will reliably control an Icom transceiver if that transceiver's "CI-V transceiver" menu setting is disabled.
73,

Dave, AA6YQ








Is someone foud the right code, or have an idea ?

TNX

73, f1ghy, patrice







<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: Icom 7851 USB settings for ports

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 12:37 PM
To: dxlab@...
Subject: [dxlab] Icom 7851 USB settings for ports

This has probably been brought up and answered before but not able to find any info it seems. Sorry if it has been. I am trying to run Commander and other associated apps from here. The problem seems when I try to use WSJTx or JTDX even with different Comm ports set in the USB driver settings in windows no luck.I get message either portin use or not able to even use what should be an available working port I see in windows. In my case I see Comm 5 and 6 installed with the Icom drivers for USB. Are there settings I maybe missing?

When you want WSJT-X to interoperate with DXLab, configure WSJT-X to use Commander as its "PTT method". This is step 2.b.iii in the WSJT-X section of
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>

Doing so will eliminate an conflicts over the use of COM ports.
73,

Dave, AA6YQ

reminder: still looking for someone with an IC-7850 or IC-7851...

Dave AA6YQ
 

...that is connected to your computer with via a standard USB A-B cable.

Both of these radios should support Commander's "Spectrum-Waterfall" window:

<http://www.dxlabsuite.com/commander/Spectrum-Waterfall-Dark-Spectrum.jpg>

IC-7300 and IC-7610 users have reported success with this window, but no one has yet reported success or failure with an IC-7850 or
IC-7851.

Step-by-step instructions are here:

<http://www.dxlabsuite.com/dxlabwiki/SpectrumWaterfallIcom>

Please post your experience here.

73,

Dave, AA6YQ

Re: reminder: still looking for someone with an IC-7850 or IC-7851...

Gennady Kupinsky
 

Hi

 

I have tried Commander's "Spectrum-Waterfall" with mi IC7851.

Works great.

Many thanks!

 

Regards,

Gennady, RM3DA

 

 

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 10:52 PM
To: dxlab@...
Subject: [dxlab] reminder: still looking for someone with an IC-7850 or IC-7851...

 

 

...that is connected to your computer with via a standard USB A-B cable.

Both of these radios should support Commander's "Spectrum-Waterfall" window:

<http://www.dxlabsuite.com/commander/Spectrum-Waterfall-Dark-Spectrum.jpg>

IC-7300 and IC-7610 users have reported success with this window, but no one has yet reported success or failure with an IC-7850 or
IC-7851.

Step-by-step instructions are here:

<http://www.dxlabsuite.com/dxlabwiki/SpectrumWaterfallIcom>

Please post your experience here.

73,

Dave, AA6YQ

Re: reminder: still looking for someone with an IC-7850 or IC-7851...

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 3:11 PM
To: dxlab@...
Subject: RE: [dxlab] reminder: still looking for someone with an IC-7850 or IC-7851...

I have tried Commander's "Spectrum-Waterfall" with mi IC7851.

Works great.

Many thanks!

Excellent. Thanks for letting me know, Gennady!
73,

Dave, AA6YQ

Re: MSWINSCK.OCX is missing or one of it's components is missing

Richard Lauer
 

I'm having the same issue as Joe. Moved to a newer computer (Windows 7) and I'm now receiving an error message (DXKeeper Error Message: DXKEEPER File: Unable to confirm QSO logged). I also note that DXKeeper's Display Error Log indicates that there is an issue with component MSWINSCK.OCX, which is located in the DXKeeper files.


All other features of DXKeeper appear to be working, manual logging and connecting with LoTW.


Any advise to help resolve the connection with WSJT-X and JTAlertX would be appreciated.


Richard

K9THB 

ps: On JTAlert's Applications Test, DXLabs Applications indicate that DXKeeper is "Running" and DDE connect is "Connected"

Strange actions using DXLab

Bill Flaherty
 

I keep my computer running and let the monitors go to sleep. When I activated my 2 monitors today I witnessed some bizarre goings on.  Dxk, dxv, pf and sc were all in use when I quit last night.  Today the DXV window was cycling thru calls similar to what SC does and the progress chart was also keeping up with the changing call signs.  I assume that the calls are being generated by incoming spots on SC.  DXK was not changing in any way.   The SC window was not populated although I could see the incoming Q's in the top left changing rapidly due to lots of activity in the ARRL DX Test.  All four sources were green.  I had set the filter for "Needed" but changed it to Band, Mode, Origin age <30 minutes.  Not change seen.

I went to DXLab Launcher it said "SC starting" but nothing was happening.  I could not terminate DXLab with Launcher.

I shut down W10 and waited 5 minutes and rebooted the computer and started DXLab again with Launcher.  All previous apps were started. SC is behaving normally but DXV is again changing like it is SC.  I happened to input one of the changing calls seen in DXV and inputted it into SC  to see if it was one of the calls seen in DXV and it was.  This action also stabilized DXV  and stopped the cycling .  When I removed the specific call filter from SC the cycling of DXV returned.

Any ideas what is going on?

WinWabbler and Icom IC-7610

bill leger
 

I have commander working perfectly with my IC- 7610 but can't get it working in WinWabbler. I get a message ( 2tone unable to open FSK port, com port unavailable). I'm sure it's more than that, any ideas??? I would like to use PSK and RTTY. Radio is going to TX but on sound out ( moni is on) is there a internal connector setting in the radio I'm missing.

Re: Strange actions using DXLab

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 4:50 PM
To: dxlab@...
Subject: [dxlab] Strange actions using DXLab

I keep my computer running and let the monitors go to sleep. When I activated my 2 monitors today I witnessed some bizarre goings on. Dxk, dxv, pf and sc were all in use when I quit last night. Today the DXV window was cycling thru calls similar to what SC does and the progress chart was also keeping up with the changing call signs. I assume that the calls are being generated by incoming spots on SC. DXK was not changing in any way. The SC window was not populated although I could see the incoming Q's in the top left changing rapidly due to lots of activity in the ARRL DX Test. All four sources were green. I had set the filter for "Needed" but changed it to Band, Mode, Origin age <30 minutes. Not change seen.

I went to DXLab Launcher it said "SC starting" but nothing was happening. I could not terminate DXLab with Launcher.

I shut down W10 and waited 5 minutes and rebooted the computer and started DXLab again with Launcher. All previous apps were started. SC is behaving normally but DXV is again changing like it is SC. I happened to input one of the changing calls seen in DXV and inputted it into SC to see if it was one of the calls seen in DXV and it was. This action also stabilized DXV and stopped the cycling . When I removed the specific call filter from SC the cycling of DXV returned.

Any ideas what is going on?

In the General panel on the General tab of SpotCollector's Configuration window, is the "Automatic DXView lookup" option enabled? If so, disable it.
73,

Dave, AA6YQ

Re: WinWabbler and Icom IC-7610

Dave AA6YQ
 

AA6YQ comments belo-w
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 4:55 PM
To: dxlab@...
Subject: [dxlab] WinWabbler and Icom IC-7610

I have commander working perfectly with my IC- 7610 but can't get it working in WinWabbler. I get a message ( 2tone unable to open FSK port, com port unavailable). I'm sure it's more than that, any ideas??? I would like to use PSK and RTTY. Radio is going to TX but on sound out ( moni is on) is there a internal connector setting in the radio I'm missing.

WinWarbler only uses the 2Tone engine for RTTY demodulation. 2Tone is not used for RTTY transmission. Thus you should not configure i2Tone to use a COM port for FSK.
Step-by-step instructions are here:
<http://www.dxlabsuite.com/dxlabwiki/ConfigureRTTY>

73,

Dave, AA6YQ

Re: Kosovo

N4KW Pete
 

Hi Dave,  Do you remember when the Quatra (sp.) first came out.  A couple for sale on QTH.com but they both want 4K, I'd say their price is holding up.
73, Pete

On 2/2/2018 3:19 PM, 'Joe Subich, W4TV' lists@... [dxlab] wrote:
 


Have you done the "recompute" step in the change log for the DXCC
Database update? See:


73,

.... Joe, W4TV

On 2/2/2018 3:04 PM, k0rs@... [dxlab] wrote:
> Anybody else having trouble with DXK recognizing Z6?
>
>
> My country code (522) flashes red and the entry can't be saved.
>
>
> Yes, it's the latest version.
>
>
> K0RS
>


Three Requests

Dave AA6YQ
 

1. If you haven't backed up your DXLab settings and critical DXLab files, please do so, as described step-by-step in

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


2. After permanently changing a DXLab application's settings, direct the Launcher to update your backed up settings, as described in
the "Saving the Windows Registry Settings of One Selected DXLab Application to a Workspace" section of

<http://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace>


3. If a DXLab application that had been functioning correctly suddenly and inexplicably stops functioning correctly, terminate the
application, and direct the Launcher to restore the application's settings from the Workspace created in step 2 above, as described
in the "Loading the Windows Registry with One Selected DXLab Application's Settings from a Workspace" section of

<http://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace>

If the restarted application still does not function incorrectly, reboot Windows into "Safe Mode with Networking" and start the
application. If it now works correctly, then configure your anti-malware applications to consider each of your DXLab applications to
be "Safe", and then reboot Windows normally.

73,

Dave, AA6YQ

Re: Spots not showing up in Spot Collector

Norman Heyen
 

Thank you Danny –

 

Got it in one, the time was off by 12 hours. Kind of surprising since I have the Dimension 4 app installed. But the default setting is to only correct for a 2 hour difference.

 

Once I got the time set correctly, all is well again.

 

73,

Norman

KC9NVN

 

From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 01:03 PM
To: dxlab@...
Subject: Re: [dxlab] Spots not showing up in Spot Collector

 

 

Check your computer time and date.  Remember to check AM versus PM.  That catches a lot of people. 

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On February 18, 2018 at 12:43 PM "'Norman Heyen' n.heyen@... [dxlab]" <dxlab@...> wrote:

 

 

Hi group,

I’m not sure what I nave managed to change but I am no longer getting spots to appear in SC. When I open the individual spot source windows, there are spots showing. But none display in the main SC window.

I’ve hit the ‘X’ button to clear things, there isn’t an entry in the call box. The only filter I have set is the Bands (boxes checked for the bands that I have an antenna for).

 

This has always worked for me in the past but haven’t been on the radio lately so not sure where I went wrong or accidentally checked or unchecked a box.

 

Running SC 7.8.8 on an old XP box. Everything else I use seems to be OK, just SC not doing its thing.

 

Any pointers or suggestions are greatly appreciated.

 

Thanks!

Norman

KC9NVN

 


 

ADIF for LOTW submission

Ed K0iL
 

I must be missing something on ADIF for LOTW submissions as I'm still new to some DXLab stuff I haven't used yet. 


After the ARRL DX contest weekend, I used DX Keeper's Export QSOs to create or Export ADIF for LOTW for this weekends QSO.  However, a look at the ADIF created shows it has a lot more log data in there than what I have seen on other ADIF logs submitted by other logging programs.  Not just the basic QSO data, but it seems to have all my DX Keeper data in the ADIF file, most of which is not necessary for an LOTW submission.


Is this normal for DX Lab?  

Or did I do something wrong for LOTW ADIF file creation?  


Thanks for setting me straight on this.  


73, de ed -K0iL


Re: ADIF for LOTW submission

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, February 18, 2018 7:58 PM
To: dxlab@...
Subject: [dxlab] ADIF for LOTW submission

I must be missing something on ADIF for LOTW submissions as I'm still new to some DXLab stuff I haven't used yet.

After the ARRL DX contest weekend, I used DX Keeper's Export QSOs to create or Export ADIF for LOTW for this weekends QSO. However, a look at the ADIF created shows it has a lot more log data in there than what I have seen on other ADIF logs submitted by other logging programs. Not just the basic QSO data, but it seems to have all my DX Keeper data in the ADIF file, most of which is not necessary for an LOTW submission.

Is this normal for DX Lab?

Or did I do something wrong for LOTW ADIF file creation?

"Export ADIF for LoTW" is identical to "Export ADIF" with some additional functionality, as described in
<http://www.dxlabsuite.com/dxkeeper/Help/Export.htm#Exporting to LotW>

Manually filtering the Log Page Display, using "Export ADIF for LoTW" to generate an ADIF file, and then invoking TQSL is a manual approach that ignores DXKeeper's automation of this process. Take a look at
<http://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing via LotW>

73,

Dave, AA6YQ

Can't open my log mdb file direct only via Launcher

Jay Kobelin <pcb4u@...>
 

I have a file I now save using DXkeeper while running the Suite. 

Launcher opens it fine but when DXKeeper is launched by itself I get an error about "....specified log QSL Queue contains more fields...."

I have the latest  error log for DXkeeper

Tnx
73
Jay
W2IJ

DXWATCH

Arthur Petteway
 

What is the port setting to use for DXWATCH.com SC setup ?