commit 03eda706cbc6c90ac82853a26b86a17008e5df8b Author: dan Date: Wed Sep 21 21:43:04 2022 -0400 Inital Commit. Motor speed/direction hardcoded but working. diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/.vscode/extensions.json b/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/.vscode/extensions.json @@ -0,0 +1,10 @@ +{ + // See http://go.microsoft.com/fwlink/?LinkId=827846 + // for the documentation about the extensions.json format + "recommendations": [ + "platformio.platformio-ide" + ], + "unwantedRecommendations": [ + "ms-vscode.cpptools-extension-pack" + ] +} diff --git a/include/README b/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/include/README @@ -0,0 +1,39 @@ + +This directory is intended for project header files. + +A header file is a file containing C declarations and macro definitions +to be shared between several project source files. You request the use of a +header file in your project source file (C, C++, etc) located in `src` folder +by including it, with the C preprocessing directive `#include'. + +```src/main.c + +#include "header.h" + +int main (void) +{ + ... +} +``` + +Including a header file produces the same results as copying the header file +into each source file that needs it. Such copying would be time-consuming +and error-prone. With a header file, the related declarations appear +in only one place. If they need to be changed, they can be changed in one +place, and programs that include the header file will automatically use the +new version when next recompiled. The header file eliminates the labor of +finding and changing all the copies as well as the risk that a failure to +find one copy will result in inconsistencies within a program. + +In C, the usual convention is to give header files names that end with `.h'. +It is most portable to use only letters, digits, dashes, and underscores in +header file names, and at most one dot. + +Read more about using header files in official GCC documentation: + +* Include Syntax +* Include Operation +* Once-Only Headers +* Computed Includes + +https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html diff --git a/lib/README b/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/lib/README @@ -0,0 +1,46 @@ + +This directory is intended for project specific (private) libraries. +PlatformIO will compile them to static libraries and link into executable file. + +The source code of each library should be placed in a an own separate directory +("lib/your_library_name/[here are source files]"). + +For example, see a structure of the following two libraries `Foo` and `Bar`: + +|--lib +| | +| |--Bar +| | |--docs +| | |--examples +| | |--src +| | |- Bar.c +| | |- Bar.h +| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html +| | +| |--Foo +| | |- Foo.c +| | |- Foo.h +| | +| |- README --> THIS FILE +| +|- platformio.ini +|--src + |- main.c + +and a contents of `src/main.c`: +``` +#include +#include + +int main (void) +{ + ... +} + +``` + +PlatformIO Library Dependency Finder will find automatically dependent +libraries scanning project source files. + +More information about PlatformIO Library Dependency Finder +- https://docs.platformio.org/page/librarymanager/ldf.html diff --git a/platformio.ini b/platformio.ini new file mode 100644 index 0000000..67e8cb2 --- /dev/null +++ b/platformio.ini @@ -0,0 +1,14 @@ +; PlatformIO Project Configuration File +; +; Build options: build flags, source filter +; Upload options: custom upload port, speed and extra flags +; Library options: dependencies, extra library storages +; Advanced options: extra scripting +; +; Please visit documentation for the other options and examples +; https://docs.platformio.org/page/projectconf.html + +[env:megaatmega2560] +platform = atmelavr +board = megaatmega2560 +framework = arduino diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..30a75c4 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,79 @@ +#include +// Front +int motor1pin1 = 53; +int motor1pin2 = 51; +int motor1EN = 2; + +int motor2pin1 = 49; +int motor2pin2 = 47; +int motor2EN = 3; + +// Back +int motor3pin1 = 52; +int motor3pin2 = 50; +int motor3EN = 4; + +int motor4pin1 = 48; +int motor4pin2 = 45; +int motor4EN = 5; + + +void setup() { + // put your setup code here, to run once: + // Front + pinMode(motor1pin1, OUTPUT); + pinMode(motor1pin2, OUTPUT); + pinMode(motor2pin1, OUTPUT); + pinMode(motor2pin2, OUTPUT); + + pinMode(motor1EN, OUTPUT); + pinMode(motor2EN, OUTPUT); + + // Back + pinMode(motor3pin1, OUTPUT); + pinMode(motor3pin2, OUTPUT); + pinMode(motor4pin1, OUTPUT); + pinMode(motor4pin2, OUTPUT); + pinMode(motor3EN, OUTPUT); + pinMode(motor4EN, OUTPUT); +} + +void loop() { + // put your main code here, to run repeatedly: + + //Controlling speed (0 = off and 255 = max speed): + analogWrite(motor1EN, 100); //ENA pin + analogWrite(motor2EN, 200); //ENB pin + + analogWrite(motor3EN, 100); //ENA pin + analogWrite(motor4EN, 200); //ENB pin + + //Controlling spin direction of motors: + digitalWrite(motor1pin1, HIGH); + digitalWrite(motor1pin2, LOW); + + digitalWrite(motor2pin1, HIGH); + digitalWrite(motor2pin2, LOW); + + digitalWrite(motor3pin1, HIGH); + digitalWrite(motor3pin2, LOW); + + digitalWrite(motor4pin1, HIGH); + digitalWrite(motor4pin2, LOW); + + + delay(1000); + + digitalWrite(motor1pin1, LOW); + digitalWrite(motor1pin2, HIGH); + + digitalWrite(motor2pin1, LOW); + digitalWrite(motor2pin2, HIGH); + + digitalWrite(motor3pin1, LOW); + digitalWrite(motor3pin2, HIGH); + + digitalWrite(motor4pin1, LOW); + digitalWrite(motor4pin2, HIGH); + delay(1000); +} \ No newline at end of file diff --git a/test/README b/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PlatformIO Test Runner and project tests. + +Unit Testing is a software testing method by which individual units of +source code, sets of one or more MCU program modules together with associated +control data, usage procedures, and operating procedures, are tested to +determine whether they are fit for use. Unit testing finds problems early +in the development cycle. + +More information about PlatformIO Unit Testing: +- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html