Keyboard Shortcuts
Likes
Search
Re: Tips on interfacing I/Q data into quisk?
¿ªÔÆÌåÓý
Hi Chuck,
Yes, this would be a nice way to do it, where the difficulty was on the MCU end.? I thought about it a bit and did a little research.? My major problem is that I was planning to use the UART to control the SDR and have that all working with Quisk using the
UART.? I'm not even sure it is possible to get the Raspberry Pi Pico I'm using to simultaneously use the USB UART and be a USB soundcard. Do you have a good solution for this problem of control and audio simultaneously?
Thanks for the warning on the UART glitches.? If I pursue this, I need to make sure they don't happen for me before pursuing it.? I also do not like the non-standard interface to SDR software.? Another way I am considering doing it is to write a
?using the UART approach.? ? ?That overcomes the nonstandard problem, but might not be as easy as a simple hack to inject the sound data into Quisk.
?73,
Rob
-- KL7NA From: [email protected] <[email protected]> on behalf of Chuck Ritola via groups.io <cjritola@...>
Sent: Tuesday, December 19, 2023 10:40 AM To: [email protected] <[email protected]> Subject: Re: [n2adr-sdr] Tips on interfacing I/Q data into quisk? ?
CAUTION: This email originated from outside the Walla Walla University email system.
It might be wise to try having the Pico emulate a USB audio device and send its samples that way. Then no modification on the user's part need be done. There are a few examples of this. The work is not trivial:
USB Audio device emulation for a "USB microphone":
USB HID emulation examples:
A design to look at is the FUNCube Dongle series of SDRs, which emulated a stereo-input USB audio interface for the I/Q samples and a USB Human Interface Device for controlling the tuner, amplifiers, etc using a PIC32MX. Bandwidth limitations of USB 1.x
were worked around by dropping the least-significant-byte of 24-bit samples so they are 16-bit. They turned out to work well. The Pico may be up to such a task.
What you are proposing is only different from a soundcard by name, with a proprietary communication format which will require modification of /every/ piece of software to use it directly, or at the least would require installation of supplementary software
on the user's machine to make it compatible with existing SDR software. I've noticed odd irregularities in data rate when transferring constant data streams over UART, even when wrapped in USB.
The complexity of creating a stream format in UART, then modifying existing software to work with it, will likely exceed writing USB firmware on the pico. From an educational POV, learning how to make a USB device could prove quite valuable.
The Pico also has onboard ADCs which have 12 bits resolution. If that's good enough, that's another part removed from the schematic. Supposedly it takes 96 cycles to process each sample:
There are tricks with 4x oversampling, lowpass filtering, and decimating to add 1 ENOB to the resolution (repeat for more) but it is unclear if the pico can muscle it and juggle USB traffic at the same time. I wouldn't bother with that, because the bandwidth-limiting
filters used in SDR software perform something mathematically similar to this task anyway.
On Mon, Dec 18, 2023 at 6:52?PM Nigel Johnson MIEEE via
<nw.johnson=[email protected]> wrote:
|