Differences

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

--- embedded:adventures:driving [2016/08/31 18:20] – [H-Bridge Control] pvela
+++ embedded:adventures:driving [2024/08/20 21:38] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 Once basic actuation of the motors is possible, the typical next step is to create an interface that abstracts the basic functionality so that you can focus on the use of the motors and not on the low-level parts of commanding them.
-Since you've already figured out how to program things so that the motors move, either via [[embedded:adventures:RCServo | RC Servo control]] or via [[embedded:adventures:MotoControl|H-Bridge control]], let's start to packaging it up for a robotic vehicle.
+Since you've already figured out how to program things so that the motors move, either via [[embedded:adventures:RCServo | RC Servo control]] or via [[embedded:adventures:MotoControl|H-Bridge control]], let's start to packaging it up for a robotic vehicle. In Arduino- and maybe Energia-speak this adventure is about writing a library (though more generally it is about creating a class to abstract some functionality).  Arduino has [[https://www.arduino.cc/en/Reference/APIStyleGuide|some tips]] on [[https://www.arduino.cc/en/Hacking/LibraryTutorial | writing libraries]].  The tips, though not necessarily the coding specifics, should apply to mBed and TI (Energia) too.
@@ Line 27: / Line 27: @@
 Interfacing an H-Bridge is a bit different since both the direction bit and the actual (variable) duty cycle signal need to be provided, per motor. The constructor should specify these four pins.  The rest should be the same.  Call this class **tankBridge**.
+-------------------
+;#;
+[[: | Main]] -- [[basics:adventures | Adventures]]
+;#;