...

FM series

• FMA: 2G (discontinued 2018)
• FMB: 2G + Bluetooth
• FMU: 3G
• FMM: LTE M1
• FMC: LTE

Current Configurator and firmware versions

On this pagepages

https://wiki.teltonika.lt/view/Teltonika_Configurator_versions

https://wiki.teltonika-gps.com/view/Firmware_versions

you find:

• current configurator version;
• current configurator file;
• current firmware version.

Please contact store@mirifica us for current firmware file download.

Teltonika FOTA WEB

We recommend to add all compatible devices to Teltonika FOTA WEB to ease device monitoring and just in case debug.

Devices supported by Teltonika FOTA WEB (as of 2019-03):

• FM3001
• FMB0yx
• FMB1yx
• FMB2yx
• FMB640
• FMB9yx

Devices NOT supported by Teltonika FOTA WEB (as of 2019-03):

• FM3xxx (apart from FM3001)
• FM6xxx
• FMB630

Devices sold by Mirifica can be added to Teltonika FOTA WEB by Mirifica easily. Please contact store@mirifica and provide the following details:

• details needed for new FOTA WEB users (in the message body):

  • FOTA WEB company name

  • FOTA WEB admin electronic address

• details needed for existing FOTA WEB users:
  one of the following two lists of devices to add to FOTA WEB (as an attached .csv file):
  • IMEI, one per text line;
  • serial number, one per text line.

Devices sold by Mirifica's competitors can be added to Teltonika FOTA WEB by Mirifica only after the device owner has got clearance from Teltonika.Release versions:

• FMB firmware errata
• FMB640 firmware errata
• TMT250 firmware errata 

Download .net for Windows

• https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-5.0.17-windows-x64-installer - x64-Version, 64-Bit
• https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-5.0.17-windows-x86-installer - x86-Version, 32-Bit
• https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Common FMB resources

• FMB AVL ID
• FMB Device Family Parameter list
  • https://wiki.teltonika.lt/wiki/index.php?title=FMB_Device_Family_Parameter_list
  • https://wiki.teltonika.lt/view/Template:FMB_Device_Family_Parameter_list
• FMB SMS/GPRS Commands
• SMS over GPRS (Codec 12)
• Codec's (Codec 8, Codec 8 Extended, Codec 12, Codec 13, Codec 16)

FMB AVL ID

https://wiki.teltonika-gps.ltcom/view/FMBTeltonika_Data_AVLSending_IDProtocols

• No. = old AVL ID (dismissed)
• Property ID = new AVL ID

All of the AVL ID's that are above 255 need to use Codec 8 Extended instead of Codec 8. The reason being, that Codec 8 AVL ID's have 1 Byte (Maximum value 255), while Codec 8 Extended has 2 Bytes for AVL ID's (Maximum value 65535). Also Codec 8 Extended can have variable size I/O elements.

compatible tracking servers

...

• basic: https://portal.simpletrack.at/
• pro: https://fleet.simpletrack.at/
• web: https://simpletrack.at/
• shop: https://shop.simpletrack.at/
• mobile:
  • Android
  • iOS

...

• Teltonika Wiki: Supported third party platforms (Fleet Management)
• Teltonika Wiki: Fleet Management platforms
• The 5 Best Free and Open Source Fleet Management Software Programs

Teltonika mobile applications (app's)

application stores

...

• by Taltonika
• by Taltonika - Pakistan

...

Record and packet size

An AVL record contains basic AVL data. An AVL packet conveys one or more AVL records. An AVL packet is sent trough the cellular network as a cellular packet.

AVL record size:

• minimum: 45 bytes (all IO elements disabled);

• maximum: 783 bytes.

AVL packet size:

• minimum: 1 record;
• maximum: 1 kbyte (for FMB devices).

Most cellular network operators have a minimum billed packet size of 1 kbyte.

The cheapest way to set up the device would be to send as many records as they fit in a maximum size packet 81 kbyte).

Typical data consumption

Cellular data consumption depends on cellular network operator (tariff in home/roaming, what is charged and what is not). For example - some operators take extra fee for data session establishment; in this case, customers configure devices to hold a session open for all the time the vehicle is driving.

It also depends on how often device will send data, so configuration also matters.

Sending protocol:

• TCP uses different amount of data (headers, confirmations etc.);
• UDP uses about 3 times less traffic data then TCP.

So it is possible to have 2-3 Mb per month, or 10-15. All depends on your application and requirements.

How to capture remote log from FM device?

• https://wiki.teltonika.lt/view/How_to_capture_remote_log_from_FM_device%3F