Hardware guide · teltonika · port 5027
Two SMS and the device reports to Moon. The catch that costs people an afternoon is not in the parameters: it is the two spaces the command has to start with.
| Protocol | Port | Server command | APN command | Tested on |
|---|---|---|---|---|
| teltonika | 5027 | setparam 2004/2005/2006 | setparam 2001/2002/2003 | 300+ vehicles in service on this hardware |
Server: trackers.moongpstracker.com (169.58.68.140), TCP. Some firmware refuses domain names — then use the IP.
The FMB920 and FMB930 are compact wired trackers made by Teltonika Telematics in Lithuania. They speak the "teltonika" protocol (Codec 8/8E) over TCP, buffer records when there is no coverage, and are the hardware we fit most often ourselves.
Both are configured the same way: by SMS from any phone, or over the air from Teltonika FOTA WEB. Nothing on this page is specific to a firmware version.
The APN belongs to the SIM, not to the tracker. These are the two we use ourselves:
On both, the APN username and password are empty — which is the usual case on IoT SIMs. If your SIM comes from a mobile operator, ask them for all three values.
Every Teltonika SMS command is prefixed by the SMS login and the SMS password, separated by spaces. On a device with factory settings both are empty — which still means two empty fields, so the command must begin with EXACTLY TWO SPACES. Without them the device receives the SMS and does nothing, silently. This is the single most common reason a Teltonika "does not answer SMS".
setparam 2001:<APN>;2002:;2003:;2004:trackers.moongpstracker.com;2005:5027;2006:0Starts with 2 spaces. Use the Copy button, or check your keyboard has not trimmed them.
Two leading spaces. 2001 is the APN, 2002 and 2003 are the APN username and password, 2004 the server, 2005 the port, 2006 the protocol (0 = TCP). Pass 2002 and 2003 EMPTY rather than leaving them out: omitted, the device keeps the credentials of the previous SIM and never attaches to the network.
web_connectStarts with 2 spaces. Use the Copy button, or check your keyboard has not trimmed them.
Forces an immediate data link. The device should show up in the panel within a minute or two.
After the device is configured it turns up in Unknown devices in the Moon panel — or straight on your map, if you registered its identifier first. The first position normally lands within minutes.
If the device does not appear, these three answers tell you where it stopped.
getstatusStarts with 2 spaces. Use the Copy button, or check your keyboard has not trimmed them.
Answers with Data Link 1/0, GPRS 1/0, the operator code and the SMS counters. Data Link 0 with GPRS 1 means the SIM is on the network but the server or port is wrong.
getparam 2004Starts with 2 spaces. Use the Copy button, or check your keyboard has not trimmed them.
Same for 2005 (port, expect 5027) and 2006 (protocol, expect 0 for TCP). If 2004 comes back as the old server, the setparam never landed — check the two leading spaces first.
If the devices are already in your FOTA WEB account you can push the same change over the air: set the secondary server to trackers.moongpstracker.com port 5027, protocol TCP, and set Backup Server Mode to "Duplicate".
"Duplicate" is worth knowing about during a migration: the device then sends every record to BOTH servers. You can run the old platform and Moon side by side, compare them on real vehicles, and only switch the primary server once you are satisfied.
Which values arrive depends on the device and the installation, never on your licence: every Moon account has the whole platform. See what the platform does.
The things that cost us time on real vehicles, written down so they do not cost you any.
Every command starts with two spaces because the SMS login and password fields are empty on a factory device. Most phone keyboards trim leading spaces on send: check the message before you send it, or paste it from a notes app.
If you drop the APN username and password from the setparam string, the device keeps the values it had. A tracker that used to run on a carrier SIM with credentials will then fail to attach on a plain IoT APN, and you get a device that answers SMS but never connects.
With the fleet configuration we use — a record every 9,600 s when stationary, and 20 records buffered before opening a link — a device that has not moved connects roughly every 53 hours. It is buffering, not broken.
The practical consequence: to command a parked vehicle you use SMS, not GPRS. A GPRS command sits in the queue until the device wakes up.
The two leading spaces stand for the SMS login and password, which are empty on a factory Teltonika. Left that way, the tracker can be reconfigured by anyone who knows its SIM number. Set an SMS login and password in the Teltonika Configurator (they then replace the two spaces at the start of every command), or use SIMs that cannot receive SMS from outside numbers — the 1NCE and Truphone SIMs we ship are set up that way.
Send the commands yourself and register the device in the panel, or tell us what you have and we will confirm what it can do on Moon before you commit to anything.
No account yet? Send us the make and model and we will set the device up on a demo account for you.
Not sure it is the right model? Send it to support@moongpstracker.com and we will tell you before you buy.
The compatibility hub lists every open port against the protocol it serves.
teltonika · port 5027
gt06 (some units: gt02) · port 5023 (gt02 units: 5022)
tk103 · port 5002
h02 · port 5013
h02 · port 5013
watch · port 5093
JT808 / Huabao · port 5015
We use cookies only to measure how the site is used (Google Analytics). No marketing, no profiling. See the cookie policy.