Skip to content

DigitalOsc guides

DRV8833 Motor Does Not Move: Check Sleep and Fault on the Logic Side

DigitalOsc editorial team · Updated 21 November 2026

A motor driver can ignore a valid-looking input while asleep or in protection. Inspect its documented logic-side conditions before changing the motor command or probing a switching bridge.

Identify the driver and protect the moving system

TI documents sleep and protective fault functions for the DRV8833. Confirm the exact carrier board, supply arrangement, control mapping and limits; a breakout can alter pin access. Secure the mechanism so an unexpected start cannot cause injury or damage. This guide addresses suitable low-voltage logic nodes, not measurements across motor outputs or an unknown high-energy system.

Check documented prerequisites

Record supply conditions, sleep control and the fault state using the exact board and IC documentation. A fault output can indicate a protective condition without uniquely identifying its cause. Do not bypass protection to force movement. A visibly changing PWM input does not prove that the driver is awake, that its power supply is valid or that the requested mode is the one configured by the board.

Capture a command and one relevant control

Use suitable common-reference inputs only on the documented safe logic side. Compare an input command with sleep or fault during one deliberate attempt. Allow enough pre-event record to see the initial state. A two-input record cannot validate every command pin and supply simultaneously. Keep the rest of the commanded mode in your notes and avoid attaching an ordinary probe ground across a motor winding.

Choose the next check from the actual state

If sleep remains active, investigate its control path. If a fault occurs with an attempt, consult the documented protection conditions and inspect the unpowered system appropriately before another attempt. Correct logic signals leave supply, load and driver condition open. Two channels can preserve command-to-fault timing, but no handheld rating alone qualifies it for differential bridge measurements. Retain the bounded logic-side result rather than declaring the motor or driver failed.

Choose a handheld for this question

Two simultaneous inputs help with the relationship described here; the FNIRSI 2C53P advertises two channels, 50 MHz and up to 250 MSa/s. Check the actual acquisition mode, capture length and probes. A single-channel OT3 cannot capture two nodes in one event.

DigitalOsc links to Payverza as the retailer. Confirm the exact probes, accessories, current price and delivery before purchase. This is a proposed low-voltage workflow, not an independent hardware test; a battery-powered case does not establish isolated inputs.

Sources and scope

Examples are illustrative, not measured results. Follow the exact device and probe documentation for pinout, voltage, reference and timing limits. Recheck specifications for the version you actually own.