New H-bridge connected
As soon as it was connected properly, which took longer than it should have, it was clear this motor controller was different from the previous model. When 40% duty cycle was applied the motor spun aggressively instead of just beating inertia. The starting duty cycle was lowered and a mere 8% was enough to move the motor. 8% was approximately one volt. Hopefully, this meant that the initial speed was only 1/12 of the final speed capable with this motor.
Meter connected to read motor voltage
An animation was made of the gears moving. This animation was actually a ping-pong loop. The actual recording was the gears moving in one direction but the animation reverses the frames to give a smooth animation. The gears were extremely loud and the motor made a high-pitch sound, probably the PWM frequency.
The high speed movement of the gears caused the left-handed nut on the motor shaft to loosen more than once. A nut driver was kept nearby to reattach it as necessary. It will be important to use a chemical thread locker or at least a mechanical lock washer.
Nut driver to retighten nut
- Panel layout PDF or DWG
- S Symbol Plate OpenSCAD source or STL model
- Ultrasonic flush-mount source or STL
- Internal ring gear
- Spring hub includes source and STL for metric and imperial
- Slow ramping Arduino sketch
- 1 Small Arduino Micro
- 2 Stereo potentiometers (10K)
- 4 Multi-turn potentiometers (10K)
- 2 Twelve volt DC motors
- 1 Dual H-bridge
- 2 Ultrasonic distance sensors
- 1 Sine wave generator or the Amazon version
- 1 Voltage Regulator
- 1 Twelve volt three amp power supply
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Completed projects from year 3.
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, are not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address firstname.lastname@example.org becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.