Jeffrey Pawlan wrote: > > When a hardware DLL is loaded, Winrad should disable the operator control of > the > LO frequency on the Winrad screen. It is thus "read only" and controlled by > the > DLL interface. If the hardware is capable of frequency control, it should be > done from a separate DLL window.
I am not sure I completely agree on this point. Winrad can (and does) communicate the LO changes done on its screen to the DLL, which then uses the information to compute a frequency step (if need be) suitable to the hardware. I don't see why eliminate this functionality, which is already in place. Moreover, as probably the implementer of the DLL will use a different method of specifying the frequency wrt Winrad, the user should continuously mentally switch from one method (when he merely wants to tune inside the segment displayed on the screen) to another (when he wants to change the LO frequency). Additionally, I have implemented a new simple function, which will be present in the next release, such that if you keep the Ctrl key pressed when you change the LO frequency from inside Winrad, the NCO frequency is changed at the same time, so to keep the actual reception frequency fixed at the point where it was initially. A bit like PowerSDR does, when it tries to avoid its DDS spurs. In Winrad that is quite useful when you want to scan a range of frequencies greater than the bandpass. Eliminating the LO control from inside Winrad would kill this new functionality, or at least would require new code to support it. 73 Alberto I2PHD _______________________________________________ Winrad mailing list [email protected] http://winrad.org/mailman/listinfo/winrad_winrad.org
