electron-rare/OSC-to-I2C-PWM-Les-amis-nos-morts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

platformIO update

Browse Source
This commit is contained in:
Clément SAILLANT
2022-10-14 20:41:33 +02:00
parent 0116c38e84
commit ed33f1729d
15 changed files with 289 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
LCD_Servo_calibration/.gitignore
+5
View File
@@ -0,0 +1,5 @@
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch
LCD_Servo_calibration/.vscode/extensions.json
Vendored
+10
View File
@@ -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"
]
}
LCD_Servo_calibration/include/README
+39
View 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
LCD_Servo_calibration/lib/README
+46
View 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
LCD_Servo_calibration/platformio.ini
+19
View File
@@ -0,0 +1,19 @@
; 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:uno]
platform = atmelavr
board = uno
framework = arduino
lib_deps =
kelleyja/WEMOS Motor Shield@^1.0.0
uipethernet/UIPEthernet@^2.0.12
cnmat/OSC@0.0.0-alpha+sha.41b44981e3
adafruit/Adafruit PWM Servo Driver Library@^2.4.1
LCD_servo_calib/LCD_servo_calib.ino → LCD_Servo_calibration/src/LCD_servo_calib.ino
View File
LCD_Servo_calibration/test/README
+11
View File
@@ -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
OSC_I2C_CORBACS/.gitignore
+5
View File
@@ -0,0 +1,5 @@
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch
OSC_I2C_CORBACS/.vscode/extensions.json
Vendored
+10
View File
@@ -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"
]
}
OSC_I2C_CORBACS/include/README
+39
View 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
OSC_I2C_CORBACS/lib/README
+46
View 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
OSC_I2C_CORBACS/platformio.ini
+19
View File
@@ -0,0 +1,19 @@
; 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:teensy41]
platform = teensy
board = teensy41
framework = arduino
lib_deps =
kelleyja/WEMOS Motor Shield@^1.0.0
uipethernet/UIPEthernet@^2.0.12
cnmat/OSC@0.0.0-alpha+sha.41b44981e3
adafruit/Adafruit PWM Servo Driver Library@^2.4.1
OSC_i2C_CORBACS/OSC_i2C_CORBACS.ino → OSC_I2C_CORBACS/src/TEENSY_OSC_i2C_CORBACS.cpp
+22 -19
View File
@@ -1,5 +1,5 @@
/*---------------------------------------------------------------------------------------------------------------------------------------------
OSC to I2C CORBACS Show pour les amis nos morts v0.1a 06/2022 06/2022
OSC to I2C CORBACS Show pour les amis nos morts v0.1a 06/2022 06/2022
https://www.facebook.com/LesAmisNosMorts/
https://lesamisnosmorts.fr/
https://www.youtube.com/watch?v=2guq3Z296mI&list=PLyRucERHaznPcJ69G39vllQ96x3izfdkT
@@ -16,10 +16,10 @@
#define DEBUG 0 // 1 pour activer le debug serie
// ethernet et OSC
// ethernet
#include <SPI.h>
#include <NativeEthernet.h>
#include <EthernetUdp.h>
#include <NativeEthernetUdp.h>
//Use youre mac and ip here---------------------------
byte mac[] = { 0x90, 0xA2, 0xDA, 0x0E, 0x9B, 0x7F };
@@ -36,10 +36,15 @@ const int osc_server_port = 10000;
//----------------------------------------------------
// valeur min et max OSC pour mappage des valeurs vers angle SERVO
#define min_value 0
#define max_value 1000
// I2C et carte PWM(servo)
#include <Wire.h>
#include <Adafruit_PWMServoDriver.h>
@@ -82,12 +87,17 @@ int servo_boot[nb_servo] = {
BOOT0 , BOOT1 , BOOT2 , BOOT3 , BOOT4 , BOOT5 , BOOT6 , BOOT7 , BOOT8 , BOOT9 , BOOT10 , BOOT11 , BOOT12 , BOOT13 , BOOT14 , BOOT15 , BOOT16 , BOOT17 , BOOT18 , BOOT19 , BOOT20 , BOOT21 , BOOT22 , BOOT23 , BOOT24 , BOOT25 , BOOT26 , BOOT27 , BOOT28 , BOOT29 , BOOT30 , BOOT31 , BOOT32 , BOOT33 , BOOT34 , BOOT35 , BOOT36 , BOOT37 , BOOT38 , BOOT39 , BOOT40 , BOOT41 , BOOT42 , BOOT43 , BOOT44 , BOOT45 , BOOT46 , BOOT47 , BOOT48
};
void setup() {
//disable sd card
pinMode(4, OUTPUT);
digitalWrite(4, HIGH);
delay(1);
#ifdef DEBUG
//Debug Mode enable in case DEBUG equal 1
//Serial.begin(115200);
//delay(5000);
//Serial.println("CORBAC I2C START");
#endif
// start the Ethernet connection:
Ethernet.begin(mac, ip);
@@ -119,23 +129,16 @@ void setup() {
}
}
#ifdef DEBUG
//Debug Mode enable in case DEBUG equal 1
Serial.begin(115200);
delay(100);
Serial.println("CORBAC I2C START");
#endif
// print your local IP address:
Serial.print("Arduino IP address: ");
Serial.println(Ethernet.localIP());
Serial.print("OSC Port ");
Serial.println(osc_server_port);
Serial.println("Setup done.");
//Serial.print("Arduino IP address: ");
//Serial.println(Ethernet.localIP());
//Serial.print("OSC Port ");
//Serial.println(osc_server_port);
//Serial.println("Setup done.");
}
OSC_i2C_CORBACS/config.h → OSC_I2C_CORBACS/src/config.h
+7 -10
View File
@@ -1,6 +1,3 @@
/*// -------------------------------------------------------------------------------------------------------------------------------------------*/
// Définition valeur servo, utilisé le fichier excel pour modifier les valeur :
// ---------------------------------------------------------------------------------------------------------------------------------------------*/
#define MIN0 230
#define MAX0 530
#define BOOT0 0
@@ -52,8 +49,8 @@
#define MIN16 220
#define MAX16 510
#define BOOT16 0
#define MIN17 180
#define MAX17 510
#define MIN17 150
#define MAX17 460
#define BOOT17 0
#define MIN18 0
#define MAX18 0
@@ -79,11 +76,11 @@
#define MIN25 0
#define MAX25 0
#define BOOT25 0
#define MIN26 220
#define MAX26 510
#define MIN26 250
#define MAX26 460
#define BOOT26 0
#define MIN27 210
#define MAX27 510
#define MAX27 450
#define BOOT27 0
#define MIN28 100
#define MAX28 240
@@ -106,8 +103,8 @@
#define MIN34 100
#define MAX34 190
#define BOOT34 0
#define MIN35 100
#define MAX35 440
#define MIN35 200
#define MAX35 560
#define BOOT35 -90
#define MIN36 0
#define MAX36 0
OSC_I2C_CORBACS/test/README
+11
View File
@@ -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