Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for JupiterSDR #1766

Closed
wants to merge 5 commits into from
Closed

Add support for JupiterSDR #1766

wants to merge 5 commits into from

Conversation

catkira
Copy link
Contributor

@catkira catkira commented Aug 8, 2023

@catkira catkira marked this pull request as draft August 8, 2023 12:39
@catkira
Copy link
Contributor Author

catkira commented Aug 8, 2023

@f4exb It still takes some more commits to get this working. I just created this PR already so that You can give early feedback.

I will try to get rx running first and then do tx.

@f4exb
Copy link
Owner

f4exb commented Aug 8, 2023

Looks like a nice SDR. Since it is a transceiver and has two synchronized inputs and outputs it may be better supported as a "mimo" device. I see it uses libiio and you probably got inspiration from PlutoSDR. Input and Output device plugin for the same device is the way of support prior to the "mimo" devices implementation. PlutoSDR has the 3 flavors of support: input, output and mimo.

@catkira
Copy link
Contributor Author

catkira commented Aug 8, 2023

ah thanks, I will have a look at the pluto MIMO device.

@github-actions
Copy link

This PR is going to be closed due to inactivity

@catkira
Copy link
Contributor Author

catkira commented Sep 21, 2023

the inactivity is unfortunately caused by ADI, because with the ADRV its not possible anymore to change the sample rate by just writing an iio attribute. With these devices one has to upload a binary blob (so called profile) that contains configured settings such as sample rate. ADI said they want to open source the code to generate the binary blob, but so far it has not been done.

@f4exb
Copy link
Owner

f4exb commented Oct 2, 2023

The "feature" label should take this PR out of the no activity scope

@f4exb
Copy link
Owner

f4exb commented Oct 2, 2023

I had a quick look at the documentation and what they call "profiles". This looks like part of the device firmware from the software point of view so there is no point in trying top change these parameters from software. However it is necessary to be able to read essential parameters like the sample rate. I did not go that far to know if this is possible but I would hope so.

Copy link

This PR is going to be closed due to inactivity

Copy link

This PR is going to be closed due to inactivity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants