The Third-party Platforms Compatible with Mictrack

Admin

Mictrack GPS Tracking devices have full compatibility with the following third-party platforms, if you choose one of them please select the related port to connect to your server.

Platform Port Supported Devices
Gurtam 22127 MT710/MT700
Flespi MT710/MT700
Traccar 5030 MT710/MT700/MT600/MP90
Traccar 5013 MT532/MP91/MC350
Navixy 47717 MT710/MT700/MT600/MP90
GPS-Server 11214 MT710/MT700/MT600/MP90
GPSWOX 6030 MT710/MT700/MT600/MP90
GPSWOX 6013 MT532/MP91/MC350
GpsGate 40299 MT710/MT700
GPS trace 30184 MT710/MT700/MT600

You can also download the protocols from this link: https://help.mictrack.com/articles/protocols/

halloonkel

Hello,
we are interest to buy some MT710.

Did you test it with GPS-Server.net?
Can you confirm if it is working or not?
Thanks

Garin

halloonkel We know the MT700 is compatible with GPS-Server.net, and the port is 11214. The MT710 protocol is similar to the MT700, so it should also work on GPS-Server. If needed, we can send a sample to point to your server for testing. Please share your IP here or email us your IP at info@mictrack.com.

halloonkel

Hello,
please point the device to IP: 79.98.27.103
Port as you write: 11214

Please give me the IMEI so I can insert the device.

Thanks

Garin

halloonkel Can you please add this device ID 865640063550245 to your server for the new test? Please make sure the server IP is 79.98.27.103. Once confirmed, we will set it up on your server and start the test.

Garin

The device ID is 862255061984701

halloonkel

I add the device.

Garin

Connected to the server.

Image description

halloonkel

It is only now. Can you let it run a while to check if the battery voltage will show correctly?
How can I contact you for an order?

The battery voltage is shown as 4,189 is that correct?

Garin

halloonkel Sure, we will make it run for few hours, and for the battery voltage into percentage you can check this post: https://help.mictrack.com/articles/how-to-calculate-battery-voltage-into-percentage-for-mictrack-devices/

You can order the sample from our online shop: https://shop.mictrack.com/product/catm1-nbiot-gps-tracker-mt710/

Garin

halloonkel voltage 4189 means 4.189V
Image description

halloonkel

The battery working time till it was empty was only around 12 hours. You write:
In our local test in MODE 1 with 60 seconds interval, the battery life up to 39 hours. Of course, in our test environment, both the GPS and network signals are good.

Can you please check if the 12 hours was correct?

Garin

halloonkel i am simply testing whether we can connect to the GPS-server platform. We will reconfigure and test the device again next week.

mahou-anisphia

Hello, I’m currently running the MT-700 in Vietnam and encountered the following set of problems

When inside the building, the device stopped the GPS tracking, which is due to lack of GPS signals, but when bring it outside, it took 8 minutes until the “green light” signaling GPS finally turned on.
After the GPS light turn on, the data sent to the server is invalid data (NULL Lat / longitude values). And it keep sending null data for 18 minutes, and didn’t stop sending null despite GPS is available unless I restart the device manually by turn it off and on.
After I restart the device, the GPS works just fine but only for the first time. All the following report, it send us the “last position” as “current valid position”, I realized by reading the UTC time value of the report. Somehow, even with GPS and I was running outside, the device just won’t update its location. Hopefully I can get a reply for my problems.
Here’s my configuration:
<CFG>:NET:TCP
GU:MT700,0000
UP:0000
SRV:IP,myserverIPAddress,myPortAddress
APN:nbiot,,
NWM:3,1,3
M1:ANY
NB1:3
GSM:ANY

<CFG>:ID:860186054704537
DBG:OFF
HBC:5m
LEP:ON
LTP:ON
TZ:0
EDRX:0,5,0010
ANGLE:0,0,0
GSE:70,70,2,187
MODE:0,60s,8h,1,0

<CFG>:ISSUED:22/10/22
MODEL:MT700
SVER:V2.0.5
HVER:V2.0.0
GMR:BG96MAR04A05M1G
LICENSE:OK
ODM:Mictrack
AUTHOR:Darren
IN:linkedin.com/in/imdarren

Garin

mahou-anisphia Please ensure that your APN is correct. We also recommend locking to NB-IoT with 2G fallback, so if NB-IoT is unavailable, it can switch to 2G.

Additionally, if possible, please try to upgrade the firmware to the latest version. Your current version is from two years ago, and there have been many upgrades since then.