Re: [Discuss-gnuradio] Questions about burst communication
My guess is no, the receiver doesn't have its own thread, because I'm not sure how to tell. On Fri, Sep 25, 2015 at 11:21 AM, Martin Braun wrote: > On 24.09.2015 16:31, lwas...@ostatemail.okstate.edu wrote: > > Julian and Martin, > > > > Typically 2 U's appear then a stream of O's. Ya, I don't have any sort > > of correlation block on the receiver side so that is definitely a > > problem. Next week I'll work on implementing a correlation block with a > > barker code preamble. > > > > Do you have any suggestions for quick testing and validation? What I've > > been doing to check the bytes, if my acknowledgment fails, is to save > > the bytes to a file and use MATLAB to inspect them. Is there an easier > > way to quickly look at individual bytes? > > If you have lots of O's, looking at bytes won't help -- the O's are > because your receive part is somehow too slow or stalling. You'll need > to fix that first. > > Does your receiver have it's own dedicated thread? > > M > > > ___ > 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
Re: [Discuss-gnuradio] Questions about burst communication
On 24.09.2015 16:31, lwas...@ostatemail.okstate.edu wrote: > Julian and Martin, > > Typically 2 U's appear then a stream of O's. Ya, I don't have any sort > of correlation block on the receiver side so that is definitely a > problem. Next week I'll work on implementing a correlation block with a > barker code preamble. > > Do you have any suggestions for quick testing and validation? What I've > been doing to check the bytes, if my acknowledgment fails, is to save > the bytes to a file and use MATLAB to inspect them. Is there an easier > way to quickly look at individual bytes? If you have lots of O's, looking at bytes won't help -- the O's are because your receive part is somehow too slow or stalling. You'll need to fix that first. Does your receiver have it's own dedicated thread? M ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Questions about burst communication
Julian and Martin, Typically 2 U's appear then a stream of O's. Ya, I don't have any sort of correlation block on the receiver side so that is definitely a problem. Next week I'll work on implementing a correlation block with a barker code preamble. Do you have any suggestions for quick testing and validation? What I've been doing to check the bytes, if my acknowledgment fails, is to save the bytes to a file and use MATLAB to inspect them. Is there an easier way to quickly look at individual bytes? I appreciate the help, Logan Sent from my Cyanogen phone On Sep 24, 2015 4:12 PM, julian.arn...@ettus.com wrote: Hi Logan, The problem is that the USRP does not know where your burst of data starts and how long it is and therefore it will respond with Us as soon as no new data is coming in. In order to tell the USRP how long a packet of data is the USRP sink in GNURadio offers the 'length tag name' property. If you set this to something not empty the USRP sink will work like a tagged stream block and can therefore handle tagged streams properly. However, you are reporting to see Os and not Us. That is a little strange. Normally it indicates that your PC is not able to keep up with the processing of the incoming data. This should be more or less independent on weather or not you are transmitting bursty data. Are you not seeing any Us and only Os? Cheers, Julian Am 24.09.2015 um 17:20 schrieb Washbourne, Logan : Hello all, I've been trying to modify the chat app tutorial into a system that can utilize USRPs and an acknowledgement system. The acknowledgement system works so far, the RX just sends a pdu back to the TX side saying that it received the message. I am now trying to implement the USRPs to have an over the air system, instead of just using one computer and simulating the channel. My grc files are on github, https://github.com/loganwashbourne/Logan.git. The modified Chat Receiver and Chat Sanitizer blocks are on the github as well. My question is, do I need to treat a burst communication system different than a continuous system? My problem is that on each side I am getting O's whenever I start the program, I have tried increasing and decreasing the sampling rate, and I didn't see any change to the output. I am using the USRP1's, with the RFX2400 daughter boards. If anyone has any ideas or avenues for me to look into it would be much appreciated. Logan Washbourne Electrical Engineering Graduate Student (Electromagnetics) ___ 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
Re: [Discuss-gnuradio] Questions about burst communication
Hi Logan, The problem is that the USRP does not know where your burst of data starts and how long it is and therefore it will respond with Us as soon as no new data is coming in. In order to tell the USRP how long a packet of data is the USRP sink in GNURadio offers the 'length tag name' property. If you set this to something not empty the USRP sink will work like a tagged stream block and can therefore handle tagged streams properly. However, you are reporting to see Os and not Us. That is a little strange. Normally it indicates that your PC is not able to keep up with the processing of the incoming data. This should be more or less independent on weather or not you are transmitting bursty data. Are you not seeing any Us and only Os? Cheers, Julian > Am 24.09.2015 um 17:20 schrieb Washbourne, Logan > : > > Hello all, > > I've been trying to modify the chat app tutorial into a system that can > utilize USRPs and an acknowledgement system. The acknowledgement system works > so far, the RX just sends a pdu back to the TX side saying that it received > the message. I am now trying to implement the USRPs to have an over the air > system, instead of just using one computer and simulating the channel. > > My grc files are on github, https://github.com/loganwashbourne/Logan.git. The > modified Chat Receiver and Chat Sanitizer blocks are on the github as well. > > My question is, do I need to treat a burst communication system different > than a continuous system? My problem is that on each side I am getting O's > whenever I start the program, I have tried increasing and decreasing the > sampling rate, and I didn't see any change to the output. > > I am using the USRP1's, with the RFX2400 daughter boards. > > If anyone has any ideas or avenues for me to look into it would be much > appreciated. > > Logan Washbourne > Electrical Engineering Graduate Student > (Electromagnetics) > > ___ > 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
Re: [Discuss-gnuradio] Questions about burst communication
On 24.09.2015 08:20, Washbourne, Logan wrote: > My question is, do I need to treat a burst communication system > different than a continuous system? My problem is that on each side I am > getting O's whenever I start the program, I have tried increasing and > decreasing the sampling rate, and I didn't see any change to the output. > > I am using the USRP1's, with the RFX2400 daughter boards. Choice of USRP shouldn't matter. I haven't checked out your fg, but here's a couple of facts: O's mean your receiving end isn't picking up stuff fast enough. Also, your receiver needs to run continuously because it doesn't know when packets are coming in. So yes, your bursty receiver is no different from a continuous receiver in this respect. Have you made sure you can sustain the receive rates on your machine? Cheers, Martin ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Questions about burst communication
Hello all, I've been trying to modify the chat app tutorial into a system that can utilize USRPs and an acknowledgement system. The acknowledgement system works so far, the RX just sends a pdu back to the TX side saying that it received the message. I am now trying to implement the USRPs to have an over the air system, instead of just using one computer and simulating the channel. My grc files are on github, https://github.com/loganwashbourne/Logan.git. The modified Chat Receiver and Chat Sanitizer blocks are on the github as well. My question is, do I need to treat a burst communication system different than a continuous system? My problem is that on each side I am getting O's whenever I start the program, I have tried increasing and decreasing the sampling rate, and I didn't see any change to the output. I am using the USRP1's, with the RFX2400 daughter boards. If anyone has any ideas or avenues for me to look into it would be much appreciated. Logan Washbourne Electrical Engineering Graduate Student (Electromagnetics) ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
