Hello, Thanks for your time!
It works completely fine, now I understand that we have to give tagged stream at the input of encoder. With Best Regards, Maitry Raval, R& D engineer|Azista Industries Pvt Ltd| 079-40605800|www.azistaaerospace.com ----- Original Message ----- From: "Cinaed Simson" <cinaed.sim...@gmail.com> To: "discuss-gnuradio" <discuss-gnuradio@gnu.org> Cc: "Maitry Raval" <maitry.ra...@azistaaerospace.com> 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" <cinaed.sim...@gmail.com> > To: "discuss-gnuradio" <discuss-gnuradio@gnu.org> > 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 >> <thomas.lavare...@gmail.com <mailto:thomas.lavare...@gmail.com>> 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 >> Discuss-gnuradio@gnu.org <mailto: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 > _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
