I’ll stop flying blind for now
But I’m not sure what else can be done ?!
We are using USRP to create a DVB-RCS terminal
We already have a commercial product using another HW platform
We are now moving this product to the USRP N210 platform
UHD programming has been mostly done, especially regarding time settings
(as DVB-RCS is TDMA).
To make it short, we now have a proto-terminal that can transmit data at
required time using timestamp. Next step is to send some hard coded
data, to ensure that the system is fine (especially the time stability,
using DVB-RCS burst receiver as time reference). Following step is to
actually create the burst to send (coding and modulation done in
So we want now to send some hard coded data (a specific burst). In order
to test the system and avoid problem on the burst generation side. The
idea is to capture for a couple of second, a signal that contain wanted
burst. Then use these captured burst to transmit theme at regular
To do that, we are using the example script to capture the data (and the
tx example to test that captured data is correct)
There is no processing of the file, except for what the provided
We tried first to capture a signal from a DVB-RCS commercial terminal
that we own, but this did not work. Then tried the same with a live
signal from the air.
When did it go wrong ?
Why playing out data just captured (using strictly same parameters) is
“flying blind” ?
Do you have any suggestion on how to acquire a burst for later use
(except generating it, as we want to avoid that for now)?
On 08/23/2011 10:36 AM, Bastien Auneau wrote:
tx_samples_from_file.exe --type short --rate 10000000 --freq 1057232000
30MHz bandwidth, why can’t we see the same bandwidth from played out
signal than from original signal ?
Also, we use the rx/tx port of the WBX board to capture then to playout
Here is my take on your method: