usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsTimed Commands Not Working
Just to add one more data point, I just ran test_timed_commands on a different computer connected to an X310 -- still UHD 4.1. I have the same problem with that device where it looks like timed commands are not working right.
Thanks,
Jim
From: Jim Palladino jim@gardettoengineering.com
Sent: Wednesday, February 2, 2022 10:44 AM
To: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Wednesday, February 2, 2022 10:39 AM
To: Jim Palladino jim@gardettoengineering.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with anything. I'm at a bit of a loss . . .
Thanks,
Jim
Just to clarify--this is with the stock FPGA image, correct?
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I couldn't
say for sure if timed commands were working for me or not in UHD 4.1. I am
using N321s with shared LO, so the normal commands I use for setting
frequency aren't critical (from a timed command perspective) except for how
the DDC/DUC might be handling them. In any case, once you find out the
issue, could you please share the solution here. If I get a chance, I will
try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino jim@gardettoengineering.com
wrote:
Just to add one more data point, I just ran test_timed_commands on a
different computer connected to an X310 -- still UHD 4.1. I have the same
problem with that device where it looks like timed commands are not working
right.
Thanks,
Jim
From: Jim Palladino jim@gardettoengineering.com
Sent: Wednesday, February 2, 2022 10:44 AM
To: Marcus D. Leech patchvonbraun@gmail.com;
usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Wednesday, February 2, 2022 10:39 AM
To: Jim Palladino jim@gardettoengineering.com;
usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with anything. I'm at
a bit of a loss . . .
Thanks,
Jim
Just to clarify--this is with the stock FPGA image, correct?
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
Thanks, Rob. I always appreciate when you "chime in". Hopefully, someone can try the uhd "test_timed_commands" example in 4.1 to help confirm whether or not it's a problem with something on my end or with UHD. Marcus already confirmed its working for him with an N310 and UHD 3.15.
Thanks,
Jim
From: Rob Kossler rkossler@nd.edu
Sent: Wednesday, February 2, 2022 3:26 PM
To: Jim Palladino jim@gardettoengineering.com
Cc: Marcus D. Leech patchvonbraun@gmail.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I couldn't say for sure if timed commands were working for me or not in UHD 4.1. I am using N321s with shared LO, so the normal commands I use for setting frequency aren't critical (from a timed command perspective) except for how the DDC/DUC might be handling them. In any case, once you find out the issue, could you please share the solution here. If I get a chance, I will try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com> wrote:
Just to add one more data point, I just ran test_timed_commands on a different computer connected to an X310 -- still UHD 4.1. I have the same problem with that device where it looks like timed commands are not working right.
Thanks,
Jim
From: Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com>
Sent: Wednesday, February 2, 2022 10:44 AM
To: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
From: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>
Sent: Wednesday, February 2, 2022 10:39 AM
To: Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com>; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with anything. I'm at a bit of a loss . . .
Thanks,
Jim
Just to clarify--this is with the stock FPGA image, correct?
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
"Hopefully, someone can try the uhd "test_timed_commands" example in 4.1
to..."
Figure I ought to be about as good as the next somebody.
test_timed_commands output with UHD 4.1.0 and an X310
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107800;
UHD_4.1.0.HEAD-0-g6bd0be9c
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1079.015300 us
Testing control timed command:
Span : 100000.000000 us
Now : 253256.340000 us
Response 1: 254437.230000 us
Response 2: 255676.840000 us
Difference of response time 1: -98819.110000 us
Difference of response time 2: -197579.500000 us
Difference between actual and expected time delta: -98760.390000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.365935 frac secs
Stream time was: 0 full secs, 0.365935 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
-Dustin
On 2/3/22 08:02, Jim Palladino wrote:
Thanks, Rob. I always appreciate when you "chime in". Hopefully,
someone can try the uhd "test_timed_commands" example in 4.1 to help
confirm whether or not it's a problem with something on my end or with
UHD. Marcus already confirmed its working for him with an N310 and UHD
3.15.
Thanks,
Jim
From: Rob Kossler rkossler@nd.edu
Sent: Wednesday, February 2, 2022 3:26 PM
To: Jim Palladino jim@gardettoengineering.com
Cc: Marcus D. Leech patchvonbraun@gmail.com;
usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I
couldn't say for sure if timed commands were working for me or not in
UHD 4.1. I am using N321s with shared LO, so the normal commands I use
for setting frequency aren't critical (from a timed command
perspective) except for how the DDC/DUC might be handling them. In any
case, once you find out the issue, could you please share the solution
here. If I get a chance, I will try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino
jim@gardettoengineering.com wrote:
Just to add one more data point, I just ran test_timed_commands on
a different computer connected to an X310 -- still UHD 4.1. I have
the same problem with that device where it looks like timed
commands are not working right.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Jim Palladino <jim@gardettoengineering.com>
*Sent:* Wednesday, February 2, 2022 10:44 AM
*To:* Marcus D. Leech <patchvonbraun@gmail.com>;
usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Marcus D. Leech <patchvonbraun@gmail.com>
*Sent:* Wednesday, February 2, 2022 10:39 AM
*To:* Jim Palladino <jim@gardettoengineering.com>;
usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with
anything. I'm at a bit of a loss . . .
Thanks,
Jim
------------------------------------------------------------------------
Just to clarify--this is with the stock FPGA image, correct?
_______________________________________________
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 tousrp-users-leave@lists.ettus.com
Dustin,
Thank you for running that. So apparently, it isn't just an issue on my end.
Thanks,
Jim
From: Dustin Widmann dw2zq@virginia.edu
Sent: Friday, February 4, 2022 11:16 AM
To: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Timed Commands Not Working
"Hopefully, someone can try the uhd "test_timed_commands" example in 4.1 to..."
Figure I ought to be about as good as the next somebody.
test_timed_commands output with UHD 4.1.0 and an X310
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107800; UHD_4.1.0.HEAD-0-g6bd0be9c
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1079.015300 us
Testing control timed command:
Span : 100000.000000 us
Now : 253256.340000 us
Response 1: 254437.230000 us
Response 2: 255676.840000 us
Difference of response time 1: -98819.110000 us
Difference of response time 2: -197579.500000 us
Difference between actual and expected time delta: -98760.390000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.365935 frac secs
Stream time was: 0 full secs, 0.365935 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
-Dustin
On 2/3/22 08:02, Jim Palladino wrote:
Thanks, Rob. I always appreciate when you "chime in". Hopefully, someone can try the uhd "test_timed_commands" example in 4.1 to help confirm whether or not it's a problem with something on my end or with UHD. Marcus already confirmed its working for him with an N310 and UHD 3.15.
Thanks,
Jim
From: Rob Kossler rkossler@nd.edumailto:rkossler@nd.edu
Sent: Wednesday, February 2, 2022 3:26 PM
To: Jim Palladino jim@gardettoengineering.commailto:jim@gardettoengineering.com
Cc: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I couldn't say for sure if timed commands were working for me or not in UHD 4.1. I am using N321s with shared LO, so the normal commands I use for setting frequency aren't critical (from a timed command perspective) except for how the DDC/DUC might be handling them. In any case, once you find out the issue, could you please share the solution here. If I get a chance, I will try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com> wrote:
Just to add one more data point, I just ran test_timed_commands on a different computer connected to an X310 -- still UHD 4.1. I have the same problem with that device where it looks like timed commands are not working right.
Thanks,
Jim
From: Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com>
Sent: Wednesday, February 2, 2022 10:44 AM
To: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
From: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>
Sent: Wednesday, February 2, 2022 10:39 AM
To: Jim Palladino <jim@gardettoengineering.commailto:jim@gardettoengineering.com>; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com <usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with anything. I'm at a bit of a loss . . .
Thanks,
Jim
Just to clarify--this is with the stock FPGA image, correct?
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
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
Seeing the same behavior using UHD 4.1.0.1 on my N320 and E320, using internal clock and time sources:
$ ./lib/uhd/examples/test_timed_commands --args addr=192.168.10.2
Creating the usrp device with: addr=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.1.0.HEAD-0-gf633b497
...
Using Device: Single USRP:
Device: N300-Series Device
Mboard 0: n320
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: Rhodium
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: Rhodium
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: Rhodium
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: Rhodium
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 2285.387207 us
Testing control timed command:
Span : 100000.000000 us
Now : 467446.240234 us
Response 1: 469725.122070 us
Response 2: 471973.376465 us
Difference of response time 1: -97721.118164 us
Difference of response time 2: -195472.863770 us
Difference between actual and expected time delta: -97751.745605 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.579987 frac secs
Stream time was: 0 full secs, 0.579987 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
---==============
$ ./lib/uhd/examples/test_timed_commands --args addr=192.168.20.2
Creating the usrp device with: addr=192.168.20.2...
[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.1.0.HEAD-0-gf633b497
...
Using Device: Single USRP:
Device: E300-Series Device
Mboard 0: e320
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: E3xx
RX Channel: 1
RX DSP: 1
RX Dboard: A
RX Subdev: E3xx
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: E3xx
TX Channel: 1
TX DSP: 1
TX Dboard: A
TX Subdev: E3xx
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 2122.163125 us
Testing control timed command:
Span : 100000.000000 us
Now : 432457.750000 us
Response 1: 434731.875000 us
Response 2: 436887.437500 us
Difference of response time 1: -97725.875000 us
Difference of response time 2: -195570.312500 us
Difference between actual and expected time delta: -97844.437500 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.550922 frac secs
Stream time was: 0 full secs, 0.550922 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
.. Now that I look closely at test_timed_commands, I'm more confused. My understand of set_command_time is that it sets an FPGA register of the future time at which to process subsequent commands, but none of the calls will block. If the application wants to wait for the timed command to occur, the user code needs to include a manual sleep. So how are timed commands useful with UHD "get" functions, such as get_time_now in this test app?
For reference, I've done it over again with the latest commits from the
UHD-4.0 and UHD-3.15.LTS branches.
Creating the usrp device with: ...
[INFO] [UHD] linux; Clang version 13.0.0 ; Boost_107400;
UHD_4.0.0.0-240-gb38c9d83
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1060.659100 us
Testing control timed command:
Span : 100000.000000 us
Now : 249431.750000 us
Response 1: 250515.950000 us
Response 2: 251521.850000 us
Difference of response time 1: -98915.800000 us
Difference of response time 2: -197909.900000 us
Difference between actual and expected time delta: -98994.100000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.359452 frac secs
Stream time was: 0 full secs, 0.359452 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
Creating the usrp device with: ...
[INFO] [UHD] linux; Clang version 13.0.0 ; Boost_107400;
UHD_3.15.0.0-74-ge35f66e8
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [GPS] No GPSDO found
[INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D00000000000)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1309 MB/s)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1315 MB/s)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 0
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 0
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 60.434350 us
Testing control timed command:
Span : 100000.000000 us
Now : 1848964.600000 us
Response 1: 1948964.655000 us
Response 2: 2048964.655000 us
Difference of response time 1: 0.055000 us
Difference of response time 2: 0.055000 us
Difference between actual and expected time delta: 0.000000 us
About to start streaming using timed command:
Received packet: 100 samples, 2 full secs, 0.155770 frac secs
Stream time was: 2 full secs, 0.155770 frac secs
Difference between stream time and first packet: 0.005000 us
Done!
--
This is pretty concerning, looks like the latest commit of the UHD-4.0
branch has this broken as well? Timed commands at least used to work in
UHD 4.0, but I hadn't tried in a while, and never with this nifty test
program. I'm going to have to see if I can find where the breakage
occurred, so I can roll back for the time being.
-Dustin
On 2/4/22 11:23, Jim Palladino wrote:
Dustin,
Thank you for running that. So apparently, it isn't just an issue on
my end.
Thanks,
Jim
From: Dustin Widmann dw2zq@virginia.edu
Sent: Friday, February 4, 2022 11:16 AM
To: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Timed Commands Not Working
"Hopefully, someone can try the uhd "test_timed_commands" example in
4.1 to..."
Figure I ought to be about as good as the next somebody.
test_timed_commands output with UHD 4.1.0 and an X310
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107800;
UHD_4.1.0.HEAD-0-g6bd0be9c
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1079.015300 us
Testing control timed command:
Span : 100000.000000 us
Now : 253256.340000 us
Response 1: 254437.230000 us
Response 2: 255676.840000 us
Difference of response time 1: -98819.110000 us
Difference of response time 2: -197579.500000 us
Difference between actual and expected time delta: -98760.390000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.365935 frac secs
Stream time was: 0 full secs, 0.365935 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
-Dustin
On 2/3/22 08:02, Jim Palladino wrote:
Thanks, Rob. I always appreciate when you "chime in". Hopefully,
someone can try the uhd "test_timed_commands" example in 4.1 to help
confirm whether or not it's a problem with something on my end or
with UHD. Marcus already confirmed its working for him with an N310
and UHD 3.15.
Thanks,
Jim
From: Rob Kossler rkossler@nd.edu mailto:rkossler@nd.edu
Sent: Wednesday, February 2, 2022 3:26 PM
To: Jim Palladino jim@gardettoengineering.com
mailto:jim@gardettoengineering.com
Cc: Marcus D. Leech patchvonbraun@gmail.com
mailto:patchvonbraun@gmail.com; usrp-users@lists.ettus.com
mailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.com
mailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I
couldn't say for sure if timed commands were working for me or not in
UHD 4.1. I am using N321s with shared LO, so the normal commands I
use for setting frequency aren't critical (from a timed command
perspective) except for how the DDC/DUC might be handling them. In
any case, once you find out the issue, could you please share the
solution here. If I get a chance, I will try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino
<jim@gardettoengineering.com mailto:jim@gardettoengineering.com> wrote:
Just to add one more data point, I just ran test_timed_commands
on a different computer connected to an X310 -- still UHD 4.1. I
have the same problem with that device where it looks like timed
commands are not working right.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Jim Palladino <jim@gardettoengineering.com
<mailto:jim@gardettoengineering.com>>
*Sent:* Wednesday, February 2, 2022 10:44 AM
*To:* Marcus D. Leech <patchvonbraun@gmail.com
<mailto:patchvonbraun@gmail.com>>; usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> <usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the N320.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Marcus D. Leech <patchvonbraun@gmail.com
<mailto:patchvonbraun@gmail.com>>
*Sent:* Wednesday, February 2, 2022 10:39 AM
*To:* Jim Palladino <jim@gardettoengineering.com
<mailto:jim@gardettoengineering.com>>; usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> <usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with
anything. I'm at a bit of a loss . . .
Thanks,
Jim
------------------------------------------------------------------------
Just to clarify--this is with the stock FPGA image, correct?
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
<mailto:usrp-users-leave@lists.ettus.com>
USRP-users mailing list --usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com mailto:usrp-users-leave@lists.ettus.com
Tested with UHD 4.0.0.0 release tag and UHD 4.1.0.0 release tag with the
same results. Hmm.
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400;
UHD_4.1.0.HEAD-0-gd21735d5
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [GPS] No GPSDO found
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1117.661250 us
Testing control timed command:
Span : 100000.000000 us
Now : 283334.600000 us
Response 1: 284555.810000 us
Response 2: 285757.450000 us
Difference of response time 1: -98778.790000 us
Difference of response time 2: -197577.150000 us
Difference between actual and expected time delta: -98798.360000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.394553 frac secs
Stream time was: 0 full secs, 0.394553 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400;
UHD_4.0.0.HEAD-0-g90ce6062
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [GPS] No GPSDO found
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1096.135400 us
Testing control timed command:
Span : 100000.000000 us
Now : 282413.770000 us
Response 1: 283653.385000 us
Response 2: 285225.740000 us
Difference of response time 1: -98760.385000 us
Difference of response time 2: -197188.030000 us
Difference between actual and expected time delta: -98427.645000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.393844 frac secs
Stream time was: 0 full secs, 0.393844 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
-Dustin
On 2/4/22 13:23, Dustin Widmann wrote:
For reference, I've done it over again with the latest commits from
the UHD-4.0 and UHD-3.15.LTS branches.
Creating the usrp device with: ...
[INFO] [UHD] linux; Clang version 13.0.0 ; Boost_107400;
UHD_4.0.0.0-240-gb38c9d83
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1060.659100 us
Testing control timed command:
Span : 100000.000000 us
Now : 249431.750000 us
Response 1: 250515.950000 us
Response 2: 251521.850000 us
Difference of response time 1: -98915.800000 us
Difference of response time 2: -197909.900000 us
Difference between actual and expected time delta: -98994.100000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.359452 frac secs
Stream time was: 0 full secs, 0.359452 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
Creating the usrp device with: ...
[INFO] [UHD] linux; Clang version 13.0.0 ; Boost_107400;
UHD_3.15.0.0-74-ge35f66e8
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [GPS] No GPSDO found
[INFO] [0/DmaFIFO_0] Initializing block control (NOC ID:
0xF1F0D00000000000)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1309 MB/s)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1315 MB/s)
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001)
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001)
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000)
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 0
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 0
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 60.434350 us
Testing control timed command:
Span : 100000.000000 us
Now : 1848964.600000 us
Response 1: 1948964.655000 us
Response 2: 2048964.655000 us
Difference of response time 1: 0.055000 us
Difference of response time 2: 0.055000 us
Difference between actual and expected time delta: 0.000000 us
About to start streaming using timed command:
Received packet: 100 samples, 2 full secs, 0.155770 frac secs
Stream time was: 2 full secs, 0.155770 frac secs
Difference between stream time and first packet: 0.005000 us
Done!
--
This is pretty concerning, looks like the latest commit of the UHD-4.0
branch has this broken as well? Timed commands at least used to work
in UHD 4.0, but I hadn't tried in a while, and never with this nifty
test program. I'm going to have to see if I can find where the
breakage occurred, so I can roll back for the time being.
-Dustin
On 2/4/22 11:23, Jim Palladino wrote:
Dustin,
Thank you for running that. So apparently, it isn't just an issue on
my end.
Thanks,
Jim
From: Dustin Widmann dw2zq@virginia.edu
Sent: Friday, February 4, 2022 11:16 AM
To: usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Timed Commands Not Working
"Hopefully, someone can try the uhd "test_timed_commands" example in
4.1 to..."
Figure I ought to be about as good as the next somebody.
test_timed_commands output with UHD 4.1.0 and an X310
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107800;
UHD_4.1.0.HEAD-0-g6bd0be9c
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: UBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: UBX TX
Testing support for timed commands on this hardware... pass
Perform fast readback of registers:
Difference between paired reads: 1079.015300 us
Testing control timed command:
Span : 100000.000000 us
Now : 253256.340000 us
Response 1: 254437.230000 us
Response 2: 255676.840000 us
Difference of response time 1: -98819.110000 us
Difference of response time 2: -197579.500000 us
Difference between actual and expected time delta: -98760.390000 us
About to start streaming using timed command:
Received packet: 100 samples, 0 full secs, 0.365935 frac secs
Stream time was: 0 full secs, 0.365935 frac secs
Difference between stream time and first packet: 0.000000 us
Done!
-Dustin
On 2/3/22 08:02, Jim Palladino wrote:
Thanks, Rob. I always appreciate when you "chime in". Hopefully,
someone can try the uhd "test_timed_commands" example in 4.1 to help
confirm whether or not it's a problem with something on my end or
with UHD. Marcus already confirmed its working for him with an N310
and UHD 3.15.
Thanks,
Jim
From: Rob Kossler rkossler@nd.edu mailto:rkossler@nd.edu
Sent: Wednesday, February 2, 2022 3:26 PM
To: Jim Palladino jim@gardettoengineering.com
mailto:jim@gardettoengineering.com
Cc: Marcus D. Leech patchvonbraun@gmail.com
mailto:patchvonbraun@gmail.com; usrp-users@lists.ettus.com
mailto:usrp-users@lists.ettus.com usrp-users@lists.ettus.com
mailto:usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: Timed Commands Not Working
Hi Jim,
This sounds like a pretty big issue. I haven't chimed in because I
couldn't say for sure if timed commands were working for me or not
in UHD 4.1. I am using N321s with shared LO, so the normal commands
I use for setting frequency aren't critical (from a timed command
perspective) except for how the DDC/DUC might be handling them. In
any case, once you find out the issue, could you please share the
solution here. If I get a chance, I will try this on some of my devices.
Rob
On Wed, Feb 2, 2022 at 12:22 PM Jim Palladino
<jim@gardettoengineering.com mailto:jim@gardettoengineering.com>
wrote:
Just to add one more data point, I just ran test_timed_commands
on a different computer connected to an X310 -- still UHD 4.1. I
have the same problem with that device where it looks like timed
commands are not working right.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Jim Palladino <jim@gardettoengineering.com
<mailto:jim@gardettoengineering.com>>
*Sent:* Wednesday, February 2, 2022 10:44 AM
*To:* Marcus D. Leech <patchvonbraun@gmail.com
<mailto:patchvonbraun@gmail.com>>; usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> <usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
Correct -- I am using the stock FPGA image for the E320 and the
N320.
Thanks,
Jim
------------------------------------------------------------------------
*From:* Marcus D. Leech <patchvonbraun@gmail.com
<mailto:patchvonbraun@gmail.com>>
*Sent:* Wednesday, February 2, 2022 10:39 AM
*To:* Jim Palladino <jim@gardettoengineering.com
<mailto:jim@gardettoengineering.com>>;
usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>>
*Subject:* Re: [USRP-users] Re: Timed Commands Not Working
On 2022-02-02 10:21, Jim Palladino wrote:
Thanks Marcus. Please let me know if R&D comes back with
anything. I'm at a bit of a loss . . .
Thanks,
Jim
------------------------------------------------------------------------
Just to clarify--this is with the stock FPGA image, correct?
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
<mailto:usrp-users-leave@lists.ettus.com>
USRP-users mailing list --usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com mailto:usrp-users-leave@lists.ettus.com