That makes sense. Thank you so much for all of your help!! It's much
appreciated and has helped me understand what's going on a lot better as
well.
On Sun, Jan 24, 2021 at 4:59 PM Jeff Long wrote:
> You're not seeing anything on the gui sinks because they only show you
> periodic snapshots
You're not seeing anything on the gui sinks because they only show you
periodic snapshots (except for gr-fosphor if you have that installed) and
the bursts fall between the snapshots. Inspectrum lets you see every sample
in a recorded file.
I'm not going to have time to try out the RX part, but
Okay, so do the bursts of digital data mean that the USRP Sink is able to
successfully get the packet as input and transmit it?
If so, when I run the packet_usrp.grc flowgraph, why do I not see the USRP
Source receive anything? For example, the graphs that represent the USRP
Source's output never
Yes, that shows bursts of digital data, which is what your tx produces. Use
a smaller FFT size to see more detail in the time domain.
On Sun, Jan 24, 2021 at 4:44 PM Jada Mariano Berenguer
wrote:
> So, from my understanding you added a File Sink that took in the USRP
> Source's output to the
Best I can tell (recording raw samples from the USRP Source to a File Sink,
then viewing it with inspectrum), it works and the single 'U' per burst is
spurious. The docs would lead you to believe you shouldn't see this.
Nothing stands out as wrong in the GRCs. What happens if you ignore this
and
Recommend you find the simplest flowgraph that demonstrates this problem.
For example, do TX only. Once you find that minimal case, post the actual
GRC file somewhere so someone can try it out. It's really difficult to look
through a bunch of parameters in a screenshot and try to guess what's
