| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| robotic:tracked [2022/04/26 09:14] – [Software] tony | robotic:tracked [2026/09/26 22:02] (current) – [Conclusion] tony |
|---|
| \\ | \\ |
| \\ | \\ |
| =====Assembled robot====== | ===== Assembled robot ===== |
| |
| \\ | \\ |
| For the motors, the //Explorer// board uses 2 pin Molex connectors the same as found in many PC power supplies (internal plug connecting the mains wires, c0mes with high current wires attached). I modified an 8 AA cell battery pack to accommodate just 6 AA cells to provide a 7.2 to 8.4V battery for the system, found a plug (ex PC speaker I think) that matched the //Explorer// power jack. Strangely the //Explorer// board has large-pinned sockets for the outgoing power to the motors, but only a tiny battery socket through which all that power has to come! | For the motors, the //Explorer// board uses 2 pin Molex connectors the same as found in many PC power supplies (internal plug connecting the mains wires, c0mes with high current wires attached). I modified an 8 AA cell battery pack to accommodate just 6 AA cells to provide a 7.2 to 8.4V battery for the system, found a plug (ex PC speaker I think) that matched the //Explorer// power jack. Strangely the //Explorer// board has large-pinned sockets for the outgoing power to the motors, but only a tiny battery socket through which all that power has to come! |
| |
| =====Software===== | ===== Software ===== |
| I started with the Arduino code that I used on //Turbo Explorer//, but changed all turning routines to drive the motors on either side in opposite directions, rather than just letting one side idle while the other powered the turn. Otherwise the tracks on one side were dragged around as the other powered the turn. | I started with the Arduino code that I used on //Turbo Explorer//, but changed all turning routines to drive the motors on either side in opposite directions, rather than just letting one side idle while the other powered the turn. Otherwise the tracks on one side were dragged around as the other powered the turn. |
| |
| |
| This code doesn't use information from the rear sensors, even if it is backing up, so is prone to bumping into things when maneuvering. It also doesn't use info about motor current consumption even though this is readily available - this data could be used to detect wheel spin or a stall. The plastic tracks tend to slip on smooth surfaces when the robot has been stopped by some obstruction that it hasn't detected (eg something below the sensors or non reflective). Carpeted surfaces are hard for the tracks to turn on, but even there the tracks still spin rather than stall the motors.. | This code doesn't use information from the rear sensors, even if it is backing up, so is prone to bumping into things when maneuvering. It also doesn't use info about motor current consumption even though this is readily available - this data could be used to detect wheel spin or a stall. The plastic tracks tend to slip on smooth surfaces when the robot has been stopped by some obstruction that it hasn't detected (eg something below the sensors or non reflective). Carpeted surfaces are hard for the tracks to turn on, but even there the tracks still spin rather than stall the motors.. |
| =====Conclusion===== | ===== Conclusions ===== |
| | \\ |
| |
| ====== References and Additional Resources ====== | ====== References and Additional Resources ====== |
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International