Quantcast
Channel: Motor drivers forum - Recent Threads
Viewing all articles
Browse latest Browse all 14309

BOOSTXL-DRV8301: Control Register 1 resets to 0, and motor stops spinning

$
0
0

Part Number:BOOSTXL-DRV8301

Problem: When trying to run motor control code with DRV8301 boosterpack on F28379D LaunchPad, motor initially spins, control register 1 goes to value 0 (control register 2 stays at its vlaue), then all three motor phases start outputting close to Vdc voltage. 

Goal: Please help me figure out how to fix this issue.

  • Notes:
    • I don't see any of the status led's turning on indicating a fault, and when reading the status registers, I read 0. 
    • I dont think the drv8301 booster pack resets and goes in an unresponsive state, because I am still able to read control register 2 correctly as a value of 9.
    • Please find IO assignments for 379D attached if you want to check correct assignment

  • Possible causes
    • 379D launchpad by itself
    • Don't think so
    • DRV8305 boosterpack,  which has almost the same pinout as drv8301,  works with 379D launchpad.
    • Tried a different 379D launchpad, and same issue
    • Don't think so
    • Tried a different drv8301 Boosterpack, and same issue
    • DRV8301 boosterpack works on 377S launchpad
  • Software
    • Don’t think so
    • 8301 booster pack works with 377S launchpad
      • So as long as gpio assignments is correct, software not an issue
    • I Checked code gpio assignments
      • Works when using 8305 boosterpack with 379D launchpad, which has almost the same pinout as 8301
      • Only differences are:
        • Reordering of the Vsense pins
        • DC-Cal for 8301 is in place of Wake pin for 8305
        • Extra octw pin for 8301
        • Extra PWRGD pin on 8305
      • Thus only sources of assignment error is octw pin

(Please visit the site to view this file)


Viewing all articles
Browse latest Browse all 14309

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>