P3 Beta code 'ghost' issue; Data A revisited
Locked
P3 Beta code 'ghost' issue; Data A revisited
 
|
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:[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] |
Re: P3 Beta code 'ghost' issue; Data A revisited
|
|
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" <[hidden email]> 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:[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] |
Re: P3 Beta code 'ghost' issue; Data A revisited
|
|
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" <[hidden email]> 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:[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] > 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] |
Re: P3 Beta code 'ghost' issue; Data A revisited
|
|
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" <[hidden email]> 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" <[hidden email]> 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:[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] > ______________________________________________________________ > 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] |
Re: P3 Beta code 'ghost' issue; Data A revisited
|
|
*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" <[hidden email]> 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" <[hidden email]> 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:[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] >> ______________________________________________________________ >> 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] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |