Re: Discuss-gnuradio Digest, Vol 258, Issue 10

[Jiya Johnson]

Hi Marcus Müller,
Please find the attached file for your reference, I think this will work.

On Sat, Apr 13, 2024 at 9:32 PM  wrote:

> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
> discuss-gnuradio-requ...@gnu.org
>
> You can reach the person managing the list at
> discuss-gnuradio-ow...@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: Determining number of dropped samples from USRP Sink in
>   TX chain (walter)
>2. Modulation and demodulation issues (Jiya Johnson)
>3. Re: Modulation and demodulation issues (Marcus Müller)
>
>
> --
>
> Message: 1
> Date: Fri, 12 Apr 2024 15:42:41 -0700
> From: walter 
> To: Adrian Winter 
> Cc: "discuss-gnuradio@gnu.org" 
> Subject: Re: Determining number of dropped samples from USRP Sink in
> TX chain
> Message-ID: <7926f395-f024-44de-a6c5-e48b17998...@hacktuary.ai>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Adrian -
>
> You wrote:
> > 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 believe the usrp/uhd attempts to treat each underrun as a one-sample
> event, and report accordingly.  There's a cogent definition in the Ettus
> Driver Manual, see the section header "Underrun notes":
>
> https://files.ettus.com/manual/page_general.html#:~:text=has space
> again.-,Underrun notes,mean the host machine can't keep up with the
> requested rates.,-Threading Notes <
> https://files.ettus.com/manual/page_general.html#:~:text=has%20space%20again.-,Underrun%20notes,mean%20the%20host%20machine%20can't%20keep%20up%20with%20the%20requested%20rates
> .,-Threading%20Notes>
>
> If we define dt = 1/samp_rate  ... then (ignoring buffering and queueing),
> one underrun event means:
>  1. the usrp started waiting for a sample from your program at time
> t=t0,  but
>  2. no sample was provided after dt seconds had elapsed, and
>  3. at time t=t0+dt the usrp issued a timestamped message
> (asynchronously) about the event. SO ...
>
>
> > 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.
>
>
> NOTE: the 'event' is a point-in-time, rather than an interval of time.  It
> takes place at a time  t0 + 1/samp_rate  as described above,  and -
> although it's printed in a format that looks weird in trace output - you
> have all the info you need:
>
> > >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))
>
>
> What you're seeing above are two underruns being reported about 2ms apart
> ...
>   - the U on the second line is stderr - you'll always see one U for
> each underrrun (or a summary, depending on config)
>   - the Message:...  is because you're routing the message output of
> the USRP to a Message Debug block.
>   - the time_spec_t object tuple(int, double) contains whole seconds
> (1333) and fractional seconds (0.280334) since the USRP 'started'.
>   - Rule of thumb re t=0: a B200/B210 finishes initializing (messages
> like '[INFO] [B200] Actually got clock rate 16.777216 MHz') at around
> (time_spec 2 , 0.1000).
>
> What to do??
> The event 'duration' of each underrun is 1/samp_rate, and those stamps
> should be accurate - time deltas to be computed between two time_spec_t
> objects.
> You probably care most about the average time between events.
> Pro tip: a better way to monitor those messages is to send them to a ZMQ
> Message Sink block and process them  in a separate flowgraph or python
> script that subscribes or pulls the messages.  You can then consume them as
> numbers at your leisure.  This adds minimal blocking / backpressure to your
> flowgraph.
>
> > Is there any way to query the USRP for further information on the event?
>
>
> Yes there is:
> 1. You're already getting the 'cue' of when to look by subscribing to the
> message source.
> 2. To dig into the

ENCODER_DECODER

[Jiya Johnson]

Greetings everyone,
Need help to design a soft decision viterbi decoder with 3 bit
quantization.Any existing blocks available
Thanks in advance

BER

[Jiya Johnson]

Greetings all,
 Need help to generate BER plot for CCSDS encoder-decoder with soft
decision(euclidean distance) decoding. I am getting constant BER throughout
the plot and sometimes more than 5.5dB is getting for soft decoding.

BPSK/PM

[Jiya Johnson]

Greetings all,
How can I use BPSK modulation and demodulation blocks available in gnuradio
for a sub  carrier signal of 30 KHZ and 120 KHZ together as two chains
along with phase modulation/demodulation  of 0.5 radians.

Re: Discuss-gnuradio Digest, Vol 255, Issue 3

[Jiya Johnson]

Greetings all,
Let's say if I want to do it for Doppler frequency of 200KHz and Doppler
rate 10KHz/s is it possible to do with USRP hardware simulations.

On Tue, Jan 2, 2024 at 7:17 AM  wrote:

> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
> discuss-gnuradio-requ...@gnu.org
>
> You can reach the person managing the list at
> discuss-gnuradio-ow...@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: Doppler (Marcus D. Leech)
>2. Re: Doppler (Jeff Long)
>3. Re: Doppler (Marcus D. Leech)
>
>
> --
>
> Message: 1
> Date: Mon, 1 Jan 2024 20:31:57 -0500
> From: "Marcus D. Leech" 
> To: discuss-gnuradio@gnu.org
> Subject: Re: Doppler
> Message-ID: 
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> On 01/01/2024 20:28, Jeff Long wrote:
> > The problem here is relating this kind of chirp to anything physical.
> > As Daniel says, this may make sense for a synthesized signal. It's
> > pretty easy to create any signal you want using some combination of
> > Python and GNU Radio (or other tools). One possible problem could be
> > specifying very large numbers for parameters in some programs.
> The term "doppler" tends to imply in many engineer's minds some type of
> actual physicality...
>
>
> >
> > On Mon, Jan 1, 2024 at 7:40 PM Marcus D. Leech
> >  wrote:
> >
> > On 01/01/2024 16:11, Marcus Müller wrote:
> >>
> >> Liya,
> >>
> >> Doppler shift Δf is proportional to both speed and carrier
> >> frequency /f/₀
> >>
> >> Δ/f/ = /f/₀ · /v///c/₀,
> >>
> >> where /v/ is the relative speed of your thing, and /c/₀ is the
> >> speed of light.
> >>
> >> The highest frequencies we can, so far, do radio communications
> >> on, are in the range of f₀=150 GHz.
> >>
> >> So, assuming you do communications on 150 GHz, for your Doppler
> >> shift to be Δ/f=/10 GHz higher after 1s, your acceleration must been
> >>
> >> /a = /Δ/f / f/₀ · /c/₀ / 1s = 10 GHz / 150 GHz · 3·10⁸ m/s / s =
> >> 2/30 · 3·10⁸ m/s² = 1/15 /c/₀/s.
> >>
> >> The fastest object mankind has ever built is the Parker Solar
> >> Probe, which will burn up while it spirals into the sun, at a
> >> maximum velocity of ca 1/15 of the speed of light. It takes it
> >> years to reach that speed, not 1s.
> >>
> >> So, you're assuming you're seeing a doppler from a satellite
> >> rotating around earth that sees a relative acceleration higher
> >> than a "satellite" around the sun actively being pulled into the
> >> sun by the sun's immense gravity.
> >>
> >> That sadly makes no physical sense!
> >>
> >> Best regards,
> >> Marcus
> >>
> > C/15 is actually about *twice* as fast as the fastest object we
> > will ever have made.
> >
> >
> >> On 01.01.24 07:51, Jiya Johnson wrote:
> >>> Yes I want to use 10GHz/s
> >>>
> >>> On Sat, Dec 30, 2023, 4:05 PM Jiya Johnson
> >>>  wrote:
> >>>
> >>> Greetings everyone,
> >>> https://github.com/daniestevez/reu-2023/tree/main/doppler
> >>> I went through these grc files and tried to do
> >>> drift_simulation, i am not getting the way to get 10GHz/s
> >>> using inspectrum and frequency sink slope calculation i have
> >>> attached the grc and screenshots.
> >>> image.png
> >>> image.png
> >>>
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> https://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20240101/934e8c35/attachment.htm
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: image.png
> Type: image/png
> Size: 194533 bytes
> Desc: not available
> URL: <
> https://lists.gnu.org/archive/html

AGC_Design

[Jiya Johnson]

Greetings community,
  Through the agc for GR satellites, available at
https://destevez.net/2017/08/
Could someone please assist me in determining which is preferable for
baseband processing—feed-forward AGC or RMS AGC—based on the points in the
RMS AGC design? I am utilizing this AGC operating on a baseband signal. I'm
not receiving the precise Python file from Github to verify.

Controlport

[Jiya Johnson]

Greetings to everyone,

self.blocks_ctrlport_monitor_performance_0 = not True or
monitor("gr-perf-monitorx")
  File
"/usr/local/lib/python3.10/dist-packages/gnuradio/ctrlport/monitor.py",
line 30, in __init__
gr.prefs().singleton().set_bool("ControlPort", "on", True)
AttributeError: 'gnuradio.gr.gr_python.prefs' object has no attribute
'singleton'
ctrlport monitor received shutdown signal

Is there any inbuilt gr_profilers in gnuradio to measure buffer,latency if
not how can i get the benchmark values for comparison.
getting this error while using Ctrlport Performance Monitor in GNU Radio
3.10.8.0.
it will be very helpful if someone can help me to clear this

Processor_Cache

[Jiya Johnson]

Greetings to everyone.

Is it possible to perform some cache algorithmic tweaks to SDR using an
embedded Python block? What kind of CPU does GNU Radio have? Any ideas on
how to develop code for cache management techniques?

embedded python block-Can't interpret source code: "'__name__' not in globals"

[Jiya Johnson]

Good morning community,
I was trying to create an embedded python module with the same code for fec
extended encoder in GNU RADIO 3.10.7 version .I am encountering this
problem "Param - Code(_source_code):
Can't interpret source code: "'__name__' not in globals""
it will be very helpful if someone can help me to clear this..The used code
is 
*https://github.com/gnuradio/gnuradio/blob/master/gr-fec/python/fec/extended_encoder.py#L21
*

Round trip time calculation - simulation

[Jiya Johnson]

Hi Johannes,
Thanks in advance for your valuable inputs!
I appreciate your help so much.

1.I want to measure the time taken by 1 sample from the random source to
the decoder unit-endpoint.
2.Need more clarifications in throttle usage in terms of latency.
3.Time stamp i have used is with two stamping before encoding and after
decoding whether it will make sense ,what i understood is time delta if i
am using it will be taking only the latest time key added.
4.How can i use the control performance monitor for this FG.
GNU Radio Companion 3.10.7.0
I will upload a PDF of the flowgraph.


Latency_CCSDS.pdf
Description: Adobe PDF document

qt_gui_bercurvesink-inputs

[Jiya Johnson]

Hi Community,
BER CURVE GEN
*this block calculates the BER itself internally by comparing the original
data (pre-distortion) from input i with the post-distortion and
post-decoding data on input i+1. So input_items[i] ^ input_items[i+1] is
the BER to plot for that particular Es/N0 point.*
I Saw this explanation(
https://lists.gnu.org/archive/html/discuss-gnuradio/2016-03/msg00490.html)
but I am not clear about the source section and the noise section. By
default it will handle how we can trace those things to get the number
samples it will be analysing.

Re: CCSDS BER PLOT

[Jiya Johnson]

Thanks for the advice!
Try to do but continuously it is showing error Param - Value(value):
Value "numpy.sqrt((10.0**(-esno/10.0))/2.0)" cannot be evaluated:
name 'numpy' is not defined
how can i rectify this?
is there any already done grc files for evaluating ccsds

On Sat, Aug 19, 2023 at 9:55 PM U L  wrote:

> I'd try this:
> 1. Change the random source to a vector source with vector [ 0xFF, 0xFF,
> 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 ] (that's 4 x
> 0xFF, 8 x 0x00)
> 2. Encoder output can go to the map input, then map to a charToFloat.
> CharToFloat to decoder.
> 3. Remove the entire noise branch. It doesn't make sense to add noise
> before the map anyways. Noise would normally be added as a float after
> charToFloat.
> 4. Vector source to a delay block, delay to one input of BER block.
> Decoder output to pack8 to BER block.
> 5. You'll have to experiment with the delay value. It's probably between 2
> and 8 bytes.
> 6. If you want to try to observe the delay between the source and the
> decoder, make a 2 input time sink and connect the unpack8 output after the
> vector source to one time sink input, and the decoder output to the other
> sink input. You should be able to see the sample delay between each block
> of inputs and compute the right delay from the difference.
>
> Good luck,
> Jared.
>
> On Sat, Aug 19, 2023 at 5:13 AM Jiya Johnson 
> wrote:
>
>> Any suggestions
>>
>> On Sat, Aug 19, 2023, 9:15 AM Jiya Johnson 
>> wrote:
>>
>>> But still  in  CCSDS case i am getting -0.3 only BER and not even
>>> saturating in FEC extended CC case(as per CCSDS Standard book it is
>>> dropping to 0 by 5dB)
>>>
>>> On Sat, Aug 19, 2023 at 8:54 AM U L  wrote:
>>>
>>>> Hmm, this has gotten more complicated since your original post. Why?
>>>>
>>>> A good place to start might be the example GRC as referenced on this
>>>> page https://wiki.gnuradio.org/index.php?title=FEC_Extended_Decoder.
>>>> You can change the FEC definitions from LDPC to CC and add a BER block with
>>>> a delay b/w the input bytes and output bytes (bypass the char to float
>>>> after the decoder). Once that's working, you can replace the FEC encoder
>>>> with a CCSDS one.
>>>>
>>>> Jared.
>>>>
>>>> On Fri, Aug 18, 2023 at 9:05 PM Jiya Johnson 
>>>> wrote:
>>>>
>>>>> I am getting need help pls look on the screenshot
>>>>>
>>>>> On Sat, Aug 19, 2023 at 8:23 AM Jiya Johnson 
>>>>> wrote:
>>>>>
>>>>>> I will try and let you know
>>>>>>
>>>>>> On Sat, Aug 19, 2023, 8:08 AM U L  wrote:
>>>>>>
>>>>>>> Probably easier to use a vector source rather than text file. Vector
>>>>>>> source lets you specify the bytes exactly. So you could put in [ 0xdd, ]
>>>>>>> and be assured that byte will be output.
>>>>>>>
>>>>>>> On Fri, Aug 18, 2023 at 8:32 PM Jiya Johnson <
>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>
>>>>>>>> What I tried is 11011101( by inputting a text file )it's hex
>>>>>>>> version came in the output with (3131303131313031) like that with 
>>>>>>>> encoding
>>>>>>>> by left shifting I got the value theoretically and decode I got dd
>>>>>>>> (11011101) bt this worked over windows not in ubuntu,this output I have
>>>>>>>> done using messag debug option I am not aware whether it is the 
>>>>>>>> correct way.
>>>>>>>>
>>>>>>>> On Sat, Aug 19, 2023, 7:58 AM U L  wrote:
>>>>>>>>
>>>>>>>>> I don't understand what this means. How do you interpret it?
>>>>>>>>> Jared.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Aug 18, 2023 at 8:25 PM Jiya Johnson <
>>>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Aug 19, 2023, 7:54 AM Jiya Johnson <
>>>>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I have tried to do with a simple input 1101

Re: CCSDS BER PLOT

[Jiya Johnson]

Any suggestions

On Sat, Aug 19, 2023, 9:15 AM Jiya Johnson  wrote:

> But still  in  CCSDS case i am getting -0.3 only BER and not even
> saturating in FEC extended CC case(as per CCSDS Standard book it is
> dropping to 0 by 5dB)
>
> On Sat, Aug 19, 2023 at 8:54 AM U L  wrote:
>
>> Hmm, this has gotten more complicated since your original post. Why?
>>
>> A good place to start might be the example GRC as referenced on this page
>> https://wiki.gnuradio.org/index.php?title=FEC_Extended_Decoder. You can
>> change the FEC definitions from LDPC to CC and add a BER block with a delay
>> b/w the input bytes and output bytes (bypass the char to float after the
>> decoder). Once that's working, you can replace the FEC encoder with a CCSDS
>> one.
>>
>> Jared.
>>
>> On Fri, Aug 18, 2023 at 9:05 PM Jiya Johnson 
>> wrote:
>>
>>> I am getting need help pls look on the screenshot
>>>
>>> On Sat, Aug 19, 2023 at 8:23 AM Jiya Johnson 
>>> wrote:
>>>
>>>> I will try and let you know
>>>>
>>>> On Sat, Aug 19, 2023, 8:08 AM U L  wrote:
>>>>
>>>>> Probably easier to use a vector source rather than text file. Vector
>>>>> source lets you specify the bytes exactly. So you could put in [ 0xdd, ]
>>>>> and be assured that byte will be output.
>>>>>
>>>>> On Fri, Aug 18, 2023 at 8:32 PM Jiya Johnson 
>>>>> wrote:
>>>>>
>>>>>> What I tried is 11011101( by inputting a text file )it's hex version
>>>>>> came in the output with (3131303131313031) like that with encoding by 
>>>>>> left
>>>>>> shifting I got the value theoretically and decode I got dd (11011101) bt
>>>>>> this worked over windows not in ubuntu,this output I have done using 
>>>>>> messag
>>>>>> debug option I am not aware whether it is the correct way.
>>>>>>
>>>>>> On Sat, Aug 19, 2023, 7:58 AM U L  wrote:
>>>>>>
>>>>>>> I don't understand what this means. How do you interpret it?
>>>>>>> Jared.
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Aug 18, 2023 at 8:25 PM Jiya Johnson <
>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Aug 19, 2023, 7:54 AM Jiya Johnson 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have tried to do with a simple input 11011101 without noise and
>>>>>>>>> with noise noise also
>>>>>>>>>
>>>>>>>>> On Sat, Aug 19, 2023, 7:52 AM U L  wrote:
>>>>>>>>>
>>>>>>>>>> Some ideas:
>>>>>>>>>>
>>>>>>>>>> 1. Remove the noise completely. Also use a fixed, repeating input
>>>>>>>>>> vector rather than random bytes. Look at the actual error patterns 
>>>>>>>>>> between
>>>>>>>>>> the input and output bits. Sometimes error patterns can clue you in.
>>>>>>>>>> 2. Check symbol polarity (i.e. 0=>-1, 1=>1, or 0=>1, 1=>-1)
>>>>>>>>>> 3. Try the more general (non-CCSDS) extended encoder with the
>>>>>>>>>> same params as the decoder.
>>>>>>>>>> 4. Esp if 3 works, compare the output of CCSDS with general
>>>>>>>>>> extended encoder.
>>>>>>>>>>
>>>>>>>>>> Good luck.
>>>>>>>>>> Jared.
>>>>>>>>>>
>>>>>>>>>> On Fri, Aug 18, 2023 at 8:04 PM Jiya Johnson <
>>>>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>> Based on the given modifications still I am getting a -0.300
>>>>>>>>>>> range of BER constantly from 0 to 15 dB range of SNR values.No 
>>>>>>>>>>> variations
>>>>>>>>>>> are happening.
>>>>>>>>>>>
>>>>>>>>>>> How can I check the functionality of the block(encoder and
>>>>>>>&

Re: CCSDS BER PLOT

[Jiya Johnson]

But still  in  CCSDS case i am getting -0.3 only BER and not even
saturating in FEC extended CC case(as per CCSDS Standard book it is
dropping to 0 by 5dB)

On Sat, Aug 19, 2023 at 8:54 AM U L  wrote:

> Hmm, this has gotten more complicated since your original post. Why?
>
> A good place to start might be the example GRC as referenced on this page
> https://wiki.gnuradio.org/index.php?title=FEC_Extended_Decoder. You can
> change the FEC definitions from LDPC to CC and add a BER block with a delay
> b/w the input bytes and output bytes (bypass the char to float after the
> decoder). Once that's working, you can replace the FEC encoder with a CCSDS
> one.
>
> Jared.
>
> On Fri, Aug 18, 2023 at 9:05 PM Jiya Johnson 
> wrote:
>
>> I am getting need help pls look on the screenshot
>>
>> On Sat, Aug 19, 2023 at 8:23 AM Jiya Johnson 
>> wrote:
>>
>>> I will try and let you know
>>>
>>> On Sat, Aug 19, 2023, 8:08 AM U L  wrote:
>>>
>>>> Probably easier to use a vector source rather than text file. Vector
>>>> source lets you specify the bytes exactly. So you could put in [ 0xdd, ]
>>>> and be assured that byte will be output.
>>>>
>>>> On Fri, Aug 18, 2023 at 8:32 PM Jiya Johnson 
>>>> wrote:
>>>>
>>>>> What I tried is 11011101( by inputting a text file )it's hex version
>>>>> came in the output with (3131303131313031) like that with encoding by left
>>>>> shifting I got the value theoretically and decode I got dd (11011101) bt
>>>>> this worked over windows not in ubuntu,this output I have done using 
>>>>> messag
>>>>> debug option I am not aware whether it is the correct way.
>>>>>
>>>>> On Sat, Aug 19, 2023, 7:58 AM U L  wrote:
>>>>>
>>>>>> I don't understand what this means. How do you interpret it?
>>>>>> Jared.
>>>>>>
>>>>>>
>>>>>> On Fri, Aug 18, 2023 at 8:25 PM Jiya Johnson 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> On Sat, Aug 19, 2023, 7:54 AM Jiya Johnson 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I have tried to do with a simple input 11011101 without noise and
>>>>>>>> with noise noise also
>>>>>>>>
>>>>>>>> On Sat, Aug 19, 2023, 7:52 AM U L  wrote:
>>>>>>>>
>>>>>>>>> Some ideas:
>>>>>>>>>
>>>>>>>>> 1. Remove the noise completely. Also use a fixed, repeating input
>>>>>>>>> vector rather than random bytes. Look at the actual error patterns 
>>>>>>>>> between
>>>>>>>>> the input and output bits. Sometimes error patterns can clue you in.
>>>>>>>>> 2. Check symbol polarity (i.e. 0=>-1, 1=>1, or 0=>1, 1=>-1)
>>>>>>>>> 3. Try the more general (non-CCSDS) extended encoder with the same
>>>>>>>>> params as the decoder.
>>>>>>>>> 4. Esp if 3 works, compare the output of CCSDS with general
>>>>>>>>> extended encoder.
>>>>>>>>>
>>>>>>>>> Good luck.
>>>>>>>>> Jared.
>>>>>>>>>
>>>>>>>>> On Fri, Aug 18, 2023 at 8:04 PM Jiya Johnson <
>>>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> Based on the given modifications still I am getting a -0.300
>>>>>>>>>> range of BER constantly from 0 to 15 dB range of SNR values.No 
>>>>>>>>>> variations
>>>>>>>>>> are happening.
>>>>>>>>>>
>>>>>>>>>> How can I check the functionality of the block(encoder and
>>>>>>>>>> decoder to check whether it's encoding and decoding properly)with a 
>>>>>>>>>> sample
>>>>>>>>>> input.
>>>>>>>>>>
>>>>>>>>>> On Sun, Aug 13, 2023, 8:11 PM U L  wrote:
>>>>>>>>>>
>>>>>>>>>>> One other thing I noticed is that the encode CCSDS, decode,
>>>>&

Re: CCSDS BER PLOT

[Jiya Johnson]

I will try and let you know

On Sat, Aug 19, 2023, 8:08 AM U L  wrote:

> Probably easier to use a vector source rather than text file. Vector
> source lets you specify the bytes exactly. So you could put in [ 0xdd, ]
> and be assured that byte will be output.
>
> On Fri, Aug 18, 2023 at 8:32 PM Jiya Johnson 
> wrote:
>
>> What I tried is 11011101( by inputting a text file )it's hex version came
>> in the output with (3131303131313031) like that with encoding by left
>> shifting I got the value theoretically and decode I got dd (11011101) bt
>> this worked over windows not in ubuntu,this output I have done using messag
>> debug option I am not aware whether it is the correct way.
>>
>> On Sat, Aug 19, 2023, 7:58 AM U L  wrote:
>>
>>> I don't understand what this means. How do you interpret it?
>>> Jared.
>>>
>>>
>>> On Fri, Aug 18, 2023 at 8:25 PM Jiya Johnson 
>>> wrote:
>>>
>>>>
>>>> On Sat, Aug 19, 2023, 7:54 AM Jiya Johnson 
>>>> wrote:
>>>>
>>>>> I have tried to do with a simple input 11011101 without noise and with
>>>>> noise noise also
>>>>>
>>>>> On Sat, Aug 19, 2023, 7:52 AM U L  wrote:
>>>>>
>>>>>> Some ideas:
>>>>>>
>>>>>> 1. Remove the noise completely. Also use a fixed, repeating input
>>>>>> vector rather than random bytes. Look at the actual error patterns 
>>>>>> between
>>>>>> the input and output bits. Sometimes error patterns can clue you in.
>>>>>> 2. Check symbol polarity (i.e. 0=>-1, 1=>1, or 0=>1, 1=>-1)
>>>>>> 3. Try the more general (non-CCSDS) extended encoder with the same
>>>>>> params as the decoder.
>>>>>> 4. Esp if 3 works, compare the output of CCSDS with general extended
>>>>>> encoder.
>>>>>>
>>>>>> Good luck.
>>>>>> Jared.
>>>>>>
>>>>>> On Fri, Aug 18, 2023 at 8:04 PM Jiya Johnson 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> Based on the given modifications still I am getting a -0.300 range
>>>>>>> of BER constantly from 0 to 15 dB range of SNR values.No variations are
>>>>>>> happening.
>>>>>>>
>>>>>>> How can I check the functionality of the block(encoder and decoder
>>>>>>> to check whether it's encoding and decoding properly)with a sample 
>>>>>>> input.
>>>>>>>
>>>>>>> On Sun, Aug 13, 2023, 8:11 PM U L  wrote:
>>>>>>>
>>>>>>>> One other thing I noticed is that the encode CCSDS, decode, CCSDS,
>>>>>>>> and BER blocks all  operate on packed bytes. (See e.g.
>>>>>>>> https://wiki.gnuradio.org/index.php?title=Encode_CCSDS_27). To do
>>>>>>>> this you would change your random source to output from 0 to 256 byte
>>>>>>>> values. Also, considering the output of the decoder block are packed 
>>>>>>>> bytes
>>>>>>>> you should probably skip the byte->float and binary slicer after your
>>>>>>>> decoder and just input it's output directly into the BER block. 
>>>>>>>> Finally,
>>>>>>>> looking at the
>>>>>>>> https://wiki.gnuradio.org/index.php?title=Decode_CCSDS_27 page it
>>>>>>>> seems the delay out of the decoder is 4 bytes, so you could add a 
>>>>>>>> delay of
>>>>>>>> 4 between your source and BER block to align the two streams.
>>>>>>>>
>>>>>>>> Jared.
>>>>>>>>
>>>>>>>> On Sat, Aug 12, 2023 at 9:58 PM U L  wrote:
>>>>>>>>
>>>>>>>>> One thing I think might be an issue is that you have no delay
>>>>>>>>> between your source reference and your BER block. Usually the FEC 
>>>>>>>>> decoders
>>>>>>>>> (and possibly the encoder?) may output blocks of 0s before they 
>>>>>>>>> output the
>>>>>>>>> samples that correspond to your inputs. I don't know much about those 
>>>>>>>>> FEC
>>>>>>>>> blocks specifically, but maybe the docs have some info on their 
>>>>>>>>> delays. You
>>>>>>>>> can just insert a delay block b/w your random source and the ber 
>>>>>>>>> block to
>>>>>>>>> align the input and output bits.
>>>>>>>>>
>>>>>>>>> Hope that helps,
>>>>>>>>> Jared.
>>>>>>>>>
>>>>>>>>> On Sat, Aug 12, 2023 at 4:28 AM Jiya Johnson <
>>>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [image: image.png]
>>>>>>>>>> Dear community
>>>>>>>>>>Need help for BER plot using the above flowgraph its always
>>>>>>>>>> coming 10^-1.17 and whenever I tried to change the noise voltage the 
>>>>>>>>>> values
>>>>>>>>>> are not changing.
>>>>>>>>>> Please find the attached GRC file for your reference.
>>>>>>>>>>
>>>>>>>>>> *Regards, JIYA JOHNSON*
>>>>>>>>>>
>>>>>>>>>>

Re: CCSDS BER PLOT

[Jiya Johnson]

What I tried is 11011101( by inputting a text file )it's hex version came
in the output with (3131303131313031) like that with encoding by left
shifting I got the value theoretically and decode I got dd (11011101) bt
this worked over windows not in ubuntu,this output I have done using messag
debug option I am not aware whether it is the correct way.

On Sat, Aug 19, 2023, 7:58 AM U L  wrote:

> I don't understand what this means. How do you interpret it?
> Jared.
>
>
> On Fri, Aug 18, 2023 at 8:25 PM Jiya Johnson 
> wrote:
>
>>
>> On Sat, Aug 19, 2023, 7:54 AM Jiya Johnson 
>> wrote:
>>
>>> I have tried to do with a simple input 11011101 without noise and with
>>> noise noise also
>>>
>>> On Sat, Aug 19, 2023, 7:52 AM U L  wrote:
>>>
>>>> Some ideas:
>>>>
>>>> 1. Remove the noise completely. Also use a fixed, repeating input
>>>> vector rather than random bytes. Look at the actual error patterns between
>>>> the input and output bits. Sometimes error patterns can clue you in.
>>>> 2. Check symbol polarity (i.e. 0=>-1, 1=>1, or 0=>1, 1=>-1)
>>>> 3. Try the more general (non-CCSDS) extended encoder with the same
>>>> params as the decoder.
>>>> 4. Esp if 3 works, compare the output of CCSDS with general extended
>>>> encoder.
>>>>
>>>> Good luck.
>>>> Jared.
>>>>
>>>> On Fri, Aug 18, 2023 at 8:04 PM Jiya Johnson 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> Based on the given modifications still I am getting a -0.300 range of
>>>>> BER constantly from 0 to 15 dB range of SNR values.No variations are
>>>>> happening.
>>>>>
>>>>> How can I check the functionality of the block(encoder and decoder to
>>>>> check whether it's encoding and decoding properly)with a sample input.
>>>>>
>>>>> On Sun, Aug 13, 2023, 8:11 PM U L  wrote:
>>>>>
>>>>>> One other thing I noticed is that the encode CCSDS, decode, CCSDS,
>>>>>> and BER blocks all  operate on packed bytes. (See e.g.
>>>>>> https://wiki.gnuradio.org/index.php?title=Encode_CCSDS_27). To do
>>>>>> this you would change your random source to output from 0 to 256 byte
>>>>>> values. Also, considering the output of the decoder block are packed 
>>>>>> bytes
>>>>>> you should probably skip the byte->float and binary slicer after your
>>>>>> decoder and just input it's output directly into the BER block. Finally,
>>>>>> looking at the
>>>>>> https://wiki.gnuradio.org/index.php?title=Decode_CCSDS_27 page it
>>>>>> seems the delay out of the decoder is 4 bytes, so you could add a delay 
>>>>>> of
>>>>>> 4 between your source and BER block to align the two streams.
>>>>>>
>>>>>> Jared.
>>>>>>
>>>>>> On Sat, Aug 12, 2023 at 9:58 PM U L  wrote:
>>>>>>
>>>>>>> One thing I think might be an issue is that you have no delay
>>>>>>> between your source reference and your BER block. Usually the FEC 
>>>>>>> decoders
>>>>>>> (and possibly the encoder?) may output blocks of 0s before they output 
>>>>>>> the
>>>>>>> samples that correspond to your inputs. I don't know much about those 
>>>>>>> FEC
>>>>>>> blocks specifically, but maybe the docs have some info on their delays. 
>>>>>>> You
>>>>>>> can just insert a delay block b/w your random source and the ber block 
>>>>>>> to
>>>>>>> align the input and output bits.
>>>>>>>
>>>>>>> Hope that helps,
>>>>>>> Jared.
>>>>>>>
>>>>>>> On Sat, Aug 12, 2023 at 4:28 AM Jiya Johnson <
>>>>>>> jiyajohnso...@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> [image: image.png]
>>>>>>>> Dear community
>>>>>>>>Need help for BER plot using the above flowgraph its always
>>>>>>>> coming 10^-1.17 and whenever I tried to change the noise voltage the 
>>>>>>>> values
>>>>>>>> are not changing.
>>>>>>>> Please find the attached GRC file for your reference.
>>>>>>>>
>>>>>>>> *Regards, JIYA JOHNSON*
>>>>>>>>
>>>>>>>>

Re: CCSDS BER PLOT

[Jiya Johnson]

I have tried to do with a simple input 11011101 without noise and with
noise noise also

On Sat, Aug 19, 2023, 7:52 AM U L  wrote:

> Some ideas:
>
> 1. Remove the noise completely. Also use a fixed, repeating input vector
> rather than random bytes. Look at the actual error patterns between the
> input and output bits. Sometimes error patterns can clue you in.
> 2. Check symbol polarity (i.e. 0=>-1, 1=>1, or 0=>1, 1=>-1)
> 3. Try the more general (non-CCSDS) extended encoder with the same params
> as the decoder.
> 4. Esp if 3 works, compare the output of CCSDS with general extended
> encoder.
>
> Good luck.
> Jared.
>
> On Fri, Aug 18, 2023 at 8:04 PM Jiya Johnson 
> wrote:
>
>> Hi,
>> Based on the given modifications still I am getting a -0.300 range of BER
>> constantly from 0 to 15 dB range of SNR values.No variations are happening.
>>
>> How can I check the functionality of the block(encoder and decoder to
>> check whether it's encoding and decoding properly)with a sample input.
>>
>> On Sun, Aug 13, 2023, 8:11 PM U L  wrote:
>>
>>> One other thing I noticed is that the encode CCSDS, decode, CCSDS, and
>>> BER blocks all  operate on packed bytes. (See e.g.
>>> https://wiki.gnuradio.org/index.php?title=Encode_CCSDS_27). To do this
>>> you would change your random source to output from 0 to 256 byte values.
>>> Also, considering the output of the decoder block are packed bytes you
>>> should probably skip the byte->float and binary slicer after your decoder
>>> and just input it's output directly into the BER block. Finally, looking at
>>> the https://wiki.gnuradio.org/index.php?title=Decode_CCSDS_27 page it
>>> seems the delay out of the decoder is 4 bytes, so you could add a delay of
>>> 4 between your source and BER block to align the two streams.
>>>
>>> Jared.
>>>
>>> On Sat, Aug 12, 2023 at 9:58 PM U L  wrote:
>>>
>>>> One thing I think might be an issue is that you have no delay between
>>>> your source reference and your BER block. Usually the FEC decoders (and
>>>> possibly the encoder?) may output blocks of 0s before they output the
>>>> samples that correspond to your inputs. I don't know much about those FEC
>>>> blocks specifically, but maybe the docs have some info on their delays. You
>>>> can just insert a delay block b/w your random source and the ber block to
>>>> align the input and output bits.
>>>>
>>>> Hope that helps,
>>>> Jared.
>>>>
>>>> On Sat, Aug 12, 2023 at 4:28 AM Jiya Johnson 
>>>> wrote:
>>>>
>>>>>
>>>>> [image: image.png]
>>>>> Dear community
>>>>>Need help for BER plot using the above flowgraph its always coming
>>>>> 10^-1.17 and whenever I tried to change the noise voltage the values are
>>>>> not changing.
>>>>> Please find the attached GRC file for your reference.
>>>>>
>>>>> *Regards, JIYA JOHNSON*
>>>>>
>>>>>

Re: CCSDS BER PLOT

[Jiya Johnson]

Hi,
Based on the given modifications still I am getting a -0.300 range of BER
constantly from 0 to 15 dB range of SNR values.No variations are happening.

How can I check the functionality of the block(encoder and decoder to check
whether it's encoding and decoding properly)with a sample input.

On Sun, Aug 13, 2023, 8:11 PM U L  wrote:

> One other thing I noticed is that the encode CCSDS, decode, CCSDS, and BER
> blocks all  operate on packed bytes. (See e.g.
> https://wiki.gnuradio.org/index.php?title=Encode_CCSDS_27). To do this
> you would change your random source to output from 0 to 256 byte values.
> Also, considering the output of the decoder block are packed bytes you
> should probably skip the byte->float and binary slicer after your decoder
> and just input it's output directly into the BER block. Finally, looking at
> the https://wiki.gnuradio.org/index.php?title=Decode_CCSDS_27 page it
> seems the delay out of the decoder is 4 bytes, so you could add a delay of
> 4 between your source and BER block to align the two streams.
>
> Jared.
>
> On Sat, Aug 12, 2023 at 9:58 PM U L  wrote:
>
>> One thing I think might be an issue is that you have no delay between
>> your source reference and your BER block. Usually the FEC decoders (and
>> possibly the encoder?) may output blocks of 0s before they output the
>> samples that correspond to your inputs. I don't know much about those FEC
>> blocks specifically, but maybe the docs have some info on their delays. You
>> can just insert a delay block b/w your random source and the ber block to
>> align the input and output bits.
>>
>> Hope that helps,
>> Jared.
>>
>> On Sat, Aug 12, 2023 at 4:28 AM Jiya Johnson 
>> wrote:
>>
>>>
>>> [image: image.png]
>>> Dear community
>>>Need help for BER plot using the above flowgraph its always coming
>>> 10^-1.17 and whenever I tried to change the noise voltage the values are
>>> not changing.
>>> Please find the attached GRC file for your reference.
>>>
>>> *Regards, JIYA JOHNSON*
>>>
>>>

CCSDS encoder-decoder BER Plot

[Jiya Johnson]

Hello GNU Radio community i tried to plot BER vs SNR by using the below
given GRC file ,I am not getting the results which is similar to the
conventional encoder/decoder ,CCSDS encoder/decoder in CCSDS standards .It
will be helpful for me to make suggestions to improve the same

options:
  parameters:
author: jiyaj
catch_exceptions: 'True'
category: '[GRC Hier Blocks]'
cmake_opt: ''
comment: ''
copyright: ''
description: ''
gen_cmake: 'On'
gen_linking: dynamic
generate_options: qt_gui
hier_block_src_path: '.:'
id: CHECKCCSDS
max_nouts: '0'
output_language: python
placement: (0,0)
qt_qss_theme: ''
realtime_scheduling: ''
run: 'True'
run_command: '{python} -u {filename}'
run_options: prompt
sizing_mode: fixed
thread_safe_setters: ''
title: 27-07-2023
window_size: (1000,1000)
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [8, 8]
rotation: 0
state: enabled

blocks:
- name: noise_stdv
  id: variable_qtgui_range
  parameters:
comment: ''
gui_hint: ''
label: Noise Amplitude
min_len: '500'
orient: QtCore.Qt.Horizontal
rangeType: float
start: '0'
step: '.01'
stop: '40'
value: '0'
widget: counter_slider
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [1488, 16.0]
rotation: 0
state: enabled
- name: samp_rate
  id: variable
  parameters:
comment: ''
value: '32000'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [248, 16.0]
rotation: 0
state: enabled
- name: variable_cc_decoder_def_0
  id: variable_cc_decoder_def
  parameters:
comment: ''
dim1: '1'
dim2: '1'
framebits: '8'
k: '7'
mode: fec.CC_TERMINATED
ndim: '0'
padding: 'False'
polys: '[109,79]'
rate: '2'
state_end: '-1'
state_start: '0'
value: '"ok"'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [1136, 12.0]
rotation: 0
state: true
- name: variable_ccsds_encoder_def_0
  id: variable_ccsds_encoder_def
  parameters:
comment: ''
dim1: '1'
dim2: '1'
framebits: '8'
mode: fec.CC_TERMINATED
ndim: '0'
state_start: '0'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [384, 12.0]
rotation: 0
state: enabled
- name: variable_constellation_0
  id: variable_constellation
  parameters:
comment: ''
const_points: '[ -1+1j, 1+1j]'
dims: '1'
normalization: digital.constellation.AMPLITUDE_NORMALIZATION
precision: '8'
rot_sym: '1'
soft_dec_lut: None
sym_map: '[1, -1]'
type: calcdist
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [760, 8.0]
rotation: 0
state: true
- name: analog_fastnoise_source_x_0
  id: analog_fastnoise_source_x
  parameters:
affinity: ''
alias: ''
amp: noise_stdv
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
noise_type: analog.GR_GAUSSIAN
samples: '8192'
seed: '0'
type: complex
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [656, 1364.0]
rotation: 0
state: enabled
- name: blocks_add_xx_0
  id: blocks_add_xx
  parameters:
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
num_inputs: '2'
type: complex
vlen: '1'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [1176, 1320.0]
rotation: 0
state: enabled
- name: blocks_char_to_float_0
  id: blocks_char_to_float
  parameters:
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
scale: '1'
vlen: '1'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [1680, 448.0]
rotation: 0
state: disabled
- name: blocks_char_to_float_0_0
  id: blocks_char_to_float
  parameters:
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
scale: '1'
vlen: '1'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [3768, 360.0]
rotation: 0
state: disabled
- name: blocks_char_to_float_0_1
  id: blocks_char_to_float
  parameters:
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
scale: '1'
vlen: '1'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [2552, 728.0]
rotation: 0
state: enabled
- name: blocks_char_to_float_1
  id: blocks_char_to_float
  parameters:
affinity: ''
alias: ''
comment: ''
maxoutbuf: '0'
minoutbuf: '0'
scale: '1'
vlen: '1'
  states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [4320, 136.0]
rotation: 0
state: true
- name: blocks_char_to_float_2
  

FEC ENCODER ,DECODER

[Jiya Johnson]

Good evening community,

I Have tried to an implementation with a file source having input 1101 1101
and i want to do encoding and decoding with convolutional codes tried to
check the functionality with message debug and QT GUI blocks but decoding
is not happening and after all process i need to check the BER.Pls help me!
It will help me a lot
Please find the GRC File of implementations and source input I have given.

-- 

*Regards, JIYA JOHNSON*
1101 1101

fec encoder_checking.grc
Description: Binary data

Algorithm in convolutional encoder and decoder blocks of grfec

[Jiya Johnson]

Good evening community,
   I am stuck with my implementation,need a clarification for the block
fec encoder and decoder.
What is the functionality of the fec encoder and decoder block .
My design of flow is in such way like need to get the convolutional encoded
and decided values seperately from the same.Please help to study the
algorithm used in convolutional encoder and decoder and also the
functionality.using Gnu radio 3.10.6

PDU vector format and Data controlling

[Jiya Johnson]

Hi GNU Radio Community,
 I tried to implement a small transmitter section with random
source with min=0 and max=2 with repeat -yes by setting samp rate as 32k
and convolution encoder ,constellation modulator in the end section ,tried
to connect the stream to PDU conversion to calculate the time taken and i
have used message debug to it but it is printing n number of times and
PYTHON IS NOT RESPONDING and after all i need to restart again.
Any solution to regulate the data stream generation so that i can restrict
data printing in the message debug.
Need more clarification regarding the PDU VECTORS i generated 0,1
continuously for 10 samples but the PDU vector( 01 :00 00 00 00 00 00
01 00 ) contents printed in the output are not able to decode .

Thanks in Advance

To limit the messages

[Jiya Johnson]

Hi GNU Radio community
Tried to implement pdu vector messages output generation but it's printing
n number of times in the terminal after it is causing to python not
responding and reopening the terminal after execution of flow graph is the
only solution,Do you have any solution suggested for this case.

Latency calculation

[Jiya Johnson]

Hi GNU Radio community,
 Is there any in build block to find out the latency in a simple
implementation of transmitter,receiver and channel .It will be helpful if I
am getting one flow graph.

eliminate the terminal messages

[Jiya Johnson]

Good afternoon,
  I am working on GNU based flowgraph designing in Windows versions 10/11
with GNU 3.10.6.1 . I would like to know *how to eliminate the terminal
messages like asynchronous message buffer overflowing *
Thanks in Advance.

Discussion regarding latency

[Jiya Johnson]

 Good morning,
  I would like to know *how to calculate the latency if we are sending
a signal or a data packet from source to receiver in GNU Radio*.

Thanks in Advance.