Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Marcus, Thanks for the suggestion. While still using the Python block, I tried changing the sources to CONST_WAVE and decreasing the sample rate to 500K, and proceeded to do that all the way down to 1, and it still was producing Us on the output. Having said that, I turned to implementing the

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Pavan, 1) if you really just need one tone, try a sampling rate like 500kS/s, and transmit a constant. Use the offset tuning capabilities to put the tone away from the LO leakage, to avoid cancellation. 2) Yes. C++ blocks tend to be much much faster. The fact that you're seeing underruns proves

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Marcus, After doing more analysis, it seems pretty clear that the signal keeps coming down whenever U is printed out, though I'm not sure how to explain the wrong multiplication aspect - perhaps the USRP is doing a multiply on whatever samples it receives, which is fewer than what it needs to

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Pavan, > I am seeing Us on the output basically every time. That means the USRP ran out of samples to transmit when they were due to be transmitted! > So, this means the block isn't fast enough to handle 30.72 million > samples per second? It seems like it, yes. > Should I lower that sampling

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Marcus, Thanks for getting back to me. To address both things you mentioned: (1) Yes, that was a typo. One of them should have said in0; I made a mistake while copying over; the code was correct, however, and that behavior still existed. (2) This is interesting. I am seeing Us on the output

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Sorry - that is a typo. That should be in0, like you said, and the next line should be in1. I made a mistake copying over. Thanks for pointing that out! On Tue, Jun 7, 2016 at 5:05 PM, wrote: > > >>> out0[:] = [x * 1 for x in in1] > ?? IS THIS A TYPO - meaning "in0" >

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Ah yet another thing: make sure you don't see any "U"s on the output; those would be underruns, which might be triggered by your block not being fast enough to keep up with 30.72 million samples per second. Best regards, Marcus On 08.06.2016 01:39, Pavan Yedavalli wrote: > Sorry, and just as an

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

>>> out0[:] = [x * 1 for x in in1] ?? IS THIS A TYPO - meaning "in0" out1[:] = [x * 1 for x in in1] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi Pavan, you put in1 to both outputs: On 08.06.2016 01:39, Pavan Yedavalli wrote: >out0[:] = [x * 1 for x in in1] > out1[:] = [x * 1 for x in in1] Is that intentional? Best regards, Marcus ___ Discuss-gnuradio mailing list

Re: [Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Sorry, and just as an addition, obviously I could use the "Multiply by" blocks in GRC, but I am trying to do a much more complex loop involving this block, so multiplying is only part of the process, and I'm running into issues there already. Thanks. On Tue, Jun 7, 2016 at 4:30 PM, Pavan

[Discuss-gnuradio] Multiplying the inputs with a scalar/vector in my own block

Hi, I created my own block because I wanted to multiply the source sinusoids by weights before transmitting them out, as shown in the attached GRC diagram (my_block.png). However, in my work() function for the block created, I am seeing that simply multiplying the inputs by anything (first test