Send Elecraft mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.qth.net/mailman/listinfo/elecraft
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Elecraft digest..."
Today's Topics:
1. Re: P3 Beta code 'ghost' issue; Data A revisited
(Joe Subich, W4TV)
2. Re: Is there a reason the receive is so Skinny (Phil Wheeler)
3. Re: Is there a reason the receive is so Skinny (GRANT YOUNGMAN)
4. Re: Is there a reason the receive is so Skinny
(Lynn W. Taylor, WB6UUT)
5. Re: Is there a reason the receive is so Skinny (David Cole)
6. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
7. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
8. Is there a reason the receive is so Skinny (Larry Wassmann)
9. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
10. Re: Is there a reason the receive is so Skinny (Don Wilhelm)
11. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
12. P3 Beta software Bug? Data A REV? (Bob Cunnings)
13. Re: Is there a reason the receive is so Skinny (Jim Brown)
14. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
15. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
16. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
17. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
18. Re: Is there a reason the receive is so Skinny (Bill Turner)
19. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
20. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
21. Power variation (Dr. William J. Schmidt, II)
22. Re: Is there a reason the receive is so Skinny (Fred Jensen)
23. Re: Is there a reason the receive is so Skinny
([email protected])
24. Re: Is there a reason the receive is so Skinny
(Milverton M. Swire via Elecraft)
25. Re: Is there a reason the receive is so Skinny
(Lynn W. Taylor, WB6UUT)
26. Are filters bought from Inrad the same as filters bought from
Elecraft ? (Larry Lopez)
27. Re: Is there a reason the receive is so Skinny
(XE3/K5ENS via Elecraft)
28. Re: Are filters bought from Inrad the same as filters bought
from Elecraft ? (XE3/K5ENS via Elecraft)
29. Re: Is there a reason the receive is so Skinny (David Cole)
30. Re: Is there a reason the receive is so Skinny (Joe Subich, W4TV)
31. Re: Is there a reason the receive is so Skinny (David Cole)
----------------------------------------------------------------------
Message: 1
Date: Sun, 27 Apr 2014 15:22:34 -0400
From: "Joe Subich, W4TV" <[email protected]>
To: "Rick Bates, WA6NHC" <[email protected]>, Elecraft
Reflector <[email protected]>
Subject: Re: [Elecraft] P3 Beta code 'ghost' issue; Data A revisited
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
*YES* with the new beta code - I'm running it and the VFO B/SPLIT
cursor is 400 Hz wide when the data sub-mode is FSK D or AFSK A.
The transmit (red) cursor only goes to 2.8 KHz when DATA A is selected.
Use AFSK A (which you should be doing for the AFSK transmit filter in
any case) if you want the narrow TX cursor.
73,
... Joe, W4TV
On 4/27/2014 3:09 PM, Rick Bates, WA6NHC wrote:
Not with the new beta P3 code...
Rick, WA6NHC
iPad = small keypad = typos = sorry ;-)
On Apr 27, 2014, at 12:07 PM, "Joe Subich, W4TV" <[email protected]> wrote:
In AFSK A/FSK D the transmit/VFO B cursor is 400 Hz.
73,
... Joe, W4TV
On 4/27/2014 12:54 PM, Ken Kontor via Elecraft wrote:
I agree with Rick's comments above. I use N1MM for FSK RTTY. I have an extra RX
window set up to receive signals from VFO B in split mode so I can tell who the
last worked station was while I copy the DX with VFO A. With a narrow 400 hz
bandwidth and 10 khz span on my P3 I can easily tune from station to station
centering his tones in the narrow P3 curser. A 2.7 KHz curser pattern on the P3
would cover up most of what I want to see. I for one would not upgrade my P3
software until this issue is corrected. A narrow 400 Hz curser is necessary for
both VFO A and B in RTTY as far as I am concerned.
73, Ken - W8KEN
On Sunday, April 27, 2014 3:34 AM, "Rick Bates, WA6NHC"
<[email protected]> wrote:
This evening as I was listening to a moderately weak station on 30 meters CW.
I noticed that the P3 display showed a wide (+-.75 KHz from center) pulse
pattern centered on the frequency I was on. I also noted that there was a
strong (XE2, not that it matters) almost 3 KHz down. The P3 pattern matched
the CW pulses of that station down band. I wasn't hearing anything but the
weak station on the K3 (well done Elecraft).
So I wondered, could this anomaly be caused by the new noise blanker algorithm?
Yup. I turned off the P3 NB function (set at 12) and the anomaly went away.
So if you're seeing something on the P3 that isn't there, turn off the NB
function and watch again.
On the subject of the Data A red pattern width change; my normal set up for
working RTTY/PSK (AFSK, Data A mode) split was:
Narrow and recenter the filter to hear only the station I want to work (sound
card doesn't get hosed);
sync the two VFOs (double tap; copy everything over to B);
go split;
move the VFO B (now with the matching pattern of VFO A RX, in red) on top of
the last station worked, fine tune by listening to the sub-RX if desired.
The former (pre-beta) pattern showed the same narrowed width as the main RX
(shows the slot my audio tones would go out), which made it easy to spot the
(TX) VFO B on or near the last station worked, simply line up their trace under
the red swath. This makes for a nice quick attack mode.
Having the wider red pattern (2.7 KHz) makes this much harder now since I can't
'see' where my tones are going to be. If given a vote, I like the old way
better if the P3 can't read the filter width and match the display to the
actual. At least I had a ballpark idea where my tones would go.
73,
Rick, WA6NHC
iPad = small keypad = typos = sorry ;-)
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net/
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
------------------------------
Message: 2
Date: Sun, 27 Apr 2014 12:25:16 -0700
From: Phil Wheeler <[email protected]>
To: [email protected]
Subject: Re: [Elecraft] Is there a reason the receive is so Skinny
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
My take on the original post is that it related to
questioning whether a rig was working as it
should, not a philosophical discussion of whether
ESSB is good or not, though I agree that its use
is pointless and bandwidth-wasting.
Phil w7ox
On 4/27/14, 12:08 PM, [email protected] wrote:
Thanks for saying it
Bob K3DJC
The infantile fascination with SSB flat from 50 Hz to 4000 Hz is
nothing more than another childish, bandwidth wasting, QRM
generating
temper-tantrum from those who don't know better or don't care.
73,
... Joe, W4TV
------------------------------
Message: 3
Date: Sun, 27 Apr 2014 14:30:32 -0500
From: GRANT YOUNGMAN <[email protected]>
To: "<[email protected]> List" <[email protected]>
Subject: Re: [Elecraft] Is there a reason the receive is so Skinny
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
?
The infantile fascination with SSB restricted to 300-3000 (or less) Hz is
nothing more than another childish, restricted bandwidth temper tantrum from
those who don?t know better or don?t care.
This never ending bandwidth argument is pointless. There?s a time and place
for both.
I?d worry more, frankly, about the horrendous, over-driven, over powered, bad
sounding, splatter-laden, rudely behaved signals during a contest than a few
guys who happen to like a bit of bandwidth any other time when the bands tend
to be relatively uncrowded wastelands.
Grant NQ5T
On Apr 27, 2014, at 2:08 PM, <[email protected]> <[email protected]>
wrote:
Thanks for saying it
Bob K3DJC
The infantile fascination with SSB flat from 50 Hz to 4000 Hz is
nothing more than another childish, bandwidth wasting, QRM
generating
temper-tantrum from those who don't know better or don't care.
73,
... Joe, W4TV
------------------------------
Message: 4
Date: Sun, 27 Apr 2014 13:20:39 -0700
From: "Lynn W. Taylor, WB6UUT" <[email protected]>
To: [email protected]
Subject: Re: [Elecraft] Is there a reason the receive is so Skinny
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 4/27/2014 12:30 PM, GRANT YOUNGMAN wrote:
The infantile fascination with SSB restricted to 300-3000 (or less) Hz is
nothing more than another childish, restricted bandwidth temper tantrum from
those who don?t know better or don?t care.
I would also hope there is a time and place for more courtesy.
Can we dial down the rhetoric? Calling something outdated is fine.
Infantile and Childish is a tiny bit much.
73 -- Lynn
------------------------------
Message: 5
Date: Sun, 27 Apr 2014 13:22:13 -0700
From: David Cole <[email protected]>
To: [email protected]
Subject: Re: [Elecraft] Is there a reason the receive is so Skinny
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Phil,
I understand totally, I spent 30 years of my life as a Broadcast
engineer... :)
