All excellent advice. I would also add that the gr-digital blocks already do a lot of this--framing and the like. They're a good place to get some clues even if you want to roll your own.
-- Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org On Dec 9, 2011, at 11:21 AM, John Malsbury <john.malsb...@ettus.com> wrote: > Domenic, > > Whenever you are transferring data from a transmitter to a receiver it is > reasonable to use some sort of framing. If you want a quick test, use a > packet encoder and decoder on your transmitter and receiver, respectively. > This will packetize the data and eliminate the continuous flow of "garbage" > data to your file since the decoder will only output data from valid > packets(w/ header + crc are removed). Bit errors will manifest themselves as > a "short file", since bad packets will be discarded. If you run the > block in verbose mode there may also be reporting for when packets are > discarded. > > Set the payload length number in the encoder so you have a known relationship > between the number of bytes missing from the file and the number of packet > errors. > > There are numerous ways to improve this simple test, but this is a start for > you. Also, you may want to perform a more fundamental bit error test. See > error rate block. > > -J > > > > On 12/09/2011 07:29 AM, Domenic Magazu III wrote: >> >> All, >> I was playing around with the DPSK block provided with GNU Radio. I was >> able to get my two USRPs talking to each other. I placed a file sink on the >> random source generator (set to transmit 10 random binary digits) and I'm >> able to see what was actually sent from that file (command: od -d >> filename.bin). I was curious how I go about verifying that the message in >> my filename.bin is received as transmitted on the other end? >> I tried placing a file sink on the DPSK demod block however because the >> receiver is constantly pulling in information my file becomes extremely >> large and it's difficult to determine where the message would be amongst the >> other 'noise'. Does anyone have any ideas on how to verify my transmitted >> message is making it to my receiver? >> >> Thank you >> Domenic >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
