Hi Martin, I think you got it right to insert the tag at least if you have a packet_len tag (and maybe MIMO). There might be a performance issue, because we get buffer underruns above 2 MHz sampling frequency, while not getting anyone with continuous streaming.
Otherwise, any solution leading to having the transmitters output a burst at identical sample times would be great. Mit freundlichen Grüßen / Best regards Stephan Ludwig Communication Technology (CR/AEH4) Robert Bosch GmbH | Renningen | 70465 Stuttgart | GERMANY | www.bosch.com Tel. +49(711)811-8809 | Mobile +49(172)5630639 | Fax +49(711)811-5187845 | [email protected] Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000; Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Markus Heyn, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Dr. Werner Struth, Peter Tyroller -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Martin Braun Gesendet: Montag, 23. November 2015 18:57 An: [email protected] Betreff: Re: [Discuss-gnuradio] N210 MIMO packet TX time alignment when using message strobe On 23.11.2015 09:54, Martin Braun wrote: > can you elaborate what exactly your suggestion for the mainline code is? > It seems like your own modifications were causing the bug you saw, but > what's the feature that's missing and you need? Wait, I think I get it: For bursty transmission, you're suggesting forcing a timestamp when none exists, right? Hm, need to think about if that's the right solution... Cheers, Martin _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
