Re: [Discuss-gnuradio] FW: Re: File sink permission error on Windows

[김태영]

When I use GRC 3792 , 'C:\\Work\\GRC_Work\\goodbin' works and
'C:\\Work\\GRC_Work\\badbin' fail

But after I install GRC 37111, both works well 

 



Original Message

Subject : Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows

Date : 2017-08-09 18:03:00

From : Marcus Müller 

To : 김태영 

Cc :



How?
 

On 08/09/2017 04:31 AM, 김태영 wrote:











Thanks

 

Anyway I solve this issue with GRC 37111

 

Regards

Kim taeyeong

 



Original Message

Subject : Re: Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows

Date : 2017-08-09 00:17:28

From : Geof Nieboer 

To : 김태영 

Cc : Geof Nieboer ,
"Discuss-gnuradio@gnuorg" 


Kim,
 

Ok, I'm feeling somewhat confident that this is a unicode or slash issue
The character you said is your path separator appears in my email client as
a W with a horizontal line through it, but when I cut/pasted that character,
it became a back slash Interesting

 

But I think that fact it ends up as a back slash is the more important part,
So try using forward slashes instead of back slashes as a workaround
It's possible the file path parser is treating the back slash as a
character escape in Windows python, which might indicate why \\badbin
doesn't work but \\goodbin does, since \\b is a backspace escape
character

 

I will take a closer look later on, but try that to keep moving forward

 

Geof


 
On Tue, Aug 8, 2017 at 2:35 AM, 김태영  wrote:












Geof

 

'goodbin' exist and no 'badbin'

The separator is \\ I confirm that by selecting some file on file sink block
file menu

How can I check if any unicode?

 

Regards

Kim taeyeong

 



Original Message

Subject : Re: [Discuss-gnuradio] FW: Re: File sink permission error on
Windows

Date : 2017-08-08 12:30:52

From : Geof Nieboer 

To : 김태영 

Cc : "Discuss-gnuradio@gnuorg" 


Kim, 

 
 

That's a very odd error Can you confirm that neither goodbin or badbin
existed in that folder? Are there any unicode characters in the filename?
Your path separators were copied as \\ Can you confirm which direction
slashes you were using?
 

 
 

Geof
 



 
On Mon, Aug 7, 2017 at 11:16 PM, 김태영  wrote:












Thanks

 

But I still have problem Some file name works good, but not the another

 

For ex 'C:\\Work\\GRC_Work\\goodbin' whithout error,

But 'C:\\Work\\GRC_Work\\badbin' fail

 

It looks like some kind of bug

 

 

Regards

Kim taeyeong

 



Original Message

Subject : Re: [Discuss-gnuradio] File sink permission error on Windows

Date : 2017-08-07 17:17:57

From : Marcus Müller 

To : 

Cc :




Hi Kim,

 

can you try to select an absolute file name rather then just
"newbin", in a directory that you definitely can generate new
files in?

To me, this looks like the reason really is that you're not allowed to
create or write to newbin

 

Best regards,

Marcus
 

On 08/07/2017 09:31 AM, 김태영 wrote:











Hi all

 

When I test file sink block on Windows 10 platform, I got permission error
GRC version is 3792

This flowgraph works well on Ubuntu environment

How can I overcome this issue

 

One more issue is the deference before "Stream to tagged stream"
and after

I want to know what this block meaning

 

 

Regards

Kim taeyeong

 

 

 Error message 


Executing: C:\\Program Files\\GNURadio-37\\gr-python27\\pythonexe -u
C:\\Work\\GRC_Work\\file_sinkpy

Using Volk machine: avx2
newbin: Permission denied
Traceback (most recent call last):
 File "C:\\Work\\GRC_Work\\file_sinkpy", line 82, in

 main()
 File "C:\\Work\\GRC_Work\\file_sinkpy", line 76, in main
 tb = top_block_cls()
 File "C:\\Work\\GRC_Work\\file_sinkpy", line 37, in __init__
 selfblocks_file_sink_0_1 = blocksfile_sink(grsizeof_int*1,
"newbin", False)
 File "C:\\Program
Files\\GNURadio-37\\lib\\site-packages\\gnuradio\\blocks\\blocks_swig0py&qu
ot;,
line 1016, in make
 return _blocks_swig0file_sink_make(itemsize, filename, append)
RuntimeError: can't open file

 

 
 


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnuorg
https://listsgnuorg/mailman/listinfo/discuss-gnuradio





 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnuorg
https://listsgnuorg/mailman/listinfo/discuss-gnuradio
 






 







 

 

 
 


___

[Discuss-gnuradio] Bits inserted at random places

[李博远]

Hi,

I have implemented BPSK and OFDM in GNURadio. They are modified from the
examples given, just without those crc32 modules. They work well in
GNURadio.

However, when I test the programs on the hardware, USRP x310, a problem
emerges. I found that often than not, there are some extra bits in my data
stream at random locations, even when the SNR is as high as 20dB. This
messes up the data alignment, and makes it difficult to calculate the
BER(bit error rate). This problem exists in both BPSK and OFDM.

Can anyone share his/her opinion on this please? What may be the cause?
What can I do to mitigate it? It has bothered me for a long time.

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

Re: [Discuss-gnuradio] diagnosing overflows

[Philip Hahn]

Sean - OK, I understand what you mean now, thank you - the overflow is not
reported until the pressure hits the source block.
Cinaed - In this case it is not my flowgraph but gnss-sdr which I've run
successfully on several platforms. In this case it is running on a
Raspberry Pi 3. I anticipate hitting some roadblocks although reportedly
it's been done before; I am trying to determine the current bottleneck.

thanks

philip

On Wed, Aug 9, 2017 at 3:15 PM, Cinaed Simson 
wrote:

> On 08/08/2017 07:56 PM, Philip Hahn wrote:
> > Folks,
> >
> >  Is there a way to diagnose which block first reports an overflow in a
> > flowgraph?
> >
> >  In my particular instance I am running a flowgraph which is overflowing
> > without pegging either RAM or CPU.
>
> It could also be an error in the plumbing of your flowgraph.
>
> -- Cinaed
>
>
>
> >
> >  Thank you,
> >
> > philip
> >
> >
> > ___
> > 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] diagnosing overflows

[Cinaed Simson]

On 08/08/2017 07:56 PM, Philip Hahn wrote:
> Folks,
> 
>  Is there a way to diagnose which block first reports an overflow in a
> flowgraph? 
> 
>  In my particular instance I am running a flowgraph which is overflowing
> without pegging either RAM or CPU. 

It could also be an error in the plumbing of your flowgraph.

-- Cinaed



> 
>  Thank you,
> 
> philip
> 
> 
> ___
> 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] Explanation on how the preamble is inserted and how the packet is detected

[李博远]

Hi Adhitha,

If you check out the tx_stage6.grc example in the folder
/src/gnuradio/gr-digital/example/packet/, you can see a Protocol Formatter.
It generates a header which contains a preamble and some additional
information, and pumps it out through the header output port.  The other
output port, called payload, outputs the original information from the
signal source. And there is another module called Tagged Stream Mux. It
combines the header and the payload, producing a packet.

As for the receiver, check out the packet_rx.grc. The Correlation
Estimation correlates the received signal with the modulated preamble and
finds out the beginning of each packet. The Header/Payload Demux splits the
header from the payload.

Hope this answers your question.

Regards,
Edwin

Adhitha Dias 于2017年8月9日周三 上午5:34写道：

> Hi Edwin,
>
> I tried the examples but there is no information on how to detect the
> preamble. What I need to do is, once the Short Training Field is identified
> record the packet so that I can use the Long Training Field can be used for
> processing.
>
> I've been looking in to the examples for a couple of days but I still
> don't have an idea on how the preamble is inserted and how to detect the
> Short Training Field in order to record the un-modulated, raw, time domain
> received signal.
>
> I really appreciate if you can kindly provide some information on this.
>
> Thanks a lot!
> Regards,
> Adhitha Dias
>
> On 9 Aug 2017 00:12, "李博远"  wrote:
>
>> Hi Adhitha,
>>
>> Just check out the examples in the folder
>> /src/gnuradio/gr-digital/examples/packet/
>>
>> Regards,
>> Edwin
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Encryption

[Marcus Müller]

Hi Ricardo,

the "Comprehensive GNU Radio Archive Network", cgran.org, is your friend :)

When you look for "encryption" there, you'll find gr-nacl (thanks to its 
author, Stefan Wunsch). It uses the rather established NaCl library; it 
should cover your cryptographic needs!


Best regards,

Marcus


On 08/09/2017 05:21 PM, Ricardo Nuszkowski wrote:

Hello,

I am building a ground station for my university and we are going to be using a 
LimeSDR and GNU radio. I was wondering what type of encryption is available 
with GNU radio. We were looking to see if it handles AES 256 or NSA type 1 
encryption.

Respectfully,

Ricardo
___
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] Encryption

[Ricardo Nuszkowski]

Hello,

I am building a ground station for my university and we are going to be using a 
LimeSDR and GNU radio. I was wondering what type of encryption is available 
with GNU radio. We were looking to see if it handles AES 256 or NSA type 1 
encryption.

Respectfully,

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