Date   

SpotCollector & "unknown" callsigns

Brian Smithson <n8wrl@...>
 

I'm confused about how SpotCollector does (or doesn't) determine DXCC from a callsign that I have logged.

TO2SP is FJ (this time.) The first time I saw it spotted, DXCCPfx was ? and DXCCCountry was blank.

I worked them and learned they were FJ, so I logged them that way.

Spots continue to stream by and all of them are still "unknown" with blanks and question marks. 

Short of adding this as a special callsign, can I tell SpotCollector to consult my log to get the country from a call it can't otherwise determine?

I realize the TO's are funky and that very same call might be somewhere else in the future...

Thank you, and 73!

-Brian n8wrl


Frequent recompute

ghassan chammas
 


Hi dave

I have some 4000 qsos in dxkeeper. However i have realized lately the following:
1.   after a session of dxing, 
2. and properly logging all qsos, and after i terminate all dxlab suite, shut down pc and radio gear, 
3. When i start another session after a random time (hours or days) when i start dxlab i realize that almost all my directly last session's qsos do not appear on the keeper log.
4. I hit recompute on the progress tab and behold, all the qsos appear properly.

This is a new situation for me.
Is it a normal behaviour due to the 4000 qsos?
Did i untick or tick something by mistake?
How can i remedy this situation?

Thank you
73
Od5ya
Ghassan



Sent from Samsung tablet.


Re: SpotCollector

n7bv@...
 

GD ART,

Thanks for the help - it is working again.

All this started a few months back when I moved everything to a new computer - guess some of the settings did not transfer.

Slowing been correcting things around here.

Tks, 73 and cu in the pileups.   Chuck N7BV


CW with WW

Gilbert Baron W0MN
 

If I use an external modem to copy CW the copied data is in the receive panel.

Is there a way I can use the keyboard and have the code I am copying by ear appear in the panel or would I have to just use an open word document or the like and copy it there. If I cannot copy by ear and type the data so that it shows in the receive panel then the operations like double click the call sign to fill in the received data call field would not be usable.

 

Copy by writing it down is tiring and error prone , especially at higher speeds. My writing is not very legible above 20WPM. 😊

 

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

 


Success: Remoted TS-2K with Commader and WSJTx

captcurt2000
 

So made an FT-8 contact today from work via internet remote.  Set-up was:  TS-2000, local PC Pentium dual core 2.8GHz running XPpro SP3. USB audio card eMU 0204.  HB audio and PTT interface.  PTT via serial com2.  Com1 to CAT port. 

Set-up DxLab Commander + several additional sequences and sliders for more rig control.  WSJT-working CAT thru Commander and PTT hard control using RTS out of com2 to the aux port on the TS2K.

Remote desktop from Teamviewer from remote Win7pro machine.  Local router configured for port forwarding and wake on LAN to bring local machine out of standby.  Commander controls power on/off to rig. 

Works as it should except the Teamviewer screen on the remote PC is not optimized for larger monitor.

MS Remote Desktop Connection works also EXCEPT NO decodes from WSJTx.  Only cluse is that on the remote display, the 15s period markers on the waterfall vary in spacing and get narrow.  THe signals are all there, no config changes, etc but no decodes.   Switch back to Teamviewer and it works again. 

Not sure why this is but still looking at it.  Maybe some internal timing problem on the local machine.

Still need to investigate echoing audio to the remote and setting up a USB controlled main power control for the 12V rig PS.

Commander was easy to add third party sequences to the panel.  Still need to add a few like Tune and AGC OFF but not too hard. 

Thanks to those who offered guidance.

Any input on the RDP no decode issue welcomed.

Curt  KU8L



Spot Collector Not displaying spots

James Aprile
 

I have been running DXlabs for years and recently Spot collector has stopped displaying the spots.

1) I have tried prior versions...no joy

2) I have uninstalled and reloaded spot collector...still no spot display


Please note that all other aspects of spot collector are running but no spots are displayed on the spot collector or on the world map of Pathfinder.


3)I have tried to manually enter the fields in spot collector configuration but they will not enter.

4) is there a reset of the spot collector spot display to reacquire the spots ? if so where?

5) I have tried to restore in Commander...no joy

6) is this a registry problem? if so how to repair.


I sure could use a little push in the right direction.  The computer in use is dedicated to the radio and is not used for anything else...windows 10 home.


Thank you for the bandwidth...


Jim K5KND



Re: Commander and WSJT-x Question

Scott
 

It is set to USB.


Re: Commander and WSJT-x Question

g4wjs
 

Hi Scott,

what do you have selected for the WSJT-X "Settings->Radio->Mode" option?

73
Bill
G4WJS.


Commander and WSJT-x Question

Scott
 

I just recently configured my Kenwood TS 590s rig so WSJT-x is controlled by Commander sharing CAT control with the USB. I really like this due to the fact my rig is at a remote location. I can use User-defined controls like Tune, CW-T, NR/NB, Power, etc. 


One thing that I'm wondering can be changed is when I switch bands, for example, to 1,840 for FT8, Commander changes the mode to LSB. Is there a way to let Commander know that WSJT-X stays on USB mode no matter the band? It may not be possible because when I click on SpotCollector, I still want it to change modes depending on the spot. 


Scott

KN3A


Re: DX Commander problem?

ihl.grange@...
 

Dave

Many thanks

That will teach him (and me!) to read manuals!

73

Ivor
MM0IEL



Re: Pathfinder: "Out of memory on line: 1" popup

Björn SM7IUN
 

So I am not alone. Thanks Danny.

73,

Björn SM7IUN


2017-11-16 23:02 GMT+01:00 Danny Douglas n7dc@... [dxlab] <dxlab@...>:

 

I did a manual check and its te4lling me the web page is out of memory.


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 November 16, 2017 at 4:46 PM "Björn Ekelund bjorn@... [dxlab]" <dxlab@...> wrote:

 

 

Is it just me who are getting an error popup when looking at DK7LX's QRZ entry via Pathfinder?

I am running Windows 10 Pro.

73,

Björn

 


 



Re: Progress data wrong after edit qso

Dave AA6YQ
 

The behavior Art PA3Creported is in fact the result of a defect in DXView. I have corrected this defect in the next version of DXView and sent this new version to Art and to Iain N6ML for assessment.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, November 14, 2017 4:54 AM
To: dxlab@...
Subject: RE: [dxlab] Progress data wrong after edit qso

*** More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, November 13, 2017 10:39 AM
To: dxlab
Subject: Re: [dxlab] Progress data wrong after edit qso


You changed a QSO's DXCC DXCC entity from "Norfolk Island" to "Australia". Having the "Automatically recompute realtime award tracking" box checked caused DXKeeper to automatically recompute the progress for "Norfolk Island", but it will not automatically recompute the progress for Australia. When you change a logged QSO's DXCC entity, you must invoke the Recompute function.
Is there any reason it couldn't automatically recompute both? Aside from the user needing to know to do it, the down-side is that (AFAIK) there's no way for a user to invoke recompute for a single entity, so they'd have to do a full recompute (entire log) which can take some time....

*** My statement above is incorrect; DXKeeper does recompute the progress both the old and new DXCC entities. The defect is that DXView's progress display is not immediately updated. I am investigating...

73,

Dave, AA6YQ



------------------------------------
Posted by: "Dave AA6YQ" <aa6yq@...>
------------------------------------


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

Yahoo Groups Links




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


Re: Pathfinder: "Out of memory on line: 1" popup

Danny Douglas <n7dc@...>
 

I did a manual check and its te4lling me the web page is out of memory.


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 November 16, 2017 at 4:46 PM "Björn Ekelund bjorn@... [dxlab]" <dxlab@...> wrote:

 

 

Is it just me who are getting an error popup when looking at DK7LX's QRZ entry via Pathfinder?

I am running Windows 10 Pro.

73,

Björn

 


 


Pathfinder: "Out of memory on line: 1" popup

Björn SM7IUN
 

Is it just me who are getting an error popup when looking at DK7LX's QRZ entry via Pathfinder?

I am running Windows 10 Pro.

73,

Björn


Re: DXLab help

Dave AA6YQ
 

Your screen shot of the CW tab of WinWarbler's Configuration window shows that you have the "CW Keying" tab set to "Xcvr Ctrl App". That means WinWarbler is transmitting CW but sending the text to be transmitted to Commander, which in turn sends it to PowerSDR using the "KY" CAT command. PowerSDR then transmits the text it receives from Commander. The timing source that PowerSDR is using to generate CW is not stable/ The same thing happens if you configure WinWarbler to transmit CW by raising and lowering a serial port modem control signal like RTS: if you move the mouse while CW is being transmitted, the timing will vary. Windows is not a real-time operating system, and does not provide a load-independent timing service.

There are three ways for WinWarbler to generate rock-solid CW timing:

1. use a WinKey

2. use an external modem (PK232, KAM, MFJ) with CW transmission capability

3. use a transceiver that can be directed to transmit CW via CAT command

For more information, see

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

and

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

73,

Dave, AA6YQ

-----Original Message-----
From: DAVE WHITE
Sent: Thursday, November 16, 2017 2:26 PM
To: Dave AA6YQ
Subject: Re: DXLab help

Hello Dave, thanks for getting back to me. I couldn't think of anything else to write in the "why do you want to join the group?" box. It seemed appropriate :-)

I've recently bought an SDR.

It's an Apache and I used the PowerSDR software that was recommended. That works OK for voice, though it's so complicated I'm still finding my way around it.

I downloaded CW Skimmer and configured it to talk to PowerSDR in RX mode. All OK (eventually)

I then wanted to be able to put VFO B onto the "spot" frequency in the pileup from Skimmer, so I tried a couple of things but no joy and then installed Commander. This acted OK as an interface between Skimmer and the PowerSDR radio control. I can click on the decode spot and it puts the TX frequency into VFO B. It's a bit flaky since I seem to have to untick and tick the secondary CAT serial port box before Skimmer gets the frequency from Commander again.

So far so good.

I then installed Winwarbler and amazingly found that I can send CW from the keyboard.

Here's the setup https://www.dropbox.com/s/9agtc3m9u1vz87h/SDR%20%26%20Skimmer%20split%20RX%20setup%2016%2011%2017.rtf?dl=0

I wrote the doc as much for my memory as anything else

What's really strange though it is sounds like irregular CW as if it's sent from a straight key by someone who's had a few too many G&Ts.

I appreciate that I'm cobbling a lot of stuff together (and the computer talks to the radio over Ethernet) so maybe I'm better off using something like a Microham keyer as an external device straight to the key on the radio rather then trying to do everything with software.

Have you come across anyone trying this before? Any ideas what's happening?

Once again thanks for getting back to me

73 Dave G0OIL


Re: Windows Insider build 17025.1000

Dave AA6YQ
 

Thanks, Iain. Several ops have posted reports here of incorrectly-rendered checkboxes, to which I could only respond "be sure to tell Microsoft Windows 10 Support!". The messages clearly got through.

To those of you running DXLab on "early access" versions of Windows 10, this is proof that the feedback loop is working. Please be sure to inform Windows 10 Support of any deficiencies you encounter!

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 16, 2017 1:39 PM
To: dxlab
Subject: [dxlab] Re: Windows Insider build 17025.1000

In case anyone cares, this may be fixed in the latest build - I'm not on the fast ring, so can't verify yet...

https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/

"We fixed an issue resulting in checkboxes being missing from certain
win32 apps."

73,

~iain / N6ML



On Wed, Nov 15, 2017 at 5:42 PM, iain macdonnell - N6ML <ar@...> wrote:
Found an item (with 105 other votes) in the feedback hub about
radio-buttons and check-boxes missing in C++ apps with this build.

73,

~iain / N6ML


On Wed, Nov 15, 2017 at 4:46 PM, iain macdonnell - N6ML <ar@...> wrote:
Any Windows Insiders out there?

I just let it update to "Version 1709 (OS Build 17025.1000)", and
find that radio-buttons and check-boxes are not rendering in the
DXLab Suite apps. No problems in any other apps so-far. Guessing it
may be a problem with a VB6 toolkit library or something....

73,

~iain / N6ML

------------------------------------
Posted by: iain macdonnell - N6ML <ar@...>
------------------------------------


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

Yahoo Groups Links




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


Re: ARRL International Grid Chase

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 16, 2017 12:50 PM
To: dxlab@...
Subject: Re: [dxlab] ARRL International Grid Chase

There is already a grid report that is useful for this. You can filter your log by year and for LoTW confirmations only if you wish.

The one deficiency in that report is that it doesn't support grid line QSOs (my report always shows many fewer than the VUCC report because of grid line and corner QSOs). That should be corrected as the ARRL International Grid Chase does allow operations from grid lines and corners.

If I extend DXLab to support the Grid Chase, that extension will include a progress report consistent with the rules.
73,

Dave, AA6YQ


Re: ARRL International Grid Chase

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 16, 2017 12:42 PM
To: dxlab@...
Subject: [dxlab] ARRL International Grid Chase

Dave I was wondering if you are thinking about creating some sort of tracking for the grid chase that starts next year. Maybe
something similar to what you did for the NPOTH last year.

DXLab's support for NPOTA was achieved by extending DXKeeper to generate an NPOTA progress report that as a "side effect"
conveyed to SpotCollector a filter that when activated highlighted all active DX stations with unworked NPOTA codes. This same
technique could be used for the upcoming Grid Chase, but there are a lot more grid squares worldwide than National Parks in the US,
so the SpotCollector filter generated by DXKeeper could become quite lengthy; having to check each active DX station against
thousands of already-worked gridsquares could impact SpotCollector's performance. There's an upper limit on the size of an SQL
expression, probably a function of your system's available resources. It'd be terrible if halfway through the year, some users lost
the ability to filter SpotCollector for unworked grid squares.

At the other extreme would be adding a "Grid Chase" progress table to each log, extending DXKeeper to maintain it and SpotCollector
to query it just as they do for DXCC, IOTA, Marathon, VUCC, WAS, WAZ, and WPX. That's a lot of work for an award with a one year
lifetime.

It might be possible to just add date and "HF band" fields to the existing VUCC progress table. The date field would record the most
recent date that each grid square was worked, enabling SpotCollector to quickly identify active DX stations in needed grid squares
(specifically, those grids never before worked, those grids worked but with no date specified, and those grids worked with a date
prior to 2018-01-01); the "HF band" field would enable the recording of grid squares in the VUCC progress table without incorrectly
counting grid squares worked on HF frequencies for VUCC awards. This approach seems promising, but better ideas are welcome...

73,

Dave, AA6YQ


Re: DX Commander problem?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 16, 2017 10:23 AM
To: dxlab@...
Subject: [dxlab] DX Commander problem?

I was over at a friend's house yesterday and am not sure whether there is a problem with his DX Commander or not.

The background is that DXLab Suite was originally put on his computer, almost a year ago, to link to a Yaesu FT991. It has not been used again until this week and he now has a Kenwood TS-990.

He has upgraded all parts of the suite to the latest versions.

DxX Commander has been set up for the Kenwood and is working correctly, including with WSJT-X and through a transverter.

But I noticed that DX Commander has options for Data-L and Data-U even though the Radio is a Kenwood. (I know that with my Kenwood TS-590 neither of these options appear)

Should this be the case or does it signify there is a problem with his DX Commander configuration?

As noted in the upper-right corner of page 4-10 of the TS-990S instruction manual, the TS-990S supports data modes.
73,

Dave, AA6YQ


Re: Windows Insider build 17025.1000

iain macdonnell - N6ML
 

In case anyone cares, this may be fixed in the latest build - I'm not
on the fast ring, so can't verify yet...

https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/

"We fixed an issue resulting in checkboxes being missing from certain
win32 apps."

73,

~iain / N6ML

On Wed, Nov 15, 2017 at 5:42 PM, iain macdonnell - N6ML <ar@...> wrote:
Found an item (with 105 other votes) in the feedback hub about
radio-buttons and check-boxes missing in C++ apps with this build.

73,

~iain / N6ML


On Wed, Nov 15, 2017 at 4:46 PM, iain macdonnell - N6ML <ar@...> wrote:
Any Windows Insiders out there?

I just let it update to "Version 1709 (OS Build 17025.1000)", and find
that radio-buttons and check-boxes are not rendering in the DXLab
Suite apps. No problems in any other apps so-far. Guessing it may be a
problem with a VB6 toolkit library or something....

73,

~iain / N6ML