[The best place to ask support questions is in our Slack community.]
The following is a table of configuration properties used by Dronesmith Engine on initialization. You can modify the existing installation's configuration variables by modifying
/opt/dsengine/config.json on the Edison in your Luci.
Flight controller address, as either a UDP Address or serial device path.
Note: The flight core's device path is
/dev/ttyMFD1 on the Edison.
Create outputs for other apps to connect to the flight core. Outputs allow you to receive and send MAVLink data to the flight controller through an external app, such as a GCS.
Address which the status page will serve to. Should be in <IP>:<Port> format.
Address to communicate with cloud.dronesmith.io. Should be in <IP>:<Port> format, although DNS names are permitted.
Address to communicate with cloud.dronesmith.io via its REST API. Should be in <IP>:<Port> format, although DNS names are permitted.
Path to files for initial setup on Luci.
Path to static assets used for serving the UX, among other things.
Path to store flight log data before it is uploaded to the cloud.
Update time period to sync flight data to cloud and to local files. Time units are in milliseconds.
Disables flight logging. Use this to avoid syncing flights to the cloud, useful in bandwidth limited scenarios.
Specify a remote UDP address. Required for certain datalinks, such as virtual or simulated drones that use dual ports for MAVLink communication.
Logging file path and name.
Suppresses console logging if true.