Difference between revisions of "Template:FMx6 CAN adapters"

From Wiki Knowledge Base | Teltonika GPS
Line 564: Line 564:
 
Due to the growing number of supported cars, program numbers have exceeded "999". In order to maintain one number format, we are moving from 3-digit to 4-digit program numbers.<br/>In new LV-CAN200 firmware (from 2017-09-01) all program numbers that were up to 999 are changed to start from 1000. So that further program numbers would continue the counting with 4-digit numbers.<br/>However, all existing program numbers stay the same, but "1" is added to the front. If the device still understands the entered 3-digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - the device number will turn into "1247". In Bootloader only a 4-digit format is available, just add "1" to the front of the needed program number.
 
Due to the growing number of supported cars, program numbers have exceeded "999". In order to maintain one number format, we are moving from 3-digit to 4-digit program numbers.<br/>In new LV-CAN200 firmware (from 2017-09-01) all program numbers that were up to 999 are changed to start from 1000. So that further program numbers would continue the counting with 4-digit numbers.<br/>However, all existing program numbers stay the same, but "1" is added to the front. If the device still understands the entered 3-digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - the device number will turn into "1247". In Bootloader only a 4-digit format is available, just add "1" to the front of the needed program number.
 
-->
 
-->
 +
 +
==CAN Adapter State Flags==
 +
 +
CAN Adapters receive data about the states of various systems within the vehicle, and send them as flags to {{{model|FMx640}}}. {{{model|FMx640}}} device stores these flags in hexadecimal format, as one variable. '''Note!''' To retrieve all flags, Firmware version '''01.02.28.Rev.13''' for '''FMx640''' and '''03.00.16.Rev.01''' for '''FMx650''' or newer must be used. Below are the table of flags that are kept by [[LV-CAN200|LV-CAN200]], [[ALL-CAN300|ALL-CAN300]] and information how to retrieve them:<br />
 +
 +
===Security State Flags P4===
 +
{| class="nd-othertables_2" style="text-align:center; border: 2px solid;border-collapse: collapse; border-bottom: 2pt solid black;"
 +
|-
 +
! style="column-width: 30px;text-align:center;"| Byte
 +
! style="column-width: 30px;text-align:center;"|Bit
 +
! style="text-align:center;"|Value bitmasks
 +
! style="column-width: 75px;text-align:center;"|LVCAN
 +
! style="column-width: 75px;text-align:center;"|ALLCAN
 +
 +
|-
 +
| style="color:#f56b00;" | 0
 +
| style="color:#f56b00;" | 0
 +
| 0x00 – CAN1 connected, currently no data is received<br />0x01 – CAN1 connected, currently data is received<br />0x02 – CAN1 not connected, needs connection<br />0x03 – CAN1 not connected does not need connection
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#f56b00;" | 0
 +
| style="color:#f56b00;" | 2
 +
| 0x00 – CAN2 connected, currently no data is received<br />0x01 – CAN2 connected, currently data is received<br />0x02 – CAN2 not connected, needs connection<br />0x03 – CAN2 not connected does not need connection
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#f56b00;" | 0
 +
| style="color:#f56b00;" | 4
 +
| 0x00 – CAN3 connected, currently no data is received<br />0x01 – CAN3 connected, currently data is received<br />0x02 – CAN3 not connected, needs connection<br />0x03 – CAN3 not connected does not need connection
 +
|
 +
|
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 8
 +
| 0x01 – ignition on
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 9
 +
| 0x02 – key in ignition lock
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 10
 +
| 0x04 – Webasto
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 11
 +
| 0x08 – engine is working
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 12
 +
| 0x10 – standalone engine
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 13
 +
| 0x20 – ready to drive
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 14
 +
| 0x40 – engine is working on CNG
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#3531ff;" | 1
 +
| style="color:#3531ff;" | 15
 +
| 0x80 – work mode (0 – private, 1 – company)
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 16
 +
| 0x01 – operator is present
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 17
 +
| 0x02 – interlock active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 18
 +
| 0x04 – handbrake is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 19
 +
| 0x08 – footbrake is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 20
 +
| 0x10 – clutch is pushed
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 21
 +
| 0x20 – status of the hazard warning lights switch active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 22
 +
| 0x40 – front left door opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#009901;" | 2
 +
| style="color:#009901;" | 23
 +
| 0x80 – front right door opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 24
 +
| 0x01 – rear left door opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 25
 +
| 0x02 – rear right door opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 26
 +
| 0x04 – trunk door opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 27
 +
| 0x08 – engine cover opened
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 28
 +
| 0x10 – charging wire is plugged
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 29
 +
| 0x20 – battery charging on
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 30
 +
| 0x40 – electric engine is working
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#d13c00;" | 3
 +
| style="color:#d13c00;" | 31
 +
| 0x80 – car is closed with factory remote control
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 32
 +
| 0x01 – car is closed
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 33
 +
| 0x02 – factory installed alarm is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 34
 +
| 0x04 – emulated alarm is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 35
 +
| 0x08 – signal of closing with factory remote control was sent
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 36
 +
| 0x10 – signal of opening with factory remote control was sent
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 37
 +
| 0x20 – rearm signal was sent
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 38
 +
| 0x40 – trunk was opened with remote control
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#ff00db;" | 4
 +
| style="color:#ff00db;" | 39
 +
| 0x80 – CAN module is in SLEEP mode
 +
| ✔
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 40
 +
| 0x01 – signal of closing with factory remote control was sent 3 times
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 41
 +
| 0x02 – parking is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 42
 +
| 0x04 – reverse is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 43
 +
| 0x08 – neutral is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 44
 +
| 0x10 – drive is active
 +
|
 +
| ✔
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 45
 +
| 0x20 – engine lock active
 +
|
 +
|
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 46
 +
| 0x40 – request to lock the engine (activation after attempt to restart the engine)
 +
|
 +
|
 +
 +
|-
 +
| style="color:#340096;" | 5
 +
| style="color:#340096;" | 47
 +
| 0x80 – factory armed
 +
|
 +
|
 +
 +
|-
 +
| style="color:#fe0000;" | 6
 +
| style="color:#fe0000;" | 48
 +
| 0x01 - roof opened
 +
| ✔
 +
| ✔
 +
 +
|}
 +
<br>
  
  
 
[[Category:FMB641 Manual]]
 
[[Category:FMB641 Manual]]

Revision as of 11:43, 28 June 2024

Alert.png

FMB640 supports CAN adapters over RS232 connection. CAN adapter support is added from 02.02.11.Rev.00 firmware
Easy steps to install and configure following CAN adapters on FMB640 device:

Installing CAN adapter with FMB640 device

Installing LV-CAN200 / ALL-CAN300

You can watch LV-CAN200 / ALL-CAN300 installation video in our YouTube channel here or follow connection instructions below.

Tools needed for installation

  • LV-CAN200 or ALL-CAN300
  • Connection scheme (Please contact Teltonika Sales Representative and provide information about vehicle manufacturer, model and year.
  • FMB640 device
  • Pliers
  • Quick splice connectors (If vehicle CAN bus wires are very thin CAN adapter wires should be connected directly)
  • Plastic pry tool
  • Zip ties

Installation steps

  1. Be ready with a vehicle connection scheme that you have received from a Teltonika Sales Representative.
  2. Check the scheme for the current vehicle connection. Look for connectors matching PINs numbers and colors (maybe different) according to the connection scheme.
  3. Connect CAN adapter with FMB640:
    1. Connect CAN adapter's RS232 to RJ45 of FMB640.
  4. Connect CAN adapter CAN wires (CAN L, CAN H) as specified in connection scheme.

    Alert.png
    		Do not swap CAN L and CAN H lines.
    Not all CAN adapter wires may be used in the vehicle.

  5. Connect CAN adapter positive and ground wires to the vehicle power supply lines or near FMB640 power wires.

    Alert.png
    		Do not swap power supply lines.
    Make sure that voltage does not exceed 30V.

  6. Switch vehicle ignition to ACC position. CAN adapter LED diode on the back should start blinking.
  7. Configure CAN adapter to read CAN bus data or control vehicle by setting its program number - CAN Adapter configuration


LV-CAN200 connection example. This is not a connection diagram for your vehicle. Every vehicle has a specific scheme.

Installing LV-CAN200 / ALL-CAN300 + ECAN02

Tools needed for installation

  • LV-CAN200 / ALL-CAN300
  • Connection scheme (Please contact Teltonika Sales Representative and provide information about vehicle manufacturer, model and year.
  • ECAN02 (Used for contactless connection. If two CAN lines need to be connected, ECAN02 must be used.)
  • FMB640 device
  • Pliers
  • Quick splice connectors (If vehicle CAN bus wires are very thin CAN adapter wires should be connected directly)
  • Plastic pry tool
  • Zip ties

Installation steps

  1. Follow the same 1, 2, 3 installation steps as with LV-CAN200 installation.
  2. Connect the appropriate CAN bus pair of wires between the CAN adapter and ECAN02:
    If CAN1 line need to be connected as specified in the connection scheme:
    1. Connect CAN adapter CAN1 L to CAN L of ECAN02.
    2. Connect CAN adapter CAN1 H to CAN H of ECAN02.
    If CAN2 line need to be connected as specified in the connection scheme:
    1. Connect CAN adapter CAN2 L to CAN L of ECAN02.
    2. Connect CAN adapter CAN2 H to CAN H of ECAN02.

      Alert.png
      		Do not swap CAN L and CAN H lines.
      Not all CAN adapter wires may be used in the vehicle.

  3. Fasten ECAN02 on vehicle CAN bus wires according to the connection scheme. Make sure CAN H and CAN L of vehicle corresponds to CAN H, CAN L markings on ECAN02 PCB.

  4. Connect CAN adapter positive and ground wires to the vehicle power supply lines or near FMB640 power wires.

    Alert.png
    		Do not swap power supply lines.
    Make sure that voltage does not exceed 30V.

  5. Configure CAN adapter to read CAN bus data by setting its program number - CAN Adapter configuration


CAN Adapter Configuration

CAN Adapter program number selection

CAN Adapter must be set to the program number which depends on the vehicle model. Needed program number is always written on CAN Adapter mounting scheme. In order to be able to enter the program number in the adapter Software date of the CAN adapter must be newer than the connection scheme date. CAN adapter Software date can be checked:

The number of digits required to enter the correct Program No. may vary depending on the Software and manufacture date of your CAN Adapter:

Entering via SMS command

Required conditions:

  • CAN adapter properly connected to FMB640 device

CAN adapter program number can be set remotely, using an SMS command. Send following SMS command to FMB640 device:

  • If you have set SMS login and password: login pass lvcansetprog X
  • If SMS login and password are not set leave two spaces before the command:   lvcansetprog X

Command example:   lvcansetprog 11434
SMS response: LVCAN ProgNum: 11434

If during SMS command FMB640 was in the following Sleep mode:

Entering via Teltonika Configurator

Required conditions:

  • CAN adapter properly connected to FMB640 device

CAN adapter program number can be set via Teltonika Configurator → LVCAN → Program Number. When the program number is entered press Save to device.png Save to device button that saves the entered program number into FMB640.

Fmx640.gif

Entering manually

Required conditions:

  • CAN adapter properly connected to FMB640 device
  • Vehicle ignition must be ON

Depending on the used CAN Adapter, the length of the setup sequence will vary.

Steps to set program number:

LV-CAN200 back
For
ALL-CAN300
LV-CAN200
3 digit 		For
ALL-CAN300
LV-CAN200
4 digit 		For
ALL-CAN300
LV-CAN200
5 digit 		1. Hold SWITCH down until LED stars blink.
2. Release the SWITCH.
3. Then the LED starts blinking and counting the first digit of the program number (one blink means digit 1, two blinks mean digit 2, etc). To stop the counter, push SWITCH.
4. Release the SWITCH, then the LED starts blinking and counting the second digit of the program number. To stop the counter, push SWITCH.
5. Release the SWITCH, then the LED starts blinking and counting the third digit on the program number. To stop the counter, push SWITCH.
6. Release the SWITCH, then the LED starts blinking and counting the fourth digit on the program number. To stop the counter, push SWITCH.
7. Release the SWITCH, then the LED starts blinking and counting the fifth digit on the program number. To stop the counter, push SWITCH.
All Devices 8. Release SWITCH, if programming is successful LED will blink 10 times.
Send data with 0 if the ignition is off

Depending on CAN Adapter I/O parameters and ignition status, FMB640 can send locked (last known) CAN Adapter I/O and active (real-time) parameter values or reset values to 0. When the ignition is off, CAN Adapter I/O parameters values sent to the server are:

CAN Adapter I/O element Status
Vehicle Speed reset
Accelerator pedal position reset
Total fuel used lock
Fuel level (liters) lock
Engine RPM reset
Total mileage lock
Fuel level (%) lock
Program number lock
Module ID lock
Engine Work Time lock
Engine Work Time (counted) lock
Total Mileage (counted) lock
Fuel Consumed (counted) lock
Fuel Rate reset
Program number lock
AdBlue Level (%) lock
AdBlue Level (liters) lock
Engine Load reset
Engine Temperature active
Axle 1 Load lock
Axle 2 Load lock
Axle 3 Load lock
Axle 4 Load lock
Axle 5 Load lock
Control State Flags active
Agricultural Machinery Flags active
Harvesting Time lock
Area of Harvest reset
Mowing Efficiency active
Grain Mown Volume active
Grain Moisture active
Harvesting Drum RPM reset
Gap Under Harvesting Drum active
Security State Flags active
Tachograph Total Vehicle Distance lock
Trip Distance reset
Tachograph Vehicle Speed reset
Tachograph Driver Card Presence active
Driver1 States active
Driver2 States active
Driver1 Continuous Driving Time active
Driver2 Continuous Driving Time active
Driver1 Cumulative Break Time active
Driver2 Cumulative Break Time active
Driver1 Selected Activity Duration active
Driver2 Selected Activity Duration active
Driver1 Cumulative Driving Time active
Driver2 Cumulative Driving Time active


SMS Configuration

All CAN Adapter IO elements can be configured remotely via SMS commands.

SMS/GPRS Commands

CAN Adapters have several dedicated SMS/GPRS commands.
SMS command structure: 

<SMS login><space><SMS password><space><command><space><value>

SMS command lvcangetinfo example:

  • If you have set SMS login and password: login pass lvcangetinfo
  • If SMS login and password are not set leave two spaces before the command: aalvcangetinfo


GPRS commands require Codec 12 protocol.

For more SMS commands please see SMS/GPRS command list

COMMAND DESCRIPTION RESPONSE
lvcansetprog # Set program number to CAN Adapter that is connected to FMB640.
# - three digit number that identity vehicle. 		Yes
lvcansimpletacho # Add or remove simpletacho start byte.
# - 0 or 1 (0 – don’t add start byte, 1 – add start byte). 		No
lvcangetprog Get program number from CAN Adapter that is connected to FMB640. Yes
lvcangetinfo Get information about connected CAN Adapter Yes
lvcanclear # Clear Total Mileage (counted), Engine Work Time (counted), Fuel Consumed (counted) parameters values.
# - parameter (0 – Engine work time (counted), 1 – Fuel Consumed (counted), 2 – Vehicle Mileage (counted)). 		Yes

CAN Adapter State Flags

CAN Adapters receive data about the states of various systems within the vehicle, and send them as flags to FMx640. FMx640 device stores these flags in hexadecimal format, as one variable. Note! To retrieve all flags, Firmware version 01.02.28.Rev.13 for FMx640 and 03.00.16.Rev.01 for FMx650 or newer must be used. Below are the table of flags that are kept by LV-CAN200, ALL-CAN300 and information how to retrieve them:

Security State Flags P4

Byte Bit Value bitmasks LVCAN ALLCAN
0 0 0x00 – CAN1 connected, currently no data is received
0x01 – CAN1 connected, currently data is received
0x02 – CAN1 not connected, needs connection
0x03 – CAN1 not connected does not need connection 		✔ ✔
0 2 0x00 – CAN2 connected, currently no data is received
0x01 – CAN2 connected, currently data is received
0x02 – CAN2 not connected, needs connection
0x03 – CAN2 not connected does not need connection 		✔ ✔
0 4 0x00 – CAN3 connected, currently no data is received
0x01 – CAN3 connected, currently data is received
0x02 – CAN3 not connected, needs connection
0x03 – CAN3 not connected does not need connection
1 8 0x01 – ignition on ✔ ✔
1 9 0x02 – key in ignition lock ✔
1 10 0x04 – Webasto ✔
1 11 0x08 – engine is working ✔
1 12 0x10 – standalone engine ✔
1 13 0x20 – ready to drive ✔
1 14 0x40 – engine is working on CNG ✔ ✔
1 15 0x80 – work mode (0 – private, 1 – company) ✔
2 16 0x01 – operator is present ✔
2 17 0x02 – interlock active ✔
2 18 0x04 – handbrake is active ✔
2 19 0x08 – footbrake is active ✔
2 20 0x10 – clutch is pushed ✔
2 21 0x20 – status of the hazard warning lights switch active ✔
2 22 0x40 – front left door opened ✔ ✔
2 23 0x80 – front right door opened ✔ ✔
3 24 0x01 – rear left door opened ✔ ✔
3 25 0x02 – rear right door opened ✔ ✔
3 26 0x04 – trunk door opened ✔ ✔
3 27 0x08 – engine cover opened ✔ ✔
3 28 0x10 – charging wire is plugged ✔
3 29 0x20 – battery charging on ✔
3 30 0x40 – electric engine is working ✔
3 31 0x80 – car is closed with factory remote control ✔
4 32 0x01 – car is closed ✔
4 33 0x02 – factory installed alarm is active ✔
4 34 0x04 – emulated alarm is active ✔
4 35 0x08 – signal of closing with factory remote control was sent ✔
4 36 0x10 – signal of opening with factory remote control was sent ✔
4 37 0x20 – rearm signal was sent ✔
4 38 0x40 – trunk was opened with remote control ✔
4 39 0x80 – CAN module is in SLEEP mode ✔ ✔
5 40 0x01 – signal of closing with factory remote control was sent 3 times ✔
5 41 0x02 – parking is active ✔
5 42 0x04 – reverse is active ✔
5 43 0x08 – neutral is active ✔
5 44 0x10 – drive is active ✔
5 45 0x20 – engine lock active
5 46 0x40 – request to lock the engine (activation after attempt to restart the engine)
5 47 0x80 – factory armed
6 48 0x01 - roof opened ✔ ✔


Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FMx6_CAN_adapters&oldid=99149"