Date   
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: 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

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: 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

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


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


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

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

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: SC startup problem

Mike - W1MI
 

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: DXView

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, January 29, 2015 5:34 PM
To: dxlab@...
Subject: Re: [dxlab] DXView

Since I always start the entire suite from Launcher I haven't noticed that. However, what does happen is that DXkeeper doesn't seem to know that Pathfinder is running even though it is. I have to close and reopen Pathfinder for DXKeeper to see it.

In what order do you start DXKeeper and Pathfinder when "DXKeeper doesn't see Pathfinder"?
73,

Dave, AA6YQ

Re: SC startup problem

Dave AA6YQ
 

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: DXView

Dave AA6YQ
 

Versions of DXView earlier than 4.0.7 did not depend on data or services from WinWarbler, and thus did not display a WW in their title bar when WinWarbler is running.

DXView 4.0.7's Main window's "Progress grid" highlights WinWarbler's "Operating Mode", so on startup, DXView 4.0.7 establishes interoperation with WinWarbler (if WinWarbler is already running).

No public version of WinWarbler informs DXView that it has started, so DXView's "Progress grid" will only highlight WinWarbler's "Operating Mode" if WinWarbler was already running when DXView started. This requirement will be eliminated by the next version of WinWarbler, which is imminent.

73,

Dave, AA6YQ

Re: DXView

Richard B Drake
 

Since I always start the entire suite from Launcher I haven't noticed
that. However, what does happen is that DXkeeper doesn't seem to know
that Pathfinder is running even though it is. I have to close and reopen
Pathfinder for DXKeeper to see it.

73, Rich - W3ZJ

iain macdonnell - N6ML @N6ML [dxlab] wrote:

On Thu, Jan 29, 2015 at 7:45 AM, Stephen Rabinowitz
srabin@... [dxlab] <dxlab@...> wrote:

With the latest version of DXView, it doesn’t seem to recognize the presence of WinWarbler unless DXV is launched after WW is already active. Does anyone else notice this?
Yes, I see the same thing with DXView 4.0.7 on both Win7 and Vista -
i.e. 'WW' does not appear in the title bar of the DXView window unless
DXView is Launched with WinWarbler already running.

Curiously, before updating from DXView 4.0.4, it didn't seem to see
WinWabler at all, no matter which was launched first!

73,

~iain / N6ML

Re: DXView

iain macdonnell - N6ML
 

On Thu, Jan 29, 2015 at 7:45 AM, Stephen Rabinowitz
srabin@... [dxlab] <dxlab@...> wrote:
With the latest version of DXView, it doesn’t seem to recognize the presence of WinWarbler unless DXV is launched after WW is already active. Does anyone else notice this?
Yes, I see the same thing with DXView 4.0.7 on both Win7 and Vista -
i.e. 'WW' does not appear in the title bar of the DXView window unless
DXView is Launched with WinWarbler already running.

Curiously, before updating from DXView 4.0.4, it didn't seem to see
WinWabler at all, no matter which was launched first!

73,

~iain / N6ML

Re: errorlog.txt

Tom Schaefer <ny4i@...>
 

Normally one logs only when trying to solve a particular issue. If you are trying to catch an intermittent error and have debugging enabled by Dave's request, then if whatever bug you are working did not happen during your session, remove the log. You could also have a batch command file you run when you shutdown to zip the logs and remove them. 

As they are text files, they should zip up very small. 

Tom NY4I 

Principal Solutions Architect
Better Software Solutions, Inc. 
727-437-2771

On Jan 29, 2015, at 11:25 AM, Curt Bowles curt_bowles@... [dxlab] <dxlab@...> wrote:

 

Good Day...

I have been searching for help discussion on the error file(s) that would give me a better understanding of how to manage the size of these files. The size of these files are starting to get large and takes a few seconds to load when opened.  Is there such a discussion/help file?

As I understand it; an error log is generated for each app if the "Log Debugging Info" box is checked. When checked it appears to log errors as well as events.

My error files have collected app data since I start the suite. Much of the data is stale, in my opinion, and the file can be cleaned out or deleted.

I assume one can go into the file and delete stale data or replace the file with an empty "Errorlog.txt file"  backing up the existing Errorlog.txt files as required. However I am not sure if their would be any implications to this approach.

I would appreciate you comments and insight!

Regards,
Curt
VE3ZN

SC startup problem

Phil & Anne Irons
 

Hi Dave...

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.)

I have made no hardware nor software changes to this computer, other than DXL updates as stated above.

Your comments/advice would be appreciated.  Win 7, Home Premium.

73,

Phil/VE1BVD

Re: errorlog.txt

Curt Bowles
 

Thanks again Art for the clarification!

73


On Thursday, January 29, 2015 1:44 PM, "ART SEARLE w2nra@... [dxlab]" wrote:


 
Yes, in fact if you leave them running these files would probably be to big and thus useless in resolving an error.  

73,
Art W2NRA
ARRL Life Member
DXCC CW Honor Roll
SKCC# 11634S

On Jan 29, 2015, at 1:21 PM, curt_bowles@... [dxlab] <dxlab@...> wrote:


Thanks for your reply Art...

So what we are saying: By default, errors are recorded.... in errorlog.txt no matter what the setting of "Log Debugging info" is....
 and 
if "Log Debugging info" is checked additional data and events are recorded including errors. 

Curt
VE3ZN 






Re: errorlog.txt

ART SEARLE <w2nra@...>
 

Yes, in fact if you leave them running these files would probably be to big and thus useless in resolving an error.  

73,
Art W2NRA
ARRL Life Member
DXCC CW Honor Roll
SKCC# 11634S

On Jan 29, 2015, at 1:21 PM, curt_bowles@... [dxlab] <dxlab@...> wrote:


Thanks for your reply Art...


So what we are saying: By default, errors are recorded.... in errorlog.txt no matter what the setting of "Log Debugging info" is....

 and 

if "Log Debugging info" is checked additional data and events are recorded including errors. 


Curt

VE3ZN 





Re: errorlog.txt

Curt Bowles
 

Thanks for your reply Art...


So what we are saying: By default, errors are recorded.... in errorlog.txt no matter what the setting of "Log Debugging info" is....

 and

if "Log Debugging info" is checked additional data and events are recorded including errors.


Curt

VE3ZN