How do I send Bulk GPRS Commands

How do I send Bulk GPRS Commands

Overview

The Bulk GPRS Commands feature allows you to send a single command to multiple devices at once. This is useful for actions like updating firmware, changing timezones, resetting odometers, or pushing configuration updates etc.


Steps to Send Bulk GPRS Commands

1. Navigate to Bulk Commands

  • Log into your White Label Tracking portal.

  • From the left menu, go to Modules → GPRS Commands.

  • Select the Bulk Commands tab


2. Select Clients

  • In the Clients panel, choose the client(s) whose devices you want to target.

  • You can tick Select All to include every client, or pick a specific client (e.g., Parallel_Solutions).


3. Choose Device Models

  • In the Device Models panel, select the model(s) you want to send commands to (e.g., Howen Hero-ME40-04 or Teltonika FMB920).

  • Filtering by model ensures the command matches supported devices.


4. Select Devices

  • In the Devices panel, select the individual devices.

  • You can tick Select All to apply the command to every device under the chosen client(s) and model(s).


5. Choose the GPRS Command

  • In the GPRS Command panel, search or scroll to find the desired command. Examples:

    • Update odometer → resets or adjusts odometer values.

    • Update timezone → synchronizes device time settings.

    • Firmware update → upgrades devices to the latest software version.

  • Click to select the command.


6. Send the Command

  • Once your selection is complete, click Send command to selected assets.

  • The system will queue and dispatch the command to all selected devices.


Monitoring Command Status

  • Go to Commands History (tab next to Bulk Commands).

  • Track delivery status:

    • Sent → Successfully dispatched.

    • Pending → Waiting for device connection.

    • Failed → (prolonged pending state ) Device unreachable or invalid command.


 Notes & Best Practices

  • Always confirm the device model supports the command before sending.

  • For sensitive actions (e.g., firmware updates), test on a small group first.

  • If devices are offline, commands will remain pending until they reconnect.