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.Documentation Index
Fetch the complete documentation index at: https://docs.edgeimpulse.com/llms.txt
Use this file to discover all available pages before exploring further.
Recent versions of Google Chrome and Microsoft Edge can connect directly to fully-supported development boards, without the serial daemon. See this blog post for more information.
Getting Started
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:Note: Your credentials are never stored. When you log in, the serial daemon exchanges your credentials for a session token, which is used to further authenticate requests.
Switching projects
You can use one device for many projects. To switch projects run:Running
--clean resets both the daemon configuration and the on-device configuration. If you run into issues, you can connect to the device using a serial console (with a baud rate of 115,200) and send the AT+CLEARCONFIG command to the device, to remove its configuration.Command Options
Serial daemon options can be invoked as follows:API authentication --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 --baud-rate
Change the rate of the communication between the device and Edge Impulse Studio. Default is 115,200 baud. Example:
Clear Configuration --clean
Clears (resets) the daemon and device configurations.
Silent mode --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.