Previous
Deploy software
If you have already deployed software, you can inspect the fragment you have created.
The JSON object for the deployed module or package has a version
field.
Unless the version
field is set to a specific version, some or all updates for that module or package can happen automatically.
To update the firmware on your microcontroller, see Over-the-air updates.
You can either use fragment tags for testing or manually overwrite the version of the module or package for a subset of machines. We strongly recommend that you test updates on a subset of machines before deploying it to all machines.
Navigate to your fragment’s page on On your fragment’s page, from the FRAGMENTS tab.
Create a stable
fragment tag.
On your fragment’s page, click on Versions in the menu bar and add a tag called stable
.
Pin all machine configurations to the stable
fragment tag.
For each machine that uses the fragment, update its configuration.
Edit the fragment and change the version of your module or package in the development fragment. This will create a new version of the fragment.
For example:
Create a development tag.
On your fragment’s page, click on Versions in the menu bar and add a tag called development
.
Select the most recent version that you just created for the tag.
Add the development fragment to a subset of machines by pinning the fragment configuration to the development
fragment tag.
For each machine that you want to test the changes on, update the configuration.
Test the new version of your module or package.
Update the stable
fragment tag.
When you are satisfied that your module or package works as expected, set the Version for the stable
fragment tag to the new version.
This will update all machines that use the stable
fragment tag.
Change the version of the module.
You can overwrite parts of a fragment to use a new version of a module or package without modifying the upstream fragment.
For each machine that you would like to test the new version of the module or package on, go to its CONFIGURE tab, find the module or package, and edit its version number.
Click Save in the upper right corner of the screen.
Test the new version of your module or package.
Update the fragment.
When you are satisfied that your module or package works as expected, update your fragment.
For example:
By default, when a fragment is updated, machines using it will automatically update when the configuration is synced next. To ensure that updates only occur when your machines are ready, configure a maintenance window. With a configured maintenance window, configuration updates will only be applied when maintenance is allowed.
To check when your machines have last updated their configuration, iterate over your machines using the Fleet Management API, connect to each machine, and use the GetMachineStatus
method.
The following example script iterates over all machines in a given location and if it can connect to the machines, it prints their status information. If it cannot connect to a machine, it prints the most recent log entries.
Was this page helpful?
Glad to hear it! If you have any other feedback please let us know:
We're sorry about that. To help us improve, please tell us what we can do better:
Thank you!