|
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz
or so below 24,890 for a while. Tuning to him - even when split with
the TX VFO in the band - caused Commander to blank the bandspread and
switch to the "out of band" color. Short of editing the Sub-Band
definition files to "extend" each band by 1 KHz, is there a way to:
(1) provide some tolerance on the band edges or (2) trigger the
blanking/out of band action based on the transmit frequency?
If not, could there be?
73,
... Joe, W4TV
|
I would guess that, technically, if the other fellow is out of band, then it's not a valid contact for DXCC.? I have run into that with a DX station recently, when I zero-beat him I concluded he was 30 Hz low.? Now, my rig might not be exactly on frequency... my justification for counting the QSO was that at least PART of his signal was within the band.
Laugh if you will...
73 de Chuck, WS1L
On Tue, Mar 1, 2016 at 9:51 AM, 'Joe Subich, W4TV' lists@... [dxlab] <dxlab@...> wrote:
?
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz
or so below 24,890 for a while. Tuning to him - even when split with
the TX VFO in the band - caused Commander to blank the bandspread and
switch to the "out of band" color. Short of editing the Sub-Band
definition files to "extend" each band by 1 KHz, is there a way to:
(1) provide some tolerance on the band edges or (2) trigger the
blanking/out of band action based on the transmit frequency?
If not, could there be?
73,
... Joe, W4TV
--
=================== Chuck Chandler ===================
|
Just worked him 17M at 10.068126 (126 Hz inside the band) all the
spots I see for him in 12M show he is on or slightly above the band
edge. 3 of the 12M spots were from reverse beacon stations that show
him at 24.891. He is working close to the band edges and guess he
could have slipped a bit at one point but I would be pretty careful
that close to the edge.
73, Rich - W3ZJ
On 3/1/2016 10:51 AM, 'Joe Subich,
W4TV' lists@... [dxlab] wrote:
toggle quoted message
Show quoted text
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz
or so below 24,890 for a while. Tuning to him - even when split with
the TX VFO in the band - caused Commander to blank the bandspread and
switch to the "out of band" color. Short of editing the Sub-Band
definition files to "extend" each band by 1 KHz, is there a way to:
(1) provide some tolerance on the band edges or (2) trigger the
blanking/out of band action based on the transmit frequency?
If not, could there be?
73,
... Joe, W4TV
|
Please forgive fat fingers that was supposed to say 18.068126 :-(
73, Rich - W3ZJ
On 3/1/2016 11:54 AM, Rich - W3ZJ
rich@... [dxlab] wrote:
toggle quoted message
Show quoted text
Just
worked him 17M at 10.068126 (126 Hz inside the band) all the spots
I see for him in 12M show he is on or slightly above the band
edge. 3 of the 12M spots were from reverse beacon stations that
show him at 24.891. He is working close to the band edges and
guess he could have slipped a bit at one point but I would be
pretty careful that close to the edge.
73, Rich - W3ZJ
|
AA6YQ comments below
-----Original Message----- From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:52 AM To: dxlab@... Subject: [dxlab] Commander Bandspread "tolerance" This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color. How did that impede your ability to work 3XY1T? Presumably you weren't interested in other 17m spots at that moment.
73, Dave, AA6YQ
|
On Tue, Mar 1, 2016 at 6:30 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:52 AM
To: dxlab@...
Subject: [dxlab] Commander Bandspread "tolerance"
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color.
How did that impede your ability to work 3XY1T? Presumably you weren't interested in other 17m spots at that moment.
When working split, a considerate operator would try to be aware of other DX "up the band", and try to avoid transmitting over it. It might also be helpful when determining the spread of the target DX's pile (if there are multiple "clumps", some of them may be calling other DX). 73, ~iain / N6ML
|
+++ AA6YQ comments below
toggle quoted message
Show quoted text
-----Original Message----- From: dxlab@... [mailto:dxlab@...] Sent: Tuesday, March 01, 2016 10:24 PM To: dxlab Subject: Re: [dxlab] Commander Bandspread "tolerance" On Tue, Mar 1, 2016 at 6:30 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:52 AM
To: dxlab@...
Subject: [dxlab] Commander Bandspread "tolerance"
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color.
How did that impede your ability to work 3XY1T? Presumably you weren't interested in other 17m spots at that moment.
When working split, a considerate operator would try to be aware of other DX "up the band", and try to avoid transmitting over it. +++ Right, but the considerate operator should do that by tuning up the band and listening, not by relying on cluster spots. It might also be helpful when determining the spread of the target DX's pile (if there are multiple "clumps", some of them may be calling other DX). +++ Callers in a pileup generally aren't spotted. +++ That said, I don't see or recall any reason to hide spots when you tune out of the current band. I've sent you and Joe W4TV a version of Commander that no longer does that; please let me know how it goes... 73, Dave, AA6YQ
|
On Tue, Mar 1, 2016 at 9:49 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
+++ AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:24 PM
To: dxlab
Subject: Re: [dxlab] Commander Bandspread "tolerance"
On Tue, Mar 1, 2016 at 6:30 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:52 AM
To: dxlab@...
Subject: [dxlab] Commander Bandspread "tolerance"
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color.
How did that impede your ability to work 3XY1T? Presumably you weren't interested in other 17m spots at that moment.
When working split, a considerate operator would try to be aware of other DX "up the band", and try to avoid transmitting over it.
+++ Right, but the considerate operator should do that by tuning up the band and listening, not by relying on cluster spots.
I may not be able to hear the other DX, though - depending on prop to my location. Just because I don't hear it doesn't mean I wouldn't be QRMing by transmitting on/near it. It might also be helpful when determining the spread of the target DX's pile (if there are multiple "clumps", some of them may be calling other DX).
+++ Callers in a pileup generally aren't spotted. No, but if you hear a clump of callers, and there's some juicy DX spotted below it, you can piece the picture together. It's all about being aware of your surroundings - like using your mirrors and your ears when driving. +++ That said, I don't see or recall any reason to hide spots when you tune out of the current band. I've sent you and Joe W4TV a version of Commander that no longer does that; please let me know how it goes... It "works as advertised" (from a quick check). I'll be on the lookout for anomalies... 73, ~iain / N6ML
|
+++ That said, I don't see or recall any reason to hide spots when
you tune out of the current band. I've sent you and Joe W4TV a
version of Commander that no longer does that; please let me know
how it goes... Works as advertised. I appreciate not losing spots in the band map when tuning the RX a short way out of the band. I have other soft- ware and hardware that inhibit PTT when the transmitter is out of band. 73, ... Joe, W4TV On 3/2/2016 12:49 AM, ' Dave AA6YQ' aa6yq@... [dxlab] wrote: +++ AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:24 PM
To: dxlab
Subject: Re: [dxlab] Commander Bandspread "tolerance"
On Tue, Mar 1, 2016 at 6:30 PM, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, March 01, 2016 10:52 AM
To: dxlab@...
Subject: [dxlab] Commander Bandspread "tolerance"
This morning 3XY1T was calling CQ (split) just a hundred (if that) Hz or so below 24,890 for a while. Tuning to him - even when split with the TX VFO in the band - caused Commander to blank the bandspread and switch to the "out of band" color.
How did that impede your ability to work 3XY1T? Presumably you weren't interested in other 17m spots at that moment.
When working split, a considerate operator would try to be aware of other DX "up the band", and try to avoid transmitting over it.
+++ Right, but the considerate operator should do that by tuning up the band and listening, not by relying on cluster spots.
It might also be helpful when determining the spread of the target DX's pile (if there are multiple "clumps", some of them may be calling other DX).
+++ Callers in a pileup generally aren't spotted.
+++ That said, I don't see or recall any reason to hide spots when you tune out of the current band. I've sent you and Joe W4TV a version of Commander that no longer does that; please let me know how it goes...
73,
Dave, AA6YQ
------------------------------------
Posted by: " Dave AA6YQ" <aa6yq@...>
------------------------------------
------------------------------------
Yahoo Groups Links
|
AA6YQ comments below
-----Original Message----- From: dxlab@... [mailto:dxlab@...] Sent: Wednesday, March 02, 2016 8:21 PM To: dxlab@... Subject: Re: [dxlab] Commander Bandspread "tolerance" > +++ That said, I don't see or recall any reason to hide spots when > you tune out of the current band. I've sent you and Joe W4TV a > version of Commander that no longer does that; please let me know > how it goes... Works as advertised. I appreciate not losing spots in the band map when tuning the RX a short way out of the band. I have other soft- ware and hardware that inhibit PTT when the transmitter is out of band. Thanks for the testing, Joe!
73, Dave, AA6YQ
|
Chuck, WS1L
iain macdonnell