Ever thought about supporting the RF-Explorer? #184
Labels
Comments
|
Sounds good, looking for volunteers with the hardware of course. |
|
I have one, but it's in use. I can help you testing, buy I cannot ship you
mine...
…On Mon, Sep 3, 2018, 18:06 Josh Blum ***@***.***> wrote:
Sounds good, looking for volunteers with the hardware of course.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#184 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEqHE81Gx0Adbf8pl7n69lOBWdND7nCVks5uXVNygaJpZM4WWkbr>
.
|
|
Looking through their products and software, I'm iffy on compatibility. From what I can tell, their SpecAn API only exposes frequency-domain values, and their SigGen API takes in dBm directly. I haven't been able to find any mention of the raw IQ samples Soapy would need to work with. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That would open up a world of possibilities for this device that is heavily used in the music world and RF industry and could make SoapySDR the go-to solution for more advanced use cases.
There is a UART API here: https://github.com/RFExplorer/RFExplorer-for-.NET/wiki/RF-Explorer-UART-API-interface-specification
Device description here: http://j3.rf-explorer.com/
The text was updated successfully, but these errors were encountered: