Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found
Select Git revision

Target

Select target project
  • pronto-3/capteur-autonome-penn-avel
1 result
Select Git revision
Show changes
Commits on Source (2)
Showing
with 164 additions and 0 deletions
No preview for this file type
No preview for this file type
{
"files.associations": {
"print": "cpp"
}
}
\ No newline at end of file
No preview for this file type
No preview for this file type
No preview for this file type
; 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:nodemcuv2]
platform = espressif8266
board = nodemcuv2
framework = arduino
upload_speed = 115200
monitor_speed = 115200
lib_deps =
lewapek/Nova Fitness Sds dust sensors library@^1.5.1
#include <Arduino.h>
#include <SoftwareSerial.h>
#include "SdsDustSensor.h"
// Définition des broches pour le SDS011 (sur ESP8266)
#define RX_PIN 14 // GPIO14 = D5 (RX de l'ESP, donc relié au TX du SDS011)
#define TX_PIN 12 // GPIO12 = D6 (TX de l'ESP, donc relié au RX du SDS011)
// Création du port série logiciel pour le capteur SDS011
SoftwareSerial SDS_Serial(RX_PIN, TX_PIN); // RX, TX
// Objet SDS011
SdsDustSensor sds(SDS_Serial);
void setup() {
Serial.begin(115200); // Moniteur série USB
SDS_Serial.begin(9600);
sds.begin();
Serial.println("SDS011 Initialisé !");
Serial.println(sds.queryFirmwareVersion().toString());
Serial.println(sds.setActiveReportingMode().toString());
Serial.println(sds.setContinuousWorkingPeriod().toString());
}
void loop() {
PmResult pm = sds.readPm();
if (pm.isOk()) {
Serial.print("PM2.5 = ");
Serial.print(pm.pm25);
Serial.print(" µg/m³, PM10 = ");
Serial.print(pm.pm10);
Serial.println(" µg/m³");
Serial.println(pm.toString());
} else {
Serial.print("Erreur de lecture SDS011 : ");
Serial.println(pm.statusToString());
}
delay(1000);
}
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch
{
// 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"
]
}
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 convention is to give header files names that end with `.h'.
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
This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into the executable file.
The source code of each library should be placed in a separate directory
("lib/your_library_name/[Code]").
For example, see the structure of the following example libraries `Foo` and `Bar`:
|--lib
| |
| |--Bar
| | |--docs
| | |--examples
| | |--src
| | |- Bar.c
| | |- Bar.h
| | |- library.json (optional. for 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
Example contents of `src/main.c` using Foo and Bar:
```
#include <Foo.h>
#include <Bar.h>
int main (void)
{
...
}
```
The PlatformIO Library Dependency Finder will find automatically dependent
libraries by scanning project source files.
More information about PlatformIO Library Dependency Finder
- https://docs.platformio.org/page/librarymanager/ldf.html