Re: Writing Drivers for Custom Hardware

Hi all, Following up on a thread from last year. After trying multiple approaches, I finally spent some time figuring out how to write a GnuRadio OOT module. My code is here . In the OOT, I took the approach of having a separate thread usin

Re: Writing Drivers for Custom Hardware

That'd be probably versions shortly before 3.4.2 or so On 13.07.24 21:02, Marcus D. Leech wrote: On 13/07/2024 12:55, Ian Buckley wrote: As an aside…. I wonder if the original USRP2 transport code is still captured in the public domain. This used a proprietary Ethernet transport for IQ before w

RE: Writing Drivers for Custom Hardware

> Message: 6 > Date: Sat, 13 Jul 2024 16:32:46 +0200 > From: Marcus Müller > To: discuss-gnuradio@gnu.org > Subject: Re: Writing Drivers for Custom Hardware > Message-ID: <3aeb60bd-5e7e-4cff-a8da-094f62b2b...@gnuradio.org> > Content-Type: text/plain; charset=UTF-8; format=f

Re: Writing Drivers for Custom Hardware

On 13/07/2024 12:55, Ian Buckley wrote: As an aside…. I wonder if the original USRP2 transport code is still captured in the public domain. This used a proprietary Ethernet transport for IQ before we switched to UDP in UHD transport. I think that was part of GnuRadio at the time, so pulling a v

Re: Writing Drivers for Custom Hardware

As an aside…. I wonder if the original USRP2 transport code is still captured in the public domain. This used a proprietary Ethernet transport for IQ before we switched to UDP in UHD transport. Sent from my iPhone > On Jul 13, 2024, at 7:33 AM, Marcus Müller wrote: > > Hi Walter, > > intere

Re: Writing Drivers for Custom Hardware

Hi Walter, interesting project! The libpcap approach seems to be reasonable; backintheday, I used to capture at Ethernet frame level using socket(PF_PACKET,…), but that's pretty non-portable and comes with its own can of worms. pcap's the way to go there, I'd say, unless you want add a protoco

Re: Writing Drivers for Custom Hardware (GNSS Firehose)

Friends - On Fri, Jul 12, 2024 at 10:09:18PM -0400, Marcus D. Leech wrote: > On 12/07/2024 16:42, Walter Szeliga wrote: > > I have a GNSS Firehose > > https://transitiva.com/product/gnss-firehose-receiver-tri-band-quad-constellation/ > Are these things actually in production?  What kind of price r

Re: Writing Drivers for Custom Hardware

On 12/07/2024 16:42, Walter Szeliga wrote: Hi all,     I have a GNSS Firehose (https://transitiva.com/product/gnss-firehose-receiver-tri-band-quad-constellation/) and have been trying to get it working, in a streaming capacity, with Gnuradio. The Firehose sends packets over ethernet using the

Re: Writing Drivers for Custom Hardware

On 12/07/2024 20:25, Chris Kuethe wrote: I've not played with the ZMQ blocks, but a number of other drivers can operate in network mode, eg. UHD, SoapySDR, and rtlsdr. Since the firehose appears to use 2-bit samples I feel like you could fairly easily convert that into something resembling rtl_

Re: Writing Drivers for Custom Hardware

I've not played with the ZMQ blocks, but a number of other drivers can operate in network mode, eg. UHD, SoapySDR, and rtlsdr. Since the firehose appears to use 2-bit samples I feel like you could fairly easily convert that into something resembling rtl_tcp ( https://github.com/osmocom/rtl-sdr/blob

Writing Drivers for Custom Hardware

Hi all, I have a GNSS Firehose ( https://transitiva.com/product/gnss-firehose-receiver-tri-band-quad-constellation/) and have been trying to get it working, in a streaming capacity, with Gnuradio. The Firehose sends packets over ethernet using the experimental ethertype 0x88b5. I've tried a few