Re: [Discuss-gnuradio] DBS_RX troubles

2005-06-23 Thread Matt Ettus
Lamar Owen wrote:
> On Thursday 23 June 2005 14:13, n4hy wrote:
> 
>>Make sure that you get the "latest and greatest and needed for DBS_RX"
>>usrp_fpga.rbf
>>from Matt if you get the DBS_RX.
> 
> 
> What's different in the new fpga stuff for DBS_RX?  Hmm, I guess I have to 
> recursive diff usrp-0.8 against the CVS, assuming the new stuff is in CVS.


I put the reference clock out on a different pin


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] DBS_RX troubles

2005-06-23 Thread n4hy
It is not.  Matt sent the file to me after he sent the DBS_RX for my GPS 
and AMSAT-NA
prototype transponder plans needed a platform.  He sent the file saying 
"Ooops, you need this".


Anyone who has a DBS_RX and does NOT have

usrp_std_clock_on_0.rbf

send me a note and I will send you a buzz ball while Matt is out of pocket.

Bob


Lamar Owen wrote:


On Thursday 23 June 2005 14:13, n4hy wrote:
 


Make sure that you get the "latest and greatest and needed for DBS_RX"
usrp_fpga.rbf
from Matt if you get the DBS_RX.
   



What's different in the new fpga stuff for DBS_RX?  Hmm, I guess I have to 
recursive diff usrp-0.8 against the CVS, assuming the new stuff is in CVS.
 





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] DBS_RX troubles

2005-06-23 Thread Lamar Owen
On Thursday 23 June 2005 14:13, n4hy wrote:
> Make sure that you get the "latest and greatest and needed for DBS_RX"
> usrp_fpga.rbf
> from Matt if you get the DBS_RX.

What's different in the new fpga stuff for DBS_RX?  Hmm, I guess I have to 
recursive diff usrp-0.8 against the CVS, assuming the new stuff is in CVS.
-- 
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC  28772
(828)862-5554
www.pari.edu


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] DBS_RX troubles

2005-06-23 Thread n4hy
Make sure that you get the "latest and greatest and needed for DBS_RX"   
usrp_fpga.rbf

from Matt if you get the DBS_RX.

Bob



Robert McGwier wrote:


I have not seen this message once on mine.

Bob



Marcus D. Leech wrote:

Matt likely isn't back from his trip to Green Bank yet, but I've 
observed that

with
 the DBS_RX, using dbs_debug, that it complains whenever you go to set a
frequency
 that "VCO failed to lock at  x" appears.

Since that particular operation is the only one that seems to get 
actively

tested for
 a correct result on the MAX2118, I'm wondering if mine is perhaps at 
least

partially
 DOA, or is this "failure to lock" to be expected?


 






___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] DBS_RX troubles

2005-06-22 Thread Robert McGwier

I have not seen this message once on mine.

Bob



Marcus D. Leech wrote:


Matt likely isn't back from his trip to Green Bank yet, but I've observed that
with
 the DBS_RX, using dbs_debug, that it complains whenever you go to set a
frequency
 that "VCO failed to lock at  x" appears.

Since that particular operation is the only one that seems to get actively
tested for
 a correct result on the MAX2118, I'm wondering if mine is perhaps at least
partially
 DOA, or is this "failure to lock" to be expected?


 






___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] DBS_RX troubles

2005-06-22 Thread Marcus D. Leech
Matt likely isn't back from his trip to Green Bank yet, but I've observed that
with
  the DBS_RX, using dbs_debug, that it complains whenever you go to set a
frequency
  that "VCO failed to lock at  x" appears.

Since that particular operation is the only one that seems to get actively
tested for
  a correct result on the MAX2118, I'm wondering if mine is perhaps at least
partially
  DOA, or is this "failure to lock" to be expected?


-- 
Marcus LeechMail:   Dept 1A12, M/S: 04352P16
Security Standards AdvisorPhone: (ESN) 393-9145  +1 613 763 9145
Advanced Technology Research
Nortel Networks  [EMAIL PROTECTED]


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio