I wish to try making the changes necessary to make this project ready for merge into GNU Radio, but I truthfully do not have any idea whether I have the required skill to do so. Could you send a quick summary of the changes that ought to be made, if you are not too busy?
Sincerely,
Chaz M.
From: discuss-gnuradio-bounces+cmaschman2=huskers.unl.edu@gnu.org <discuss-gnuradio-bounces+cmaschman2=huskers.unl.edu@gnu.org> on behalf of discuss-gnuradio-request@gnu.org <discuss-gnuradio-request@gnu.org>
Sent: Friday, April 12, 2024 11:00 AM
To: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Discuss-gnuradio Digest, Vol 258, Issue 9
Caution: Non-NU Email
Send Discuss-gnuradio mailing list submissions to
discuss-gnuradio@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://urldefense.com/v3/__https://lists.gnu.org/mailman/listinfo/discuss-gnuradio__;!!PvXuogZ4sRB2p-tU!Ayv1UMgj3sHifM4-JHhlX3wnRVnXE7IJrVB5JNYGtDPPNO2r_FwdUKx5wuwG6XEriguwUXNUCWgcK0y_lB8-zzjXMHd1pTNOqQ$
or, via email, send a message with subject or body 'help' to
discuss-gnuradio-request@gnu.org
You can reach the person managing the list at
discuss-gnuradio-owner@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."
Today's Topics:
1. Re: Inquiring about an old GSoC (Marcus Müller)
2. Determining number of dropped samples from USRP Sink in TX
chain (Adrian Winter)
----------------------------------------------------------------------
Message: 1
Date: Thu, 11 Apr 2024 22:13:22 +0200
From: Marcus Müller <mmueller@gnuradio.org>
To: discuss-gnuradio@gnu.org, luca.schmid@kit.edu
Subject: Re: Inquiring about an old GSoC
Message-ID: <649d99d5-155e-4ee0-88b3-05177516cf30@gnuradio.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
I'll brazenly forward that question to Luca here :) The honest answer is
that you should really not blame Luca, time was short (and is always
short), and we (and especially I) never gotten around to bring this to a
state where it can be upstreamed.
Any help achieving that would be greatly appreciated! Regarding
necessary changes: yes, a few things will need to be updated to GNU
Radio 3.10, but that's mostly syntax, not functionality. If you want to
pick up the job of updating things to 3.10, you can be sure I'd support you.
Best regards,
Marcus Müller
On 2024-04-11 03:03, Chaz Maschman wrote:
> Hello GNU Radio folk,
>
>
> I have been attempting to use MIMO technology within GNU Radio and have stumbled upon an old Google Summer of Code project sponsored by GNU Radio that does everything I could have wanted to do but in a more competent manner:
> https://urldefense.com/v3/__https://mimognuradio.wordpress.com/__;!!PvXuogZ4sRB2p-tU!Ayv1UMgj3sHifM4-JHhlX3wnRVnXE7IJrVB5JNYGtDPPNO2r_FwdUKx5wuwG6XEriguwUXNUCWgcK0y_lB8-zzjXMHfgRNuoDQ$
> https://urldefense.com/v3/__https://github.com/kit-cel/gnuradio__;!!PvXuogZ4sRB2p-tU!Ayv1UMgj3sHifM4-JHhlX3wnRVnXE7IJrVB5JNYGtDPPNO2r_FwdUKx5wuwG6XEriguwUXNUCWgcK0y_lB8-zzjXMHe6onpjlQ$
>
> The commentary by the developer surrounding this suggests that he expected or intended for the final code to be merged into GNU Radio, but it seems like it never was. Is there a reason for this? Is there anything that needs to be changed from the code for it to be merged?
>
> Sincerely,
> Chaz M.
>
>
------------------------------
Message: 2
Date: Fri, 12 Apr 2024 10:15:41 +0000
From: Adrian Winter <Adrian.Winter@sintef.no>
To: "discuss-gnuradio@gnu.org" <discuss-gnuradio@gnu.org>
Subject: Determining number of dropped samples from USRP Sink in TX
chain
Message-ID:
<SV0P279MB01866E179F40BAA94107A1C9FA042@SV0P279MB0186.NORP279.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="utf-8"
Hey,
I'm wondering if there is any possibility to programmatically check how long an underrun event in a flowgraph that uses a USRP sink lasted.
I do get messages from the sink when and that an underrun happened, but I can't see if that was for 1 ms or 20 seconds.
> message_debug :warning: Message: (uhd_async_msg (channel . 0) (time_spec 1333 . 0.277859) (event_code underflow))
> Umessage_debug :warning: Message: (uhd_async_msg (channel . 0) (time_spec 1333 . 0.280334) (event_code underflow))
When googling I find a bunch of stuff on _overruns_, but this is in the transmit path.
Background is that a very short underrun we can live with, but a long interruption would be bad. I don't fancy sitting next to the USRP and staring at the LED for days...
Is there any way to query the USRP for further information on the event?
Thanks!
Med vennlig hilsen
Adrian Winter
Forsker
SINTEF Digital
Sustainable Communication Technologies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.com/v3/__https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20240412/a0aec237/attachment.htm__;!!PvXuogZ4sRB2p-tU!Ayv1UMgj3sHifM4-JHhlX3wnRVnXE7IJrVB5JNYGtDPPNO2r_FwdUKx5wuwG6XEriguwUXNUCWgcK0y_lB8-zzjXMHfPIbsCTw$ >
------------------------------
Subject: Digest Footer
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://urldefense.com/v3/__https://lists.gnu.org/mailman/listinfo/discuss-gnuradio__;!!PvXuogZ4sRB2p-tU!Ayv1UMgj3sHifM4-JHhlX3wnRVnXE7IJrVB5JNYGtDPPNO2r_FwdUKx5wuwG6XEriguwUXNUCWgcK0y_lB8-zzjXMHd1pTNOqQ$
------------------------------
End of Discuss-gnuradio Digest, Vol 258, Issue 9
************************************************
No comments:
Post a Comment