Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Firdavs Pulat]

The data rate I'm dealing with is ~30 Mbytes/s. Receiver should be able to
keep up with the required data rates (but barely), but it wasn't designed
to work with Ethernet packets, so it's having a hard time due to the bursty
nature of the incoming UDP packets. On top of that, it's got limited rx
buffer.

I was really hoping I could handle this in GnuRadio, but it sounds like I
need to figure out a different way. Thanks for the suggestions!


On Sun, Mar 4, 2018 at 6:50 PM, Michael Piscopo 
wrote:

> I think if you want to smooth it out, you'll need to add the packets to a
> custom queue and use your own transmit thread rather than trying to do it
> all in the work function.  That way you can send consistent-sized packets
> and adjust the per-packet timing if you need to.
>
>
>
> On Sun, Mar 4, 2018 at 7:23 PM, Firdavs Pulat  wrote:
>
>> Setting it on the UDP itself didn't change the behavior either. Do you
>> (or anyone else) have any other ideas?
>>
>> Thank you
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_-8113279904684015709_m_-4079682633075123343_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> On Sun, Mar 4, 2018 at 5:16 PM, Jeff Long  wrote:
>>
>>> I think you'd want to set that on the UDP sink itself.
>>>
>>> On 03/04/2018 01:30 PM, Firdavs Pulat wrote:
>>>
 Thanks for the suggestion, Jeff. Unfortunately, that didn't seem to
 help. I still see bursty packet transmission.

 Btw, currently I have: USRP source --> Low-Pass Filter -->
 ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added the
 set_max_noutput_items line at the output of the Endian Swap block since
 that would be the input to UDP. Is that the only place where I would have
 to make that change, or on all the blocks?

 Thanks!


 
  Virus-free. www.avast.com 

 <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


 On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long >>> willco...@gmail.com>> wrote:

 Try yourblock.set_max_noutput_items(1024/itemsize)


 On 03/03/2018 09:57 PM, Firdavs Pulat wrote:

 Hello everyone,

 I have a B200mini device I'm communicating over USB to a pc
 which is running the gnuradio software. The gnuradio does some
 processing (e.g., low-pass filtering, data type conversion,
 etc), and finally gets to the UDP sink block where packets are
 generated and sent through Ethernet to an external device. The
 issue I'm having is that, in the UDP block,
 noutput_items*d_itemsize size is alot larger than the UDP
 payload size (1024 bytes). So, UDP gets 4-6K worth of bytes and
 bursts it all out really fast (I can see this behavior in
 Wireshark), then waits to buffer up another 4-6K bytes, and
 sends it all out really fast. This process then continues. Is
 there a way to smooth this out so that it's not bursting bunch
 of packets all at once? Otherwise the external device isn't able
 to keep up and it's leading to tons of dropped packets.

 I tried setting the max output buffer in python but I get this
 warning when I run: gr::log :WARN: flat_flowgraph - Block
 (endian_swap_impl0) max output buffer set to 2048 instead of
 requested 512.

 Any ideas on what I can do to change this behaviour?

 Thanks!



 ___
 Discuss-gnuradio mailing list
 Discuss-gnuradio@gnu.org 
 https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 


 ___
 Discuss-gnuradio mailing list
 Discuss-gnuradio@gnu.org 
 https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 



>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Michael Piscopo]

I think if you want to smooth it out, you'll need to add the packets to a
custom queue and use your own transmit thread rather than trying to do it
all in the work function.  That way you can send consistent-sized packets
and adjust the per-packet timing if you need to.



On Sun, Mar 4, 2018 at 7:23 PM, Firdavs Pulat  wrote:

> Setting it on the UDP itself didn't change the behavior either. Do you (or
> anyone else) have any other ideas?
>
> Thank you
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-4079682633075123343_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Sun, Mar 4, 2018 at 5:16 PM, Jeff Long  wrote:
>
>> I think you'd want to set that on the UDP sink itself.
>>
>> On 03/04/2018 01:30 PM, Firdavs Pulat wrote:
>>
>>> Thanks for the suggestion, Jeff. Unfortunately, that didn't seem to
>>> help. I still see bursty packet transmission.
>>>
>>> Btw, currently I have: USRP source --> Low-Pass Filter -->
>>> ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added the
>>> set_max_noutput_items line at the output of the Endian Swap block since
>>> that would be the input to UDP. Is that the only place where I would have
>>> to make that change, or on all the blocks?
>>>
>>> Thanks!
>>>
>>>
>>> >> =link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
>>>  Virus-free. www.avast.com >> il?utm_medium=email&utm_source=link&utm_campaign=sig-email&u
>>> tm_content=webmail&utm_term=link>
>>>
>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>>
>>> On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long >> willco...@gmail.com>> wrote:
>>>
>>> Try yourblock.set_max_noutput_items(1024/itemsize)
>>>
>>>
>>> On 03/03/2018 09:57 PM, Firdavs Pulat wrote:
>>>
>>> Hello everyone,
>>>
>>> I have a B200mini device I'm communicating over USB to a pc
>>> which is running the gnuradio software. The gnuradio does some
>>> processing (e.g., low-pass filtering, data type conversion,
>>> etc), and finally gets to the UDP sink block where packets are
>>> generated and sent through Ethernet to an external device. The
>>> issue I'm having is that, in the UDP block,
>>> noutput_items*d_itemsize size is alot larger than the UDP
>>> payload size (1024 bytes). So, UDP gets 4-6K worth of bytes and
>>> bursts it all out really fast (I can see this behavior in
>>> Wireshark), then waits to buffer up another 4-6K bytes, and
>>> sends it all out really fast. This process then continues. Is
>>> there a way to smooth this out so that it's not bursting bunch
>>> of packets all at once? Otherwise the external device isn't able
>>> to keep up and it's leading to tons of dropped packets.
>>>
>>> I tried setting the max output buffer in python but I get this
>>> warning when I run: gr::log :WARN: flat_flowgraph - Block
>>> (endian_swap_impl0) max output buffer set to 2048 instead of
>>> requested 512.
>>>
>>> Any ideas on what I can do to change this behaviour?
>>>
>>> Thanks!
>>>
>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org 
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>> 
>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org 
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>> 
>>>
>>>
>>>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Jeff Long]

I can't think of anything else within the GR core. The scheduler tries 
to maximize sample throughput, but doesn't try to do any kind of pacing.


It sounds like whatever is receiving the UDP packets is operating at its 
limits, assuming it would work if the packets were evenly paced. Do you 
know whether the receiver can handle this data rate at all? Or does it 
just have a very small RX buffer?


You might be able to get the Linux stack to help using tc (traffic 
control), depending on the rates you're dealing with.


On 03/04/2018 07:23 PM, Firdavs Pulat wrote:
Setting it on the UDP itself didn't change the behavior either. Do you 
(or anyone else) have any other ideas?


Thank you

 
	Virus-free. www.avast.com 
 



<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 4, 2018 at 5:16 PM, Jeff Long > wrote:


I think you'd want to set that on the UDP sink itself.

On 03/04/2018 01:30 PM, Firdavs Pulat wrote:

Thanks for the suggestion, Jeff. Unfortunately, that didn't seem
to help. I still see bursty packet transmission.

Btw, currently I have: USRP source --> Low-Pass Filter -->
ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added
the set_max_noutput_items line at the output of the Endian Swap
block since that would be the input to UDP. Is that the only
place where I would have to make that change, or on all the blocks?

Thanks!



> 
    Virus-free. www.avast.com 


>


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long mailto:willco...@gmail.com> >> wrote:

     Try yourblock.set_max_noutput_items(1024/itemsize)


     On 03/03/2018 09:57 PM, Firdavs Pulat wrote:

         Hello everyone,

         I have a B200mini device I'm communicating over USB to a pc
         which is running the gnuradio software. The gnuradio
does some
         processing (e.g., low-pass filtering, data type conversion,
         etc), and finally gets to the UDP sink block where
packets are
         generated and sent through Ethernet to an external
device. The
         issue I'm having is that, in the UDP block,
         noutput_items*d_itemsize size is alot larger than the UDP
         payload size (1024 bytes). So, UDP gets 4-6K worth of
bytes and
         bursts it all out really fast (I can see this behavior in
         Wireshark), then waits to buffer up another 4-6K bytes, and
         sends it all out really fast. This process then
continues. Is
         there a way to smooth this out so that it's not
bursting bunch
         of packets all at once? Otherwise the external device
isn't able
         to keep up and it's leading to tons of dropped packets.

         I tried setting the max output buffer in python but I
get this
         warning when I run: gr::log :WARN: flat_flowgraph - Block
         (endian_swap_impl0) max output buffer set to 2048
instead of
         requested 512.

         Any ideas on what I can do to change this behaviour?

         Thanks!



         ___
         Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org 
>
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


>


     ___
     Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org 
>
https://lists.gnu.or

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Firdavs Pulat]

Setting it on the UDP itself didn't change the behavior either. Do you (or
anyone else) have any other ideas?

Thank you


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 4, 2018 at 5:16 PM, Jeff Long  wrote:

> I think you'd want to set that on the UDP sink itself.
>
> On 03/04/2018 01:30 PM, Firdavs Pulat wrote:
>
>> Thanks for the suggestion, Jeff. Unfortunately, that didn't seem to help.
>> I still see bursty packet transmission.
>>
>> Btw, currently I have: USRP source --> Low-Pass Filter -->
>> ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added the
>> set_max_noutput_items line at the output of the Endian Swap block since
>> that would be the input to UDP. Is that the only place where I would have
>> to make that change, or on all the blocks?
>>
>> Thanks!
>>
>>
>> > =link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
>>  Virus-free. www.avast.com > il?utm_medium=email&utm_source=link&utm_campaign=sig-email&
>> utm_content=webmail&utm_term=link>
>>
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>> On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long > willco...@gmail.com>> wrote:
>>
>> Try yourblock.set_max_noutput_items(1024/itemsize)
>>
>>
>> On 03/03/2018 09:57 PM, Firdavs Pulat wrote:
>>
>> Hello everyone,
>>
>> I have a B200mini device I'm communicating over USB to a pc
>> which is running the gnuradio software. The gnuradio does some
>> processing (e.g., low-pass filtering, data type conversion,
>> etc), and finally gets to the UDP sink block where packets are
>> generated and sent through Ethernet to an external device. The
>> issue I'm having is that, in the UDP block,
>> noutput_items*d_itemsize size is alot larger than the UDP
>> payload size (1024 bytes). So, UDP gets 4-6K worth of bytes and
>> bursts it all out really fast (I can see this behavior in
>> Wireshark), then waits to buffer up another 4-6K bytes, and
>> sends it all out really fast. This process then continues. Is
>> there a way to smooth this out so that it's not bursting bunch
>> of packets all at once? Otherwise the external device isn't able
>> to keep up and it's leading to tons of dropped packets.
>>
>> I tried setting the max output buffer in python but I get this
>> warning when I run: gr::log :WARN: flat_flowgraph - Block
>> (endian_swap_impl0) max output buffer set to 2048 instead of
>> requested 512.
>>
>> Any ideas on what I can do to change this behaviour?
>>
>> Thanks!
>>
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>> 
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>> 
>>
>>
>>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Jeff Long]

I think you'd want to set that on the UDP sink itself.

On 03/04/2018 01:30 PM, Firdavs Pulat wrote:
Thanks for the suggestion, Jeff. Unfortunately, that didn't seem to 
help. I still see bursty packet transmission.


Btw, currently I have: USRP source --> Low-Pass Filter --> 
ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added the 
set_max_noutput_items line at the output of the Endian Swap block since 
that would be the input to UDP. Is that the only place where I would 
have to make that change, or on all the blocks?


Thanks!


 
	Virus-free. www.avast.com 
 



<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long > wrote:


Try yourblock.set_max_noutput_items(1024/itemsize)


On 03/03/2018 09:57 PM, Firdavs Pulat wrote:

Hello everyone,

I have a B200mini device I'm communicating over USB to a pc
which is running the gnuradio software. The gnuradio does some
processing (e.g., low-pass filtering, data type conversion,
etc), and finally gets to the UDP sink block where packets are
generated and sent through Ethernet to an external device. The
issue I'm having is that, in the UDP block,
noutput_items*d_itemsize size is alot larger than the UDP
payload size (1024 bytes). So, UDP gets 4-6K worth of bytes and
bursts it all out really fast (I can see this behavior in
Wireshark), then waits to buffer up another 4-6K bytes, and
sends it all out really fast. This process then continues. Is
there a way to smooth this out so that it's not bursting bunch
of packets all at once? Otherwise the external device isn't able
to keep up and it's leading to tons of dropped packets.

I tried setting the max output buffer in python but I get this
warning when I run: gr::log :WARN: flat_flowgraph - Block
(endian_swap_impl0) max output buffer set to 2048 instead of
requested 512.

Any ideas on what I can do to change this behaviour?

Thanks!



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org 
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org 
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Firdavs Pulat]

Thanks for the suggestion, Jeff. Unfortunately, that didn't seem to help. I
still see bursty packet transmission.

Btw, currently I have: USRP source --> Low-Pass Filter -->
ComplexToInterleavedShort --> Endian Swap --> UDP Sink. I added the
set_max_noutput_items line at the output of the Endian Swap block since
that would be the input to UDP. Is that the only place where I would have
to make that change, or on all the blocks?

Thanks!



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 4, 2018 at 6:44 AM, Jeff Long  wrote:

> Try yourblock.set_max_noutput_items(1024/itemsize)
>
>
> On 03/03/2018 09:57 PM, Firdavs Pulat wrote:
>
>> Hello everyone,
>>
>> I have a B200mini device I'm communicating over USB to a pc which is
>> running the gnuradio software. The gnuradio does some processing (e.g.,
>> low-pass filtering, data type conversion, etc), and finally gets to the UDP
>> sink block where packets are generated and sent through Ethernet to an
>> external device. The issue I'm having is that, in the UDP block,
>> noutput_items*d_itemsize size is alot larger than the UDP payload size
>> (1024 bytes). So, UDP gets 4-6K worth of bytes and bursts it all out really
>> fast (I can see this behavior in Wireshark), then waits to buffer up
>> another 4-6K bytes, and sends it all out really fast. This process then
>> continues. Is there a way to smooth this out so that it's not bursting
>> bunch of packets all at once? Otherwise the external device isn't able to
>> keep up and it's leading to tons of dropped packets.
>>
>> I tried setting the max output buffer in python but I get this warning
>> when I run: gr::log :WARN: flat_flowgraph - Block (endian_swap_impl0) max
>> output buffer set to 2048 instead of requested 512.
>>
>> Any ideas on what I can do to change this behaviour?
>>
>> Thanks!
>>
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Just posted 2 job offerings

[mehtap özkan]

You are right if it were an implementation from scratch. In reality, it is
just a re-implementation of your gr-ccsds fork.
The real reason is that we tested your code with an USRP N310. It worked
fine except some frame drops.
Then we tried it with LIMESDR. The result was terrible with lots of frame
drops (and the constellation looks funny ).
We blamed ourselves and decided that someone else should take a look. (Its
either us or some settings in Osmocom-source/sink blocks)
Do you understand our situation now?




2018-03-04 18:03 GMT+03:00 Dan CaJacob :

> LOL, $30 - $250 budget for a CCSDS modem.
>
> On Sun, Mar 4, 2018 at 5:39 AM mehtap özkan 
> wrote:
>
>> https://discourse.myriadrf.org/t/just-posted-two-
>> freelance-jobs/2421?u=booth
>>
>> If you are interested send me a message.
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> --
> Very Respectfully,
>
> Dan CaJacob
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Just posted 2 job offerings

[Marcus D. Leech]

On 03/04/2018 10:03 AM, Dan CaJacob wrote:

LOL, $30 - $250 budget for a CCSDS modem.

Hey, in hacker movies, exotic new attacks on complex systems can 
generally be consed up in mere minutes of furious monkey-like typing.


The real world is the same, no?:)



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Just posted 2 job offerings

[Dan CaJacob]

LOL, $30 - $250 budget for a CCSDS modem.

On Sun, Mar 4, 2018 at 5:39 AM mehtap özkan  wrote:

>
> https://discourse.myriadrf.org/t/just-posted-two-freelance-jobs/2421?u=booth
>
> If you are interested send me a message.
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
-- 
Very Respectfully,

Dan CaJacob
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] How to link OOT module in CMakeLists.txt

[ruiy]

Now I create a OOT module named slave_demo, and I have installed it. And I can 
find the dynamic lib in /usr/local/lib/libgnuradio-slave-demo.so. 

So I link it in my CMakeLists.txt by writing like this:
target_link_libraries(target ... /usr/local/lib/libgnuradio-slave-demo.so ...). 


I suppose that writing the path directly is a bad coding style. I want to know 
whether gnuradio provides some variables equals to the path when I install my 
created OOT module in my PC. I will appreciate it If anyone know something.___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] UDP Sink sending bursty packets

[Jeff Long]

Try yourblock.set_max_noutput_items(1024/itemsize)

On 03/03/2018 09:57 PM, Firdavs Pulat wrote:

Hello everyone,

I have a B200mini device I'm communicating over USB to a pc which is 
running the gnuradio software. The gnuradio does some processing (e.g., 
low-pass filtering, data type conversion, etc), and finally gets to the 
UDP sink block where packets are generated and sent through Ethernet to 
an external device. The issue I'm having is that, in the UDP block, 
noutput_items*d_itemsize size is alot larger than the UDP payload size 
(1024 bytes). So, UDP gets 4-6K worth of bytes and bursts it all out 
really fast (I can see this behavior in Wireshark), then waits to buffer 
up another 4-6K bytes, and sends it all out really fast. This process 
then continues. Is there a way to smooth this out so that it's not 
bursting bunch of packets all at once? Otherwise the external device 
isn't able to keep up and it's leading to tons of dropped packets.


I tried setting the max output buffer in python but I get this warning 
when I run: gr::log :WARN: flat_flowgraph - Block (endian_swap_impl0) 
max output buffer set to 2048 instead of requested 512.


Any ideas on what I can do to change this behaviour?

Thanks!



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Just posted 2 job offerings

[mehtap özkan]

https://discourse.myriadrf.org/t/just-posted-two-freelance-jobs/2421?u=booth

If you are interested send me a message.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Regarding Tempest implementation in GNURadio.

[Kushagra Dixit]

Hello Everybody,

I am currently a third year Bachelors in Electronics student from India. I
have had signals and systems and digital signal processing in my course
already. I have used different GNURadio projects (gr-gsm, openBTS) in the
past and have gone through Micheal Ossmann's Videos. I am very interested
in making a GNURadio implementation of Tempest (
https://github.com/martinmarinov/TempestSDR) for LCD screens. What would be
the correct way of approaching the problem ? Also what all will I need to
learn to do it efficiently ? The languages I know are C, Java and Python. I
have a USRP B210.

P.S. Also is there any definitive guide to such signals I cannot find any
reading material on them.

Any help would be greatly appreciated. This project will be for my final
year presentation.

Best Regards,
Kushagra Dixit
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio