No change using UHD 3.9.7 :-(
On September 16, 2017 at 07:19:05, Steven Knudsen (ee.k...@gmail.com) wrote:
Steven Knudsen, Ph.D., P.Eng.
www. techconficio.ca
www.linkedin.com/in/knudstevenknudsen
So fest wie die Hand den Stein hält. Sie hält ihn aber fest, nur um ihn desto
weiter zu verwerfen
Hi yet again…I thought to see what would happen if I modified txrx_loopback_to_file.cpp to output scheduled transmit bursts.I modified the transmit worker function to schedule bursts. Up to the settling time (i.e., when the recv starts grabbing samples), the output on the scope looks as expected —
Hi again, Marcus (and all).
I have continued to try and sort out this problem and may be able to provide
some more insight, or at least failed approaches.
Another reader suggested that using STREAM_MODE_NUM_SAMPS_AND_MORE may help if
there is a setup or latency issue. So, I changed the receptio
On 09/09/2017 12:16 AM, Steven Knudsen wrote:
I am not sure that is an option. The TDMA scheme is such that the
TX/RX to inactive time duty cycle is low. During the “inactive” time,
other things are going on.
I suppose maybe I could just turn the RX gain to zero (and will be anyway)
But what
I am not sure that is an option. The TDMA scheme is such that the TX/RX to
inactive time duty cycle is low. During the “inactive” time, other things are
going on.
I suppose maybe I could just turn the RX gain to zero (and will be anyway)
But what you are really suggesting is more polling vs
On 09/08/2017 11:53 PM, Steven Knudsen wrote:
Okay, I can accept that.
What it means is that since my customer has not settled on a USRP
platform, I should put some checks in that enforce timing constraints.
Stuff like looking at the number of samples for the max expected
packet length times
Okay, I can accept that.
What it means is that since my customer has not settled on a USRP platform, I
should put some checks in that enforce timing constraints. Stuff like looking
at the number of samples for the max expected packet length times the sample
rate and comparing to a max allowable
On 09/08/2017 11:38 PM, Steven Knudsen wrote:
Let me see if I understand you correctly. Are you saying that turning
on the first reception takes significant time?
In my case, the receive loop is running before the scheduling starts;
it just times out and spins around again. So I am not sure th
Let me see if I understand you correctly. Are you saying that turning on the
first reception takes significant time?
In my case, the receive loop is running before the scheduling starts; it just
times out and spins around again. So I am not sure that the receive startup is
the problem.
But if
On 09/08/2017 10:54 PM, Steven Knudsen wrote:
Hi Marcus,
I did rebuild LiquidDSP, though it has no dependencies on the UHD. No
change in behaviour.
Rather than speculate further with you (and waste your time), I
pressed ahead with various avenues of investigation and appear to have
had some
Hi Marcus,
I did rebuild LiquidDSP, though it has no dependencies on the UHD. No change in
behaviour.
Rather than speculate further with you (and waste your time), I pressed ahead
with various avenues of investigation and appear to have had some success.
What seems to be the problem is that w
On 09/07/2017 12:37 AM, Steven Knudsen wrote:
Thanks, Marcus.
I was running a slightly older version, so updated
to release_003_010_002_000.
Now it does not get as far at all, but seg faults :-(
Backtrace looks like
Did you rebuild your LiquidDSP libraries after doing the UHD upgrade?
Th
Thanks, Marcus.
I was running a slightly older version, so updated to release_003_010_002_000.
Now it does not get as far at all, but seg faults :-(
Backtrace looks like
Thread 18 "TxRxFlood" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe8ff9700 (LWP 7602)]
0x7ff
On 09/06/2017 08:15 PM, Steven Knudsen via USRP-users wrote:
Hi All,
I am building a TDMA system based on the B200mini. TX is out the TRX
port and RX is on RX2.
I schedule both TX and RX using stream commands. Tested separately,
they work great. However, when I have them running together (se
Hi All,
I am building a TDMA system based on the B200mini. TX is out the TRX port and
RX is on RX2.
I schedule both TX and RX using stream commands. Tested separately, they work
great. However, when I have them running together (separate threads for send
and recv calls), the transmit waveform
15 matches
Mail list logo
