Experimental Brake Pedal
by aburks on Aug.08, 2010, under Formula SAE, Pedals
Design
This summer I have had access to the waterjet at NREC where I had my internship. The current pedal design calls for a series of 2-dimensional parts that I knew I could cut on the waterjet very easily (it can cut through stuff faster than 10 inches/minute, so it’s preferable to a CNC for this application). Unfortunately I put off cutting these parts until the last week of my internship. At 10PM on the last Tuesday night of the summer, I realized that I needed to prepare the .dxf files (files that define the shapes of a 2-dimensional part) I would need to cut some parts out after work.
When I went to make the .dxf files, I realized that I could make the entire pedal assembly out of welded steel plates cut from the waterjet. That night I started making a new version of the pedals (version 9) and had the rough outlines of all of the key parts by the time I went to bed at 3AM. I also never made the .dxf files I wanted for the next day.
Wednesday night I made the .dxf files I needed for the old pedal design, then spent the rest of the night optimizing the brake pedal assembly for weight. Here are some renders of the design, as well as some FEA results:
| Stress Plot |
Factor of Safety Plot |
An Exploded View Animation of the Assembly Process
Fabrication
On Thursday night I stayed after work to cut my parts on the waterjet off-hours. It took about 5 hours to cut three sets of parts for the old design and two sets of the experimental pedal. Though the brake pedal hasn’t been welded yet, the tabs were easy to press together to get a good sense of what it will look like in real life. I was really impressed that I could go from concept to completion in only 48 hours, thanks to SolidWorks, NREC, and the waterjet. Mike was kind enough to take some glamour shots of the final product:
Stepper Motor Driver – NAND Gates
by aburks on Jul.11, 2010, under RobOrchestra, Robotics Club
The Problem
I still need to find a cost effective way of turning a bipolar stepper motor on and off using just one pin. I want to have the ability to use a powered brake, and I want to be able to use half-stepping control of the motor for smoother rotation.
Half-stepping gives the motor higher resolution, which is good for my application because one full step cycle is enough to move a single ball through. The 4-stage process from before turns into an 8-stage process when you change to half-stepping.
t=0 A=1 B=0 C=0 D=0
t=1 A=1 B=1 C=0 D=0
t=2 A=0 B=1 C=0 D=0
t=3 A=0 B=1 C=1 D=0
t=4 A=0 B=0 C=1 D=0
t=5 A=0 B=0 C=1 D=1
t=6 A=0 B=0 C=0 D=1
t=7 A=1 B=0 C=0 D=1
t=8=0
The Solution
I noticed that in half stepping (and full stepping) if you view the logic for each of the four wires as a wave, they are always 90 degrees out of phase and have a specific shape. I wanted to create four unique signal lines, one for each of the four wave patterns, and transmit this signal to each of the 30 stepper controllers. At each controller, I should be able to choose either some default value (like a powered or unpowered brake) or let the motor run off the signal.
Because my focus was centered on the powered brake, my initial idea was to take my on-off line at each motor and perform a logical AND with three of the four waves and a logical OR with the other wave. The OR would drive its input high while the AND would drive its inputs low. This solved my problem, but unfortunately I couldn’t find a chip with an AND and an OR circuit on it.
You can build any logic gate with a combination of NAND or NOR gates. It takes two NAND gates to build an AND gate, and three NAND gates to build an OR gate (and vice-versa when building from NOR gates). They sell IC’s with 4 NAND gates in them, so I really wanted to find a way to do my OR operation with only 2 NAND gates.
Eventually I realized that if I negated the signal wave coming from the Arduino (by using 1 NAND as an inverter) and then performed a NAND operation with the wave signal and the on-off signal I got the exact output I wanted! of course, if I had just used an AND on each of the four inputs, I would have an unpowered brake and less of a headache.
I made this circuit on a protoboard, and tested it with both full and half stepping. It worked like a charm. The next step is to see if half-stepping combined with a smaller diameter wheel will be able to push balls along without jamming. Here is the protoboard layout:
Pros
This setup allows for full and half stepping. It costs less than the shift register design, about $2 per unit (only $0.75 from the two NAND ICs). Each of the four inputs is completely isolated from the others, so the wiring is simpler (which makes the PCB layout easier).
Cons
There are now 4 common signal wires instead of just one. These 4 wires will need to be jumped from board to board, potentially requiring some sort of transistor to keep the voltage from dropping as it moves across the boards.
More Photos
Stepper Motor Driver – Shift Register
by aburks on Jul.06, 2010, under RobOrchestra, Robotics Club
The Problem
I need to be able to turn 30 identical stepper motors on and off individually. I can only afford to have one unique wire going to each stepper unit because I only have ~40 digital outputs to work with. I can afford to have a few common outputs that are jumped from board to board. basically I need to turn four inputs that go in a pattern into one input.
The four lines on the motor driver (H-Bridge) basically take turns going high when I want the motor to turn. When I want it to stand still, only one of the lines should be high. This is called “wave driving” a stepper motor. Here is what happens when a bipolar stepper motor is wave driven.
t=0: A=1 B=0 C=0 D=0
t=1: A=0 B=1 C=0 D=0
t=2: A=0 B=0 C=1 D=0
t=3: A=0 B=0 C=0 D=1
t=4=0
The Solution
A Serial in Parallel out (SIPO) Shift Register does basically exactly what I’m looking for. If I have one common clock (a line that goes high every 1/4 step) and connect the 4th output to the data input, then the four parallel outputs will shift through my 4 states like a champ. The only catch is that I need to seed the circuit with the initial “1″ so that the “1″ can move along the shift register.
Luckily, because a shift register is just 4 flip-flops lined up in a row, I could build my own shift register out of flip flops, and access the set/reset abilities of the individual flip-flops. So in the final setup, I had a single clock coming from the Arduino (pulsing at 100ms intervals) which controlled the speed of the motor, and a “stop” pin coming from the Arduino to control whether or not the motor was turning.
The “stop” pin was tied to the reset pin on the first flip-flop and the set pins on the other 3. This means that when the “stop” pin was driven low, it would force the shift register into the “1-0-0-0″ state, and when it was released the “1″ would shift sequentially at the speed of the clock to drive the motor. Here is a view of the protoboard layout (the center IC is the motor driver, and the other two each contain two flip-flops):
Pros
This is a huge improvement over controlling all 120 lines individually. An Arduino mega can easily output a single clock and 30 control lines. The cost of each circuit is about $4 in parts (three Integrated Circuits, or ICs), more if you PCB it. It works, and it lets you do a powered brake as well.
Cons
The two IC’s with flip-flops are about $2.50 0f the total parts cost. For this price ($2.50×30=$75) it would technically be cheaper to buy some other board that can take serial from the Arduino and control the 120 outputs. Also, the wiring is a bit complex and uninsulated because each flip-flop’s output feeds into the next one’s input.
More Photos
Vibraphone Ball Dispensing Testing
by aburks on Jun.30, 2010, under RobOrchestra, Robotics Club
General Concept
With the current direction for the Vibraphone design, the notes are played by dropping a steel ball onto the keys. There are several ways to actuate the balls, but considering the cycle times we want to achieve and the cost of each device (since we need 30 total) using a small motor and a wheel to push balls off of a queue and into free-fall seemed like the best idea.
The club has a few sets of tiny motors that have been donated, and each set has as least 30 motors of that kind. The two sets we investigated are the tiny DC motors from the handheld fans, and some tiny bipolar stepper motors.
There are two trains of though for what to put at the end of the motor. One possibility is to put a circle with a squishy perimeter on the motor, and use friction to pull balls through the mechanism one at a time. Another concept is to cut ball-sized notches into the perimeter of a plastic circle, acting like a sprocket on a row of queued balls.
We have tested both concepts on the fan motor, and they each have their advantages and disadvantages. After testing them both on the stepper motor in a more controlled way, we should have a better sense for which type of wheel will work best for us.
Here is a photo of the notched wheel Mike Ornstein and I milled in the roboclub CNC mill the other night. The notches fit the balls great, but a consistent problem we had with the fan motor was that balls would jam if they tried to fill an empty queue.
Fan Motor
The fan motor is easy to control. If you put a voltage difference between the two wires, it will spin. If you give it a low voltage (1V) it will spin fast. If you give it a higher voltage (3V) it will spin VERY fast.
From my observations, there just didn’t seem to be enough torque on the motor to handle the balls we were giving it. Also, when testing with the notched wheel, the fan seemed to lack all braking ability. Obviously with a friction wheel instead of a notched wheel the motor will be able to resist back pressure, so I look forward to seeing how that performs once we get a nicer friction wheel made (Plastic circle with a notch for an O-ring).
Stepper Motor
The club has a box of 150 tiny stepper motors with 4 wires coming out of each of them. Starting the process knowing absolutely nothing about steppers, I eventually determined that our stepers were Bipolar Stepper Motors. Basically, there are two pairs of wires and I need to follow a cycle of powering and releasing the pairs in different directions in a certain order so I can get the motor to ’step’ 1/48th of a rotation.
By using an H-Bridge configuration on each pair of wires, I could independently control the direction of the current in the wires with digital logic. 20 lines of C++ and an Arduino later, I had a great test rid that let me step the motor at whatever speed I wanted!
I was very pleased with the initial performance of the stepper motor. There seemed to be a lot of torque behind the motor, despite its size. The biggest advantage in my eyes though was the powered braking. By setting only one set of wires in only one direction and leaving it there, the motor was in a powered lock. This should help with the back pressure issue we were facing on the fan with the notched wheel.
Here are some photos of my final Arduino/H-bridge setup. I was very happy because both the circuit and the program worked on the first try! That never happens!










