449d2a6367
Contains two different component folders per each implementation (serial_master and serial_slave) with concrete ports. Added common public api for master and slave and common interface for master and slave implementation. Add support of cmake system (added cmake files). Added sdkconfig.defaults files for slave and master modbus examples. Updated make file and KConfig for freemodbus component Update according to review and fix doxygen warnings Fix Doxyfile to pass documentation build Update headers and change interface file names as per review comments Merge branch feature/freemodbus_move_rs485_mode_control Update after review: The stack modbus folder updated to support master and slave ports together and moved into freemodbus/modbus Stack and port files updated to remove duplicated simbols Make file, KConfig and CMakeLists.txt updated to compile master and slave stacks, common interface and concrete implementations of ports Stack callback functions execute callbacks using interface pointer from concrete port implementation User can instantiate any of concrete port using common API (only one concrete port at a time) and it does not require to select port by KConfig Port pins and mode configuration moved into example files from port files to allow user select pins and port mode (customer request) Changes tested using pymodbus, ModbusPoll and communication between two boards Updated DoxyFile according to public include path Fix maximum instance size for slave (merge from master of customer issue) Fix critical section issue TW#28622 (change spin lock based critical section to semaphore) Move serial port files into component port folder for master and slave accordingly Fix example issue showed in the log when IO slave is not configured correctly Fix conflicts while merging from origin/master Fix errors handling in modbus controller interface + some final corrections according to review Update maximum allowed number of slaves in the network segment Fix bug with incorrect coils read mask Closes https://github.com/espressif/esp-idf/issues/858 |
||
---|---|---|
.. | ||
bluetooth | ||
build_system | ||
common_components/protocol_examples_common | ||
ethernet | ||
get-started | ||
mesh | ||
peripherals | ||
protocols | ||
provisioning | ||
storage | ||
system | ||
wifi | ||
README.md |
Examples
This directory contains a range of example ESP-IDF projects. These are intended to demonstrate parts of ESP-IDF functionality, and to provide code that you can copy and adapt into your own projects.
Example Layout
The examples are grouped into subdirectories by category. Each category directory contains one or more example projects:
bluetooth
contains Bluetooth (BLE & BT Classic) examples.ethernet
contains Ethernet examples.get-started
contains some very simple examples with minimal functionality.mesh
contains Wi-Fi Mesh examples.peripherals
contains examples showing driver functionality for the various onboard ESP32 peripherals.protocols
contains examples showing network protocol interactions.storage
contains examples showing data storage methods using SPI flash or external storage like the SD/MMC interface.system
contains examples which demonstrate some internal chip features, or debugging & development tools.wifi
contains examples of advanced Wi-Fi features. (For network protocol examples, seeprotocols
instead.)build_system
contains examples of build system features
Using Examples
Building an example is the same as building any other project:
- Follow the Getting Started instructions which include building the "Hello World" example.
- Change into the directory of the new example you'd like to build.
make menuconfig
to configure the example. Most examples have a project-specific "Example Configuration" section here (for example, to set the WiFi SSID & password to use).make
to build the example.- Follow the printed instructions to flash, or run
make flash
.
Copying Examples
Each example is a standalone project. The examples do not have to be inside the esp-idf directory. You can copy an example directory to anywhere on your computer in order to make a copy that you can modify and work with.
The IDF_PATH
environment variable is the only thing that connects the example to the rest of ESP-IDF.
If you're looking for a more bare-bones project to start from, try esp-idf-template.
Contributing Examples
If you have a new example you think we'd like, please consider sending it to us as a Pull Request.
In the ESP-IDF documentation, you can find a "Creating Examples" page which lays out the steps to creating a top quality example.