[Top] [All Lists]

Re: [SD-User] Rig Control in V17.06

Subject: Re: [SD-User] Rig Control in V17.06
From: "Dave Sergeant" <>
Date: Mon, 15 Jul 2013 18:10:05 +0100
List-post: <">>
Thanks Paul for the explanation - still puzzled why it went to Top Band 
with that callsign...

The other issue which caused me to abandon SD and do the remainder of 
the contest with N1MM was what I posted here on April 1st that you 
never commented on:

Just used v17.00 in tonight's 80m CC contest - in unregistered mode. I 
became aware after around 15 minutes that stations I worked were not 
appearing in the dupe check window (or shown as such when SCP was 
enabled), although still came up as dupes in the logging window if I 
typed the full call in. A few stations I worked early on did show but 
later ones did not. I decided to exit the program and restart, 
whereupon it worked properly till the end, all the missing earlier ones 

Same thing happened on Saturday, I was working S&P and typing calls 
that I had worked in the callsign field and they were not showing in 
the dupe check window (but did show as dupes when I typed the full call 
in). In this case closing SD and restarting made no difference. At 
which point I decided I had had enough - at least I was able to export 
the log as ADIF via SDCheck and import that into N1MM.

And as an aside, why do I get a UAC admin prompt when I start SD (but 
not SD Check) on Windows 7?

73 Dave G3YMC

On 15 Jul 2013 at 17:43, Paul O'Kane wrote:

> > Using 17.07 in the IARU contest, interfaced to my Elecraft K2. Why 
> when I type 8HQ (as part of 9A28HQ) and press space bar or enter does my
> rig change to 160m LSB? Nearly lost a QSO...
> This happened for callsigns beginning with a number
> and ending with the letter "Q".  It was caused by
> broken code (many months ago) associated with the
> need to distinguish between a "frequency change"
> command and a "QSO edit" command when there were
> more than 1800 QSOs in the log - Q at the end of the
> number was used to identify a QSO Edit rather than a
> frequency change.
> This is not an issue in other loggers that don't
> offer direct editing of a QSO by entering the QSO
> number.
> As many discovered, the way to get round the bug
> was to use Tab, rather that Enter, after 9A27HQ
> and similar callsigns.
> It's fixed in V17.08, for release later this week.

SD-User mailing list

<Prev in Thread] Current Thread [Next in Thread>