...
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.
Release versions:
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
...
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 supported by Teltonika FOTA WEB (as of 2019-03):
- FM3xxx (apart from FM3001)
- FM6xxx
- FMB630
...
- FMB SMS/GPRS Commands
- SMS over GPRS (Codec 12)
- Codec's (Codec 8, Codec 8 Extended, Codec 12, Codec 13, Codec 16)
| Note | ||
|---|---|---|
| ||
Not all FM parameters are documented by Teltonika all the time. Some parameters may be present only in your latest Teltonika Configurator at the beginning. |
FMB AVL ID
https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols
- 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.
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.