Save this video free

EECS 373 - Fall 2026 - Lecture 15: "DACs"

Interactive Sensing and Computing Lab · 1:10:40 · Watch on YouTube

Part of University of Michigan EECS 373. See all 17 lectures and search them

These notes were made with YouTube Collector. Paste any YouTube link and get the same: a summary, chapters and a searchable transcript.

Overview

The lecture compares practical digital-to-analog converter designs, from PWM with an RC filter to voltage-divider, R-2R, and binary-weighted resistor DACs, emphasizing trade-offs in speed, resolution, linearity, area, and power. It also explains output loading and buffering, DAC error types, and why a microcontroller DAC may need an external speaker driver or a dedicated audio DAC for demanding applications.

Key takeaways

Chapters

0:00 Project Revisions, Homework, and Upcoming Course Deadlines
6:14 DACs as Function Generators and Audio Outputs
8:44 DAC Output Loading and Voltage Buffers
15:36 PWM Plus an RC Filter as a Low-Cost Analog Output
19:03 Voltage-Divider DACs Select Predefined Voltage Steps
25:09 Summing Amplifiers Combine Weighted Currents
29:06 R-2R DACs Generate Binary-Weighted Currents
37:39 Binary-Weighted Resistor DACs Trade Accuracy for Smaller Area
45:30 Quantization Steps and Output Filtering
47:11 Comparing DAC Resolution, Speed, Linearity, and Area
58:29 Choosing Between Microcontroller and Dedicated Audio DACs
59:24 Microcontroller DAC Limits and Speaker-Driver Requirements
1:02:28 DAC Offset and Full-Scale Errors Can Be Calibrated
1:07:13 Differential Nonlinearity, Integrated Error, and Practical Bit Trust

Keep these chapters and the full searchable transcript in your own library.

Transcript excerpt

0:00 All right. All right, we're going to get started. Let's see here. All right, so I talked to almost all of you. 30 groups is a lot. We saw some more group discussions to go through, but because we changed schedule around a little bit Project revisions are due on Friday. Please label your revised project proposal as revision so we can look at the delta between the first and the second. You're only really graded on the second and really the purpose of the project proposal is to force you to think through all the pieces of your project

0:50 and kind of get your head around the scope. The thing I want you all to think about in the like the next week or so is and maybe next two weeks is really you need to You have a very vague notion of some aspects of your project and you need to start getting line of sight on them and understanding how complicated they are. How does it really work? If you can't gauge how much work is ahead of you, you're in a lot of trouble. So if maybe you have lots of questions about how your wireless module is going to work and it feels like a opaque black box and it's horrible, right? Like it's just complete unknown. You don't know anything about RF, well start doing some research online, get the parts, go talk to James, go talk to me or the IAs and get that information so it's not overwhelming so you know like how much work is it going to take to get that done. I worry when there's unknowns in your mind and then you get to like a week

1:38 before the deadline and you just haven't even started it. That's usually a recipe

This is the start of the transcript. Save this video free for the whole transcript, searchable and time-coded.

In this course

Related notes

Summary, takeaways, and chapters were generated by AI from the video's transcript and may contain errors. The video belongs to its creator, Interactive Sensing and Computing Lab.

Want the full transcript?

Save this video in YouTube Collector to get its complete searchable transcript, your own AI summaries, and a library that keeps every video you collect in one place.