Skip to content
Snippets Groups Projects
Commit 352d03e0 authored by Zoe Pfister's avatar Zoe Pfister :speech_balloon:
Browse files

remove client code from host directory

parent 367974c7
No related branches found
No related tags found
5 merge requests!39Merge Develop into Main,!19development into master,!17Inital Host, initial Client,!3Merge Branch `develop` into `sensor_readout`,!1Espnow
.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 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
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
#include <esp_now.h>
#include <esp_wifi.h>
#include "espnow.hpp"
#include "WiFi.h"
#include <ESP32Time.h>
uint8_t BROADCAST_MAC[] = {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF}; // leaving this in as possible backup
esp_now_peer_info_t hostInfo;
ESP32Time rtc;
void on_data_sent(const uint8_t *mac_addr, esp_now_send_status_t status){
Serial.println((String) "Message sent: " + status);
}
void on_data_recv(const uint8_t *mac, const uint8_t *incomingData, int len){
data_struct lastData;
memcpy(&lastData, incomingData, sizeof(lastData));
Serial.println("message copied");
Serial.println((String) lastData.values[0]);
Serial.println((String) "sent time: " + lastData.timestamp);
Serial.println((String) "RTC time: " + rtc.getMillis());
Serial.flush();
}
esp_err_t espnow_setup(){
esp_err_t result;
WiFi.mode(WIFI_STA);
result = esp_now_init();
if(result != ESP_OK){
//initialization failed
return result; // not sure about this
}
memcpy(hostInfo.peer_addr, BROADCAST_MAC, sizeof(BROADCAST_MAC));
hostInfo.channel = 0;
hostInfo.encrypt = 0;
esp_now_add_peer(&hostInfo);
esp_now_register_recv_cb(on_data_recv);
esp_now_register_send_cb(on_data_sent);
return ESP_OK;
}
Message :: Message(){
memcpy(recipient, BROADCAST_MAC, sizeof(BROADCAST_MAC));
config = (config_struct*) malloc(sizeof(config_struct));
esp_wifi_get_mac(WIFI_IF_STA, config->host);
config->time_millis = rtc.getMillis();
}
esp_err_t Message::send(){
return esp_now_send(recipient, (uint8_t *) &config, sizeof(config));
}
\ No newline at end of file
#ifndef _ESPNOW
#define _ESPNOW
#define NUM_SENSORS 10
typedef struct data_struct{
int identifiers[NUM_SENSORS];
float values[NUM_SENSORS];
int amountData;
long timestamp; //maybe make this array
}data_struct;
typedef struct config_struct{
uint8_t host[6];
long time_millis;
}config_struct;
class Message{
public:
Message();
esp_err_t send();
uint8_t recipient[6];
private:
config_struct *config;
};
esp_err_t espnow_setup();
#endif
\ No newline at end of file
; 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:esp32-c3-devkitm-1]
platform = espressif32
board = esp32-c3-devkitm-1
framework = arduino
monitor_speed=115200
lib_deps = fbiego/ESP32Time@^2.0.0
#include <Arduino.h>
#include <esp_wifi.h>
#include "WiFi.h"
#include "espnow.hpp"
void setup() {
// put your setup code here, to run once:
Serial.begin(115200);
while(!Serial);
Serial.flush();
espnow_setup();
}
int counter = 0;
void loop() {
// put your main code here, to run repeatedly:
if(counter++ % 10 == 0){
Message* msg = new Message;
msg->send();
delete msg;
}
Serial.println("No message...");
delay(1000);
}
\ No newline at end of file
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
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment