Incorrect description in website?
2 views (last 30 days)
Show older comments
aakash dewangan
on 21 Mar 2023
Commented: Christine
on 9 Aug 2023
Hi,Can you please confirm that the description on resolution of Arduino due DAC pin given in the page is incorrect.In simulink it gives only 8bit resolution, but board has the capability of 12bits. Please provide the solution to change resolution to 12bits DAC. The link for page is: https://in.mathworks.com/help/supportpkg/arduino/ref/analogoutput.html
4 Comments
Christine
on 9 Aug 2023
The Arduino Due has two 12-bit digital-to-analog converters (DAC) which provide analog output on pins DAC0 and DAC1. Each of these DACs can provide a voltage output with a resolution of 12 bits, allowing for 4096 distinct voltage levels.
In Simulink, you should be able to set up the Arduino Due's DAC pins to output analog signals with 12-bit resolution. Check here general outline of the steps you might need to follow:
- Model Configuration:
- Open your Simulink model.
- Add the necessary blocks for generating analog output, often using the "Analog Output" or "Arduino Analog Write" block.
- Block Configuration:
- Double-click on the block you added in the previous step to open its configuration dialog.
- Look for settings related to the resolution or number of bits. Make sure it's set to 12 bits (4096 levels).
- Signal Values:
- When generating analog output, ensure that the values you're sending to the DAC block range from 0 to 4095 (for 12-bit resolution). This corresponds to the full range of the DAC's capability.
- Compile and Upload:
- Once you've configured your Simulink model to output analog signals with 12-bit resolution, compile the model and upload it to your Arduino Due.
Remember that the specific steps might vary slightly depending on the version of Simulink you're using and the exact block names. If you're having trouble finding the settings for 12-bit resolution, you might want to consult the Simulink documentation or contact MathWorks support for assistance.
Accepted Answer
Ganapathi Subramanian
on 31 Mar 2023
Hi Aakash,
It seems like a potential bug. It has been reported to our development team. We will try to fix this in future releases of MATLAB.
More Answers (0)
See Also
Categories
Find more on Modeling in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!