Date   
Re: SC startup problem

Mike - AA1AR
 

Assuming the sh/dx portion is working ok, shouldn’t there be a slash between “wwv” and “36”?

73, Mike – AA1AR

 

From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, January 29, 2015 5:38 PM
To: dxlab@...
Subject: RE: [dxlab] SC startup problem

 

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, January 29, 2015 3:30 PM
To: dxlab@...
Subject: [dxlab] SC startup problem

For a number of reasons, I haven't been active in the shack since Christmas, except to update new versions of apps and databases. I was up here the other day, and noticed that even though my initial cluster command reads "sh/wwv36<13><10>sh/dx/200<13><10>set/dxgrid", the WWV part of the SC window is not updating. To get the correct WWV report, I have to open the appropriate spot source and send the command directly to the server. (I use W1NR.)

>>>Is the Enable box in the "Initial Cluster command" panel checked?

73,

Dave, AA6YQ

Re: SC startup problem

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, January 29, 2015 7:02 PM
To: dxlab@...
Subject: RE: [dxlab] SC startup problem

Assuming the sh/dx portion is working ok, shouldn’t there be a slash between “wwv” and “36”?

Yes. Good catch, Mike!
73,

Dave, AA6YQ

Re: WinWarbler sending Text for QTH-ID

df9dd@...
 

it would be possible to create a macro?
could be as simple to insert an appropriate text.

73 de DF9DD Ed


---In dxlab@..., <aa6yq@...> wrote :

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, January 29, 2015 3:46 AM
To: dxlab@...
Subject: [dxlab] WinWarbler sending Text for QTH-ID

it is possible to send a text in dependence of the QTH ID field?
Example: <qthid1: text> <qthid2: text>

>>>It's not, Ed.

73,

Dave, AA6YQ

TS-590SG and TS-590S firmware/software updates: the full story.

Ian_Wade_G3NRW <g3nrw-radio@...>
 

TS-590SG and TS-590S firmware/software updates: the full story.

Today (29 January), Kenwood released firmware and software updates for
the TS-590SG and TS-590S. Specifically:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TS-590SG:
==========

*** Firmware v1.01

*** ARCP-590G v1.01
(You need to install this to be compatible with firmware v1.01).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TS-590S:
==========

*** Firmware v2.00
(This is a major upgrade, changing the function of several
TS-590S controls. When you install it, it automatically does
a full radio reset).

*** ARCP-590 v2.00
(You need to install this to be compatible with firmware v2.00).

*** ARHP-590 v2.00
(You need to install this to be compatible with firmware v2.00).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

REMINDER: The TS-590SG and TS-590S are two entirely different radios.
The firmware and software for one radio will not work on the other.

Also, before updating the firmware, remember to back up *all* the
radio's settings (including the front-panel controls that ARCP does not
back up). Details at:

http://homepage.ntlworld.com/wadei/TS-590S_HOWTO_firmware_q&a_v1.1.pdf

As usual, links to all Kenwood firmware and software products are
conveniently collected together in one place on the "TS-590 Family
Resources Page":

http://homepage.ntlworld.com/wadei/ts-590s.htm

--
73
Ian, G3NRW

dxkeeper

David Elsea
 

Hello group,
I am new to DXLabs and have a 2 questions about dxkeeper.
 is
1. Is there a program that will auto populate the QRZ info when a QSO is entered. I know command puts all radio info in the capture mode, just wondering about the other stuff.

2. Is there a way to left margin justify the log info when a QSO is logged. Every column is right justified.

Thanks for any help.

Dave w6dke


Re: dxkeeper

Larry Knain
 

There is a checkbox under the Callbook tab of config  (bottom center) that says “Automatically use callbook data to initialize new QSOs”.
 
I have never used it but there is an option under the Log tab of DXK config to define a LogPage layout file. Perhaps that would allow left-justified field definition.
 
73, Larry  W6NWS
 

Sent: Friday, January 30, 2015 9:13 AM
Subject: [dxlab] dxkeeper
 
 

Hello group,
I am new to DXLabs and have a 2 questions about dxkeeper.
is
1. Is there a program that will auto populate the QRZ info when a QSO is entered. I know command puts all radio info in the capture mode, just wondering about the other stuff.

2. Is there a way to left margin justify the log info when a QSO is logged. Every column is right justified.

Thanks for any help.

Dave w6dke


Re: dxkeeper

Richard B Drake
 

dkelsea@... [dxlab] wrote:
Hello group,
I am new to DXLabs and have a 2 questions about dxkeeper.
is
1. Is there a program that will auto populate the QRZ info when a QSO is entered. I know command puts all radio info in the capture mode, just wondering about the other stuff.
Yes, see file:///C:/DXLab/DXKeeper/Help/Configuration.htm#Callbook Tab

2. Is there a way to left margin justify the log info when a QSO is logged. Every column is right justified.
Yes via DXkeeper Config, Log Tab, Log Page Display.

73, Rich - W3ZJ

Thanks for any help.

Dave w6dke

scripting confusion

Tuck Hartshorn
 

When I entered "(App_DXKeeper_LotW_QSLRdate > #2015-01-29#)" I did not get what I expected.

Instead, I got almost half my DB. What's wrong?


fyi, when I sort by App_DXKeeper_LotW_QSLRdate, it works fine.

TU 73 Tuck AF6GQ


 

Re: WinWarbler sending Text for QTH-ID

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, January 30, 2015 4:50 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler sending Text for QTH-ID

it would be possible to create a macro?
could be as simple to insert an appropriate text.

I understand the mechanism you're proposing be added, but I'd like to understand how you intend to employ this mechanism. What capability are you trying to gain?
73,

Dave, AA6YQ

Re: scripting confusion

iain macdonnell - N6ML
 

On Fri, Jan 30, 2015 at 12:58 PM, tuck@... [dxlab]
<dxlab@...> wrote:



When I entered "(App_DXKeeper_LotW_QSLRdate > #2015-01-29#)" I did not get what I expected.

Instead, I got almost half my DB. What's wrong?
The "empty" value for that field is #4000-01-01#, so your filter would
match any QSO that has not been confirmed by LotW. Instead, you might
try:

App_DXKeeper_LotW_QSL_Rcvd in ('Y','S','V') and
App_DXKeeper_LotW_QSLRdate > #2015-01-29#

73,

~iain / N6ML

Re: dxkeeper

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, January 30, 2015 9:14 AM
To: dxlab@...
Subject: [dxlab] dxkeeper

I have 2 questions so far that I can't seem to find answers for.

1. Does any of the DXlabs programs auto populate QTH info in the logger?

Yes. DXKeeper can be configured to query online or local callbooks,
as described in
<http://www.dxlabsuite.com/dxlabwiki/CallbookLookup

and

<http://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Callbook Tab>

With DXKeeper running, checking the "automatic lookup" box in the "QSO Info" panel on the Log tab of WinWarbler's Configuration window will result in WinWarbler querying the callbook selected in DXKeeper.

2. Can the log info be left justified instead of right justified?

Yes, you can control the alignment of each column in the Log Page
Display. See
<http://www.dxlabsuite.com/dxlabwiki/LogPageDisplayConfiguration>

and

<http://www.dxlabsuite.com/dxkeeper/Help/ConfigureLogPageDisplay.htm>

73,

Dave, AA6YQ

Re: scripting confusion

Joe Subich, W4TV
 

Instead, you might try:

App_DXKeeper_LotW_QSL_Rcvd in ('Y','S','V') and
App_DXKeeper_LotW_QSLRdate > #2015-01-29#
or:

APP_DXKeeper_LotW_QSLRDATE between #2015-01-29# and #2100-01-01#

73,

... Joe, W4TV


On 2015-01-30 4:13 PM, iain macdonnell - N6ML @N6ML [dxlab] wrote:
On Fri, Jan 30, 2015 at 12:58 PM, tuck@... [dxlab]
<dxlab@...> wrote:



When I entered "(App_DXKeeper_LotW_QSLRdate > #2015-01-29#)" I did not get what I expected.

Instead, I got almost half my DB. What's wrong?
The "empty" value for that field is #4000-01-01#, so your filter would
match any QSO that has not been confirmed by LotW. Instead, you might
try:

App_DXKeeper_LotW_QSL_Rcvd in ('Y','S','V') and
App_DXKeeper_LotW_QSLRdate > #2015-01-29#

73,

~iain / N6ML


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


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

Yahoo Groups Links



WinWarbler 8.2.1 is available

Dave AA6YQ
 

This release

- doesn't display transmit frequency tone markers when operating in RTTY FSK (tnx to Bob KB1JZU)

- only saves RTTY soundcard and external modem transceiver modes to the Registry if they've been initialized

- notifies the user if the selected RTTY soundcard or external transceiver mode is not specified

- if an optimal RTTY offset box is cleared, doesn't automatically set it to 2210

- removes leading or trailing spaces in the Station Callsign, Operator Callsign, or Owner Callsign when resolving a macro
substitution command or logging a QSO

- in CW mode, prevents the F4 key from initiating transmission (tnx to Salvatore I4FYV)

- ensures that the Callsign in the Main window's "QSO Info" panel is colored to reflect "need" (tnx to Chris NJ5N)

- ensures that all boxes in the Main window's "QSO Info" panel default to the "MS Sans Serif" font (tnx to Salvatore I4FYV)

- when responding to a double-clicked Spot Database Entry, properly initializes the "QSO Info" panel's "Ant Path" selector (tnx to
Salvatore I4FYV)

- responds to a double-click of the word 'Grid' to the left of the QSO info panel's Gridsquare box by directing DXKeeper to filter
the Log Page Display to display all QSOs with a matching grid square, ignoring any sub-square (tnx to Mike W3QT)

- provides a WPX box in the Main window's "QSO Info" panel that displays the callsign's WPX prefix; double-clicking the word 'WPX'
to the left of this box directs DXKeeper to filter the Log Page Display to display all QSOs with a matching WPX prefix (tnx to Mike
W3QT)

- offers DIGL and DIGU transceiver modes when Commander's primary transceiver supports them

- on the Main window's "QSO Info" panel, highlights a Special Callsign in bold font with the specified color when DXKeeper and
DXView are running (tnx to Chris NJ5N)

- increases the speed at which Shift-F10 removes the Windows menu

- provides a <delayedxcvrsequence> macro command (tnx to Joe W4TV)

- notifies DXView on startup so its Progress Grid's mode can immediately be highlighted in bold green font (tnx to Brian G0VAX and
Nuno CT2IRY))

- updates the Logging.htm, LogSettings.htm, Macros.htm, and SoundcardRTTYSettings.htm documentation files


WinWarbler 8.2.1 is available via the DXLab Launcher or via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ

WinWarbler 8.2.2 is available

Dave AA6YQ
 

It's WinWarbler 8.2.2 that's now available (not 8.2.1 was incorrectly announced).

This release

- doesn't display transmit frequency tone markers when operating in RTTY FSK (tnx to Bob KB1JZU)

- only saves RTTY soundcard and external modem transceiver modes to the Registry if they've been initialized

- notifies the user if the selected RTTY soundcard or external transceiver mode is not specified

- if an optimal RTTY offset box is cleared, doesn't automatically set it to 2210

- removes leading or trailing spaces in the Station Callsign, Operator Callsign, or Owner Callsign when resolving a macro
substitution command or logging a QSO

- in CW mode, prevents the F4 key from initiating transmission (tnx to Salvatore I4FYV)

- ensures that the Callsign in the Main window's "QSO Info" panel is colored to reflect "need" (tnx to Chris NJ5N)

- ensures that all boxes in the Main window's "QSO Info" panel default to the "MS Sans Serif" font (tnx to Salvatore I4FYV)

- when responding to a double-clicked Spot Database Entry, properly initializes the "QSO Info" panel's "Ant Path" selector (tnx to
Salvatore I4FYV)

- responds to a double-click of the word 'Grid' to the left of the QSO info panel's Gridsquare box by directing DXKeeper to filter
the Log Page Display to display all QSOs with a matching grid square, ignoring any sub-square (tnx to Mike W3QT)

- provides a WPX box in the Main window's "QSO Info" panel that displays the callsign's WPX prefix; double-clicking the word 'WPX'
to the left of this box directs DXKeeper to filter the Log Page Display to display all QSOs with a matching WPX prefix (tnx to Mike
W3QT)

- offers DIGL and DIGU transceiver modes when Commander's primary transceiver supports them

- on the Main window's "QSO Info" panel, highlights a Special Callsign in bold font with the specified color when DXKeeper and
DXView are running (tnx to Chris NJ5N)

- increases the speed at which Shift-F10 removes the Windows menu

- provides a <delayedxcvrsequence> macro command (tnx to Joe W4TV)

- notifies DXView on startup so its Progress Grid's mode can immediately be highlighted in bold green font (tnx to Brian G0VAX and
Nuno CT2IRY))

- updates the Logging.htm, LogSettings.htm, Macros.htm, and SoundcardRTTYSettings.htm documentation files


WinWarbler 8.2.2is available via the DXLab Launcher or via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ






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


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

Yahoo Groups Links

Re: scripting confusion

Tuck Hartshorn
 

aHa.  I get it
tnx
73 tuck af6gq

N1MM-DXK Gateway

Hunter Mills - K3IE
 

I just learned of this real-time feature several weeks ago here in the forum and was anxious to try it but I can't seem to get it to work.

I edited and saved the N1MM .ini file as indicated in the Gateway Help page.  I even added my IP address.  Saved the file and confirmed the .ini file retained the changes.

The Gateway is running and its Status indicates it is connected to DXKeeper.

However, N1MM entries are not populating DXK.

I have unsuccessfully tried this with N1MM Logger and N1MM Logger +.

This would be an extremely efficient tool for me since I participate in many contests and it would save me the manual transfer process.

Any suggestions would be appreciated.

Hunter, K3IE


Re: N1MM-DXK Gateway

ray cathode
 

Hello Hunter,



Be sure to enter your computer's IPv4 address.

Works flawlessly..






From: "H Mills k3ie77@... [dxlab]"
To: "dxlab@..."
Sent: Friday, January 30, 2015 8:02 PM
Subject: [dxlab] N1MM-DXK Gateway

 
I just learned of this real-time feature several weeks ago here in the forum and was anxious to try it but I can't seem to get it to work.

I edited and saved the N1MM .ini file as indicated in the Gateway Help page.  I even added my IP address.  Saved the file and confirmed the .ini file retained the changes.

The Gateway is running and its Status indicates it is connected to DXKeeper.

However, N1MM entries are not populating DXK.

I have unsuccessfully tried this with N1MM Logger and N1MM Logger +.

This would be an extremely efficient tool for me since I participate in many contests and it would save me the manual transfer process.

Any suggestions would be appreciated.

Hunter, K3IE




Re: N1MM-DXK Gateway

Hunter Mills - K3IE
 

I found the problem - a combination of pilot error. I did not have the proper IPv4 address and did not properly edit the correct .ini file in N1MM. 

Working now - fantastic feature. 

Thanks to all - Hunter, K3IE


On Jan 30, 2015, at 8:40 PM, ray cathode ray_cathode1@... [dxlab] <dxlab@...> wrote:

 

Hello Hunter,



Be sure to enter your computer's IPv4 address.

Works flawlessly..






From: "H Mills k3ie77@... [dxlab]" <dxlab@...>
To: "dxlab@..." <dxlab@...>
Sent: Friday, January 30, 2015 8:02 PM
Subject: [dxlab] N1MM-DXK Gateway

 
I just learned of this real-time feature several weeks ago here in the forum and was anxious to try it but I can't seem to get it to work.

I edited and saved the N1MM .ini file as indicated in the Gateway Help page.  I even added my IP address.  Saved the file and confirmed the .ini file retained the changes.

The Gateway is running and its Status indicates it is connected to DXKeeper.

However, N1MM entries are not populating DXK.

I have unsuccessfully tried this with N1MM Logger and N1MM Logger +.

This would be an extremely efficient tool for me since I participate in many contests and it would save me the manual transfer process.

Any suggestions would be appreciated.

Hunter, K3IE




Zz

Hunter Mills - K3IE
 

DXView 4.0.8 is available

Dave AA6YQ
 

This release

- prevents errorlog.txt file entries from being generated when terminating

- provides a new "Scan DX" capability

- updates the Configuration.htm and Operation.htm documentation files


In previous versions of DXView, you could observe actual propagation on each band by clearing DXView's Band filter, and then
sequentially selecting one band after another. This version of DXView automates this process by providing a one-click "Scan DX"
capability:

* on the Configuration window's "Plot Settings" tab, a new "Scan DX Bands" panel lets you select the bands to be included in the
scan, and the number of seconds (from 1 to 30) for which DXView will "dwell" while displaying active DX on each band

* DXView's Main and "World Map" windows both provide "Scan DX buttons that when clicked,

---- save the current "Xcvr band only" and "Band Filter" settings

---- manipulate the "Band Filter" to display active DX stations on each of the bands selected in the "Scan DX Bands" panel for the
number of seconds specified, and subject to the Mode Filter, Continent Filter, and Origin Filter

---- restore the "Xcvr band only" and Band Filter settings to their saved settings


While a "Scan DX" operation is in progress,

* the name of the band whose active DX is currently being displayed will appear to the right of the Scan DX button on the Main
window, and above the Scan DX button on the World Map window

* clicking the Scan DX button on either the Main or World Map window will immediately terminate the Scan DX operation


The "Scan DX" operation will display active DX stations on DXLab's built-in world map or on the DX Atlas map. If Google Earth is
running, the "Scan DX" operation will also display active DX stations there, but the "dwell" setting should be at least 5 seconds to
give Google Earth time to update.

When you first run DXView 4.0.8, the new "Scan DX Bands" panel will have its 160m, 80m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, 6m, and
2m boxes checked, and the "dwell" will be set to 1 second.


DXView 4.0.8 is available via the DXLab Launcher or via

<http://www.dxlabsuite.com/download.htm>


73,

Dave, AA6YQ