MT710 firmware/backend architecture

lorycala

Hello Mictrack team,

We are evaluating the MT710 for a pet-tracking product and we need a few technical clarifications to finalize our firmware/backend architecture and battery-life claims.

Could you please confirm the following points with as much precision as possible?

MODE 7 actual current consumption

What is the real average current draw of MODE 7 for:

T1 = 5 minutes

T1 = 10 minutes

Is the average consumption closer to MODE 2 benchmark values or does MODE 7 use a more efficient duty cycle?

If available, please share measured current values in mA for real-world operation, not only theoretical estimates.

MODE 3 and 48-hour timer support

Does the MT710 firmware truly support a 48-hour interval in MODE 3 / Deep Sleep?

If we send MODE,3,password,48, is this fully supported by the firmware?

Or is the effective maximum interval limited to 24 hours due to PSM / network timer constraints?

Please confirm whether T3412 or the equivalent internal sleep timer can really reach 48 hours on this device.

SMS command behavior in deep sleep

In MODE 3, can the tracker receive and process the SMS command WHERE0000 immediately while in deep sleep/PSM?

Or is the SMS processed only at the next scheduled wake-up?

If instant SMS reception is not possible in MODE 3, is MODE 6 (SMS Only) required for immediate SMS response?

Heartbeat command interaction

If we configure HBC with a 12-hour interval while the device is in MODE 7 or MODE 8, does the heartbeat generate an additional network transmission that increases battery consumption?

Or is HBC simply synchronized with the active reporting logic of the current mode?

In other words: does HBC add extra current usage beyond the selected working mode?

Battery benchmark validation

Your public materials mention very long standby life and very low current in deep sleep.

Do you have any instrumented real-world test data measured on the MT710 hardware itself?

For example, current measurements made with a power analyzer such as Nordic PPK2 or an equivalent instrument?

If yes, could you share the measured standby current and the exact test conditions?

Clarification on published battery-life claims

Your published battery-life figures are very useful, but we need to validate them against our own product claims.

Could you confirm whether the published standby numbers assume:

a specific network condition,

a specific SIM/operator,

GPS on or off,

heartbeat enabled or disabled,

and which exact working mode was used in the test?

These points are important for us because we want to design a product that is both battery-efficient and reliable for end users.

Garin

lorycala Hi, @lorycala

Thanks for reaching out. Detailed answers below:

POWER CONSUMPTION IN MODE 7

MODE 7 reporting interval is 10–1440 minutes when moving, and 1–24 hours when stationary. The minimum interval is 10 minutes.

At a 10-minute interval with 2 hours of daily movement:

Active consumption: 5.58 mA
Sleep consumption: 4.5 µA

Average daily draw:
(5.58 mA × 2h + 4.5 µA × 22h) / 24h
= (11.16 mAh + 0.099 mAh) / 24h
= 0.469 mA

With a 650mAh battery:
650 mAh / 0.469 mA = 1,386 hours = 57.8 days

Accounting for battery self-discharge (×80%): approximately 49 days.

MODE 3 AND 48-HOUR INTERVAL

MODE 3 supports 1–24 hour intervals only — 48 hours is not available.

At a 24-hour interval in MODE 3, average consumption is 98.99 µA. Full breakdown here:
https://www.mictrack.com/downloads/Mictrack_MT710_Battery_Life.pdf

SMS BEHAVIOR IN DEEP SLEEP

In MODE 3, the device cannot receive SMS while in sleep mode. SMS is only received when the device is already awake — and importantly, commands sent during sleep are not queued or delivered later when the device wakes up. They are simply lost.

So to send a command successfully, the device must be awake at the time of sending. This is not limited to MODE 6 — any mode where the device is awake will work.

HEARTBEAT (HBC)

HBC applies only to MODE 2 and MODE 5. Other working modes do not use heartbeat, so there is no additional transmission or battery impact in MODE 7 or MODE 8.

TEST CONDITIONS

All figures come from real measurements taken in our office using a low-power analyzer, not theoretical estimates. Test conditions:

GPS and network signal: good
Network: China Mobile NB-IoT, eDRX disabled
Temperature: 25°C
Positioning priority: GPS first (searches up to 2 minutes; if GPS unavailable, falls back to WiFi, then LBS)
Modes tested: MODE 0, MODE 2, MODE 3, MODE 7

Happy to share the full measurement data by email if that would help your validation.

lorycala

no news on this topic?

Garin

By the way, you can check our real-world test data with one report per day in MODE 3 here:
https://forum.mictrack.com/public/d/7-mictrack-mt710-battery-life-real-test