Hello LJ Eads: There are some tutorials that will help you get started with GNU Radio.
https://kb.ettus.com/Suggested_Videos The UHD USRP Source and UHD USRP Sink blocks in GNU Radio represent your X300/X310 radio. The source block is for receiving samples, and the sink block is for transmitting samples. Which 10 Giagbit Ethernet card are you using? The Intel X520-DA2, X540-DA2, and X710-DA2 cards work very reliably under Ubuntu 16.04.4. Please let me know if you have any further questions. --Neel Pandeya 408-610-6370 On 2 May 2018 at 05:14, Eads, LJ D. via USRP-users < usrp-users@lists.ettus.com> wrote: > Hello, > > I just setup a X310 that I plan on using with GNURadio over 10 gigabit.. I > have everything working and functioning properly (drivers and all) but my > only concern right now is that GNURadio is running off of the sound card on > my server and not the GPU. GNURadio isn't able to handle practically > anything because I am limited by the sound card capability. > > How would I be able to use the CPU (Sixteen-Core Intel Xeon Processor > E5-2683 v4 2.10GHz 40MB Cache (120W)) or the GPU (NVIDIA Tesla K80 GPU > Computing Accelerator - 24GB GDDR5 - Passive Cooler) for better > functionality of the X310? > > Thank you, > > LJ Eads > > > -----Original Message----- > From: USRP-users [mailto:usrp-users-boun...@lists.ettus.com] On Behalf Of > usrp-users-requ...@lists.ettus.com > Sent: Tuesday, May 1, 2018 12:00 PM > To: usrp-users@lists.ettus.com > Subject: USRP-users Digest, Vol 93, Issue 1 > > Send USRP-users mailing list submissions to > usrp-users@lists.ettus.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > or, via email, send a message with subject or body 'help' to > usrp-users-requ...@lists.ettus.com > > You can reach the person managing the list at > usrp-users-ow...@lists.ettus.com > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of USRP-users digest..." > > > Today's Topics: > > 1. Fwd: USRP No antenna port listed (Daniel Guarecuco) > 2. Re: Fwd: USRP No antenna port listed (Marcus D. Leech) > 3. Re: New (soon) owner question (USB3 over Ethernet) (Marcus M?ller) > 4. Turbo Product Codes on USRP E312 (Ronakraj Gosalia) > 5. How to define FIR RFnoc block with float taps (Allouche Ishai) > 6. Re: How to define FIR RFnoc block with float taps (Marcus M?ller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 30 Apr 2018 14:54:17 -0400 > From: Daniel Guarecuco <daniel.guarec...@gmail.com> > To: usrp-users@lists.ettus.com > Subject: [USRP-users] Fwd: USRP No antenna port listed > Message-ID: > <CAE3AEx3zkme_ydjDieowKxwYfgdX3GhLUcBZXFiP2M > xzbjq...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > I have an USRP1 with a BasicTX and a BasicRX. > I have been trying to receive data with no luck, it seems there is a > problem with the antenna port. > I run uhd_usrp_probe.exe and this is what I get: > > C:\Program Files\UHD\bin>uhd_usrp_probe > [INFO] [UHD] Win32; Microsoft Visual C++ version 14.0; Boost_105900; > UHD_3.11.0. > 0-release > [INFO] [NIRIO] rpc_client stopping... > [INFO] [NIRIO] rpc_client stopped. > [ERROR] [UHD] Device discovery error: input stream error [INFO] [USRP1] > Opening a USRP1 device... > [INFO] [USRP1] Using FPGA clock rate of 64.000000MHz... > _____________________________________________________ > / > | Device: USRP1 Device > | _____________________________________________________ > | / > | | Mboard: USRP1 > | | serial: 480f888c > | | name: USRP_ettus > | | > | | Time sources: none > | | Clock sources: internal > | | Sensors: > | | _____________________________________________________ > | | / > | | | RX DSP: 0 > | | | > | | | Freq range: -32.000 to 32.000 MHz > | | _____________________________________________________ > | | / > | | | RX DSP: 1 > | | | > | | | Freq range: -32.000 to 32.000 MHz > | | _____________________________________________________ > | | / > | | | RX Dboard: A > | | | ID: Basic RX (0x0001) > | | | _____________________________________________________ > | | | / > | | | | RX Frontend: AB > | | | | Name: BasicRX (AB) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > | | | | Connection Type: IQ > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | RX Frontend: BA > | | | | Name: BasicRX (BA) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > | | | | Connection Type: QI > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | RX Frontend: A > | | | | Name: BasicRX (A) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > | | | | Connection Type: I > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | RX Frontend: B > | | | | Name: BasicRX (B) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > | | | | Connection Type: Q > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | RX Codec: A > | | | | Name: ad9522 > | | | | Gain range pga: 0.0 to 20.0 step 1.0 dB > | | _____________________________________________________ > | | / > | | | RX Dboard: B > | | | _____________________________________________________ > | | | / > | | | | RX Frontend: 0 > | | | | Name: Unknown (0xffff) - 0 > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: 0.000 to 0.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz > | | | | Connection Type: IQ > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | RX Codec: B > | | | | Name: ad9522 > | | | | Gain range pga: 0.0 to 20.0 step 1.0 dB > | | _____________________________________________________ > | | / > | | | TX DSP: 0 > | | | > | | | Freq range: -44.000 to 44.000 MHz > | | _____________________________________________________ > | | / > | | | TX DSP: 1 > | | | > | | | Freq range: -44.000 to 44.000 MHz > | | _____________________________________________________ > | | / > | | | TX Dboard: A > | | | ID: Basic TX (0x0000) > | | | _____________________________________________________ > | | | / > | | | | TX Frontend: AB > | | | | Name: BasicTX (AB) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > | | | | Connection Type: IQ > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | TX Frontend: BA > | | | | Name: BasicTX (BA) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > | | | | Connection Type: QI > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | TX Frontend: A > | | | | Name: BasicTX (A) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > | | | | Connection Type: I > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | TX Frontend: B > | | | | Name: BasicTX (B) > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: -250.000 to 250.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > | | | | Connection Type: Q > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | TX Codec: A > | | | | Name: ad9522 > | | | | Gain range pga: -20.0 to 0.0 step 0.1 dB > | | _____________________________________________________ > | | / > | | | TX Dboard: B > | | | _____________________________________________________ > | | | / > | | | | TX Frontend: 0 > | | | | Name: Unknown (0xffff) - 0 > | | | | Antennas: > | | | | Sensors: > | | | | Freq range: 0.000 to 0.000 MHz > | | | | Gain Elements: None > | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz > | | | | Connection Type: IQ > | | | | Uses LO offset: No > | | | _____________________________________________________ > | | | / > | | | | TX Codec: B > | | | | Name: ad9522 > | | | | Gain range pga: -20.0 to 0.0 step 0.1 dB > > > > > There is no antenna listed. Is this a firmware or hardware problem? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.ettus.com/pipermail/usrp-users_lists. > ettus.com/attachments/20180430/016b24c5/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Mon, 30 Apr 2018 16:09:22 -0400 > From: "Marcus D. Leech" <mle...@ripnet.com> > To: usrp-users@lists.ettus.com > Subject: Re: [USRP-users] Fwd: USRP No antenna port listed > Message-ID: <5ae777f2.3010...@ripnet.com> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > On 04/30/2018 02:54 PM, Daniel Guarecuco via USRP-users wrote: > > Hi, > > I have an USRP1 with a BasicTX and a BasicRX. > > I have been trying to receive data with no luck, it seems there is a > > problem with the antenna port. > > I run uhd_usrp_probe.exe and this is what I get: > > > > C:\Program Files\UHD\bin>uhd_usrp_probe [INFO] [UHD] Win32; Microsoft > > Visual C++ version 14.0; Boost_105900; UHD_3.11.0. > > 0-release > > [INFO] [NIRIO] rpc_client stopping... > > [INFO] [NIRIO] rpc_client stopped. > > [ERROR] [UHD] Device discovery error: input stream error [INFO] > > [USRP1] Opening a USRP1 device... > > [INFO] [USRP1] Using FPGA clock rate of 64.000000MHz... > > _____________________________________________________ > > / > > | Device: USRP1 Device > > | _____________________________________________________ > > | / > > | | Mboard: USRP1 > > | | serial: 480f888c > > | | name: USRP_ettus > > | | > > | | Time sources: none > > | | Clock sources: internal > > | | Sensors: > > | | _____________________________________________________ > > | | / > > | | | RX DSP: 0 > > | | | > > | | | Freq range: -32.000 to 32.000 MHz > > | | _____________________________________________________ > > | | / > > | | | RX DSP: 1 > > | | | > > | | | Freq range: -32.000 to 32.000 MHz > > | | _____________________________________________________ > > | | / > > | | | RX Dboard: A > > | | | ID: Basic RX (0x0001) > > | | | _____________________________________________________ > > | | | / > > | | | | RX Frontend: AB > > | | | | Name: BasicRX (AB) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > > | | | | Connection Type: IQ > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | RX Frontend: BA > > | | | | Name: BasicRX (BA) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > > | | | | Connection Type: QI > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | RX Frontend: A > > | | | | Name: BasicRX (A) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > > | | | | Connection Type: I > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | RX Frontend: B > > | | | | Name: BasicRX (B) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > > | | | | Connection Type: Q > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | RX Codec: A > > | | | | Name: ad9522 > > | | | | Gain range pga: 0.0 to 20.0 step 1.0 dB > > | | _____________________________________________________ > > | | / > > | | | RX Dboard: B > > | | | _____________________________________________________ > > | | | / > > | | | | RX Frontend: 0 > > | | | | Name: Unknown (0xffff) - 0 > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: 0.000 to 0.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz > > | | | | Connection Type: IQ > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | RX Codec: B > > | | | | Name: ad9522 > > | | | | Gain range pga: 0.0 to 20.0 step 1.0 dB > > | | _____________________________________________________ > > | | / > > | | | TX DSP: 0 > > | | | > > | | | Freq range: -44.000 to 44.000 MHz > > | | _____________________________________________________ > > | | / > > | | | TX DSP: 1 > > | | | > > | | | Freq range: -44.000 to 44.000 MHz > > | | _____________________________________________________ > > | | / > > | | | TX Dboard: A > > | | | ID: Basic TX (0x0000) > > | | | _____________________________________________________ > > | | | / > > | | | | TX Frontend: AB > > | | | | Name: BasicTX (AB) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > > | | | | Connection Type: IQ > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | TX Frontend: BA > > | | | | Name: BasicTX (BA) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 500000000.0 to 500000000.0 step 0.0 Hz > > | | | | Connection Type: QI > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | TX Frontend: A > > | | | | Name: BasicTX (A) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > > | | | | Connection Type: I > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | TX Frontend: B > > | | | | Name: BasicTX (B) > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: -250.000 to 250.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 250000000.0 to 250000000.0 step 0.0 Hz > > | | | | Connection Type: Q > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | TX Codec: A > > | | | | Name: ad9522 > > | | | | Gain range pga: -20.0 to 0.0 step 0.1 dB > > | | _____________________________________________________ > > | | / > > | | | TX Dboard: B > > | | | _____________________________________________________ > > | | | / > > | | | | TX Frontend: 0 > > | | | | Name: Unknown (0xffff) - 0 > > | | | | Antennas: > > | | | | Sensors: > > | | | | Freq range: 0.000 to 0.000 MHz > > | | | | Gain Elements: None > > | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz > > | | | | Connection Type: IQ > > | | | | Uses LO offset: No > > | | | _____________________________________________________ > > | | | / > > | | | | TX Codec: B > > | | | | Name: ad9522 > > | | | | Gain range pga: -20.0 to 0.0 step 0.1 dB > > > > > > > > > > There is no antenna listed. Is this a firmware or hardware problem? > > > There isn't a problem. The BASIC_RX doesn't have switchable antennas. > > There are two distinct parameters involved. One describes the signal > chain via the subdevice specification, and the other describes any > switchable antenna > ports available on that connection. In the case of BASIC_*, there are > no switchable antenna connections--in fact that is true for some other > boards > as well. > > https://files.ettus.com/manual/page_dboards.html#dboards_basicrx > > Instead, on the BASIC_RX, you'd use the subdevice spec to tell the > hardware what you're interested in. > > For the "A" side of your USRP1: > > A:A A:B A:AB A:BA > > Are all plausible > > For the "B" side: > > B:A B:B B:AB B:BA > > Are all plausible for your subdev spec. > > What I don't recall is whether there are enough DDC resources in the > USRP1 to support all 4 input as separate real-mode streams. I think you > need > to specific the usrp1_fpga_4rx.rbf FPGA image when you instantiate the > device (via the fpga= argument), and that image precludes the use > of TX at all (because there aren't enough resources in the FPGA to > support TX when you have 4 DDC channels). > > The USRP1 is now obsolete, and no new work is being done on it. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.ettus.com/pipermail/usrp-users_lists. > ettus.com/attachments/20180430/54c961de/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Mon, 30 Apr 2018 23:32:41 +0200 > From: Marcus M?ller <marcus.muel...@ettus.com> > To: Brian Gieryk <ke6...@mac.com> > Cc: usrp-users <usrp-users@lists.ettus.com> > Subject: Re: [USRP-users] New (soon) owner question (USB3 over > Ethernet) > Message-ID: <1525123961.20313.84.ca...@ettus.com> > Content-Type: text/plain; charset="UTF-8" > > Ah! The situation is different then! > Chances are that the same bandwidth will still fit through USB2, and since > USB3 is backwards compatible: You don't even have a problem :) Just connect > your B200 as you did your HackRF. > > Note that full-duplex might need more USB bandwidth than half, but I guess > the easiest way to figure that out is to try :) > > Best regards, > Marcus > > On Sun, 2018-04-29 at 16:44 -0600, Brian Gieryk wrote: > > I am currently running a HackRF on a Pi 3B, doing multi frequency NBFM > > RX, VHF-Hi and UHF (monitoring multiple frequencies on large fires). > > > > Would like a single radio solution (HackRF can not be both source and > > sink in GNUradio, so 2 boxes must be used). > > > > Brian > > KE6IYC > > > > > > Sent from my iPhone > > > > > On Apr 29, 2018, at 16:14, Marcus M?ller <marcus.muel...@ettus.com> > > > wrote: > > > > > > Hi Brian! > > > > > > It probably won't work great: since USB and ethernet are > > > fundamentally different, the round-trip delay won't be of any fun, > > > and I really don't see why you should spend your money on a > > > network-connected USB3 hub (wasn't even aware something like that > > > existed!) to couple a computer with USB2 to a USB3 device. > > > > > > You should really directly opt for a computer with a USB3 port. > > > Also, > > > Software Defined Radio at rates that require USB3 (instead of only > > > USB2, since you can also use USB2 if your sampling rates are below > > > ca > > > 10 MS/s) usually means a high CPU demand ? not sure that the Pi3 is > > > the universally best choice here. (I want so say that: very likely > > > it's > > > not.) > > > > > > So, to be honest: simply start with a decent desktop or laptop PC, > > > preferably running Linux; you might already be using one, so this is > > > a zero cost option initially. Whatever you design there can (unless > > > you do something architecture-specific) be ported to an ARM like > > > that in the Pi easily (if necessary at all), but you're not subject > > > to the computational limitations of the Pi while you design your > > > system. > > > When > > > you've shown it works, you can try to make it work on a Pi - > > > optimize the things that are bottlenecks and so on. > > > > > > But: you surely wouldn't be considering the Pi up front if you > > > didn't have an application for such a device: What are you working > > > on? Can we help you with feedback, suggestions or just > > > encouragement? > > > > > > Best regards, > > > Marcus > > > > > > > On Sun, 2018-04-29 at 15:54 -0600, Brian Gieryk via USRP-users > > > > wrote: > > > > Forgive me, please, if this has been asked before, but I find no > > > > way to search the archives. > > > > > > > > I am currently shopping for a B200/B200 mini for experimenting. > > > > > > > > I will be using a Raspberry Pi 3B+ (gigabit Ethernet), GNUradio, > > > > and am wondering if anyone has used/tried network attached USB > > > > hubs to use a USB3 device with a computer that only has USB2 > > > > ports? > > > > > > > > Good bad or indifferent, does it work? > > > > > > > > Thank you in advance, > > > > > > > > Brian > > > > KE6IYC > > > > > > > > > > > > > > > > Sent from my iPhone > > > > _______________________________________________ > > > > USRP-users mailing list > > > > USRP-users@lists.ettus.com > > > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.co > > > > m > > > > ------------------------------ > > Message: 4 > Date: Tue, 1 May 2018 22:13:49 +1000 > From: Ronakraj Gosalia <mastergosa...@gmail.com> > To: usrp-users <usrp-users@lists.ettus.com> > Subject: [USRP-users] Turbo Product Codes on USRP E312 > Message-ID: > <CAKy6aSAh97A4J-g=ksNdAMQJ3n1uKn6QnJojdw_x8S1hOhzCMw@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi everyone, > > I am using a USRP E312 with GNU Radio 3.7.10.2. GNU Radio has an inbuilt > FEC block that supports Turbo Product Codes (TPC). I'm trying to run a > flowgraph (completely in simulation) on the E312 that includes a TPC > encoder and decoder. The TPC parameters are: > > parallelism: 0 > row encoding polynomial: 3 > column encoding polynomial: 123 > K Row: 3 > K Column: 18 > B: 0 > Q: 6 > > This is a standard 1/2 rate TPC with 6 data byte frame and 12 coded byte > frame as per slide 6 on https://kirankarra.files. > wordpress.com/2016/01/sep18_02_karra_turbocodes.pdf. > On my host machine running Ubuntu 16.04 LTS the flowgraph simulates as > expected and my ASYNC FEC encoding and decoding blocks with TPC work and > decode properly. I copied across the exact same flowgraph to my E312 and > ran it on there, but the decoded bits that come out of the FEC Decoder > (diagnosed using a Message Debug block) are all 0s. It's as if the TPC > decoder has not attempted to decode at all and prints out the default > initialised vector of 0s. I tried all types of TPC decoding including > LOG-MAP C factor, LOG-MAP LUT factor, Constant LOG-MAP, max LOG-MAP and > Linear LOG-MAP with various levels of iterations from 1-6. All yielded the > same response. I even tried to use a ZMQ push/pull sink/source and > offloaded the FEC decoding to my host machine while everything else leading > up to it was done on the E312 - this works perfectly and the FEC decoding > performs as expected on my host laptop. > > I suspect there's a subtle bit of code that is malfunctioning on the E312, > but there's no diagnosis output that hint at where this may be. For > reference, I followed the instructions here https://kb.ettus.com/Software_ > Development_on_the_E3xx_USRP_-_Building_RFNoC_UHD_/_GNU_ > Radio_/_gr-ettus_from_Source > to setup my E312. I have not faced an issue like this before with any > other block either in tree or out of tree. > > Has anyone experienced an issue like this before or know where I should > look? > Thank you for reading and for your help in advance :). > > Kind Regards, > > Ronakraj > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.ettus.com/pipermail/usrp-users_lists. > ettus.com/attachments/20180501/ba3b2a6c/attachment-0001.html> > > ------------------------------ > > Message: 5 > Date: Tue, 1 May 2018 14:31:37 +0000 > From: Allouche Ishai <ishai.allou...@elbitsystems.com> > To: "usrp-users@lists.ettus.com" <usrp-users@lists.ettus.com> > Subject: [USRP-users] How to define FIR RFnoc block with float taps > Message-ID: > <0bf926169829cd4899242577bc25e30414ea7...@mxbnb02.esl.corp. > elbit.co.il> > > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I try to use the FIR filter and define the taps to be float number, but > the problem is that the taps must to be integer number. > > Can someone please help me how solve this issue. > > Thanks in advance > Ishai > > > The information in this e-mail transmission contains proprietary and > business sensitive information. Unauthorized interception of this e-mail > may constitute a violation of law. If you are not the intended recipient, > you are hereby notified that any review, dissemination, distribution or > duplication of this communication is strictly prohibited. You are also > asked to contact the sender by reply email and immediately destroy all > copies of the original message. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.ettus.com/pipermail/usrp-users_lists. > ettus.com/attachments/20180501/d4e50692/attachment-0001.html> > > ------------------------------ > > Message: 6 > Date: Tue, 01 May 2018 16:59:29 +0200 > From: Marcus M?ller <marcus.muel...@ettus.com> > To: Allouche Ishai <ishai.allou...@elbitsystems.com>, > "usrp-users@lists.ettus.com" <usrp-users@lists.ettus.com> > Subject: Re: [USRP-users] How to define FIR RFnoc block with float > taps > Message-ID: <1525186769.20313.88.ca...@ettus.com> > Content-Type: text/plain; charset="UTF-8" > > Dear Ishai, > > convert the taps to integers. This typically involves scaling with a power > of two (pick one that would allow the matching signal to stay within > numerical limits of your internal stream format) and rounding. > No magic involved here :) > > Best regards, > Marcus > On Tue, 2018-05-01 at 14:31 +0000, Allouche Ishai via USRP-users wrote: > > Hi all, > > > > I try to use the FIR filter and define the taps to be float number, > > but the problem is that the taps must to be integer number. > > > > Can someone please help me how solve this issue. > > > > Thanks in advance > > Ishai > > > > > > The information in this e-mail transmission contains proprietary and > > business sensitive information. Unauthorized interception of this > > e-mail may constitute a violation of law. If you are not the intended > > recipient, you are hereby notified that any review, dissemination, > > distribution or duplication of this communication is strictly > > prohibited. You are also asked to contact the sender by reply email > > and immediately destroy all copies of the original message. > > _______________________________________________ > > USRP-users mailing list > > USRP-users@lists.ettus.com > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > ------------------------------ > > End of USRP-users Digest, Vol 93, Issue 1 > ***************************************** > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
