In this article:
Introduction
The Myriota Network Information, known as "network info", is stored in the module to provide essential Myriota constellation data, enabling the module to predict satellite passes and wake up for communication when needed. Starting from SDK 2.0.0, there are two types of network info available: Warm Start and Cold Start, each serving a distinct purpose.
- Warm Start network info is a fully populated version, ready for immediate use by the module to facilitate network participation.
- Cold Start network info, by contrast, does not contain information about the Myriota Network. The module will learn the network info automatically after deployment.
Consequently, the first messages from these two versions may have different latencies. Additionally, because the constellation is dynamic, Warm Start network info can expire over time if the module is left undeployed. After a certain period, it will revert to the Cold Start state, necessitating a refresh from downlink satellites for further communication.
Enabling Warm Start Mode
To set the module to Warm Start mode, obtain the latest Warm Start network info, and deploy the device immediately after programming for best results. There are three ways to access the latest network info:
-
SDK Default Option: Warm Start network info is the default build option in the SDK. When building an application, the SDK automatically merges the application binary with the latest network info. During programming, both the application and network info will be uploaded to the module. The raw network info file can also be found in the
raw_binariesfolder for standalone programming if needed. -
DeviceAssist Tool: Use the Myriota DeviceAssist tool to download the latest network info. Detailed instructions are provided in the DeviceAssist user guide.
-
Direct Download: Access the network info directly via this download link.
Cold Start Triggers
The module may enter Cold Start mode in the following scenarios:
-
Delayed Deployment: If the module is programmed with a fresh Warm Start network info but deployed after the network info has expired, it will revert to Cold Start. The validity of Warm Start network info may vary slightly, but is typically around 8 days.
-
Cold Start Programming: The module is initially programmed with Cold Start network info. This version can be downloaded directly at Cold Start network info.
-
Downlink Timeout: The module does not receive any data from downlink satellites for 72 hours.
Please note that a system reset will not immediately trigger a Cold Start if the module has already acquired the latest network info.
Comparison Table
| Version | Warm Start | Cold Start |
|---|---|---|
| Concept | Full network info available for immediate satellite communication | Blank network info, filled from downlink satellites before communication |
| Default | Yes | No |
| Use case |
- Minimizes startup latency for quick deployments and tests. Requires the latest warm-start network info to be programmed before deployments - Production. It will switch to Cold Start automatically |
- Cold Start performance tests - Production |
| Validity | Typical for 8 days. Module reverts to Cold Start if deployed after this period | No expiration. Once synced, updates occur through downlink satellites |
| Network Info Size | ~ 3 KB | 19 B |
| First Message Latency (Median) | < 3 hours | < 12 hours |
| First Message Latency (P90) | < 8 hours | < 24 hours |
| Download Method | Building a project, Myriota DeviceAssist, or Link | Link |
Network Info Programming
To program the network info onto the module, you can either:
- Run the
updater.py -n [networkinfo_file_name]command (requires SDK installation), or - Use the Myriota DeviceAssist tool.
Notes:
- For SDK 1.x.x: It’s recommended to update the network info before each deployment to avoid potential issues such as poor performance, message loss, or communication loss.
- For SDK 2.0.0 and later: Updating network info is optional and can be based on specific testing and production requirements.