-
Notifications
You must be signed in to change notification settings - Fork 207
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
Some questions about the hardware configuration #660
Comments
Dear Maxim,
Yes, it's correct.
Normally, all the commands are in the Matlab example.
In the current configuration the second output (OUT2) is already used. It outputs the same signal as the first output (OUT1). It's possible to add an AXI4-Stream switch between the DDS and the DAC and to output various combination of the sine and cosine signals generated by the DDS.
The pins DIO0_P - DIO7_P are already configured as output in the VNA configuration. For the auxiliary DACs, the easiest would be to use a quad I2C DAC (MCP4728 or similar). Best regards, Pavel |
Dear Pavel, Thank you very much for your explanations. I really appreciate your great work. Could you explain how to use the DIO0_P - DIO7_P digital outputs? Maybe you have an Matlab example? Best regards |
The command that controls the digital outputs is in on the lines 36-38 of the Matlab script: |
The code that controls the phase offsets of both outputs is now in the latest release. |
Dear Pavel,
I saw the Matlab example. It is very clear, a very good educational tool. However, I would like to know more about the hardware configuration.
I would also like to make some suggestions:
Could you give a more detailed command list of the Redpitaya and the data transfer protocole.
Since there is one output left, could you create the quadrature signal of the sinusoidal exciting output, which has same amplitude but 90°-out of phase? This can help to make an analog modulator, or a rotating magnetic field, etc.
Are there any possibilities to have some GPIO or auxiliary DACs?
Thanks a lot
Maxim
The text was updated successfully, but these errors were encountered: