Michael Thanks for the response. That's exactly what I'm trying to accomplish. You mention the "complex to ||^2 can be vectorized. My question is how exactly do you go about doing that?
Tellrell On Mon, Feb 12, 2018 at 9:42 AM, Michael Dickens <michael.dick...@ettus.com> wrote: > Hi Tellrell - So I'm not sure about the non-sim error / issue, but to me > the larger question is: what are you really trying to do? If you're trying > to detect energy via converting an FFT vector output to dB and > thresholding, on a specific number of items per FFT, then why not just use > vectors throughout to guarantee the # of items is as desired? The FFT block > is, of course, vectorized; so is the "complex to ||^2" block (or, rather it > can be; you're not currently using it in this manner). Then, you set the > energy detector to take in 1 vector of length N (same-same as the FFT and > ||^2) & you're good to go. Maybe I'm missing something? Hope this is > useful. - MLD > > On Sun, Feb 11, 2018, at 9:00 PM, Tellrell White wrote: > > I've created a customized block that takes in a number of input items and > once that number of input items surpasses a certain number, 1024 of the > input items are taken and stored into a list, and then those items are > converted to dB and lastly compared to a threshold value. If any of the > values are greater than the threshold value, a message is printed > indicating a signal is present, and if none of the values are greater than > the threshold, this is indicated with a message stating "No signal is > present". I've tested the block in both simulation and currently, I'm > testing the block over the air using the N210. The block performed > correctly in simulation, however, over the air, the block gives a response > of "no signal present" regardless of the input. The error message " > > python: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 > > also printed during runtime. Any suggestions are welcome. Both the > simulation flow graph and the flow graph used over the air are attached. > > >
_______________________________________________ Discuss-gnuradio mailing list Discussemail@example.com https://lists.gnu.org/mailman/listinfo/discuss-gnuradio