Elecraft

Data Mode Sideband

Classic

List

Threaded

19 messages Options

Mike Harris-9

Data Mode Sideband

Guru's,

Trying to get a handle on a problem with frequency reporting in MMTTY.
Not an operational issue, I just don't take any notice of MMTTY
frequencies. In AFSK A mode they are incorrect.

The following has become apparent, albeit undocumented.

Mode AFSK A normal LSB. I assumed that if by using the ALT function and
consequently switching to TX DATA REV that the sideband was switched
from LSB to USB. Apparently not the case. It looks like keying is
reversed but shifted in frequency on the waterfall by one keying shift
value eg 170Hz. However, whilst in data mode selection the sideband
indicator does change from LSB to USB using ALT.

Mode DATA A normal USB. Using the ALT function does indeed swap sidebands.

Can anyone confirm or deny this observation and is this the way it is
intended to function?

Regards,

Mike VP8NO
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Subich, W4TV-4

Re: Data Mode Sideband

> Mode AFSK A normal LSB. I assumed that if by using the ALT function
> and consequently switching to TX DATA REV that the sideband was
> switched from LSB to USB.

It is.

> It looks like keying is reversed but shifted in frequency on the
> waterfall by one keying shift value eg 170Hz. However, whilst in data
> mode selection the sideband indicator does change from LSB to USB
> using ALT.

The MARK frequency in the K3 does not change - it's still 2125. That
results in a displayed SPACE frequency. Wayne/Lyle, you probably want
to offset MARK by Shift when in AFSK REV (and maybe FSK REV). Remember,
MARK is always the higher RF frequency so the tones have to be exchanged
in AFSK REV and both mark/direction of the shift changed in FSK REV.

73,

... Joe, W4TV

On 2014-08-23 2:03 PM, Mike Harris wrote:

> Guru's,
>
> Trying to get a handle on a problem with frequency reporting in MMTTY.
> Not an operational issue, I just don't take any notice of MMTTY
> frequencies. In AFSK A mode they are incorrect.
>
> The following has become apparent, albeit undocumented.
>
> Mode AFSK A normal LSB. I assumed that if by using the ALT function and
> consequently switching to TX DATA REV that the sideband was switched
> from LSB to USB. Apparently not the case. It looks like keying is
> reversed but shifted in frequency on the waterfall by one keying shift
> value eg 170Hz. However, whilst in data mode selection the sideband
> indicator does change from LSB to USB using ALT.
>
> Mode DATA A normal USB. Using the ALT function does indeed swap sidebands.
>
> Can anyone confirm or deny this observation and is this the way it is
> intended to function?
>
> Regards,
>
> Mike VP8NO
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Mike Harris-9

Re: Data Mode Sideband

Not so sure. I monitored the TX frequency on another RX and the only
change was the slight shift I mentioned, not what would, in my case
(1445Hz Mark) be approx 3kHz.

Using DATA A, which really does swap sideband results in a near 3k
frequency shift.

Regards,

Mike VP8NO

On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>
>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>> and consequently switching to TX DATA REV that the sideband was
>> switched from LSB to USB.
>
> It is.
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm-4

Re: Data Mode Sideband

Mike,

Do you have MMTTY set for 1445Hz Mark *and* the K3. Hold PITCH button
to check/change.
That would make a difference in AFSK A, but not in DATA A mode

73,
Don W3FPR

On 8/23/2014 3:00 PM, Mike Harris wrote:

> Not so sure. I monitored the TX frequency on another RX and the only
> change was the slight shift I mentioned, not what would, in my case
> (1445Hz Mark) be approx 3kHz.
>
> Using DATA A, which really does swap sideband results in a near 3k
> frequency shift.
>
> Regards,
>
> Mike VP8NO
>
> On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>>
>>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>>> and consequently switching to TX DATA REV that the sideband was
>>> switched from LSB to USB.
>>
>> It is.
>>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Richard Ferch

Re: Data Mode Sideband

In reply to this post by Mike Harris-9

In AFSK A the K3 displays the actual Mark frequency on its dial, not the
suppressed carrier or BFO frequency as it does in DATA A.

I believe what is happening is the following (this is the same as what Joe
stated, just in different words and using a different PITCH setting): In
normal AFSK A, if the PITCH setting is 1445 Hz, the two audio tones are at
1445 Hz Mark and 1615 Hz Space. In AFSK A - REV, the K3's dial still
displays a frequency 1445 Hz different from the suppressed carrier
frequency (1445 Hz higher in USB vs. 1445 Hz lower in LSB). However, in
REV mode the tone that is 1445 Hz away from the suppressed carrier is the
Space frequency, not the Mark frequency (i.e. it is the lower of the two
frequencies, not the higher). This difference results in a 170 Hz
discrepancy between the dial frequency and the actual Mark frequency (the
higher of the two frequencies at RF).

To put it another way, the K3's dial is reporting the Space (lower)
frequency in AFSK A - REV instead of the amateur standard Mark (higher)
frequency. If the two tones in normal AFSK A are 1445 Hz Mark and 1615 Hz
Space, then in AFSK A - REV the two tones should be 1615 Hz Mark and 1445
Hz Space, and the displayed dial frequency should be 1615 Hz above the
suppressed carrier, not 1445 Hz higher.

73,
Rich VE3KI

VP8NO wrote:

Not so sure. I monitored the TX frequency on another RX and the only
change was the slight shift I mentioned, not what would, in my case
(1445Hz Mark) be approx 3kHz.

Using DATA A, which really does swap sideband results in a near 3k
frequency shift.

Regards,

Mike VP8NO

On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>
>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>> and consequently switching to TX DATA REV that the sideband was
>> switched from LSB to USB.
>
> It is.
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Subich, W4TV-4

Re: Data Mode Sideband

Rich is correct. The K3 shifts the carrier frequency between AFSK and
AFSK REV (of FSK and FSK REV) but fails to account for the the exchange
of mark/space tones.

To be rigorous, MMTTY and the K3 should probably use 1275 Hz Mark in
AFSK (lower tone = higher RF frequency) and 1445 Hz Mark in AFSK REV
(higher tone = higher RF frequency).

73,

... Joe, W4TV

On 2014-08-23 3:55 PM, Richard Ferch wrote:

> In AFSK A the K3 displays the actual Mark frequency on its dial, not the
> suppressed carrier or BFO frequency as it does in DATA A.
>
> I believe what is happening is the following (this is the same as what Joe
> stated, just in different words and using a different PITCH setting): In
> normal AFSK A, if the PITCH setting is 1445 Hz, the two audio tones are at
> 1445 Hz Mark and 1615 Hz Space. In AFSK A - REV, the K3's dial still
> displays a frequency 1445 Hz different from the suppressed carrier
> frequency (1445 Hz higher in USB vs. 1445 Hz lower in LSB). However, in
> REV mode the tone that is 1445 Hz away from the suppressed carrier is the
> Space frequency, not the Mark frequency (i.e. it is the lower of the two
> frequencies, not the higher). This difference results in a 170 Hz
> discrepancy between the dial frequency and the actual Mark frequency (the
> higher of the two frequencies at RF).
>
> To put it another way, the K3's dial is reporting the Space (lower)
> frequency in AFSK A - REV instead of the amateur standard Mark (higher)
> frequency. If the two tones in normal AFSK A are 1445 Hz Mark and 1615 Hz
> Space, then in AFSK A - REV the two tones should be 1615 Hz Mark and 1445
> Hz Space, and the displayed dial frequency should be 1615 Hz above the
> suppressed carrier, not 1445 Hz higher.
>
> 73,
> Rich VE3KI
>
>
> VP8NO wrote:
>
> Not so sure. I monitored the TX frequency on another RX and the only
> change was the slight shift I mentioned, not what would, in my case
> (1445Hz Mark) be approx 3kHz.
>
> Using DATA A, which really does swap sideband results in a near 3k
> frequency shift.
>
> Regards,
>
> Mike VP8NO
>
> On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>>
>>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>>> and consequently switching to TX DATA REV that the sideband was
>>> switched from LSB to USB.
>>
>> It is.
>>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Mike Harris-9

Re: Data Mode Sideband

In reply to this post by Don Wilhelm-4

Hi Don,

I've made thousands of RTTY QSOs. I know what I'm doing.

Pondering the problem further I now believe that AFSK A and AFSK A Rev
are similar in operation to CW and CW Rev. Theoretically the decode
will (should) stay correctly tuned as the "suppressed carrier" is
shifted to suit. The handbook offers no clarification on this.

Important note: I run MMTTY in Logger32 which doesn't present the MMTTY
UI quite the same as native MMTTY. What I attribute to MMTTY is likely
a consequence of the way Logger32 talks to MMTTY.

The situation, which actually is of no consequence, is that MMTTY or
whatever doesn't understand the frequency manipulations that the K3
performs with respect to VFO display vs mode. The K3 reported frequency
via the IF; command is interpreted as the suppressed carrier frequency,
which it isn't. ALT is responded to as a sideband change, which it
isn't in conventional terms eg switching sidebands in SSB because of
additional frequency manipulation in the K3.

The consequences are that the RTTY frequency MMTTY displays is incorrect
and hence any logging info produced would also be incorrect. This could
also be an issue with other data applications. I don't run any others
so that is for others to determine.

Now in my circumstance as I have said it is of no consequence. Logger32
correctly logs the displayed frequency from the K3 as reported by IF;.
I simply ignore any frequency displays that this implementation of MMTTY
presents.

The reason for trying to get a detailed handle on what was happening was
to see if it was possible to somehow, through a radio profile or other
means, to bring everything into line without too much effort.

Regards,

Mike VP8NO

On 23/08/2014 16:50, Don Wilhelm wrote:

> Mike,
>
> Do you have MMTTY set for 1445Hz Mark *and* the K3. Hold PITCH button
> to check/change.
> That would make a difference in AFSK A, but not in DATA A mode
>
> 73,
> Don W3FPR
>
> On 8/23/2014 3:00 PM, Mike Harris wrote:
>> Not so sure. I monitored the TX frequency on another RX and the only
>> change was the slight shift I mentioned, not what would, in my case
>> (1445Hz Mark) be approx 3kHz.
>>
>> Using DATA A, which really does swap sideband results in a near 3k
>> frequency shift.
>>
>> Regards,
>>
>> Mike VP8NO
>>
>> On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>>>
>>>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>>>> and consequently switching to TX DATA REV that the sideband was
>>>> switched from LSB to USB.
>>>
>>> It is.

Joe Subich, W4TV-4

Re: Data Mode Sideband

Mike,

> Important note: I run MMTTY in Logger32 which doesn't present the
> MMTTY UI quite the same as native MMTTY. What I attribute to MMTTY is
> likely a consequence of the way Logger32 talks to MMTTY.

More than likely it is not MMTTY that is doing the display frequency
manipulating but the Logger32 Digital interface code.

The native MMTTY interface will correct for USB operation. In USB one
selects REV in the display and MMTTY will correctly use MARK + Shift
for internal frequency calculations.

Last time I checked the Logger32 "Display frequency from Radio" option
in the Sound Card Data Window as dumb - it did not understand that the
K3 and most Yaesu radios could report "Mark" frequency in AFSK - and
simply added (AFSK) or subtracted (AFSK-R) MMTTY's MARK frequency from
the reported radio frequency. This results in incorrect display for
two reasons - 1) with the K3 it is applying an offset that is already
applied in the reported frequency, 2) the offset is applied in the
wrong direction since Logger32 always assumes AFSK (audio) is USB.

Logger32 has had the same brain dead interface for the Sound Card Data
Window for perhaps 10 years. It did not work correctly with the Yaesu
FT-1000D/MP/MKV and still does not work correctly with the K3.

None of this absolves the K3/and P3 of one mistake. The P3 frequency
cursor (and K3 frequency display) appear to show the SPACE frequency
in AFSK R (and FSK R) - perhaps they are really "reverse" as opposed
to "opposite sideband" <G>.

73,

... Joe, W4TV

On 2014-08-24 8:49 AM, Mike Harris wrote:

> Hi Don,
>
> I've made thousands of RTTY QSOs. I know what I'm doing.
>
> Pondering the problem further I now believe that AFSK A and AFSK A Rev
> are similar in operation to CW and CW Rev. Theoretically the decode
> will (should) stay correctly tuned as the "suppressed carrier" is
> shifted to suit. The handbook offers no clarification on this.
>
> Important note: I run MMTTY in Logger32 which doesn't present the MMTTY
> UI quite the same as native MMTTY. What I attribute to MMTTY is likely
> a consequence of the way Logger32 talks to MMTTY.
>
> The situation, which actually is of no consequence, is that MMTTY or
> whatever doesn't understand the frequency manipulations that the K3
> performs with respect to VFO display vs mode. The K3 reported frequency
> via the IF; command is interpreted as the suppressed carrier frequency,
> which it isn't. ALT is responded to as a sideband change, which it
> isn't in conventional terms eg switching sidebands in SSB because of
> additional frequency manipulation in the K3.
>
> The consequences are that the RTTY frequency MMTTY displays is incorrect
> and hence any logging info produced would also be incorrect. This could
> also be an issue with other data applications. I don't run any others
> so that is for others to determine.
>
> Now in my circumstance as I have said it is of no consequence. Logger32
> correctly logs the displayed frequency from the K3 as reported by IF;. I
> simply ignore any frequency displays that this implementation of MMTTY
> presents.
>
> The reason for trying to get a detailed handle on what was happening was
> to see if it was possible to somehow, through a radio profile or other
> means, to bring everything into line without too much effort.
>
> Regards,
>
> Mike VP8NO
>
> On 23/08/2014 16:50, Don Wilhelm wrote:
>> Mike,
>>
>> Do you have MMTTY set for 1445Hz Mark *and* the K3. Hold PITCH button
>> to check/change.
>> That would make a difference in AFSK A, but not in DATA A mode
>>
>> 73,
>> Don W3FPR
>>
>> On 8/23/2014 3:00 PM, Mike Harris wrote:
>>> Not so sure. I monitored the TX frequency on another RX and the only
>>> change was the slight shift I mentioned, not what would, in my case
>>> (1445Hz Mark) be approx 3kHz.
>>>
>>> Using DATA A, which really does swap sideband results in a near 3k
>>> frequency shift.
>>>
>>> Regards,
>>>
>>> Mike VP8NO
>>>
>>> On 23/08/2014 15:27, Joe Subich, W4TV wrote:
>>>>
>>>>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
>>>>> and consequently switching to TX DATA REV that the sideband was
>>>>> switched from LSB to USB.
>>>>
>>>> It is.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

NK7Z

Re: Data Mode Sideband

In reply to this post by Mike Harris-9

Hi,
Please DO NOT take this discussion off list... Or if you do, please
include me in the loop. I find this most interesting.
--
Thanks and 73's,
For equipment, and software setups and reviews see:
www.nk7z.net
for MixW support see;
http://groups.yahoo.com/neo/groups/mixw/info
for Dopplergram information see:
http://groups.yahoo.com/neo/groups/dopplergram/info
for MM-SSTV see:
http://groups.yahoo.com/neo/groups/MM-SSTV/info

On Sun, 2014-08-24 at 09:49 -0300, Mike Harris wrote:

> Hi Don,
>
> I've made thousands of RTTY QSOs. I know what I'm doing.
>
> Pondering the problem further I now believe that AFSK A and AFSK A Rev
> are similar in operation to CW and CW Rev. Theoretically the decode
> will (should) stay correctly tuned as the "suppressed carrier" is
> shifted to suit. The handbook offers no clarification on this.
>
> Important note: I run MMTTY in Logger32 which doesn't present the MMTTY
> UI quite the same as native MMTTY. What I attribute to MMTTY is likely
> a consequence of the way Logger32 talks to MMTTY.
>
> The situation, which actually is of no consequence, is that MMTTY or
> whatever doesn't understand the frequency manipulations that the K3
> performs with respect to VFO display vs mode. The K3 reported frequency
> via the IF; command is interpreted as the suppressed carrier frequency,
> which it isn't. ALT is responded to as a sideband change, which it
> isn't in conventional terms eg switching sidebands in SSB because of
> additional frequency manipulation in the K3.
>
> The consequences are that the RTTY frequency MMTTY displays is incorrect
> and hence any logging info produced would also be incorrect. This could
> also be an issue with other data applications. I don't run any others
> so that is for others to determine.
>
> Now in my circumstance as I have said it is of no consequence. Logger32
> correctly logs the displayed frequency from the K3 as reported by IF;.
> I simply ignore any frequency displays that this implementation of MMTTY
> presents.
>
> The reason for trying to get a detailed handle on what was happening was
> to see if it was possible to somehow, through a radio profile or other
> means, to bring everything into line without too much effort.
>
> Regards,
>
> Mike VP8NO
>
> On 23/08/2014 16:50, Don Wilhelm wrote:
> > Mike,
> >
> > Do you have MMTTY set for 1445Hz Mark *and* the K3. Hold PITCH button
> > to check/change.
> > That would make a difference in AFSK A, but not in DATA A mode
> >
> > 73,
> > Don W3FPR
> >
> > On 8/23/2014 3:00 PM, Mike Harris wrote:
> >> Not so sure. I monitored the TX frequency on another RX and the only
> >> change was the slight shift I mentioned, not what would, in my case
> >> (1445Hz Mark) be approx 3kHz.
> >>
> >> Using DATA A, which really does swap sideband results in a near 3k
> >> frequency shift.
> >>
> >> Regards,
> >>
> >> Mike VP8NO
> >>
> >> On 23/08/2014 15:27, Joe Subich, W4TV wrote:
> >>>
> >>>> Mode AFSK A normal LSB. I assumed that if by using the ALT function
> >>>> and consequently switching to TX DATA REV that the sideband was
> >>>> switched from LSB to USB.
> >>>
> >>> It is.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

Don Wilhelm-4

Re: Data Mode Sideband

I have used MMTTY and find no problem, but I have not tried running
MMTTY under Logger32, and that appears to be the problem source.

I believe Joe Subich W4TV has explained the problem scenario
adequately. As such, the thread should be closed and the individual
problem areas addressed to the parties responsible for the 'strange
happenings'.

As Joe pointed out, the K3/P3 may have a space/mark problem, but
Logger32 has a bigger problem in not recognizing the various Data
sub-modes in the K3 properly.

73,
Don W3FPR

On 8/24/2014 7:12 PM, David Cole wrote:
> Hi,
> Please DO NOT take this discussion off list... Or if you do, please
> include me in the loop. I find this most interesting.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Lynn W. Taylor, WB6UUT

Re: Data Mode Sideband

In reply to this post by NK7Z

On 8/24/2014 4:12 PM, David Cole wrote:
> Hi,
> Please DO NOT take this discussion off list... Or if you do, please
> include me in the loop. I find this most interesting.
Please do not take this discussion (or others) off list.

When you do, when you go off list, the information is no longer shared
with those of us reading along.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Joe Subich, W4TV-4

Re: Data Mode Sideband

There was nothing "off list".

Logger32 does not properly update the "frequency bar" above the
Spectrum/Waterfall if the transceiver reports "Mark" frequency in
AFSK or FSK. The "radio frequency" will be 'off' by the value of
the MARK. This is a failing of Logger32 ...

The K3/P3 does not change the MARK tone/cursor when switching
between AFSK/AFSK R or between FSK/FSK R. There is some debate
whether the "reverse" modes are meant to represent shift in the
opposite direction from normal (in other words, shift *UP* in
"reverse") or the "reverse" modes are the opposite sideband
although amateur practice is to reverse the mark/space tones
when shifting sidebands so the shift is correct in either sideband.

73,

... Joe, W4TV

On 2014-08-24 11:03 PM, Lynn W. Taylor, WB6UUT wrote:

> On 8/24/2014 4:12 PM, David Cole wrote:
>> Hi,
>> Please DO NOT take this discussion off list... Or if you do, please
>> include me in the loop. I find this most interesting.
> Please do not take this discussion (or others) off list.
>
> When you do, when you go off list, the information is no longer shared
> with those of us reading along.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>

Lynn W. Taylor, WB6UUT

Re: Data Mode Sideband

Joe,

I don't know what, if anything, was taken off list. I didn't mean this
as an accusation.

I'm simply repeating a concept -- that information taken off list is
lost to the rest of us, and I renew my plea that discussions not be
taken off list.

73 -- Lynn

On 8/24/2014 8:31 PM, Joe Subich, W4TV wrote:
> There was nothing "off list".

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

NK7Z

Re: Data Mode Sideband

In reply to this post by NK7Z

I brought up OFF LIST, and I did so in order to be able to see what was
going on here... AFAIK nothing has been taken off list... I just want
to be sure it is not, sometimes interesting discussions just stop, and I
can only guess they have moved off list, hence the request. This is a
fascinating discussion.
--
Thanks and 73's,
For equipment, and software setups and reviews see:
www.nk7z.net
for MixW support see;
http://groups.yahoo.com/neo/groups/mixw/info
for Dopplergram information see:
http://groups.yahoo.com/neo/groups/dopplergram/info
for MM-SSTV see:
http://groups.yahoo.com/neo/groups/MM-SSTV/info

On Sun, 2014-08-24 at 16:12 -0700, David Cole wrote:
> Hi,
> Please DO NOT take this discussion off list... Or if you do, please
> include me in the loop. I find this most interesting.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Lynn W. Taylor, WB6UUT

Re: Data Mode Sideband

One small grumble with the list is that it is configured so that "reply"
goes back to the originator, not to the list.

If we aren't careful to "reply-all" or "reply-list," the conversation
moves off list by accident.

On 8/25/2014 6:16 AM, David Cole wrote:
> I brought up OFF LIST, and I did so in order to be able to see what was
> going on here... AFAIK nothing has been taken off list... I just want
> to be sure it is not, sometimes interesting discussions just stop, and I
> can only guess they have moved off list, hence the request. This is a
> fascinating discussion.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Phil Wheeler-2

Re: Data Mode Sideband

Nice to have that choice, not available without
more effort with some lists.

Can't please everyone, it seems.

Phil W7OX

On 8/25/14, 10:22 AM, Lynn W. Taylor, WB6UUT wrote:

> One small grumble with the list is that it is
> configured so that "reply" goes back to the
> originator, not to the list.
>
> If we aren't careful to "reply-all" or
> "reply-list," the conversation moves off list by
> accident.
>
> On 8/25/2014 6:16 AM, David Cole wrote:
>> I brought up OFF LIST, and I did so in order to
>> be able to see what was
>> going on here... AFAIK nothing has been taken
>> off list... I just want
>> to be sure it is not, sometimes interesting
>> discussions just stop, and I
>> can only guess they have moved off list, hence
>> the request. This is a
>> fascinating discussion.
>

Eric Swartz - WA6HHQ

Re: Data Mode Sideband

Administrator

Guys - Time to end this thread. Please post issues like this to the list owner
(me) rather than taking up ;list b/w for other readers.

73,

Eric
List Moderator
elecraft.com

On 8/25/2014 10:34 AM, Phil Wheeler wrote:
> Nice to have that choice, not available without more effort with some lists.
>
> Can't please everyone, it seems.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Eric Swartz - WA6HHQ

Re: Data Mode Sideband

Administrator

Note that I am referring to the on/off list discussion under this subject, not
the Data Mode Sideband discussion.

Eric
elecraft.com

On 8/25/2014 10:40 AM, Eric Swartz - WA6HHQ, Elecraft wrote:

> Guys - Time to end this thread. Please post issues like this to the list owner
> (me) rather than taking up ;list b/w for other readers.
>
> 73,
>
> Eric
> List Moderator
> elecraft.com
>
> On 8/25/2014 10:34 AM, Phil Wheeler wrote:
>> Nice to have that choice, not available without more effort with some lists.
>>
>> Can't please everyone, it seems.
>

NK7Z

Re: Data Mode Sideband

Thank you for clarifying that Eric... Scared me!
--
Thanks and 73's,
For equipment, and software setups and reviews see:
www.nk7z.net
for MixW support see;
http://groups.yahoo.com/neo/groups/mixw/info
for Dopplergram information see:
http://groups.yahoo.com/neo/groups/dopplergram/info
for MM-SSTV see:
http://groups.yahoo.com/neo/groups/MM-SSTV/info

On Mon, 2014-08-25 at 10:41 -0700, Eric Swartz - WA6HHQ, Elecraft wrote:

> Note that I am referring to the on/off list discussion under this subject, not
> the Data Mode Sideband discussion.
>
> Eric
> elecraft.com
>
> On 8/25/2014 10:40 AM, Eric Swartz - WA6HHQ, Elecraft wrote:
> > Guys - Time to end this thread. Please post issues like this to the list owner
> > (me) rather than taking up ;list b/w for other readers.
> >
> > 73,
> >
> > Eric
> > List Moderator
> > elecraft.com
> >
> > On 8/25/2014 10:34 AM, Phil Wheeler wrote:
> >> Nice to have that choice, not available without more effort with some lists.
> >>
> >> Can't please everyone, it seems.
> >
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]