[hpsdr] Alex Control

[Bill Tracey]

I'm sure we can sort this out with Phil when he gets back.  I argued 
for having the firmware do the filter selection directly since it 
knows the frequency in use and the capabilities of the filter 
board.  My thinking was I did not want to have knowledge of the 
filters have to be in the PC side code  -  if the firmware could just 
'do the right thing' then why not do it that way and  save folks from 
having to write PC code to do it.  However 'the right thing' may not 
be easily defined so we probably need to think a bit more on this.

Cheers,

Bill (kd5tfd)

At 04:34 PM 9/1/2011, Gordon & Lois Duff wrote:
>***** High Performance Software Defined Radio Discussion List *****
>
>
>Content-Type: multipart/alternative;
>         boundary="----=_NextPart_000_00B6_01CC68CD.714BF710"
>Content-Language: en-us
>
>Looking at the protocol for communications between the PC and 
>Ozy/Metis, there is no provision for Alex filter selection, hence it 
>would appear to be done downstream from any PC software.
>
>I would prefer to have filter selection under software control (and 
>I would like to be able to bypass all filters, which Alex RX 
>provides for.)  Why software select?  Suppose there are multiple 
>RX's and I want to optimize one, suppose I want the Broad spectrum 
>to not be treated by a high-pass filter.   There may be other 
>reasons, but these come to mind.   I don't have the skill to 
>implement the code in Metis, so I hope someone else will see the 
>need and make it happen.
>
>Gordon, KA2NLM


 1314938997.0