My Projects

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

arduino:Controller_for_Cybot [2020/02/06 20:42]
tony
arduino:Controller_for_Cybot [2021/07/30 15:55] (current)
tony
Line 4: Line 4:
 \\ \\
  
-I have received a discarded Cybot robot which is mostly complete and decided to replace its control chips with an Arduino, which will require writing software to control the motors and receive inputs from the ultrasonic and LDR sensors.  ​The are quite a few projects on the internet that reuse the Cybot hardware but replace or modify the sensors and interface boards -  the objective with this project is to make a substitute for the processor board, that can plug into any other unmodified Cybot.+I have received a discarded Cybot robot which is mostly complete and decided to replace its control chips with an Arduino, which will require writing software to control the motors and receive inputs from the ultrasonic and LDR sensors.  ​There are quite a few projects on the internet that reuse the Cybot hardware but replace or modify the sensors and interface boards -  the objective with this project is to make a substitute for the processor board, that can plug into any other unmodified Cybot.
  
 <​HTML>​ <​HTML>​
Line 19: Line 19:
  
 ===== Hardware description ===== ===== Hardware description =====
-The Cybot was originally built in stages from kitset parts supplied with a magazine. It is built on a three wheeled platform, with two independent driving wheels and one caster wheel to balance the front. There is a 6 volt battery holder for the wheels and a separate 9V battery to drive the electronics. Interface and controller boards are modular and plug together as more features are added. There were a number of stages, developing eventually to a remote controlled beast. But the one I have was just at the end of the first stage, it has two powered wheels with an H-bridge control circuit made of discrete components, two Light Dependent Resistors (LDRs) for detecting light sources, a line following module, and two pairs of ultrasonic transmitter/​receivers for detecting its environment.+The Cybot was originally built in stages from kitset parts supplied with a magazine. It is built on a three-wheeled platform, with two independent driving wheels and one caster wheel to balance the front. There is a 6-volt battery holder for the wheels and a separate 9V battery to drive the electronics. Interface and controller boards are modular and plug together as more features are added. There were a number of stages, developing eventually to a remote-controlled beast. But the one I have was just at the end of the first stage, it has two powered wheels with an H-bridge control circuit made of discrete components, two Light Dependent Resistors (LDRs) for detecting light sources, a line following module, and two pairs of ultrasonic transmitter/​receivers for detecting its environment.
  
-Using the ultrasonic sensors appears to be the most difficult part. They have a fairly minimal interface, but from 3rd party documentation should produce 40kHz pulses when something reflects the signal, perhaps an interrupt driven routine will be useful. There are a few other projects on the Internet that have made these types of modifications,​ but all seem to have skipped the ultrasonic sensors, some even add other more sophisticated ultrasonic range finding hardware instead.+Using the ultrasonic sensors appears to be the most difficult part. They have a fairly minimal interface, but from 3rd party documentation should produce 40kHz pulses when something reflects the signal, perhaps an interrupt-driven routine will be useful. There are a few other projects on the Internet that have made these types of modifications,​ but all seem to have skipped the ultrasonic sensors, some even add other more sophisticated ultrasonic range finding hardware instead.
  
 There appears to be a requirement for 15 I/O pins from the controller. There appears to be a requirement for 15 I/O pins from the controller.
Line 53: Line 53:
 The Arduino has to generate the 40kHz, 10V p-p, driving signal for the two transmitters,​ then check for a received echo on the right and left receivers. The echo signal should provide range information as well as just presence/​absence of obstructions. The sensors face forward on an angle so do not actually tell you whether the detected object is forward or to the sides of the Cybot. If an object is directly ahead, and flat, both sensors should receive an equal signal that decreases in distance as the Cybot advances, but two converging walls on either side would produce a similar result. The Arduino has to generate the 40kHz, 10V p-p, driving signal for the two transmitters,​ then check for a received echo on the right and left receivers. The echo signal should provide range information as well as just presence/​absence of obstructions. The sensors face forward on an angle so do not actually tell you whether the detected object is forward or to the sides of the Cybot. If an object is directly ahead, and flat, both sensors should receive an equal signal that decreases in distance as the Cybot advances, but two converging walls on either side would produce a similar result.
  
-I decided that the software echo detector should be interrupt driven, so that the Cybot can continue to manoeuvre etc, and have the sensors update independently. The output of the Cybot sonar board is a negative going pulse for each echo received. Looking at an oscilloscope I see many more echo pulses than wave cycles transmitted,​ I expect that the Cybot'​s pings are bouncing back and forth between the Cybot and the target, generating multiple echoes. The transmitter produces a broad pulse, so there are also multiple echoes from different ​direction ​and distances so there are groups of echoes returned. Difficult to interpret all the echoes, so we will ignore all but the first pulse seen after sending our ping - that will give us the distance to the nearest object.+I decided that the software echo detector should be interrupt-driven, so that the Cybot can continue to manoeuvre etc, and have the sensors update independently. The output of the Cybot sonar board is a negative-going pulse for each echo received. Looking at an oscilloscope I see many more echo pulses than wave cycles transmitted,​ I expect that the Cybot'​s pings are bouncing back and forth between the Cybot and the target, generating multiple echoes. The transmitter produces a broad pulse, so there are also multiple echoes from different ​directions ​and distances so there are groups of echoes returned. Difficult to interpret all the echoes, so we will ignore all but the first pulse seen after sending our ping - that will give us the distance to the nearest object.
  
 {{arduino:​cybot:​p2117151b.jpg?​350}} {{arduino:​cybot:​p2117153b.jpg?​350}} {{arduino:​cybot:​p2117151b.jpg?​350}} {{arduino:​cybot:​p2117153b.jpg?​350}}
Line 74: Line 74:
 ==== Arduino Sonar test code ==== ==== Arduino Sonar test code ====
  
-  * {{arduino:​cybot:​v1.00:​Cybot-sonar-test.ino}},​ sketch to test drive the Cybot'​s sonar board. ​ This is a stand alone piece of code to test drive the sonar, it expects an ANSI serial terminal program is present to display the results.+  * {{arduino:​cybot:​v1.00:​Cybot-sonar-test.ino}},​ sketch to test drive the Cybot'​s sonar board. ​ This is a stand-alone piece of code to test drive the sonar, it expects an ANSI serial terminal program is present to display the results.
  
 ==== Arduino Sonar obstacle avoidance testing ==== ==== Arduino Sonar obstacle avoidance testing ====
-  * {{arduino:​cybot:​v1.00:​cybot-motor-sonar-v1.06.ino|v1.06}} Sonar test of obstacle avoidance. ​ This is an expanded program with an interrupt driven routine to handle the ultrasonic sensors. ​  It tries to steer the Cybot away from obstacles and detect whether it has become stalled.+  * {{arduino:​cybot:​v1.00:​cybot-motor-sonar-v1.06.ino|v1.06}} Sonar test of obstacle avoidance. ​ This is an expanded program with an interrupt-driven routine to handle the ultrasonic sensors. ​  It tries to steer the Cybot away from obstacles and detect whether it has become stalled.
  
 <​HTML>​ <​HTML>​
Line 90: Line 90:
 {{ arduino:​cybot:​v1.00:​cybot_arduino_schem.png?​600 |Arduino to Cybot connections}} {{ arduino:​cybot:​v1.00:​cybot_arduino_schem.png?​600 |Arduino to Cybot connections}}
  
-{{arduino:​cybot:​v1.00:​p1269362b.mp4}} ​Test drive of Cybot showing it sometimes avoiding hard surfaces, sometimes crashing into them.  Also shows stall detection when it runs into an edge which the angled front sonar detectors can not see - after 20 seconds it decides it is stalled, and restarts. (NB in this test the front wheel is tending to veer right so the Cybot does not travel in straight lines).+Test drive of Cybot showing it sometimes avoiding hard surfaces, sometimes crashing into them.  Also shows stall detection when it runs into an edge that the angled front sonar detectors can not see - after 20 seconds it decides it is stalled, and restarts. (NB in this test the front wheel is tending to veer right so the Cybot does not travel in straight lines).
  
-My main problem was detecting when the Cybot had got itself into trouble and was not moving. ​ I tried looking at whether the sonar echos were unchanging - indicating it was not moving (or there was a very uniform environment),​ but there was too much "​noise",​ natural variability,​ in  the returned echos to tell the difference. ​ Of course there are lots of ways involving adding extra sensors (eg wheel rotation detectors) to detect whether it was stalled, but adding them would be going against the plan of trying to make the best Cybot using the current hardware, but just replacing the brains. ​  I did add a voltage divider to monitor the battery level using an Arduino analog input - when stalled the Cybot draws a lot of current and because of the batteries internal resistance, the voltage drops. ​ While not actually adding another active sensor device, this is cheating a little. ​  Not 100% successful as on smooth surfaces the Cybot'​s wheels just spin when it is stalled, so the current peek is not as high.+<​HTML>​ 
 +  <div class="​shadows"​ style="​text-align:​center">​ 
 +    <video width="​640" ​ controls>​ 
 +      <source src="/​dokuwiki/​_media/​arduino/​cybot/​v1.00/​p1269362b.mp4"​ type="​video/​mp4">​ 
 +Your browser does not support the video tag. 
 +    </​video>​ 
 +    <div class="​container">​ 
 +      Test drive of Arduino controlled Cybot 
 +    </​div>​ 
 +  </​div>​ 
 +</​HTML>​ 
 + 
 +My main problem was detecting when the Cybot had got itself into trouble and was not moving. ​ I tried looking at whether the sonar echos were unchanging - indicating it was not moving (or there was a very uniform environment),​ but there was too much "​noise",​ natural variability,​ in the returned echos to tell the difference. ​ Of course there are lots of ways involving adding extra sensors (eg wheel rotation detectors) to detect whether it was stalled, but adding them would be going against the plan of trying to make the best Cybot using the current hardware, but just replacing the brains. ​  I did add a voltage divider to monitor the battery level using an Arduino analog input - when stalled the Cybot draws a lot of current and because of the batteries internal resistance, the voltage drops. ​ While not actually adding another active sensor device, this is cheating a little. ​  Not 100% successful as on smooth surfaces the Cybot'​s wheels just spin when it is stalled, so the current peek is not as high.
  
 For testing purposes the Arduino was fitted with an LCD display so that I could monitor what the code was seeing, and what it "​thought"​ its current state was (eg running, turning, stalled). ​ This version monitors current speed, battery voltage, and the left and right sonar return levels. For testing purposes the Arduino was fitted with an LCD display so that I could monitor what the code was seeing, and what it "​thought"​ its current state was (eg running, turning, stalled). ​ This version monitors current speed, battery voltage, and the left and right sonar return levels.
Line 113: Line 125:
      * Forum: Microcontroller and Digital Electronics,​ AT MEGA 163 ([[https://​www.mikrocontroller.net/​topic/​2486|German]],​ [[https://​www.mikrocontroller.net/​topic/​2486|English]])      * Forum: Microcontroller and Digital Electronics,​ AT MEGA 163 ([[https://​www.mikrocontroller.net/​topic/​2486|German]],​ [[https://​www.mikrocontroller.net/​topic/​2486|English]])
        * [[https://​www.mikrocontroller.net/​attachment/​683/​komplett.gif|Cybot schematic]]{{:​arduino:​cybot:​komplett.gif?​1| }}.        * [[https://​www.mikrocontroller.net/​attachment/​683/​komplett.gif|Cybot schematic]]{{:​arduino:​cybot:​komplett.gif?​1| }}.
-     * [[http://​www.adrirobot.it/​menu_new/​index/​index_cybot.htm|Adrirobot Cybot Presentazione]]. (Italian site with built in translation option).+     * [[http://​www.adrirobot.it/​menu_new/​index/​index_cybot.htm|Adrirobot Cybot Presentazione]]. (Italian site with built-in translation option).
        * [[http://​www.adrirobot.it/​menu_new/​index/​index_cybot_telecomando.htm|Cybot remote control]].        * [[http://​www.adrirobot.it/​menu_new/​index/​index_cybot_telecomando.htm|Cybot remote control]].
-     * [[http://​hobbyelectronica.hol.es/​|Electronica als hobby]]. (Dutch site, but built in translation links).+     * [[http://​hobbyelectronica.hol.es/​|Electronica als hobby]]. (Dutch site, but built-in translation links).
      * [[https://​web.archive.org/​web/​20121010142548/​http://​www.mstracey.btinternet.co.uk/​|Mike'​s Cybot Page]].      * [[https://​web.archive.org/​web/​20121010142548/​http://​www.mstracey.btinternet.co.uk/​|Mike'​s Cybot Page]].
      * [[https://​web.archive.org/​web/​20080821101139/​http://​www.cybench.co.uk/​index.php|Robotics,​ Cybot and Electronics Resources]].      * [[https://​web.archive.org/​web/​20080821101139/​http://​www.cybench.co.uk/​index.php|Robotics,​ Cybot and Electronics Resources]].
Line 133: Line 145:
      * [[https://​www.youtube.com/​watch?​v=MqYYqw0RPKc|Cybot Upgrade]].\\ Cybot internals replaced with Arduino Uno, follows light based on LDR readings ({{arduino:​cybot:​cybot_ldr_light_follower.c|the code}}).\\      * [[https://​www.youtube.com/​watch?​v=MqYYqw0RPKc|Cybot Upgrade]].\\ Cybot internals replaced with Arduino Uno, follows light based on LDR readings ({{arduino:​cybot:​cybot_ldr_light_follower.c|the code}}).\\
      * [[https://​web.archive.org/​web/​20060925083315/​http://​linbot.sourceforge.net/​index.html|Linbot]] (also [[http://​www.ouroboros.org/​linbot/​index.html|new site]]) by Ricardo Tellez.\\ Start of project to control Cybot from Linux.\\      * [[https://​web.archive.org/​web/​20060925083315/​http://​linbot.sourceforge.net/​index.html|Linbot]] (also [[http://​www.ouroboros.org/​linbot/​index.html|new site]]) by Ricardo Tellez.\\ Start of project to control Cybot from Linux.\\
-     * [[https://​github.com/​XarpeSerpe/​cybot|gitub XarpeSerpe'​s Cybot]] (French).\\ Control firmware for a Cybot replacing its processors with an arduino.\\+     * [[https://​github.com/​XarpeSerpe/​cybot|gitub XarpeSerpe'​s Cybot]] (French).\\ Control firmware for a Cybot replacing its processors with an Arduino.\\
      * [[https://​github.com/​fitzterra/​Cybot|github Fitzterra'​s Cybot]].\\ Cybot Resurrected - Arduino based Cybot re-engineered.\\      * [[https://​github.com/​fitzterra/​Cybot|github Fitzterra'​s Cybot]].\\ Cybot Resurrected - Arduino based Cybot re-engineered.\\
      * [[https://​github.com/​djneo92nl/​cybot|github Djneo92nl'​s Cybot]].\\ Cybot (cheap toy) arduino driver.\\      * [[https://​github.com/​djneo92nl/​cybot|github Djneo92nl'​s Cybot]].\\ Cybot (cheap toy) arduino driver.\\