# Burst detector files **URL:** \ **Category:** GNU Radio\ **Created:** [May 1, 2012, 12:09am UTC](https://www.ruby-forum.com/t/burst-detector-files/219370 "2012-05-01T00:09:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Gurdipe\_D](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/b77776/32.png) [@Gurdipe\_D](https://www.ruby-forum.com/u/Gurdipe_D)\ **Post date:** [May 1, 2012, 12:09am UTC](https://www.ruby-forum.com/t/burst-detector-files/219370/1 "2012-05-01T00:09:12Z")
I am working with the uhd\_burst\_detector examples. I ran it for 0.5 second (using sleep) and was able to generate files using the internal trigger. It generates the correct number of files with the correct time stamps given the internal trigger waveform. I tried to read the file using the read\_complex\_binary.m file and was able to get 1000 data points, but the values were all very small (see the 1st 10 values below). Am I reading them correctly? 1.0e-003 \* -0.0916 - 0.1831i 0.0916 -0.2136 + 0.0610i -0.1221 + 0.1526i 0 + 0.2136i -0.0916 + 0.0916i 0.1831 - 0.0610i 0.1526 -0.0916 - 0.2136i -0.0305 + 0.0305i ## Thanks, Eugene Lee View this message in context: [http://old.nabble.com/burst-detector-files-tp33763321p33763321.html](http://old.nabble.com/burst-detector-files-tp33763321p33763321.html) Sent from the GnuRadio mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![Eugene\_Lee](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/ea666f/32.png) [@Eugene\_Lee](https://www.ruby-forum.com/u/Eugene_Lee)\ **Post date:** [May 1, 2012, 4:37pm UTC](https://www.ruby-forum.com/t/burst-detector-files/219370/2 "2012-05-01T16:37:46Z")
On Mon, Apr 30, 2012 at 6:08 PM, Eugene Lee [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 1.0e-003 \* > > -0.0916 - 0.1831i Eugene, That’s actually not a very weak signal. Convert it into dBm and see what it’s power is. When working with real signals over the air, you have to get used to working with small numbers. Tom ---
**Author:** ![Eugene\_Lee](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/ea666f/32.png) [@Eugene\_Lee](https://www.ruby-forum.com/u/Eugene_Lee)\ **Post date:** [May 1, 2012, 5:15pm UTC](https://www.ruby-forum.com/t/burst-detector-files/219370/3 "2012-05-01T17:15:40Z")
I understand, it turns out I misread how the flow graph routed the vector source. I thought that the internal trigger was flowing in as a source rather than the RF threshold. Thanks for the help.