summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
Diffstat (limited to 'include')
-rw-r--r--include/README4
-rw-r--r--include/settings.h20
2 files changed, 11 insertions, 13 deletions
diff --git a/include/README b/include/README
index 194dcd4..49819c0 100644
--- a/include/README
+++ b/include/README
@@ -25,9 +25,7 @@ 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.
+In C, the convention is to give header files names that end with `.h'.
Read more about using header files in official GCC documentation:
diff --git a/include/settings.h b/include/settings.h
index 45fd574..4fb4a48 100644
--- a/include/settings.h
+++ b/include/settings.h
@@ -5,20 +5,20 @@ const int OLED_WIDTH = 128;
const int OLED_HEIGHT = 64;
const int OLED_ADDR = 0x3C;
-const int SDA_PIN = D2;
-const int SCL_PIN = D1;
+const int SCL_PIN = 8;
+const int SDA_PIN = 10;
// RGB LED
-const int RED_PIN = D6;
-const int GREEN_PIN = D5;
-const int BLUE_PIN = D0;
+const int RED_PIN = 2;
+const int GREEN_PIN = 4;
+const int BLUE_PIN = 6;
// MOTORS
-const int IN1 = D7;
-const int IN2 = D8;
+// const int IN1 = D7;
+// const int IN2 = D8;
-const int IN3 = D3;
-const int IN4 = D4;
+// const int IN3 = D3;
+// const int IN4 = D4;
// BUZZER
-const int BUZZER_PIN = A0; \ No newline at end of file
+// const int BUZZER_PIN = 3; \ No newline at end of file