diff --git a/Datasheets_controller/BC327-D.PDF b/Datasheets_controller/BC327-D.PDF new file mode 100644 index 0000000..fb19d79 Binary files /dev/null and b/Datasheets_controller/BC327-D.PDF differ diff --git a/Datasheets_controller/BC337-D.PDF b/Datasheets_controller/BC337-D.PDF new file mode 100644 index 0000000..190ea97 Binary files /dev/null and b/Datasheets_controller/BC337-D.PDF differ diff --git a/Datasheets_controller/TD62783AF.pdf b/Datasheets_controller/TD62783AF.pdf new file mode 100644 index 0000000..25d67c3 Binary files /dev/null and b/Datasheets_controller/TD62783AF.pdf differ diff --git a/Datasheets_controller/doc-full_pinout_Wroom_rev2.webp b/Datasheets_controller/doc-full_pinout_Wroom_rev2.webp new file mode 100644 index 0000000..3f3562e Binary files /dev/null and b/Datasheets_controller/doc-full_pinout_Wroom_rev2.webp differ diff --git a/Datasheets_controller/sn74hc595.pdf b/Datasheets_controller/sn74hc595.pdf new file mode 100644 index 0000000..988273d Binary files /dev/null and b/Datasheets_controller/sn74hc595.pdf differ diff --git a/flipcontrol_esp32/.gitignore b/flipcontrol_esp32/.gitignore new file mode 100644 index 0000000..03f4a3c --- /dev/null +++ b/flipcontrol_esp32/.gitignore @@ -0,0 +1 @@ +.pio diff --git a/flipcontrol_esp32/.travis.yml b/flipcontrol_esp32/.travis.yml new file mode 100644 index 0000000..7c486f1 --- /dev/null +++ b/flipcontrol_esp32/.travis.yml @@ -0,0 +1,67 @@ +# Continuous Integration (CI) is the practice, in software +# engineering, of merging all developer working copies with a shared mainline +# several times a day < https://docs.platformio.org/page/ci/index.html > +# +# Documentation: +# +# * Travis CI Embedded Builds with PlatformIO +# < https://docs.travis-ci.com/user/integration/platformio/ > +# +# * PlatformIO integration with Travis CI +# < https://docs.platformio.org/page/ci/travis.html > +# +# * User Guide for `platformio ci` command +# < https://docs.platformio.org/page/userguide/cmd_ci.html > +# +# +# Please choose one of the following templates (proposed below) and uncomment +# it (remove "# " before each line) or use own configuration according to the +# Travis CI documentation (see above). +# + + +# +# Template #1: General project. Test it using existing `platformio.ini`. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio run + + +# +# Template #2: The project is intended to be used as a library with examples. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# env: +# - PLATFORMIO_CI_SRC=path/to/test/file.c +# - PLATFORMIO_CI_SRC=examples/file.ino +# - PLATFORMIO_CI_SRC=path/to/test/directory +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N diff --git a/flipcontrol_esp32/include/README b/flipcontrol_esp32/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/flipcontrol_esp32/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/flipcontrol_esp32/lib/README b/flipcontrol_esp32/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/flipcontrol_esp32/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/flipcontrol_esp32/platformio.ini b/flipcontrol_esp32/platformio.ini new file mode 100644 index 0000000..7997102 --- /dev/null +++ b/flipcontrol_esp32/platformio.ini @@ -0,0 +1,16 @@ +; 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:esp32doit-devkit-v1] +platform = espressif32 +board = esp32doit-devkit-v1 +framework = arduino + +monitor_speed = 115200 \ No newline at end of file diff --git a/flipcontrol_esp32/src/main.cpp b/flipcontrol_esp32/src/main.cpp new file mode 100644 index 0000000..1ffbf80 --- /dev/null +++ b/flipcontrol_esp32/src/main.cpp @@ -0,0 +1,184 @@ +#include + +/* +D7 - Ser (data) +D5 - clock +D1 - _OE +D2 - latch +D3 - _clear +*/ + +//Pins connected to Shift registers on own controller board +#define PIN_DATA 13 +#define PIN_CLK 14 +#define PIN_OE 27 //active low +#define PIN_LATCH 26 + + +//Pins connected to stuff on annax driver board +#define PIN_DATA_DRVBRD 33 +#define PIN_CLK_DRVBRD 32 + +//#define PIN_CLEAR 25 //active low + +#define PIN_DRIVE 33 //enables 12v to panels + +#define NUMPANELS 1 + + +//void sr_clear(); +void shiftOutSlow(uint8_t dataPin, uint8_t clockPin, uint8_t bitOrder, uint8_t val); + +unsigned long loopmillis=0; +unsigned long last_update=0; +#define UPDATE_INTERVAL 5000 + +void setup() { + pinMode(PIN_DATA, OUTPUT); + pinMode(PIN_CLK, OUTPUT); + pinMode(PIN_OE, OUTPUT); + pinMode(PIN_LATCH, OUTPUT); + //pinMode(PIN_CLEAR, OUTPUT); + pinMode(PIN_DRIVE, OUTPUT); + + pinMode(PIN_DATA_DRVBRD, OUTPUT); + pinMode(PIN_CLK_DRVBRD, OUTPUT); + + + digitalWrite(PIN_OE, HIGH); //Active Low + digitalWrite(PIN_LATCH, LOW); + //sr_clear(); + digitalWrite(PIN_DRIVE, LOW); + + Serial.begin(115200); +} + +int countz=0; + +uint8_t rowA=0; //first shift register of own controller +uint8_t rowB=0; //second shift register of own controller +uint8_t colA=0; +uint8_t colB=0; +uint8_t colC=0; +uint8_t colD=0; +uint8_t colE=0; +uint8_t colF=0; +uint8_t colG=0; + +void loop() { + loopmillis = millis(); + digitalWrite(PIN_OE, LOW); //Active Low + + + + + + if (loopmillis > last_update + UPDATE_INTERVAL) + { + + Serial.print("count="); + Serial.print(countz); + + /* + Serial.println("High"); + digitalWrite(PIN_DATA, HIGH); + + delay(1000); + + Serial.println("Low"); + digitalWrite(PIN_DATA, LOW); + + delay(1000); + */ + + + /* + rowA=pow(2, (countz/2)%8); + + + if (countz%2==0) { + colA=0; + }else{ + colA=64; //64=IL0 + } + */ + + if (countz%2==0) { + colC=2+8+32+128; + colB=0; + }else{ + //colA=64; //64=IL0 + colC=0; //IH + colB=32+128; + } + + //setting colX to 128, 32, 8,2 (or a combination of), then appling 12V to driver and GND to Clear, clears these colums + // this applies +12v to selected columns + //setting colX to 64,16,4,1 (or a combination of), then setting row shift registers to some setting sets the selected dots + // this applies GND to selected columns + //reset pin on annax board input should be used (not pulled to gnd for a short time) after dots have been flipped (to disable potentially activated transistors) + + + + + Serial.print(", rowA="); + Serial.print(rowA); + + Serial.print(", colA="); + Serial.print(colA); + + Serial.println(); + + //reset pin on ribbon cable high (12Vpullup/open), then low (via Transistor) + + //Select Columns via Shift registers + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colG); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colF); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colE); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colD); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colC); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colB); + shiftOutSlow(PIN_DATA_DRVBRD, PIN_CLK_DRVBRD, LSBFIRST, colA); //colA=128(bit 8) sets first output of shift registers high (lsbfirst) + + //select Rows via shift registers on own controller board + shiftOutSlow(PIN_DATA, PIN_CLK, LSBFIRST, rowB); + shiftOutSlow(PIN_DATA, PIN_CLK, LSBFIRST, rowA); //LSBFIRST= LSB is QH, bit 8 is QA. + digitalWrite(PIN_LATCH, HIGH); + delayMicroseconds(100); + digitalWrite(PIN_LATCH, LOW); + + + + last_update=loopmillis; + countz++; + + } + + +} + +/* +void sr_clear() { + digitalWrite(PIN_CLEAR, LOW); + delayMicroseconds(1000); + digitalWrite(PIN_CLEAR, HIGH); + delayMicroseconds(1000); +}*/ + +void shiftOutSlow(uint8_t dataPin, uint8_t clockPin, uint8_t bitOrder, uint8_t val) +{ + uint8_t i; + + for (i = 0; i < 8; i++) { + if (bitOrder == LSBFIRST) + digitalWrite(dataPin, !!(val & (1 << i))); + else + digitalWrite(dataPin, !!(val & (1 << (7 - i)))); + + delayMicroseconds(100); + digitalWrite(clockPin, HIGH); + delayMicroseconds(100); + digitalWrite(clockPin, LOW); + delayMicroseconds(100); + } +} \ No newline at end of file diff --git a/flipcontrol_esp32/test/README b/flipcontrol_esp32/test/README new file mode 100644 index 0000000..df5066e --- /dev/null +++ b/flipcontrol_esp32/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PIO 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 PIO Unit Testing: +- https://docs.platformio.org/page/plus/unit-testing.html