Re: [linuxham] fldigi, further comments
Yes, a QSY function would help. With my rig, I'd prefer to keep the VFO
at 14.070 or whatever and use DSP for this, but QSY would be better when
you have a fixed set of filters to work with.
I suppose I would want to work like this:
1. View the wide band (100 to 3,000 Hz)
2. Find signal, click to decode it (still wide band)
3. If interesting (or in QSO), click to center it in the narrow passband(s).
4. When done, click to go back to wide band view.
I don't know how folks work when their rig only permits voice-like
bandpasses (>2 kHz) for USB receive. What if you have narrower filters
for CW? (Switch to CW for receive? ;-) I suppose this whole scenario is
for DSP rigs, and maybe not all of *them*...
You might want to place the signal of interest right at the edge of your
passband to help filter out nearby interference on one side of the
signal. What are the semantics for that? ;-) (It's easier if your model
is panning and zooming the DSP bandpass.)
If we're considering things that would be nice -- you could also set the
notch control from the fldigi waterfall... Actually, that is not too
helpful for current Orion users as the notch is applied after the AGC loop.
Hamlib may not be smart enough to do all this transparently -- bandpass
selection is highly rig-dependent. QSY should work, of course.
73, Martin AA6E
Leigh L Klotz, Jr. wrote:
> I took a swing at this in gmfsk a couple of years ago, but the hamlib
> support for the K2 wasn't there for filters. I did manage to add the
> qsy feature, and Dave put that in fldigi as well.
> I think this feature is definitely ripe for inclusion and I see one way
> to do it with these 3 things.
> Please tell me if this is what you mean.
> 1. The waterfall needs to have a mode where click does rig QSY and not
> AF selection. This mode could be global, and/or it could be
> automatically selectrd when you click at the very low <200Hz or very
> high >2200Hz ends (for example).
> 2. There needs to be a mode for narrowing the filter when you click.
> Probably useful only after #1 because most filters are centered on a
> frequency and can't be changed by rig control. So, we can use the sweet
> spot again for this, but may need to have one per filter.
> 3. The click-and-slide support presently in the x2 and x4 modes for
> scrolling the waterfall needs to be extended to work in x1, and in all 3
> zooms, should use rig control to change the vfo once there is no more
> range for scrolling the AF, which is immediately in x1 mode. Probably
> once the cursor scrolls off the screen it should reappear at the sweet
> Martin - AA6E wrote:
>> 3. Passband control. A feature I'd like to have, especially for DSP
>> rigs like the Orion, is the ability to zoom and pan the receiver's
>> passband. That is, you find signals in a 3 kHz "full" band, and then
>> focus the IF in more tightly when you're in QSO with somebody. That
>> really helps control dynamic range / AGC problems when there are strong
>> signals in the 3 kHz band. You would probably want to set the IF
>> passband around the selected tuning spot, with the mouse if possible.
>> Sometimes it is helpful to place the passband asymmetrically around the
>> desired signal, in order to zap a particularly close-in source of QRM.
>> I have a little Python widget that lets me do some of this for the
>> Orion, but it would be better if it were graphically integrated into
>> fldigi's waterfall/tuning panel. Maybe it's an excuse to learn C++ and
>> All for what it's worth!
>> 73 Martin AA6E