usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

X410 not powering on

Z
zhou
Sat, May 27, 2023 10:22 AM

Hi Marcus,
The sampling rate can be 30.72MHz or 184,32MHz. It can vary in different test cases.Below are the final parts of the pass and failed captures (fs=30.72MHz):With eye, we can hardly see difference between these two captures. EVM is not bad in the failed case but CRC failed.I am not too worried about this problem because I have the solution. I reported it as a possible issue in usrp.
Have a nice weekend,

On Friday, 26 May 2023 at 20:05:28 BST, Marcus D. Leech <patchvonbraun@gmail.com> wrote:  

On 26/05/2023 14:11, zhou wrote:

Hi Marcus,
Sorry for the late response. My system setup:  - UHD 4.4 - Ubuntu 22.04 server version - USRP: X310

The capture code:  uhd::usrp::multi_usrp::sptr usrp = uhd::usrp::multi_usrp::make("addr=192.168.12.2, second_addr=192.168.13.2, master_clock_rate=184.32e6"); uhd::stream_args_t stream_args_rx("sc16", "sc16"); stream_args_rx.channels.push_back(0); stream_args_rx.channels.push_back(1); uhd::rx_streamer::sptr rx_stream = usrp->get_rx_stream(stream_args_rx); uhd::stream_cmd_t stream_cmd(uhd::stream_cmd_t::STREAM_MODE_NUM_SAMPS_AND_DONE); stream_cmd.num_samps = num_requested_samples; stream_cmd.stream_now = false; stream_cmd.time_spec = uhd::time_spec_t(ul_time_spec); rx_stream->issue_stream_cmd(stream_cmd); size_t num_rx_samps; unsigned long num_total_samps = 0; while(num_requested_samples != num_total_samps) {    num_rx_samps = rx_stream->recv(buff, num_requested_samples, md, 5.0);    num_total_samps += num_rx_samps; }
If I capture exactly num_requested_samples, then the final part of the capture will not be good. I have to capture 1ms more. In UHD 3.10, I don't see this problem.

Thanks for any feedback.

I don't see where you set the sample rate--what is your sample rate?

Can you perhaps share a time-domain plot of the last samples in the case where it doesn't work right?


USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Hi Marcus, The sampling rate can be 30.72MHz or 184,32MHz. It can vary in different test cases.Below are the final parts of the pass and failed captures (fs=30.72MHz):With eye, we can hardly see difference between these two captures. EVM is not bad in the failed case but CRC failed.I am not too worried about this problem because I have the solution. I reported it as a possible issue in usrp. Have a nice weekend, On Friday, 26 May 2023 at 20:05:28 BST, Marcus D. Leech <patchvonbraun@gmail.com> wrote: On 26/05/2023 14:11, zhou wrote: Hi Marcus, Sorry for the late response. My system setup:  - UHD 4.4 - Ubuntu 22.04 server version - USRP: X310 The capture code: uhd::usrp::multi_usrp::sptr usrp = uhd::usrp::multi_usrp::make("addr=192.168.12.2, second_addr=192.168.13.2, master_clock_rate=184.32e6"); uhd::stream_args_t stream_args_rx("sc16", "sc16"); stream_args_rx.channels.push_back(0); stream_args_rx.channels.push_back(1); uhd::rx_streamer::sptr rx_stream = usrp->get_rx_stream(stream_args_rx); uhd::stream_cmd_t stream_cmd(uhd::stream_cmd_t::STREAM_MODE_NUM_SAMPS_AND_DONE); stream_cmd.num_samps = num_requested_samples; stream_cmd.stream_now = false; stream_cmd.time_spec = uhd::time_spec_t(ul_time_spec); rx_stream->issue_stream_cmd(stream_cmd); size_t num_rx_samps; unsigned long num_total_samps = 0; while(num_requested_samples != num_total_samps) {    num_rx_samps = rx_stream->recv(buff, num_requested_samples, md, 5.0);    num_total_samps += num_rx_samps; } If I capture exactly num_requested_samples, then the final part of the capture will not be good. I have to capture 1ms more. In UHD 3.10, I don't see this problem. Thanks for any feedback. I don't see where you set the sample rate--what is your sample rate? Can you perhaps share a time-domain plot of the last samples in the case where it doesn't work right? _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-leave@lists.ettus.com
MD
Marcus D. Leech
Sat, May 27, 2023 12:41 PM

On 27/05/2023 06:22, zhou wrote:

Hi Marcus,

The sampling rate can be 30.72MHz or 184,32MHz. It can vary in
different test cases.
Below are the final parts of the pass and failed captures (fs=30.72MHz):
Inline imagemichael york
With eye, we can hardly see difference between these two captures. EVM
is not bad in the failed case but CRC failed.
I am not too worried about this problem because I have the solution. I
reported it as a possible issue in usrp.

Have a nice weekend,

On Friday, 26 May 2023 at 20:05:28 BST, Marcus D. Leech
patchvonbraun@gmail.com wrote:

On 26/05/2023 14:11, zhou wrote:
Hi Marcus,

Sorry for the late response.
My system setup:

  • UHD 4.4
  • Ubuntu 22.04 server version
  • USRP: X310

The capture code:
uhd::usrp::multi_usrp::sptr usrp =
uhd::usrp::multi_usrp::make("addr=192.168.12.2,
second_addr=192.168.13.2, master_clock_rate=184.32e6");
uhd::stream_args_t stream_args_rx("sc16", "sc16");
stream_args_rx.channels.push_back(0);
stream_args_rx.channels.push_back(1);
uhd::rx_streamer::sptr rx_stream = usrp->get_rx_stream(stream_args_rx);
uhd::stream_cmd_t
stream_cmd(uhd::stream_cmd_t::STREAM_MODE_NUM_SAMPS_AND_DONE);
stream_cmd.num_samps = num_requested_samples;
stream_cmd.stream_now = false;
stream_cmd.time_spec = uhd::time_spec_t(ul_time_spec);
rx_stream->issue_stream_cmd(stream_cmd);
size_t num_rx_samps;
unsigned long num_total_samps = 0;
while(num_requested_samples != num_total_samps)
{
   num_rx_samps = rx_stream->recv(buff, num_requested_samples, md, 5.0);
   num_total_samps += num_rx_samps;
}

If I capture exactly num_requested_samples, then the final part of the
capture will not be good. I have to capture 1ms more. In UHD 3.10, I
don't see this problem.

Thanks for any feedback.

I don't see where you set the sample rate--what is your sample rate?

Can you perhaps share a time-domain plot of the last samples in the
case where it doesn't work right?

Between UHD 3.10 and UHD 4.4, there have been a considerable number of
changes to the device implementation, including
  restructuring of the DDC and DUC filters -- which will have changed
their group-delay.    This is probably what you're seeing.
  It's likely that simply asking for a few microseconds more data
would work fine.

On 27/05/2023 06:22, zhou wrote: > Hi Marcus, > > The sampling rate can be 30.72MHz or 184,32MHz. It can vary in > different test cases. > Below are the final parts of the pass and failed captures (fs=30.72MHz): > Inline imagemichael york > With eye, we can hardly see difference between these two captures. EVM > is not bad in the failed case but CRC failed. > I am not too worried about this problem because I have the solution. I > reported it as a possible issue in usrp. > > Have a nice weekend, > > > > On Friday, 26 May 2023 at 20:05:28 BST, Marcus D. Leech > <patchvonbraun@gmail.com> wrote: > > > On 26/05/2023 14:11, zhou wrote: > Hi Marcus, > > Sorry for the late response. > My system setup: > - UHD 4.4 > - Ubuntu 22.04 server version > - USRP: X310 > > The capture code: > uhd::usrp::multi_usrp::sptr usrp = > uhd::usrp::multi_usrp::make("addr=192.168.12.2, > second_addr=192.168.13.2, master_clock_rate=184.32e6"); > uhd::stream_args_t stream_args_rx("sc16", "sc16"); > stream_args_rx.channels.push_back(0); > stream_args_rx.channels.push_back(1); > uhd::rx_streamer::sptr rx_stream = usrp->get_rx_stream(stream_args_rx); > uhd::stream_cmd_t > stream_cmd(uhd::stream_cmd_t::STREAM_MODE_NUM_SAMPS_AND_DONE); > stream_cmd.num_samps = num_requested_samples; > stream_cmd.stream_now = false; > stream_cmd.time_spec = uhd::time_spec_t(ul_time_spec); > rx_stream->issue_stream_cmd(stream_cmd); > size_t num_rx_samps; > unsigned long num_total_samps = 0; > while(num_requested_samples != num_total_samps) > { >    num_rx_samps = rx_stream->recv(buff, num_requested_samples, md, 5.0); >    num_total_samps += num_rx_samps; > } > > If I capture exactly num_requested_samples, then the final part of the > capture will not be good. I have to capture 1ms more. In UHD 3.10, I > don't see this problem. > > Thanks for any feedback. > > > I don't see where you set the sample rate--what is your sample rate? > > Can you perhaps share a time-domain plot of the last samples in the > case where it doesn't work right? > Between UHD 3.10 and UHD 4.4, there have been a considerable number of changes to the device implementation, including   restructuring of the DDC and DUC filters -- which will have changed their group-delay.    This is probably what you're seeing.   It's likely that simply asking for a few *microseconds* more data would work fine.
PK
Piotr Krysik
Tue, May 30, 2023 4:03 PM

Hello

I've got a similar issue: completely new USRP X410 that doesn't react to
power button.
More specifically, there is a little sign of life - it constantly prints
something like this on UART that I suppose is a port of STM32
microcontroller:
 --- UART initialized after reboot ---
[Reset cause: reset-pin power-on]
[Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10
@dc6a9f0cf8d7]
[0.00�

--- UART initialized after reboot ---
[Reset cause: reset-pin power-on]
[Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10
@dc6a9f0cf8d7]
[0.00�

...

Do you have any ideas how to solve the issue other than returning the
device?

--
Best Regards,
Piotr Krysik

W dniu 19.05.2023 o 15:41, Arjan Feta via USRP-users pisze:

Hi Wade,

Coincidentally I just measured the output voltage of the power supply
and found that the three of them wobble around 8 to 9 volts. Thew
point is that I have two of them and they do the same thing, which
raises the suspicion it is not a coincidence.

I guess I should check that the AC power source is not playing a bad
joke on me.

Thank you,

Arjan

Arjan FETA
SDR Engineer

http://www.rheagroup.com/

RHEA GROUP

2, Rue d’Arlon, L-8399 Windhof

Office: +32 (0)…| Mobile: +39 3287071042

www.rheagroup.com
http://t.sidekickopen54.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg2BpyRFW8qStpx3My7xPW2BW4zb56dTT6f5_X-rg02?t=http%3A%2F%2Fwww.rheagroup.com%2F&si=6251671876534272&pi=84d8d6f5-3fd1-4962-9bfd-7b2b225b6306

*From:*Wade Fife wade.fife@ettus.com
Sent: 19 May 2023 15:35
To: Arjan Feta a.feta@rheagroup.com
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: X410 not powering on

You don't often get email from wade.fife@ettus.com. Learn why this is
important https://aka.ms/LearnAboutSenderIdentification

*Caution:*This email was sent from an external source, do not click
links or open attachments unless you recognize the sender email
address and know the content is safe.

Hi Arjan,

I have not heard of this before. It should be as simple as connecting
an appropriate AC cable to the X410 power supply brick, plugging the
AC cable into the wall, then plugging the 6-pin power cable into the
X410 and pressing the power button. If you haven't already, try
disconnecting everything from the X410 itself except the power cable
and powering it on. Also try different AC cables (the one that
connects the power supply brick to the wall socket). If you have a
voltage meter you could also measure the voltage on the power supplies
to confirm they're OK. I suggest you contact support@ettus.com if you
can't get it to work.

Wade

On Fri, May 19, 2023 at 2:55 AM Arjan Feta via USRP-users
usrp-users@lists.ettus.com wrote:

 Sorry, no question in the message :).

 Had anyone had this kind of issue before?

 Thanks,

 Arjan

 _______________________________________________
 USRP-users mailing list -- usrp-users@lists.ettus.com
 To unsubscribe send an email to usrp-users-leave@lists.ettus.com

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Hello I've got a similar issue: completely new USRP X410 that doesn't react to power button. More specifically, there is a little sign of life - it constantly prints something like this on UART that I suppose is a port of STM32 microcontroller:  --- UART initialized after reboot --- [Reset cause: reset-pin power-on] [Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10 @dc6a9f0cf8d7] [0.00� --- UART initialized after reboot --- [Reset cause: reset-pin power-on] [Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10 @dc6a9f0cf8d7] [0.00� ... Do you have any ideas how to solve the issue other than returning the device? -- Best Regards, Piotr Krysik W dniu 19.05.2023 o 15:41, Arjan Feta via USRP-users pisze: > > Hi Wade, > > Coincidentally I just measured the output voltage of the power supply > and found that the three of them wobble around 8 to 9 volts. Thew > point is that I have two of them and they do the same thing, which > raises the suspicion it is not a coincidence. > > I guess I should check that the AC power source is not playing a bad > joke on me. > > Thank you, > > Arjan > > *Arjan FETA* > SDR Engineer > > <http://www.rheagroup.com/> > > *RHEA GROUP* > > 2, Rue d’Arlon, L-8399 Windhof > > Office: +32 (0)…| Mobile: +39 3287071042 > > www.rheagroup.com > <http://t.sidekickopen54.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg2BpyRFW8qStpx3My7xPW2BW4zb56dTT6f5_X-rg02?t=http%3A%2F%2Fwww.rheagroup.com%2F&si=6251671876534272&pi=84d8d6f5-3fd1-4962-9bfd-7b2b225b6306> > > *From:*Wade Fife <wade.fife@ettus.com> > *Sent:* 19 May 2023 15:35 > *To:* Arjan Feta <a.feta@rheagroup.com> > *Cc:* usrp-users@lists.ettus.com > *Subject:* Re: [USRP-users] Re: X410 not powering on > > > > > You don't often get email from wade.fife@ettus.com. Learn why this is > important <https://aka.ms/LearnAboutSenderIdentification> > > > > *Caution:*This email was sent from an external source, do not click > links or open attachments unless you recognize the sender email > address and know the content is safe. > > Hi Arjan, > > I have not heard of this before. It should be as simple as connecting > an appropriate AC cable to the X410 power supply brick, plugging the > AC cable into the wall, then plugging the 6-pin power cable into the > X410 and pressing the power button. If you haven't already, try > disconnecting everything from the X410 itself except the power cable > and powering it on. Also try different AC cables (the one that > connects the power supply brick to the wall socket). If you have a > voltage meter you could also measure the voltage on the power supplies > to confirm they're OK. I suggest you contact support@ettus.com if you > can't get it to work. > > Wade > > On Fri, May 19, 2023 at 2:55 AM Arjan Feta via USRP-users > <usrp-users@lists.ettus.com> wrote: > > Sorry, no question in the message :). > > Had anyone had this kind of issue before? > > Thanks, > > Arjan > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com
MD
Marcus D. Leech
Tue, May 30, 2023 4:34 PM

On 30/05/2023 12:03, Piotr Krysik wrote:

Hello

I've got a similar issue: completely new USRP X410 that doesn't react
to power button.
More specifically, there is a little sign of life - it constantly
prints something like this on UART that I suppose is a port of STM32
microcontroller:
 --- UART initialized after reboot ---
[Reset cause: reset-pin power-on]
[Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10
@dc6a9f0cf8d7]
[0.00�

--- UART initialized after reboot ---
[Reset cause: reset-pin power-on]
[Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10
@dc6a9f0cf8d7]
[0.00�

...

Do you have any ideas how to solve the issue other than returning the
device?

--
Best Regards,
Piotr Krysik

Are you able to measure the voltage of the power supply?

W dniu 19.05.2023 o 15:41, Arjan Feta via USRP-users pisze:

Hi Wade,

Coincidentally I just measured the output voltage of the power supply
and found that the three of them wobble around 8 to 9 volts. Thew
point is that I have two of them and they do the same thing, which
raises the suspicion it is not a coincidence.

I guess I should check that the AC power source is not playing a bad
joke on me.

Thank you,

Arjan

Arjan FETA
SDR Engineer

http://www.rheagroup.com/

RHEA GROUP

2, Rue d’Arlon, L-8399 Windhof

Office: +32 (0)…| Mobile: +39 3287071042

www.rheagroup.com
http://t.sidekickopen54.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg2BpyRFW8qStpx3My7xPW2BW4zb56dTT6f5_X-rg02?t=http%3A%2F%2Fwww.rheagroup.com%2F&si=6251671876534272&pi=84d8d6f5-3fd1-4962-9bfd-7b2b225b6306

*From:*Wade Fife wade.fife@ettus.com
Sent: 19 May 2023 15:35
To: Arjan Feta a.feta@rheagroup.com
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: X410 not powering on

You don't often get email from wade.fife@ettus.com. Learn why this is
important https://aka.ms/LearnAboutSenderIdentification

*Caution:*This email was sent from an external source, do not click
links or open attachments unless you recognize the sender email
address and know the content is safe.

Hi Arjan,

I have not heard of this before. It should be as simple as connecting
an appropriate AC cable to the X410 power supply brick, plugging the
AC cable into the wall, then plugging the 6-pin power cable into the
X410 and pressing the power button. If you haven't already, try
disconnecting everything from the X410 itself except the power cable
and powering it on. Also try different AC cables (the one that
connects the power supply brick to the wall socket). If you have a
voltage meter you could also measure the voltage on the power
supplies to confirm they're OK. I suggest you contact
support@ettus.com if you can't get it to work.

Wade

On Fri, May 19, 2023 at 2:55 AM Arjan Feta via USRP-users
usrp-users@lists.ettus.com wrote:

    Sorry, no question in the message :).

    Had anyone had this kind of issue before?

    Thanks,

    Arjan

    _______________________________________________
    USRP-users mailing list -- usrp-users@lists.ettus.com
    To unsubscribe send an email to usrp-users-leave@lists.ettus.com


USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com


USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

On 30/05/2023 12:03, Piotr Krysik wrote: > Hello > > I've got a similar issue: completely new USRP X410 that doesn't react > to power button. > More specifically, there is a little sign of life - it constantly > prints something like this on UART that I suppose is a port of STM32 > microcontroller: >  --- UART initialized after reboot --- > [Reset cause: reset-pin power-on] > [Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10 > @dc6a9f0cf8d7] > [0.00� > > --- UART initialized after reboot --- > [Reset cause: reset-pin power-on] > [Image: RO, titanium_v0.0.13821-2ba974b2d 2021-07-15 11:05:10 > @dc6a9f0cf8d7] > [0.00� > > ... > > Do you have any ideas how to solve the issue other than returning the > device? > > -- > Best Regards, > Piotr Krysik > Are you able to measure the voltage of the power supply? > > W dniu 19.05.2023 o 15:41, Arjan Feta via USRP-users pisze: >> >> Hi Wade, >> >> Coincidentally I just measured the output voltage of the power supply >> and found that the three of them wobble around 8 to 9 volts. Thew >> point is that I have two of them and they do the same thing, which >> raises the suspicion it is not a coincidence. >> >> I guess I should check that the AC power source is not playing a bad >> joke on me. >> >> Thank you, >> >> Arjan >> >> *Arjan FETA* >> SDR Engineer >> >> <http://www.rheagroup.com/> >> >> *RHEA GROUP* >> >> 2, Rue d’Arlon, L-8399 Windhof >> >> Office: +32 (0)…| Mobile: +39 3287071042 >> >> www.rheagroup.com >> <http://t.sidekickopen54.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg2BpyRFW8qStpx3My7xPW2BW4zb56dTT6f5_X-rg02?t=http%3A%2F%2Fwww.rheagroup.com%2F&si=6251671876534272&pi=84d8d6f5-3fd1-4962-9bfd-7b2b225b6306> >> >> *From:*Wade Fife <wade.fife@ettus.com> >> *Sent:* 19 May 2023 15:35 >> *To:* Arjan Feta <a.feta@rheagroup.com> >> *Cc:* usrp-users@lists.ettus.com >> *Subject:* Re: [USRP-users] Re: X410 not powering on >> >> >> >> >> You don't often get email from wade.fife@ettus.com. Learn why this is >> important <https://aka.ms/LearnAboutSenderIdentification> >> >> >> >> *Caution:*This email was sent from an external source, do not click >> links or open attachments unless you recognize the sender email >> address and know the content is safe. >> >> Hi Arjan, >> >> I have not heard of this before. It should be as simple as connecting >> an appropriate AC cable to the X410 power supply brick, plugging the >> AC cable into the wall, then plugging the 6-pin power cable into the >> X410 and pressing the power button. If you haven't already, try >> disconnecting everything from the X410 itself except the power cable >> and powering it on. Also try different AC cables (the one that >> connects the power supply brick to the wall socket). If you have a >> voltage meter you could also measure the voltage on the power >> supplies to confirm they're OK. I suggest you contact >> support@ettus.com if you can't get it to work. >> >> Wade >> >> On Fri, May 19, 2023 at 2:55 AM Arjan Feta via USRP-users >> <usrp-users@lists.ettus.com> wrote: >> >>     Sorry, no question in the message :). >> >>     Had anyone had this kind of issue before? >> >>     Thanks, >> >>     Arjan >> >>     _______________________________________________ >>     USRP-users mailing list -- usrp-users@lists.ettus.com >>     To unsubscribe send an email to usrp-users-leave@lists.ettus.com >> >> >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-leave@lists.ettus.com > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com