Home > Arduino, Balanduino, Bluetooth, Guides, TKJ Electronics > Full size DIY Balancing Robot

Full size DIY Balancing Robot

It has been quite a while since my last blog post, but I am finally ready to reveal what I have been working on the last months. Ever since I made my first balancing robot: http://blog.tkjelectronics.dk/2012/03/the-balancing-robot/ and the Balanduino I wanted to build myself a full size version which I would be able to ride just like a regular Segway.

Finally I decided to make one together with a good friend of mine Mads Friis Bornebusch in a course at my university DTU (Danish Technical University/Technical University of Denmark).

Video demonstration

Mechanical construction
The main frame is an aluminium checker plate that is 500x360x7mm which the motors are bolted onto. This width was chosen, so it would be able to go through a normal door opening. The motors used are two MY1020Z 500W, 24V, 12.6Nm brushed DC motors.

I ordered them from Germany, as I needed them right away, but you should be able to get them much cheaper by ordering them directly from China.

Below is an image of the aluminium checker plate after we have drilled the holes for the 8mm steel bolts. Note that these are countersunk, so they are flush with the surface. I would recommend using lock nuts to ensure that the bolts will stay in place – you can also use Loctite instead.

Aluminium checker plate - ready to mount the motors

Aluminium checker plate – ready to mount the motors

Motor with hub

Motor with hub

Countersunk bolt

Countersunk bolt

Motor bolted onto frame

Motor bolted onto frame

After that we drilled four countersunk 10mm holes. These are used to bolt two SKF Y bearings to the middle of the frame. Inside these are mounted a 300mm ½″ steel water pipe with some custom made fittings for the 25mm bearing.

Custom fitting on the pipe

Custom fitting on the pipe

Finished assembly

Finished assembly

In one end is mounted a 10kΩ potentiometer which is used to tell the position of the steering rod. It is mounted to a hole in the endcap secured using some epoxy. The potentiometer is then bolted to a square aluminum bracket secured to the main frame using screw holes we made.
In the other end is mounted a 90° bracket – note that we have welded a solid iron rod inside the rod, at the bracket, as it broke off during testing. All pipes are just ½″ steel water pipe that you should be able to get at your local hardware store.

Potentiometer for steering mechanism

Potentiometer for steering mechanism

90° bracket

90° bracket

Mounted to the other end of the 90° bracket is the steering rod. This is 1050mm long with a T-bracket in the other end. Two 180mm pieces with an endcap are then used as the handlebar. I decided to put some tape used for bicycles around the handlebars to give them a more comfortable grip.

Two springs from an old washing machine are connected from the edge of the frame to 230mm up on the steering rod. This ensures that the steering rod will always center itself. The hose clamps are there to ensure that both are equally tight.

Spring mechanism

Spring mechanism

On the handlebar is also a deadman button which is connected to the reset pin on the motor drivers. This needs to be held in while riding it and will prevent the motors from turning if it is released.

Deadman button

Deadman button

In order to mount the wheels onto the motors we made a custom motor hub.
A 3D-rendering of the motor hub can be seen below (not supported on mobile devices and some browsers). Note that the cylinder going out from the hub is meant to add support, as it will fit around the motor shaft. We did this as we were worried that the load might damage the gearing inside the motors.

The 3D-drawings are available at the Github repository.

Finished motor hub

Finished motor hub

The electronics

The heart of the main board is a 16MHz Arduino Pro Mini running at 5V it reads a MPU-6050, 3-axis accelerometer and gyroscope in order to estimate the angle. This is done by reading the accelerometer and gyroscope at 500Hz. The measurements are then fusioned together using the Kalman filter I wrote some time ago.
It then uses the angle as an input to a manually tuned PID-controller which will output the PWM value needed to keep the robot balanced.

A Bluetooth SPP module is connected to the microcontroller as well. This allows it to communicate with an Android phone via Bluetooth using an application I have written.

Two inputs on a LM324 operational amplifier is used as a buffer. This buffers the signal coming from the deadman switch. This is needed as there is a 20kΩ pull-up resistor on each of the motor drivers reset inputs. The diode D1 is there to ensure that the microcontroller will never be able to drive the signal going to the reset pins on the motor drivers high.
Furthermore one input is also used to buffer the voltage measurement read from the batteries.

One input is used as a inverted amplifier in order to amplify the signal coming from the potentiometer connected to the steering mechanism. The 10kΩ potentiometer is used to adjust the output until it is roughly 2.5V.

A buzzer is also connected. This is used for basic feedback, as it will beep when the robot is turned on and will be turned on in case the battery voltage gets too low.

Headers for signal going to the two motor drives are also available.

Main board schematic

Main board schematic

Below is a picture of the finished PCB. Note that the MPU-6050 is mounted using some double sticky foam – this is to reduce vibrations.
The final PCB can be found at the following link: https://github.com/Lauszus/BalancingRobotFullSize/tree/master/PCB.

Etched PCB

Etched PCB

Main board almost done

Main board almost done

In order to control the two motors you will need two high power motor drivers. We decided use the Pololu High-Power Motor Driver 24V/23A. Each motor driver is rated at 23A continuous current without a heatsink. We have mounted heat sinks on the motor drivers to ensure that they can handle the current, as the motors have a peak current of 26.7A according to its specification. In this setup the motor drivers does not even get hot.

Motor driver front

Motor driver front

Motor driver back

Motor driver back

In order to control the motors you simply apply a PWM signal to PWMH and control the direction using the DIR input. This allows you to easily control the motors with only two pins. Note that PWML is not used in the final setup. Furthermore the motor driver has two “Fault flag indicators” labeled FF1 and FF2. These will be drive high in case of a fault. The motor driver can be reset by driving the RESET pin low – this is done if the deadman button is released.
Finally it also features a current sense output. The current sensor is powered by soldering a jumper on the PCB – more information can be found at the product page.

I decided to use this motor driver, as I can control it directly using the I/O on the microcontroller instead of using a serial interface which is also used on some motor drivers. I did not want to use this, as the serial communication is slow compared to just controlling it directly using the pins on the microcontroller.

Also note that the microcontroller and motor driver are both grounded via the same battery. If you intend to power the microcontroller from a separate battery. You will need to solder a wire to GND as well.

Below is a picture of the motor drivers before and after we mounted the heatsink. Note that we cut away the heat shrink at the MOSFETs and applied some cooling paste before mounting the heatsink to the motor drives using some long bolts.

Motor drivers

Motor drivers

Motor driver with heatsink

Motor driver with heatsink

To power everything we decided to use three 6S LiPo 3000mAh batteries in parallel giving a total capacity of 9000mAh.
I have not actually made an endurance test, but they seem to last a pretty long time – it lasted from 10am to 4pm at a conference with only two batteries.

As the maximum voltage of the LiPo batteries is 25.2V (4.2V per cell) you can not simply connect the batteries directly to the VIN/RAW pin on the Arduino Pro Mini. Instead we are using a LM2596 step down switch mode regulator in order to step down the voltage to 8V. This is then stepped down by a 7805 5V linear regulator which is located on the main PCB.

It is very important that all you apply a good amount of solder to all your connections, so they can handle the high power needed. Below is a picture of the custom parallel cable I made. This was done by first applying solder to a 10AWG wire. Three 12AWG wires were then soldered to one end and a wire was wrapped around them in order to keep them in place. The same thing was then done for the other side. Finally a wire was wrapped around the entire joint and solder was applied. This will require a good soldering iron and a large tip in order to reflow the entire soldering joint.

Before connectors and heat shrink

Before connectors and heat shrink

Finished battery cable

Finished battery cable

Below is a picture of the three batteries connected to the parallel cable I made. The three female XT60 connectors are connect to the two motor drivers and the last one is connect to the LM2596 switch mode regulator.

Batteries with parallel cable

Batteries with parallel cable

The finished PCB is then mounted inside a electronic enclosure on the bottomside of the robot. It is mounted using double sided sticky foam in order to reduce the vibrations to the MPU-6050.

Electronics mounted inside enclosure

Electronics mounted inside enclosure

Robot bottom side

Robot bottom side

Robot overview

Robot overview

Me driving the robot

Me driving the robot

The code

Flowchart of the code

Flowchart of the code

The code was inspired by the Balanduino code: https://github.com/tkjelectronics/Balanduino and the basic structure is basically the same. It is written in C/C++ using some libraries and functions from the Arduino platform – these are the Wire (I2C) library and the timekeeping functions millis and micros.

A flowchart of the main loop of the code can be seen to the right.

At first the microcontroller is powered on by connecting the battery to the LM2596 regulator. Then it initializes an input which makes it able to read the current status of the deadman button. After that it sets the pin connected to the buzzer to output and reads the different values from the EEPROM including PID-values, Kalman values etc. If it detects that the EEPROM values should be restored (if the structure of the values have changed due to a value being added or removed to the configuration struct) it will turn on the buzzer for 1 second and proceed afterwards.
The next step is to initialize the UART (Universal asynchronous receiver/transmitter) at 57600 baud rate, the pins connected to the motor drivers and configure the MPU-6050 at a sample rate of 500Hz and set the accelerometer ±2g and the gyroscope range to ±250deg/s. It then calibrates the steering and finally turns on the buzzer for 100ms and initializes the timers it uses for timekeeping.

Now the main loop is running. As it can be seen on the flowchart it will run forever until power is removed. The first step is to check if any of the diagnostic pins on the motor driver are high, this means that there is some kind of fault. If that is the case it will turn on the buzzer to alert the user that something is wrong. The next is to check if any new IMU data is available. The MPU-6050 is configured so it will hold its INT pin high if there are new measurements available.
If there is no new data from the IMU it will check if any data is available at the serial port. This is used to configure PID-values, Kalman values, the amount of turning etc.
If new measurements are available it will read the sensors and calculate the angle using the Kalman filter. Then it reads the steering input from the potentiometer and checks if the robot is upright and the deadman button is pressed. If that is not the case it either means that the robot has fallen over or the user has let go of the button. In this case it will turn off the motors. If not it will calculate new PWM-values for the motors using a PID-controller.

To turn the robot a value is simply added to one motor’s PWM value and subtracted from the other. This value depends on the value read from the potentiometer connected to the steering rod. The specific code can be found inside PID.cpp.

Finally the battery voltage is checked. If the battery is too low it will start the buzzer. After this final step it will go back to the start of the loop.

One key difference between this hardware and the Balanduino is that there is no encoders on the full size version, so it is actually not possible for it to balance on its own.
This also makes it harder to estimate the speed of the robot. This is instead estimated by integrating the PWM value. This is used to tilt the robot backwards as the speed increases to prevent it from falling over.

To control the robot you simply lean forward/backward which will make the robot start to travel in the given direction. You tilt the steering rod to either side in order to turn. The full source code is available at Github: https://github.com/Lauszus/BalancingRobotFullSize.

Android application

In order to easily tune the PID-values and get data from the robot I wrote an Android application.

Below is a picture showing an overview of the Android application.

At the first screen the user is able to see the current draw of the motors, the turning value, battery level, run time and finally the PWM-value on a custom speedometer.

The next screen allows the user to adjust the PID-values, target angle and adjust how fast the robot should be able to turn.

The third screen shows the current position on a map. The position is obtained using the built-in GPS module on the Android device.

The fourth and final screen shows a graph of the current angle calculated using the accelerometer, gyroscope and the angle estimated using the Kalman filter. It also allows the users to adjust the Kalman filter coefficients.

The communication between the microcontroller and Android application is done via Bluetooth. In order to make sure that the data is parsed properly a protocol for this was implemented. It consist of a constant string header, then one byte to indicate the command and then one byte indicating the length of the data to follow. After the data there is a simple checksum. This checksum is calculated by taking XOR of each byte in the message excluding the header. The full serial protocol can be seen in the source codes: Protocol.cpp, BluetoothChatService.java and BluetoothProtocol.java

The phone is mounted on a smartphone dock that is simply zip tied to the steering rod.

Application screenshots

Application screenshots

Further documentation

Part of the assignment was to write a very brief six pages paper. The paper can be found at the following link: GRP12_AUT2_Two_wheeled_robot.pdf. I would really recommend you read through it if you are new to the concept of balancing robots as it explains the basic of how two wheeled balancing robot works and some of the theory behind it.

Furthermore we also did a presentation. A link to the poster is available as well: POSTER_GRP12_AUT2_Two_wheeled_robot.pdf

Future improvements
The final product turned out just as we planned, but there is still room for some improvements that we left out due to time constraints.

First of is to replace the current tires, as they are made of solid rubber. I believe it would help replacing these with some pneumatic tires instead in order to reduce vibrations on rough terrain.

Furthermore I would like to mount some encoders, so it would be able to balance on its own. This would allow me to remote control it! This would also allow me to measure the speed of the robot precisely instead of just integrating the PWM-value. Which should make it travel a bit smoother.

If I had to built it again I would consider making a slot for the steering rod, so it did not land on it if the robot fall over. It would also be nice if I could take the steering arm off in order to ease transportation.

I have also considered replacing the deadman switch with some kind of weight enabled mechanism, so you did not have to hold in the deadman button while riding it.

An obvious improvement would also be to upgrade the motors as they are not nearly as powerful as the ones on the Segway – these are 1500W each. This would enable it to handle rough terrain better and allow it to go faster. I would like to try some hub brushless motors so the ride could be as smooth as possible.

Finally I still need to mount the batteries and motor drivers inside some enclosures in order to protect them from water and physical damage.

If you got any questions or comments. Please do not hesitate to leave them below. Also if you want a picture of some details on the robot just tell and I will upload it!

Part list

Update 9th Juni 2015
I would also recommend the following motor driver as well: 30A 5-25V Single Brushed DC Motor Driver.

Update 8th November 2015
A 3D model of an enclosure for the new motor driver (see update above) is now available at the Github repository. I printed this on my Prusa i3 3D printer using PLA, a layer height of 0.2 mm and an infill of 20%.

Motor driver enclosure bottom

Motor driver enclosure bottom

Motor driver enclosure lid

Motor driver enclosure lid

  1. Anonym
    August 26th, 2014 at 07:02 | #1

    Jeg er dybt imponeret. :-)
    Hvor svært kan det være at efterligne en Segway?
    Håber at I får lidt mediedækning for det er den slags der kunne motivere andre unge til at lave lignende “skøre” ting.
    Godt gået guys.

  2. August 26th, 2014 at 07:13 | #2

    Haha ja præcis 😉 Mange tak!

  3. tirupathi reddy
    August 26th, 2014 at 09:18 | #3

    Hi, nice project, for the given battery specification, how much distance we can travel.
    Thank you

  4. August 26th, 2014 at 18:11 | #4

    @tirupathi reddy
    I’m not sure, as I haven’t tested it, but my guess would be about 10km. But you could easily use more batteries if you like.

  5. roscoopc
    September 8th, 2014 at 21:57 | #5

    Good work! Whit the motor datasheet (450 rpm, 6,7:1 gear ratio) and the wheel diameter I have calculated a maximum speed slightly higher than 4 km/h. It’s correct? If the robot has so much torque is possible enlarge the wheels…
    Ps I’m planning my robot 😉

  6. September 8th, 2014 at 22:04 | #6

    No we have measured a maximum speed of approximately 15 km/h :)

  7. kang
    September 21st, 2014 at 15:36 | #7

    hi, Good work! i’m studying on control system and i have studied the segway’s mechanism.
    I have a question about your work.
    Does your wheel system have tilting motion?
    i can’t know the solution of my question in your video.
    please, let me know.

  8. September 21st, 2014 at 20:33 | #8

    What exactly do you mean by tilting motion? The wheels are bolted directly to the motors.

  9. scphil
    September 29th, 2014 at 21:31 | #9

    Hi, ever thought of doing a kick start for the full size? I am looking to see if there is any way to build this for disabled (sitting position)? I assume it would work as long as there is adequate balancing? Any idea what would happen with stairs ? / curbs ?

  10. September 29th, 2014 at 22:13 | #10

    We haven’t any specific plans to do a Kickstarter, but you can never say never 😉

    You can already buy a kit to convert a regular Segway to a balancing wheelchair: http://www.allychair.com/. I believe it can handle smaller curbs fine, but differently not stairs.

  11. tk
    October 1st, 2014 at 11:43 | #11

    Hi…. very fun project. could you tell me change this” Pololu High-Power Motor Driver ” in to DIY IR2184 driver….Thank you

  12. October 2nd, 2014 at 00:40 | #12

    Please post a link to the exact driver you are talking about?

  13. tk
    October 2nd, 2014 at 05:40 | #13

    Hi….this link is use ir2184 driver …. http://www.open-electronics.org/discover-openwheels-electronics-and-test-it/
    Because in my cities easily purchase ir2184 .
    Thank you for your answer.

  14. October 4th, 2014 at 08:41 | #14

    Yes that MOSFET seems to be fine.

  15. Thamanoon
    October 18th, 2014 at 06:16 | #15

    Hi, Thank you for your tutorial. I will make a new one with stm32f3discovery board. Can I use android appication to control stm32f3discovery via bluetooth?

  16. October 18th, 2014 at 06:17 | #16

    What do you mean by control? My application simple sends out a data via Bluetooth which are then received on the UART port on the ATmega328P.

  17. October 21st, 2014 at 20:47 | #17

    I decided to build balancing robot with heart from this tutorial, but with completly different body. Posts are written in polish, but I’m also publishing a lot of photos, so I think that will be understandable :). Maybe someone will be inspired with that. Visit: https://www.facebook.com/ZbLaB

  18. October 22nd, 2014 at 03:41 | #18

    Thanks for sharing ZbLab :)

  19. Brice Daunay
    October 30th, 2014 at 20:53 | #19

    I am very impressed by you machine . I have been looking for a long time for a DIY. Segway
    I will be interested in building a more powerful machine with you.
    I have an extensive knowledge in composit carbon fiber and will be keen in building a frame and a houssing for the new machine to host all yor mechanical and electronic parts
    I have reserch some more powerfull electrical wheels 1000 to 2000 w with brshless motos and controleurs. http://www.goldenmotor.com/
    would you be interested

  20. November 1st, 2014 at 01:46 | #20

    @Brice Daunay
    That sounds like a great plan! I have send you an email 😉

  21. scampa123
  22. December 23rd, 2014 at 18:43 | #22

    By reading the description of the encoder it is clearly a two-phase octogonal encoder with AB output. This means that you could attach and use this with the Balanduino and balancing robot code without any modifications, as this is the same we use.
    So if you can get this encoder attached to your mechanical mount it should work.

    And that is correct, you will need an encoder for each motor!

    Best regards
    Thomas Jespersen

  23. Rafael Caballos
    January 13th, 2015 at 20:23 | #23

    Your work is impressive. It is one of the simplest segway clones I’ve ever seen. I’d like to make a similar one in our school. I already have motors (although less powerful, around 200W) wheels, arduinos, mpu6050, and bluetooth. But the motor drivers you say are a bit expensive for me. I found cheaper ones in ebay but I do not know if I can use them. Could you please tell me if I could, for example:
    or this:

    Thank you very much for your help.

  24. January 14th, 2015 at 11:21 | #24

    @Rafael Caballos
    Thank you for your kind words. Unfortunately I don’t think 200W is enough. You should aim for at least 350-400W.

    You can always try to use them, but in my experience motor drivers from eBay are often much less powerful compared to their claimed specs.

  25. Rafael
    January 14th, 2015 at 23:25 | #25

    Thank you for your help and sorry for the email. I did not pretend to be impatient.


  26. January 15th, 2015 at 13:07 | #26

    No problem. Don’t hesitate to contact me again if you have any further questions. I’m on vacation currently, so that is why it took me longer than normal to get back to you :)

  27. scampa123
    January 17th, 2015 at 03:39 | #27

    Hi Lauszus,

    I was wondering what pin 8 on SV3 is connected to on the motor controller board. From what I can tell you were making the same connections on both motor controllers, and SV3 is one of the connections from the motor controller to the main board. SV3 has the 8th pin which says VBAT. I also see that SV4 only utilizes the 7 pins…

    So what is VBAT on SV3 on the main board? Is that something from the motor controller board??


  28. January 17th, 2015 at 10:43 | #28

    VBAT is connected directly to the battery. It is marked V+ on the motor driver: https://www.pololu.com/product/1456.

    It is used to monitor the battery voltage -- as you can see VBAT is connected to a voltage divider and then connected to the microcontroller (see VSENSE on the schematic).

  29. scampa123
    January 17th, 2015 at 13:55 | #29


    Thank you for the quick response!!

  30. January 27th, 2015 at 18:40 | #30


    do you make board from this project? I made one by myself, “segway” runs, but I have problem with android application (or data transfer via BT) -- and I can’t find why. Please, let me know, when you finish your board.

  31. Vijay
    February 9th, 2015 at 12:35 | #31

    Thanks for this Tutorial -- I am going to replicate the same for my learning -- Do you suggest me any changes

  32. vijay
    February 9th, 2015 at 15:13 | #32

    This model is having a extra rod to drive when compared with balduino….how does this self balance when there is a extra weight one side

  33. February 9th, 2015 at 16:53 | #33

    The design files are available here: https://github.com/Lauszus/BalancingRobotFullSize/tree/master/PCB.

    I would recommend that you find another motor driver, as it has actually burned for the second time now.

    You can simply adjust the variable called targetAngle in the code. This was also how I mounted a GoPro on the Balanduino: https://www.youtube.com/watch?v=p2ip31PooXQ.

  34. vijay
    February 10th, 2015 at 13:46 | #34

    Thanks Lauszus for the link. Are there any more notes in connecting the electronic circuits used for this machine…..Iam a s/w engr but a starter in learning arduino

  35. joel leon
    April 9th, 2015 at 10:17 | #35

    Hello Kristian,
    We have just built the structure of our segway clone and are trying to go with the electronics. We have built the main board and have all the components, but face a problem: with just the schematics some components are difficult to find where they go. Could you have some picture (apart from the picture in this page) that shows us where to solder the components?

    Thank you for your help and congratulations for your great work

  36. April 9th, 2015 at 12:49 | #36

    Unfortunately no. You need to figure it out yourself 😉

    @joel leon
    All the PCB files are available at the Git repository: https://github.com/Lauszus/BalancingRobotFullSize/tree/master/PCB.

    You need Eagle to open them: http://www.cadsoftusa.com/.

  37. Joel
    April 10th, 2015 at 11:04 | #37


    Sorry to read that.
    Anyway, in the picture of the board with the components, there is a blue component with square shape on the top right corner which I can’t identify in the schematics. Is it a potentiometer? The only one I see in the schematics is R3, a 10K potentiometer ad I think it is the one attached to the steering rod. Am I right? Could you tell me if it is a different component?
    Thank you

  38. April 14th, 2015 at 15:16 | #38

    Why are you sorry? All the PCB files are available?
    Yes that is a potentiometer.

  39. May 7th, 2015 at 14:27 | #39

    Where did you get your nice wheels ?

  40. May 7th, 2015 at 17:58 | #40

    I got them from an old mobility scooter, but you can also find similar wheels online.

  41. joel
    May 19th, 2015 at 08:15 | #41

    We are going ahead with our segway clone. At this moment we have a problem with the connection of the Pololu motor drivers. In the pictures I can see 7 wires connected, and in the schematic motor 1 has 7 and motor one has 6 wires connected, but the name of the wires are not the same, for example, wire 2 is not connected, while in the picture it seems that they are all continued, without gaps. Another problem we have is that it seems the GND is not connected between the main board and the Pololus. Can you clarify us these terms, please?
    Thank you very much

  42. May 23rd, 2015 at 17:14 | #42

    The reason why one of them has 6 pins connected and the other has 7, is because VBAT is connected to one of the motor drivers. This allows us to monitor the state of the battery.

    They are all sharing the same GND as they are all connected to the same battery. That is why a connecting to GND is not necessary.

  43. Willie
    July 1st, 2015 at 01:03 | #43

    Hey, I’ve noticed there is a VBAT connection to be made to the driver, is it required? Also what pin on the driver is it, because none have that label, my guess is either VCS or V+? Or is it something different?

  44. July 3rd, 2015 at 22:27 | #44

    No it is not required, but I would recommend monitoring the battery voltage in another way then like to connecting a battery alarm: http://hobbyking.com/hobbyking/store/__18987__HobbyKing_8482_Lipoly_Low_Voltage_Alarm_2s_4s_.html.

    VBAT on the PCB corresponds to V+ on the motor driver.

  45. Willie
    July 13th, 2015 at 03:23 | #45

    Alright, I’m probably going to sound like an idiot, and I’m probably missing something that’s really obvious. But I’ll explain the situation. I’ve wired up everything exactly as you did. I’ve uploaded the arduino software, which wasn’t very straight forwad(there were compiling problems,and serial adapter problems). Fyi, I have arduino experience I’ve made a 3d printer from scratch with one. And I made sure my board was in the exact same orientation as the way you did it. And yet, I can connect the batteries(which are charged, I’m not that stupid). The arduino led will come on, the MPU-6050 led will come on, and the bluetooth module light will start blinking. I can connect to the module with my phone and make the bluetooth light go solid. But that’s it, there are never any beeps from the buzzer and the motors never make any noise or move at all. And yes I am depressing the deadmans button and I have the robot held in a vertical position. Any help would be appreciated. Thanks

  46. July 16th, 2015 at 23:29 | #46

    If there is never any beeps from the buzzer, then it means that it failed somewhere doing initialising.

    Is there any output in the serial terminal?

  47. Willie
    August 17th, 2015 at 03:59 | #47

    This is my serial output:

    i2cRead fail
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cReaNÆC/`1hh”neÀG@Œ îCn`àì)��†zq‹Ì)‰�Q†:RŒ îC.“Ì)��†zq�Ì)‰�QIgHWNË.`0`h#NeÀc`H)”neÀì!��-„zq‹Ì)‰�†:PŒ îCn`Àì)��„zq‹Ì)‰�†:PŒ îCn“ì)��†zq�Ì)‰�QCgHWNK.“Ì)��†:ÐH(“ne

    The string was a lot longer than that, I just cut off about 95% off it. It just keeps putting out a a string of “random” characters. I say “random” because it seems to have some what of a pattern just looking at it.

    Fyi, I’m using an Offficial Arudino USB2SERIAL to connect the board to my computer. It uses 602 bytes (29% of the memory) when uploaded, is that correct? I’ve set the board as “Arduino Pro or Pro Mini”, Processor “ATmega328(5v, 16MHz), and Programmer “AVRISP mkII”. Also I’ve tried this from a completely different computer and got the same results.

    Any ideas or help would be appreciated, thanks.

  48. August 17th, 2015 at 14:05 | #48

    Make sure you have set the baud rate to 57600 in the serial monitor.

    Also those errors mean that it couldn’t find the sensor.

  49. Willie
    August 17th, 2015 at 23:27 | #49

    After correcting the baud rate from 9600 to 57600, the serial output is just:

    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2
    i2cRead failed: 2

    Which keeps on going forever.

    When you say “Also those errors mean that it couldn’t find the sensor.” what sensor exactly are you referring to? Thanks

  50. August 17th, 2015 at 23:39 | #50

    How have you connected the MPU-6050? Are you sure that you are using the right address? By default it is set to 0x68: https://github.com/Lauszus/BalancingRobotFullSize/blob/0cb9cb50e50909b8e86c9eeb608befbfa4238936/IMU.cpp#L30 as it assumes that AD0 is pulled low on the MPU-6050. Try setting it to 0x69.

Comment pages
1 2 3 4546
  1. No trackbacks yet.