Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update from UPV #49

Open
wants to merge 14 commits into
base: development
Choose a base branch
from
Open

Update from UPV #49

wants to merge 14 commits into from

Conversation

jsroldan
Copy link

@jsroldan jsroldan commented Oct 1, 2024

Changelog:

  • Fix computation of BLER
  • Added new GPS logs (speed)
  • Added PDSCH EVM.
  • Resynchronization logic to be faster, tries to attach into the same frequency, no search.
  • New CSV structure. Better format for postprocessing in numeric programs like Octave/Matlab
  • Added auxiliar ringbuffer to improve the writing I/Q samples into HDD.
  • Added new backend functions for rt-mbms-wui.

jsroldan added 13 commits March 13, 2023 12:40
The recevier doesn't search every cell ID when loses the synchrononization, tries to connect to the same already known cell.
…peat the reading of a sample file.

The computation of the BLER was erronious, it has been fixed. Also the columns and structure on how the data is saved in the CSV has been change, now every time there's a new measurment a new row is saved in the file indicating the status of the receiver (SYNCING, SEARCHING, o printing the data if it's processing).
…the samples to a disk.

With this secondary buffer, the chunks to be saved are bigger, and this way minimizes the blocking of writting when saving by small chunks.
…ty for the rt-wui

Only pendind things are the displayed of cir and correlation.
@dsilhavy dsilhavy self-requested a review October 8, 2024 06:59
@dsilhavy dsilhavy added this to the 1.3.0 milestone Oct 8, 2024
@dsilhavy
Copy link
Contributor

dsilhavy commented Oct 8, 2024

@alessandro-lucco: Fyi, this PR includes the changes presented by @jsroldan in the last call. If you find the time, it would be nice if you can run some tests on your side as well. We are currently testing against sample recordings: https://5g-mag.github.io/Getting-Started/pages/lte-based-5g-broadcast/additional/sample-files.html

@alessandro-lucco
Copy link

@alessandro-lucco: Fyi, this PR includes the changes presented by @jsroldan in the last call. If you find the time, it would be nice if you can run some tests on your side as well. We are currently testing against sample recordings: https://5g-mag.github.io/Getting-Started/pages/lte-based-5g-broadcast/additional/sample-files.html

Thanks Daniel and Jaime, I did some tests in the last day.
With different sample files it works very well. Using an SDR card with live signal it receives correctly but after a few seconds it returns a segmentation fault. I am in contact with Jaime to try to understand the problem. I do not know if others have had the opportunity to test it.
The setup I used is a PC with Ubuntu 22, 16GB of RAM and an i5 processor, as SDR I tested both with BladeRF and with USRP B210. I tested also on Ubuntu 20 and and I see the same behavior.

@dsilhavy
Copy link
Contributor

@alessandro-lucco: Fyi, this PR includes the changes presented by @jsroldan in the last call. If you find the time, it would be nice if you can run some tests on your side as well. We are currently testing against sample recordings: https://5g-mag.github.io/Getting-Started/pages/lte-based-5g-broadcast/additional/sample-files.html

Thanks Daniel and Jaime, I did some tests in the last day. With different sample files it works very well. Using an SDR card with live signal it receives correctly but after a few seconds it returns a segmentation fault. I am in contact with Jaime to try to understand the problem. I do not know if others have had the opportunity to test it. The setup I used is a PC with Ubuntu 22, 16GB of RAM and an i5 processor, as SDR I tested both with BladeRF and with USRP B210. I tested also on Ubuntu 20 and and I see the same behavior.

Thanks for testing @alessandro-lucco . I only tested a sample file so far and that worked fine. Where does the live signal come from? Is it the 5G-MAG transmitter, or are you using a commercial solution like R&S? Do you see the same problem with the version that does not include the changes by @jsroldan ?

@alessandro-lucco
Copy link

@alessandro-lucco: Fyi, this PR includes the changes presented by @jsroldan in the last call. If you find the time, it would be nice if you can run some tests on your side as well. We are currently testing against sample recordings: https://5g-mag.github.io/Getting-Started/pages/lte-based-5g-broadcast/additional/sample-files.html

Thanks Daniel and Jaime, I did some tests in the last day. With different sample files it works very well. Using an SDR card with live signal it receives correctly but after a few seconds it returns a segmentation fault. I am in contact with Jaime to try to understand the problem. I do not know if others have had the opportunity to test it. The setup I used is a PC with Ubuntu 22, 16GB of RAM and an i5 processor, as SDR I tested both with BladeRF and with USRP B210. I tested also on Ubuntu 20 and and I see the same behavior.

Thanks for testing @alessandro-lucco . I only tested a sample file so far and that worked fine. Where does the live signal come from? Is it the 5G-MAG transmitter, or are you using a commercial solution like R&S? Do you see the same problem with the version that does not include the changes by @jsroldan ?

At the moment i can only test with R&S transmitter. No, with the other versions I have always done the same steps (with same input signal) and I did not encounter segmentation faults, except in very few cases. I think it's a buffer issue related to the SDR management.

@jsroldan
Copy link
Author

The next week I'll debug it to try to figure out what is wrong, I've never tested with a SDR so thanks @alessandro-lucco for the finding!

@dsilhavy
Copy link
Contributor

Comment from the call by @alessandro-lucco : No 5GBC signal needed, but SDR needs to be connected to reproduce the issue that @alessandro-lucco reported above.

@jsroldan
Copy link
Author

Hi all, I finally found the error, the modem stored the samples in the writing buffer although writing the I/Q samples to a file was disable, so basically the buffer was been fulfilled but never emptied (read), no checks if writing is enable to do that.

The samples were saved to the writing buffer even when the writing was disable, causing an overflow.
@jordijoangimenez jordijoangimenez self-assigned this Oct 25, 2024
@jordijoangimenez jordijoangimenez added the enhancement New feature or request label Oct 25, 2024
@jordijoangimenez
Copy link
Contributor

We wait for confirmation for merging this PR after telco between @jsroldan and @alessandro-lucco

@jsroldan
Copy link
Author

jsroldan commented Nov 4, 2024

Last week, Alexandro and I had a meeting to check the issues Alexandro found. We can confirm that are a few things that I need to have a look at. The sample rate is not choose correctly (which happens also in previous versions), and the writing of the samples to a file present some problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging this pull request may close these issues.

4 participants