Hello Alberto,

well, thinking further about the situation, it might become more difficulty. I 
think the way it works with the mouse wheel is very nice, but now imagine that 
there is a L.O. that can only handle 5kHz steps. Each time you scroll on the 
1kHz digit, the frequency is sent out to the PLL, and it returns the 
step-rounded value, means that there was no change, because step size was not 
exceeded even half.

So I guess that this must be combined with telling the step size to Winrad.

Any other idea how to handle it? Writing an own GUI is too much effort, you've 
made a nice user interface. Even being a professional SW developer, I never 
made GUI SW for Windows or Linux. Just a lot on the embedded world. And why 
invent the wheel for a 2nd time?

73, Günter

PS: I am somehow still waiting for the feature where to stop winrad during 
transmissions...

 

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Alberto I2PHD
Gesendet: 16 March 2007 22:54
An: winrad discussion list
Betreff: Re: [Winrad] Interface DLL

Hello Guenter,

   you raise a very good point, that of the granularity of the frequency 
generated by the external LO.
Presently, you can change the LO frequency by two means. You can do that from 
inside Winrad, changing the value on the 
screen. Winrad will then send that value to the DLL, and forgets completely the 
matter. It doesn't ask the DLL what the 
actual value of the frequency set is, supposing that the DLL did obey to its 
command...:-)
Or you can change the LO frequency from inside the GUI of the DLL, and in such 
a case the DLL sends an asynchronous 
alert to Winrad, telling it what the new frequency is. In this latter case 
Winrad just takes that value, displays it on 
the screen, and uses it to compute what the actual reception frequency is.

It is apparent from the above that, if the LO is capable only of discrete jumps 
greater than 1 Hz, the first of the two 
methods can lead to errors. So I have decided to modify the SetHWLO call so 
that the return value from the DLL is no 
more an indication of the success of the operation, but it is instead the 
actual value of the frequency that has been 
set on the LO.

Before doing that, I will await for comments and further suggestions. Thanks 
for the raising the issue.

73  Alberto  I2PHD
----------------------------------


Koellner, Guenter wrote:
> Hello Alberto,
> 
> I have two questions about the interface DLL:
> 
> - When you set the frequency of the external L.O., do you immediatly read 
> back the value before it becomes displayed? 
 > I am asking because if the external PLL might not provide the resolution, 
 > there will result an offset.
 > For example, your external L.O. is working in 25kHz steps, but the user 
 > wants to set a frequency not matching this.
> 
> - How often does winrad read this value? Only in case of setting or more 
> frequent. 
 > This question because it might be that the external L.O. becomes changed 
 > with external functions.
> 
> 73, Günter, DL4MEA


_______________________________________________
Winrad mailing list
[email protected]
http://winrad.org/mailman/listinfo/winrad_winrad.org

_______________________________________________
Winrad mailing list
[email protected]
http://winrad.org/mailman/listinfo/winrad_winrad.org

Reply via email to