Teltonika Telematics Wiki - User contributions [en]

Template:FMB640 RS-232 and RS-485

2022-02-09T13:27:46Z

Renat Galiachmetov:

==RS-232 / RS-485 interface==
RS-232 supports only full-duplex communication, which means the data can be sent and also received at the same time. 
'''Note:''' In RS-232 LLS mode can be connected only one LLS fuel level sensor. 

RS-485 supports only half-duplex communication, which means data is transferred only one way at a time. 
'''Note No. 1:''' In RS-485 LLS mode can be connected up to 5 LLS fuel level sensors. 
'''Note No. 2:''' when activated RS-485 driver chip draws a constant 30 mA current when entering Sleep or Deep sleep RS-485 will be powered off.

==RS-232 / RS-485 modes==
Available modes for RS-232 and RS-485 interfaces:

{| class="wikitable" style="text-align:center; background-color:#ffffff;"
|- style="text-align:left;"
! rowspan="2" style="text-align:center; vertical-align:middle; font-weight:bold; background: #0054A6; color: white;" | Interface
! colspan="16" style="text-align:center; background: #0054A6; color: white;" | Mode
|-
| Log Mode
| NMEA
| LLS
| LCD
| RFID HID
| RFID MF7
| Garmin FMI
| TCP/UDP Ascii
| TCP/UDP Binary
| TCP/UDP Ascii Buffered
| TCP/UDP Binary Buffered
| UL202 Fuel Sensor
| REC to LCD
| ATOL Tachograph
| Backup Sattelite
|-
| style="vertical-align:middle;" | RS-232
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| style="vertical-align:middle;" | RS-485
| ✔
| ✔
| ✔
|
|
|
|
| ✔
| ✔
| ✔
| ✔
|
|
|
|
|}

====Log mode====
In this mode via RS-232 or RS-485 interface prints the {{{model|FMX640}}} device log and does not respond to commands. 

====GNSS NMEA mode====
In NMEA mode via RS-232 or RS-485 interface {{{model|FMX640}}} prints GNSS NMEA log and does not respond to commands. 

====LLS mode====
In LLS mode RS-232 supports one and RS-485 supports up to five LLS sensors - each of which has a receiver ID. 

====TCP (ASCII/Binary) modes====

In ''TCP Ascii/Binary'' mode all data received from the external device is sent directly to the server. Data is encapsulated in Codec 12 format. ''TCP Binary'' Mode has a delay of 30 ms, if no data is received for 30 ms, data is sent to the server. ''TCP Ascii'' mode waits for the End of Line (EOL) character (0x0D0A, \r\n, <CR><LF>) to pack data and send it to the server.

''TCP Ascii Buffered'' and ''TCP Binary Buffered'' modes are used to collect data from RS232 and save it in the buffer if there is no link with the server and data cannot be sent immediately. When the link is established and there is data to transmit, then RS232 data from the buffer is transmitted after all records are sent.

{| class="nd-othertables_2" style="width:100%;"
|-
!
! TCP Binary/TCP ASCII mode
! TCP Binary/TCP ASCII Buffered mode
|-
| '''Data is saved in buffer'''
| No
| Yes
|-
| '''Data sending protocol'''
| Codec 12
| Codec 13*
|-
| '''Timestamp'''
| Not using
| Is using*
|-
| '''To which server is sent'''
| Main
| Main and backup
|}
''*If the Timestamp parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.''
 

=====Message Timestamp=====
[[File:Timestamp.gif|right]] Message Timestamp parameter is used to determine if it is necessary to include a timestamp in the RS-232 TCP packet when sending to the server. If the parameter is Enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.

===== RS-232 / RS-485 CMD ID=====
This parameter is used when {{{model|}}} is sending RS232/RS485 packet to a server, it overrides command type value in Codec12/Codec13 with user-defined CMD ID value (1 - 14). {{{model|}}} behavior when it receives different CMD ID (Type) values in GPRS packet from server.
[[File:CMD.gif|right]]

==RS-232 modes==
Below you will find descriptions of available modes only for RS-232 interface:

====RS-232 LCD mode====
In this mode, the user is able to communicate with the server through the terminal. A link between the FMB device and the server has to be established for this mode to function properly.

To communicate from terminal to server - in terminal send command "WT^W your text here"
To communicate with the server to the terminal - send "#DO DAT=you text here" packet in [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols#Codec_12 Codec12 protocol]

====RS-232 RFID HID/RFID MF7 mode====
Radio-frequency identification (RFID) is the use of a wireless non-contact system that uses radio-frequency electromagnetic fields to transfer data from a tag attached to an object, for the purposes of automatic identification and tracking. [[{{{model|FMB640}}}]] can be configured in a way to use with an RFID reader. When an RFID of some sort (typically a plastic card with a magnetic line) is used with an RFID reader that is connected to [[{{{model|FMB640}}}]], the device creates a record with the data that the RFID reader has read and can be sent to a server with all other information. RFID ID is activated like an I/O parameter:
 
[[image:FMB640_RS232_RFID.png]]
 
To set up [[{{{model|FMB640}}}]] so it can be connected to an RFID reader, some parameters have to be set up. Go to RS232 \ RS485 and set up COM1 or COM2 settings to RFID Mode or RFID MF7 Mode (the used mode depends on the mode that the RFID reader works). See Figure 922. The Baudrates for each mode are:
* '''''RFID Mode''''' – 57600
* '''''RFID MF7 Mode''''' – 9600
[[image:FMB640_RS232_RFIDconf.png]] 
The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode [[{{{model|FMB640}}}]] understands RFID messages that are in hexadecimal text format and RFID HID Mode interprets messages that are in binary format. The type of RFID message sent to [[{{{model|FMB640}}}]] depends on the RFID reader. For example, the RFID MF7 mode message looks like $aa$02$03$04$17$89$00$01 while the HID mode message is of the following format: "1213141519".
The selected mode has to correspond to the RFID reader's mode.
Please contact your local sales representative for more information about RFID IDs and devices.

====REC to LCD mode====
In this mode, records are sent via ports.
This is an example view that is displayed in Terminal:

[[File:rec-lcd.jpg]]

====ATOL Tachograph mode====
This mode is used to connect the ATOL tachograph.

====UL202-2 Fuel Sensor====
Select this mode to make [[UL202 Ultrasonic Fuel Sensor|Ultrasonic Fuel Sensors]] work on the COM port.

====Satellite Backup mode====
Since 00.02.05 firmware version device supports [[TSM232|Iridium devices]] which can send short burst data (SBD) to the server. This means that some data can be sent from the FM device to the server through satellites.
In order to get those records, you have to connect the device to [[{{{model|FMB640}}}]] COM1 or COM2 port. Select COM1 or COM2 mode Satellite backup mode. Those settings could be found in RS232/RS485 tab in the configurator. Baudrate for satellite devices is 19200 bps. Furthermore, [[TSM232]] functionality should be enabled. These settings can be found in the Features tab in Short burst data settings. So, with this mode, some data can be sent from the FM device to the server through satellites using [[TSM232|Iridium devices]].

====RS-232 Garmin mode====
Garmin provides a Fleet Management Interface Tool Kit, once [[{{{model|FMB640}}}]] is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging and offers job dispatch capabilities to help them be more efficient. [[{{{model|FMB640}}}]] and Garmin operational diagram is shown in the figure below:
{{{image|[[Image:FMB640_GARMIN_BLOCK.png|800px|center]]}}}

Garmin configuration is shown in the figure below: 
[[image:FMB640_RS232_Garmin.png]]

==LLS Sensor==
LLS sensor series liquid level sensors are solid-state capacitive devices with no moving parts. The sensors use capacitive technology to produce accurate liquid level measurements of standard factory-grade DIESEL OIL and PURE GASOLINE (BENZINE) carbon fuels. The LLS sensor liquid level sensors are strictly prohibited to use in any liquids which are not factory-grade carbon fuels or contain: BIOFUEL, METHANOL, ETHANOL, UREA, and similar aggressive components in pure form or as additives for factory-grade carbon fuels for use in INTERNAL COMBUSTION ENGINES. Operating media – Diesel fuel (oil), pure gasoline (benzene). 
In order to use the LLS fuel counter, the newest firmware version is needed which can be obtained from Teltonika or a representative. Firmware is updated over GPRS or using a cable update method. 

====Specifications====

<table class="nd-othertables_2" style="width:40%;">
<tr>
<th rowspan="1" style="width:70%; vertical-align: middle; text-align: center;">Parameter</th>
<th rowspan="1" style="width:30%; vertical-align: middle; text-align: center;">Value</th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Supply voltage</th>
<td style="vertical-align: middle; text-align: left; ">+10..+50 V</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Current consumption, mA (for 12/24 V)</th>
<td style="vertical-align: middle; text-align: left; ">25 mA / 50 mA</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Working temperature</th>
<td style="vertical-align: middle; text-align: left; ">-40..+85 ºC</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Working mode</th>
<td style="vertical-align: middle; text-align: left; ">Continuous</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Weight</th>
<td style="vertical-align: middle; text-align: left; ">< 2.0 kg</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Working pressure</th>
<td style="vertical-align: middle; text-align: left; ">Atmospheric</td>
</tr>
</table>

====Wiring And Configuration====

First of all, the LLS fuel sensor must be connected to the [[{{{model|FMB640}}}]] device. Please find examples below:
<table class="nd-othertables_2" style="width:100%;">
<tr>
<td style="vertical-align: middle; text-align: left; ">'''Using RS232 socket'''</th>
<td style="vertical-align: middle; text-align: left; ">'''Using RS485 socket'''</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left; ">[[Image:FMX6 ir LLS sensor pajungimo schema RS232 WIKI V1.2.png|575px]]</th>
<td style="vertical-align: middle; text-align: left; ">[[Image:FMX6 ir LLS sensor pajungimo schema RS485 WIKI V1.0.png|585px]]</td>
</tr>
<tr>
</table>

Then [[{{{model|FMB640}}}]] must be configured. Both fuel level and fuel temperature has to be set up by the configurator’s I/O menu: 
[[image:FMB640_RS232_LLSmenu.png]]

==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. [[{{{model|FMB640}}}]] can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of [[{{{model|FMB640}}}]] and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.

====Standard protocols====
Text Message Protocol:
* Allows text messages sent to the device to be displayed in "inbox" on the navigation unit;
* Garmin can provide a confirmation that the message was read;
* Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
* Messages can be up to 199 characters long;
* Messages can also be generated from the device and sent to dispatcher/office;
* Messages received will be notified to the driver through a pop-up alert on the Garmin screen;
* Garmin provides a "virtual keyboard" for text communication.

Stop (Destination) Protocol:
* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";
* Driver has the ability to navigate directly to Stop from the list;
* Garmin can provide the status of a current Stop in progress;
* Garmin can indicate whether the driver has stopped at the location;
* Garmin can inform how far the driver has progressed through the list of Stops;
* Garmin can provide confirmation that the driver has received a particular Stop, familiarized himself/herself with its details, or removed it from the list;
* Can provide confirmation that a Stop has been reached.

Estimated Time of Arrival Protocol:
* Dispatcher/office can request the ETA of the current Stop/job in progress;
* Garmin can notify about the actual time of arrival as well as the distance remaining to a Stop.

Auto-Arrival at Stop Protocol:
* This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if he/she would like to mark the Stop as done and begin navigating to the Next Stop on the list;
* Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated.

Data Deletion Protocol:
* Dispatcher/office has the ability to wipe clean the data on Garmin PND;
* It allows to clean messages in the inbox and remove stops.

====Enhanced protocols====
Canned Responses/Messages:
* Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
* Up to 50 of these canned responses can be utilized for any given scenario;
* Drivers can store up to 120 canned messages, eliminating the need to type while driving.

Status Protocol:
* Up-to-the-minute communications that allow drivers to automatically send status updates;
* Driver's units can store up to 16 status indicators such as start/stop shift, on/off the break, etc.

====Supported features on TAVL client application====
TAVL client application lets the user use the following features of Garmin FMI:
* Text messaging;
* Destination message;
* ETA request.

====Text messaging====
The text messaging feature lets users communicate with the driver (the user that operates the Garmin device) by sending text messages via GPRS.

====Destination message====
A destination message is used to inform the driver of a new destination. When the Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver the ability to start navigating to the Stop location. A new destination in the TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

====ETA request message====
''Estimated Time of Arrival'' request message is used when the user wants to know an expected arrival time to the currently active destination and the distance (in meters) from the current object location to the destination.

FMM640 General description

2021-10-06T07:03:04Z

Renat Galiachmetov: /* Basic characteristics */

{{Template:FMM64 General description|model=FMM640}}

{{FMM640 Package contents}}

==Basic characteristics==

{{FMM640_Basic_characteristics}}

Cellular:

*LTE CAT M1/CAT NB1/EGPRS technologies
*2G bands: Quad-band 800/850/900/1900 MHz
*4G bands:
**FDD-LTE: B1/ B2/ B3/ B4/ B5/ B8/ B12/ B13/ B18/B19/ B20/ B26/ B28
**TDD-LTE: B39 (for Cat.M1 only)
*Data transfer:
**LTE FDD: Max. 375Kbps (DL)/Max.375Kbps (UL)
**LTE TDD: Max. 32Kbps (DL)/Max. 70Kbps (UL)
**GPRS: Max. 107Kbps (DL)/Max. 85.6Kbps (UL)
*SMS (text, data)


GNSS features:

*Tracking: 33/ 99 acquisition channels
*-165 dBM sensitivity
*Hot start <1s
*Warm Start < 25s
*Cold start < 35s
*NMEA-183 protocol
*GPS, GLONASS, GALILEO, BEIDOU, SBAS, QZSS, DGPS, AGPS
*Accuracy < 3m

Hardware features:

*STM32 processor;
*2 MB internal Flash memory;
*External memory card slot;
*Built-in accelerometer;
*Built-in Blue-tooth 5.0;
*Internal backup battery included;

Interface:

*Integrated KLINE
*Dual CAN J1939
*J1708 CAN
*RS485 and 2x RS232 support
*4 Digital Inputs for object status monitoring
*4 Digital Open-collector Outputs (controlling external relays, LED, buzzers, etc.)
*4 Analog Inputs
*1-wire interface
*Ni-Mh 550 mAh internal battery
*MicroSD card
*2 status LED
*Dimensions: L(104,1mm)xW(76,8mm)xH(31,5mm)
*Configuration and firmware update (via FOTA and USB cable)
*External GSM antenna for higher sensitivity
*External GNSS antenna for higher sensitivity

Special features:

*Fast position fix;
*High Quality track even in high density urban canyon;
*Ultra small case;
*Ready for harsh environment;
*Easy to mount in limited access areas;
*Firmly fasten;
*2 LED status indication;
*Real time tracking;
*Smart data acquisition based on:
** Time;
** Speed;
** Angle;
** Distance;
** Ignition or any other I/O event;
*Sending acquired data via GPRS;
*GPRS and SMS I/O events;
*Virtual odometer;
*Jamming detection;
*Configurable using Secured SMS Commands;
*1x micro SIM card; 1x eSIM;
*Overvoltage protection;
* Reverse polarity protection;

{{Template:FMM1_Supply voltage 10 30}}

{{Template:FMM640 Technical features|gprs=60|nominal=40|gnss_sleep=31|deep_sleep=4|onl_deep_sleep=13|battery=55|operating_min=-40|operating_max=+85|storage_min=-40|storage_max=+85|humidity_min=5|humidity_max=95|}}

==Technical information about internal battery==

{{Template:FMB640_Battery_information}}

== Battery tests ==
The amount of time the device will work from internal battery depends on the battery health, how often the device saves/sends information to the server, external peripherals connected to the device and the results may also differ depending on firmware used.

For general comparison purpose, and to see what results can be achieved, you can refer to the following internal test results in different modes and sending frequencies:
 

<table class="nd-othertables" style="width: 100%;">
<tr>
<th style="width: 10%; text-align:center; vertical-align:middle; color: black">Mode:</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color: black">Min Period (data saving frequency)</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color: black">Send Period (data sending frequency)</th>
<th style="width: 15%; text-align:center; vertical-align:middle; color: black">Starting Voltage</th>
<th style="width: 15%; text-align:center; vertical-align:middle; color: black">Cut off Voltage</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color: black">Time achieved</th>
</tr>
<tr>
<td style="vertical-align:middle">Operating</td>
<td> 10 seconds</td>
<td> 60 seconds</td>
<td>10,1V</td>
<td>7,6V</td>
<td>438 min (7 hours 18 minutes)</td>
</tr>
<tr>
<td style="vertical-align:middle">Operating</td>
<td>60 seconds</td>
<td>60 seconds</td>
<td>10,5V</td>
<td>7,6V</td>
<td>506 min (8 hours 26 minutes)</td>
</tr>
<tr>
<td style="vertical-align:middle">Deep Sleep</td>
<td>12 hours</td>
<td>12 hours</td>
<td>10,2V</td>
<td>8,2V</td>
<td>5040 min (84 hours 0 minutes)</td>
</tr>
<tr>
<td style="vertical-align:middle">Online Deep Sleep</td>
<td>12 hours</td>
<td>12 hours</td>
<td>10,1V</td>
<td>8,0V</td>
<td>2160 min (36 hours 0 minutes)</td>
</tr>
</tr></table>
 
{{Template:FMB640_Electrical_characteristics}}
[[Category:FMM640 Manual]]

Template:FMB640 Special features

2021-10-06T07:02:15Z

Renat Galiachmetov:

Special features:
* Fast position fix;
* High Quality track even in high density urban canyon;
* Ultra small case;
* Ready for harsh environment;
* Easy to mount in limited access areas;
* Firmly fasten;
* 2 LED status indication;
* Real time tracking;
* Smart data acquisition based on:
** Time;
** Speed;
** Angle;
** Distance;
** Ignition or any other I/O event;
* Sending acquired data via GPRS;
* GPRS and SMS I/O events;
* Virtual odometer;
* Jamming detection;
* Configurable using Secured SMS Commands;
{{{sim|* 1x micro SIM card; 1x eSIM;}}}
{{{spec|}}}
* Overvoltage protection;
* Reverse polarity protection;

Template:FMC640 Special features

2021-10-06T07:01:09Z

Renat Galiachmetov:

Template:FMC640 Special features

2021-10-06T07:00:28Z

Renat Galiachmetov:

File:CAN Adapter update via FOTA WEB.gif

2021-04-27T13:06:31Z

Renat Galiachmetov: Renat Galiachmetov uploaded a new version of File:CAN Adapter update via FOTA WEB.gif

CAN Adapter update

2021-04-27T13:05:56Z

Renat Galiachmetov:

The software of CAN adapters - [[LV-CAN200]], [[ALL-CAN300]] and [[CAN-CONTROL]] can now be updated Over The Air by using [[FOTA]] and one of the FMB1YX devices. Upgrading the software of CAN adapter will add more program numbers, thus, more vehicle models will be supported.

Please note, that only the newer version of LV-CAN200 and ALL-CAN300 CAN adapters support this feature. The version of the CAN adapter can be checked by sending an SMS command [[FMB_lvcangetinfo|lvcangetinfo]]. If, in the response message, "SWRev:" is 145, the CAN adapter is older and if it is 245, the adapter is newer. It does not apply to CAN-CONTROL - all CAN-CONTROL adapters support firmware updates over the air.

In order to update your device‘s firmware please follow a quick and simple step-by-step guide below. The procedure is the same for all devices.

*FMB1YX device, which is connected to the CAN adapter (or [[FMB140]] which has an internal CAN adapter), must be registered in Fota – device‘s model, firmware version, serial number, and other information must be shown.

*FMB1YX device, which is connected to the CAN adapter, must have a correct firmware version uploaded. Currently, this feature is supported from firmware 03.25.15.Rev.143 (FMB140 Firmware version), however it is suggested to use Firmware version which is 03.25.16.Rev.410 [[FMB140_firmware_errata|FMB140]]. If you want to update your CAN Adapter, please contact your local Teltonika sales manager or Teltonika GPS technical support. Once a device with the correct firmware version connects to Fota on the next scheduled connection (or instant connection, initiated by an SMS command "web_connect"), a small, blue, „CAN“ logo will appear next to the device‘s model. And current version of the CAN adapter software can be checked in the table on the right.

[[Image:11I registered.jpg|1160x1160px|center]]
 

*If the software is not up-to-date it can be updated in the previous window. A check-box needs to be ticked, then the „Actions“ button pressed and „Update CAN adapter firmware“ selected:

[[File:CAN Adapter update via FOTA WEB.gif|alt=|center]]
 

*Once the software update task has been assigned, it can be seen in the main window. Please note, that uploading will start after the next scheduled connection to Fota (or instant connection, initiated by an SMS command "web_connect"):

*When the update is finished, a new software version can be seen in the details window after the next scheduled connection to Fota (or instant connection, initiated by an SMS command "web_connect"):

[[Category: Frequently Asked Questions - FAQ]]

File:11I registered.jpg

2021-04-27T13:01:28Z

Renat Galiachmetov: Renat Galiachmetov uploaded a new version of File:11I registered.jpg

Template:FMC640 and FMM640 BLE module update

2021-04-27T12:50:31Z

Renat Galiachmetov: /* Update via FOTA WEB */

==Update via Configurator==
The BLE Firmware for FMC640 and FMM640 devices can be update via Configurator. Firstly, you should obtain the BLE FW file from your Sales Manager, then connect the device to the PC, open configurator, press on "Bluetooth 4.0" tab and at the bottom you will find "Transfer BLE Firmware file" with the "Upload" button. Press "Upload" button, choose BLE FW file, click OK and the device will be updated shortly.

[[File:BLE Update Configurator.png|center]]

==Update via FOTA WEB==
The BLE Firmware for FMC640 and FMM640 devices can now be updated Over The Air by using FOTA WEB.
Updating the BLE can enhanced performance and stability of BLE devices.

Please note:
- the minimal device firmware that supports over the air BLE update is 01.00.02.
- the minimal BLE firmware version is v0.1.5
In order to update your device‘s BLE firmware please follow a quick and simple step-by-step guide below. The procedure is the same for all devices. To get the module's firmware file, please contact your sales manager or fill a query in the VIP helpdesk.

FMC640 or FMM640 device must be registered in FOTA Web – device‘s model, firmware version, serial number and other information must be shown.

FMC640 or FMM640 device must have a correct device firmware version uploaded (Minimal device firmware 01.00.02). Once device with correct device firmware version connects to FOTA Web on the next scheduled connection (or instant connection, initiated by an SMS command "web_connect"), the data about the device will be updated.

[[File:04 FMx640 bluetooth update.jpg|center]]

To update BLE a check-box needs to be ticked, then „Create task“ button pressed and „Update BLE firmware“ selected:

[[File:03 FMX640 bluetooth update.gif]]

Once the software update task has been assigned, it can be seen in the main window. Please note, that uploading will start after the next scheduled connection to Fota Web (or instant connection, initiated by an SMS command "web_connect"):

Template:FMC640 and FMM640 BLE module update

2021-04-27T06:15:57Z

Renat Galiachmetov: /* Update via FOTA WEB */

==Update via Configurator==
The BLE Firmware for FMC640 and FMM640 devices can be update via Configurator. Firstly, you should obtain the BLE FW file from your Sales Manager, then connect the device to the PC, open configurator, press on "Bluetooth 4.0" tab and at the bottom you will find "Transfer BLE Firmware file" with the "Upload" button. Press "Upload" button, choose BLE FW file, click OK and the device will be updated shortly.

[[File:BLE Update Configurator.png|center]]

==Update via FOTA WEB==
The BLE Firmware for FMC640 and FMM640 devices can now be updated Over The Air by using FOTA WEB.
Updating the BLE can enhanced performance and stability of BLE devices.

Please note:
- the minimal device firmware that supports over the air BLE update is 01.00.02.
- the minimal BLE firmware version is v0.1.5
In order to update your device‘s BLE firmware please follow a quick and simple step-by-step guide below. The procedure is the same for all devices. To get the module's firmware file, please contact your sales manager or fill a query in the VIP helpdesk.

FMC640 or FMM640 device must be registered in FOTA Web – device‘s model, firmware version, serial number and other information must be shown.

FMC640 or FMM640 device must have a correct device firmware version uploaded (Minimal device firmware 01.00.02). Once device with correct device firmware version connects to FOTA Web on the next scheduled connection (or instant connection, initiated by an SMS command "web_connect"), the data about the device will be updated.

[[File:04 FMx640 bluetooth update.jpg|center]]

To update BLE a check-box needs to be ticked, then „Create task“ button pressed „Update BLE firmware“ selected:

[[File:03 FMX640 bluetooth update.gif]]

Once the software update task has been assigned, it can be seen in the main window. Please note, that uploading will start after the next scheduled connection to Fota Web (or instant connection, initiated by an SMS command "web_connect"):

File:03 FMX640 bluetooth update.gif

2021-04-27T06:06:41Z

Renat Galiachmetov: Renat Galiachmetov uploaded a new version of File:03 FMX640 bluetooth update.gif

03 FMX640 bluetooth update

File:04 FMx640 bluetooth update.jpg

2021-04-27T05:56:22Z

Renat Galiachmetov: Renat Galiachmetov uploaded a new version of File:04 FMx640 bluetooth update.jpg

04 FMx640 bluetooth update

Teltonika DualCam

2021-04-02T11:34:49Z

Renat Galiachmetov:

__TOC__
==Introduction to the product==
Teltonika DualCam is connected to FMX125 and FMU126 devices using the RS232 interface. 
[[image:DualCam1.png|400px]] 

==How to insert microSD cards==

Teltonika DualCam can hold 2 x microSD cards, which are inserted on both sides of the camera (front and rear). 
When the card is inserted correctly, it locks in with a "click". How the cards are inserted is depicted in the photos.

[[image:Dual_camera_MicroSD_card_insert_1.png|400px]]
[[image:Dual_camera_MicroSD_card_insert_2.png|400px]]

==Basic characteristics==
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Technical data</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Supported by</td>
<td style="width: 8%; text-align:left">FMC125, FMM125, FMU125, FMU126, FMB125</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Day & Night Vision Effect</td>
<td style="width: 8%; text-align:left">Day (Color), Night (Black & White)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Angle of View</td>
<td style="width: 8%; text-align:left">Horizontal 120°, Vertical 70°</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Dual Camera</td>
<td style="width: 8%; text-align:left">Front and Rear (equal characteristics)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera casing dimensions</td>
<td style="width: 8%; text-align:left">126.2 x 36.6 x 36.6 mm</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera mounting</td>
<td style="width: 8%; text-align:left">Sticky tape (3M) or screws</td>
</tr>
<tr>
 <table class="nd-othertables" style="width: 68%;">

<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Electrical parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Input voltage range</td>
<td style="width: 8%; text-align:left">9 ~ 36 V</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Working temperature and humidity</td>
<td style="width: 8%; text-align:left">Temperature: 30 °C ~ 85 °C
Humidity: <90%
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Stand-by electric current</td>
<td style="width: 8%; text-align:left">60 mA</td>
</tr>
<tr></table>
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Function parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Real time clock (RTC) synchronization</td>
<td style="width: 8%; text-align:left">Available over FM (via NTP, NITZ or GNSS)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Picture resolution</td>
<td style="width: 8%; text-align:left">1280 x 720 (default) (50KB transfer period 18 sec), Configurable: 160 x 120; 320 x 240; 640 x 480; 1920 x 1080</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">IR Distance</td>
<td style="width: 8%; text-align:left">2 Meters</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Cable length</td>
<td style="width: 8%; text-align:left">RS232 (3.5 m)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video compression</td>
<td style="width: 8%; text-align:left">H.265</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video resolution</td>
<td style="width: 8%; text-align:left">720P (20 sec. – 6MB, transfer period ~ 320 sec.)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video storage</td>
<td style="width: 8%; text-align:left">2psc. MicroSD card (Max 64GB up to 72 hours of video)</td>
</tr>
</table>
 

==Installation==
To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.
[[Image:Dual_camera-wiring_scheme.png|{{{general|size}}}|center]]
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam input for data reception through RS232
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''VCC(9-36V)''' (+)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply for the DualCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground
|}
 

==DualCam RS232 camera support==
DualCam camera support was introduced from firmware version 03.27.00.Rev.100. A new RS232 mode "DualCam"
was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |18
|}
[[Image:DualCamCFG.PNG|{{{general|size}}}|right]]
Configuration version 8.1.6.0 has to be used if configuration is being made in offline mode.
 
 
 
 

==Camera Feature Settings==
[[Image:CameraFeatureSettings.PNG|{{{general|size}}}|right]]
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Resolution
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |66000
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - 160 x 120
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |3
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - 320 x 240
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - 640 x 480
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - 1280 x 720
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |4 - 1920 x 1080
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Compression
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66001
| rowspan="1" style="text-align: center; vertical-align: center;" |[0 - 100] (%)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |50
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |OSD Display
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66002
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video Frame Rate
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66003
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-30] (frames per second)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30
|}
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled.
 

==Camera Scenario Settings==
[[Image:CameraScenarioSettings.PNG|{{{general|size}}}|right]]
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Periodic Image sending
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66006
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sending interval
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66007
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[10-1800] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |600
|-
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video sending trigger
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |66008
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - None
| colspan="1" rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - Crash
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration before trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66009
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration after trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66010
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
|}
 
===Periodic image sending scenario===
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter). If a camera has not finished uploading picture to a server, then the photo capture is skipped.

'''Note:''' Data sending from camera to server works only when ignition status is on.
 
 

===Video sending by trigger===
Video sending by trigger scenario monitors the selected trigger (video sending trigger parameter) and captures video before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |SOS trigger
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |499
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Server request
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Crash
|}
 

===Camera request command===
A new camera request has been added, which allows server to request files from a camera. The format is as provided below in the table:
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration>
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made.
|}
The arguments are as follows:

*<file_type>
**0 - Video
**1 - Photo
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras
*<timestamp>
**Unix timestamps in decimal (not required for photo download)
*<duration>
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)

{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Arguments are invalid
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid argument in camera request cmd!
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for photo from source <1-3> received
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for video from source <1-3> received for <1-30> seconds since YYYY-MM-DDHH:MM:SS
|}
 

==Camera ping transmission and TF status checking==
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for both front and rear camera every 20 seconds when ignition is on. The received result from this command is stored in two corresponding AVL elements “Front camera state” and “Rear camera state”. The following do not only store TF status, but also if response from the camera was received or not.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
|-
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state:
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |498
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected
|-
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |Rear camera state:
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |497
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty
|-
|}
 

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
 

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 
===Camera file transfer reconnection===
If FMU1YX device has bad reception, server is not reachable or wrong server details are configured, then the device tries to open a link to a camera server few consecutive times. If no connection was possible to be established, then the connection is postponed for 30 minutes and tried again (or tried every configured sending interval if periodic image sending is enabled).
 

==DualCam camera file transfer support==
[[Image:CameraServerSettings.PNG|{{{general|size}}}|right]]
Once camera has at least one file captured, it starts connection to a remote server, which is configured by parameters “Domain” and “Port” found in the “Camera Settings” tab.
 

==Initialization packet==
On connection, a device sends an initialization packet.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Header(0x0000)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Protocol ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''IMEI'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 bytes
|}
Protocol ID – just a reference for the protocol version that is running on a device (for server cross compatibility with older versions). Firmware FMB.Ver.03.27.00.Rev.100 and up have protocol ID 5.
Settings flag contains information on what is available for download. Structure is provided below:
{| class="wikitable"
|+
! colspan="32" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings, 4 B'''
|-
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 3'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 2'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 1'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 0'''
|-
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |1
! rowspan="1" style="width: 400px; background: background: white; color: black;" |2
! rowspan="1" style="width: 400px; background: background: white; color: black;" |3
! rowspan="1" style="width: 400px; background: background: white; color: black;" |4
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
|}

#Video, rear (%videor)
#Video, front (%videof)
#Photo, rear (%photor)
#Photo, front (%photof)

If identifier sent to a server is not valid, device disconnects.
 

==General command structure==
General communication packet structure is as in the table bellow. It consist of CMD_ID (2 bytes), Data length of a command and a payload.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |[data length] bytes
|}
 
==Communication protocol==
'''Close a session command (CMD ID 0x0000)''' 
In case when a device connects to a server, but the server does not expect it to connect, server will respond by sending a CLOSE command after which the connection will be terminated. This command is also used when device connects to a server for a custom file sending and server finishes to send all custom files to the device.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Data length'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
|}
 
'''Start file transfer command (CMD ID 0x0001)''' 
After device received file request command from the server (0x0008) device sends START command with file data (packet count).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Packets (4 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Blank field (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0001
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0006
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x12345678
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000 (always same value)
|}
 
'''File request command (CMD ID 0x0008)''' 
After device is connected for a file upload, server initiates file transfer by sending a FILE REQ command.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Identifier'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0008
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |''See the table below''
|}
Device should answer with a START command described above indicating a size and CRC of the requested file.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''File source, type'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Identifier (ASCII chars)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photof
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videof
|}
 
'''Resume file transfer command (CMD ID 0x0002)''' 
In a response to the START command a RESUME command must be sent from server.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Packet offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0002
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
To begin file transfer from the start, offset should be set to 1 (4 bytes value). In case when the file transfer was interrupted, to resume file transfer, offset can be set to the desired value (1 ≤ [offset] ≤ [file packets]).
 
 
'''Synchronize file transfer command (CMD ID 0x0003)''' 
In a response to the RESUME command a SYNC command is sent from device.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0003
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
By sending SYNC command it is ensured that next data command will contain file data starting from the specified offset.
 
 
'''File data transfer command (CMD ID 0x0004)''' 
After sending a SYNC command, a file data transfer is started by sending DATA commands.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File data (up to 1024 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data CRC (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0402
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
|}
A File data is split into 1024 byte parts, each part wrapped into a DATA command and is sent. 
Note: ''if a command with a bad CRC is received, RESUME command should be sent with the last valid file offset, after receiving a RESUME command, server will stop sending DATA commands and continue communication from'' '''“Resume file transfer”''' ''step.'' 
CRC polynomial expression: 0x8408
Initial value, when calculating CRC, is previously received packet (CMD ID 0x0004) CRC value.
 
 
'''File transfer status command (CMD ID 0x0005)''' 
After a file transfer is completed and no more files are required from the device, a server should send a COMPLETED command to the device (this command does not work after executing repeat init command0 x0009 – in this case the server should send a CLOSE SESSION 0x0000 command mentioned before).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0005
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
|}
In case of the server using invalid arguments, commands or not following the file request flow, the device will send this command with a Status field set to one of the few possible error codes. List of possible ones is provided below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status value (hexadecimal)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Notes'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |File transfer process completed
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from server
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000002
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close GPRS
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000003
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close socket
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000005
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid response from server to init packet
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000011
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |This error code forces the device to disconnect from server
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Sent from device. Possible causes:

*Camera is not configured
*The requested file is not available by camera
|}
After a COMPLETED command device should disconnect from the server.
 
 
'''Initialization packet repeat command (CMD ID 0x0009)''' 
When sent, the initialization packet is repeated. This is used, when all of the files are downloaded and additional check is carried out for any additional files, that may have been captured during the download operation.
 

==File transfer visual flow==
[[Image:FileTransferVisual.PNG|{{{general|size}}}|center]]
[[Category:Accessories]]

Teltonika DualCam

2021-04-02T11:26:56Z

Renat Galiachmetov:

__TOC__
==Introduction to the product==
Teltonika DualCam is connected to FMX125 and FMU126 devices using the RS232 interface. 
[[image:DualCam1.png|400px]] 

==How to insert microSD cards==

Teltonika DualCam can hold 2 x microSD cards, which are inserted on both sides of the camera (front and rear). 
When the card is inserted correctly, it locks in with a "click". How the cards are inserted is depicted in the photos.

[[image:Dual_camera_MicroSD_card_insert_1.png|400px]]
[[image:Dual_camera_MicroSD_card_insert_2.png|400px]]

==Basic characteristics==
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Technical data</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Supported by</td>
<td style="width: 8%; text-align:left">FMC125, FMM125, FMU125, FMU126, FMB125</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Day & Night Vision Effect</td>
<td style="width: 8%; text-align:left">Day (Color), Night (Black & White)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Angle of View</td>
<td style="width: 8%; text-align:left">Horizontal 120°, Vertical 70°</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Dual Camera</td>
<td style="width: 8%; text-align:left">Front and Rear (equal characteristics)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera casing dimensions</td>
<td style="width: 8%; text-align:left">126.2 x 36.6 x 36.6 mm</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera mounting</td>
<td style="width: 8%; text-align:left">Sticky tape (3M) or screws</td>
</tr>
<tr>
 <table class="nd-othertables" style="width: 68%;">

<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Electrical parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Input voltage range</td>
<td style="width: 8%; text-align:left">9 ~ 36 V</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Working temperature and humidity</td>
<td style="width: 8%; text-align:left">Temperature: 30 °C ~ 85 °C
Humidity: <90%
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Stand-by electric current</td>
<td style="width: 8%; text-align:left">60 mA</td>
</tr>
<tr></table>
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Function parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Real time clock (RTC) synchronization</td>
<td style="width: 8%; text-align:left">Available over FM (via NTP, NITZ or GNSS)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Picture resolution</td>
<td style="width: 8%; text-align:left">1280 x 720 (default) (50KB transfer period 18 sec), Configurable: 160 x 120; 320 x 240; 640 x 480; 1920 x 1080</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">IR Distance</td>
<td style="width: 8%; text-align:left">2 Meters</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Cable length</td>
<td style="width: 8%; text-align:left">RS232 (3.5 m)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video compression</td>
<td style="width: 8%; text-align:left">H.265</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video resolution</td>
<td style="width: 8%; text-align:left">720P (20 sec. – 6MB, transfer period ~ 320 sec.)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video storage</td>
<td style="width: 8%; text-align:left">2psc. MicroSD card (Max 64GB up to 72 hours of video)</td>
</tr>
</table>
 

==Installation==
To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.
[[Image:Dual_camera-wiring_scheme.png|{{{general|size}}}|center]]
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam input for data reception through RS232
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''VCC(9-36V)''' (+)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply for the DualCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground
|}
 

==DualCam RS232 camera support==
DualCam camera support was introduced from firmware version 03.27.00.Rev.100. A new RS232 mode "DualCam"
was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |18
|}
[[Image:DualCamCFG.PNG|{{{general|size}}}|right]]
Configuration version 8.1.6.0 has to be used if configuration is being made in offline mode.
 
 
 
 

==Camera Feature Settings==
[[Image:CameraFeatureSettings.PNG|{{{general|size}}}|right]]
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Resolution
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |66000
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - 160 x 120
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |3
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - 320 x 240
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - 640 x 480
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - 1280 x 720
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |4 - 1920 x 1080
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Compression
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66001
| rowspan="1" style="text-align: center; vertical-align: center;" |[0 - 100] (%)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |50
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |OSD Display
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66002
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video Frame Rate
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66003
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-30] (frames per second)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30
|}
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled.
 

==Camera Scenario Settings==
[[Image:CameraScenarioSettings.PNG|{{{general|size}}}|right]]
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Periodic Image sending
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66006
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sending interval
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66007
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[10-1800] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |600
|-
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video sending trigger
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |66008
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - None
| colspan="1" rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - Crash
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration before trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66009
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration after trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66010
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
|}
 
===Periodic image sending scenario===
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter). If a camera has not finished uploading picture to a server, then the photo capture is skipped.

Note: Any data sending from camera to server only when ignition status is on.
 
 

===Video sending by trigger===
Video sending by trigger scenario monitors the selected trigger (video sending trigger parameter) and captures video before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |SOS trigger
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |499
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Server request
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Crash
|}
 

===Camera request command===
A new camera request has been added, which allows server to request files from a camera. The format is as provided below in the table:
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration>
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made.
|}
The arguments are as follows:

*<file_type>
**0 - Video
**1 - Photo
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras
*<timestamp>
**Unix timestamps in decimal (not required for photo download)
*<duration>
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)

{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Arguments are invalid
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid argument in camera request cmd!
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for photo from source <1-3> received
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for video from source <1-3> received for <1-30> seconds since YYYY-MM-DDHH:MM:SS
|}
 

==Camera ping transmission and TF status checking==
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for both front and rear camera every 20 seconds when ignition is on. The received result from this command is stored in two corresponding AVL elements “Front camera state” and “Rear camera state”. The following do not only store TF status, but also if response from the camera was received or not.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
|-
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state:
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |498
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected
|-
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |Rear camera state:
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |497
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty
|-
|}
 

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
 

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 
===Camera file transfer reconnection===
If FMU1YX device has bad reception, server is not reachable or wrong server details are configured, then the device tries to open a link to a camera server few consecutive times. If no connection was possible to be established, then the connection is postponed for 30 minutes and tried again (or tried every configured sending interval if periodic image sending is enabled).
 

==DualCam camera file transfer support==
[[Image:CameraServerSettings.PNG|{{{general|size}}}|right]]
Once camera has at least one file captured, it starts connection to a remote server, which is configured by parameters “Domain” and “Port” found in the “Camera Settings” tab.
 

==Initialization packet==
On connection, a device sends an initialization packet.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Header(0x0000)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Protocol ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''IMEI'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 bytes
|}
Protocol ID – just a reference for the protocol version that is running on a device (for server cross compatibility with older versions). Firmware FMB.Ver.03.27.00.Rev.100 and up have protocol ID 5.
Settings flag contains information on what is available for download. Structure is provided below:
{| class="wikitable"
|+
! colspan="32" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings, 4 B'''
|-
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 3'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 2'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 1'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 0'''
|-
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |1
! rowspan="1" style="width: 400px; background: background: white; color: black;" |2
! rowspan="1" style="width: 400px; background: background: white; color: black;" |3
! rowspan="1" style="width: 400px; background: background: white; color: black;" |4
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
|}

#Video, rear (%videor)
#Video, front (%videof)
#Photo, rear (%photor)
#Photo, front (%photof)

If identifier sent to a server is not valid, device disconnects.
 

==General command structure==
General communication packet structure is as in the table bellow. It consist of CMD_ID (2 bytes), Data length of a command and a payload.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |[data length] bytes
|}
 
==Communication protocol==
'''Close a session command (CMD ID 0x0000)''' 
In case when a device connects to a server, but the server does not expect it to connect, server will respond by sending a CLOSE command after which the connection will be terminated. This command is also used when device connects to a server for a custom file sending and server finishes to send all custom files to the device.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Data length'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
|}
 
'''Start file transfer command (CMD ID 0x0001)''' 
After device received file request command from the server (0x0008) device sends START command with file data (packet count).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Packets (4 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Blank field (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0001
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0006
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x12345678
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000 (always same value)
|}
 
'''File request command (CMD ID 0x0008)''' 
After device is connected for a file upload, server initiates file transfer by sending a FILE REQ command.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Identifier'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0008
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |''See the table below''
|}
Device should answer with a START command described above indicating a size and CRC of the requested file.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''File source, type'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Identifier (ASCII chars)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photof
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videof
|}
 
'''Resume file transfer command (CMD ID 0x0002)''' 
In a response to the START command a RESUME command must be sent from server.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Packet offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0002
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
To begin file transfer from the start, offset should be set to 1 (4 bytes value). In case when the file transfer was interrupted, to resume file transfer, offset can be set to the desired value (1 ≤ [offset] ≤ [file packets]).
 
 
'''Synchronize file transfer command (CMD ID 0x0003)''' 
In a response to the RESUME command a SYNC command is sent from device.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0003
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
By sending SYNC command it is ensured that next data command will contain file data starting from the specified offset.
 
 
'''File data transfer command (CMD ID 0x0004)''' 
After sending a SYNC command, a file data transfer is started by sending DATA commands.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File data (up to 1024 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data CRC (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0402
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
|}
A File data is split into 1024 byte parts, each part wrapped into a DATA command and is sent. 
Note: ''if a command with a bad CRC is received, RESUME command should be sent with the last valid file offset, after receiving a RESUME command, server will stop sending DATA commands and continue communication from'' '''“Resume file transfer”''' ''step.'' 
CRC polynomial expression: 0x8408
Initial value, when calculating CRC, is previously received packet (CMD ID 0x0004) CRC value.
 
 
'''File transfer status command (CMD ID 0x0005)''' 
After a file transfer is completed and no more files are required from the device, a server should send a COMPLETED command to the device (this command does not work after executing repeat init command0 x0009 – in this case the server should send a CLOSE SESSION 0x0000 command mentioned before).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0005
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
|}
In case of the server using invalid arguments, commands or not following the file request flow, the device will send this command with a Status field set to one of the few possible error codes. List of possible ones is provided below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status value (hexadecimal)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Notes'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |File transfer process completed
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from server
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000002
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close GPRS
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000003
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close socket
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000005
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid response from server to init packet
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000011
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |This error code forces the device to disconnect from server
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Sent from device. Possible causes:

*Camera is not configured
*The requested file is not available by camera
|}
After a COMPLETED command device should disconnect from the server.
 
 
'''Initialization packet repeat command (CMD ID 0x0009)''' 
When sent, the initialization packet is repeated. This is used, when all of the files are downloaded and additional check is carried out for any additional files, that may have been captured during the download operation.
 

==File transfer visual flow==
[[Image:FileTransferVisual.PNG|{{{general|size}}}|center]]
[[Category:Accessories]]

Teltonika DualCam

2021-04-02T11:24:24Z

Renat Galiachmetov:

__TOC__
==Introduction to the product==
Teltonika DualCam is connected to FMX125 and FMU126 devices using the RS232 interface. 
[[image:DualCam1.png|400px]] 

==How to insert microSD cards==

Teltonika DualCam can hold 2 x microSD cards, which are inserted on both sides of the camera (front and rear). 
When the card is inserted correctly, it locks in with a "click". How the cards are inserted is depicted in the photos.

[[image:Dual_camera_MicroSD_card_insert_1.png|400px]]
[[image:Dual_camera_MicroSD_card_insert_2.png|400px]]

==Basic characteristics==
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Technical data</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Supported by</td>
<td style="width: 8%; text-align:left">FMC125, FMM125, FMU125, FMU126, FMB125</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Day & Night Vision Effect</td>
<td style="width: 8%; text-align:left">Day (Color), Night (Black & White)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Angle of View</td>
<td style="width: 8%; text-align:left">Horizontal 120°, Vertical 70°</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Dual Camera</td>
<td style="width: 8%; text-align:left">Front and Rear (equal characteristics)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera casing dimensions</td>
<td style="width: 8%; text-align:left">126.2 x 36.6 x 36.6 mm</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera mounting</td>
<td style="width: 8%; text-align:left">Sticky tape (3M) or screws</td>
</tr>
<tr>
 <table class="nd-othertables" style="width: 68%;">

<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Electrical parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Input voltage range</td>
<td style="width: 8%; text-align:left">9 ~ 36 V</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Working temperature and humidity</td>
<td style="width: 8%; text-align:left">Temperature: 30 °C ~ 85 °C
Humidity: <90%
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Stand-by electric current</td>
<td style="width: 8%; text-align:left">60 mA</td>
</tr>
<tr></table>
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Function parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Real time clock (RTC) synchronization</td>
<td style="width: 8%; text-align:left">Available over FM (via NTP, NITZ or GNSS)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Picture resolution</td>
<td style="width: 8%; text-align:left">1280 x 720 (default) (50KB transfer period 18 sec), Configurable: 160 x 120; 320 x 240; 640 x 480; 1920 x 1080</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">IR Distance</td>
<td style="width: 8%; text-align:left">2 Meters</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Cable length</td>
<td style="width: 8%; text-align:left">RS232 (3.5 m)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video compression</td>
<td style="width: 8%; text-align:left">H.265</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video resolution</td>
<td style="width: 8%; text-align:left">720P (20 sec. – 6MB, transfer period ~ 320 sec.)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video storage</td>
<td style="width: 8%; text-align:left">2psc. MicroSD card (Max 64GB up to 72 hours of video)</td>
</tr>
</table>
 

==Installation==
To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.
[[Image:Dual_camera-wiring_scheme.png|{{{general|size}}}|center]]
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam input for data reception through RS232
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''VCC(9-36V)''' (+)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply for the DualCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground
|}
 

==DualCam RS232 camera support==
DualCam camera support was introduced from firmware version 03.27.00.Rev.100. A new RS232 mode "DualCam"
was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |18
|}
[[Image:DualCamCFG.PNG|{{{general|size}}}|right]]
Configuration version 8.1.6.0 has to be used if configuration is being made in offline mode.
 
 
 
 

==Camera Feature Settings==
[[Image:CameraFeatureSettings.PNG|{{{general|size}}}|right]]
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Resolution
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |66000
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - 160 x 120
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |3
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - 320 x 240
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - 640 x 480
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - 1280 x 720
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |4 - 1920 x 1080
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Compression
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66001
| rowspan="1" style="text-align: center; vertical-align: center;" |[0 - 100] (%)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |50
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |OSD Display
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66002
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video Frame Rate
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66003
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-30] (frames per second)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30
|}
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled.
 

==Camera Scenario Settings==
[[Image:CameraScenarioSettings.PNG|{{{general|size}}}|right]]
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Periodic Image sending
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66006
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sending interval
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66007
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[10-1800] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |600
|-
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video sending trigger
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |66008
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - None
| colspan="1" rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - Crash
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration before trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66009
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration after trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66010
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
|}
 
===Periodic image sending scenario===
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter). If a camera has not finished uploading picture to a server, then the photo capture is skipped.

Note: Any data sending from camera to server only when ignition status is on.

 

 

===Video sending by trigger===
Video sending by trigger scenario monitors the selected trigger (video sending trigger parameter) and captures video before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |SOS trigger
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |499
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Server request
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Crash
|}
 

===Camera request command===
A new camera request has been added, which allows server to request files from a camera. The format is as provided below in the table:
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration>
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made.
|}
The arguments are as follows:

*<file_type>
**0 - Video
**1 - Photo
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras
*<timestamp>
**Unix timestamps in decimal (not required for photo download)
*<duration>
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)

{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Arguments are invalid
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid argument in camera request cmd!
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for photo from source <1-3> received
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for video from source <1-3> received for <1-30> seconds since YYYY-MM-DDHH:MM:SS
|}
 

==Camera ping transmission and TF status checking==
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for both front and rear camera every 20 seconds when ignition is on. The received result from this command is stored in two corresponding AVL elements “Front camera state” and “Rear camera state”. The following do not only store TF status, but also if response from the camera was received or not.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
|-
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state:
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |498
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected
|-
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |Rear camera state:
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |497
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty
|-
|}
 

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
 

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 
===Camera file transfer reconnection===
If FMU1YX device has bad reception, server is not reachable or wrong server details are configured, then the device tries to open a link to a camera server few consecutive times. If no connection was possible to be established, then the connection is postponed for 30 minutes and tried again (or tried every configured sending interval if periodic image sending is enabled).
 

==DualCam camera file transfer support==
[[Image:CameraServerSettings.PNG|{{{general|size}}}|right]]
Once camera has at least one file captured, it starts connection to a remote server, which is configured by parameters “Domain” and “Port” found in the “Camera Settings” tab.
 

==Initialization packet==
On connection, a device sends an initialization packet.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Header(0x0000)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Protocol ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''IMEI'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 bytes
|}
Protocol ID – just a reference for the protocol version that is running on a device (for server cross compatibility with older versions). Firmware FMB.Ver.03.27.00.Rev.100 and up have protocol ID 5.
Settings flag contains information on what is available for download. Structure is provided below:
{| class="wikitable"
|+
! colspan="32" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings, 4 B'''
|-
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 3'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 2'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 1'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 0'''
|-
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |1
! rowspan="1" style="width: 400px; background: background: white; color: black;" |2
! rowspan="1" style="width: 400px; background: background: white; color: black;" |3
! rowspan="1" style="width: 400px; background: background: white; color: black;" |4
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
|}

#Video, rear (%videor)
#Video, front (%videof)
#Photo, rear (%photor)
#Photo, front (%photof)

If identifier sent to a server is not valid, device disconnects.
 

==General command structure==
General communication packet structure is as in the table bellow. It consist of CMD_ID (2 bytes), Data length of a command and a payload.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |[data length] bytes
|}
 
==Communication protocol==
'''Close a session command (CMD ID 0x0000)''' 
In case when a device connects to a server, but the server does not expect it to connect, server will respond by sending a CLOSE command after which the connection will be terminated. This command is also used when device connects to a server for a custom file sending and server finishes to send all custom files to the device.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Data length'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
|}
 
'''Start file transfer command (CMD ID 0x0001)''' 
After device received file request command from the server (0x0008) device sends START command with file data (packet count).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Packets (4 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Blank field (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0001
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0006
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x12345678
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000 (always same value)
|}
 
'''File request command (CMD ID 0x0008)''' 
After device is connected for a file upload, server initiates file transfer by sending a FILE REQ command.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Identifier'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0008
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |''See the table below''
|}
Device should answer with a START command described above indicating a size and CRC of the requested file.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''File source, type'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Identifier (ASCII chars)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photof
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videof
|}
 
'''Resume file transfer command (CMD ID 0x0002)''' 
In a response to the START command a RESUME command must be sent from server.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Packet offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0002
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
To begin file transfer from the start, offset should be set to 1 (4 bytes value). In case when the file transfer was interrupted, to resume file transfer, offset can be set to the desired value (1 ≤ [offset] ≤ [file packets]).
 
 
'''Synchronize file transfer command (CMD ID 0x0003)''' 
In a response to the RESUME command a SYNC command is sent from device.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0003
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
By sending SYNC command it is ensured that next data command will contain file data starting from the specified offset.
 
 
'''File data transfer command (CMD ID 0x0004)''' 
After sending a SYNC command, a file data transfer is started by sending DATA commands.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File data (up to 1024 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data CRC (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0402
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
|}
A File data is split into 1024 byte parts, each part wrapped into a DATA command and is sent. 
Note: ''if a command with a bad CRC is received, RESUME command should be sent with the last valid file offset, after receiving a RESUME command, server will stop sending DATA commands and continue communication from'' '''“Resume file transfer”''' ''step.'' 
CRC polynomial expression: 0x8408
Initial value, when calculating CRC, is previously received packet (CMD ID 0x0004) CRC value.
 
 
'''File transfer status command (CMD ID 0x0005)''' 
After a file transfer is completed and no more files are required from the device, a server should send a COMPLETED command to the device (this command does not work after executing repeat init command0 x0009 – in this case the server should send a CLOSE SESSION 0x0000 command mentioned before).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0005
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
|}
In case of the server using invalid arguments, commands or not following the file request flow, the device will send this command with a Status field set to one of the few possible error codes. List of possible ones is provided below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status value (hexadecimal)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Notes'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |File transfer process completed
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from server
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000002
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close GPRS
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000003
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close socket
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000005
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid response from server to init packet
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000011
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |This error code forces the device to disconnect from server
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Sent from device. Possible causes:

*Camera is not configured
*The requested file is not available by camera
|}
After a COMPLETED command device should disconnect from the server.
 
 
'''Initialization packet repeat command (CMD ID 0x0009)''' 
When sent, the initialization packet is repeated. This is used, when all of the files are downloaded and additional check is carried out for any additional files, that may have been captured during the download operation.
 

==File transfer visual flow==
[[Image:FileTransferVisual.PNG|{{{general|size}}}|center]]
[[Category:Accessories]]

Teltonika DualCam

2021-04-02T11:22:57Z

Renat Galiachmetov: /* Periodic image sending scenario */

__TOC__
==Introduction to the product==
Teltonika DualCam is connected to FMX125 and FMU126 devices using the RS232 interface. 
[[image:DualCam1.png|400px]] 

==How to insert microSD cards==

Teltonika DualCam can hold 2 x microSD cards, which are inserted on both sides of the camera (front and rear). 
When the card is inserted correctly, it locks in with a "click". How the cards are inserted is depicted in the photos.

[[image:Dual_camera_MicroSD_card_insert_1.png|400px]]
[[image:Dual_camera_MicroSD_card_insert_2.png|400px]]

==Basic characteristics==
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Technical data</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Supported by</td>
<td style="width: 8%; text-align:left">FMC125, FMM125, FMU125, FMU126, FMB125</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Day & Night Vision Effect</td>
<td style="width: 8%; text-align:left">Day (Color), Night (Black & White)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Angle of View</td>
<td style="width: 8%; text-align:left">Horizontal 120°, Vertical 70°</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Dual Camera</td>
<td style="width: 8%; text-align:left">Front and Rear (equal characteristics)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera casing dimensions</td>
<td style="width: 8%; text-align:left">126.2 x 36.6 x 36.6 mm</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera mounting</td>
<td style="width: 8%; text-align:left">Sticky tape (3M) or screws</td>
</tr>
<tr>
 <table class="nd-othertables" style="width: 68%;">

<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Electrical parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Input voltage range</td>
<td style="width: 8%; text-align:left">9 ~ 36 V</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Working temperature and humidity</td>
<td style="width: 8%; text-align:left">Temperature: 30 °C ~ 85 °C
Humidity: <90%
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Stand-by electric current</td>
<td style="width: 8%; text-align:left">60 mA</td>
</tr>
<tr></table>
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Function parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Real time clock (RTC) synchronization</td>
<td style="width: 8%; text-align:left">Available over FM (via NTP, NITZ or GNSS)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Picture resolution</td>
<td style="width: 8%; text-align:left">1280 x 720 (default) (50KB transfer period 18 sec), Configurable: 160 x 120; 320 x 240; 640 x 480; 1920 x 1080</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">IR Distance</td>
<td style="width: 8%; text-align:left">2 Meters</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Cable length</td>
<td style="width: 8%; text-align:left">RS232 (3.5 m)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video compression</td>
<td style="width: 8%; text-align:left">H.265</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video resolution</td>
<td style="width: 8%; text-align:left">720P (20 sec. – 6MB, transfer period ~ 320 sec.)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video storage</td>
<td style="width: 8%; text-align:left">2psc. MicroSD card (Max 64GB up to 72 hours of video)</td>
</tr>
</table>
 

==Installation==
To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.
[[Image:Dual_camera-wiring_scheme.png|{{{general|size}}}|center]]
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam input for data reception through RS232
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''VCC(9-36V)''' (+)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply for the DualCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground
|}
 

==DualCam RS232 camera support==
DualCam camera support was introduced from firmware version 03.27.00.Rev.100. A new RS232 mode "DualCam"
was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |18
|}
[[Image:DualCamCFG.PNG|{{{general|size}}}|right]]
Configuration version 8.1.6.0 has to be used if configuration is being made in offline mode.
 
 
 
 

==Camera Feature Settings==
[[Image:CameraFeatureSettings.PNG|{{{general|size}}}|right]]
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Resolution
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |66000
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - 160 x 120
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |3
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - 320 x 240
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - 640 x 480
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - 1280 x 720
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |4 - 1920 x 1080
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Compression
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66001
| rowspan="1" style="text-align: center; vertical-align: center;" |[0 - 100] (%)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |50
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |OSD Display
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66002
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video Frame Rate
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66003
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-30] (frames per second)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30
|}
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled.
 

==Camera Scenario Settings==
[[Image:CameraScenarioSettings.PNG|{{{general|size}}}|right]]
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Periodic Image sending
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66006
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sending interval
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66007
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[10-1800] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |600
|-
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video sending trigger
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |66008
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - None
| colspan="1" rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - Crash
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration before trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66009
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration after trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66010
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
|}
 
===Periodic image sending scenario===
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter). If a camera has not finished uploading picture to a server, then the photo capture is skipped.

 

 

===Video sending by trigger===
Video sending by trigger scenario monitors the selected trigger (video sending trigger parameter) and captures video before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |SOS trigger
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |499
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Server request
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Crash
|}
 

===Camera request command===
A new camera request has been added, which allows server to request files from a camera. The format is as provided below in the table:
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration>
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made.
|}
The arguments are as follows:

*<file_type>
**0 - Video
**1 - Photo
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras
*<timestamp>
**Unix timestamps in decimal (not required for photo download)
*<duration>
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)

{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Arguments are invalid
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid argument in camera request cmd!
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for photo from source <1-3> received
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for video from source <1-3> received for <1-30> seconds since YYYY-MM-DDHH:MM:SS
|}
 

==Camera ping transmission and TF status checking==
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for both front and rear camera every 20 seconds when ignition is on. The received result from this command is stored in two corresponding AVL elements “Front camera state” and “Rear camera state”. The following do not only store TF status, but also if response from the camera was received or not.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
|-
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state:
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |498
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected
|-
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |Rear camera state:
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |497
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty
|-
|}
 

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
 

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 
===Camera file transfer reconnection===
If FMU1YX device has bad reception, server is not reachable or wrong server details are configured, then the device tries to open a link to a camera server few consecutive times. If no connection was possible to be established, then the connection is postponed for 30 minutes and tried again (or tried every configured sending interval if periodic image sending is enabled).
 

==DualCam camera file transfer support==
[[Image:CameraServerSettings.PNG|{{{general|size}}}|right]]
Once camera has at least one file captured, it starts connection to a remote server, which is configured by parameters “Domain” and “Port” found in the “Camera Settings” tab.
 

==Initialization packet==
On connection, a device sends an initialization packet.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Header(0x0000)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Protocol ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''IMEI'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 bytes
|}
Protocol ID – just a reference for the protocol version that is running on a device (for server cross compatibility with older versions). Firmware FMB.Ver.03.27.00.Rev.100 and up have protocol ID 5.
Settings flag contains information on what is available for download. Structure is provided below:
{| class="wikitable"
|+
! colspan="32" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings, 4 B'''
|-
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 3'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 2'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 1'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 0'''
|-
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |1
! rowspan="1" style="width: 400px; background: background: white; color: black;" |2
! rowspan="1" style="width: 400px; background: background: white; color: black;" |3
! rowspan="1" style="width: 400px; background: background: white; color: black;" |4
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
|}

#Video, rear (%videor)
#Video, front (%videof)
#Photo, rear (%photor)
#Photo, front (%photof)

If identifier sent to a server is not valid, device disconnects.
 

==General command structure==
General communication packet structure is as in the table bellow. It consist of CMD_ID (2 bytes), Data length of a command and a payload.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |[data length] bytes
|}
 
==Communication protocol==
'''Close a session command (CMD ID 0x0000)''' 
In case when a device connects to a server, but the server does not expect it to connect, server will respond by sending a CLOSE command after which the connection will be terminated. This command is also used when device connects to a server for a custom file sending and server finishes to send all custom files to the device.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Data length'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
|}
 
'''Start file transfer command (CMD ID 0x0001)''' 
After device received file request command from the server (0x0008) device sends START command with file data (packet count).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Packets (4 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Blank field (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0001
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0006
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x12345678
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000 (always same value)
|}
 
'''File request command (CMD ID 0x0008)''' 
After device is connected for a file upload, server initiates file transfer by sending a FILE REQ command.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Identifier'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0008
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |''See the table below''
|}
Device should answer with a START command described above indicating a size and CRC of the requested file.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''File source, type'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Identifier (ASCII chars)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photof
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videof
|}
 
'''Resume file transfer command (CMD ID 0x0002)''' 
In a response to the START command a RESUME command must be sent from server.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Packet offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0002
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
To begin file transfer from the start, offset should be set to 1 (4 bytes value). In case when the file transfer was interrupted, to resume file transfer, offset can be set to the desired value (1 ≤ [offset] ≤ [file packets]).
 
 
'''Synchronize file transfer command (CMD ID 0x0003)''' 
In a response to the RESUME command a SYNC command is sent from device.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0003
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
By sending SYNC command it is ensured that next data command will contain file data starting from the specified offset.
 
 
'''File data transfer command (CMD ID 0x0004)''' 
After sending a SYNC command, a file data transfer is started by sending DATA commands.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File data (up to 1024 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data CRC (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0402
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
|}
A File data is split into 1024 byte parts, each part wrapped into a DATA command and is sent. 
Note: ''if a command with a bad CRC is received, RESUME command should be sent with the last valid file offset, after receiving a RESUME command, server will stop sending DATA commands and continue communication from'' '''“Resume file transfer”''' ''step.'' 
CRC polynomial expression: 0x8408
Initial value, when calculating CRC, is previously received packet (CMD ID 0x0004) CRC value.
 
 
'''File transfer status command (CMD ID 0x0005)''' 
After a file transfer is completed and no more files are required from the device, a server should send a COMPLETED command to the device (this command does not work after executing repeat init command0 x0009 – in this case the server should send a CLOSE SESSION 0x0000 command mentioned before).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0005
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
|}
In case of the server using invalid arguments, commands or not following the file request flow, the device will send this command with a Status field set to one of the few possible error codes. List of possible ones is provided below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status value (hexadecimal)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Notes'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |File transfer process completed
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from server
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000002
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close GPRS
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000003
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close socket
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000005
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid response from server to init packet
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000011
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |This error code forces the device to disconnect from server
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Sent from device. Possible causes:

*Camera is not configured
*The requested file is not available by camera
|}
After a COMPLETED command device should disconnect from the server.
 
 
'''Initialization packet repeat command (CMD ID 0x0009)''' 
When sent, the initialization packet is repeated. This is used, when all of the files are downloaded and additional check is carried out for any additional files, that may have been captured during the download operation.
 

==File transfer visual flow==
[[Image:FileTransferVisual.PNG|{{{general|size}}}|center]]
[[Category:Accessories]]

Teltonika DualCam

2021-04-02T11:22:36Z

Renat Galiachmetov: /* Periodic image sending scenario */

__TOC__
==Introduction to the product==
Teltonika DualCam is connected to FMX125 and FMU126 devices using the RS232 interface. 
[[image:DualCam1.png|400px]] 

==How to insert microSD cards==

Teltonika DualCam can hold 2 x microSD cards, which are inserted on both sides of the camera (front and rear). 
When the card is inserted correctly, it locks in with a "click". How the cards are inserted is depicted in the photos.

[[image:Dual_camera_MicroSD_card_insert_1.png|400px]]
[[image:Dual_camera_MicroSD_card_insert_2.png|400px]]

==Basic characteristics==
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Technical data</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Supported by</td>
<td style="width: 8%; text-align:left">FMC125, FMM125, FMU125, FMU126, FMB125</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Day & Night Vision Effect</td>
<td style="width: 8%; text-align:left">Day (Color), Night (Black & White)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Angle of View</td>
<td style="width: 8%; text-align:left">Horizontal 120°, Vertical 70°</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Dual Camera</td>
<td style="width: 8%; text-align:left">Front and Rear (equal characteristics)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera casing dimensions</td>
<td style="width: 8%; text-align:left">126.2 x 36.6 x 36.6 mm</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Camera mounting</td>
<td style="width: 8%; text-align:left">Sticky tape (3M) or screws</td>
</tr>
<tr>
 <table class="nd-othertables" style="width: 68%;">

<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Electrical parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Input voltage range</td>
<td style="width: 8%; text-align:left">9 ~ 36 V</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Working temperature and humidity</td>
<td style="width: 8%; text-align:left">Temperature: 30 °C ~ 85 °C
Humidity: <90%
</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Stand-by electric current</td>
<td style="width: 8%; text-align:left">60 mA</td>
</tr>
<tr></table>
 
<table class="nd-othertables" style="width: 68%;">
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Function parameters</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Real time clock (RTC) synchronization</td>
<td style="width: 8%; text-align:left">Available over FM (via NTP, NITZ or GNSS)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Picture resolution</td>
<td style="width: 8%; text-align:left">1280 x 720 (default) (50KB transfer period 18 sec), Configurable: 160 x 120; 320 x 240; 640 x 480; 1920 x 1080</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">IR Distance</td>
<td style="width: 8%; text-align:left">2 Meters</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Cable length</td>
<td style="width: 8%; text-align:left">RS232 (3.5 m)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video compression</td>
<td style="width: 8%; text-align:left">H.265</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video resolution</td>
<td style="width: 8%; text-align:left">720P (20 sec. – 6MB, transfer period ~ 320 sec.)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Video storage</td>
<td style="width: 8%; text-align:left">2psc. MicroSD card (Max 64GB up to 72 hours of video)</td>
</tr>
</table>
 

==Installation==
To connect the DualCam to a supported device, you have to make sure to connect 4 PINs of the camera to the PINs of your device correctly.
[[Image:Dual_camera-wiring_scheme.png|{{{general|size}}}|center]]
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NUMBER
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |PIN NAME
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Tx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam output for data transmission through RS232
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''RS232-Rx'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DualCam input for data reception through RS232
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''VCC(9-36V)''' (+)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply for the DualCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''GND''' (-)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground
|}
 

==DualCam RS232 camera support==
DualCam camera support was introduced from firmware version 03.27.00.Rev.100. A new RS232 mode "DualCam"
was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |18
|}
[[Image:DualCamCFG.PNG|{{{general|size}}}|right]]
Configuration version 8.1.6.0 has to be used if configuration is being made in offline mode.
 
 
 
 

==Camera Feature Settings==
[[Image:CameraFeatureSettings.PNG|{{{general|size}}}|right]]
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Resolution
| colspan="1" rowspan="6" style="text-align: center; style=" width: 150px; background: white; color: black;" |66000
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - 160 x 120
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |3
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - 320 x 240
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - 640 x 480
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - 1280 x 720
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |4 - 1920 x 1080
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Camera Picture Compression
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66001
| rowspan="1" style="text-align: center; vertical-align: center;" |[0 - 100] (%)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |50
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |OSD Display
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66002
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video Frame Rate
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66003
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-30] (frames per second)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30
|}
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled.
 

==Camera Scenario Settings==
[[Image:CameraScenarioSettings.PNG|{{{general|size}}}|right]]
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Parameter values'''
! rowspan="1" style="width: 350px; background: #0054A6; color: white;" |'''Default values'''
|-
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Periodic Image sending
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |66006
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - Disabled
| colspan="1" rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - Enabled
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sending interval
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66007
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[10-1800] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |600
|-
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video sending trigger
| colspan="1" rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |66008
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |0 - None
| colspan="1" rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; vertical-align: center;" |3 - Crash
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration before trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66009
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video duration after trigger
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |66010
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |[1-10] (seconds)
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |5
|-
|}
 
===Periodic image sending scenario===
Periodic image sending triggers photo capture from a front camera, whenever the timeout is reached (sending interval parameter). If a camera has not finished uploading picture to a server, then the photo capture is skipped.

Note: Any data sending from camera to server only when ignition status is on.
 

 

===Video sending by trigger===
Video sending by trigger scenario monitors the selected trigger (video sending trigger parameter) and captures video before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter value'''
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |SOS trigger
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |499
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Server request
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - DIN1
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - DIN2
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Crash
|}
 

===Camera request command===
A new camera request has been added, which allows server to request files from a camera. The format is as provided below in the table:
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration>
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made.
|}
The arguments are as follows:

*<file_type>
**0 - Video
**1 - Photo
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras
*<timestamp>
**Unix timestamps in decimal (not required for photo download)
*<duration>
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)

{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Arguments are invalid
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid argument in camera request cmd!
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for photo from source <1-3> received
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video requested
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Request for video from source <1-3> received for <1-30> seconds since YYYY-MM-DDHH:MM:SS
|}
 

==Camera ping transmission and TF status checking==
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for both front and rear camera every 20 seconds when ignition is on. The received result from this command is stored in two corresponding AVL elements “Front camera state” and “Rear camera state”. The following do not only store TF status, but also if response from the camera was received or not.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values'''
|-
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state:
| rowspan="2" style="text-align: center; style=" width: 150px; background: white; color: black;" |498
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected
|-
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card
|-
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |Rear camera state:
| rowspan="4" style="text-align: center; style=" width: 150px; background: white; color: black;" |497
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed
|-
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty
|-
|}
 

==Camera RTC synchronization==
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
 

==Other camera related functionality==
Camera is configured if all of these conditions are met:

#'''RS232 mode is selected (DualCam)'''
#'''Camera was not configured since startup or one of the related parameters were changed (compression, framerate or OSD)'''
#'''Camera file transfer is not active'''

Active camera reconfiguration is accompanied by two consecutive camera shutter clicks.
If camera is disconnected and later reconnected, a device will detect it by periodic camera ping packet. Once camera is detected, the device will reissue the reconfiguration procedure.
 
===Camera file transfer reconnection===
If FMU1YX device has bad reception, server is not reachable or wrong server details are configured, then the device tries to open a link to a camera server few consecutive times. If no connection was possible to be established, then the connection is postponed for 30 minutes and tried again (or tried every configured sending interval if periodic image sending is enabled).
 

==DualCam camera file transfer support==
[[Image:CameraServerSettings.PNG|{{{general|size}}}|right]]
Once camera has at least one file captured, it starts connection to a remote server, which is configured by parameters “Domain” and “Port” found in the “Camera Settings” tab.
 

==Initialization packet==
On connection, a device sends an initialization packet.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Header(0x0000)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Protocol ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''IMEI'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 bytes
|}
Protocol ID – just a reference for the protocol version that is running on a device (for server cross compatibility with older versions). Firmware FMB.Ver.03.27.00.Rev.100 and up have protocol ID 5.
Settings flag contains information on what is available for download. Structure is provided below:
{| class="wikitable"
|+
! colspan="32" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Settings, 4 B'''
|-
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 3'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 2'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 1'''
! colspan="8" rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Byte 0'''
|-
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |1
! rowspan="1" style="width: 400px; background: background: white; color: black;" |2
! rowspan="1" style="width: 400px; background: background: white; color: black;" |3
! rowspan="1" style="width: 400px; background: background: white; color: black;" |4
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
! rowspan="1" style="width: 400px; background: background: white; color: black;" |
|}

#Video, rear (%videor)
#Video, front (%videof)
#Photo, rear (%photor)
#Photo, front (%photof)

If identifier sent to a server is not valid, device disconnects.
 

==General command structure==
General communication packet structure is as in the table bellow. It consist of CMD_ID (2 bytes), Data length of a command and a payload.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |[data length] bytes
|}
 
==Communication protocol==
'''Close a session command (CMD ID 0x0000)''' 
In case when a device connects to a server, but the server does not expect it to connect, server will respond by sending a CLOSE command after which the connection will be terminated. This command is also used when device connects to a server for a custom file sending and server finishes to send all custom files to the device.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Data length'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000
|}
 
'''Start file transfer command (CMD ID 0x0001)''' 
After device received file request command from the server (0x0008) device sends START command with file data (packet count).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Packets (4 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Blank field (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0001
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0006
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x12345678
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0000 (always same value)
|}
 
'''File request command (CMD ID 0x0008)''' 
After device is connected for a file upload, server initiates file transfer by sending a FILE REQ command.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File Identifier'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0008
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 bytes
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |''See the table below''
|}
Device should answer with a START command described above indicating a size and CRC of the requested file.
{| class="wikitable"
|+
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''File source, type'''
! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Identifier (ASCII chars)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Photo from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%photof
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, rear
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videor
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video from camera, front
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |%videof
|}
 
'''Resume file transfer command (CMD ID 0x0002)''' 
In a response to the START command a RESUME command must be sent from server.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Packet offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0002
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
To begin file transfer from the start, offset should be set to 1 (4 bytes value). In case when the file transfer was interrupted, to resume file transfer, offset can be set to the desired value (1 ≤ [offset] ≤ [file packets]).
 
 
'''Synchronize file transfer command (CMD ID 0x0003)''' 
In a response to the RESUME command a SYNC command is sent from device.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File offset (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0003
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000001
|}
By sending SYNC command it is ensured that next data command will contain file data starting from the specified offset.
 
 
'''File data transfer command (CMD ID 0x0004)''' 
After sending a SYNC command, a file data transfer is started by sending DATA commands.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''File data (up to 1024 bytes)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data CRC (2 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0402
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |...
|}
A File data is split into 1024 byte parts, each part wrapped into a DATA command and is sent. 
Note: ''if a command with a bad CRC is received, RESUME command should be sent with the last valid file offset, after receiving a RESUME command, server will stop sending DATA commands and continue communication from'' '''“Resume file transfer”''' ''step.'' 
CRC polynomial expression: 0x8408
Initial value, when calculating CRC, is previously received packet (CMD ID 0x0004) CRC value.
 
 
'''File transfer status command (CMD ID 0x0005)''' 
After a file transfer is completed and no more files are required from the device, a server should send a COMPLETED command to the device (this command does not work after executing repeat init command0 x0009 – in this case the server should send a CLOSE SESSION 0x0000 command mentioned before).
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Data length'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status (4 bytes)'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0005
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x0004
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
|}
In case of the server using invalid arguments, commands or not following the file request flow, the device will send this command with a Status field set to one of the few possible error codes. List of possible ones is provided below.
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Status value (hexadecimal)'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Notes'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000000
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |File transfer process completed
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from server
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000002
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close GPRS
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000003
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Failed to close socket
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000005
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Invalid response from server to init packet
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Sent from device
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x00000011
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |This error code forces the device to disconnect from server
| rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Sent from device. Possible causes:

*Camera is not configured
*The requested file is not available by camera
|}
After a COMPLETED command device should disconnect from the server.
 
 
'''Initialization packet repeat command (CMD ID 0x0009)''' 
When sent, the initialization packet is repeated. This is used, when all of the files are downloaded and additional check is carried out for any additional files, that may have been captured during the download operation.
 

==File transfer visual flow==
[[Image:FileTransferVisual.PNG|{{{general|size}}}|center]]
[[Category:Accessories]]

Codec

2021-01-08T13:00:10Z

Renat Galiachmetov:

='''<big>Introduction</big>'''=
A codec is a device or computer program for encoding or decoding a digital data stream or signal. Codec is a portmanteau of coder – decoder. A codec encodes a data stream or a signal for transmission and storage, possibly in encrypted form, and the decoder function reverses the encoding for playback or editing. 
Below you will see a table of all Codec types with ID’s:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 8
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 8 Extended
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 16
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 12
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 13
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec 14
|-
| style="vertical-align: middle; text-align: center;" |0x08
| style="vertical-align: middle; text-align: center;" |0x8E
| style="vertical-align: middle; text-align: center;" |0x10
| style="vertical-align: middle; text-align: center;" |0x0C
| style="vertical-align: middle; text-align: center;" |0x0D
| style="vertical-align: middle; text-align: center;" |0x0E
|-
|}
Also, there are using two data transport protocols: TCP and UDP. But it is not important which one will be use in Codec.

='''<big>Codec for device data sending</big>'''=
In this chapter you will find information about every Codec protocol which are using for device data sending and differences between them.

=='''<big>Codec 8</big>'''==

*'''<big>Protocol Overview</big>'''

Codec8 – a main FM device protocol that is used for sending data to server. 

*'''<big>Codec 8 protocol sending over TCP</big>'''

TCP is a connection-oriented protocol that is used for communication between devices. The workings of this type of protocol is described below in the '''communication with server''' section. 

*'''AVL Data Packet'''

Below table represents AVL Data Packet structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Field Length
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 2
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' – the packet starts with four zero bytes. 
'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2. 
'''Codec ID''' – in Codec8 it is always <code>0x08</code>. 
'''Number of Data 1''' – a number which defines how many records is in the packet. 
'''AVL Data''' – actual data in the packet (more information below). 
'''Number of Data 2''' – a number which defines how many records is in the packet. This number must be the same as “Number of Data 1”. 
'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 
'''Note:''' for [[FMB630]], [[FMB640]] and [[FM6300|FM63XY]], minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL record size is 255 bytes. Maximum AVL packet size is 512 bytes. For other devices, minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes. 

*AVL Data

Below table represents AVL Data structure.
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Timestamp
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |GPS Element
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |IO Element
|-
| style="vertical-align: middle; text-align: center;" |8 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |15 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
|-
|}

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time). 
'''Priority''' – field which define AVL data priority (more information below). 
'''GPS Element''' – location information of the AVL data (more information below). 
'''IO Element''' – additional configurable information from device (more information below). 

*Priority

Below table represents Priority values. Packet priority depends on device configuration and records sent.
{| class="nd-othertables_2" style="width:25%;"
|+
! colspan="2" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |0
| style="vertical-align: middle; text-align: center;" |Low
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |High
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |2
| style="vertical-align: middle; text-align: center;" |Panic
|} 

*GPS element

Below table represents GPS Element structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Longitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Latitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Altitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Angle
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Satellites
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Speed
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
|}

'''Longitude''' – east – west position. 
'''Latitude''' – north – south position. 
'''Altitude''' – meters above sea level. 
'''Angle''' – degrees from north pole. 
'''Satellites''' – number of visible satellites. 
'''Speed''' – speed calculated from satellites. 
'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid. 
Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula: 
[[Image:GPS.png]]
 
Where: 
d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000) 
If longitude is in west or latitude in south, multiply result by –1. 
Note: 
To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is 0, coordinate is positive, if it is 1, coordinate is negative. 
Example: 
Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic. 

*IO Element

{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
| rowspan="26" style=" width:5%; vertical-align: middle; text-align: left;" |
| rowspan="26" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state changed and it generate event, Event IO ID will be <code>0xEF</code> (AVL ID: 239). If it’s not eventual record – the value is 0. 
'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8). 
'''N1''' – number of properties, which length is 1 byte. 
'''N2''' – number of properties, which length is 2 bytes. 
'''N4''' – number of properties, which length is 4 bytes. 
'''N8''' – number of properties, which length is 8 bytes. 
'''N’th IO ID''' - AVL ID. 
'''N’th IO Value''' - AVL ID value. 
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N of Total IO
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2 of Two Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4 of Four Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO Value
| style="vertical-align: middle; text-align: center;" |4 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8 of Eight Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |8 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO ID
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO Value
| style="vertical-align: middle; text-align: center;" |8 bytes
|-
|} 

*'''Communication with server'''

First, when module connects to server, module sends its IMEI. First comes short identifying number of bytes written and then goes IMEI as text (bytes). 
For example, IMEI <code>356307042441013</code> would be sent as <code>000F333536333037303432343431303133</code>. 
First two bytes denote IMEI length. In this case <code>0x000F</code> means, that IMEI is 15 bytes long. 
After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module <code>01</code>, if not - <code>00</code>. Note that confirmation should be sent as binary packet. I.e. 1 byte <code>0x01</code> or <code>0x00</code>. 
Then module starts to send first AVL data packet. After server receives packet and parses it, server must report to module number of data received as integer (four bytes). 
If sent data number and reported by server doesn’t match module resends sent data. 

*Example: 

Module connects to server and sends IMEI: 
<code>000F333536333037303432343431303133</code> 
Server accepts the module: 
01 
Module sends data packet:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |Four Zero Bytes – 0x00000000,
“AVL Data Array” length – 0x000000FE
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x08,
Number of Data – '''0x02''' 
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”
|-
| style="vertical-align: middle; text-align: center;" |00000000000000FE
| style="vertical-align: middle; text-align: center;" |08'''02'''...(data elements)...'''02'''
| style="vertical-align: middle; text-align: center;" |00008612
|-
|}

Server acknowledges data reception (2 data elements): '''<code>00000002</code>''' 

*'''Examples'''

Hexadecimal stream of AVL Data Packet receiving and response in these examples are given in hexadecimal form. The different fields of packets are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 

'''1'st example''' 
Receiving one data record with each element property (1 byte, 2 bytes, 4 byte and 8 byte). 
Received data in hexadecimal stream: 
<code>000000000000003608010000016B40D8EA30010000000000000000000000000000000105021503010101425E0F01F10000601A014E0000000000000000010000C7CF</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 36
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="24" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D8 EA 30 (GMT: Monday, June 10, 2019 10:04:46 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |03
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |5E 0F
|-
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |F1 (AVL ID: 241, Name: Active GSM Operator)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 60 1A
|-
| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |4E (AVL ID: 78, Name: iButton)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 00 00 00 00
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 C7 CF
|-
|}

Server response: <code>00000001</code> 

'''2'nd example''' 
Receiving one data record with one or two different element properties (1 byte, 2 byte). 
Received data in hexadecimal stream: 
<code>000000000000002808010000016B40D9AD80010000000000000000000000000000000103021503010101425E100000010000F22A</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 28
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="20" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D9 AD 80 (GMT: Monday, June 10, 2019 10:05:36 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |03
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |03
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |5E 0F
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 F2 2A
|-
|}

Server response: <code>00000001</code> 

'''3'rd example''' 
Receiving two or more data records with one or more different element properties. 
Received data in hexadecimal stream: 
<code>000000000000004308020000016B40D57B480100000000000000000000000000000001010101000000000000016B40D5C198010000000000000000000000000000000
101010101000000020000252C</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 43
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |02
|-
| rowspan="16" style="vertical-align: middle; text-align: center;" |AVL Data
(1'st record)
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D5 7B 48 (GMT: Monday, June 10, 2019 10:01:01 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| rowspan="16" style="vertical-align: middle; text-align: center;" |AVL Data
(2'nd record)
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D5 C1 98 (GMT: Monday, June 10, 2019 10:01:19 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 25 2C
|-
|}

Server response: <code>00000002</code> 

*'''<big>Codec8 protocol sending over UDP</big>'''

UDP is a transport layer protocol above UDP/IP to add reliability to plain UDP/IP using acknowledgment packets. 

*'''AVL Data Packet'''

The packet structure is as follows:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Datagram
|-
| style="vertical-align: middle; text-align: center;" |Example
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
| style="vertical-align: middle; text-align: center;" |Not Usable Byte
| style="vertical-align: middle; text-align: center;" |1 byte
|-
| style="vertical-align: middle; text-align: center;" |Packet Payload
| style="vertical-align: middle; text-align: center;" |Variable
|-
|}

'''Example''' – packet length (excluding this field) in big ending byte order. 
'''Packet ID''' – packet ID unique for this channel. 
'''Not Usable Byte''' – not usable byte. 
'''Packet payload''' – data payload. 

*Acknowledgment packet

Acknowledgment packet should have the same Packet ID as acknowledged data packet and empty Data Payload. Acknowledgement should be sent in binary format.
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Acknowledgment Packet
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Packet Length
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Packet ID
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Not Usable Byte
|-
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
|}

'''Packet Length''' – packet length by sending/response data. 
'''Packet ID''' – same as in acknowledgment packet. 
'''Not Usable Byte''' – always will be <code>0x01</code>. 

*Sending AVL Packet Payload using UDP channel

Below table represents Sending Packet Payload structure.
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="4" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL data encapsulated in UDP channel packet
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Packet ID
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |IMEI Length
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Module IMEI
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data Array
|-
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |15 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
|-
|}
'''AVL Packet ID''' – ID identifying this AVL packet. 
'''IMEI Length''' – always will be <code>0x000F</code>. 
'''Module IMEI''' – IMEI of a sending module encoded the same as with TCP. 
'''AVL Data Array''' – array of encoded AVL data (same as TCP AVL Data Array). 

*Server response Packet Payload using UDP channel

Below table represents Server Response Packet Payload structure.
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Response to AVL Data Packet
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Packet ID
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Number of Accepted AVL Elements
|-
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
|-
|} 

*'''Communication with server'''

Module sends UDP channel packet with encapsulated AVL data packet. Server sends UDP channel packet with encapsulated response module validates AVL Packet ID and Number of accepted AVL elements. If server response with valid AVL Packet ID is not received within configured timeout, module can retry sending. 

*Example:

Module sends the data:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x00FE,
Packet ID – 0xCAFE 
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
IMEI Length – 0x000F 
IMEI – 0x313233343536373839303132333435
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x08,
Number of Data – 0x02 
(Encoded using continuous bit stream)
|-
| style="vertical-align: middle; text-align: center;" |00FECAFE01
| style="vertical-align: middle; text-align: center;" |DD000F3133343536373839303132333435
| style="vertical-align: middle; text-align: center;" |0802…(data elements)…02
|-
|}

Server must respond with acknowledgment:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x0005,
Packet ID – 0xCAFE,
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
Number of Accepted Data – 0x02
|-
| style="vertical-align: middle; text-align: center;" |0005CAFE01
| style="vertical-align: middle; text-align: center;" |DD02
|-
|} 

*'''Example'''

Hexadecimal stream of AVL Data Packet receiving and response in this example are given in hexadecimal form. The different fields of packet are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Received data in hexadecimal stream: 
<code>003DCAFE0105000F33353230393330383634303336353508010000016B4F815B30010000000000000000000000000000000103021503010101425DBC000001</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |00 3D
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |AVL Packet Header
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |IMEI Length
| style="vertical-align: middle; text-align: center;" |00 0F
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |33 35 32 30 39 33 30 38 36 34 30 33 36 35 35
|-
| rowspan="23" style="vertical-align: middle; text-align: center;" |AVL Data Array
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 4F 81 5B 30 (GMT: Thursday, June 13, 2019 6:23:26 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |03
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |03
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |5D BC
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
|}

Server response in hexadecimal stream:
<code>0005CAFE010501</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Response to AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |Server Response Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Number of Accepted Data
| style="vertical-align: middle; text-align: center;" |01
|-
|} 

=='''<big>Codec 8 Extended</big>'''==

*'''<big>Protocols overview</big>'''

Codec8 Extended is using for FMBXXX family devices. This protocol looks familiar like Codec8 but they have some differences. Main differences between are shown in below table:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8 Extended
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0x08
| style="vertical-align: middle; text-align: center;" |0x8E
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element total IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element AVL ID length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Variable size IO elements
| style="vertical-align: middle; text-align: center;" |Does not include
| style="vertical-align: middle; text-align: center;" |Includes variable size elements
|-
|} 

*'''<big>Codec 8 Extended protocol sending over TCP</big>'''

*'''AVL data packet'''

Below table represents AVL data packet structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Field Length
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 2
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' – the packet starts with four zero bytes. 
'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2. 
'''Codec ID''' – in Codec8 Extended it is always <code>0x8E</code>. 
'''Number of Data 1''' – a number which defines how many records is in the packet. 
'''AVL Data''' – actual data in the packet (more information below). 
'''Number of Data 2''' – a number which defines how many records is in the packet. This number must be the same as “Number of Data 1”. 
'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 
'''Note:''' for [[FMB630]], [[FMB640]] and [[FM6300|FM63XY]], minimum AVL packet size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 255 bytes. For other devices, minimum AVL packet size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes. 

*AVL Data

Below table represents AVL Data structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Timestamp
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |GPS Element
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |IO Element
|-
| style="vertical-align: middle; text-align: center;" |8 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |15 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
|-
|}

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time). 
'''Priority''' – field which define AVL data priority (more information below). 
'''GPS Element''' – locational information of the AVL data (more information below). 
'''IO Element''' – additional configurable information from device (more information below). 

*Priority

Below table represents Priority values. Packet priority depends on device configuration and records sent.
{| class="nd-othertables_2" style="width:25%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |0
| style="vertical-align: middle; text-align: center;" |Low
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |High
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |2
| style="vertical-align: middle; text-align: center;" |Panic
|} 

*GPS element

Below table represents GPS Element structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Longitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Latitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Altitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Angle
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Satellites
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Speed
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
|}

'''Longitude''' – east – west position. 
'''Latitude''' – north – south position. 
'''Altitude''' – meters above sea level. 
'''Angle''' – degrees from north pole. 
'''Satellites''' – number of visible satellites. 
'''Speed''' – speed calculated from satellites. 
'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid. 
Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula: 
[[Image:GPS.png]]
 
Where: 
d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000) 
If longitude is in west or latitude in south, multiply result by –1. 
Note: 
To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, coordinate is positive, if it is <code>1</code>, coordinate is negative. 
Example: 
Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic. 

*IO Element

{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
| rowspan="33" style=" width:5%; vertical-align: middle; text-align: left;" |
| rowspan="33" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state changed and it generate event, Event IO ID will be 0xEF (AVL ID: 239). If it’s not eventual record – the value is 0. 
'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8). 
'''N1''' – number of properties, which length is 1 byte. 
'''N2''' – number of properties, which length is 2 bytes. 
'''N4''' – number of properties, which length is 4 bytes. 
'''N8''' – number of properties, which length is 8 bytes. 
'''NX''' – a number of properties, which length is defined by length element.
'''N’th IO ID''' - AVL ID. 
'''N'th Lenght''' - AVL ID value lenght. 
'''N’th IO Value''' - AVL ID value. 
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N of Total IO
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2 of Two Bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4 of Four Bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO Value
| style="vertical-align: middle; text-align: center;" |4 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8 of Eight Bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |8 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO Value
| style="vertical-align: middle; text-align: center;" |8 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |NX of X Byte IO
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Length
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |Defined by lenght
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |NX’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |NX’th Length
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |NX’th Value
| style="vertical-align: middle; text-align: center;" |Defined by lenght
|-
|} 

*'''Communication with server'''

Communication with server is the same as with Codec8 protocol, except in Codec8 Extended protocol Codec ID is 0x8E. 

*Example:

Module connects to server and sends IMEI: 
<code>000F333536333037303432343431303133</code> 
Server accepts the module: 
<code>01</code> 
Module sends data packet:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |Four Zero Bytes – 0x00000000,
“AVL Data Array” length – 0x000000FE
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x8E,
Number of Data – '''0x02''' 
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”
|-
| style="vertical-align: middle; text-align: center;" |00000000000000FE
| style="vertical-align: middle; text-align: center;" |8E'''02'''...(data elements)...'''02'''
| style="vertical-align: middle; text-align: center;" |00008612
|-
|}

Server acknowledges data reception (2 data elements): '''<code>00000002</code>''' 

*'''Example'''

Hexadecimal stream of AVL Data Packet receiving and response in this example are given in hexadecimal form. The different fields of packet are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Received data in hexadecimal stream: 
<code>000000000000004A8E010000016B412CEE000100000000000000000000000000000000010005000100010100010011001D00010010015E2C880002000B000000003544C87
A000E000000001DD7E06A00000100002994</code> 
Parsed data:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 4A
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="25" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 41 2C EE 00 (GMT: Monday, June 10, 2019 11:36:32 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 11 (AVL ID: 17, Name: Axis X)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 1D
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 10 (AVL ID: 16, Name: Total Odometer)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01 5E 2C 88
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 0B (AVL ID: 11, Name: ICCID1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 35 44 C8 7A
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 0E (AVL ID: 14, Name: ICCID2)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 1D D7 E0 6A
|-
| style="vertical-align: middle; text-align: center;" |NX of X Byte IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 29 94
|-
|}

Server response: <code>00000001</code> 

*'''<big>Codec8 Extended protocol sending over UDP</big>'''

*'''UDP channel protocol'''

AVL data packet is the same as with Codec8, except Codec ID is changed to <code>0x8E</code>. 

*'''Communication with server'''

Module sends UDP channel packet with encapsulated AVL data packet. Server sends UDP channel packet with encapsulated response module validates AVL Packet ID and Number of accepted AVL elements. If server response with valid AVL Packet ID is not received within configured timeout, module can retry sending. 

*Example:

Module sends the data:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x00FE,
Packet ID – 0xCAFE 
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
IMEI Length – 0x000F 
IMEI – 0x313233343536373839303132333435
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x8E,
Number of Data – 0x02 
(Encoded using continuous bit stream)
|-
| style="vertical-align: middle; text-align: center;" |00FECAFE01
| style="vertical-align: middle; text-align: center;" |DD000F3133343536373839303132333435
| style="vertical-align: middle; text-align: center;" |8E02…(data elements)…02
|-
|}

Server must respond with acknowledgment:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x0005,
Packet ID – 0xCAFE,
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
Number of Accepted Data – 0x02
|-
| style="vertical-align: middle; text-align: center;" |0005CAFE01
| style="vertical-align: middle; text-align: center;" |DD02
|-
|} 

*'''Example'''

Hexadecimal stream of AVL Data Packet receiving and response in this example are given in hexadecimal form. The different fields of packet are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Received data in hexadecimal stream: 
<code>005FCAFE0107000F3335323039333038363430333635358E010000016B4F831C680100000000000000000000000000000000010005000100010100010011009D000100</code>
<code>10015E2C880002000B000000003544C87A000E000000001DD7E06A000001</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |00 5F
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |AVL Packet Header
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |IMEI Length
| style="vertical-align: middle; text-align: center;" |00 0F
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |33 35 32 30 39 33 30 38 36 34 30 33 36 35 35
|-
| rowspan="27" style="vertical-align: middle; text-align: center;" |AVL Data Array
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B 4F 83 1C 68 (GMT: Thursday, June 13, 2019 6:25:21 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 11 (AVL ID: 17, Name: Axis X)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 1D
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 10 (AVL ID: 16, Name: Total Odometer)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01 5E 2C 88
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 0B (AVL ID: 11, Name: ICCID1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 35 44 C8 7A
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 0E (AVL ID: 14, Name: ICCID2)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 1D D7 E0 6A
|-
| style="vertical-align: middle; text-align: center;" |NX of X Byte IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
|}

Server response in hexadecimal stream:
<code>0005CAFE010701</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Response to AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |Server Response Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |07
|-
| style="vertical-align: middle; text-align: center;" |Number of Accepted Data
| style="vertical-align: middle; text-align: center;" |01
|-
|} 

=='''<big>Codec 16</big>'''==

*'''<big>Protocol overview</big>'''

Codec16 is using for FMB630/FM63XY devices. This protocol looks familiar like Codec8 but they have some differences. Main differences between are shown in table below:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec16
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0x08
| style="vertical-align: middle; text-align: center;" |0x10
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element ID event length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element AVL ID length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Generation Type
| style="vertical-align: middle; text-align: center;" |Not Using
| style="vertical-align: middle; text-align: center;" |Is Using
|-
|}

'''Note:''' Codec16 is supported from firmware – 00.03.xx and newer. ([[FMB630]]/FM63XY) || AVL ID‘s which are higher than 255 will can be used only in Codec16 protocol. 

*'''<big>Codec 16 protocol sending over TCP</big>'''

*'''AVL data packet'''

Below table represents AVL data packet structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Field Length
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Number of Data 2
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' – the packet starts with four zero bytes. 
'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2. 
'''Codec ID''' – in Codec16 it is always 0x10. 
'''Number of Data 1''' – a number which defines how many records is in the packet. 
'''AVL Data''' – actual data in the packet (more information below). 
'''Number of Data 2''' – a number which defines how many records is in the packet. This number must be the same as “Number of Data 1”. 
'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 
'''Note:''' for [[FMB630]] and FM63XY, minimum AVL packet size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 255 bytes. 

*AVL Data

Below table represents AVL Data structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Timestamp
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |GPS Element
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |IO Element
|-
| style="vertical-align: middle; text-align: center;" |8 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |15 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
|-
|}

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time). 
'''Priority''' – field which define AVL data priority (more information below). 
'''GPS Element''' – location information of the AVL data (more information below). 
'''IO Element''' – additional configurable information from device (more information below). 

*Priority

Below table represents Priority values. Packet priority depends on device configuration and records sent.
{| class="nd-othertables_2" style="width:25%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Priority
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |0
| style="vertical-align: middle; text-align: center;" |Low
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |High
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |2
| style="vertical-align: middle; text-align: center;" |Panic
|} 

*GPS element

Below table represents GPS Element structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Longitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Latitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Altitude
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Angle
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Satellites
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Speed
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
|}

'''Longitude''' – east – west position. 
'''Latitude''' – north – south position. 
'''Altitude''' – meters above sea level. 
'''Angle''' – degrees from north pole. 
'''Satellites''' – number of visible satellites. 
'''Speed''' – speed calculated from satellites. 
'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid. 
Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula: 
[[Image:GPS.png]]
 
Where: 
d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000) 
If longitude is in west or latitude in south, multiply result by –1. 
Note: 
To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, coordinate is positive, if it is <code>1</code>, coordinate is negative. 
Example: 
Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic. 

*IO Element

{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
| rowspan="27" style=" width:5%; vertical-align: middle; text-align: left;" |
| rowspan="27" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state changed and it generate event, Event IO ID will be 0xEF (AVL ID: 239). If it’s not eventual record – the value is 0. 
'''Generation type''' - data event generation type. More information about it you can find here. 
'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8). 
'''N1''' – number of properties, which length is 1 byte. 
'''N2''' – number of properties, which length is 2 bytes. 
'''N4''' – number of properties, which length is 4 bytes. 
'''N8''' – number of properties, which length is 8 bytes. 
'''N’th IO ID''' - AVL ID. 
'''N’th IO Value''' - AVL ID value. 
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |Generation Type
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N of Total IO
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N1’th IO Value
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2 of Two Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N2’th IO Value
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4 of Four Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N4’th IO Value
| style="vertical-align: middle; text-align: center;" |4 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8 of Eight Bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |8 byte
|-
| colspan="2" style="vertical-align: middle; text-align: center;" |...
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO ID
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |N8’IO Value
| style="vertical-align: middle; text-align: center;" |8 bytes
|-
|} 

*Generation type

{| class="nd-othertables_2" style="width:30%;"
|+
! rowspan="1" style="width:50%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Value
! rowspan="1" style="width:50%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Record Created
|-
| style="vertical-align: middle; text-align: center;" |0
| style="vertical-align: middle; text-align: center;" |On Exit
|-
| style="vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |On Entrance
|-
| style="vertical-align: middle; text-align: center;" |2
| style="vertical-align: middle; text-align: center;" |On Both
|-
| style="vertical-align: middle; text-align: center;" |3
| style="vertical-align: middle; text-align: center;" |Reserved
|-
| style="vertical-align: middle; text-align: center;" |4
| style="vertical-align: middle; text-align: center;" |Hysteresis
|-
| style="vertical-align: middle; text-align: center;" |5
| style="vertical-align: middle; text-align: center;" |On Change
|-
| style="vertical-align: middle; text-align: center;" |6
| style="vertical-align: middle; text-align: center;" |Eventual
|-
| style="vertical-align: middle; text-align: center;" |7
| style="vertical-align: middle; text-align: center;" |Periodical
|-
|} 

*'''Communication with server'''

Communication with server is the same as with Codec8 protocol, except in Codec16 protocol Codec ID is <code>0x10</code> and has generation type. 

*Example:

Module connects to server and sends IMEI: 
<code>000F333536333037303432343431303133</code> 
Server accepts the module: 
<code>01</code> 
Module sends data packet:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |Four Zero Bytes – 0x00000000,
“AVL Data Array” length – 0x000000FE
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x10,
Number of Data – '''0x02''' 
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”
|-
| style="vertical-align: middle; text-align: center;" |00000000000000FE
| style="vertical-align: middle; text-align: center;" |10'''02'''...(data elements)...'''02'''
| style="vertical-align: middle; text-align: center;" |00008612
|-
|}

Server acknowledges data reception (2 data elements): '''<code>00000002</code>''' 

*'''Example'''

Hexadecimal stream of AVL Data Packet receiving and response in this example are given in hexadecimal form. The different fields of packet are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Received data in hexadecimal stream: 
<code>000000000000005F10020000016BDBC7833000000000000000000000000000000000000B05040200010000030002000B00270042563A00000000016BDBC78718</code>
<code>00000000000000000000000000000000000B05040200010000030002000B00260042563A00000200005FB3</code> 
Parsed data:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 5F
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |10
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |02
|-
| rowspan="23" style="vertical-align: middle; text-align: center;" |AVL Data
(1'st record)
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 83 30 (GMT: Wednesday, July 10, 2019 12:06:54 PM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 0B
|-
| style="vertical-align: middle; text-align: center;" |Generation Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |04
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 03 (AVL ID: 3, Name: DIN3)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 0B (AVL ID: 11, Name: ICCID1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 27
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |56 3A
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| rowspan="23" style="vertical-align: middle; text-align: center;" |AVL Data
(2'nd record)
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 87 18 (GMT: Wednesday, July 10, 2019 12:06:55 PM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 0B
|-
| style="vertical-align: middle; text-align: center;" |Generation Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |04
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 03 (AVL ID: 3, Name: DIN3)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 0B (AVL ID: 11, Name: ICCID1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 26
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |56 3A
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 5F B3
|-
|}

Server response: <code>00000002</code> 

*'''<big>Codec16 Extended protocol sending over UDP</big>'''
*'''UDP channel protocol'''

AVL data packet is the same as with Codec8, except Codec ID is changed to <code>0x10</code>. 

*'''Communication with server'''

Module sends UDP channel packet with encapsulated AVL data packet. Server sends UDP channel packet with encapsulated response module validates AVL Packet ID and Number of accepted AVL elements. If server response with valid AVL Packet ID is not received within configured timeout, module can retry sending. 

*Example:

Module sends the data:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Array
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x00FE,
Packet ID – 0xCAFE 
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
IMEI Length – 0x000F 
IMEI – 0x313233343536373839303132333435
(Encoded using continuous bit stream. Last byte padded to align to byte boundary)
| style="vertical-align: middle; text-align: center;" |Codec ID – 0x10,
Number of Data – 0x02 
(Encoded using continuous bit stream)
|-
| style="vertical-align: middle; text-align: center;" |00FECAFE01
| style="vertical-align: middle; text-align: center;" |DD000F3133343536373839303132333435
| style="vertical-align: middle; text-align: center;" |1002…(data elements)…02
|-
|}

Server must respond with acknowledgment:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |UDP Channel Header
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
|-
| style="vertical-align: middle; text-align: center;" |Length – 0x0005,
Packet ID – 0xCAFE,
Not Usable Byte – 0x01
| style="vertical-align: middle; text-align: center;" |AVL Packet ID – 0xDD,
Number of Accepted Data – 0x02
|-
| style="vertical-align: middle; text-align: center;" |0005CAFE01
| style="vertical-align: middle; text-align: center;" |DD02
|-
|} 

*'''Example'''

Hexadecimal stream of AVL Data Packet receiving and response in this example are given in hexadecimal form. The different fields of packet are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Received data in hexadecimal stream: 
<code>015BCAFE0101000F33353230393430383532333135393210070000015117E40FE80000000000000000000000000000000000EF05050400010000030000B4000</code>
<code>0EF01010042111A000001</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |01 5B
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |AVL Packet Header
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |07
|-
| style="vertical-align: middle; text-align: center;" |IMEI Length
| style="vertical-align: middle; text-align: center;" |00 0F
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |33 35 32 30 39 34 30 38 35 32 33 31 35 39 32
|-
| rowspan="28" style="vertical-align: middle; text-align: center;" |AVL Data Array
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |10
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 51 17 E4 0F E8 (GMT: Wednesday, November 18, 2015 12:00:01 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 EF
|-
| style="vertical-align: middle; text-align: center;" |Generation type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |04
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 01 (AVL ID: 1, Name: DIN1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 03 (AVL ID: 3, Name: DIN3)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 B4 (AVL ID: 180, Name: DOUT2)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID: 239, Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |4’th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |11 1A
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
|}

Server response in hexadecimal stream:
<code>0005CAFE010700</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Response to AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |Server Response Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" style="vertical-align: middle; text-align: center;" |UDP Channel Header
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |Packet ID
| style="vertical-align: middle; text-align: center;" |CA FE
|-
| style="vertical-align: middle; text-align: center;" |Not usable byte
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |AVL Packet Acknowledgment
| style="vertical-align: middle; text-align: center;" |AVL packet ID
| style="vertical-align: middle; text-align: center;" |07
|-
| style="vertical-align: middle; text-align: center;" |Number of Accepted Data
| style="vertical-align: middle; text-align: center;" |00
|-
|} 

=='''<big>Differences between Codec 8, Codec 8 Extended and Codec 16</big>'''==
In the table below you will see differences between Codec8, Codec8 Extended and Codec16.
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8 Extended
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec16
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0x08
| style="vertical-align: middle; text-align: center;" |0x8E
| style="vertical-align: middle; text-align: center;" |0x10
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element total IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Generation Type
| style="vertical-align: middle; text-align: center;" |Is Using
| style="vertical-align: middle; text-align: center;" |Not Using
| style="vertical-align: middle; text-align: center;" |Is Using
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element AVL ID length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Variable size IO elements
| style="vertical-align: middle; text-align: center;" |Does not include
| style="vertical-align: middle; text-align: center;" |Includes variable size elements
| style="vertical-align: middle; text-align: center;" |Does not include
|-
|} 

='''<big>Codec for communication over GPRS messages</big>'''=
In this chapter you will find information about every Codec protocol which are using for communication over GPRS messages and differences between them.

=='''<big>Codec 12</big>'''==

*'''<big>About Codec12</big>'''

Codec12 is the original and main Teltonika protocol for device-server communication over GPRS messages. Codec12 GPRS commands can be used for sending configuration, debug, digital outputs control commands or other (special purpose command on special firmware versions). This protocol is also necessary for using [[FMB630]]/[[FM6300]]/FM5300/FM5500/FM4200 features like: Garmin, LCD communication, COM TCP Link Mode. 

*'''<big>FM firmware requirements</big>'''

Supported GPRS commands on each device depending on the firmware version. For available GPRS commands on each device, please refer to the table below.
{| class="nd-othertables" style="width:75%;"
|+
! rowspan="1" style="width:25%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Device
! rowspan="1" style="width:25%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |SMS over GPRS via TCP
! rowspan="1" style="width:25%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |SMS over GPRS via UDP
|-
| style="vertical-align: middle; text-align: left;" |FM36YX
| style="vertical-align: middle; text-align: center;" |Available in base firmware
| style="vertical-align: middle; text-align: center;" |Since base firmware 01.06.01
|-
| style="vertical-align: middle; text-align: left;" |FM63YX
| style="vertical-align: middle; text-align: center;" |Available in base firmware
| style="vertical-align: middle; text-align: center;" |Since base firmware 00.02.19
|-
| style="vertical-align: middle; text-align: left;" |FMB, FMC, FMM, FMU family devices (exclude FMB6YX, [[FMC640]], [[FMM640]])
| style="vertical-align: middle; text-align: center;" |Available in base firmware
| style="vertical-align: middle; text-align: center;" |Available in base firmware
|-
| style="vertical-align: middle; text-align: left;" |FMB6YX
| style="vertical-align: middle; text-align: center;" |Available in base firmware
| style="vertical-align: middle; text-align: center;" |Since base firmware 00.02.19
|-
| style="vertical-align: middle; text-align: left;" |[[FMC640]], [[FMM640]]
| style="vertical-align: middle; text-align: center;" |Available in base firmware
| style="vertical-align: middle; text-align: center;" |Available in base firmware
|-
|} 
'''Note:''' “SMS over GPRS” means that all standard SMS commands text can be sent to the device via GPRS in Codec12 format.

*'''<big>GPRS command session</big>'''

The following figure shows how the GRPS command session is started over TCP. 
[[File:Codec12.png|1150px]]
First, the Teltonika device opens the GPRS session and sends AVL data to the server (refer device protocols). Once all records are sent and correct sent data array acknowledgment is received by device then GPRS commands in Hex can be sent to the device. 
The ACK (acknowledge of IMEI from server) is a one-byte constant 0x01. The acknowledgment of each data array send from the device is four bytes integer – the number of records received. 
Note, that the GPRS session should remain active between device and server, while GPRS commands are sent. For this reason, active datalink timeout (global parameters in device configuration) is recommended to be set to 259200 (maximum value). 

*'''<big>General Codec12 message structure</big>'''

The following diagram shows basic structure of Codec12 messages. 
'''Command message structure:'''
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Quantity 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Type (0x05)
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Size
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Quantity 2
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Response message structure:'''
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response Quantity 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Type (0x06)
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response Size
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response Quantity 2
! rowspan="1" style="width:14%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' - the packet starts with four zero bytes. 
'''Data Size''' - size is calculated from Codec ID field to the second command or response quantity field. 
'''Codec ID''' - in Codec12 it is always <code>0x0C</code>. 
'''Command/Response Quantity 1''' - it is ignored when parsing the message. 
'''Type''' - it can be 0x05 to denote command or 0x06 to denote response. 
'''Command/Response Size''' – command or response length. 
'''Command/Response''' – command or response in HEX. 
'''Command/Response Quantity 2''' - a byte which defines how many records (commands or responses) is in the packet. This byte will not be parsed but it’s recommended that it should contain same value as Command/Response Quantity 1. 
'''CRC-16''' – calculated from Codec ID to the Command Quantity 2. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 
Note that difference between commands and responses is message type field: <code>0x05</code> means command and <code>0x06</code> means response. 

*'''<big>Command coding table</big>'''

Command has to be converted from ASCII characters (char) to hexadecimal (HEX): 
[[File:ASCII.png]] 

*'''<big>Command parsing example</big>'''

Hexadecimal stream of command and answer in this example is given in hexadecimal form. The different fields of the message are separated into different table columns for better readability and understanding. 

*'''<big>GPRS commands examples</big>'''

Hexadecimal stream of GPRS command and answer in these examples are given in hexadecimal form. The different fields of messages are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
'''1'st example:''' Sending ''[[FMB getinfo|getinfo]]'' SMS command via GPRS Codec12 
Server request in hexadecimal stream: 
<code>000000000000000F0C010500000007676574696E666F0100004312</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Command
|-
! rowspan="1" style="width:14%; vertical-align: middle; text-align: center;" |Server Command Part
! rowspan="1" style="width:14%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 0F
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0C
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Command Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Command Size
| style="vertical-align: middle; text-align: center;" |00 00 00 07
|-
| style="vertical-align: middle; text-align: center;" |Command
| style="vertical-align: middle; text-align: center;" |67 65 74 69 6E 66 6F
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 43 12
|-
|}

Note that Server Command converted from HEX to ASCII means ''[[FMB getinfo|getinfo]]'' 
Device response in hexadecimal stream: 
<code>00000000000000900C010600000088494E493A323031392F372F323220373A3232205254433A323031392F372F323220373A3533205253543A32204552523A</code>
<code>312053523A302042523A302043463A302046473A3020464C3A302054553A302F302055543A3020534D533A30204E4F4750533A303A3330204750533A312053</code>
<code>41543A302052533A332052463A36352053463A31204D443A30010000C78F</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Device Answer
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Device Answer Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 90
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0C
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Response Type
| style="vertical-align: middle; text-align: center;" |06
|-
| style="vertical-align: middle; text-align: center;" |Response Size
| style="vertical-align: middle; text-align: center;" |00 00 00 88
|-
| style="vertical-align: middle; text-align: center;" |Response
| style="vertical-align: middle; text-align: center;" |49 4E 49 3A 32 30 31 39 2F 37 2F 32 32 20 37 3A 32 32 20 52 54 43 3A 32 30 31 39 2F 37 2F 32 32 20 37 3A 35 33 20 52 53 54 3A 32 20 45 52 52 3A 31 20 53 52 3A 30 20 42 52 3A 30 20 43 46 3A 30 20 46 47 3A 30 20 46 4C 3A 30 20 54 55 3A 30 2F 30 20 55 54 3A 30 20 53 4D 53 3A 30 20 4E 4F 47 50 53 3A 30 3A 33 30 20 47 50 53 3A 31 20 53 41 54 3A 30 20 52 53 3A 33 20 52 46 3A 36 35 20 53 46 3A 31 20 4D 44 3A 30
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 C7 8F
|-
|} 
Note that Device Response converted from HEX to ASCII means: 
''INI:2019/7/22 7:22 RTC:2019/7/22 7:53 RST:2 ERR:1 SR:0 BR:0 CF:0 FG:0 FL:0 TU:0/0 UT:0 SMS:0 NOGPS:0:30 GPS:1 SAT:0 RS:3 RF:65 SF:1 MD:0'' 

'''2'nd example:''' Sending ''[[FMB getio|getio]]'' SMS command via GPRS Codec12 
Server request in hexadecimal stream: 
<code>000000000000000D0C010500000005676574696F01000000CB</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Command
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Server Command Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 0D
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0C
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Command Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Command Size
| style="vertical-align: middle; text-align: center;" |00 00 00 05
|-
| style="vertical-align: middle; text-align: center;" |Command
| style="vertical-align: middle; text-align: center;" |67 65 74 69 6F
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 00 CB
|-
|}

Note that Server Command converted from HEX to ASCII means ''[[FMB getio|getio]]'' 
Device response in hexadecimal stream: 
<code>00000000000000370C01060000002F4449313A31204449323A30204449333A302041494E313A302041494E323A313639323420444F313A3020444F323A3101000066E3</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Device Answer
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Device Answer Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 37
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0C
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Response Type
| style="vertical-align: middle; text-align: center;" |06
|-
| style="vertical-align: middle; text-align: center;" |Response Size
| style="vertical-align: middle; text-align: center;" |00 00 00 2F
|-
| style="vertical-align: middle; text-align: center;" |Response
| style="vertical-align: middle; text-align: center;" |44 49 31 3A 31 20 44 49 32 3A 30 20 44 49 33 3A 30 20 41 49 4E 31 3A 30 20 41 49 4E 32 3A 31 36 39 32 34 20 44 4F 31 3A 30 20 44 4F 32 3A 31
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 66 E3
|-
|}

Note that Device Response converted from HEX to ASCII means: 
''DI1:1 DI2:0 DI3:0 AIN1:0 AIN2:16924 DO1:0 DO2:1'' 

*'''<big>Communication with server</big>'''

The GSM/GPRS commands can be sent from a terminal program. We recommend to use Hercules (in TCP server mode). Simply write command as explained below into Hercules Send field, check HEX box and click Send button. Note that the TCP server must be listening on specified port (see Port field and Listen button below).

[[File:Hercules.jpeg]]
 

*'''<big>FMXX and Codec12 functionality</big>'''
*'''Garmin'''

All information is provided in “FMXX and Garmin development.pdf” document. 

*'''COM TCP Link Mode'''

All information is provided in “FMxx TCP Link mode test instructions.pdf” document.

=='''<big>Codec 13</big>'''==

*'''<big>About Codec13</big>'''

Codec13 is original Teltonika protocol for device-server communication over GPRS messages and it is based on Codec12 protocol. Main differences of Codec13 are that timestamp is using in messages and communication is one way only (Codec13 is used for Device -> Server sending). 

*'''<big>General Codec13 message structure</big>'''

The following diagram shows basic structure of Codec 13 messages:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (Preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data Size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec ID
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Quantity 1
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Type
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Timestamp
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command Quantity 2
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' – the packet starts with preamble field (four zero bytes). 
'''Data Size''' – size is calculated from Codec ID field to the second Command Quantity field. 
'''Codec ID''' – in Codec13 it is always <code>0x0D</code>. 
'''Command Quantity 1''' – <code>0x01</code>, it is ignored when parsing the message. 
'''Command Type''' – it is always <code>0x05</code> since the packet is direction is FM->Server. 
'''Command Size''' – command size field includes size of timestamp too, so it is equal to size of payload + size of timestamp. 
'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time). 
'''Command''' – actual received data. 
'''Command Quantity 2''' – a byte which defines how many records (commands) is in the packet. This byte will not be parsed but it’s recommended that it should contain same value as Command/Response Quantity 1. 
'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 
'''Note:''' Codec13 packets are used only when “Message Timestamp” parameter in RS232 settings is enabled. 

*'''<big>Command parsing example</big>'''

Hexadecimal stream of GPRS command in this example is given in hexadecimal form. The different fields of message are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Sending ''[[FMB getinfo|getinfo]]'' SMS command via GPRS Codec13. 
Hexadecimal stream: 
<code>00000000000000170D01050000000F0A81C320676574696E666F0100006855</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Command
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Server Command Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 17
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0D
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Command Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Command Size
| style="vertical-align: middle; text-align: center;" |00 00 00 07
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |0A 81 C3 20
|-
| style="vertical-align: middle; text-align: center;" |Command
| style="vertical-align: middle; text-align: center;" |67 65 74 69 6E 66 6F
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 68 55
|-
|}

Note that Server Command converted from HEX to ASCII means ''[[FMB getinfo|getinfo]]''

=='''<big>Codec 14</big>'''==

*'''<big>About Codec14</big>'''

Codec14 is original Teltonika protocol for device-server communication over GPRS messages and it is based on Codec12 protocol. 
Main difference of Codec14 is that, device will answer to GPRS command if device physical IMEI number matches specified IMEI number in GPRS command. 

Codec14 GPRS commands can be used for sending configuration, debug, digital outputs control commands or other (special purpose command on special firmware versions). 

*'''<big>FMB firmware requirements</big>'''

Implemented in base firmware from FMB.Ver.03.25.04.Rev.00 and newer. 

*'''<big>General Codec14 message structure</big>'''

The following diagram shows basic structure of Codec14 messages. 

'''Command message structure'''
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x0E (Codec ID)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command quantity
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x05 (Message type)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command size + IMEI size (8 bytes)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |IMEI (HEX)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Command quantity
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |8 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Response message structure'''
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x00000000 (preamble)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Data size
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x0E (Codec ID)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response quantity
! colspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |0x06 / 0x11 (Message type)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response size + IMEI size (8 bytes)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |IMEI (HEX)
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Response quantity
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |CRC-16
|-
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
| style="vertical-align: middle; text-align: center;" |8 bytes
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |1 bytes
| style="vertical-align: middle; text-align: center;" |4 bytes
|-
|}

'''Preamble''' – the packet starts with four zero bytes. 
'''Data Size''' – size is calculated from Codec ID field to the second command or response quantity field. 
'''Codec ID''' – in Codec14 it is always <code>0x0E</code>. 
'''Command/Response Quantity 1''' – it is ignored when parsing the message. 
'''Type''' – if it is request command from server it has to contain 0x05. The response type field will contain <code>0x06</code> if it’s ACK or <code>0x11</code> if it’s nACK. 
''Explanation:'' If command message IMEI is equal to actual device IMEI, received command will be executed and response will be sent with ACK (<code>0x06</code>) message type field value. If command message IMEI doesn’t match actual device IMEI, received command won’t be executed and response to server will be sent with nACK (<code>0x11</code>) message type field value. 
'''Command/Response Size''' – command or response length. 
''Note:'' make sure that size is IMEI size 8 + actual command size. Minimal value is 8 because Codec14 always contain IMEI and it’s 8 bytes. 
'''IMEI (HEX)''' – it is send as HEX value. Example if device IMEI is 123456789123456 then IMEI data field will contain <code>0x0123456789123456</code> value. 
'''Command/Response''' – command or response in HEX. 
'''Command/Response Quantity 2''' - a byte which defines how many records (commands or responses) is in the packet. This byte will not be parsed but it’s recommended that it should contain same value as Command/Response Quantity 1. '''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]]. 

*'''<big>GPRS in Codec14 examples</big>'''

Hexadecimal stream of GPRS command and answer in this example are given in hexadecimal form. The different fields of message are separate into different table columns for better readability and some of them are converted to ASCII values for better understanding. 
Sending ''[[FMB getver|getver]]'' SMS command via GPRS Codec14: 
Server requests in Hexadecimal stream: 
<code>00000000000000160E01050000000E0352093081452251676574766572010000D2C1</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Server Command
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Server Command Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 16
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0E
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Command Type
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Command Size
| style="vertical-align: middle; text-align: center;" |00 00 00 0E
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |03 52 09 30 81 45 22 51
|-
| style="vertical-align: middle; text-align: center;" |Command
| style="vertical-align: middle; text-align: center;" |67 65 74 76 65 72
|-
| style="vertical-align: middle; text-align: center;" |Command Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 D2 C1
|-
|}

Note that Server Command converted from HEX to ASCII means ''[[FMB getver|getver]]'' 
Device ACK response in hexadecimal stream: 
<code>00000000000000AB0E0106000000A303520930814522515665723A30332E31382E31345F3034204750533A41584E5F352E31305F333333332048773A464D42313230</code>
<code>204D6F643A313520494D45493A33353230393330383134353232353120496E69743A323031382D31312D323220373A313320557074696D653A3137323334204D4143</code>
<code>3A363042444430303136323631205350433A312830292041584C3A30204F42443A3020424C3A312E362042543A340100007AAE</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Device Answer
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Device Answer Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 37
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0E
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Response Type
| style="vertical-align: middle; text-align: center;" |06
|-
| style="vertical-align: middle; text-align: center;" |Response Size
| style="vertical-align: middle; text-align: center;" |00 00 00 A3
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |03 52 09 30 81 45 22 51
|-
| style="vertical-align: middle; text-align: center;" |Response
| style="vertical-align: middle; text-align: center;" |56 65 72 3A 30 33 2E 31 38 2E 31 34 5F 30 34 20 47 50 53 3A 41 58 4E 5F 35 2E 31 30 5F 33 33 33 33 20 48 77 3A 46 4D 42 31 32 30 20 4D 6F 64 3A 31 35 20 49 4D 45 49 3A 33 35 32 30 39 33 30 38 31 34 35 32 32 35 31 20 49 6E 69 74 3A 32 30 31 38 2D 31 31 2D 32 32 20 37 3A 31 33 20 55 70 74 69 6D 65 3A 31 37 32 33 34 20 4D 41 43 3A 36 30 42 44 44 30 30 31 36 32 36 31 20 53 50 43 3A 31 28 30 29 20 41 58 4C 3A 30 20 4F 42 44 3A 30 20 42 4C 3A 31 2E 36 20 42 54 3A 34
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 7A AE
|-
|}

Note that Device Response converted from HEX to ASCII means: 
''Ver:03.18.14_04 GPS:AXN_5.10_3333 Hw:FMB120 Mod:15 IMEI:352093081452251 Init:2018-11-22 7:13 Uptime:17234 MAC:60BDD0016261 SPC:1(0) AXL:0 OBD:0 BL:1.6 BT:4'' 
Device nACK response in hexadecimal stream: 
<code>00000000000000100E011100000008035209308145246801000032AC</code> 
Parsed:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Device Answer
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Device Answer Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Size
| style="vertical-align: middle; text-align: center;" |00 00 00 10
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0E
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 1
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Response Type
| style="vertical-align: middle; text-align: center;" |11
|-
| style="vertical-align: middle; text-align: center;" |Response Size
| style="vertical-align: middle; text-align: center;" |00 00 00 08
|-
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |03 52 09 30 81 45 24 68
|-
| style="vertical-align: middle; text-align: center;" |Response Quantity 2
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 32 AC
|-
|} 

=='''<big>Differences between Codec 12, Codec 13 and Codec 14</big>'''==
In the table below you will see differences between Codec12, Codec13 and Codec14.
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec12
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec13
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec14
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Communication
| style="vertical-align: middle; text-align: center;" |Server - Device Communication
| style="vertical-align: middle; text-align: center;" |One-way (Device -> Server communication)
| style="vertical-align: middle; text-align: center;" |Server - Device Communication
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0x0C
| style="vertical-align: middle; text-align: center;" |0x0D
| style="vertical-align: middle; text-align: center;" |0x0E
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Response Message Type
| style="vertical-align: middle; text-align: center;" |0x06
| style="vertical-align: middle; text-align: center;" | -
| style="vertical-align: middle; text-align: center;" |0x06 (if it is ACK) or 0x11 (if it is nACK)
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Command / Response size
| style="vertical-align: middle; text-align: center;" |Only Command/Response
| style="vertical-align: middle; text-align: center;" |Only Command
| style="vertical-align: middle; text-align: center;" |Command/Response + IMEI
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |Not Using
| style="vertical-align: middle; text-align: center;" |Is Using
| style="vertical-align: middle; text-align: center;" |Not Using
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |Not Using
| style="vertical-align: middle; text-align: center;" |Not Using
| style="vertical-align: middle; text-align: center;" |Is Using
|-
|} 

='''<big>24 Position SMS Data Protocol</big>'''=

24-hour SMS is usually sent once every day and contains GPS data of last 24 hours. TP-DCS field of this SMS should indicate that message contains 8-bit data (i.e. TP-DCS can be <code>0x04</code>). 
Note, that 24 position data protocol is used only with subscribed SMS. Event SMS use standard AVL data protocol. 

*'''<big>Encoding</big>'''

To be able to compress 24 GPS data entries into one SMS (140 octets), the data is encoded extensively using bit fields. Data packet can be interpreted as a bit stream, where all bits are numbered as follows:
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Byte 1
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Byte 2
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Byte 3
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Byte 4 ...
|-
| style="vertical-align: middle; text-align: center;" |Bits 0 - 7
| style="vertical-align: middle; text-align: center;" |Bits 8 - 15
| style="vertical-align: middle; text-align: center;" |Bits 16 - 24
| style="vertical-align: middle; text-align: center;" |Bits 25 - ...
|-
|}

Bits in a byte are numbered starting from least significant bit. A field of 25 bits would consist of bits 0 to 24 where 0 is the least significant bit and bit 24 – most significant bit. 

*'''<big>Structure</big>'''

Below in the tables you will see SMS Data Structure:
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |SMS Data Structure
|-
| style="width:10%; vertical-align: middle; text-align: center;" |8
| style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="width:10%; vertical-align: middle; text-align: center;" |Codec ID = 4 (0x04)
|-
| style="vertical-align: middle; text-align: center;" |35
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |Time corresponding to the first (oldest) GPS data element, represented in seconds elapsed from 2000.01.01 00:00 EET.
|-
| style="vertical-align: middle; text-align: center;" |5
| style="vertical-align: middle; text-align: center;" |ElementCount
| style="vertical-align: middle; text-align: center;" |Number of GPS data elements
|-
|} 
{| class="nd-othertables_2" style="width:100%;"
|+

! colspan="4" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |SMS Data Structure
|-
| rowspan="3" style="width:10%; vertical-align: middle; text-align: center;" |ElementCount *
| style="width:10%; vertical-align: middle; text-align: center;" |
| style="width:10%; vertical-align: middle; text-align: center;" |GPSDataElement
| style="width:10%; vertical-align: middle; text-align: center;" |GPS data elements
|-
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Byte - align padding
| style="vertical-align: middle; text-align: center;" |Padding bits to align to 8 - bits boundary represented in seconds elapsed from 2000.01.01 00:00 EET.
|-
| style="vertical-align: middle; text-align: center;" |64
| style="vertical-align: middle; text-align: center;" |IMEI
| style="vertical-align: middle; text-align: center;" |IMEI of sending device as 8 byte long integer
|-
|}

The time of only the first GPS data element is specified in Timestamp field. Time corresponding to each further element can be computed as elementTime = Timestamp + (1 hour * elementNumber). 
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="5" rowspan="1" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |GPS Data Element
|-
! rowspan="1" style="width:20%; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:20%; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:12%; vertical-align: middle; text-align: center;" |Size (bits)
! colspan="1" style="width:20%; vertical-align: middle; text-align: center;" |Field
! rowspan="1" style="width:28%; vertical-align: middle; text-align: center;" |Description
|-
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |ValidElement
| style="vertical-align: middle; text-align: center;" |ValidElement = 1 – there is a valid Gps Data Element following,
ValidElement = 0 – no element at this position
|-
| rowspan="5" style="vertical-align: middle; text-align: center;" |ValidElement == 1
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |1
| style="vertical-align: middle; text-align: center;" |DifferentialCoords
| style="vertical-align: middle; text-align: center;" |Format of following data
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |DifferentialCoords == 1
| style="vertical-align: middle; text-align: center;" |14
| style="vertical-align: middle; text-align: center;" |LongitudeDiff
| style="vertical-align: middle; text-align: center;" |Difference from previous element‘s longitude.
LongitudeDiff = prevLongitude – Longitude + 213 – 1
|-
| style="vertical-align: middle; text-align: center;" |14
| style="vertical-align: middle; text-align: center;" |LatitudeDiff
| style="vertical-align: middle; text-align: center;" |Difference from previous element‘s latitude
LatitudeDiff = prevLatitude – Latitude + 213 – 1
|-
| rowspan="2" style="vertical-align: middle; text-align: center;" |DifferentialCoords == 0
| style="vertical-align: middle; text-align: center;" |21
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |Longitude = {(LongDegMult + 18 * 108) * (221 – 1)} over {36*108}
|-
| style="vertical-align: middle; text-align: center;" |20
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |Latitude = (LatDegMult + 9*108) * (220 – 1) over {18*108}
|-
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |8
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |Speed in km/h
|-
|}

'''Longitude''' - longitude field value of GPSDataElement 
'''Latitude''' - latitude field value of GPSDataElement 
'''LongDegMult''' - longitude in degrees multiplied by 107 (integer part) 
'''LatDegMult''' - latitude in degrees multiplied by 107 (integer part) 
'''prevLongitude''' - longitude field value of previous GPSDataElemen 
'''prevLatitude''' - latitude field value of previous GPSDataElement 

*'''<big>Decoding GPS position</big>'''

When decoding GPS data with DifferentialCoords = 1, Latitude and Longitude values can be computed as follows: Longitude = prevLongitude – LongitudeDiff + 213 – 1, Latitude = prevLatitude – LatitudeDiff + 213 – 1. 
If there were no previous non-differential positions, differential coordinates should be computed assuming prevLongitude = prevLatitude = 0. 
When Longitude and Latitude values are known, longitude and latitude representation in degrees can be computed as follows:

[[File:24SMS.png]]

*'''<big>SMS Events</big>'''

When Configured to generate SMS event user will get this SMS upon event: 
''<Year/Month/Day> <Hour:Minute:Second> P:<profile_nr> <SMS Text> Val:<Event Value> Lon:<longitude> Lat:<latitude> Q:<HDOP>'' 
Example: 
''2016./04/11 12:00:00 P:3 Digital Input 1 Val:1 Lon:51.12258 Lat: 25.7461 Q:0.6'' 

='''<big>Sending data using SMS</big>'''=
This type data sending is using for FMBXXX devices which can be configured in [[FMB120 SMS/Call settings#SMS Data Sending|SMS Data Sending settings]]. 

*'''<big>Data sending via SMS</big>'''

AVL data or events can be sent encapsulated in binary SMS. TP-DCS field of these SMS should indicate that message contains 8-bit data (for example: TP-DCS can be <code>0x04</code>).
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |SMS data (TP-UD)
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL data array
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |IMEI
|-
| style="vertical-align: middle; text-align: center;" |X bytes
| style="vertical-align: middle; text-align: center;" |8 bytes
|-
|}

'''AVL data array''' – array of encoded AVL data. 
'''IMEI''' – IMEI of sending module encoded as a big endian 8 byte long number.

='''<big>CRC-16</big>'''=
CRC (Cyclic Redundancy Check) is an error-detecting code using for detect accidental changes to RAW data. The algorithm how to calculate CRC-16 (also known as CRC-16/IBM) you will find below. 
[[File:CRC16.png]]

FMC640 Product Change Notifications

2020-10-27T12:58:54Z

Renat Galiachmetov: /* 2020.10.26: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.26: Base firmware update==

We would like to inform you about base firmware update for FMC640 starting from October 26th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMC640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMC640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMC640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMC640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 26th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}
[[Category: FMC640]]

FMC640 Product Change Notifications

2020-10-27T12:58:00Z

Renat Galiachmetov: /* 2020.10.14: Top Marking Changes */

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.25: Base firmware update==

We would like to inform you about base firmware update for FMC640 starting from October 25th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMC640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMC640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMC640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMC640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 25th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}
[[Category: FMC640]]

Template:FMC640 & FMM640 firmware errata

2020-10-27T12:55:49Z

Renat Galiachmetov: /* Firmware versions */

FMM640 Product Change Notifications

2020-10-27T12:53:51Z

Renat Galiachmetov: /* 2020.10.26: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.26: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 26th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 26th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMB640 Product Change Notifications

2020-10-27T12:52:59Z

Renat Galiachmetov: /* 2020.10.26: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.26: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 26th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 26th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMB640 firmware errata

2020-10-27T12:52:27Z

Renat Galiachmetov: /* Firmware versions */

__TOC__
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world. 
This document describes '''FMB640 ''' devices firmware improvements, changes, new features implementations as well as current firmware release version.

===Firmware versioning===
*Structure
FM.VER.[XX].[YY].[ZZ]
*Syntax description
**<code>XX</code> – client number. Value range: 00 – Teltonika, 02..99 – Specific clients
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – minor changes like small fixes, improvements and new minor features addition.

===Firmware versions===
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''01.00.05''' (Current firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.10.26
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Tachograph FrontPanel improvements
* Additional tachograph parameters added
* AutoCAN reading improvements
* Sleep modes improvements
* Battery charging/discharging improved
* Tracking On demand added
* LVCAN DTC codes reading improvements
* 1Wire TSH202 multiple sensors support added
* Periodical TSM232 SBD records saving improvements
* TCP buffering to SD card added
* GPRS Remote log improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.79'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.08.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |

*Tachograph driver data handling improvements
*Tacho download improvements
*Record send stability improved
*AutoCAN, ManualCAN improvements
*Tachograph data reading improvements
*TSM232 stability improvements.
*Added TSM232 check feature in Configurator Status>Maintenance Tab.
*Added Geofence Over speeding DOUT control in every geozone.
*Added Dout Control to every geozone.
*TPMS funcionality improvements
*Added Custom scenario event onExit feature.
*Added DOUT control in progress event reset.
*Added FMS Tell status IOs
*Garmin improvements
*LVCAN,ALLCAN, CAN-CONTROL reading improvements
*DSleep logic improvements
*COM modes stability improvements
*TCP,UDP packets handling improve
*Internal improvements for manufacture
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.65''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* UDP data sending improvements
* Battery charge mode parameter added
* GPS FIX time after sleep improved
* Wake up from sleep modes improved
* FrontPanel DDD files sending stability improvements
* K-Line midnight record saving logic changed
* ManualCAN improvements
* Tachograph data reading improvements
* FMC640, FMM640 support added
* Movement source parameter added
* IO elements data sending mode added
* GALILEO and BEIDOU selection for GNSS mode added
* Device and FOTAWEB communication stability improvements
* Carrier freezer new parameters added
* LVCAN, ALLCAN communication improved
* CAN-CONTROL with DTC reading added
* LLS fuel sensor reading stability improved
* Immobilizer improvements
* iButton read notification improvements
* Accelerometer autocalibration logic improved
* Continental TPMS improvements
* New type of zone for Manual geofence added
|-w

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.50''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.06.19
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DTCO VDO 4.0 tachograph support added
* Tachograph data sending improvements
* Records saving to SD card improvements
* Ping mode improvements
* GPS sleep mode improvements
* DOUT control improvements
* Configuration stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.45''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.04.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Carrier freezer support added
* Tachograph data sending improvements
* LVCAN setting program nr. via configurator added
* Odometer value improvements
* Accelerometer improvements added
* Additional FMS parameters added
* CAN CONTROL functionality added
* FOTA Web functionality improvements
* DOUT control improvements
* SMS/GPRS commands improvements
* iButton functionality improvements
* FrontPanel DDD files reading support added
* GPRS stability improvements
* NTP improvements
* Deep sleep consumption improvements
* Alternative DDD card download added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.21''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* K-Line improvements
* Sleep mode improvements
* Data sending improvements
* Custom Scenarios functionality added
* Additional MCAN parameters added
* Static Navigation deactivation source added
* New function for iButton notifications scenario added
* K-Line record merged with periodic record
* Configurator changes. FMS I/O parameter "Distance" moved to Tachograph Data tab
* Tachograph communication improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.14''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.04
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FMS IO AdBlue parameter added
* LVCAN stability improvements
* Manual CAN2 list implemented
* GPRS Limits added
* DOUT control via call functionality added
* Autogeofence deactivate by Engine RPM added
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.08'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.12.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FOTA Web stability improvements
* Data sending improvements
* Tacho download improvements
* Dual server functionality improvements
* IO elements configuration improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.04'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.11.27
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* MobilEye support added
* 100 geozones support added
* MCAN2 support added
* DOUT control improvements
* Battery charge improvements
* Records saving and sending improvements
* SMS commands improvements
* Immobilizer scenario improvements
* Crach detection improvements
* Status window implemented
* Tachocheck SMS command improvements
* Dual server functionality improvements
* Overspeeding scenario improvements
* Device stability improvements
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.01.05'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.08.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CAN adapter (LV-CAN200/ALL-CAN300) improvements
* ADC (Analog to Digital Converter) accuracy improvement
* J1708 CAN Fuel Level/Consumption parameters added
* Quectell Hardware support added
* Zbit flash added
* USB connection improvements
* "On Delta Change" operand (event generating) added.
* Codec 12 parsing improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.00.13'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.05.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* SMS sending for panic records added to code.
* SMS events improvements.
* Tachograph auto connect improved.
* Fota Web support added
* Deep Sleep Improvements
* USB improvements
|}
[[Category:FMB640]]

FMM640 Product Change Notifications

2020-10-27T12:51:14Z

Renat Galiachmetov: /* 2020.10.14: Top Marking Changes */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.25: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 25th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 25th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMB640 Product Change Notifications

2020-10-27T12:49:18Z

Renat Galiachmetov: /* 2020.10.12: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.25: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 25th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 25th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMB640 Product Change Notifications

2020-10-27T12:49:03Z

Renat Galiachmetov: /* 2020.10.12: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.12: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 25th, 2020. New production firmware version will be '''01.00.05'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.05
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 25th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

Template:FMC640 & FMM640 firmware errata

2020-10-27T12:47:23Z

Renat Galiachmetov: /* Firmware versions */

FMB640 firmware errata

2020-10-27T12:45:03Z

Renat Galiachmetov: /* Firmware versions */

__TOC__
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world. 
This document describes '''FMB640 ''' devices firmware improvements, changes, new features implementations as well as current firmware release version.

===Firmware versioning===
*Structure
FM.VER.[XX].[YY].[ZZ]
*Syntax description
**<code>XX</code> – client number. Value range: 00 – Teltonika, 02..99 – Specific clients
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – minor changes like small fixes, improvements and new minor features addition.

===Firmware versions===
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''01.00.05''' (Current firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.10.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Tachograph FrontPanel improvements
* Additional tachograph parameters added
* AutoCAN reading improvements
* Sleep modes improvements
* Battery charging/discharging improved
* Tracking On demand added
* LVCAN DTC codes reading improvements
* 1Wire TSH202 multiple sensors support added
* Periodical TSM232 SBD records saving improvements
* TCP buffering to SD card added
* GPRS Remote log improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.79'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.08.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |

*Tachograph driver data handling improvements
*Tacho download improvements
*Record send stability improved
*AutoCAN, ManualCAN improvements
*Tachograph data reading improvements
*TSM232 stability improvements.
*Added TSM232 check feature in Configurator Status>Maintenance Tab.
*Added Geofence Over speeding DOUT control in every geozone.
*Added Dout Control to every geozone.
*TPMS funcionality improvements
*Added Custom scenario event onExit feature.
*Added DOUT control in progress event reset.
*Added FMS Tell status IOs
*Garmin improvements
*LVCAN,ALLCAN, CAN-CONTROL reading improvements
*DSleep logic improvements
*COM modes stability improvements
*TCP,UDP packets handling improve
*Internal improvements for manufacture
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.65''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* UDP data sending improvements
* Battery charge mode parameter added
* GPS FIX time after sleep improved
* Wake up from sleep modes improved
* FrontPanel DDD files sending stability improvements
* K-Line midnight record saving logic changed
* ManualCAN improvements
* Tachograph data reading improvements
* FMC640, FMM640 support added
* Movement source parameter added
* IO elements data sending mode added
* GALILEO and BEIDOU selection for GNSS mode added
* Device and FOTAWEB communication stability improvements
* Carrier freezer new parameters added
* LVCAN, ALLCAN communication improved
* CAN-CONTROL with DTC reading added
* LLS fuel sensor reading stability improved
* Immobilizer improvements
* iButton read notification improvements
* Accelerometer autocalibration logic improved
* Continental TPMS improvements
* New type of zone for Manual geofence added
|-w

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.50''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.06.19
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DTCO VDO 4.0 tachograph support added
* Tachograph data sending improvements
* Records saving to SD card improvements
* Ping mode improvements
* GPS sleep mode improvements
* DOUT control improvements
* Configuration stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.45''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.04.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Carrier freezer support added
* Tachograph data sending improvements
* LVCAN setting program nr. via configurator added
* Odometer value improvements
* Accelerometer improvements added
* Additional FMS parameters added
* CAN CONTROL functionality added
* FOTA Web functionality improvements
* DOUT control improvements
* SMS/GPRS commands improvements
* iButton functionality improvements
* FrontPanel DDD files reading support added
* GPRS stability improvements
* NTP improvements
* Deep sleep consumption improvements
* Alternative DDD card download added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.21''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* K-Line improvements
* Sleep mode improvements
* Data sending improvements
* Custom Scenarios functionality added
* Additional MCAN parameters added
* Static Navigation deactivation source added
* New function for iButton notifications scenario added
* K-Line record merged with periodic record
* Configurator changes. FMS I/O parameter "Distance" moved to Tachograph Data tab
* Tachograph communication improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.14''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.04
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FMS IO AdBlue parameter added
* LVCAN stability improvements
* Manual CAN2 list implemented
* GPRS Limits added
* DOUT control via call functionality added
* Autogeofence deactivate by Engine RPM added
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.08'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.12.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FOTA Web stability improvements
* Data sending improvements
* Tacho download improvements
* Dual server functionality improvements
* IO elements configuration improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.04'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.11.27
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* MobilEye support added
* 100 geozones support added
* MCAN2 support added
* DOUT control improvements
* Battery charge improvements
* Records saving and sending improvements
* SMS commands improvements
* Immobilizer scenario improvements
* Crach detection improvements
* Status window implemented
* Tachocheck SMS command improvements
* Dual server functionality improvements
* Overspeeding scenario improvements
* Device stability improvements
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.01.05'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.08.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CAN adapter (LV-CAN200/ALL-CAN300) improvements
* ADC (Analog to Digital Converter) accuracy improvement
* J1708 CAN Fuel Level/Consumption parameters added
* Quectell Hardware support added
* Zbit flash added
* USB connection improvements
* "On Delta Change" operand (event generating) added.
* Codec 12 parsing improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.00.13'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.05.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* SMS sending for panic records added to code.
* SMS events improvements.
* Tachograph auto connect improved.
* Fota Web support added
* Deep Sleep Improvements
* USB improvements
|}
[[Category:FMB640]]

Template:FMC640 & FMM640 firmware errata

2020-10-27T12:43:55Z

Renat Galiachmetov: /* Firmware versions */

FMB640 firmware errata

2020-10-27T12:42:33Z

Renat Galiachmetov: /* Firmware versions */

__TOC__
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world. 
This document describes '''FMB640 ''' devices firmware improvements, changes, new features implementations as well as current firmware release version.

===Firmware versioning===
*Structure
FM.VER.[XX].[YY].[ZZ]
*Syntax description
**<code>XX</code> – client number. Value range: 00 – Teltonika, 02..99 – Specific clients
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – minor changes like small fixes, improvements and new minor features addition.

===Firmware versions===
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''01.00.05''' (Current firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.10.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Tachograph FrontPanel improvements
* Additional tachograph parameters added
* Sleep modes improvements
* Battery charging/discharging improved
* Tracking On demand added
* LVCAN DTC codes reading improvements
* 1Wire TSH202 multiple sensors support added
* Periodical TSM232 SBD records saving improvements
* TCP buffering to SD card added
* GPRS Remote log improvements
* AutoCAN reading improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.79'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.08.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |

*Tachograph driver data handling improvements
*Tacho download improvements
*Record send stability improved
*AutoCAN, ManualCAN improvements
*Tachograph data reading improvements
*TSM232 stability improvements.
*Added TSM232 check feature in Configurator Status>Maintenance Tab.
*Added Geofence Over speeding DOUT control in every geozone.
*Added Dout Control to every geozone.
*TPMS funcionality improvements
*Added Custom scenario event onExit feature.
*Added DOUT control in progress event reset.
*Added FMS Tell status IOs
*Garmin improvements
*LVCAN,ALLCAN, CAN-CONTROL reading improvements
*DSleep logic improvements
*COM modes stability improvements
*TCP,UDP packets handling improve
*Internal improvements for manufacture
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.65''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* UDP data sending improvements
* Battery charge mode parameter added
* GPS FIX time after sleep improved
* Wake up from sleep modes improved
* FrontPanel DDD files sending stability improvements
* K-Line midnight record saving logic changed
* ManualCAN improvements
* Tachograph data reading improvements
* FMC640, FMM640 support added
* Movement source parameter added
* IO elements data sending mode added
* GALILEO and BEIDOU selection for GNSS mode added
* Device and FOTAWEB communication stability improvements
* Carrier freezer new parameters added
* LVCAN, ALLCAN communication improved
* CAN-CONTROL with DTC reading added
* LLS fuel sensor reading stability improved
* Immobilizer improvements
* iButton read notification improvements
* Accelerometer autocalibration logic improved
* Continental TPMS improvements
* New type of zone for Manual geofence added
|-w

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.50''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.06.19
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DTCO VDO 4.0 tachograph support added
* Tachograph data sending improvements
* Records saving to SD card improvements
* Ping mode improvements
* GPS sleep mode improvements
* DOUT control improvements
* Configuration stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.45''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.04.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Carrier freezer support added
* Tachograph data sending improvements
* LVCAN setting program nr. via configurator added
* Odometer value improvements
* Accelerometer improvements added
* Additional FMS parameters added
* CAN CONTROL functionality added
* FOTA Web functionality improvements
* DOUT control improvements
* SMS/GPRS commands improvements
* iButton functionality improvements
* FrontPanel DDD files reading support added
* GPRS stability improvements
* NTP improvements
* Deep sleep consumption improvements
* Alternative DDD card download added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.21''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* K-Line improvements
* Sleep mode improvements
* Data sending improvements
* Custom Scenarios functionality added
* Additional MCAN parameters added
* Static Navigation deactivation source added
* New function for iButton notifications scenario added
* K-Line record merged with periodic record
* Configurator changes. FMS I/O parameter "Distance" moved to Tachograph Data tab
* Tachograph communication improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.14''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.04
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FMS IO AdBlue parameter added
* LVCAN stability improvements
* Manual CAN2 list implemented
* GPRS Limits added
* DOUT control via call functionality added
* Autogeofence deactivate by Engine RPM added
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.08'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.12.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FOTA Web stability improvements
* Data sending improvements
* Tacho download improvements
* Dual server functionality improvements
* IO elements configuration improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.04'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.11.27
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* MobilEye support added
* 100 geozones support added
* MCAN2 support added
* DOUT control improvements
* Battery charge improvements
* Records saving and sending improvements
* SMS commands improvements
* Immobilizer scenario improvements
* Crach detection improvements
* Status window implemented
* Tachocheck SMS command improvements
* Dual server functionality improvements
* Overspeeding scenario improvements
* Device stability improvements
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.01.05'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.08.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CAN adapter (LV-CAN200/ALL-CAN300) improvements
* ADC (Analog to Digital Converter) accuracy improvement
* J1708 CAN Fuel Level/Consumption parameters added
* Quectell Hardware support added
* Zbit flash added
* USB connection improvements
* "On Delta Change" operand (event generating) added.
* Codec 12 parsing improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.00.13'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.05.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* SMS sending for panic records added to code.
* SMS events improvements.
* Tachograph auto connect improved.
* Fota Web support added
* Deep Sleep Improvements
* USB improvements
|}
[[Category:FMB640]]

FMB640 firmware errata

2020-10-27T12:40:48Z

Renat Galiachmetov: /* Firmware versions */

__TOC__
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world. 
This document describes '''FMB640 ''' devices firmware improvements, changes, new features implementations as well as current firmware release version.

===Firmware versioning===
*Structure
FM.VER.[XX].[YY].[ZZ]
*Syntax description
**<code>XX</code> – client number. Value range: 00 – Teltonika, 02..99 – Specific clients
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – minor changes like small fixes, improvements and new minor features addition.

===Firmware versions===
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''01.00.05''' (Current firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.10.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Tachograph FrontPanel improvements
* Additional tachograph parameters added
* Sleep modes improvements
* Battery charging/discharging improved
* Tracking On demand added
* LVCAN DTC codes reading improvements
* 1Wire TSH202 multiple sensors support added
* Periodical TSM232 SBD records saving improvements
* TCP buffering to SD card added
* GPRS Remote log improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.79'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.08.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |

*Tachograph driver data handling improvements
*Tacho download improvements
*Record send stability improved
*AutoCAN, ManualCAN improvements
*Tachograph data reading improvements
*TSM232 stability improvements.
*Added TSM232 check feature in Configurator Status>Maintenance Tab.
*Added Geofence Over speeding DOUT control in every geozone.
*Added Dout Control to every geozone.
*TPMS funcionality improvements
*Added Custom scenario event onExit feature.
*Added DOUT control in progress event reset.
*Added FMS Tell status IOs
*Garmin improvements
*LVCAN,ALLCAN, CAN-CONTROL reading improvements
*DSleep logic improvements
*COM modes stability improvements
*TCP,UDP packets handling improve
*Internal improvements for manufacture
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.65''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* UDP data sending improvements
* Battery charge mode parameter added
* GPS FIX time after sleep improved
* Wake up from sleep modes improved
* FrontPanel DDD files sending stability improvements
* K-Line midnight record saving logic changed
* ManualCAN improvements
* Tachograph data reading improvements
* FMC640, FMM640 support added
* Movement source parameter added
* IO elements data sending mode added
* GALILEO and BEIDOU selection for GNSS mode added
* Device and FOTAWEB communication stability improvements
* Carrier freezer new parameters added
* LVCAN, ALLCAN communication improved
* CAN-CONTROL with DTC reading added
* LLS fuel sensor reading stability improved
* Immobilizer improvements
* iButton read notification improvements
* Accelerometer autocalibration logic improved
* Continental TPMS improvements
* New type of zone for Manual geofence added
|-w

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.50''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.06.19
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DTCO VDO 4.0 tachograph support added
* Tachograph data sending improvements
* Records saving to SD card improvements
* Ping mode improvements
* GPS sleep mode improvements
* DOUT control improvements
* Configuration stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.45''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.04.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Carrier freezer support added
* Tachograph data sending improvements
* LVCAN setting program nr. via configurator added
* Odometer value improvements
* Accelerometer improvements added
* Additional FMS parameters added
* CAN CONTROL functionality added
* FOTA Web functionality improvements
* DOUT control improvements
* SMS/GPRS commands improvements
* iButton functionality improvements
* FrontPanel DDD files reading support added
* GPRS stability improvements
* NTP improvements
* Deep sleep consumption improvements
* Alternative DDD card download added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.21''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* K-Line improvements
* Sleep mode improvements
* Data sending improvements
* Custom Scenarios functionality added
* Additional MCAN parameters added
* Static Navigation deactivation source added
* New function for iButton notifications scenario added
* K-Line record merged with periodic record
* Configurator changes. FMS I/O parameter "Distance" moved to Tachograph Data tab
* Tachograph communication improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.14''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.04
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FMS IO AdBlue parameter added
* LVCAN stability improvements
* Manual CAN2 list implemented
* GPRS Limits added
* DOUT control via call functionality added
* Autogeofence deactivate by Engine RPM added
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.08'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.12.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FOTA Web stability improvements
* Data sending improvements
* Tacho download improvements
* Dual server functionality improvements
* IO elements configuration improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.04'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.11.27
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* MobilEye support added
* 100 geozones support added
* MCAN2 support added
* DOUT control improvements
* Battery charge improvements
* Records saving and sending improvements
* SMS commands improvements
* Immobilizer scenario improvements
* Crach detection improvements
* Status window implemented
* Tachocheck SMS command improvements
* Dual server functionality improvements
* Overspeeding scenario improvements
* Device stability improvements
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.01.05'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.08.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CAN adapter (LV-CAN200/ALL-CAN300) improvements
* ADC (Analog to Digital Converter) accuracy improvement
* J1708 CAN Fuel Level/Consumption parameters added
* Quectell Hardware support added
* Zbit flash added
* USB connection improvements
* "On Delta Change" operand (event generating) added.
* Codec 12 parsing improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.00.13'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.05.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* SMS sending for panic records added to code.
* SMS events improvements.
* Tachograph auto connect improved.
* Fota Web support added
* Deep Sleep Improvements
* USB improvements
|}
[[Category:FMB640]]

Template:FMC640 & FMM640 firmware errata

2020-10-27T06:35:13Z

Renat Galiachmetov: /* Firmware versions */

FMM640 Product Change Notifications

2020-10-27T06:32:08Z

Renat Galiachmetov: /* 2020.10.12: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}


[[Category:FMM640]]

FMC640 Product Change Notifications

2020-10-27T06:31:36Z

Renat Galiachmetov: /* 2020.10.12: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}


[[Category: FMC640]]

Template:FMC640 & FMM640 firmware errata

2020-10-22T05:56:28Z

Renat Galiachmetov: /* Firmware versions */

FMB640 firmware errata

2020-10-22T05:55:46Z

Renat Galiachmetov: /* Firmware versions */

__TOC__
===Introduction===
We are always improving our devices performance, stability and reliability. That’s why Teltonika is one of the leading GNSS trackers manufacturers in the world. 
This document describes '''FMB640 ''' devices firmware improvements, changes, new features implementations as well as current firmware release version.

===Firmware versioning===
*Structure
FM.VER.[XX].[YY].[ZZ]
*Syntax description
**<code>XX</code> – client number. Value range: 00 – Teltonika, 02..99 – Specific clients
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
**<code>ZZ</code> – minor changes like small fixes, improvements and new minor features addition.

===Firmware versions===
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''01.00.03''' (Current firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.10.12
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Tachograph FrontPanel improvements
* Additional tachograph parameters added
* Sleep modes improvements
* Battery charging/discharging improved
* Tracking On demand added
* LVCAN DTC codes reading improvements
* 1Wire TSH202 multiple sensors support added
* Periodical TSM232 SBD records saving improvements
* TCP buffering to SD card added
* GPRS Remote log improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.79'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.08.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |

*Tachograph driver data handling improvements
*Tacho download improvements
*Record send stability improved
*AutoCAN, ManualCAN improvements
*Tachograph data reading improvements
*TSM232 stability improvements.
*Added TSM232 check feature in Configurator Status>Maintenance Tab.
*Added Geofence Over speeding DOUT control in every geozone.
*Added Dout Control to every geozone.
*TPMS funcionality improvements
*Added Custom scenario event onExit feature.
*Added DOUT control in progress event reset.
*Added FMS Tell status IOs
*Garmin improvements
*LVCAN,ALLCAN, CAN-CONTROL reading improvements
*DSleep logic improvements
*COM modes stability improvements
*TCP,UDP packets handling improve
*Internal improvements for manufacture
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.65''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2020.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* UDP data sending improvements
* Battery charge mode parameter added
* GPS FIX time after sleep improved
* Wake up from sleep modes improved
* FrontPanel DDD files sending stability improvements
* K-Line midnight record saving logic changed
* ManualCAN improvements
* Tachograph data reading improvements
* FMC640, FMM640 support added
* Movement source parameter added
* IO elements data sending mode added
* GALILEO and BEIDOU selection for GNSS mode added
* Device and FOTAWEB communication stability improvements
* Carrier freezer new parameters added
* LVCAN, ALLCAN communication improved
* CAN-CONTROL with DTC reading added
* LLS fuel sensor reading stability improved
* Immobilizer improvements
* iButton read notification improvements
* Accelerometer autocalibration logic improved
* Continental TPMS improvements
* New type of zone for Manual geofence added
|-w

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.50''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.06.19
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DTCO VDO 4.0 tachograph support added
* Tachograph data sending improvements
* Records saving to SD card improvements
* Ping mode improvements
* GPS sleep mode improvements
* DOUT control improvements
* Configuration stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.45''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.04.25
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Carrier freezer support added
* Tachograph data sending improvements
* LVCAN setting program nr. via configurator added
* Odometer value improvements
* Accelerometer improvements added
* Additional FMS parameters added
* CAN CONTROL functionality added
* FOTA Web functionality improvements
* DOUT control improvements
* SMS/GPRS commands improvements
* iButton functionality improvements
* FrontPanel DDD files reading support added
* GPRS stability improvements
* NTP improvements
* Deep sleep consumption improvements
* Alternative DDD card download added
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.21''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* K-Line improvements
* Sleep mode improvements
* Data sending improvements
* Custom Scenarios functionality added
* Additional MCAN parameters added
* Static Navigation deactivation source added
* New function for iButton notifications scenario added
* K-Line record merged with periodic record
* Configurator changes. FMS I/O parameter "Distance" moved to Tachograph Data tab
* Tachograph communication improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.14''' 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2019.01.04
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FMS IO AdBlue parameter added
* LVCAN stability improvements
* Manual CAN2 list implemented
* GPRS Limits added
* DOUT control via call functionality added
* Autogeofence deactivate by Engine RPM added
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.08'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.12.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* FOTA Web stability improvements
* Data sending improvements
* Tacho download improvements
* Dual server functionality improvements
* IO elements configuration improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.03.04'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.11.27
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* MobilEye support added
* 100 geozones support added
* MCAN2 support added
* DOUT control improvements
* Battery charge improvements
* Records saving and sending improvements
* SMS commands improvements
* Immobilizer scenario improvements
* Crach detection improvements
* Status window implemented
* Tachocheck SMS command improvements
* Dual server functionality improvements
* Overspeeding scenario improvements
* Device stability improvements
* Tacho download improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.01.05'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.08.06
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* CAN adapter (LV-CAN200/ALL-CAN300) improvements
* ADC (Analog to Digital Converter) accuracy improvement
* J1708 CAN Fuel Level/Consumption parameters added
* Quectell Hardware support added
* Zbit flash added
* USB connection improvements
* "On Delta Change" operand (event generating) added.
* Codec 12 parsing improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | '''00.00.13'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 2018.05.10
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* SMS sending for panic records added to code.
* SMS events improvements.
* Tachograph auto connect improved.
* Fota Web support added
* Deep Sleep Improvements
* USB improvements
|}
[[Category:FMB640]]

FMB640 Product Change Notifications

2020-10-22T05:54:23Z

Renat Galiachmetov: /* 2020.10.12: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.12: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 12th, 2020. New production firmware version will be '''01.00.03'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.03
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 12th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMC640 Product Change Notifications

2020-10-22T05:51:56Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.12: Base firmware update==

We would like to inform you about base firmware update for FMC640 starting from October 12th, 2020. New production firmware version will be '''01.00.03'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMC640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMC640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMC640 01.00.03
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMC640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 12th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category: FMC640]]

FMM640 Product Change Notifications

2020-10-22T05:50:35Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.12: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 12th, 2020. New production firmware version will be '''01.00.03'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.03
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 12th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMM640 Product Change Notifications

2020-10-22T05:50:20Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 12th, 2020. New production firmware version will be '''01.00.03'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.03
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 12th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMB640 Product Change Notifications

2020-10-22T05:33:32Z

Renat Galiachmetov: /* 2019.07.22: new no brand Eco friendly boxes */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMB640 Product Change Notifications

2020-10-22T05:32:18Z

Renat Galiachmetov: /* 2019.10.18: New FMB640 case design / Top Marking Changes */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMM640 Product Change Notifications

2020-10-21T13:56:56Z

Renat Galiachmetov: /* 2020.10.14: Top Marking Changes */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMM640 Product Change Notifications

2020-10-21T13:56:36Z

Renat Galiachmetov: /* 2020.10.14: Top Marking Changes */

{{Template:Pcn_intro_FM
| product_name = FMM640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMM640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMM640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMM640 E-Mark]]) 
Added CE approval marking. (More information: [[FMM640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMM640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMM640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMM640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMM640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMM640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMM640
| style="text-align: left; background: white;" |FMM640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category:FMM640]]

FMC640 Product Change Notifications

2020-10-21T13:54:30Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMC640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMC640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMC640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMC640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMC640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}
{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

[[Category: FMC640]]

FMB640 Product Change Notifications

2020-10-21T13:53:19Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

FMB640 Product Change Notifications

2020-10-21T13:51:18Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMB640 Product Change Notifications

2020-10-21T13:50:48Z

Renat Galiachmetov: /* 2020.10.11: Base firmware update */

{{Template:Pcn_intro_FM
| product_name = FMB640
}}
==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMB640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.79
| style="text-align: left; background: white;" |New version: FMB640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2020.08.10: Base firmware update==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMB640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMB640 00.03.65
| style="text-align: left; background: white;" |New version: FMB640 00.03.79
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMB640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 August 10th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

==2019.10.18: New FMB640 case design / Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |External/visual
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |New case design. 
Device marking changed from tampography to laser printing. Information provided on module will remain the same.

|-
| style="text-align: left; background: white;" |Old version: [[File:FMB640 00 demo.png|center|400px]] Dimensions: 104.5 (L) x 70.9 (W) x 31.5 (H) mm
| style="text-align: left; background: white;" |New version: [[File:FMB640_New_Case_Laser.png|center|400px]] Dimensions: 104.5 (L) x 71.6 (W) x 27.3 (H) mm
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |New case design as other FMB series devices to fit corporate design and make it more ergonomic, smaller in dimensions.

Tampography to laser printing changed, to improve manufacturing speed, efficiency and reliability.

|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 First part of January
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}
You can already order sample with new case and laser printing by order code: FMB6403BFE01. (Max quantity of samples per order 2pcs )
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20191018 EN.pdf|click here]].

==2019.07.22: new no brand Eco friendly boxes==

Effective from 1Q of year 2020, FMB640 trackers with no brand packaging will be shipped with a '''new no brand eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old single packaging version: [[File:Medium-white1-cut.png|left|365px]] Dimensions: 177 (W) x 145 (D) x 64 (H)
| style="text-align: left; background: white;" |New single packaging version: [[File:Medium-eco-cut.png|center|400px]] Dimensions: 173 (W) x 148 (D) x 71 (H)
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new packaging will be released in manufacturing from 1Q of year 2020 with 2 months of transition period. Over this period devices with white packaging can be delivered as well as devices with the new eco boxes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640, FM6300.
| style="text-align: left; background: white;" |FMB640******, FM6300******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to the new look of boxes we strongly recommend to update your marketing materials. Because of the new color of the packaging box, if necessary, update your branding materials (stickers, logo layouts).
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2019.06.14: Device module information display changes==

We would like to inform you, that information display on device module TM2500 will be updated in factory from july 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Information display on TM2500 module will change from sticker to laser print. Information provided on module will remain the same.
|-
| style="text-align: left; background: white;" |Old Version: [[File: TM2500_sticker_v1.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File: TM2500_laser_v1.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |Laser printing will increase reliability, speed, and will reduce paper waste.
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new module marking will be released in manufacturing from july with 2 months of transition period. Over this period devices with sticker can be delivered as well as devices with laser print.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 448px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 221px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB001, FMB010, FMB100, FMB110, FMB120, FMB122, FMB125, FMB202, FMB204, FMB900, FMB920, FMB964, FMT100, FMB640, FMB130, MTB100, TMT250, GH5200.
| style="text-align: left; background: white;" |FMB001******, FMB010******, FMB100******, FMB110******, FMB120******, FMB122******, FMB125******, FMB202******, FMB204******, FMB900******, FMB920******, FMB964******, FMT100******, FMB640******, TMT250******, FMB130******, MTB100******, GH5200******.
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |The change will not affect clients. All the module characteristics will remain unchanged. The only sticker on module will be changed to laser print. The displayed information will remain the same.

|-
| style="text-align: left; background: white;" |Suggested implementation plan.
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in the customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN TM2500 20190614 EN.pdf|click here]].

==2019.04.10: IMEI/SN display on device Changes==

We would like to inform you, that IMEI/SN info display on FMB640 device will be updated in factory from june 2019.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="3" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |IMEI/SN info on device display change from barcode to QR
|-
| style="text-align: left; background: white;" |Old Version: [[File:IMEI_SN_Barcode_10x25mm.png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:IMEI_SN_QR_10x25mm.png|left|400px]]
|-
| colspan="2" style="text-align: left; background: white;" |This change will not affect device packing and logistic lists. It will remain as barcode. [[File:Packing_and_list.png|left|800px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |QR format will increase reliability and minimize error rate, because of the error correction feature and improved reading in low contrast.
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Devices with new QR Code format will be released in manufacturing from June with 2 months of transition period. Over this period devices with barcode can be delivered as well as devices with QR code.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device information display we strongly recommend to check, and prepare your tools to read QR codes.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190410 EN.pdf|click here]]

==2019.03.04: Top Tampography Changes==

We would like to inform you, that tampography of FMB640 device was updated in factory on the 4th of March.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top tampography design changed
|-
| style="text-align: left; background: white;" |Old Version: [[File:FMB640 black old .png|left|400px]]
| style="text-align: left; background: white;" |New Version: [[File:FMB 640 new.png|left|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |1. Updated Teltonika address to Saltoniskiu st. 9B-1 2. Added WEEE label. (WEEE - Waste from Electrical and Electronic Equipment)
|-
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Updated tampography will be used from the time when the stock will be sold all leftovers.
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190205 EN.pdf|click here]].

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190124 EN.pdf|click here]].

==2019.01.18: new eco friendly box==

Effective January 2019, week 4, FMB640 trackers will be packed with a '''new eco friendly box'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Packaging
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Improved and more environmentally friendly packaging box
|-
| style="text-align: left; background: white;" |Old version: [[File:Device packaging box tilted.png|left|300px]]
| style="text-align: left; background: white;" |New version: [[File:Eco friendly packaging box tilted.png|left|300px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |The new box is better for the environment
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |January 2019, week 4
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMB640
| style="text-align: left; background: white;" |FMB640*******
| style="text-align: left; background: white;" |No changes
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |No risk factors encountered with this change
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |Due to changes in device appearance we strongly recommend to contact your customs agent with our change log information, to avoid any unexpected delays in customs clearance process.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

To download the pdf version of this notification, [[Media:PCN FMB640 20190118 EN.pdf|click here]].
[[Category:FMB640]]

FMC640 Product Change Notifications

2020-10-21T13:47:31Z

Renat Galiachmetov:

{{Template:Pcn_intro_FM
| product_name = FMC640
}}

==2020.10.14: Top Marking Changes==

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |External/visual
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Top label design changed

|-
| style="text-align: left; background: white;" |Old version: [[File:FMC640_00.png|center|400px]]
| style="text-align: left; background: white;" |New version: [[File:FMC640_4000x4000_1.png|center|400px]]
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |
Added E-Mark approval marking. (More information: [[FMC640 E-Mark]]) 
Added CE approval marking. (More information: [[FMC640 CE/RED]])
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |Planned date: 2020 October 14th
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640******
| style="text-align: left; background: white;" |No changes
|-
|}
{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Risk assessment for devices management required
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |No implementation plan needed
|-
|}

{| class="wikitable"
|+
! colspan="3" style="width: 1141px; text-align: left; background: white;" |Acknowledgement of PCN receipt
|-
| colspan="3" style="text-align: left; background: white;" |If no feedback is received within two weeks after the issue date of this notification - Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above
|-
|}

==2020.10.11: Base firmware update==

We would like to inform you about base firmware update for FMC640 starting from October 11th, 2020. New production firmware version will be '''01.00.02'''.

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change description
|-
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |Firmware update
|-
| rowspan="2" style="width: 221px; text-align: left; background: white;" |Detailed description
| colspan="2" style="width: 908px; text-align: left; background: white;" |Key improvements from last production firmware are listed in errata: https://wiki.teltonika-gps.com/view/FMC640_firmware_errata
|-
| style="text-align: left; background: white;" |Old version: FMC640 00.03.74.T112
| style="text-align: left; background: white;" |New version: FMC640 01.00.02
|-
| style="text-align: left; background: white;" |Change reasons
| colspan="2" style="text-align: left; background: white;" |FMC640 base firmware version update
|-
| style="text-align: left; background: white;" |Product release date
| colspan="2" style="text-align: left; background: white;" |2020 October 11th.
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Affected products
|-
| style="width: 221px; text-align: left; background: white;" |Model
| style="width: 448px; text-align: left; background: white;" |Affected order codes
| style="width: 448px; text-align: left; background: white;" |Order code changes
|-
| style="text-align: left; background: white;" |FMC640
| style="text-align: left; background: white;" |FMC640*******order codes with base Firmware
| style="text-align: left; background: white;" |Update firmware
|-
|}

{| class="wikitable"
|+
! colspan="3" style="text-align: left; background: white;" |Change impact
|-
| style="width: 221px; text-align: left; background: white;" |Risk assessment
| colspan="2" style="width: 908px; text-align: left; background: white;" |Client's special firmware versions or order codes with special firmware will not be updated to latest base firmware automatically
|-
| style="text-align: left; background: white;" |Suggested implementation plan
| colspan="2" style="text-align: left; background: white;" |If you are using special firmware version and would like an upgrade to new features of latest base firmware, please contact your Teltonika sales manager
|-
|}

[[Category: FMC640]]