first commit
This commit is contained in:
commit
24ad614e84
10 changed files with 278 additions and 0 deletions
BIN
corel/Sicherungskopie_von_omobidisplay.cdr
Normal file
BIN
corel/Sicherungskopie_von_omobidisplay.cdr
Normal file
Binary file not shown.
BIN
corel/omobidisplay.cdr
Normal file
BIN
corel/omobidisplay.cdr
Normal file
Binary file not shown.
5
vscode/OmobiLEDdisplay/.gitignore
vendored
Normal file
5
vscode/OmobiLEDdisplay/.gitignore
vendored
Normal file
|
@ -0,0 +1,5 @@
|
|||
.pio
|
||||
.vscode/.browse.c_cpp.db*
|
||||
.vscode/c_cpp_properties.json
|
||||
.vscode/launch.json
|
||||
.vscode/ipch
|
67
vscode/OmobiLEDdisplay/.travis.yml
Normal file
67
vscode/OmobiLEDdisplay/.travis.yml
Normal file
|
@ -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
|
7
vscode/OmobiLEDdisplay/.vscode/extensions.json
vendored
Normal file
7
vscode/OmobiLEDdisplay/.vscode/extensions.json
vendored
Normal file
|
@ -0,0 +1,7 @@
|
|||
{
|
||||
// See http://go.microsoft.com/fwlink/?LinkId=827846
|
||||
// for the documentation about the extensions.json format
|
||||
"recommendations": [
|
||||
"platformio.platformio-ide"
|
||||
]
|
||||
}
|
39
vscode/OmobiLEDdisplay/include/README
Normal file
39
vscode/OmobiLEDdisplay/include/README
Normal file
|
@ -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
|
46
vscode/OmobiLEDdisplay/lib/README
Normal file
46
vscode/OmobiLEDdisplay/lib/README
Normal file
|
@ -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 <Foo.h>
|
||||
#include <Bar.h>
|
||||
|
||||
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
|
17
vscode/OmobiLEDdisplay/platformio.ini
Normal file
17
vscode/OmobiLEDdisplay/platformio.ini
Normal file
|
@ -0,0 +1,17 @@
|
|||
; 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:nodemcu]
|
||||
platform = espressif8266
|
||||
board = nodemcuv2
|
||||
framework = arduino
|
||||
lib_deps =
|
||||
Wire
|
||||
SPI
|
86
vscode/OmobiLEDdisplay/src/main.cpp
Normal file
86
vscode/OmobiLEDdisplay/src/main.cpp
Normal file
|
@ -0,0 +1,86 @@
|
|||
// Adafruit_NeoMatrix example for tiled NeoPixel matrices. Scrolls
|
||||
// 'Howdy' across three 10x8 NeoPixel grids that were created using
|
||||
// NeoPixel 60 LEDs per meter flex strip.
|
||||
|
||||
#include <Adafruit_GFX.h>
|
||||
#include <Adafruit_NeoMatrix.h>
|
||||
#include <Adafruit_NeoPixel.h>
|
||||
#ifndef PSTR
|
||||
#define PSTR // Make Arduino Due happy
|
||||
#endif
|
||||
|
||||
#define PIN D8
|
||||
|
||||
// MATRIX DECLARATION:
|
||||
// Parameter 1 = width of EACH NEOPIXEL MATRIX (not total display)
|
||||
// Parameter 2 = height of each matrix
|
||||
// Parameter 3 = number of matrices arranged horizontally
|
||||
// Parameter 4 = number of matrices arranged vertically
|
||||
// Parameter 5 = pin number (most are valid)
|
||||
// Parameter 6 = matrix layout flags, add together as needed:
|
||||
// NEO_MATRIX_TOP, NEO_MATRIX_BOTTOM, NEO_MATRIX_LEFT, NEO_MATRIX_RIGHT:
|
||||
// Position of the FIRST LED in the FIRST MATRIX; pick two, e.g.
|
||||
// NEO_MATRIX_TOP + NEO_MATRIX_LEFT for the top-left corner.
|
||||
// NEO_MATRIX_ROWS, NEO_MATRIX_COLUMNS: LEDs WITHIN EACH MATRIX are
|
||||
// arranged in horizontal rows or in vertical columns, respectively;
|
||||
// pick one or the other.
|
||||
// NEO_MATRIX_PROGRESSIVE, NEO_MATRIX_ZIGZAG: all rows/columns WITHIN
|
||||
// EACH MATRIX proceed in the same order, or alternate lines reverse
|
||||
// direction; pick one.
|
||||
// NEO_TILE_TOP, NEO_TILE_BOTTOM, NEO_TILE_LEFT, NEO_TILE_RIGHT:
|
||||
// Position of the FIRST MATRIX (tile) in the OVERALL DISPLAY; pick
|
||||
// two, e.g. NEO_TILE_TOP + NEO_TILE_LEFT for the top-left corner.
|
||||
// NEO_TILE_ROWS, NEO_TILE_COLUMNS: the matrices in the OVERALL DISPLAY
|
||||
// are arranged in horizontal rows or in vertical columns, respectively;
|
||||
// pick one or the other.
|
||||
// NEO_TILE_PROGRESSIVE, NEO_TILE_ZIGZAG: the ROWS/COLUMS OF MATRICES
|
||||
// (tiles) in the OVERALL DISPLAY proceed in the same order for every
|
||||
// line, or alternate lines reverse direction; pick one. When using
|
||||
// zig-zag order, the orientation of the matrices in alternate rows
|
||||
// will be rotated 180 degrees (this is normal -- simplifies wiring).
|
||||
// See example below for these values in action.
|
||||
// Parameter 7 = pixel type flags, add together as needed:
|
||||
// NEO_RGB Pixels are wired for RGB bitstream (v1 pixels)
|
||||
// NEO_GRB Pixels are wired for GRB bitstream (v2 pixels)
|
||||
// NEO_KHZ400 400 KHz bitstream (e.g. FLORA v1 pixels)
|
||||
// NEO_KHZ800 800 KHz bitstream (e.g. High Density LED strip)
|
||||
|
||||
// Example with three 10x8 matrices (created using NeoPixel flex strip --
|
||||
// these grids are not a ready-made product). In this application we'd
|
||||
// like to arrange the three matrices side-by-side in a wide display.
|
||||
// The first matrix (tile) will be at the left, and the first pixel within
|
||||
// that matrix is at the top left. The matrices use zig-zag line ordering.
|
||||
// There's only one row here, so it doesn't matter if we declare it in row
|
||||
// or column order. The matrices use 800 KHz (v2) pixels that expect GRB
|
||||
// color data.
|
||||
Adafruit_NeoMatrix matrix = Adafruit_NeoMatrix(8, 8, 6, 1, PIN,
|
||||
NEO_TILE_TOP + NEO_TILE_LEFT + NEO_TILE_ROWS + NEO_TILE_PROGRESSIVE +
|
||||
NEO_MATRIX_TOP + NEO_MATRIX_LEFT + NEO_MATRIX_ROWS + NEO_TILE_PROGRESSIVE,
|
||||
NEO_GRB + NEO_KHZ800);
|
||||
|
||||
const uint16_t colors[] = {
|
||||
matrix.Color(255, 0, 0), matrix.Color(0, 255, 0), matrix.Color(0, 0, 255) };
|
||||
|
||||
void setup() {
|
||||
matrix.begin();
|
||||
matrix.setTextWrap(false);
|
||||
matrix.setBrightness(40);
|
||||
matrix.setTextColor(colors[0]);
|
||||
}
|
||||
|
||||
int x = matrix.width();
|
||||
int pass = 0;
|
||||
String scroll_text = "OMOBI-Ortsbus ... ab Juni 2020 EINFACH einsteigen!!!";
|
||||
|
||||
void loop() {
|
||||
matrix.fillScreen(0);
|
||||
matrix.setCursor(x, 0);
|
||||
matrix.print(scroll_text.c_str());
|
||||
if(--x < (int)(-6*scroll_text.length())) {
|
||||
x = matrix.width();
|
||||
if(++pass >= 3) pass = 0;
|
||||
matrix.setTextColor(colors[pass]);
|
||||
}
|
||||
matrix.show();
|
||||
delay(100);
|
||||
}
|
11
vscode/OmobiLEDdisplay/test/README
Normal file
11
vscode/OmobiLEDdisplay/test/README
Normal file
|
@ -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
|
Loading…
Reference in a new issue