Discussion and technical support related to USRP, UHD, RFNoC
View all threadsHi,
Recently I upgraded UHD driver from 4.7 to 4.8. After the update, I discovered my RFNOC application has a new issue. Method set_tx_bandwidth() and set_rx_bandwidth no longer works properly. A call to get_tx_bandwidth() and get_rx_bandwidth() returned 40MHz regardless of the bandwidth parameter specified in the set function call. I installed UHD 4.8 FPGA image to my X310 properly. I built UHD 4.8 driver source and installed it on my development host without any issue. When running the same app compiled with UHD 4.7, get_tx_bandwidth() and get_rx_bandwidth() returned the same value as the parameter specified in the set method call.
I compiled the UHD RFNOC example application rfnoc_radio_loopback with UHD 4.8 library. It produced a similar issue.
Has anyone experienced the same issue on UHD 4.8?
In some old posts, some people thought set_tx_bandwidth() and set_rx_bandwidth() doesn't do anything if the radio daughter card has a fixed analog bandpass filter. Is it still the case for UHD 4.8?
The radio daughter card WBX-120 has a fixed bandwidth of 40MHz, but I would assume set_tx_bandwidth() and set_rx_bandwidth() adjust the digital filter bandwidth rather than the analog RF bandpass filter.
Hardware & Software driver used:
X310, radio daughter card WBX-120.
UHD 4.8 release installed on the Ubuntu host, UHD 4.8 release FPGA (usrp_x310_Fpga_HG.bit) installed on X310.
Host OS: Ubuntu 24.04 LTS
Tom
The information contained in this e-mail and any attachments from W5 Technologies, Inc. may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
I'm working with NI x310 USRPs for OAI testing and developing purposes and, when using v4.8 of the UHD i have the same issue as well. With the v4.7, the set_tx_bandwidth()/set_rx_bandwidth() do work, getting the values from the get_tx_bandwidth()/get_tx_bandwidth() in accordance. In the case of v4.8, it seems that those "set" functions are not doing anything as you say... Couldn't find any solution or explanation for that yet...
De: Tommy Tsui tommytsui@w5tech.com
Enviado: 31 de maio de 2025 04:14
Para: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Assunto: [USRP-users] UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
You don't often get email from tommytsui@w5tech.com. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
Hi,
Recently I upgraded UHD driver from 4.7 to 4.8. After the update, I discovered my RFNOC application has a new issue. Method set_tx_bandwidth() and set_rx_bandwidth no longer works properly. A call to get_tx_bandwidth() and get_rx_bandwidth() returned 40MHz regardless of the bandwidth parameter specified in the set function call. I installed UHD 4.8 FPGA image to my X310 properly. I built UHD 4.8 driver source and installed it on my development host without any issue. When running the same app compiled with UHD 4.7, get_tx_bandwidth() and get_rx_bandwidth() returned the same value as the parameter specified in the set method call.
I compiled the UHD RFNOC example application rfnoc_radio_loopback with UHD 4.8 library. It produced a similar issue.
Has anyone experienced the same issue on UHD 4.8?
In some old posts, some people thought set_tx_bandwidth() and set_rx_bandwidth() doesn’t do anything if the radio daughter card has a fixed analog bandpass filter. Is it still the case for UHD 4.8?
The radio daughter card WBX-120 has a fixed bandwidth of 40MHz, but I would assume set_tx_bandwidth() and set_rx_bandwidth() adjust the digital filter bandwidth rather than the analog RF bandpass filter.
Hardware & Software driver used:
X310, radio daughter card WBX-120.
UHD 4.8 release installed on the Ubuntu host, UHD 4.8 release FPGA (usrp_x310_Fpga_HG.bit) installed on X310.
Host OS: Ubuntu 24.04 LTS
Tom
The information contained in this e-mail and any attachments from W5 Technologies, Inc. may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
AVISO DE CONFIDENCIALIDADE
Esta mensagem e quaisquer ficheiros anexos a ela contêm informação confidencial, propriedade do grupo MEO e/ou das demais sociedades que com ela se encontrem em relação de domínio, Fundação MEO e MEO ACS, destinando-se ao uso exclusivo do destinatário. Se não for o destinatário pretendido, não deve usar, distribuir, imprimir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado
On 2025-06-04 08:15, Alexandre José Monteiro Sério via USRP-users wrote:
I'm working with NI x310 USRPs for OAI testing and developing purposes
and, when using v4.8 of the UHD i have the same issue as well. With
the v4.7, the set_tx_bandwidth()/set_rx_bandwidth() do work, getting
the values from the get_tx_bandwidth()/get_tx_bandwidth() in
accordance. In the case of v4.8, it seems that those "set" functions
are not doing anything as you say... Couldn't find any solution or
explanation for that yet...
The set_XX_bandwidth calls configure the ANALOG bandwidth of the RF
front-end on the USRP.
In MANY cases, those analog front-ends have no way to set the analog
bandwidth, so those calls do nothing. I can't immediately think of any
X310-compatible
daughtercards that have variable analog bandwidth--which cards do you
have?
De: Tommy Tsui tommytsui@w5tech.com
Enviado: 31 de maio de 2025 04:14
Para: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Assunto: [USRP-users] UHD 4.8 set_tx_bandwidth() and
set_rx_bandwidth() method no longer works
You don't often get email from tommytsui@w5tech.com. Learn why this is
important https://aka.ms/LearnAboutSenderIdentification
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor,
não clique em links nem abra anexos, a não ser que conheça o remetente
e saiba que o seu conteúdo é seguro.
Hi,
Recently I upgraded UHD driver from 4.7 to 4.8. After the update, I
discovered my RFNOC application has a new issue. Method
set_tx_bandwidth() and set_rx_bandwidth no longer works properly. A
call to get_tx_bandwidth() and get_rx_bandwidth() returned 40MHz
regardless of the bandwidth parameter specified in the set function
call. I installed UHD 4.8 FPGA image to my X310 properly. I built UHD
4.8 driver source and installed it on my development host without any
issue. When running the same app compiled with UHD 4.7,
get_tx_bandwidth() and get_rx_bandwidth() returned the same value as
the parameter specified in the set method call.
I compiled the UHD RFNOC example application rfnoc_radio_loopback with
UHD 4.8 library. It produced a similar issue.
Has anyone experienced the same issue on UHD 4.8?
In some old posts, some people thought set_tx_bandwidth() and
set_rx_bandwidth() doesn’t do anything if the radio daughter card has
a fixed analog bandpass filter. Is it still the case for UHD 4.8?
The radio daughter card WBX-120 has a fixed bandwidth of 40MHz, but I
would assume set_tx_bandwidth() and set_rx_bandwidth() adjust the
digital filter bandwidth rather than the analog RF bandpass filter.
Hardware & Software driver used:
X310, radio daughter card WBX-120.
UHD 4.8 release installed on the Ubuntu host, UHD 4.8 release FPGA
(usrp_x310_Fpga_HG.bit) installed on X310.
Host OS: Ubuntu 24.04 LTS
Tom
The information contained in this e-mail and any attachments from W5
Technologies, Inc. may contain confidential and/or proprietary
information, and is intended only for the named recipient to whom it
was originally addressed. If you are not the intended recipient, any
disclosure, distribution, or copying of this e-mail or its attachments
is strictly prohibited. If you have received this e-mail in error,
please notify the sender immediately by return e-mail and permanently
delete the e-mail and any attachments.
AVISO DE CONFIDENCIALIDADE
Esta mensagem e quaisquer ficheiros anexos a ela contêm informação
confidencial, propriedade do grupo MEO e/ou das demais sociedades que
com ela se encontrem em relação de domínio, Fundação MEO e MEO ACS,
destinando-se ao uso exclusivo do destinatário. Se não for o
destinatário pretendido, não deve usar, distribuir, imprimir ou copiar
este e-mail. Se recebeu esta mensagem por engano, por favor informe o
emissor e elimine-a imediatamente. Obrigado
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com
Hi Marcus,
After further investigation, I concur with your comment. My X310 has a WBX-40 installed (not WBX-120 mentioned in the original post). It has a fixed analog bandwidth 40MHz. What I discovered is that the actual digital bandwidth is determined by the sampling rate. The lower the sampling rate, the narrower the bandwidth. My app used 7.68MHz sampling rate, which is closed to the target bandwidth 10MHz it set. From an Agilent signal generator frequency sweep, I can see when the sampling rate is higher, the perceived X310 receive bandwidth is higher until the bandwidth hits the 40MHz limit.
I think UHD 4.8 release fixed the get_rx_bandwidth() and get_tx_bandwidth() API issue. Both return the analog bandwidth limit (40MHz) of the radio daughter card rather than the value set by set_tx_bandwidth() and set_rx_bandwidth() method. I thought the UHD driver API documentation on Ettus Research “USRP Hardware Driver and USRP manual” website could be improved. If it would have a clear description of how the API works and, if any, the limitation(s) of the API. In this case, the set bandwidth method works only when the radio card supports a configurable analog bandpass filter, that would have prevented many users finding an answer to the issue that they encountered.
Tom
Hi Marcus,
My USRPs are the USRP-2944 from NI, and the daughterboards are UBX-160.
Here i find that "set_XX_bandwidth() is used to configure the analog filter channel:
https://files.ettus.com/manual/classuhd_1_1rfnoc_1_1rf__control_1_1core__iface.html#a71f0132ae3c35a62e793e5aab1d8f11b
With your answer, i am now in doubt. In context, at the "usrp_lib.cpp" file of the OpenAirInterface5G software they have the following snippet of code:
if (device->type != USRP_N300_DEV) {
for(int i=0; i<((int) s->usrp->get_tx_num_channels()) && i<openair0_cfg[0].tx_num_channels; i++)
s->usrp->set_tx_bandwidth(openair0_cfg[0].tx_bw,i+choffset);
for(int i=0; i<((int) s->usrp->get_rx_num_channels()) && i<openair0_cfg[0].rx_num_channels; i++)
s->usrp->set_rx_bandwidth(openair0_cfg[0].rx_bw,i+choffset);
}
for (int i=0; i<openair0_cfg[0].rx_num_channels; i++) {
LOG_I(HW,"RX Channel %d\n",i);
LOG_I(HW," Actual RX sample rate: %fMSps...\n",s->usrp->get_rx_rate(i+choffset)/1e6);
LOG_I(HW," Actual RX frequency: %fGHz...\n", s->usrp->get_rx_freq(i+choffset)/1e9);
LOG_I(HW," Actual RX gain: %f...\n", s->usrp->get_rx_gain(i+choffset));
LOG_I(HW," Actual RX bandwidth: %fM...\n", s->usrp->get_rx_bandwidth(i+choffset)/1e6);
LOG_I(HW," Actual RX antenna: %s...\n", s->usrp->get_rx_antenna(i+choffset).c_str());
}
for (int i=0; i<openair0_cfg[0].tx_num_channels; i++) {
LOG_I(HW,"TX Channel %d\n",i);
LOG_I(HW," Actual TX sample rate: %fMSps...\n", s->usrp->get_tx_rate(i+choffset)/1e6);
LOG_I(HW," Actual TX frequency: %fGHz...\n", s->usrp->get_tx_freq(i+choffset)/1e9);
LOG_I(HW," Actual TX gain: %f...\n", s->usrp->get_tx_gain(i+choffset));
LOG_I(HW," Actual TX bandwidth: %fM...\n", s->usrp->get_tx_bandwidth(i+choffset)/1e6);
LOG_I(HW," Actual TX antenna: %s...\n", s->usrp->get_tx_antenna(i+choffset).c_str());
LOG_I(HW," Actual TX packet size: %lu\n",s->tx_stream->get_max_num_samps());
From what i am understanding, this set_XX_bandwidth() functions are not doing anything since UBX-160 daughterboards work at a fixed analog bandwidth of 160 MHz, is that right??? (In my case of these x310, the value that is passed over "openair0_cfg[0].tx_bw" is 5 MHz)
Fact is that, when i was using v4.7.0.0 of the UHD lib, the output values from the "get_XX_bandwidth()" were the same passed by the "set_XX_bandwidth()". That doesn't happen when using v4.8.0.0. Thats why i'm confused by your answer.
I'm a begginer in the USRP usage, so i'm trying to understand and learn so any "docs or references" are mostly welcome too...
Thank you Marcus
De: Marcus D. Leech patchvonbraun@gmail.com
Enviado: 4 de junho de 2025 15:19
Para: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Assunto: [USRP-users] Re: UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
On 2025-06-04 08:15, Alexandre José Monteiro Sério via USRP-users wrote:
I'm working with NI x310 USRPs for OAI testing and developing purposes and, when using v4.8 of the UHD i have the same issue as well. With the v4.7, the set_tx_bandwidth()/set_rx_bandwidth() do work, getting the values from the get_tx_bandwidth()/get_tx_bandwidth() in accordance. In the case of v4.8, it seems that those "set" functions are not doing anything as you say... Couldn't find any solution or explanation for that yet...
The set_XX_bandwidth calls configure the ANALOG bandwidth of the RF front-end on the USRP.
In MANY cases, those analog front-ends have no way to set the analog bandwidth, so those calls do nothing. I can't immediately think of any X310-compatible
daughtercards that have variable analog bandwidth--which cards do you have?
De: Tommy Tsui tommytsui@w5tech.commailto:tommytsui@w5tech.com
Enviado: 31 de maio de 2025 04:14
Para: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Assunto: [USRP-users] UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
You don't often get email from tommytsui@w5tech.commailto:tommytsui@w5tech.com. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
Hi,
Recently I upgraded UHD driver from 4.7 to 4.8. After the update, I discovered my RFNOC application has a new issue. Method set_tx_bandwidth() and set_rx_bandwidth no longer works properly. A call to get_tx_bandwidth() and get_rx_bandwidth() returned 40MHz regardless of the bandwidth parameter specified in the set function call. I installed UHD 4.8 FPGA image to my X310 properly. I built UHD 4.8 driver source and installed it on my development host without any issue. When running the same app compiled with UHD 4.7, get_tx_bandwidth() and get_rx_bandwidth() returned the same value as the parameter specified in the set method call.
I compiled the UHD RFNOC example application rfnoc_radio_loopback with UHD 4.8 library. It produced a similar issue.
Has anyone experienced the same issue on UHD 4.8?
In some old posts, some people thought set_tx_bandwidth() and set_rx_bandwidth() doesn’t do anything if the radio daughter card has a fixed analog bandpass filter. Is it still the case for UHD 4.8?
The radio daughter card WBX-120 has a fixed bandwidth of 40MHz, but I would assume set_tx_bandwidth() and set_rx_bandwidth() adjust the digital filter bandwidth rather than the analog RF bandpass filter.
Hardware & Software driver used:
X310, radio daughter card WBX-120.
UHD 4.8 release installed on the Ubuntu host, UHD 4.8 release FPGA (usrp_x310_Fpga_HG.bit) installed on X310.
Host OS: Ubuntu 24.04 LTS
Tom
The information contained in this e-mail and any attachments from W5 Technologies, Inc. may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
AVISO DE CONFIDENCIALIDADE
Esta mensagem e quaisquer ficheiros anexos a ela contêm informação confidencial, propriedade do grupo MEO e/ou das demais sociedades que com ela se encontrem em relação de domínio, Fundação MEO e MEO ACS, destinando-se ao uso exclusivo do destinatário. Se não for o destinatário pretendido, não deve usar, distribuir, imprimir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado
USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com
Hi Alexandre,
This was confirmed by Tom on his email on 4th June.
Link: https://www.mail-archive.com/usrp-users%40lists.ettus.com/msg18359.html
BR
Sumit Kumar
Research and Technology Scientist
https://www.linkedin.com/in/sumitstop
https://sites.google.com/view/sumit1985
https://scholar.google.com/citations?hl=en&user=-qjjN2sAAAAJ
Luxembourg Institute of Science and Technology (LIST)
5, avenue des Hauts-Fourneaux | L-4362 Esch-sur-Alzette
[cid:ee829769-e2b4-44fd-87a1-4723cf7ecbf5]
From: Alexandre José Monteiro Sério via USRP-users usrp-users@lists.ettus.com
Sent: Thursday, June 12, 2025 7:12 PM
To: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
Hi Marcus,
My USRPs are the USRP-2944 from NI, and the daughterboards are UBX-160.
Here i find that "set_XX_bandwidth() is used to configure the analog filter channel:
https://files.ettus.com/manual/classuhd_1_1rfnoc_1_1rf__control_1_1core__iface.html#a71f0132ae3c35a62e793e5aab1d8f11b
With your answer, i am now in doubt. In context, at the "usrp_lib.cpp" file of the OpenAirInterface5G software they have the following snippet of code:
if (device->type != USRP_N300_DEV) {
for(int i=0; i<((int) s->usrp->get_tx_num_channels()) && i<openair0_cfg[0].tx_num_channels; i++)
s->usrp->set_tx_bandwidth(openair0_cfg[0].tx_bw,i+choffset);
for(int i=0; i<((int) s->usrp->get_rx_num_channels()) && i<openair0_cfg[0].rx_num_channels; i++)
s->usrp->set_rx_bandwidth(openair0_cfg[0].rx_bw,i+choffset);
}
for (int i=0; i<openair0_cfg[0].rx_num_channels; i++) {
LOG_I(HW,"RX Channel %d\n",i);
LOG_I(HW," Actual RX sample rate: %fMSps...\n",s->usrp->get_rx_rate(i+choffset)/1e6);
LOG_I(HW," Actual RX frequency: %fGHz...\n", s->usrp->get_rx_freq(i+choffset)/1e9);
LOG_I(HW," Actual RX gain: %f...\n", s->usrp->get_rx_gain(i+choffset));
LOG_I(HW," Actual RX bandwidth: %fM...\n", s->usrp->get_rx_bandwidth(i+choffset)/1e6);
LOG_I(HW," Actual RX antenna: %s...\n", s->usrp->get_rx_antenna(i+choffset).c_str());
}
for (int i=0; i<openair0_cfg[0].tx_num_channels; i++) {
LOG_I(HW,"TX Channel %d\n",i);
LOG_I(HW," Actual TX sample rate: %fMSps...\n", s->usrp->get_tx_rate(i+choffset)/1e6);
LOG_I(HW," Actual TX frequency: %fGHz...\n", s->usrp->get_tx_freq(i+choffset)/1e9);
LOG_I(HW," Actual TX gain: %f...\n", s->usrp->get_tx_gain(i+choffset));
LOG_I(HW," Actual TX bandwidth: %fM...\n", s->usrp->get_tx_bandwidth(i+choffset)/1e6);
LOG_I(HW," Actual TX antenna: %s...\n", s->usrp->get_tx_antenna(i+choffset).c_str());
LOG_I(HW," Actual TX packet size: %lu\n",s->tx_stream->get_max_num_samps());
From what i am understanding, this set_XX_bandwidth() functions are not doing anything since UBX-160 daughterboards work at a fixed analog bandwidth of 160 MHz, is that right??? (In my case of these x310, the value that is passed over "openair0_cfg[0].tx_bw" is 5 MHz)
Fact is that, when i was using v4.7.0.0 of the UHD lib, the output values from the "get_XX_bandwidth()" were the same passed by the "set_XX_bandwidth()". That doesn't happen when using v4.8.0.0. Thats why i'm confused by your answer.
I'm a begginer in the USRP usage, so i'm trying to understand and learn so any "docs or references" are mostly welcome too...
Thank you Marcus
De: Marcus D. Leech patchvonbraun@gmail.com
Enviado: 4 de junho de 2025 15:19
Para: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Assunto: [USRP-users] Re: UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
On 2025-06-04 08:15, Alexandre José Monteiro Sério via USRP-users wrote:
I'm working with NI x310 USRPs for OAI testing and developing purposes and, when using v4.8 of the UHD i have the same issue as well. With the v4.7, the set_tx_bandwidth()/set_rx_bandwidth() do work, getting the values from the get_tx_bandwidth()/get_tx_bandwidth() in accordance. In the case of v4.8, it seems that those "set" functions are not doing anything as you say... Couldn't find any solution or explanation for that yet...
The set_XX_bandwidth calls configure the ANALOG bandwidth of the RF front-end on the USRP.
In MANY cases, those analog front-ends have no way to set the analog bandwidth, so those calls do nothing. I can't immediately think of any X310-compatible
daughtercards that have variable analog bandwidth--which cards do you have?
De: Tommy Tsui tommytsui@w5tech.commailto:tommytsui@w5tech.com
Enviado: 31 de maio de 2025 04:14
Para: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Assunto: [USRP-users] UHD 4.8 set_tx_bandwidth() and set_rx_bandwidth() method no longer works
You don't often get email from tommytsui@w5tech.commailto:tommytsui@w5tech.com. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
Hi,
Recently I upgraded UHD driver from 4.7 to 4.8. After the update, I discovered my RFNOC application has a new issue. Method set_tx_bandwidth() and set_rx_bandwidth no longer works properly. A call to get_tx_bandwidth() and get_rx_bandwidth() returned 40MHz regardless of the bandwidth parameter specified in the set function call. I installed UHD 4.8 FPGA image to my X310 properly. I built UHD 4.8 driver source and installed it on my development host without any issue. When running the same app compiled with UHD 4.7, get_tx_bandwidth() and get_rx_bandwidth() returned the same value as the parameter specified in the set method call.
I compiled the UHD RFNOC example application rfnoc_radio_loopback with UHD 4.8 library. It produced a similar issue.
Has anyone experienced the same issue on UHD 4.8?
In some old posts, some people thought set_tx_bandwidth() and set_rx_bandwidth() doesn’t do anything if the radio daughter card has a fixed analog bandpass filter. Is it still the case for UHD 4.8?
The radio daughter card WBX-120 has a fixed bandwidth of 40MHz, but I would assume set_tx_bandwidth() and set_rx_bandwidth() adjust the digital filter bandwidth rather than the analog RF bandpass filter.
Hardware & Software driver used:
X310, radio daughter card WBX-120.
UHD 4.8 release installed on the Ubuntu host, UHD 4.8 release FPGA (usrp_x310_Fpga_HG.bit) installed on X310.
Host OS: Ubuntu 24.04 LTS
Tom
The information contained in this e-mail and any attachments from W5 Technologies, Inc. may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments.
AVISO DE CONFIDENCIALIDADE
Esta mensagem e quaisquer ficheiros anexos a ela contêm informação confidencial, propriedade do grupo MEO e/ou das demais sociedades que com ela se encontrem em relação de domínio, Fundação MEO e MEO ACS, destinando-se ao uso exclusivo do destinatário. Se não for o destinatário pretendido, não deve usar, distribuir, imprimir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado
USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com