FMB640 Manual CAN IO - Revision history

AndrejKondratjev: /* General description */ Removed information about USB, as it is outdated infomration about FM53

2023-05-16T11:25:10Z

General description: Removed information about USB, as it is outdated infomration about FM53

← Older revision		Revision as of 14:25, 16 May 2023
Line 37:		Line 37:

	==General description==		==General description==
	* CAN works if no USB cable is inserted and isn’t in deep sleep mode (applies only to FM53 devices);
	* Uses six different speeds: 50 kbps, 100 kbps, 125 kbps, 250 kbps, 500 kbps, 1000kbps;		* Uses six different speeds: 50 kbps, 100 kbps, 125 kbps, 250 kbps, 500 kbps, 1000kbps;
	* Auto Baud rate detection;		* Auto Baud rate detection;

AndrejKondratjev: /* General description */

2023-05-16T09:33:32Z

General description

← Older revision		Revision as of 12:33, 16 May 2023
Line 37:		Line 37:

	==General description==		==General description==
	* CAN works if no USB cable is inserted and isn’t in deep sleep mode;		* CAN works if no USB cable is inserted and isn’t in deep sleep mode (applies only to FM53 devices);
	* Uses six different speeds: 50 kbps, 100 kbps, 125 kbps, 250 kbps, 500 kbps, 1000kbps;		* Uses six different speeds: 50 kbps, 100 kbps, 125 kbps, 250 kbps, 500 kbps, 1000kbps;
	* Auto Baud rate detection;		* Auto Baud rate detection;

Sandra.Gasyte at 08:44, 31 August 2020

2020-08-31T08:44:17Z

← Older revision		Revision as of 11:44, 31 August 2020
Line 45:		Line 45:

	==Configuration==		==Configuration==
	{{{~~module~~\|FMB640}}} has 70 configurable Manual CAN elements~~. Manual CAN data can be configured using “Manual CAN” in the CAN tab~~.		[[{{{model\|FMB640}}}]] has 70 configurable Manual CAN elements.

	{{{image1\|[[Image:FMB640_Manual_CAN.png\|700px\|none]]}}}		{{{image1\|[[Image:FMB640_Manual_CAN.png\|700px\|none]]}}}
Line 59:		Line 59:
	'''Example:'''		'''Example:'''
	A sample CAN message has the following structure: <code>X18FEE9018FFFFFFFF23840300</code>, where essential parts are <code>FEE9</code> – identifier and <code>FFFFFFFF23840300</code> – data bytes.		A sample CAN message has the following structure: <code>X18FEE9018FFFFFFFF23840300</code>, where essential parts are <code>FEE9</code> – identifier and <code>FFFFFFFF23840300</code> – data bytes.


	CAN messages are configured like any other I/O parameters. They consist of 4 identifier bytes and 8 data bytes. Below you will find a sample configuration for fuel consumption parameter:		CAN messages are configured like any other I/O parameters. They consist of 4 identifier bytes and 8 data bytes. Below you will find a sample configuration for fuel consumption parameter:
	* ID type – is always 29 bits.		* '''ID type''' – is always 29 bits.
	Output data mask – defines which data bytes are sent to the server (sometimes not all data bytes are necessary).		* '''Output data mask''' – defines which data bytes are sent to the server (sometimes not all data bytes are necessary).
	* CAN ID – this is 4 byte identifier. Messages use 4 bytes, but the first and last bytes may differ in different vehicle models while the middle four bytes are the same for all vehicles. The first and last bytes may have any value. Because of this reason, it is recommended to write <code>FF</code> in the first byte and the same in the last byte.		* '''CAN ID''' – this is 4 byte identifier. Messages use 4 bytes, but the first and last bytes may differ in different vehicle models while the middle four bytes are the same for all vehicles. The first and last bytes may have any value. Because of this reason, it is recommended to write <code>FF</code> in the first byte and the same in the last byte.

	'''Note:''' This information is provided only as an example and Teltonika takes no responsibility for information accuracy or damage that may be done to the vehicle or {{{model\|FMB640}}} module while integrating it.


	~~'''~~Example~~:'''~~		==Example==
	All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect {{{model\|FMB640}}} module to the CAN bus. This can be done by connecting to a special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For the CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.		All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect [[{{{model\|FMB640}}}]] module to the CAN bus. This can be done by connecting to a special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For the CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.

	CAN wires can be found on the X5 connector located in the fuse box:		CAN wires can be found on the X5 connector located in the fuse box:
Line 77:		Line 75:
	{{{image4\|[[Image:FMB630_manual_CAN4.png\|500px\|none]]}}}		{{{image4\|[[Image:FMB630_manual_CAN4.png\|500px\|none]]}}}

	In the example {{{model\|FMB640}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).		In the example [[{{{model\|FMB640}}}]] will filter all CAN messages with identifier FFFEE9FF (fuel consumption).

	{{{image5\|[[Image:FMB640_Manual_CAN5.png\|600px\|none]]}}}		{{{image5\|[[Image:FMB640_Manual_CAN5.png\|600px\|none]]}}}

	'''Note:''' Averaging constant cannot be used with CAN data, because this information comes in digital format. So in order to prevent data loss, set Averaging constant parameter to 1.		'''Note:''' Averaging constant cannot be used with CAN data, because this information comes in digital format. So in order to prevent data loss, set Averaging constant parameter to 1.


	Most parameters have a certain resolution. <code>FEE9</code> parameter has 0.5L/bit gain, so the value that is sent to the server has to be multiplied by 0.5.		Most parameters have a certain resolution. <code>FEE9</code> parameter has 0.5L/bit gain, so the value that is sent to the server has to be multiplied by 0.5.
Line 143:		Line 140:
	SPN		SPN
	\|}		\|}

			'''Note:''' This information is provided only as an example and Teltonika takes no responsibility for information accuracy or damage that may be done to the vehicle or [[{{{model\|FMB640}}}]] module while integrating it.

	[[Category:FMB640 Configuration]]		[[Category:FMB640 Configuration]]

Sandra.Gasyte at 08:28, 31 August 2020

2020-08-31T08:28:20Z

Show changes

Kudalevas.da at 06:03, 21 October 2019

2019-10-21T06:03:39Z

← Older revision		Revision as of 09:03, 21 October 2019
Line 138:		Line 138:
	SPN		SPN
	\|}		\|}

			[[Category:FMB640 Configuration]]

Gediminas.suminas: Protected "FMB640 Manual CAN IO" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2019-07-10T06:58:17Z

Protected "FMB640 Manual CAN IO" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 09:58, 10 July 2019
(No difference)

Gediminas.suminas: /* Configuration */

2019-07-10T05:22:58Z

Configuration

← Older revision		Revision as of 08:22, 10 July 2019
Line 138:		Line 138:
	SPN		SPN
	\|}		\|}


	~~The example indicates how fuel consumption message is selected and how configuration impacts this selection.~~

	~~{{{image6\|[[Image:FMB630_manual_CAN6.png\|450px\|none]]}}}~~

	~~When certain message is filtered, {{{model\|FMB640}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard.~~

	~~{\| class="wikitable"~~
	\|+
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 5''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 6''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 7''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 8''~~
	~~! style="background: black; color: white;" rowspan=1 \|'''Byte No.'''~~
	\|-
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''Bit no'''~~
	\|-
	~~! style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=1 \|'''Name'''~~
	\|-
	~~! rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| Values~~
	\|-
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| Values~~
	\|-
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| SAE ref~~
	\|-
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| SPN~~
	\|-
	\|}


	~~{{{image7\|[[Image:FMB630_manual_CAN7.png\|400px\|none]]}}}~~

	~~Data bytes are filtered by selecting the checkboxes in Output data mask. Note, that configurator has them listed starting with MSB.~~
	After message is filtered it is attached to the data packet and sent to the server. Values are returned in HEX. 00 03 84 23(HEX) = 230435(DEC). Notice, that data resolution is 0.5L/bit gain – value has to be multiplied by 0.5, therefore vehicle used a total 115217,5 liters of fuel.

Gediminas.suminas at 05:22, 10 July 2019

2019-07-10T05:22:32Z

← Older revision		Revision as of 08:22, 10 July 2019
Line 52:		Line 52:

	Message ID value is entered in hex format. This parameter is used to configure hardware message filter. All messages contain 8 bytes of data, to select particular data/bytes “Output Data Mask” is used, it’s done by ticking required bytes, only selected bytes are sent to server.		Message ID value is entered in hex format. This parameter is used to configure hardware message filter. All messages contain 8 bytes of data, to select particular data/bytes “Output Data Mask” is used, it’s done by ticking required bytes, only selected bytes are sent to server.


	~~{{{image3\|[[Image:FMB630_manual_CAN2.png\|500px\|none]]}}}~~

	Example		Example
Line 77:		Line 74:
	In the example {{{model\|FMB640}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).		In the example {{{model\|FMB640}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).

	{{{image5\|[[Image:~~FMB630_manual_CAN5~~.png\|600px\|none]]}}}		{{{image5\|[[Image:FMB640_Manual_CAN5.png\|600px\|none]]}}}

	CAN parameter configuration example		CAN parameter configuration example

Gediminas.suminas: /* Configuration */

2019-07-10T05:20:37Z

Configuration

← Older revision		Revision as of 08:20, 10 July 2019
Line 42:		Line 42:

	==Configuration==		==Configuration==
	Manual CAN data can be configured using “Manual CAN” in CAN tab.		FMB640 has 70 configurable Manual CAN elements. Manual CAN data can be configured using “Manual CAN” in CAN tab.

	{{{image1\|[[Image:FMB640_Manual_CAN.png\|700px\|none]]}}}		{{{image1\|[[Image:FMB640_Manual_CAN.png\|700px\|none]]}}}

Gediminas.suminas: /* Configuration */

2019-07-10T05:19:19Z

Configuration

← Older revision		Revision as of 08:19, 10 July 2019
Line 44:		Line 44:
	Manual CAN data can be configured using “Manual CAN” in CAN tab.		Manual CAN data can be configured using “Manual CAN” in CAN tab.

	{{{image1\|[[Image:~~FMB630_manual_CAN1~~.png\|700px\|none]]}}}		{{{image1\|[[Image:FMB640_Manual_CAN.png\|700px\|none]]}}}

	CAN message ID type: Message ID type two types according to SAEJ1939 standard: Standard ID (value: 0 to 0x7FFh) and Extended ID (value: 0 to 0x1FFFFFFFh).		CAN message ID type: Message ID type two types according to SAEJ1939 standard: Standard ID (value: 0 to 0x7FFh) and Extended ID (value: 0 to 0x1FFFFFFFh).

	{{{image2\|[[Image:~~FMB630_manual_CAN3~~.png\|200px\|none]]}}}		{{{image2\|[[Image:FMB640_Manual_CAN1.png\|200px\|none]]}}}


Line 65:		Line 65:

	This information is provided only as an example and Teltonika		This information is provided only as an example and Teltonika
	takes no responsibility for information accuracy or damage that may be done to the vehicle or {{{model\|~~FMB630~~}}} module while integrating it.		takes no responsibility for information accuracy or damage that may be done to the vehicle or {{{model\|FMB640}}} module while integrating it.

	Example:		Example:
	All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect {{{model\|~~FMB630~~}}} module to CAN bus. This can be done by connecting to special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.		All Mercedes Benz Actros 2 models with Vehicle Identification Number (VIN) starting with WDB93 have a possibility to connect {{{model\|FMB640}}} module to CAN bus. This can be done by connecting to special PSM module (which may or may not be included in the truck) or ground module of the vehicle. For CAN signal to be available, parameter 520 must be enabled in “kommunikationsschnittstelle” in the vehicle with Mercedes Stardiagnose.
	CAN wires can be found on X5 connector located in the fuse box:		CAN wires can be found on X5 connector located in the fuse box:
	Pin 5: CAN Low signal (yellow wire)		Pin 5: CAN Low signal (yellow wire)
Line 75:		Line 75:
	{{{image4\|[[Image:FMB630_manual_CAN4.png\|500px\|none]]}}}		{{{image4\|[[Image:FMB630_manual_CAN4.png\|500px\|none]]}}}

	In the example {{{model\|~~FMB630~~}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).		In the example {{{model\|FMB640}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).

	{{{image5\|[[Image:FMB630_manual_CAN5.png\|600px\|none]]}}}		{{{image5\|[[Image:FMB630_manual_CAN5.png\|600px\|none]]}}}
Line 147:		Line 147:
	{{{image6\|[[Image:FMB630_manual_CAN6.png\|450px\|none]]}}}		{{{image6\|[[Image:FMB630_manual_CAN6.png\|450px\|none]]}}}

	When certain message is filtered, {{{model\|~~FMB630~~}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard.		When certain message is filtered, {{{model\|FMB640}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard.

	{\| class="wikitable"		{\| class="wikitable"

← Older revision		Revision as of 08:22, 10 July 2019
Line 138:		Line 138:
	SPN		SPN
	\|}		\|}


	~~The example indicates how fuel consumption message is selected and how configuration impacts this selection.~~

	~~{{{image6\|[[Image:FMB630_manual_CAN6.png\|450px\|none]]}}}~~

	~~When certain message is filtered, {{{model\|FMB640}}} checks which data bytes should be sent to server. Document indicates that 5-8 bytes are used in FMS standard.~~

	~~{\| class="wikitable"~~
	\|+
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 5''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 6''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 7''~~
	~~! style="background: black; color: white;" colspan=8 rowspan=1 \|''Data Byte 8''~~
	~~! style="background: black; color: white;" rowspan=1 \|'''Byte No.'''~~
	\|-
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''8'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''7'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''6'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''5'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''4'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''3'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''2'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''1'''~~
	~~! style=" background: black; color: white;" rowspan=1 \|'''Bit no'''~~
	\|-
	~~! style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=8 \|'''Total fuel used'''~~
	~~\| style=" background: black; color: white;" rowspan=1 colspan=1 \|'''Name'''~~
	\|-
	~~! rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| rowspan=1 colspan=8 \|0,5 L/Bit gain~~
	~~\| Values~~
	\|-
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| rowspan=1 colspan=8 \| 0 L offset~~
	~~\| Values~~
	\|-
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| rowspan=1 colspan=8 \| 5.2.5.66~~
	~~\| SAE ref~~
	\|-
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| rowspan=1 colspan=8 \|'''SPN 250'''~~
	~~\| SPN~~
	\|-
	\|}


	~~{{{image7\|[[Image:FMB630_manual_CAN7.png\|400px\|none]]}}}~~

	~~Data bytes are filtered by selecting the checkboxes in Output data mask. Note, that configurator has them listed starting with MSB.~~
	After message is filtered it is attached to the data packet and sent to the server. Values are returned in HEX. 00 03 84 23(HEX) = 230435(DEC). Notice, that data resolution is 0.5L/bit gain – value has to be multiplied by 0.5, therefore vehicle used a total 115217,5 liters of fuel.