Date   

Re: WinWarbler version 2.1.6 is available

Dave, AA6YQ <dhb@...>
 

One click is a standard Windows gesture that means "select"; clicking in
a WinWarbler receive pane designates its channel as the one on which you
will transmit. Changing this to "a receive pane is selected whenever the
mouse pointer is overhead" would be very inconvenient -- for example,
you'd have to be very careful about moving the mouse from the QSO Info
panel to the Macros panel without inadvertently changing the selected
receive pane.

At three or for double-clicks per QSO, you'd have to work a lot of PSK31
to put a dent in a mouse switch's service lifetime..

73,

Dave, AA6YQ

-----Original Message-----
From: Chris BONDE [mailto:ve7hcb@...]
Sent: Friday, December 14, 2001 4:00 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

Why have the double click at all? Just wears the mouse out twice as
fast. I try to remove all needs thereof. Place the pointer over, it
highlights itself or you highlight, then one click, why two?

Chris opr VE7HCB
At 02:25 PM 2001-12-14 -0500, you wrote:
That's probably OK, I haven't seen any one throwing in meaningless
hyphens -
not that they couldn't. But that reminds me of something else. Normally
when
you click in a QTH, you hold down ALT and double click on it to put it
into
the QTH field. However fairly often QTH's are two words like, "Mexico
City".
In this case the way to do it is to highlight "Mexico City" hold down
ALT
and single click. If you double click (as is habit to do) it does
something
nutty like put Mexico into the callsign field. This has confused me on
a
number of occasions. Suggest that double click be allowed on a
multiword
QTH.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 11:34 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available


Underscore sounds right. I wonder whether we should eliminate the
minus/hyphen character. If you click on a hyphenated name like
Jean-Paul, you don't want Jean or Paul, you want Jean-Paul; is there
a
down-side to this?

73,

Dave, AA6YQ



-----Original Message-----
From: muck@... [mailto:muck@...]
Sent: Friday, December 14, 2001 4:22 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

On Dec 13, 3:27pm, "Dave, AA6YQ" wrote:
}
} This is easy to fix, but lets first agree on the right
} set of delimiters. At the moment, WinWarbler considers
} the following as delimiters when you double-click
} in a receive pane: space, colon, comma, plus, minus,
} greater-than, less-than, and equals.
}
} Besides adding period, are there other
} nominations? Should anything be removed from this list?


The underscore "_"




Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705

063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou

pmail/S=1705063108:HM/A=904006/rand=345371443>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/





To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/





Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=921844484>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


Re: WinWarbler version 2.1.6 is available

Chris BONDE <ve7hcb@...>
 

Why have the double click at all? Just wears the mouse out twice as fast. I try to remove all needs thereof. Place the pointer over, it highlights itself or you highlight, then one click, why two?

Chris opr VE7HCB

At 02:25 PM 2001-12-14 -0500, you wrote:
That's probably OK, I haven't seen any one throwing in meaningless hyphens -
not that they couldn't. But that reminds me of something else. Normally when
you click in a QTH, you hold down ALT and double click on it to put it into
the QTH field. However fairly often QTH's are two words like, "Mexico City".
In this case the way to do it is to highlight "Mexico City" hold down ALT
and single click. If you double click (as is habit to do) it does something
nutty like put Mexico into the callsign field. This has confused me on a
number of occasions. Suggest that double click be allowed on a multiword
QTH.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 11:34 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available


Underscore sounds right. I wonder whether we should eliminate the
minus/hyphen character. If you click on a hyphenated name like
Jean-Paul, you don't want Jean or Paul, you want Jean-Paul; is there a
down-side to this?

73,

Dave, AA6YQ



-----Original Message-----
From: muck@... [mailto:muck@...]
Sent: Friday, December 14, 2001 4:22 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

On Dec 13, 3:27pm, "Dave, AA6YQ" wrote:
}
} This is easy to fix, but lets first agree on the right
} set of delimiters. At the moment, WinWarbler considers
} the following as delimiters when you double-click
} in a receive pane: space, colon, comma, plus, minus,
} greater-than, less-than, and equals.
}
} Besides adding period, are there other
} nominations? Should anything be removed from this list?


The underscore "_"




Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705> 063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou> pmail/S=1705063108:HM/A=904006/rand=345371443>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.





To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/





To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Re: How to report bugs effectively

Chris BONDE <ve7hcb@...>
 

At 04:04 PM 2001-12-13 +0000, you wrote:
. He needs a little
coaching from a good DXPeditioner. Those guys know how to work the
propagation :-)
Experience . . . . . a wonderful thing we spend most of
our life accumulating.
Jim - M0ZAK [ gathering experience]
I think that it is an old Dutch saying,
"Too late we grow smart, too soon, old." I am sure we could say, "Too late experienced, too soon worn out."

Chris opr VE7HCB


Re: OS/feature issue(s)

Rick Fletcher
 

Your problem most definitely is Win9X which uses memory in the first 640K
for GUI management amongst other things. This is a carryover from the
Win3.x days. You might check to see what is being loaded via the
AUTOEXEC.BAT and CONFIG.SYS files and remove any memory-resident items you
don't really need or move them into the EMM memory space between the lower
640K and the first 1Meg address mark. Sometimes this will free up enough of
that lower 640K of memory to eliminate the resource error message. Neither
Win2K nor XP have this limitation, so either one is a sure-fire fix for
your problem. They're also far more stable operating systems as well.

73s,

Rick
KG6IAL

----- Original Message -----
From: "Richard B. Drake" <rich@...>
To: <dxlab@...>
Sent: Friday, December 14, 2001 12:53 PM
Subject: RE: [dxlab] OS/feature issue(s)


Pagel,

Your 1GHZ 256MB machine is ample. Your problem is almost assuredly Win 98
SE. With all the DXLAB applications up and running, Win 98 may complain
that
its out of memory. The error message is wrong, it's not out of memory,
it's
out of a software entity called system resources. If you bring up the
system
resource meter which should be available under Programs/Accessories/System
Tools, you can very plainly see this happening. I used to run Win 98 SE on
this machine, a 550 MHz 256MB Dell and had the same problem. I upgraded to
Windows XP and the problem is completely gone. Not only that, you will
notice a HUGE improvement in your systems performance (speed) and
stability
(no crashes). Although I have never run Win 2K, indications from Dave and
others would suggest that it also would accomplish these improvements.
However, if you're going to spend money on an upgrade, then why not go to
the latest version? I heartily recommend Windows XP to you.

-----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 3:32 PM
To: dxlab@...
Subject: RE: [dxlab] OS/feature issue(s)


My personal experience is that Windows 2000 does a far better job of
managing resources than Windows 9X or ME; I suspect (but cannot
guarantee) that an upgrade will eliminate your problem, as well as
improve overall system reliability. I'd invest in the upgrade before I
invested in more memory, though doing both is probably the right answer.
My experience with XP is limited to a weekend with a system I installed
for my father; I was very impressed, but did not have time to load and
test and DXLab applications. Rich W3ZJ has been running DXLab on XP for
awhile and is thus a better source. Perhaps others on the reflector are
using XP as well.

Regarding your DXKeeper question, there is currently no "auto-complete"
feature, though its certainly do-able. One suggested workaround: you can
adjust the order and widths of the fields in DXKeeper's log page display
so that Name and QTH are always visible without scrolling.

73,

Dave, AA6YQ

-----Original Message-----
From: Pagel, Mike [mailto:mpagel@...]
Sent: Friday, December 14, 2001 12:18 PM
To: dxlab@...
Subject: [dxlab] OS/feature issue(s)

Two questions for everyone.....

I'm currently using Windows 98 SE on a 1 GHz machine with 256 MB RAM,
and I'm down to 4% system and user resources after running DXView,
DXKeeper, CI-V Commander, and SpotCollector. Opening WinWarbler, for
instance, requires terminating some other component to free up
resources.

I'm hearing that an OS upgrade to 2000 or XP will solve some of these
problems. True? Are there any other system upgrades that would help
solve the lack of resources? More RAM, for instance?

My other question deals with DXKeeper. When I enter a call of a station
I'm contacting on the QSO capture screen, I never know if I've worked
the station before unless I can simultaneously see the main screen.
Even if I can do that, I must scroll laterally to see the name of the
operator, assuming it is there. Is there some sort of "auto-complete"
that can be established to fill in the fields from previous QSO's - if
there are any previous QSO's to tap? I'm interested in rapid access to
name and QTH, if possible. I'm not asking for a automatic update from a
CD-ROM or the QRZ web site. If I've logged the other op's name and QTH
previously, however, I'd like to have access to it immediately and/or
avoid having to enter it again.

Is this feature already in place, and have I managed to miss it somehow?
Would anyone else find value in having this?

A special "thank you" to you, Dave, for your amazing patience and
service orientation!

73, de Mike, K9UW





Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=583193740>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Re: OS/feature issue(s)

Richard B Drake
 

Pagel,

Your 1GHZ 256MB machine is ample. Your problem is almost assuredly Win 98
SE. With all the DXLAB applications up and running, Win 98 may complain that
its out of memory. The error message is wrong, it's not out of memory, it's
out of a software entity called system resources. If you bring up the system
resource meter which should be available under Programs/Accessories/System
Tools, you can very plainly see this happening. I used to run Win 98 SE on
this machine, a 550 MHz 256MB Dell and had the same problem. I upgraded to
Windows XP and the problem is completely gone. Not only that, you will
notice a HUGE improvement in your systems performance (speed) and stability
(no crashes). Although I have never run Win 2K, indications from Dave and
others would suggest that it also would accomplish these improvements.
However, if you're going to spend money on an upgrade, then why not go to
the latest version? I heartily recommend Windows XP to you.

-----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 3:32 PM
To: dxlab@...
Subject: RE: [dxlab] OS/feature issue(s)


My personal experience is that Windows 2000 does a far better job of
managing resources than Windows 9X or ME; I suspect (but cannot
guarantee) that an upgrade will eliminate your problem, as well as
improve overall system reliability. I'd invest in the upgrade before I
invested in more memory, though doing both is probably the right answer.
My experience with XP is limited to a weekend with a system I installed
for my father; I was very impressed, but did not have time to load and
test and DXLab applications. Rich W3ZJ has been running DXLab on XP for
awhile and is thus a better source. Perhaps others on the reflector are
using XP as well.

Regarding your DXKeeper question, there is currently no "auto-complete"
feature, though its certainly do-able. One suggested workaround: you can
adjust the order and widths of the fields in DXKeeper's log page display
so that Name and QTH are always visible without scrolling.

73,

Dave, AA6YQ

-----Original Message-----
From: Pagel, Mike [mailto:mpagel@...]
Sent: Friday, December 14, 2001 12:18 PM
To: dxlab@...
Subject: [dxlab] OS/feature issue(s)

Two questions for everyone.....

I'm currently using Windows 98 SE on a 1 GHz machine with 256 MB RAM,
and I'm down to 4% system and user resources after running DXView,
DXKeeper, CI-V Commander, and SpotCollector. Opening WinWarbler, for
instance, requires terminating some other component to free up
resources.

I'm hearing that an OS upgrade to 2000 or XP will solve some of these
problems. True? Are there any other system upgrades that would help
solve the lack of resources? More RAM, for instance?

My other question deals with DXKeeper. When I enter a call of a station
I'm contacting on the QSO capture screen, I never know if I've worked
the station before unless I can simultaneously see the main screen.
Even if I can do that, I must scroll laterally to see the name of the
operator, assuming it is there. Is there some sort of "auto-complete"
that can be established to fill in the fields from previous QSO's - if
there are any previous QSO's to tap? I'm interested in rapid access to
name and QTH, if possible. I'm not asking for a automatic update from a
CD-ROM or the QRZ web site. If I've logged the other op's name and QTH
previously, however, I'd like to have access to it immediately and/or
avoid having to enter it again.

Is this feature already in place, and have I managed to miss it somehow?
Would anyone else find value in having this?

A special "thank you" to you, Dave, for your amazing patience and
service orientation!

73, de Mike, K9UW





Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=583193740>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Re: OS/feature issue(s)

Dave, AA6YQ <dhb@...>
 

My personal experience is that Windows 2000 does a far better job of
managing resources than Windows 9X or ME; I suspect (but cannot
guarantee) that an upgrade will eliminate your problem, as well as
improve overall system reliability. I'd invest in the upgrade before I
invested in more memory, though doing both is probably the right answer.
My experience with XP is limited to a weekend with a system I installed
for my father; I was very impressed, but did not have time to load and
test and DXLab applications. Rich W3ZJ has been running DXLab on XP for
awhile and is thus a better source. Perhaps others on the reflector are
using XP as well.

Regarding your DXKeeper question, there is currently no "auto-complete"
feature, though its certainly do-able. One suggested workaround: you can
adjust the order and widths of the fields in DXKeeper's log page display
so that Name and QTH are always visible without scrolling.

73,

Dave, AA6YQ

-----Original Message-----
From: Pagel, Mike [mailto:mpagel@...]
Sent: Friday, December 14, 2001 12:18 PM
To: dxlab@...
Subject: [dxlab] OS/feature issue(s)

Two questions for everyone.....

I'm currently using Windows 98 SE on a 1 GHz machine with 256 MB RAM,
and I'm down to 4% system and user resources after running DXView,
DXKeeper, CI-V Commander, and SpotCollector. Opening WinWarbler, for
instance, requires terminating some other component to free up
resources.

I'm hearing that an OS upgrade to 2000 or XP will solve some of these
problems. True? Are there any other system upgrades that would help
solve the lack of resources? More RAM, for instance?

My other question deals with DXKeeper. When I enter a call of a station
I'm contacting on the QSO capture screen, I never know if I've worked
the station before unless I can simultaneously see the main screen.
Even if I can do that, I must scroll laterally to see the name of the
operator, assuming it is there. Is there some sort of "auto-complete"
that can be established to fill in the fields from previous QSO's - if
there are any previous QSO's to tap? I'm interested in rapid access to
name and QTH, if possible. I'm not asking for a automatic update from a
CD-ROM or the QRZ web site. If I've logged the other op's name and QTH
previously, however, I'd like to have access to it immediately and/or
avoid having to enter it again.

Is this feature already in place, and have I managed to miss it somehow?
Would anyone else find value in having this?

A special "thank you" to you, Dave, for your amazing patience and
service orientation!

73, de Mike, K9UW





Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=583193740>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


Re: Commander 3.1.8 is available

Dave, AA6YQ <dhb@...>
 

Great. Sounds like FT817 support is complete (finally!); let me know if
you encounter other problems or opportunities.

I understand your point re "DIGI", but I am reluctant to make the change
given that most radios denote the mode as "RTTY" - or at least it looks
that way from their PC interface documentation. I suppose I could
provide settings that allow users to customize the names associated with
each mode..

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Friday, December 14, 2001 11:54 AM
To: dxlab@...
Subject: RE: [dxlab] Commander 3.1.8 is available



This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable
transceivers
Yes!! Boy this is getting to be good.

One little nit pick, how about changing "RTTY" to "DIGI" or something of
that sort. Of course I know that I select "RTTY" when I want "PSK31" but
it
just doesn't sit right.

At least on FT-817 "DIGI" means whatever digital mode you have
previously
set up in the rig menus. In my case this is "USER-U" (User mode upper
side
band) which is good for both PSK31 and RTTY with reverse tones. By
using
2125 as the default tone for both RTTY and PSK31, my IF passband and
filter
settings are correct for both modes and I can switch between PSK31 and
RTTY
by doing nothing more than checking the appropriate box on WinWarbler's
screen - slick!!

73, Rich - W3ZJ






Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=265416007>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


Re: Commander 3.1.8 is available

Dave, AA6YQ <dhb@...>
 

My terminology was imprecise - I meant "selectable via the PC
interface". I agree that users of rigs whose filters cannot be selected
or set via the PC interface should not be presented with filter panels
or choices.

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Friday, December 14, 2001 10:17 AM
To: dxlab@...
Subject: RE: [dxlab] Commander 3.1.8 is available

Dave,

Actually the FT-817 does have "a" user selectable filter. A purchase
option
is to get one of either of two available Collins mechanical filters. A
2.4
KHz SSB filter or a 500 Hz CW filter. I have the CW filter which is also
usable on digital modes. Similar to your original ICOM, you can select
either wide or narrow and what that means depends on which filter you
have
installed. In my case narrow is available on CW and digital motes but
not on
any of the voice modes. I didn't mention this to you before because as I
look at the CAT documentation it looks like the only way to change it is
by
writing to the EPROM and I'm not sure I want to be the guinea pig for
that
experiment :-) What I normally do is set the rig menus up so that I can
switch from wide to narrow by pressing one button on the rig front panel
and
that works pretty well.

Bye the way, when filter selection is not available for a particular
rig,
you probably should not show it on Commander's screen. I know it doesn't
work on either the Omni VI+ or the Ft-817 and I ignore it but some may
think
that is a problem.

-----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 2:01 AM
To: dxlab@...
Cc: dhb@...
Subject: [dxlab] Commander 3.1.8 is available


This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable
transceivers

- introduces new filter support

The new filter support requires some discussion.

As you may know, Commander began life exclusively supporting Icom
transceivers. Icom has a very simple model for filters: if you're
allowed to control them, you do so by choosing between "wide" and
"narrow". The 756PRO introduced a third option: "normal". Actual
filter
bandwidths are a function of mode: "narrow" in CW mode might select a
250hz filter, but "narrow" in USB might select a 1900hz filter. A
stock
radio might come equipped with some or all filters; you can change
what's there, or add more. After some thought, I refer to Icom's
filter
model as a "fixed filter groups". The term "group" is appropriate
because something like "Wide" actually means

SSB 2400 hz
CW 250 hz
RTTY 500 hz

The adjective "fixed" is appropriate because one cannot add additional
groups. Your IC706 comes with wide and narrow filter groups; you can't
add a third filter group.

The challenge was to develop a filter model that would encompass
support
not just for Icom (and look-alike TenTec) radios, but also for Yaesu
and
Kenwood radios. As usual, Yaesu radios are all over the place. Some,
like the FT817, have no user selectable filters. Others, like the
FT920,
provide fixed filter groups just like Icom's. Still others, like the
FT100, FT1000, and the MP1000s, provide direct control of IF filters.
In
the MP1000, for example, one can choose a 2400hz second IF filter, a
1900hz third IF filter, and a 2400hz subreceiver filter; curiously
(but
not surprisingly - this is Yaesu we're talking about) the MP1000's
front
panel provides fixed filter groups (nor, nar1, nar2); direct filter
control is only available via PC control. It was for this reason that
K6SE developed MPFilters (see
http://www.qsl.net/va3cr/main/mpfilters.htm ), a very nice application
that provides direct control of an MP1000's IF filters. Clearly this
functionality belongs in Commander - but not just for MP1000s, we need
it for all radios that support direct control of IF filters.

A second form of direct control is found in recent Kenwood (e.g.
TS-870)
and Icom (e.g. 756PROII) transceivers - direct control of bandwidth
via
DSP.

Direct control is powerful, but not particularly convenient. Every
time
we change modes, we have to directly specify each IF filter or the DSP
filter bandwidth. What we need is the ability to define filter groups
like this:

SSB CW RTTY

DXing 2100 500 500
Contesting 1900 250 500
Ragchewing 2400 500 500

In a radio like the MP1000 MarkV, we'd be able to specify three IF
filters (main 2nd IF, main 3rd IF, subreceiver). Basically, you fill
out
tables, and then select the appropriate filter group while operating.
Since these filter groups are managed by Commander, you can define as
many as you like - they simply appear as choices in a pulldown
selection
control. This model is thus "user-defined filter groups"

From a control point of view, I suggest that we need two things:

1. the ability to select a filter group (either one of the fixed
groups supported by the radio's hardware, or one of the user-defined
filter groups for radios supporting direct control of IF or DSP
filters)

2. the ability to see exactly what filter bandwidths are actually
selected and, for radios that allow direct control, the ability to
change each filter independently

In the case of a radio with fixed filter groups, like our IC706 cited
above, the filter bandwidth display would show exactly one value: the
radio's second IF filter bandwidth. Switch from Wide to Narrow, for
from
CW to RTTY would display the appropriate value.

In the case of a radio with user-defined filter groups, like an MP1000
MkV, you can directly control the main 2nd IF, main 3rd IF, and
subreceiver filter bandwidths, or you can select a filter group like
"Ragchewing" to set all of them to specified values.

That's the theory. The description is more complicated than I'd like,
but I can't think of a simpler conceptual model that transcends
product
lines. Critique and suggestions will be greatly appreciated.

I've started the transition to this model in version 3.1.8. I'd
planned
to get a little further before making a release, but didn't want to
"fork" the code in order to respond to the above defects and
enhancement
requests. So visually, this version is a little rougher than usual.
Specifically,

- Filter Group selection is no longer accomplished by radio
buttons
below the VFO. The previous "Devices" tab has been renamed "Filters &
Devices", and includes a Filters panel; filter Group selection is
accomplished via pulldown control in this panel.

- For radios supporting direct control, Commander presents a
pulldown for each controllable IF. In this release, this only happens
for the Yeasu MP1000 and MP1000 MarkV - the functionality is identical
to K6SE's MPFilters application. I will add support for the other
direct
control radios in future releases.

- the main window is wider than in previous versions

- the maximum number of frequency-dependent devices has been
reduced
from 4 to 3 , and may go to 2 when macros buttons appear. Any
objections? Two covers an antenna tuner and an amplifier; is there a
need for more?

In 3.1.8, there is no display of IF filter bandwidths for radios with
fixed filter groups - I'll add this in the next release or two. There
is
also no support for user-defined filter groups; that will come too.
And
if your radio doesn't support fixed filter groups or direct control,
you'll see an empty Filters panel; future releases will properly
suppress this ugliness.

Let me know what you think.

To upgrade, see http://www.qsl.net/civ_commander/development.htm -
you'll be downloading
http://www.qsl.net/civ_commander/Commander318Update.exe . Note that
this
release introduces a new radios.txt file - if you've been maintaining
your own version, you'll need to merge in your changes. Also note that
the keyword "Filters" has been changed to "FilterGroups".


73,

Dave, AA6YQ










To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/






Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=783017627>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


OS/feature issue(s)

Pagel, Mike <mpagel@...>
 

Two questions for everyone.....

I'm currently using Windows 98 SE on a 1 GHz machine with 256 MB RAM,
and I'm down to 4% system and user resources after running DXView,
DXKeeper, CI-V Commander, and SpotCollector. Opening WinWarbler, for
instance, requires terminating some other component to free up
resources.

I'm hearing that an OS upgrade to 2000 or XP will solve some of these
problems. True? Are there any other system upgrades that would help
solve the lack of resources? More RAM, for instance?

My other question deals with DXKeeper. When I enter a call of a station
I'm contacting on the QSO capture screen, I never know if I've worked
the station before unless I can simultaneously see the main screen.
Even if I can do that, I must scroll laterally to see the name of the
operator, assuming it is there. Is there some sort of "auto-complete"
that can be established to fill in the fields from previous QSO's - if
there are any previous QSO's to tap? I'm interested in rapid access to
name and QTH, if possible. I'm not asking for a automatic update from a
CD-ROM or the QRZ web site. If I've logged the other op's name and QTH
previously, however, I'd like to have access to it immediately and/or
avoid having to enter it again.

Is this feature already in place, and have I managed to miss it somehow?
Would anyone else find value in having this?

A special "thank you" to you, Dave, for your amazing patience and
service orientation!

73, de Mike, K9UW


Re: Commander 3.1.8 is available

Richard B Drake
 


This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable transceivers
Yes!! Boy this is getting to be good.

One little nit pick, how about changing "RTTY" to "DIGI" or something of
that sort. Of course I know that I select "RTTY" when I want "PSK31" but it
just doesn't sit right.

At least on FT-817 "DIGI" means whatever digital mode you have previously
set up in the rig menus. In my case this is "USER-U" (User mode upper side
band) which is good for both PSK31 and RTTY with reverse tones. By using
2125 as the default tone for both RTTY and PSK31, my IF passband and filter
settings are correct for both modes and I can switch between PSK31 and RTTY
by doing nothing more than checking the appropriate box on WinWarbler's
screen - slick!!

73, Rich - W3ZJ


Re: WinWarbler version 2.1.6 is available

Richard B Drake
 

That's probably OK, I haven't seen any one throwing in meaningless hyphens -
not that they couldn't. But that reminds me of something else. Normally when
you click in a QTH, you hold down ALT and double click on it to put it into
the QTH field. However fairly often QTH's are two words like, "Mexico City".
In this case the way to do it is to highlight "Mexico City" hold down ALT
and single click. If you double click (as is habit to do) it does something
nutty like put Mexico into the callsign field. This has confused me on a
number of occasions. Suggest that double click be allowed on a multiword
QTH.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 11:34 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available


Underscore sounds right. I wonder whether we should eliminate the
minus/hyphen character. If you click on a hyphenated name like
Jean-Paul, you don't want Jean or Paul, you want Jean-Paul; is there a
down-side to this?

73,

Dave, AA6YQ



-----Original Message-----
From: muck@... [mailto:muck@...]
Sent: Friday, December 14, 2001 4:22 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

On Dec 13, 3:27pm, "Dave, AA6YQ" wrote:
}
} This is easy to fix, but lets first agree on the right
} set of delimiters. At the moment, WinWarbler considers
} the following as delimiters when you double-click
} in a receive pane: space, colon, comma, plus, minus,
} greater-than, less-than, and equals.
}
} Besides adding period, are there other
} nominations? Should anything be removed from this list?


The underscore "_"




Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=345371443>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Re: Commander 3.1.8 is available

Richard B Drake
 

Dave,

Actually the FT-817 does have "a" user selectable filter. A purchase option
is to get one of either of two available Collins mechanical filters. A 2.4
KHz SSB filter or a 500 Hz CW filter. I have the CW filter which is also
usable on digital modes. Similar to your original ICOM, you can select
either wide or narrow and what that means depends on which filter you have
installed. In my case narrow is available on CW and digital motes but not on
any of the voice modes. I didn't mention this to you before because as I
look at the CAT documentation it looks like the only way to change it is by
writing to the EPROM and I'm not sure I want to be the guinea pig for that
experiment :-) What I normally do is set the rig menus up so that I can
switch from wide to narrow by pressing one button on the rig front panel and
that works pretty well.

Bye the way, when filter selection is not available for a particular rig,
you probably should not show it on Commander's screen. I know it doesn't
work on either the Omni VI+ or the Ft-817 and I ignore it but some may think
that is a problem.

-----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 2:01 AM
To: dxlab@...
Cc: dhb@...
Subject: [dxlab] Commander 3.1.8 is available


This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable transceivers

- introduces new filter support

The new filter support requires some discussion.

As you may know, Commander began life exclusively supporting Icom
transceivers. Icom has a very simple model for filters: if you're
allowed to control them, you do so by choosing between "wide" and
"narrow". The 756PRO introduced a third option: "normal". Actual filter
bandwidths are a function of mode: "narrow" in CW mode might select a
250hz filter, but "narrow" in USB might select a 1900hz filter. A stock
radio might come equipped with some or all filters; you can change
what's there, or add more. After some thought, I refer to Icom's filter
model as a "fixed filter groups". The term "group" is appropriate
because something like "Wide" actually means

SSB 2400 hz
CW 250 hz
RTTY 500 hz

The adjective "fixed" is appropriate because one cannot add additional
groups. Your IC706 comes with wide and narrow filter groups; you can't
add a third filter group.

The challenge was to develop a filter model that would encompass support
not just for Icom (and look-alike TenTec) radios, but also for Yaesu and
Kenwood radios. As usual, Yaesu radios are all over the place. Some,
like the FT817, have no user selectable filters. Others, like the FT920,
provide fixed filter groups just like Icom's. Still others, like the
FT100, FT1000, and the MP1000s, provide direct control of IF filters. In
the MP1000, for example, one can choose a 2400hz second IF filter, a
1900hz third IF filter, and a 2400hz subreceiver filter; curiously (but
not surprisingly - this is Yaesu we're talking about) the MP1000's front
panel provides fixed filter groups (nor, nar1, nar2); direct filter
control is only available via PC control. It was for this reason that
K6SE developed MPFilters (see
http://www.qsl.net/va3cr/main/mpfilters.htm ), a very nice application
that provides direct control of an MP1000's IF filters. Clearly this
functionality belongs in Commander - but not just for MP1000s, we need
it for all radios that support direct control of IF filters.

A second form of direct control is found in recent Kenwood (e.g. TS-870)
and Icom (e.g. 756PROII) transceivers - direct control of bandwidth via
DSP.

Direct control is powerful, but not particularly convenient. Every time
we change modes, we have to directly specify each IF filter or the DSP
filter bandwidth. What we need is the ability to define filter groups
like this:

SSB CW RTTY

DXing 2100 500 500
Contesting 1900 250 500
Ragchewing 2400 500 500

In a radio like the MP1000 MarkV, we'd be able to specify three IF
filters (main 2nd IF, main 3rd IF, subreceiver). Basically, you fill out
tables, and then select the appropriate filter group while operating.
Since these filter groups are managed by Commander, you can define as
many as you like - they simply appear as choices in a pulldown selection
control. This model is thus "user-defined filter groups"

From a control point of view, I suggest that we need two things:

1. the ability to select a filter group (either one of the fixed
groups supported by the radio's hardware, or one of the user-defined
filter groups for radios supporting direct control of IF or DSP filters)

2. the ability to see exactly what filter bandwidths are actually
selected and, for radios that allow direct control, the ability to
change each filter independently

In the case of a radio with fixed filter groups, like our IC706 cited
above, the filter bandwidth display would show exactly one value: the
radio's second IF filter bandwidth. Switch from Wide to Narrow, for from
CW to RTTY would display the appropriate value.

In the case of a radio with user-defined filter groups, like an MP1000
MkV, you can directly control the main 2nd IF, main 3rd IF, and
subreceiver filter bandwidths, or you can select a filter group like
"Ragchewing" to set all of them to specified values.

That's the theory. The description is more complicated than I'd like,
but I can't think of a simpler conceptual model that transcends product
lines. Critique and suggestions will be greatly appreciated.

I've started the transition to this model in version 3.1.8. I'd planned
to get a little further before making a release, but didn't want to
"fork" the code in order to respond to the above defects and enhancement
requests. So visually, this version is a little rougher than usual.
Specifically,

- Filter Group selection is no longer accomplished by radio buttons
below the VFO. The previous "Devices" tab has been renamed "Filters &
Devices", and includes a Filters panel; filter Group selection is
accomplished via pulldown control in this panel.

- For radios supporting direct control, Commander presents a
pulldown for each controllable IF. In this release, this only happens
for the Yeasu MP1000 and MP1000 MarkV - the functionality is identical
to K6SE's MPFilters application. I will add support for the other direct
control radios in future releases.

- the main window is wider than in previous versions

- the maximum number of frequency-dependent devices has been reduced
from 4 to 3 , and may go to 2 when macros buttons appear. Any
objections? Two covers an antenna tuner and an amplifier; is there a
need for more?

In 3.1.8, there is no display of IF filter bandwidths for radios with
fixed filter groups - I'll add this in the next release or two. There is
also no support for user-defined filter groups; that will come too. And
if your radio doesn't support fixed filter groups or direct control,
you'll see an empty Filters panel; future releases will properly
suppress this ugliness.

Let me know what you think.

To upgrade, see http://www.qsl.net/civ_commander/development.htm -
you'll be downloading
http://www.qsl.net/civ_commander/Commander318Update.exe . Note that this
release introduces a new radios.txt file - if you've been maintaining
your own version, you'll need to merge in your changes. Also note that
the keyword "Filters" has been changed to "FilterGroups".


73,

Dave, AA6YQ










To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Re: WinWarbler version 2.1.6 is available

Dave, AA6YQ <dhb@...>
 

Underscore sounds right. I wonder whether we should eliminate the
minus/hyphen character. If you click on a hyphenated name like
Jean-Paul, you don't want Jean or Paul, you want Jean-Paul; is there a
down-side to this?

73,

Dave, AA6YQ

-----Original Message-----
From: muck@... [mailto:muck@...]
Sent: Friday, December 14, 2001 4:22 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

On Dec 13, 3:27pm, "Dave, AA6YQ" wrote:
}
} This is easy to fix, but lets first agree on the right
} set of delimiters. At the moment, WinWarbler considers
} the following as delimiters when you double-click
} in a receive pane: space, colon, comma, plus, minus,
} greater-than, less-than, and equals.
}
} Besides adding period, are there other
} nominations? Should anything be removed from this list?


The underscore "_"




Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/spiderman.sonypictures.com> See the
Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=345371443>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


Re: WinWarbler version 2.1.6 is available

muck@...
 

On Dec 13, 3:27pm, "Dave, AA6YQ" wrote:
}
} This is easy to fix, but lets first agree on the right
} set of delimiters. At the moment, WinWarbler considers
} the following as delimiters when you double-click
} in a receive pane: space, colon, comma, plus, minus,
} greater-than, less-than, and equals.
}
} Besides adding period, are there other
} nominations? Should anything be removed from this list?


The underscore "_"


Re: Commander 3.1.8 is available

jim.steel <jim.steel@...>
 

Hi Dave
Trust you are well ??? quite busy here in the run up to Christmas etc etc. Have not
forgot about Commander will get round to it sometime over the weekend [probably]. Take
care,
Jim - M0ZAK

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 7:01 AM
To: dxlab@...
Cc: dhb@...
Subject: [dxlab] Commander 3.1.8 is available

This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable transceivers

- introduces new filter support

The new filter support requires some discussion.

As you may know, Commander began life exclusively supporting Icom
transceivers. Icom has a very simple model for filters: if you're
allowed to control them, you do so by choosing between "wide" and
"narrow". The 756PRO introduced a third option: "normal". Actual filter
bandwidths are a function of mode: "narrow" in CW mode might select a
250hz filter, but "narrow" in USB might select a 1900hz filter. A stock
radio might come equipped with some or all filters; you can change
what's there, or add more. After some thought, I refer to Icom's filter
model as a "fixed filter groups". The term "group" is appropriate
because something like "Wide" actually means

SSB 2400 hz
CW 250 hz
RTTY 500 hz

The adjective "fixed" is appropriate because one cannot add additional
groups. Your IC706 comes with wide and narrow filter groups; you can't
add a third filter group.

The challenge was to develop a filter model that would encompass support
not just for Icom (and look-alike TenTec) radios, but also for Yaesu and
Kenwood radios. As usual, Yaesu radios are all over the place. Some,
like the FT817, have no user selectable filters. Others, like the FT920,
provide fixed filter groups just like Icom's. Still others, like the
FT100, FT1000, and the MP1000s, provide direct control of IF filters. In
the MP1000, for example, one can choose a 2400hz second IF filter, a
1900hz third IF filter, and a 2400hz subreceiver filter; curiously (but
not surprisingly - this is Yaesu we're talking about) the MP1000's front
panel provides fixed filter groups (nor, nar1, nar2); direct filter
control is only available via PC control. It was for this reason that
K6SE developed MPFilters (see
http://www.qsl.net/va3cr/main/mpfilters.htm ), a very nice application
that provides direct control of an MP1000's IF filters. Clearly this
functionality belongs in Commander - but not just for MP1000s, we need
it for all radios that support direct control of IF filters.

A second form of direct control is found in recent Kenwood (e.g. TS-870)
and Icom (e.g. 756PROII) transceivers - direct control of bandwidth via
DSP.

Direct control is powerful, but not particularly convenient. Every time
we change modes, we have to directly specify each IF filter or the DSP
filter bandwidth. What we need is the ability to define filter groups
like this:

SSB CW RTTY

DXing 2100 500 500
Contesting 1900 250 500
Ragchewing 2400 500 500

In a radio like the MP1000 MarkV, we'd be able to specify three IF
filters (main 2nd IF, main 3rd IF, subreceiver). Basically, you fill out
tables, and then select the appropriate filter group while operating.
Since these filter groups are managed by Commander, you can define as
many as you like - they simply appear as choices in a pulldown selection
control. This model is thus "user-defined filter groups"

From a control point of view, I suggest that we need two things:

1. the ability to select a filter group (either one of the fixed
groups supported by the radio's hardware, or one of the user-defined
filter groups for radios supporting direct control of IF or DSP filters)

2. the ability to see exactly what filter bandwidths are actually
selected and, for radios that allow direct control, the ability to
change each filter independently

In the case of a radio with fixed filter groups, like our IC706 cited
above, the filter bandwidth display would show exactly one value: the
radio's second IF filter bandwidth. Switch from Wide to Narrow, for from
CW to RTTY would display the appropriate value.

In the case of a radio with user-defined filter groups, like an MP1000
MkV, you can directly control the main 2nd IF, main 3rd IF, and
subreceiver filter bandwidths, or you can select a filter group like
"Ragchewing" to set all of them to specified values.

That's the theory. The description is more complicated than I'd like,
but I can't think of a simpler conceptual model that transcends product
lines. Critique and suggestions will be greatly appreciated.

I've started the transition to this model in version 3.1.8. I'd planned
to get a little further before making a release, but didn't want to
"fork" the code in order to respond to the above defects and enhancement
requests. So visually, this version is a little rougher than usual.
Specifically,

- Filter Group selection is no longer accomplished by radio buttons
below the VFO. The previous "Devices" tab has been renamed "Filters &
Devices", and includes a Filters panel; filter Group selection is
accomplished via pulldown control in this panel.

- For radios supporting direct control, Commander presents a
pulldown for each controllable IF. In this release, this only happens
for the Yeasu MP1000 and MP1000 MarkV - the functionality is identical
to K6SE's MPFilters application. I will add support for the other direct
control radios in future releases.

- the main window is wider than in previous versions

- the maximum number of frequency-dependent devices has been reduced
from 4 to 3 , and may go to 2 when macros buttons appear. Any
objections? Two covers an antenna tuner and an amplifier; is there a
need for more?

In 3.1.8, there is no display of IF filter bandwidths for radios with
fixed filter groups - I'll add this in the next release or two. There is
also no support for user-defined filter groups; that will come too. And
if your radio doesn't support fixed filter groups or direct control,
you'll see an empty Filters panel; future releases will properly
suppress this ugliness.

Let me know what you think.

To upgrade, see http://www.qsl.net/civ_commander/development.htm -
you'll be downloading
http://www.qsl.net/civ_commander/Commander318Update.exe . Note that this
release introduces a new radios.txt file - if you've been maintaining
your own version, you'll need to merge in your changes. Also note that
the keyword "Filters" has been changed to "FilterGroups".


73,

Dave, AA6YQ










To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/01

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/01


Commander 3.1.8 is available

Dave, AA6YQ <dhb@...>
 

This release

- correctly sets the FT817's frequency when switching to or from CW
mode using the A=B or memory buttons

- supports CW-reverse and RTTY-reverse modes for capable transceivers

- introduces new filter support

The new filter support requires some discussion.

As you may know, Commander began life exclusively supporting Icom
transceivers. Icom has a very simple model for filters: if you're
allowed to control them, you do so by choosing between "wide" and
"narrow". The 756PRO introduced a third option: "normal". Actual filter
bandwidths are a function of mode: "narrow" in CW mode might select a
250hz filter, but "narrow" in USB might select a 1900hz filter. A stock
radio might come equipped with some or all filters; you can change
what's there, or add more. After some thought, I refer to Icom's filter
model as a "fixed filter groups". The term "group" is appropriate
because something like "Wide" actually means

SSB 2400 hz
CW 250 hz
RTTY 500 hz

The adjective "fixed" is appropriate because one cannot add additional
groups. Your IC706 comes with wide and narrow filter groups; you can't
add a third filter group.

The challenge was to develop a filter model that would encompass support
not just for Icom (and look-alike TenTec) radios, but also for Yaesu and
Kenwood radios. As usual, Yaesu radios are all over the place. Some,
like the FT817, have no user selectable filters. Others, like the FT920,
provide fixed filter groups just like Icom's. Still others, like the
FT100, FT1000, and the MP1000s, provide direct control of IF filters. In
the MP1000, for example, one can choose a 2400hz second IF filter, a
1900hz third IF filter, and a 2400hz subreceiver filter; curiously (but
not surprisingly - this is Yaesu we're talking about) the MP1000's front
panel provides fixed filter groups (nor, nar1, nar2); direct filter
control is only available via PC control. It was for this reason that
K6SE developed MPFilters (see
http://www.qsl.net/va3cr/main/mpfilters.htm ), a very nice application
that provides direct control of an MP1000's IF filters. Clearly this
functionality belongs in Commander - but not just for MP1000s, we need
it for all radios that support direct control of IF filters.

A second form of direct control is found in recent Kenwood (e.g. TS-870)
and Icom (e.g. 756PROII) transceivers - direct control of bandwidth via
DSP.

Direct control is powerful, but not particularly convenient. Every time
we change modes, we have to directly specify each IF filter or the DSP
filter bandwidth. What we need is the ability to define filter groups
like this:

SSB CW RTTY

DXing 2100 500 500
Contesting 1900 250 500
Ragchewing 2400 500 500

In a radio like the MP1000 MarkV, we'd be able to specify three IF
filters (main 2nd IF, main 3rd IF, subreceiver). Basically, you fill out
tables, and then select the appropriate filter group while operating.
Since these filter groups are managed by Commander, you can define as
many as you like - they simply appear as choices in a pulldown selection
control. This model is thus "user-defined filter groups"

From a control point of view, I suggest that we need two things:

1. the ability to select a filter group (either one of the fixed
groups supported by the radio's hardware, or one of the user-defined
filter groups for radios supporting direct control of IF or DSP filters)

2. the ability to see exactly what filter bandwidths are actually
selected and, for radios that allow direct control, the ability to
change each filter independently

In the case of a radio with fixed filter groups, like our IC706 cited
above, the filter bandwidth display would show exactly one value: the
radio's second IF filter bandwidth. Switch from Wide to Narrow, for from
CW to RTTY would display the appropriate value.

In the case of a radio with user-defined filter groups, like an MP1000
MkV, you can directly control the main 2nd IF, main 3rd IF, and
subreceiver filter bandwidths, or you can select a filter group like
"Ragchewing" to set all of them to specified values.

That's the theory. The description is more complicated than I'd like,
but I can't think of a simpler conceptual model that transcends product
lines. Critique and suggestions will be greatly appreciated.

I've started the transition to this model in version 3.1.8. I'd planned
to get a little further before making a release, but didn't want to
"fork" the code in order to respond to the above defects and enhancement
requests. So visually, this version is a little rougher than usual.
Specifically,

- Filter Group selection is no longer accomplished by radio buttons
below the VFO. The previous "Devices" tab has been renamed "Filters &
Devices", and includes a Filters panel; filter Group selection is
accomplished via pulldown control in this panel.

- For radios supporting direct control, Commander presents a
pulldown for each controllable IF. In this release, this only happens
for the Yeasu MP1000 and MP1000 MarkV - the functionality is identical
to K6SE's MPFilters application. I will add support for the other direct
control radios in future releases.

- the main window is wider than in previous versions

- the maximum number of frequency-dependent devices has been reduced
from 4 to 3 , and may go to 2 when macros buttons appear. Any
objections? Two covers an antenna tuner and an amplifier; is there a
need for more?

In 3.1.8, there is no display of IF filter bandwidths for radios with
fixed filter groups - I'll add this in the next release or two. There is
also no support for user-defined filter groups; that will come too. And
if your radio doesn't support fixed filter groups or direct control,
you'll see an empty Filters panel; future releases will properly
suppress this ugliness.

Let me know what you think.

To upgrade, see http://www.qsl.net/civ_commander/development.htm -
you'll be downloading
http://www.qsl.net/civ_commander/Commander318Update.exe . Note that this
release introduces a new radios.txt file - if you've been maintaining
your own version, you'll need to merge in your changes. Also note that
the keyword "Filters" has been changed to "FilterGroups".


73,

Dave, AA6YQ


Re: WinWarbler version 2.1.6 is available

Richard B Drake
 

Aside from the occasional garble which we can't do anything about, that
sounds like a good list to me.

73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Thursday, December 13, 2001 6:28 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available


This is easy to fix, but lets first agree on the right set of
delimiters. At the moment, WinWarbler considers the following as
delimiters when you double-click in a receive pane: space, colon, comma,
plus, minus, greater-than, less-than, and equals.

Besides adding period, are there other nominations? Should anything be
removed from this list?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Thursday, December 13, 2001 2:32 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

I have a pet peeve on PSK31. It's not WinWarbler's fault Dave, but
perhaps
WinWarbler could fix it. People who type their callsigns as W3ZJ...W3ZJ
and
give their names as Rich...Rich. Do you know what happens when you try
to
click that into the log? :-) We could holler at them and ask them to
stop
that nonsense or we could make "." a delimiter since it doesn't normally
appear in callsigns or names. What do you think?

----
73, Rich - W3ZJ



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



SpotCollector users: DX Central changes

Dave, AA6YQ <dhb@...>
 

Besides switching from port 6904 to port 23, DX Central no longer
requires a password. You can remove the password from your DX Central
login sequence via the following steps:

1. click the Config button to display SpotCollector's Configuration
window

2. click the Spot Sources tab

3. in the Telnet panel, delete the contents of DX Central's
password textbox


73,

Dave, AA6YQ


Re: WinWarbler version 2.1.6 is available

Dave, AA6YQ <dhb@...>
 

This is easy to fix, but lets first agree on the right set of
delimiters. At the moment, WinWarbler considers the following as
delimiters when you double-click in a receive pane: space, colon, comma,
plus, minus, greater-than, less-than, and equals.

Besides adding period, are there other nominations? Should anything be
removed from this list?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Thursday, December 13, 2001 2:32 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

I have a pet peeve on PSK31. It's not WinWarbler's fault Dave, but
perhaps
WinWarbler could fix it. People who type their callsigns as W3ZJ...W3ZJ
and
give their names as Rich...Rich. Do you know what happens when you try
to
click that into the log? :-) We could holler at them and ask them to
stop
that nonsense or we could make "." a delimiter since it doesn't normally
appear in callsigns or names. What do you think?

----
73, Rich - W3ZJ



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


Re: WinWarbler 2.1.7 is available

Ben Kraaijenhagen <PD5SAM@...>
 

That's quick :-) Fixed Dave, nice going!

73, Ben

-----Oorspronkelijk bericht-----
Van: Dave, AA6YQ [mailto:dhb@...]
Verzonden: donderdag 13 december 2001 23:43
Aan: dxlab@...
Onderwerp: [dxlab] WinWarbler 2.1.7 is available


This release corrects the defect reported by Ben below.

To upgrade, follow the instructions in
http://www.qsl.net/winwarbler/development.htm -- you'll be downloading
http://www.qsl.net/winwarbler/WinWarbler217Update.exe .

73,

Dave, AA6YQ