Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

Current Configurator and firmware versions

On this page

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

...

Common FMB resources

FMB AVL ID

https://wiki.teltonika.lt/view/FMB_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.

...

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.

compatible tracking servers

Teltonika mobile applications (app's)

application stores

...