Re: [Discuss-gnuradio] Regarding correlate access code-tag block

[Maitry Raval]

Hello,
I have updated Ubuntu version to 18.10 in order to install GNU radio version 
3.7.12. (As GNU radio version 3.7.12 have bug fixes for additive CCSDS de 
scrambler, as per said by gr-satellites). but the different problem arises, 
when I have simulate(run) the same GRC flow graph file (the one with correlate 
access tag stream and fixed length packet tagger). I have attached the GRC file 
for your reference.As this file is run with generate option to NO GUI option, 
once I press the run button in GRC, it is not continuously run the flow graph 
and didnot get the output. can you please tell me, when am i dong wrong.

With Best Regards,
Maitry Raval,


----- Original Message -----
From: "Maitry Raval" <address@hidden>
To: "Cinaed Simson" <address@hidden>
Cc: "discuss-gnuradio" <address@hidden>
Sent: Friday, January 18, 2019 10:11:18 AM
Subject: Re: [Discuss-gnuradio] Regarding correlate access code-tag block

Thanks for your guidance and support.
I will try to make flow graph with the blocks as per examples given by you.

With Best Regards,
Maitry Raval,

----- Original Message -----
From: "Cinaed Simson" <address@hidden>
To: "Maitry Raval" <address@hidden>
Cc: "discuss-gnuradio" <address@hidden>
Sent: Tuesday, January 15, 2019 10:25:52 AM
Subject: Re: [Discuss-gnuradio] Regarding correlate access code-tag block

Actually, with the Default Header Format file, and the Protocol
Formatter, use correlation-access tagged block was a piece of cake.

Also, here's an example of bspk using constellations - if you haven't
found already.

-- Cinaed

On 1/14/19 12:39 PM, Cinaed Simson wrote:
> As you may have already discovered, I was wrong about unpacking bits for
> fec.
> 
> Actually, I have no idea on how I'm getting the results I'm getting
> using my modifications of your flowgraph - those depreciated blocks
> definitely have strange problems. If I insert the unpack k=8 block as
> required for fec the flowgraph doesn't work.
> 
> I ran into a problem testing fec - I modified your sources and I didn't
> have enough frame bits. So I set the frame bits to exactly what I need.
> 
> And I can't get a simple correlation access tagged test working - even
> with a tag gate. The only way it works is if remove the access code -
> which defeats the purpose.
> 
> So I'm go to have to evolve and get the protocol formatter working.
> 
> Also, you don't have to use the rx and tx packet blocks - you can use
> the replacements for the PSK mod/demod blocks - the constellation
> mod/demod blocks - you probably shouldn't use any depreciated blocks.
> 
> -- Cinaed
> 
> 
> On 1/10/19 10:01 PM, Maitry Raval wrote:
>> Hello,
>>
>> Ok, One more query, what is the purpose of the block unpack k=1 bit at 
>> output of PSK demod block, because the meaning of unpack k=1 means byte to 
>> byte conversion, right?
>>
>> With Best Regards,
>> Maitry Raval,
>>
>> ----- Original Message -----
>> From: "Cinaed Simson" <address@hidden>
>> To: "Maitry Raval" <address@hidden>
>> Cc: "discuss-gnuradio" <address@hidden>
>> Sent: Friday, January 11, 2019 2:11:54 AM
>> Subject: Re: [Discuss-gnuradio] Regarding correlate access code-tag block
>>
>> On 1/10/19 2:47 AM, Maitry Raval wrote:
>>> Hello,
>>>
>>> Thanks for your time!
>>>
>>> It works completely fine, now I understand that we have to give tagged 
>>> stream at the input of encoder.
>>
>> Sorry, I didn't mean to imply you needed the stream to tagged stream
>> block to make it work.
>>
>> I just put in at the beginning so I could use the tag debug as a brute
>> force search to find out what was blocking the flow.
>>
>> There are two sequential tag blocks - the correlate correlate access
>> code-tag from gnuradio and a block from gr-satellites - I would guess
>> that is all you need.
>>
>> Select "pass thru" on the stream to tagged stream block - it should
>> still work.
>>
>> -- Cinaed
>>
>>
>>>
>>>
>>> With Best Regards,
>>> Maitry Raval,
>>> R& D engineer|Azista Industries Pvt Ltd| 
>>> 079-40605800|www.azistaaerospace.com
>>>
>>> ----- Original Message -----
>>> From: "Cinaed Simson" <address@hidden>
>>> To: "discuss-gnuradio" <address@hidden>
>>> Cc: "Maitry Raval" <address@hidden>
>>> Sent: Thursday, January 10, 2019 1:21:34 PM
>>> Subject: Re: [Discuss-gnuradio] Regarding correlate access code-tag block
>>>
>>> Hi Mailry - I was able to get it run.
>>>
>>> I used the "correlate access" block from gnuradio - my installation of
>>> gnuradio didn't like the block in your flowgraph.
>>>
>>> And then I had to install the python module "construct" in order to get
>>> the flowgraph to run.
>>>
>>> In order to get the flowchart to work - at least in the sense of filling
>>> up the output.txt file - I added a "Stream to Tagged Stream" block and
>>> define a consist tag to get the Tag Debug block to work.
>>>
>>> Also, I had to remove the "unpack" block before the PSK modulation,
>>> added a "Unpack K=1" block just after the PSK demodulation - and I set
>>> "Generate Options" to "No Gui" in the Options block.
>>>
>>> -- Cinaed
>>>
>>>
>>>
>>> On 1/8/19 12:40 AM, Maitry Raval wrote:
>>>> Hello, 
>>>> thanks for your guidance.
>>>> I have also attached the grc file, input/output files and python file for 
>>>> your reference. after adding tag debug, still didn't get any output. I 
>>>> have also tried this same in ubuntu 18.04 with GNU radio 3.7.11 version.
>>>> actually because these psk blocks are deprecated, I have tried it with 
>>>> dpsk mod, demod block. But as I wanted to do continuous transmission, I 
>>>> didn't find replaced block for correlate access code-tag block, and the 
>>>> cusom block from gr-satellites are for extracting syncbits. 
>>>> I have also tried with simple flow graph by just sream muxing 2 files one 
>>>> with sync bits and other one is payload file and give that output to 
>>>> correlate access code-tag block, but that also didn't work.
>>>>
>>>> It would be grateful, If you guide me on this. I just want to make that 
>>>> sync bits searching and extracting from payload and receive only payload 
>>>> at the output. 
>>>>
>>>>
>>>> With Best Regards,
>>>> Maitry Raval,
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Cinaed Simson" <address@hidden>
>>>> To: "discuss-gnuradio" <address@hidden>
>>>> Sent: Tuesday, January 8, 2019 1:47:56 PM
>>>> Subject: Re: [Discuss-gnuradio] Regarding correlate access code-tag block
>>>>
>>>> I broke down and looked at the image.
>>>>
>>>> Note, PSK Demod, Correlate Access Code - Tag, Packet Encoder, and Packet
>>>> Decoder have been depreciated.
>>>>
>>>> And they're usually depreciated because they have problems - and they
>>>> are usually replaced with different blocks which work better and are
>>>> typically more general.
>>>>
>>>> The tutorials are good place to start looking for the replacements.
>>>>
>>>> -- Cinaed
>>>>
>>>>
>>>> On 1/7/19 11:22 PM, Thomas Lavarenne wrote:
>>>>> Oh, it is "File Sink" not "Tagged file sink", didn't see sorry.
>>>>>
>>>>> Le mar. 8 janv. 2019 à 08:20, Thomas Lavarenne
>>>>> <address@hidden <mailto:address@hidden>> a écrit :
>>>>>
>>>>>
>>>>>
>>>>>     Hi,
>>>>>
>>>>>         But, the issue is that correlate access code-tag block is not
>>>>>         working and producing tags, so that my output file will come
>>>>>         blank. as  I am certain that at the output of FEC extended
>>>>>         decoder, both the sync bits and payload is available which I
>>>>>         have seen by attaching file sink at the output of FEC extended
>>>>>         decoder.
>>>>>
>>>>>
>>>>>     There is a block "Tag Debug" to see if the tag is generated behind
>>>>>     "correlate access code - tag block".
>>>>>
>>>>>     On the other hand, the documentation of "Tagged File sink" indicate
>>>>>     that the block need the keyword "burst" (with value: True) to
>>>>>     trigger the saving of the data.
>>>>>
>>>>>     Best regards,
>>>>>
>>>>>     Thomas
>>>>>
>>>>>     _______________________________________________
>>>>>
>>>>>         Discuss-gnuradio mailing list
>>>>>         address@hidden <mailto:address@hidden>
>>>>>         https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Discuss-gnuradio mailing list
>>>>> address@hidden
>>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Discuss-gnuradio mailing list
>>>> address@hidden
>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>
>>>>
>>>> _______________________________________________
>>>> Discuss-gnuradio mailing list
>>>> address@hidden
>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>
>>> .
>>>
>>
>

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

mod-demod.grc
Description: application/xml