You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on integrating srsRAN with a LimeXTRX on PCIe. After updating LimeSuite, We are encountering some unexpected signal behavior. Here's what we've found:
Observations
Calibration: Calibration works successfully across all commits.
Issue: After commit 39717c2, there's no visible signal output on a signal analyzer (aside from initial configuration).
Verification: We've run LimeSuite's basicTX example to isolate my implementation as the cause.
Could you help us identify changes in or after commit 39717c2 that might cause this signal behavior change? Any suggestions on troubleshooting or areas to investigate further would be greatly appreciated.
Thank you!
Eduard
The text was updated successfully, but these errors were encountered:
We are running the new 5G Stack, modified from here with commit b5be23f. This constellation is working for us.
Regarding later changes, we were able to port the changes to the latest commit with the changed API of LimeSuite, but we are running in the above mentioned issue, which is the same as for the basicTX example.
Another comment on the previous commit, where basicTX still works:
The output I get is the following:
Devices found :
0: LimeSDR XTRX, media=PCIe, addr=/dev/LimeXTRX0
Configuring device ...
LML TX phase search FAIL
SDR configured in 1648ms
Stream started ...
Stream started ...
TX total samples sent: 11130368
TX total samples sent: 21157376
TX total samples sent: 31169024
Although I can see an output on the signal analyzer, the error message indicates, that the library has some issue configuring the board. For this reason, this commit fails with srsRAN, as it terminates execution on catching the error.
Hello,
We are working on integrating srsRAN with a LimeXTRX on PCIe. After updating LimeSuite, We are encountering some unexpected signal behavior. Here's what we've found:
Observations
Calibration: Calibration works successfully across all commits.
Issue: After commit 39717c2, there's no visible signal output on a signal analyzer (aside from initial configuration).
Verification: We've run LimeSuite's
basicTX
example to isolate my implementation as the cause.Environment
OS: Ubuntu 22.04
LimeSuite Branch: litepcie-update
Request
Could you help us identify changes in or after commit
39717c2
that might cause this signal behavior change? Any suggestions on troubleshooting or areas to investigate further would be greatly appreciated.Thank you!
Eduard
The text was updated successfully, but these errors were encountered: