How to Remotely Change the Working Mode of Your GPS Tracker

If you’re integrating GPS tracking devices MT710 into your own platform for the first time, you’re likely wondering how to send configuration commands from your server to the tracker—especially when the device is not always online.

This guide will walk you through how downlink commands work and how to design your server to handle them properly, including support for pre-saved commands when devices are in deep sleep mode.

What Are Downlink Commands?

• Downlink commands are instructions sent from your server to the GPS tracker. For example, you might want to change the reporting interval, reboot the device, or modify other settings remotely.
• The MT710 supports various downlink commands when it’s connected to the network. You can find a complete list of supported commands in the Commands List.

Click here to check the MT710 Commands List.

Understanding Sleep Modes and Limitations

The MT710 supports multiple power-saving working modes, such as:

• MODE 0/2/3/4/7/8/9/10

In these modes, the device enters deep sleep to save power. While asleep, it disconnects from the server and cannot receive commands in real time.

This behavior is common in ultra-low-power asset trackers.

Click here to check the MT710 Working Mode

How to Deal with Commands in Deep Sleep Mode

To handle this, we strongly recommend your server supports a pre-save command mechanism.

Here’s how it works:

• Your platform allows the user to send a configuration command even when the device is asleep.
• The command is stored on your server.
• Once the device wakes up and connects to the server, the server should immediately push the pending command.
• We suggest the server sends the command within 30 seconds of device reconnection.

Example Scenario

Let’s say the device is currently working in this mode:

MODE,3,1  → Reports data every 1 hour

But now you want to change it to:

MODE,1,10  → Reports every 10 seconds

Since the device is in deep sleep, it won’t receive the new command right away. Instead:

1. Your server saves the MODE,1,10 command.
2. One hour later, the device wakes up and sends its scheduled GPS report.
3. The server detects the connection and immediately sends the pre-saved command.
4. The device receives the command and updates its mode.

Example Scenario

Each GPS tracker has a unique device ID. Make sure your platform uses this ID to:

• Store commands correctly per device
• Match the command delivery when the device reconnects

Final Thoughts

For developers building custom platforms, this approach ensures reliable remote control of trackers even when they’re operating in low-power modes. A pre-save command system is essential for devices that don’t maintain a constant connection.

By designing your server with these principles in mind, you’ll have a more robust and user-friendly GPS tracking system.

If you have any questions or need a sample server-side implementation, feel free to reach out to us at [email protected].