Other Parts Discussed in Thread: DAC8734
I recently followed the Breadboard's tutorial/review for this DAC on youtube (https://www.youtube.com/watch?v=uYl_jqJeGtA), and found it to be fairly comprehensive and straight forward; However, the DAC does not seem to be working properly. We have successfully used the code before to test one of these DACs in the past.
I am testing what is described in the next paragraph with the Teensy connected to a breadboard, using jumpers as connections.
The micro controller in use is a teensy 3.6, and the respective MOSI, MISO, CK and CS pins are connected to the pins on the DAC, as per that tutorial. The 3v3 pin is connected tho the 3v3 pin on the teensy, and the 5 V pin is connected to a power supply which is supplying 5 V (and it says its drawing .01 A of current). A common ground is being used between the power supplies, analog GND and digital GND (I tried separating analog and digital, but it yielded the same result). The two voltages on the pins requiring a positive and negative range are ~+- 16.58 V. These are also hooked up correctly and fall withing the range specified in the user guide.
I have two DAC8734EVM, and I believe that at least one of them is broken. They are acting differently in response to the commands being sent to the DAC. One of them is producing no output, while the other produces spikes that go quickly back to 0 V as seen below.
It spikes whenever a significant change is given. For example shifting between the 0th position and the 20,000th position of the DAC. It is not consistent. Sometimes when switching to 20,000 from 0 it will yield negative spikes, and sometimes it will yield positive spikes. The same can be said from switching to 0 from any other significantly greater number. I would expect to get an analog voltage from the DAC instead of the spike. The jumpers shorting the pins are as they came in the box for both DACs. Would it seem to you like the DAC is broken, or does it sound like I did something wrong in the wiring? If the DACs might be broken, is this an issue likely to have been caused by something I did earlier?