This instructable will show you how to make your Arduino into an R/C interface that you can use for just about anything requiring remote control. I will also show you how I built an R/C lawnmower using my Arduino, a cheap R/C transmitter and receiver pair, and a couple of electric-wheelchair motors from Ebay. I have used this interface to control anything from basic LED's to Bipolar stepper motors, mini-robots, lifeless R/C cars from the thrift store, and even a 100lb lawnmower (all with appropriate motor controllers). It is very flexible and easy to change and very simple to set up.
See a slightly different version of the Lawnbot400 in my new book "Arduino Robotics" , as well as a DIY Segway and several other bots.
Check it out in MAKE magazine in the April 2010 issue (#22) or here:
UPDATE 3-24-10
New wheel-barrow bucket mounted on top with hinges so it can dump its contents.
UPDATE 3-10-10: NEW CODE
And new video of the Lawnbot400 moving a bunch of dirt from my truck to the flower beds across the yard, also I updated the code again.
.
I added some new code to the project that is safer, including a manual kill-switch and a Failsafe switch.
To implement the Failsafe, I used another Atmega168 (or an Arduino), to control a normally-open 60amp power relay. The relay disconnects the power to the motor-controller unless receiving a "good" signal from the 2nd microcontroller. This signal is updated 2 times every second and is either ON or OFF. If the bot gets out of range, it loses power to the motors. If I flip the kill-switch on the Transmitter, it loses power to the motors. This is also a handy way to disable it remotely if anything were to go near it that wasn't supposed to. The updated code for both microcontrollers is on the CODE page.
In addition to the failsafe, I changed the way the code reads the PPM signals to make it more reliable. Also, I realized that I was only able to run the bot at 80% speed with the old code, so now it is quite a bit faster and has more power (it can carry me across the yard @ 155lb).
Check out this new video of me riding the Lawnbot400, my wife driving it over a bunch of branches, then me making do some wheelies. Don't worry, the mower was turned off this time since the grass didn't need cutting, we were just having fun.
Disclaimer:
DANGER!!! This is a VERY dangerous piece of equipment if not handled appropriately. Since all the electronics have been home-built and the Arduino code is new, you MUST be very careful while operating anything heavy with this code. I have had 1 or 2 times during testing - and before adding a secondary failsafe - that the main Arduino jammed up and I temporarily lost control of the mower for a few seconds!!!! Though I have added several filters to discard unwanted signals and I rarely have any issues, an un-manned lawnmower IS STILL A POTENTIAL DEATH TRAP and I assume no responsibility for anything that happens as a result of your use of this code or this tutorial. This is meant as a guide for people who not only have the ability to build such a contraption, but the responsibiltity to operate it safely as well. Any suggestions or ideas on how to make this a safer project is always gladly accepted. Having said that, it's also awesome.
Background:
Most R/C equipment comes packaged for a single specific use, which makes it easy to use but is very limited in what you can do with it. So using the Arduino as an interpreter between the R/C system and the motor driver, I can use any motor controller that I want (depending on the size of the motor and power required), reprogramming the Arduino to supply the required signals.
What I ended up with:
After successfully hacking a few R/C cars from the thrift store, I got bored driving them around the driveway and I was having a hard time convincing my wife that there was any usefulness in the revived toy car. So I decided it was time to make my biggest chore at home, a whole lot easier and actually put my Arduino to work, and thats how I ended up building an R/C lawnmower.
While designing the lawnmower, I thought it would be cool to learn about the electronics that made it move, so I designed and built my own motor speed controller (or H-bridge) to power the lawnmower. I looked around at every H-bridge design I could find before deciding to go with a Mosfet h-bridge that uses both N-channel and P-channel Mosfets.
I built several different motor driver boards for this project, the first two were on Radio-Shack perf-board and the next 4 were designed using EagleCad and etched to a piece of copper-clad PCB, using the toner-transfer method. The most recent board is the one I use to mow the lawn as it has the ability to stay cool even while operating for long periods of time (30-40 mins straight) at 10-20amps and 24vdc. FWIW, I had to burn up a lot of Mosfets to find this out. If you want to see any of my other motor controllers, go to www.rediculouslygoodlooking.com and check out the Mosfet shield.
Here is what I bought already assembled:
FM R/C transmitter and receiver pair from ebay = $40
Arduino = $30
I already had a used push-mower = $60
Here is what I bought and assembled into the Lawnbot400 (as I call it):
(2) electric-wheelchair motors from ebay = $40 ea
(2) 12v marine deep cycle batteries - Walmart - $60 ea new (used batteries might work)
36" pieces of 2" angle-iron (2) and 1" square-tubing (2) from Home Depot = $8 ea
36" pieces of 1" angle-iron (2) and 1" flat steel bar (2) from Home Depot = $5 ea
(a lot) of nuts, bolts, washers, lock washers 3/8" or 1/2" with drill bit = $20
(2) caster wheels from Harbor Freight Tools = $14 ea
(2) drive wheels from Harbor Freight Tools = $8 ea
(36") 5/8" threaded rod with several 5/8" nuts and washers from Home Depot = $8
(2) sprockets from Allelectronics = $5 ea
#25 roller chain and a few universal links from Allelectronics = $10 for 3'
sprockets from Electronics Goldmine = $1.50 ea
(24) mosfets from Digikey = $1 ea
(there were quite a few small parts for building the H-bridge, they are listed later on)
Remove these ads by
Signing UpStep 1Setting up
2. Upload code to Arduino (it is on the last page)
3. Make sure you are getting a good signal
You will need an R/C radio transmitter(Tx) and receiver(Rx) pair, which is the most expensive part of the project, but can be used for every future project you might have involving R/C. I went with a 6-channel FM system, but I have tested a 27mHz AM transmitter/receiver and it works just as well. The beauty of the Arduino is that if you want to adjust the deadband or the motor-speed at turn-on, (unlike commercial ESC's) it is all easy changed in the Arduino IDE.
Once you have your radio, all you need to do is upload the code to your Arduino, plug in the 2 channels that you want to use from your radio receiver into Digital pins 2 and 3 of the Arduino (these are the 2 external interrupt pins on the Arduino) and you are ready to control whatever you want. If you don't have a batter pack for the receiver, you can run jumper wires from the Arduino +5v and GND to the R/C receiever for power, you only need to supply a single channel with GND and +5v (it is not necessary to power every channel).
Upload the code using the Aruino IDE (I am using version 0016 on Ubuntu).
I started by controlling 3 LED's with 1 channel on a breadboard. I wired a red LED to be Forward (digital pin 9), a yellow LED for Reverse(digital pin 5), and a green LED for Neutral (digital pin 12). This allows you to adjust the code to fit the needs of your radio system. You will have smooth 0-100% PWM control of both LED's and the neutral light will turn on when the control stick is centered. If needed, you can widen the deadband for Neutral, but doing so will increase the speed at turn-on (which starts at 0%, so that would likely be desirable). See pictures.
----------------------------------------
The code has 4 PWM outputs for motor control:
channel 1 Forward = Arduino digital pin 9
channel 1 Reverse = Arduino digital pin 5
channel 2 Forward = Arduino digital pin 10
channel 2 Reverse = Arduino digital pin 6
2 outputs for Neutral indicator lights:
channel 1 = digital pin 12
channel 2 = digital pin 13
The 2 INPUTS from the R/C receiver should go to:
channel 1 = digital pin 2
channel 2 = digital pin 3
---------------------------------------
If you are interested to see your readings, turn on your Serial Monitor in the Arduino IDE (set to 9600bps) and you can see the actual real-time pulse readings for each channel, they should read:
full forward = 2000 (2 milliseconds)
center = 1500 (1.5 ms)
full reverse = 1000 (1 ms)
These readings reflect the number of microseconds that the pulse signal from the R/C receiver stays HIGH (or at 5v). The typical Servo signal that comes from an R/C receiver is a pulse whose length varies from approximately 1 ms to 2 ms with 1.5 ms being Neutral (which should also be the position that the control stick returns to when you let it go). The transmitter reads the position of the control stick and sends that pulse length about once every 20milliseconds. So it is constantly updating for precise control (for more info, look up PPM on wikipedia). If you push the transmitter control stick forward, the reading should go up to 2000, if you push it backward it should go down to 1000. You can also use a voltage meter at this point to see that Digital Pins 5, 6, 9, & 10 will be changing from 0-5v depending on the position of the control sticks on the R/C transmitter.
If you care to know, the code uses the Arduino's 2 external interrupts to capture when the Rx signal pin changes states (goes from HIGH to LOW or vice versa), when it does at the beginning of each signal, it calls the interrupt function which reads the digital state of the pin and if HIGH, it records the microseconds value on the Arduino system timer0. It then returns to the loop until the pin goes LOW, at which point it subtracts the previously recorded microsecond value from the new current microsecond value to determine how long the pulse stayed HIGH (which tells us the position of the Transmitter control stick). It then does that over and over really fast.
I have the values constrained from 600-2400 in the Arduino code to keep things simple. Once it receives the signal and constrains it, it maps that value to be proportionally between 0 and 511, where 255 will be Neutral. The code then determines when the value changes and uses a function to determine the appropriate 0-255 PWM value in the appropriate direction and each direction has it's own PWM output pin to control the H-bridge.
On a side note:
To make things easier, I built an Arduino-based breakout board using Radio-Shack perf-board, a 28pin DIP socket, a 16mhz oscillator, and a bit of wire. I also added a set of female-headers in such a way that I can plug my R/C receiver directly onto the breakout board. For secure connections while mowing grass, I added screw-terminals on each Output pin and each of the 6 channels from the receiver. It also has a built in 5v regulator to power both the Atmega168 from the Arduino and the R/C receiver (which gets power when you plug it onto the breakout board). So you just route jumper wires from the channels you want to use on the receiver, to the Atmega digital pins 2 and 3. I also added 2 LED lights that are hard wired to the digital pins 12 and 13 for the Neutral lights for each channel so I can easily see when I am in neutral.
Since this bot is a Tank steer setup with 1 drive motor on each wheel, the coding is very straightforward where the left stick controls the left motor and the right stick controls the right motor. Both sticks forward means lawnmower goes straight forward, both backward and it goes in reverse. If you push the left forward and the right backward, it does a zero-turn circle. As you can imagine, mowing the grass is really fun now.
| « Previous Step | Download PDFView All Steps | Next Step » |








































































Thanks for also posting the code you used. I'm putting together a bot using parts from a wheelchair.
Also using a Spektrum Tx & Rx to drive it for now (using a Sabertooth2X25 motor driver).
I noticed in your code you have it setup for independent steering. Was wondering by ommitting the 'b' in motor 1 & 2 I could run it using differential steering.
Thanks,
Thomas
I add some data fo my robot:
-Length: 120cm
-weight: about 100kg
-Width: 70cm (100cm with a tracks)
-height 20cm
I will post some pictures of progress soon as possible!!
I finished my project
http://www.youtube.com/watch?v=7Diwy08YR9Y
I don't like the sprocket and chain system though, but I haven't done enough research or know for sure I can do it any other way. I'm worried the chain is too complex and something weeds and twigs will get caught in.
The main problem I'm having is I can't find these wheelchair motors for a reasonable price. I live in Australia and there don't seem to be any local cheap ebay auctions for these, and shipping on these suckers from the USA is $100-$200. I can't even find a cheap old wheelchair.
Is there a more... retail... kind of product I can use? Something like a servo/actuator I can order? I have no idea what I'd need to look for in terms of torque though. What sort of specs would I need to ensure in such a product to make it work with this project?
I need it to go up steep hills (30 degrees?) in long grass on rough ground. I'm already getting hardier wheels, larger drive wheels, and I found a company in Australia called Fallshaw that makes puncture-proof semi-pneumatic castors (though I can't find a price!), I will check out one of their stockists soon.
Because I need to mow my rocky terrain sooner rather than later, I might build the frame and use it like a push mower until I can get the motors and retrofit the electronics.
Any suggestions on alternatives to wheelchair motors would be appreciated.
I was denied the money I worked 2 years but the project eventually end only needs to be persistent.
If there are old people living near by (lol) there should be a scooter shop which will have parts. Batteries I got for $5 each (deep cycle) as they replace both batteries at once and one is normally "still ok".
Hope this helps
Can you give me the code for the arduino to duty cycle is less than 100% and the maximum without the relay, just an ordinary convert the signal from RC receiver in 4 PwM signal of 0-90% duty cycle, and where if necessary after I change the duty cycle?
Thanks a lot and I apologize for the inconvenience
Got to love the RC stuff, without them, where would we be. Keep up the good work and happy flying .... ooooops, mowing.
What about hooking the remote up to a pc and programming some sort of app that calculates mowing pattern so that it does it all automatically. You could even set it to vary the patterns so that they're never the same, and you'll always have a nice looking lawn.
~adamvan2000
1) Does the Lawnmower work? I see the gas engine on top but no vids of it cutting grass.
2) If you could lay out a grid of you property could you use coordinates of where you needed it to go? It seams easy enough to control but automated is better ( I have seen Arduino based UAV's , GPS might not be accurate enough for this ) but just a though more on the lines of cutting grass but it looked like you had you garden beds situated so if it could just turn and stop at say 4 points for every garden bed you would be set in the hauling aspect.
I don't Property or I would definitely be into this project. But much Props! I like it.
you are correct, 8 switches, each with 3 mosfets each. You can use 4 wires for each motor, but you can also connect the opposite (diagonal) legs of the H-bridge together, which are the 2 you would turn on separately to make the motor move. I decided to tie those opposite pins together in the circuit so you would only need 1 wire to go forward and 1 wire to go reverse for each motor.
If you have my book, check out page 94, fig 3-11. The second and third diagrams show how if you close switch 1 (S1) and switch 4 (S4) at the same time, current can flow through the motor and it will go one direction. If you close S2 and S3, it will go the other way. When the opposite inputs are tied together like this, the only thing you need to be concerned with to keep the board safe, is not turning on both inputs for one motor at the same time... which would open all switches and cause a short circuit for that h-bridge (see figure 3-12 on pg 94).
I hope that helps
~jd
The capacitors are used to store electricity for those times when the battery is just not enough. While these are not "required", they will greatly improve the stability and overall operation of the motor controller. I usually add a few capacitors to every pcb to smooth out the voltage ripples caused by deficient immediate supply from the batteries. You are welcome to try it both ways to see what you think (thats what i did)... it should not hurt the board to do without the capacitors, though they are only about $1 each and without them you will likely experience jittery movements from the motors. Just make sure to get capacitors with a voltage rating of about 50% higher than the battery voltage. The capacitance (microfarad in this case) will determine how much energy the capacitor can store, so generally larger is better for a motor controller, but I typically use around 1000 - 3000 microfarad (uF) value, and you do this by adding (2) 500uF caps or (1) 1000uF, simply add the capacitances together of all the caps that you use... make sure they all have the same voltage rating though.
Hey
goes from arduino for each mosfet, tending one way out of the arduino ide two mosfet on the high side and low, can any another logic level, because the output is 5v arduino which is insufficient to completely open standard mosfet.
Here's a picture:
http://www.dodaj.rs/f/Q/4J/2EuyX78E/fda89k9g1qwb96j.png
http://www.dodaj.rs/f/1b/Gf/3VPVduTf/h-most.jpg
yes, you can use any other logic-level N-channel mosfet to drive the P-channel mosfets. They do not consume any current, so the amperage rating should not be a concern.... this is why I originally used the 2n7000. They are an excellent and cheap N-channel mosfet with a logic-level gate and it can switch 200mA.
I have routinely used the much larger FQP50N06L logic-level power mosfet to switch very small loads, it does not hurt anything, but you may pay $1.50 for a power mosfet and around $0.60 for the smaller ones.... but availability usually rules that decision.
regards,
jd
it looks like that mosfet should work fine. It is the same chip.
i want to design a motor drive circuit for driving 2, 5A 22v DC motors. Motors will be used in an electric wheel chair, i also want to control the speed of motors with PWM. Can you provide me with any help
~jd
I may have responded to the wrong person, but yes you can use any logic-level mosfet in place of the small 2n7000. If you are using my PCB design for the triple8 motor-controller, it has holes placed for use with either transistor package (the smaller to-92, and the larger to-220) which have different pin positions. So you can use either the 2n7000 type or the FQP50N06L type.
I want to make this controller with arduino
but there is a problem, because can not find this anywhere MOSFET FQP47P06 FQP50N06L and 2N7000L
I have MTP50N06 n channel 8 pieces, they were in the control unit of the wheelchair that is broken can not be repaired, and they are fine
whether there is a solution that they use no driver like HIP4081
because I do not have much money.
engines are the same of the wheelchair
I ask for your help
I'm not sure if you can get parts from Digikey.com, but they have both of the original transistors that I used in the Lawnbor400 motor-controller (Triple8). But if you cannot order those particular transistors, you can try to find a similar pair of N-channel and P-channel mosfets with similar amperage rating and RdsOn value.
N-channel FQP50N06L:
http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=fqp50
P-channel FQP47P06:
http://search.digikey.com/us/en/products/FQP47P06/FQP47P06-ND/1057079
If you would like to use an all N-channel mosfet h-bridge , you can use the OSMC design that I have used in the past (uses the HIP4081) h-bridge driver IC that has a built-in charge pump (voltage doubler) to fully turn on the N-channel mosfet gates when being used as High-side switches (remember the source and drain pins must be connected backwards). You can populate this board with any type of N-channel mosfets (or I assume the new SciFets and Ganfets), but there is a few extra components that you will need to make this board, which actually will be more expensive than building my Triple8 design, but the OSMC design is far more efficient and powerful.
here is a link to my OSMC designs:
http://www.rediculouslygoodlooking.com/site/osmc_jd.shtml
If you are really short on cash, you could make a hybrid H-bridge using a high-power Relay (DPDT) to switch the motors direction, and a single N-channel mosfet to provide the full PWM speed control that is otherwise not possible with a relay.
I'm going to do this most cheaper option, and then I get this when MOSFET
Thanks again for your prompt reply, it means a lot to me.
http://books.google.com/books?id=tBdKnLcf2oEC&printsec=frontcover&source=gbs_ge_summary_r&cad=0#v=onepage&q&f=false