Eventually, the over-current pin is triggered resulting in one motor getting disabled and stopping movement. (I checked for over-temperature. It's definitely not that.)
Do I need a different driver or? Also, I am using the ESP32's DAC to connect to the VREF pins of the stepper driver. There might be an issue with using that since GPIO pins on the ESP32 can only deliver 12 mA max.
Stepper motors don't draw current. They are given current by the driver.
What current is tge driver set up to?
Any heatsink on the driver?
Any forced cooling used?
Schematics please. Not enough powering is another possibility.
There is a gigantic heat sink with thermal paste and a fan. It's a cool 30-31 C (thermocouple measurement at bottom of inch long fins).
I am not using a carrier/dev board. The DRV8825s are on a custom PCB (which I cannot share). Before using the DAC to control the torque on previous version of the PCB it worked. So I soldered in wires on the old version and it worked to control the torque that way.
Then, with a new version of the PCB, the first assembled PCB worked as expected. I've assembled 5 more boards in the exact same way and with the same components and one motor always just stops after a while (about a minute).
So I ordered new PCBs with grounding layers and some pulldown resistors and the same behavior persists, just over a slightly longer period of time. One motor stops (after 5-10 minutes).
Okey. Likely no overhating but the way the fault appears it looks like overheating.
DACs usually supply not much current. Is 30k Ohm okey?
It looks like You changed someting after the first working board. Now there are issues. Check up the change and check up the boards from the manufactorer. Something has gone wrong.
Always the same motor? Swap the motors and see if it follows the motor? Do you have other motors to try, or always the same motors. Eliminate motors if possible.
Are the 200mOhm resistors really that resistance? Replace with measured, identical resistors.
I have swapped the motors. I have four total. I should also note, both motors function seemingly forever if the program runs them 1:1. When the program starts a more circular shape, where it might be something like 2:3, then one stops.
