EIGENROOMLAB WORKSHEET 16DC motor · Design challenges
A good margin, a bad run
NameSectionDate
Goal
Show that a phase margin describes the small-signal loop and cannot certify a saturated run.
Setup
Lab eigenroom.com/lab?lesson=margin-versus-saturation · short link eigenroom.com/margin-versus-saturation
Open it on a phone or a computer; there is nothing to log in to or install. The link loads run A's settings:
- Target speed
- 120 rad/s
- Loop
- Closed loop
- Controller type
- PID
- Proportional Kp
- 0.4
- Integral Ki
- 0.6
- Derivative Kd
- 0.008
- Anti-windup
- Off
- Load torque
- 0.04 N·m
- Sensor noise
- 0
- Controller period
- 20 ms
- Disturbance events
- None
- Recording
- 12 s
- APreset, exactly as the link opens it.
- BChange only: Target speed → 20 rad/s.
Pin each run before you change a setting, so you can compare runs at the same replay time.
1. Predict
Why can the frequency plot look acceptable while the motor overshoots?
Write your prediction and a reason before you run anything.
2. Observe
Read each value in the lab and write it in the table.
| Quantity | Where to read it | A | B |
|---|---|---|---|
| Phase margin (°) | Frequency workbench | ||
| Requested voltage at t = 0 s (V) | Readout at 0 s | ||
| Overshoot vs target (%) | Measured response | ||
| Settling, ±2% of target (s) | Measured response |
3. Explain
The phase margin is the same in both runs. Why?
Use the requested voltage at t = 0 s to explain why run A overshoots so much more than run B.
Extension (optional)
Try targets of 30 rad/s and 40 rad/s. Where does the request at t = 0 s first exceed 12 V, and what happens to the overshoot?