diff --git a/.gitignore b/.gitignore deleted file mode 100644 index e257658..0000000 --- a/.gitignore +++ /dev/null @@ -1,34 +0,0 @@ -# ---> C++ -# Prerequisites -*.d - -# Compiled Object files -*.slo -*.lo -*.o -*.obj - -# Precompiled Headers -*.gch -*.pch - -# Compiled Dynamic libraries -*.so -*.dylib -*.dll - -# Fortran module files -*.mod -*.smod - -# Compiled Static libraries -*.lai -*.la -*.a -*.lib - -# Executables -*.exe -*.out -*.app - diff --git a/CrabbyHome-comp/CrabbyHome-conn/.gitignore b/CrabbyHome-comp/CrabbyHome-conn/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/CrabbyHome-comp/CrabbyHome-conn/.vscode/extensions.json b/CrabbyHome-comp/CrabbyHome-conn/.vscode/extensions.json new file mode 100644 index 0000000..0f0d740 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/.vscode/extensions.json @@ -0,0 +1,7 @@ +{ + // See http://go.microsoft.com/fwlink/?LinkId=827846 + // for the documentation about the extensions.json format + "recommendations": [ + "platformio.platformio-ide" + ] +} diff --git a/CrabbyHome-comp/CrabbyHome-conn/include/README b/CrabbyHome-comp/CrabbyHome-conn/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/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/CrabbyHome-comp/CrabbyHome-conn/lib/README b/CrabbyHome-comp/CrabbyHome-conn/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/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/CrabbyHome-comp/CrabbyHome-conn/platformio.ini b/CrabbyHome-comp/CrabbyHome-conn/platformio.ini new file mode 100644 index 0000000..6869843 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/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:wemos_d1_mini32] +platform = espressif32 +board = wemos_d1_mini32 +framework = arduino diff --git a/CrabbyHome-comp/CrabbyHome-conn/src/main.cpp b/CrabbyHome-comp/CrabbyHome-conn/src/main.cpp new file mode 100644 index 0000000..58b344c --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/src/main.cpp @@ -0,0 +1,9 @@ +#include + +void setup() { + // put your setup code here, to run once: +} + +void loop() { + // put your main code here, to run repeatedly: +} \ No newline at end of file diff --git a/CrabbyHome-comp/CrabbyHome-conn/test/README b/CrabbyHome-comp/CrabbyHome-conn/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-conn/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PlatformIO Unit Testing 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/page/plus/unit-testing.html diff --git a/CrabbyHome-comp/CrabbyHome-master/.gitignore b/CrabbyHome-comp/CrabbyHome-master/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/CrabbyHome-comp/CrabbyHome-master/.vscode/extensions.json b/CrabbyHome-comp/CrabbyHome-master/.vscode/extensions.json new file mode 100644 index 0000000..0f0d740 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/.vscode/extensions.json @@ -0,0 +1,7 @@ +{ + // See http://go.microsoft.com/fwlink/?LinkId=827846 + // for the documentation about the extensions.json format + "recommendations": [ + "platformio.platformio-ide" + ] +} diff --git a/CrabbyHome-comp/CrabbyHome-master/include/README b/CrabbyHome-comp/CrabbyHome-master/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/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/CrabbyHome-comp/CrabbyHome-master/lib/README b/CrabbyHome-comp/CrabbyHome-master/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/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/CrabbyHome-comp/CrabbyHome-master/platformio.ini b/CrabbyHome-comp/CrabbyHome-master/platformio.ini new file mode 100644 index 0000000..67e8cb2 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/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/CrabbyHome-comp/CrabbyHome-master/src/main.cpp b/CrabbyHome-comp/CrabbyHome-master/src/main.cpp new file mode 100644 index 0000000..58b344c --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/src/main.cpp @@ -0,0 +1,9 @@ +#include + +void setup() { + // put your setup code here, to run once: +} + +void loop() { + // put your main code here, to run repeatedly: +} \ No newline at end of file diff --git a/CrabbyHome-comp/CrabbyHome-master/test/README b/CrabbyHome-comp/CrabbyHome-master/test/README new file mode 100644 index 0000000..b94d089 --- /dev/null +++ b/CrabbyHome-comp/CrabbyHome-master/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PlatformIO Unit Testing 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/page/plus/unit-testing.html diff --git a/README.md b/README.md index d21da1c..d9b3577 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,16 @@ -# CrabbyHome +#CrabbyHome +Ayyay captain! Are you ready for the crabby home system? Turn your pineapple into an smart pineapple. With automatic lightning and a website to control everything you want in your cosy pineapple. This project is made with platformio in c++. -CrabbyHome arduino project \ No newline at end of file +##Inculding + * Arduino mega (controller) + * DHT11 sensor (temperature) + * lcd 16x2 (display) + * SR04 sensor (motion) + * RF transmittor + * and receiver(lights) + +##Design +For this project there are specific designs made such as a lasercut design for a 3d krusty crab to store the arduino. An electronic circuit on how to connect the arduino and its components. And more file that may come in handy for remaking this project. All of these files can be found ate "/CrabbyHome-docs". + + +