Re: [Discuss-gnuradio] File source problem

2016-06-16 Thread mleech
Among SDRs, there is no universal "model" for things like total gain, acceptable baseband magnitudes, etc. Even if there were, expected variations in analog behavior mean that you usually have to tweak things to make it work across multiple hardware. That's just an attribute of the analog world

Re: [Discuss-gnuradio] File source problem

2016-06-16 Thread Olivier Goyette
UPDATE Even without any Costa loop or clock recovery, it works. It seems that the trouble was only the TX amplitude. 2016-06-16 9:36 GMT-04:00 Olivier Goyette : > YEH ! it works now. > > Only 2 major things to do : > > 1st - I multiplied the TX amplitude

Re: [Discuss-gnuradio] File source problem

2016-06-16 Thread Olivier Goyette
YEH ! it works now. Only 2 major things to do : 1st - I multiplied the TX amplitude by 0.5 with a multiply const block 2nd - I used a Costa loop before my demod and it works great. My video got a tiny bit of error but I guess that with a special coding (reed solomon ) I could get it back

Re: [Discuss-gnuradio] File source problem

2016-06-16 Thread Johannes Demel
Hi Olivier, I guess Nick already pointed out the important bits. Also, the warnings GRC prints to the shell should help you. Could you solve your file source issues? Your questions here seem to be related to a different issue. Tx flowgraph: get rid of the throttle block. (also see the

Re: [Discuss-gnuradio] File source problem

2016-06-15 Thread Olivier Goyette
Ok I will try that. Just for your information, throttle or not, it works in both cases on the Nutaq Zepto Le 2016-06-15 17:15, "Nick Foster" a écrit : > One clue for you is already being printed out for you in the TX flowgraph > image. Get rid of the throttle block. > > The

Re: [Discuss-gnuradio] File source problem

2016-06-15 Thread Nick Foster
One clue for you is already being printed out for you in the TX flowgraph image. Get rid of the throttle block. The RX time domain plot looks actually pretty healthy. It's showing a frequency offset, which is normal for unsynchronized devices. The constellation plot needs to happen after timing

Re: [Discuss-gnuradio] File source problem

2016-06-15 Thread Olivier Goyette
I'm giving a copy of the email I just sent to Ettus Research. I think that it's been a hardware problem since the beginning but i'm waiting for their response. Check it out, maybe some of view have already seen this kind of bug

Re: [Discuss-gnuradio] File source problem

2016-06-15 Thread Marcus Müller
Hi Olivier, what does this mean: > The 1st file contains only '1' and the other only '0'. How did you generate these files. Without knowing better, I'd say this is a case for our File Format FAQ:

Re: [Discuss-gnuradio] File source problem

2016-06-14 Thread Olivier Goyette
This is non sense seriously. This is my flowgraph : https://www.dropbox.com/s/4cfptq5419kvyhz/file_source.png?dl=0 When I send only zeros '0', this is what I get : https://www.dropbox.com/s/aipf6wsj5ekwxnb/zeros.png?dl=0 When I send only ones '1' this is what I get :

[Discuss-gnuradio] File source problem

2016-06-14 Thread Olivier Goyette
Hi I have a problem. On my first setup, I use 2 file source. The 1st file contains only '1' and the other only '0'. The 2 file sources go through a selector and end up in a CPFSK mod block. When I run this, switching from '1' to '0' makes the frequency drift from + to - FSK_deviation like it