[BUG] Lower duty cycle PWM results in motor stall conditions #6

New issue

Closed

opened 2025-02-20 16:45:41 +00:00 by jakegoodwin · 3 comments

jakegoodwin commented

2025-02-20 16:45:41 +00:00

Owner

Steps to fix:

Find minimum viable duty cycle.
Refactor motor functions to map to new valid range.
Send out new version for testing.

Steps to fix: - Find minimum viable duty cycle. - Refactor motor functions to map to new valid range. - Send out new version for testing.

jakegoodwin added the

bug

label 2025-02-20 16:45:41 +00:00

jakegoodwin self-assigned this 2025-02-20 16:45:41 +00:00

jakegoodwin commented

2025-02-20 16:46:34 +00:00

Author

Owner

As a side note, I could potentially write a program that would attempt various duty cycles at different frequencies to figure out which one worked correctly.

This could potentially auto calibrate the fader/motor setup, however it may take up too much space.

As a side note, I could potentially write a program that would attempt various duty cycles at different frequencies to figure out which one worked correctly. This could potentially auto calibrate the fader/motor setup, however it may take up too much space.

jakegoodwin commented

2025-02-20 23:49:13 +00:00

Author

Owner

Added speed control during the motor movement loop. This should help better test the duty cycle. Now it's configured with a F_CPU equal to 1/8 of the crystal so 9.6/8=1.2. I think this could have been part of the issue, it previously assumed no clock divider.

Added speed control during the motor movement loop. This should help better test the duty cycle. Now it's configured with a `F_CPU` equal to 1/8 of the crystal so `9.6/8=1.2`. I think this could have been part of the issue, it previously assumed no clock divider.

jakegoodwin commented

2025-02-25 17:58:13 +00:00

Author

Owner

A minimum of duty cycle for the PWM has been setup so this is no longer a issue.

jakegoodwin closed this issue

2025-02-25 17:58:13 +00:00