Table of Contents
This document describes the internals of the embeNET demo application running on NUCLEO-WL55JC boards and provides information on how to modify and extend the demo.
How does the demo application work
The demo application uses the embeNET Node C API library to join the network and run two network services:
- ENMS: embeNET Network Management service that allows to gather information about the network operation from the nodes
- custom exemplary service, that sends out a simple message every 5 seconds and also reacts to some simple messages
Below is a short explanation of all important steps. Basically the whole application fits into the main function.
Initialization
The initialization part configures STM32 HAL, system clock, GPIOs and USART1:
Next we configure the logging facility of the embeNET:
Next the embeNET stack is initialized:
After that the ENMS service is initialized:
In case of root we just start it:
In case of nodes we start the custom demo service and MQTT-SN service:
Joining the network
In order to join the network the node has to setup the required network configuration:
The main loop
The application's main loop consists of a call to:
- embeNET Node processing function
- MQTT-SN service process (only needed for polling button status)
Network join event
Once the node joins the network an event callback will be called. In our demo application this callback simply starts the network services:
Network leave event
In case when node gets disconnected from the network, another callback is called. In our demo application this callback stops the network services:
Handling critical errors
In cases when the embeNET stack detects a critical condition, the following handler is called by the stack, giving a chance to react:
Customizing and extending the demo application
The structure of the firmware project embenet_demo_cubeide is mostly generated by STM32CubeMX application. The source *.ioc* file is included in the project. This allows you to easily customize the peripherals for your demo project as needed.
>The only requirement is NOT to change configuration of peripherals used by the port implementation, i.e. RADIO, CRYP, TIM2.
Writing or extending a custom network service.
The best starting point is to look at implementation of the existing custom_service.
Disabling "zero rule"
In order to disable the "zero rule", delete the rule with "uid": 0,
from your config.json file, and add appropriate rules for your nodes, for example:
This will allow only nodes with uid = 2 and 3, to join the network, provided that their PSKs match those from config.json file.
Using custom name for network interface
You may specify the name of desired network interface in .json file, by adding on root level:
Limitations of embeNET demo application
The demo version of the embeNET stack allows to connect up to 10 nodes only, with network depth of max. 3 hops.
Generated on Mon Dec 4 2023 14:00:05 for Getting started with embeNET demo for NUCLEO-WL55JC board by 1.9.8