Most likely, many transmit bursts are queued up on the device. The
example code that produces timed bursts doesnt wait for particular user
control or feedback from rx packets, its just sending out samples w/
burst tags – which there is some finite amount of buffering upstream to
hold.
Thanks for the reply, problem goes away if I set burst and idle duration
to
1 second.
A question. If I want not to transmit the samples/bursts that are coming
during the idle duration, how can I do that? For example, transmit a
single burst at time t1 for burst duration and then wait for time t2.
The
samples that are coming during wait time should never be transmitted.
After
idle duration a new burst of upcoming samples should be transmitted and
so
on. How should I go about it? Any pointers on this?
-josh
Regards,
Sam
–
Sam