© Felix Rome / Mara Predator Conservation Program
INVENTA
With Iridium, IoT and GSM the configuration of the devices can be changed remotely by sending a command. The delivery of remote commands to Vectronic devices follows an asynchronous communication loop. Since devices operate in energy-saving modes, commands are not pushed instantly but are queued until the next scheduled device transmission.
That means when you send a remote command, it is not delivered instantly. Because the collar stays in energy-saving mode to conserve battery, the collar only checks for and downloads new commands during its next scheduled data transmission.
Here is a diagram showing the general message flow with status descriptions:
1. Command Creation: The user configures a command in INVENTA and submits it to the Vectronic servers.
2. Validation & Encoding: The Vectronic servers validate, store, and encode the command before forwarding it to the provider.
Provider Timeout & Retries: Commands are limited by the provider’s queue timeout. If a command times out before device retrieval, Vectronic servers automatically renew the command for 10 days until it expires.
3. Provider Queuing: The provider queues the encoded command, where it waits for the device’s next transmission.
4. Device Check-In: When the device initiates its next scheduled data transmission, the provider automatically checks its queue for pending commands for this specific device.The device decodes and execute the command
5. Command Delivery: If a pending command is found, the provider attaches it to the downlink response of the current transmission and sends it to the device.
6. Execution: The device decodes and executes the command locally.
7. Acknowledgment (Handshake): Upon successful execution, the device sends a confirmation status back to the provider during its next transmission window to signal that the command has been successfully applied.
8. Data Forwarding: The provider forwards the incoming transmission—including the device’s command acknowledgment—to the Vectronic servers.
9. Status & Config Update: The Vectronic servers process the acknowledgment, update the final command status (e.g., Acknowledged), and refresh the device’s configuration footprint in INVENTA.
Remote Command status descriptions
| Status | Description |
| Created | The command has been generated in INVENTA and is awaiting transmission to the communication provider. |
| Sent | The command has been sent from the server to the communication provider and is ready for pickup by the device on its next check in. |
| Acknowledged | The device has processed the command and sent a confirmation back to the server, verifying that the configuration changes have been applied. |
| Failed/Expired | The command could not be delivered for 10 days or was rejected by the device (e.g., due to invalid parameter ranges). |
| Canceled | The user canceled the command. This does not remove open commands in the queue of the provider. |
Applies to Iridium, IoT, and GSM remote commands. (excluding Globalstar)
Globalstar is a one-way communication. So device transmits to the satellite but cannot receive commands.
Good to know:
Using the latest Collar firmware optimizes the protocols for reduced data costs by bundling multiple configuration changes into a single compact binary command.
Related Articles:
• Send Remote Commands