Hi,

we are currently checking out, if we can use RFNoC to develop a simple PHY for 
real-time low-latency signal transmission. We have done this before in LabView, 
but now we need a small device for mobile applications, and our LV only 
supports big USRPs (X310). We are aiming to use the E310 device.

Hence, I was looking into RFNoC documentation to evaluate, if we should give it 
a try to re-develop the PHY layer within RFNoC using Vivado HLS.

One main question that occurs to me immediately was: Can different blocks in 
RFNoC share a common timing? For example, in a TDD frame structure, the TX 
frame shall only be sent, when there is no reception going on. Can different 
blocks synchronize each other? As an example, a synchronization block (which 
knows when a reception is going on) should let the TX radio know, when it is 
allowed to transmit. The same goes for the AGC: The RX gain should only be 
changed, between the reception of two adjacent frames (otherwise one frame 
(which assumes a time-constant channel) would be destroyed). Hence, the 
synchronization should let the RX radio know, when it should change its AGC 
value.

I would be very grateful, if you could point me to some documentation in this 
regard. I searched the internet, but unfortunately, did not find any 
information about this issue.

Thank you very much for your assistance!
Max




Maximilian Matthe

Head of Engineering Lab

maximilian.mat...@barkhauseninstitut.org

Tel.: +49 173 4509667


Barkhausen Institut
www.barkhauseninstitut.org


Barkhausen Institut gGmbH | Sitz: Würzburger Straße 46, 01187 Dresden, Germany 
| Registergericht: Amtsgericht Dresden, HRB 37267 | Geschäftsführer: Prof. Dr. 
Gerhard Fettweis, Dr. Tim Hentschel | Vorsitzender der 
Gesellschafterdelegation: Dr. Andreas Handschuh

Hinweise zum Datenschutz und zur Verarbeitung Ihrer Daten finden Sie unter: 
https://barkhauseninstitut.org/data-privacy

This email and any attachments are intended only for the person to whom this 
email is addressed and may contain confidential and/or privileged information. 
If you received this email in error, please do not disclose the contents to 
anyone, but notify the sender by return email and delete this email (and any 
attachments) from your system. Information on data protection and processing of 
your personal information: https://barkhauseninstitut.org/data-privacy

_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to