Skip to content

Summary

Protocol Port Server command APN command Tested on
teltonika 5027 setparam 2004/2005/2006 setparam 2001/2002/2003 FMB920 and FMB930 tested by us; the rest share the firmware family

Server: trackers.moongpstracker.com (169.58.68.140), TCP. Some firmware refuses domain names — then use the IP.

What it is

FMB, FMC and FMM are Teltonika model families that share a firmware base and therefore a command set: FMB001, FMB003, FMB120, FMB125, FMB130, FMB140, FMB204, FMB209, FMB920, FMB930, FMC130 and FMM130 all take the same setparam string.

What changes between them is the hardware around the modem — OBD plug versus wired harness, 2G versus LTE, ingress protection, CAN interfaces, internal battery size. The way you point one at a server does not change.

Be careful with what we are claiming here: we have tested the FMB920 and the FMB930 on our own vehicles. The others are the same firmware family and the same documented parameter numbers, but we have not put every one of them on a bench. If yours is on that list and behaves differently, tell us and we will correct this page.

What you need

  • A data SIM in the device, and the APN string for that SIM
  • The SIM's phone number for the two SMS below
  • The device IMEI, printed on the case
  • For OBD models (FMB003, FMB001): the vehicle, since the device is powered by the OBD socket

APN examples

The APN belongs to the SIM, not to the tracker. These are the two we use ourselves:

  • 1NCE: iot.1nce.net
  • Truphone: iot.truphone.com

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.

SMS commands

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".

Point the device at Moon (replace <APN> with your SIM APN)
  setparam 2001:<APN>;2002:;2003:;2004:trackers.moongpstracker.com;2005:5027;2006:0

Starts 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.

Make it connect now, without waiting for the next record
  web_connect

Starts 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 it does not show up

The same two questions answer for every model in the family.

Is it online, and on which operator?
  getstatus

Starts 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.

Read back the server it is pointed at
  getparam 2004

Starts 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.

Alternative: Teltonika FOTA WEB

For a fleet already registered in FOTA WEB, push a configuration with trackers.moongpstracker.com port 5027 over TCP as the secondary server and Backup Server Mode "Duplicate". Every record then goes to both the old platform and Moon, which is how a live fleet moves without a cutover date.

What Moon shows you

  • Live position, speed and full trip history with stops and addresses
  • Engine cut and release through a digital output, where the vehicle is wired for it
  • Digital inputs (ignition, alarm loops) as vehicle state and as alert triggers
  • Internal battery and external supply voltage — a disconnected vehicle is visible, not just silent
  • Odometer, engine hours and CAN bus values on the models wired for them

What it does not do

  • Which values you actually get depends on the model and the installation, not on your Moon licence: an FMB001 in an OBD socket cannot report a digital input that is not wired.

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.

Gotchas

The things that cost us time on real vehicles, written down so they do not cost you any.

Same command, different capabilities

The setparam string works across the family, but what the device can then do does not. Engine cut needs a digital output and an installation wired for it; CAN values need a model with a CAN interface and a vehicle that publishes them. Send us the model and how it is fitted and we will tell you what will actually appear in Moon.

Two leading spaces, on every model

The empty SMS login and password fields are a firmware-level convention, so the two leading spaces apply to the whole family. A phone keyboard that trims them turns every command into a no-op.

Factory password

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.

Teltonika FMB, FMC and FMM series: questions we get asked

My model is not in your list. Will it work?
Probably, if it is an FMB, FMC or FMM. The parameter numbers 2001 to 2006 are documented across the family. Send us the model and we will confirm, and open a port for it if it turns out to speak something else.
Which models have you actually tested?
FMB920 and FMB930, on our own vehicles, in daily service. Everything else on this page is the same firmware family and the same documented parameters, but not tested by us — we would rather say that than imply a bench we did not run.
Do I need different ports for different models?
No. Every FMB, FMC and FMM speaks the teltonika protocol and goes to port 5027 on trackers.moongpstracker.com.
Can I keep using FOTA WEB after moving to Moon?
Yes. FOTA WEB is Teltonika's device management and is unaffected by which platform receives the data. Firmware and configuration keep coming from Teltonika; positions come to Moon.

Two ways to go from here

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.