|
From: | Patel, Priyank |
Subject: | Re: [Discuss-gnuradio] Setting up a simple packet radio in 3.7.7.2 |
Date: | Tue, 25 Aug 2015 14:17:06 +0000 |
Hi Julian,
I've verified that it works with the setup you provided (it was very similar to a test I did initially before I switched to TCP sources/sinks). The reason I want to use a TCP source/sink is that I want to be able to send application data through the radio (fairly slow and small data packets, i.e. occasional application commands).
I then switched over the Time sink to a TCP sink: address 127.0.0.1, port 9001, client mode I ran the code again with the sine wave still outputting as the source and opened up a terminal with nc -l 9001 (to connect to the tcp sink client). I was immediately able to see the data was flowing through still (it was garbled, but data regardless in the terminal window).
I then switched the Signal Source to the TCP source: address 127.0.0.1, port 9000, server mode I ran the code again and got nothing as I entered data into the TCP source terminal window (using nc 127.0.0.1 9000). I added a QT GUI Number sink to the output of the encoder and saw that the output as always 0.
I believe I am still getting blocked at the packet encoder whenever I use my TCP source. I've tried changing the data links between the TCP source/sink and Packet Encoder/Decoder to bytes, but still didn't change the output of the encoder at always being 0.
Any other ideas? I feel like there must be some simple setting or method I am using incorrectly at this point.
Thanks for your help!
From: Julian Arnold <address@hidden>
Sent: Tuesday, August 25, 2015 5:04 AM To: Patel, Priyank Cc: address@hidden Subject: Re: [Discuss-gnuradio] Setting up a simple packet radio in 3.7.7.2 Hi Priyank,
I rebuild your setup without the TCP source and it is working for me [1]. Can you run it without using TCP?You have to wait a little for the output to appear on time sink though. Is there something I need to do for the terminal messages I am sending through the tcp-source in order for the encoder block to properly process it? No, generally everything should be handled within the packet encoder.
[1] Cheers,
Julian
On Mon, Aug 24, 2015 at 9:47 PM, Patel, Priyank
<address@hidden> wrote:
-- Julian Arnold
|
[Prev in Thread] | Current Thread | [Next in Thread] |