Wiki Knowledge Base | Teltonika GPS

Changes

Template:FMB630 Manual CAN (view source)

Revision as of 12:31, 31 October 2019

5,177 bytes added ,  12:31, 31 October 2019
m
Protected "Template:FMB630 Manual CAN" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
Line 29: Line 29:  
• Tachograph data *<br />
 
• Tachograph data *<br />
   −
''Availability of parameter depends on vehicle’s model and configuration of FMS interface of the truck.''
+
''Availability of parameter depends on vehicle’s model and configuration of FMS interface of the truck.''
 +
''J1708 is additional FMS protocol used by some vehicle manufacturers. If your vehicle supports J1939 and J1708 both protocols then you must disable J1708 in configuration to receive fuel data. ''
   −
''J1708 is additional FMS protocol used by some vehicle manufacturers. If your vehicle supports J1939 and J1708 both protocols then you must disable J1708 in configuration to receive fuel data. ''
     −
 
+
==General description==
−
16.1General 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;
 
* 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;
Line 41: Line 40:  
* Using mask, filters required bytes;
 
* Using mask, filters required bytes;
 
* Different CAN configurations.
 
* Different CAN configurations.
−
Configuration
  −
Manual CAN data can be configured using “Manual CAN” in CAN tab, Figure 88 below ( CAN configuration window).
      +
==Configuration==
 +
Manual CAN data can be configured using “Manual CAN” in CAN tab.
 +
 +
{{{image1|[[Image:FMB630_manual_CAN1.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 (Figure 89) 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]]}}}
      −
CAN message ID types
+
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 (Figure 90). 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.
     −
CAN message filter configuration
+
{{{image3|[[Image:FMB630_manual_CAN2.png|500px|none]]}}}
   −
16.3Example
+
Example
 
A sample CAN message has the following structure: X18FEE9018FFFFFFFF23840300, where essential parts are ‘FEE9’ – identifier and ‘FFFFFFFF23840300’ – data bytes.
 
A sample CAN message has the following structure: X18FEE9018FFFFFFFF23840300, where essential parts are ‘FEE9’ – identifier and ‘FFFFFFFF23840300’ – 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:
Line 63: 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 FMB630 module while integrating it.
+
takes no responsibility for information accuracy or damage that may be done to the vehicle or {{{model|FMB630}}} 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 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|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.
−
CAN wires can be found on X5 connector located in the fuse box (Figure 91):
+
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)
 
Pin 2: CAN High signal (blue wire)
 
Pin 2: CAN High signal (blue wire)
   −
X5 plug on Mercedes Benz
+
{{{image4|[[Image:FMB630_manual_CAN4.png|500px|none]]}}}
   −
In the example FMB630 will filter all CAN messages with identifier FFFEE9FF (fuel consumption) (Figure 92).
+
In the example {{{model|FMB630}}} will filter all CAN messages with identifier FFFEE9FF (fuel consumption).
    +
{{{image5|[[Image:FMB630_manual_CAN5.png|600px|none]]}}}
    
CAN parameter configuration example
 
CAN parameter configuration example
Line 83: Line 86:  
Data parsing is preceded by selecting correct message from all available on CAN bus. FMS standard interface description indicates that fuel consumption is parameter with ID FEE9:
 
Data parsing is preceded by selecting correct message from all available on CAN bus. FMS standard interface description indicates that fuel consumption is parameter with ID FEE9:
   −
FMS standard – fuel consumption
+
{| class="wikitable"
−
00FEE9 PGN Hex
+
|+
−
65,257 PGN
+
! style="background: black; color: white;" colspan=8 rowspan=1 |'''00FEE9'''
−
1000 ms Rep. Rate
+
! style="width: 90px; background: black; color: white;" rowspan=1 |'''PGN HEX'''
−
Data Byte 1 Data Byte 2 Data Byte 3 Data Byte 4 Data Byte 5 Data Byte 6 Data Byte 7 Data Byte 8 Byte No.
+
|-
−
Not used for FMS-Standard Not used for FMS-Standard Not used for FMS-Standard Not used for FMS-Standard Total fuel used
+
 
−
0,5 L/Bit gain
+
! style="background: black; color: white;" colspan=8 rowspan=1 |'''65,257'''
−
0 L offset
+
! style="width: 90px; background: black; color: white;" rowspan=1 |'''PGN'''
−
5.2.5.66
+
|-
−
SPN 250 Total fuel used
+
 
−
0,5 L/Bit gain
+
! style="width: 110px; background: black; color: white;" colspan=8 |'''1000 ms'''
−
0 L offset
+
! style="width: 90px; background: black; color: white;" rowspan=1 |'''Rep. Rate'''
−
5.2.5.66
+
|-
−
SPN 250 Total fuel used
+
 
−
0,5 L/Bit gain
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 1
−
0 L offset
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 2
−
5.2.5.66
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 3
−
SPN 250 Total fuel used
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 4
−
0,5 L/Bit gain
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 5
−
0 L offset
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 6
−
5.2.5.66
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 7
−
SPN 250 Name
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Data Byte 8
−
Values
+
! style="width: 90px; background: black; color: white;" rowspan=1 |Byte No.
−
Values
+
|-
−
Values
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Not used for<br /> FMS-<br />Standard
−
SAE ref
+
! style="width: 110px; background: black; color: white;" rowspan=1 |Not used for<br /> FMS-<br />Standard
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Not used for<br /> FMS-<br />Standard
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Not used for<br /> FMS-<br />Standard
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Total fuel used<br />
 +
0,5 L/Bit gain<br />
 +
0 L offset<br />
 +
5.2.5.66<br />
 +
SPN 250
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Total fuel used<br />
 +
0,5 L/Bit gain<br />
 +
0 L offset<br />
 +
5.2.5.66<br />
 +
SPN 250
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Total fuel used<br />
 +
0,5 L/Bit gain<br />
 +
0 L offset<br />
 +
5.2.5.66<br />
 +
SPN 250
 +
! style="width: 110px; background: black; color: white;" rowspan=1 |Total fuel used<br />
 +
0,5 L/Bit gain<br />
 +
0 L offset<br />
 +
5.2.5.66<br />
 +
SPN 250
 +
! style="width: 90px; background: black; color: white;" rowspan=1 |Name<br />
 +
Values<br />
 +
Values<br />
 +
Values<br />
 +
SAE ref<br />
 
SPN
 
SPN
 +
|}
 +
 +
 +
The example indicates how fuel consumption message is selected and how configuration impacts this selection.
   −
The example indicates how fuel consumption message is selected and how configuration impacts this selection (Figure 93).
+
{{{image6|[[Image:FMB630_manual_CAN6.png|450px|none]]}}}
   −
Example
+
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, FMB630 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
 +
|-
 +
|}
   −
Table 58 FMS standard – fuel consumption (5-8 bytes)
  −
Data Byte 5 Data Byte 6 Data Byte 7 Data Byte 8 Byte No.
  −
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 Bit no
  −
Total fuel used
  −
0,5 L/Bit gain
  −
0 L offset
  −
5.2.5.66
  −
SPN 250 Total fuel used
  −
0,5 L/Bit gain
  −
0 L offset
  −
5.2.5.66
  −
SPN 250 Total fuel used
  −
0,5 L/Bit gain
  −
0 L offset
  −
5.2.5.66
  −
SPN 250 Total fuel used
  −
0,5 L/Bit gain
  −
0 L offset
  −
5.2.5.66
  −
SPN 250 Name
  −
Values
  −
Values
  −
Values
  −
SAE ref
  −
SPN
        −
Example
+
{{{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.  
 
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.
 
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.
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/14611...47954"