The serial daemon is used to connect fully-supported devices to Edge Impulse so that data from their on-board sensors can be uploaded directly into Edge Impulse Studio. This is particularly helpful for devices without an IP connection, for which the serial daemon acts as a data upload proxy. You can also use the serial daemon to configure the upload parameters.
The serial daemon is part of the Edge Impulse CLI. In order to use the daemon, you first have to install the CLI.
To use the daemon, connect a fully-supported development board to your computer and run:
The daemon will prompt you to log in, and then configure the device. If your device does not have the right firmware yet, it will also prompt you to upgrade it.
This is an example of the output of the daemon:
You can use one device for many projects. To switch projects run:
And select the new project. The device will remain listed in the old project, and if you switch back will retain the same name and last seen date.
Serial daemon options can be invoked as follows:
--api-key
Enables authentication using a project API key. API keys are long strings of random characters that start with ei_
and can be obtained from the project's dashboard on Edge Impulse Studio. Example:
--baud-rate
Change the rate of the communication between the device and Edge Impulse Studio. Default is 115,200 baud. Example:
--clean
Clears (resets) the daemon and device configurations.
--silent
Skip all wizards (except for the login prompt). This is useful in headless environments where the session token has already been obtained, or authentication is requested via the --api-key
option.
--verbose
Print additional information during execution. Useful for debugging.
--version
Prints the version of the Edge Impulse CLI (and therefore, the serial daemon) installed.
If you are using the ST B-L475E-IOT01A development board, you may experience the following error when attempting to connect to a WiFi network:
There is a known issue with the firmware for this development board's WiFi module that results in a timeout during network scanning if there are more than 20 WiFi access points detected. If you are experiencing this issue, you can work around it by attempting to reduce the number of access points within range of the device, or by skipping WiFi configuration.