Difference between revisions of "FMB640 CAN adapters"

From Wiki Knowledge Base | Teltonika GPS
(Replaced content with "==Purpose of CAN adapters LV-CAN200 and ALL-CAN300== LV-CAN200 is used to listening data from light vehicles, while ALL-CAN300 is used to listening data from any type of...")
Line 1: Line 1:
 
==Purpose of CAN adapters LV-CAN200 and ALL-CAN300==
 
==Purpose of CAN adapters LV-CAN200 and ALL-CAN300==
  
LV-CAN200 is used to listening data from light vehicles, while ALL-CAN300 is used to listening data from any type of transport: light vehicles, Trucks, busses, agriculture and other special transport. With those adapters FMB640 device is able to collect and send vehicle data.
+
[[Image:FMB640_can_connx_diagram.png|350px|center]]
 +
LV-CAN200 is used to read data from light vehicles, while ALL-CAN300 is used to read data from any type of transport: light vehicles, trucks, buses, agriculture transport and other special transport. Using these adapters {{{model|FMB640}}} device is able to collect and send vehicle data.
 +
 
 +
{| class="wikitable"
 +
|+
 +
! style="width: 200px; background: black; color: white;"  | Parameter
 +
! style="width: 300px; background: black; color: white;" | Value
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Supply voltage
 +
| style="text-align: left; vertical-align: top;" | +9..+50 V
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Power supply current
 +
| style="text-align: left; vertical-align: top;" | Average 10 mA. Max (peak) 100 mA
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Working temperature
 +
| style="text-align: left; vertical-align: top;" | -40..+85 ºC
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Max working humidity
 +
| style="text-align: left; vertical-align: top;" | 60 % (non condensate).
 +
|-
 +
|}
 +
 
 +
==LV-CAN200 and ALL-CAN300 program number selection==
 +
LV-CAN200 or ALL-CAN300 must be set to program number which depends on the vehicle model. '''Needed program number is always written on LV-CAN200 or ALL-CAN300 mounting scheme.''' Please contact Teltonika sales manager to get the latest supported vehicle list and mounting scheme for your vehicle providing information about car manufacturer, model and year.
 +
 
 +
===LV-CAN200 and ALL-CAN300 program number configuration via SMS command===
 +
----
 +
LV-CAN200 and ALL-CAN300 program number can be set remotely, using SMS command, where X is new program number value (more CAN commands can be found in section {{{ctrSMS|[[Template:FMB_SMS/GPRS_command_list#Commands_related_to_LV-CAN200.2FALL-CAN300]]}}}):<br/>''"lvcansetprog X"''<br/>
 +
 
 +
===Selecting LV-CAN200 and ALL-CAN300 program number manually===
 +
----
 +
 
 +
[[Image:FMB640_adapter_led.png|300px|right]]
 +
Steps to set program number:
 +
* Hold SWITCH down until LED stars blinking.
 +
* Release the SWITCH.
 +
* Then LED starts blinking and counting first digit of program number (one blink means digit 1, two blinks mean digit 2 etc).
 +
* To stop counter push SWITCH.
 +
* Release the SWITCH, then LED starts blinking and counting second digit of program number.
 +
* To stop counter push SWITCH.
 +
* Release the SWITCH, then LED starts blinking and counting third digit on program number.
 +
* To stop counter push SWITCH.
 +
* Release SWITCH, if programming is successful LED will blink 10 times.
 +
 
 +
==SIMPLE-CAN - contactless CAN-BUS reader==
 +
 
 +
[[Image:FMB640_simplecan.png|300px|right]]
 +
SIMPLE-CAN is a contactless adapter used to read vehicle CAN data with LV-CAN200 or ALL-CAN300. If LV-CAN200 or ALL-CAN300 connection requires two CAN lines to get all data, then two SIMPLE-CAN readers are required.
 +
 
 +
<font size="+1">Technical details</font>
 +
* Power supply voltage +9..+63 V.
 +
* Power supply current: standby 1.6 mA, active 8.3 mA @ 12 V; standby 0.91 mA, active 4.3 mA @ 24 V.
 +
* CAN-BUS speeds from 33.33 to 500 kb/s.
 +
* Automatically sets CAN Low, CAN High polarity.
 +
* Automatically adjusts signal level and speed.<br/><br/>
 +
 
 +
SIMPLE-CAN works in the '''listening mode only''', so that not all the data available on the CAN-BUS may be received using this solution. '''The device automatically sets CAN L/H polarity''', but the calibration has to be always performed during installation process. Connection of previously calibrated unit to another car needs new calibration because the reader '''automatically adjusts signal level and speed''' to different CAN buses. The device also '''automatically adapts''' to the found '''noise level'''.
  
[[Image:FMB640_can_connx_diagram.png|350px|center]]
+
[[Image:FMB640_simplecan_pinout.png|800px|center]]
 +
 
 +
When power supply is connected, the LED shines continuously. It means that device is waiting for calibration. '''Calibration process''' has to be carried out when CAN-BUS twisted pair is tightened on SIMPLE-CAN and when ignition is ON. Please press the switch briefly and wait for the LED to start blinking every second. Automatic calibration process takes up to 10 seconds depending on the vehicle's model. Correct calibration process is confirmed by LED starting to blink every 2 seconds (when the CAN-BUS is active). When the CAN-BUS enters sleep mode, SIMPLE-CAN device also enters sleep mode and takes 1.6mA @ 12V. In the sleep mode LED does not shine. If after calibration process LED shines continuously, it means that device is not calibrated yet, CAN-BUS transmission has failed or ignition during calibration was not ON.
 +
 
 +
==Connecting FMB640 CAN adapters ALL-CAN300 and LV-CAN200==
 +
 
 +
Connect LV-CAN200/ALL-CAN300 Pin 5 to {{{model|FMB640}}} Pin 12 (INPUT 5) or Pin 6 (INPUT 6) and connect light vehicle CAN adapter to other end of the cable.<br/>Connect CAN adapter Pin 1 and Pin 2 to car's CAN bus. CAN interface location of the supported light vehicle is described on mounting scheme.<br/>Connect car power supply lines to Pin 3 positive, Pin 4 negative.<br/>Pin 9 and 10 connections are optional depending on the exact car model.<br/>For exact pinout see the sticker of light vehicle CAN adapter.
 +
 
 +
[[Image:FMB640_lv-can200_pinout.png|800px|center]]
 +
[[Image:FMB640_all-can300_pinout.png|800px|center]]
 +
 
 +
{| class="wikitable" style="border-style: solid; border-width: 0px"
 +
|+
 +
|-
 +
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
 +
| style="text-align: left; background: #F6F6FB;"        | '''ATTENTION! For detailed diagram of connection between adapter and light vehicle please contact Teltonika sales representative and provide information about car manufacturer, model and year.'''
 +
|-
 +
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
 +
| style="text-align: left; background: #F6F6FB;"        | '''ATTENTION! Do not swap CAN L and CAN H lines.<br/>Do not swap power supply lines. Make sure that voltage does not exceed 30V. Power supply lines should be connected at the end of installation work.'''
 +
|}
 +
 
 +
==FMB640 ALL-CAN300 and LV-CAN200 parameters configuration==
 +
 
 +
Because FMB640 have LV-CAN200/ALL-CAN300 RX and TX in its own pinout, device configuration can be performed via micro-USB when CAN adapter is connected to the vehicle.<br/>When {{{model|FMB640}}} is connected to LV-CAN200 or ALL-CAN300, user can see all information that is received from the vehicle in configurator LVCAN section, all data are highlighted by green background color. Information in this section is automatically refreshed. CAN bus data which can be read from your car is provided in "Light or All Vehicles CAN adapter supported cars" document.<br/>The LVCAN I/O element can be configured like any other I/O element in FMB640 configurator.
 +
 
 +
[[Image:FMB640_can_conf_example.png|800px|centre]]
 +
 
 +
When using offline configuration method user can select which CAN data will be read from LV-CAN200 or ALL-CAN300 and sent directly to the server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. For further information check "Light and All Vehicles CAN adapter supported cars” document.<br/>All information about I/O element parameters description is in section [[FMB640 I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in "FMB640 Protocols" document, except ALL-CAN300 bitmasks, which are described in the table below.
 +
 
 +
{| class="wikitable"
 +
|+
 +
! style="width: 150px; background: black; color: white;"  | Property name
 +
! style="width: 50px; background: black; color: white;" | Size, bytes
 +
! style="width: 400px; background: black; color: white;" | Value bitmasks
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Control state flags
 +
| style="text-align: left; vertical-align: top;" | 4
 +
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#FF6600>0x01</span> – STOP<br/><span style=color:#FF6600>0x02</span> – Oil pressure / level<br/><span style=color:#FF6600>0x04</span> – Coolant liquid temperature / level<br/><span style=color:#FF6600>0x08</span> – Handbrake system<br/><span style=color:#FF6600>0x20</span> – AIRBAG<br/><br/>
 +
Byte1:<br/><span style=color:#0000FF>0x01</span> – CHECK ENGINE<br/><span style=color:#0000FF>0x02</span> – Lights failure<br/><span style=color:#0000FF>0x04</span> – Low tire pressure<br/><span style=color:#0000FF>0x08</span> – Wear of brake pads<br/><span style=color:#0000FF>0x10</span> – Warning<br/><span style=color:#0000FF>0x20</span> – ABS<br/><span style=color:#0000FF>0x40</span> – Low Fuel<br/><br/>
 +
Byte2:<br/><span style=color:#339A6C>0x01</span> – ESP<br/><span style=color:#339A6C>0x02</span> – Glow plug indicator<br/><span style=color:#339A6C>0x04</span> – FAP<br/><span style=color:#339A6C>0x08</span> – Electronics pressure control<br/><span style=color:#339A6C>0x10</span> – Parking lights<br/><span style=color:#339A6C>0x20</span> – Dipped headlights<br/><span style=color:#339A6C>0x40</span> – Full beam headlights<br/><br/>
 +
Byte3:<br/><span style=color:#9A3300>0x40</span> – Passenger's seat belt<br/><span style=color:#9A3300>0x80</span> – Driver's seat belt<br/>
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Agricultural machinery flags
 +
| style="text-align: left; vertical-align: top;" | 8
 +
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#FF6600>0x01</span> – Mowing<br/><span style=color:#FF6600>0x02</span> – Grain release from hopper<br/><span style=color:#FF6600>0x04</span> – First front hydraulic turned on<br/><span style=color:#FF6600>0x08</span> – Rear Power Take-Off turned on<br/><br/>
 +
Byte1:<br/><span style=color:#0000FF>0x01</span> – Excessive play under the threshing drum<br/><span style=color:#0000FF>0x02</span> – Grain tank is open<br/><span style=color:#0000FF>0x04</span> – 100% of Grain tank<br/><span style=color:#0000FF>0x08</span> – 70% of Grain tank<br/><span style=color:#0000FF>0x10</span> – Drain filter in hydraulic system of drive cylinders is plugged<br/><span style=color:#0000FF>0x20</span> – Pressure filter of drive cylinders hydraulic system is plugged<br/><span style=color:#0000FF>0x40</span> – Alarm oil level in oil tank<br/><span style=color:#0000FF>0x80</span> – Pressure filter of brakes hydraulic system is plugged<br/><br/>
 +
Byte2:<br/><span style=color:#339A6C>0x01</span> – Oil filter of engine is plugged<br/><span style=color:#339A6C>0x02</span> – Fuel filter is plugged<br/><span style=color:#339A6C>0x04</span> – Air filter is plugged<br/><span style=color:#339A6C>0x08</span> – Alarm oil temperature in hydraulic system of chassis<br/><span style=color:#339A6C>0x10</span> – Alarm oil temperature in hydraulic system of drive cylinders<br/><span style=color:#339A6C>0x20</span> – Alarm oil pressure in engine<br/><span style=color:#339A6C>0x40</span> – Alarm coolant level<br/><span style=color:#339A6C>0x80</span> – Overflow chamber of hydraulic unit<br/><br/>
 +
Byte3:<br/><span style=color:#9A3300>0x01</span> – Unloader drive is ON. Unloading tube pivot is in idle position<br/><span style=color:#9A3300>0x02</span> – No operator!<br/><span style=color:#9A3300>0x04</span> – Straw walker is plugged<br/><span style=color:#9A3300>0x08</span> – Water in fuel<br/><span style=color:#9A3300>0x10</span> – Cleaning fan RPM<br/><span style=color:#9A3300>0x20</span> – Trashing drum RPM<br/><br/>
 +
Byte4:<br/><span style=color:#FF00FF>0x02</span> – Low water level in the tank<br/><span style=color:#FF00FF>0x04</span> – First rear hydraulic turned on<br/><span style=color:#FF00FF>0x08</span> – Standalone engine working<br/><span style=color:#FF00FF>0x10</span> – Right joystick moved right<br/><span style=color:#FF00FF>0x20</span> – Right joystick moved left<br/><span style=color:#FF00FF>0x40</span> – Right joystick moved front<br/><span style=color:#FF00FF>0x80</span> – Right joystick moved back<br/><br/>
 +
Byte5:<br/><span style=color:#339A6C>0x01</span> – Brushes turned on<br/><span style=color:#339A6C>0x02</span> – Water supply turned on<br/><span style=color:#339A6C>0x04</span> – Vacuum cleaner<br/><span style=color:#339A6C>0x08</span> – Unloading from the hopper<br/><span style=color:#339A6C>0x10</span> – High Pressure washer (Karcher)<br/><span style=color:#339A6C>0x20</span> – Salt (sand) disperser ON<br/><span style=color:#339A6C>0x40</span> – Low salt (sand) level<br/><br/>
 +
Byte6:<br/><span style=color:#66D6AD>0x01</span> – Second front hydraulic turned on<br/><span style=color:#66D6AD>0x02</span> – Third front hydraulic turned on<br/><span style=color:#66D6AD>0x04</span> – Fourth front hydraulic turned on<br/><span style=color:#66D6AD>0x08</span> – Second rear hydraulic turned on<br/><span style=color:#66D6AD>0x10</span> – Third rear hydraulic turned on<br/><span style=color:#66D6AD>0x20</span> – Fourth rear hydraulic turned on<br/><span style=color:#66D6AD>0x40</span> – Front three-point Hitch turned on<br/><span style=color:#66D6AD>0x80</span> – Rear three-point Hitch turned on<br/><br/>
 +
Byte7:<br/><span style=color:#00331A>0x01</span> – Left joystick moved right<br/><span style=color:#00331A>0x02</span> – Left joystick moved left<br/><span style=color:#00331A>0x04</span> – Left joystick moved front<br/><span style=color:#00331A>0x08</span> – Left joystick moved back<br/><span style=color:#00331A>0x10</span> – Front Power Take-Off turned on<br/>
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Security state flags
 +
| style="text-align: left; vertical-align: top;" | 8
 +
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#008181>0x20</span> – Bit appears when any operate button in car was put<br/><span style=color:#008181>0x40</span> – Bit appears when immobiliSer is in service mode<br/><span style=color:#008181>0x80</span> – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car<br/><br/>
 +
Byte1:<br/><span style=color:#FF6600>0x01</span> – the key is in ignition lock<br/><span style=color:#FF6600>0x02</span> – Ignition on<br/><span style=color:#FF6600>0x04</span> – Dynamic ignition on<br/><span style=color:#FF6600>0x08</span> – Webasto<br/><span style=color:#FF6600>0x20</span> – Car closed by factory's remote control<br/><span style=color:#FF6600>0x40</span> – Factory-installed alarm system is actuated (is in panic mode)<br/><span style=color:#FF6600>0x80</span> – Factory-installed alarm system is emulated by module<br/><br/>
 +
Byte2:<br/><span style=color:#339A6C>0x01</span> – Parking activated (automatic gearbox)<br/><span style=color:#339A6C>0x10</span> – Handbrake is actuated (information available only with ignition on)<br/><span style=color:#339A6C>0x20</span> – Footbrake is actuated (information available only with ignition on)<br/><span style=color:#339A6C>0x40</span> – Engine is working (information available only when the ignition on)<br/><span style=color:#339A6C>0x80</span> – Reverse is on<br/><br/>
 +
Byte3:<br/><span style=color:#0000FF>0x01</span> – Front left door opened<br/><span style=color:#0000FF>0x02</span> – Front right door opened<br/><span style=color:#0000FF>0x04</span> – Rear left door opened<br/><span style=color:#0000FF>0x08</span> – Rear right door opened<br/><span style=color:#0000FF>0x10</span> – Engine cover opened<br/><span style=color:#0000FF>0x20</span> – Trunk door opened<br/><br/>
 +
Byte4:<br/><span style=color:#9DCD00>0x01</span> – Car was closed by the factory's remote control<br/><span style=color:#9DCD00>0x02</span> – Car was opened by the factory's remote control<br/><span style=color:#9DCD00>0x03?</span> – Trunk cover was opened by the factory's remote control<br/><span style=color:#9DCD00>0x04</span> – Module has sent a rearming signal<br/><span style=color:#9DCD00>0x05?</span> – Car was closed three times by the factory's remote control<br/>
 +
- High nibble (mask 0xF0 bit)<br/><span style=color:#9DCD00>0x80</span> – CAN module goes to sleep mode<br/>
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Tachograph driver card presence
 +
| style="text-align: left; vertical-align: top;" | 1
 +
| style="text-align: left; vertical-align: top;" | <span style=color:#9A3300>0x00</span> – No driver card<br/><span style=color:#9A3300>0x01</span> – Driver1 card presence<br/><span style=color:#9A3300>0x02</span> – Driver2 card presence<br/><span style=color:#9A3300>0x03</span> – Driver1 and driver2 cards present<br/>
 +
|-
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver 1 states
 +
| style="text-align: left; vertical-align: top;" | 1
 +
| style="text-align: left; vertical-align: top;" rowspan=2 | <span style=color:#124806>0xX0</span> – Break/rest<br/><span style=color:#124806>0xX1</span> – Availability<br/><span style=color:#124806>0xX2</span> – Work<br/><span style=color:#124806>0xX3</span> – Driving<br/><span style=color:#124806>0x0X</span> – No time-related warning detected<br/><span style=color:#124806>0x1X</span> – Limit #1: 15 min before 4 1/2 h<br/><span style=color:#124806>0x2X</span> – Limit #2: 4 1/2 h reached (continuous driving time exceeded)<br/><span style=color:#124806>0x3X</span> – Limit #3: 15 minutes before optional warning 1<br/><span style=color:#124806>0x4X</span> – Limit #4: optional warning 1 reached<br/><span style=color:#124806>0x5X</span> – Limit #5: 15 min before optional warning<br/><span style=color:#124806>0x6X</span> – Limit #6: optional warning 2 reached<br/>
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver 2 states
 +
| style="text-align: left; vertical-align: top;" | 1
 +
|}
 +
 
 +
==Send data with 0, if ignition is off==
 +
 
 +
Depending on LV-CAN200/ALL-CAN300 I/O parameters and ignition status, FMB640 can send locked (last known) LV-CAN200/ALL-CAN300 I/O and active (real time) parameters values or reset values to 0. When ignition is off, LV-CAN200/ALL-CAN300 I/O parameters values sent to server are:
 +
 
 +
{| class="wikitable"
 +
|+
 +
! style="width: 300px; background: black; color: white;"  | LV-CAN200/ALL-CAN300 I/O element
 +
! style="width: 100px; background: black; color: white;" | Status
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Vehicle Speed
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Accelerator pedal position
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Total fuel used
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Fuel level (liters)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Engine RPM
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Total mileage
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Fuel level (%)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Program number
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Module ID
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Engine Work Time
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Engine Work Time (counted)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Total Mileage (counted)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Fuel Consumed (counted)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Fuel Rate
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Program number
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | AdBlue Level (%)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | AdBlue Level (liters)
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Engine Load
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Engine Temperature
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Axle 1 Load
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Axle 2 Load
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Axle 3 Load
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Axle 4 Load
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Axle 5 Load
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Control State Flags
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Agricultural Machinery Flags
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Harvesting Time
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Area of Harvest
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Mowing Efficiency
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Grain Mown Volume
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Grain Moisture
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Harvesting Drum RPM
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Gap Under Harvesting Drum
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Security State Flags
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Tachograph Total Vehicle Distance
 +
| style="text-align: left; vertical-align: top;" | lock
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Trip Distance
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Tachograph Vehicle Speed
 +
| style="text-align: left; vertical-align: top;" | reset
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Tachograph Driver Card Presence
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver1 States
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver2 States
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver1 Continuous Driving Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver2 Continuous Driving Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver1 Cumulative Break Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver2 Cumulative Break Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver1 Selected Activity Duration
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver2 Selected Activity Duration
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver1 Cumulative Driving Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Driver2 Cumulative Driving Time
 +
| style="text-align: left; vertical-align: top;" | active
 +
|-
 +
|}
 +
 
 +
==LV-CAN200/ALL-CAN300 Important Information==
 +
===Program Number logic change===
 +
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/ALL-CAN300 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. Device still understands the entered 3-digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - device number will turn into "1247". In Bootloader only 4-digit format is available, just add "1" to the front of the needed program number.
 +
 
 +
===Example===
 +
When using older connection schemes where program number displayed as 3-digit program number:
 +
[[Image:FMB640_can_prog_number.png|600px|center]]
 +
 
 +
Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of program number:
 +
[[Image:FMB640_can_updater.png|400px|center]]

Revision as of 14:26, 28 May 2018

Main Page > EOL Products > FMB640 > FMB640 Manual > FMB640 CAN adapters

Purpose of CAN adapters LV-CAN200 and ALL-CAN300

FMB640 can connx diagram.png

LV-CAN200 is used to read data from light vehicles, while ALL-CAN300 is used to read data from any type of transport: light vehicles, trucks, buses, agriculture transport and other special transport. Using these adapters FMB640 device is able to collect and send vehicle data.

Parameter Value
Supply voltage +9..+50 V
Power supply current Average 10 mA. Max (peak) 100 mA
Working temperature -40..+85 ºC
Max working humidity 60 % (non condensate).

LV-CAN200 and ALL-CAN300 program number selection

LV-CAN200 or ALL-CAN300 must be set to program number which depends on the vehicle model. Needed program number is always written on LV-CAN200 or ALL-CAN300 mounting scheme. Please contact Teltonika sales manager to get the latest supported vehicle list and mounting scheme for your vehicle providing information about car manufacturer, model and year.

LV-CAN200 and ALL-CAN300 program number configuration via SMS command


LV-CAN200 and ALL-CAN300 program number can be set remotely, using SMS command, where X is new program number value (more CAN commands can be found in section Template:FMB_SMS/GPRS_command_list#Commands_related_to_LV-CAN200.2FALL-CAN300):
"lvcansetprog X"

Selecting LV-CAN200 and ALL-CAN300 program number manually


FMB640 adapter led.png

Steps to set program number:

  • Hold SWITCH down until LED stars blinking.
  • Release the SWITCH.
  • Then LED starts blinking and counting first digit of program number (one blink means digit 1, two blinks mean digit 2 etc).
  • To stop counter push SWITCH.
  • Release the SWITCH, then LED starts blinking and counting second digit of program number.
  • To stop counter push SWITCH.
  • Release the SWITCH, then LED starts blinking and counting third digit on program number.
  • To stop counter push SWITCH.
  • Release SWITCH, if programming is successful LED will blink 10 times.

SIMPLE-CAN - contactless CAN-BUS reader

FMB640 simplecan.png

SIMPLE-CAN is a contactless adapter used to read vehicle CAN data with LV-CAN200 or ALL-CAN300. If LV-CAN200 or ALL-CAN300 connection requires two CAN lines to get all data, then two SIMPLE-CAN readers are required.

Technical details

  • Power supply voltage +9..+63 V.
  • Power supply current: standby 1.6 mA, active 8.3 mA @ 12 V; standby 0.91 mA, active 4.3 mA @ 24 V.
  • CAN-BUS speeds from 33.33 to 500 kb/s.
  • Automatically sets CAN Low, CAN High polarity.
  • Automatically adjusts signal level and speed.

SIMPLE-CAN works in the listening mode only, so that not all the data available on the CAN-BUS may be received using this solution. The device automatically sets CAN L/H polarity, but the calibration has to be always performed during installation process. Connection of previously calibrated unit to another car needs new calibration because the reader automatically adjusts signal level and speed to different CAN buses. The device also automatically adapts to the found noise level.

FMB640 simplecan pinout.png

When power supply is connected, the LED shines continuously. It means that device is waiting for calibration. Calibration process has to be carried out when CAN-BUS twisted pair is tightened on SIMPLE-CAN and when ignition is ON. Please press the switch briefly and wait for the LED to start blinking every second. Automatic calibration process takes up to 10 seconds depending on the vehicle's model. Correct calibration process is confirmed by LED starting to blink every 2 seconds (when the CAN-BUS is active). When the CAN-BUS enters sleep mode, SIMPLE-CAN device also enters sleep mode and takes 1.6mA @ 12V. In the sleep mode LED does not shine. If after calibration process LED shines continuously, it means that device is not calibrated yet, CAN-BUS transmission has failed or ignition during calibration was not ON.

Connecting FMB640 CAN adapters ALL-CAN300 and LV-CAN200

Connect LV-CAN200/ALL-CAN300 Pin 5 to FMB640 Pin 12 (INPUT 5) or Pin 6 (INPUT 6) and connect light vehicle CAN adapter to other end of the cable.
Connect CAN adapter Pin 1 and Pin 2 to car's CAN bus. CAN interface location of the supported light vehicle is described on mounting scheme.
Connect car power supply lines to Pin 3 positive, Pin 4 negative.
Pin 9 and 10 connections are optional depending on the exact car model.
For exact pinout see the sticker of light vehicle CAN adapter.

FMB640 lv-can200 pinout.png
FMB640 all-can300 pinout.png
Bw nb.png ATTENTION! For detailed diagram of connection between adapter and light vehicle please contact Teltonika sales representative and provide information about car manufacturer, model and year.
Bw nb.png ATTENTION! Do not swap CAN L and CAN H lines.
Do not swap power supply lines. Make sure that voltage does not exceed 30V. Power supply lines should be connected at the end of installation work.

FMB640 ALL-CAN300 and LV-CAN200 parameters configuration

Because FMB640 have LV-CAN200/ALL-CAN300 RX and TX in its own pinout, device configuration can be performed via micro-USB when CAN adapter is connected to the vehicle.
When FMB640 is connected to LV-CAN200 or ALL-CAN300, user can see all information that is received from the vehicle in configurator LVCAN section, all data are highlighted by green background color. Information in this section is automatically refreshed. CAN bus data which can be read from your car is provided in "Light or All Vehicles CAN adapter supported cars" document.
The LVCAN I/O element can be configured like any other I/O element in FMB640 configurator.

When using offline configuration method user can select which CAN data will be read from LV-CAN200 or ALL-CAN300 and sent directly to the server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. For further information check "Light and All Vehicles CAN adapter supported cars” document.
All information about I/O element parameters description is in section I/O settings.
All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in "FMB640 Protocols" document, except ALL-CAN300 bitmasks, which are described in the table below.

Property name Size, bytes Value bitmasks
Control state flags 4 Byte0 (LSB):
0x01 – STOP
0x02 – Oil pressure / level
0x04 – Coolant liquid temperature / level
0x08 – Handbrake system
0x20 – AIRBAG

Byte1:
0x01 – CHECK ENGINE
0x02 – Lights failure
0x04 – Low tire pressure
0x08 – Wear of brake pads
0x10 – Warning
0x20 – ABS
0x40 – Low Fuel

Byte2:
0x01 – ESP
0x02 – Glow plug indicator
0x04 – FAP
0x08 – Electronics pressure control
0x10 – Parking lights
0x20 – Dipped headlights
0x40 – Full beam headlights

Byte3:
0x40 – Passenger's seat belt
0x80 – Driver's seat belt

Agricultural machinery flags 8 Byte0 (LSB):
0x01 – Mowing
0x02 – Grain release from hopper
0x04 – First front hydraulic turned on
0x08 – Rear Power Take-Off turned on

Byte1:
0x01 – Excessive play under the threshing drum
0x02 – Grain tank is open
0x04 – 100% of Grain tank
0x08 – 70% of Grain tank
0x10 – Drain filter in hydraulic system of drive cylinders is plugged
0x20 – Pressure filter of drive cylinders hydraulic system is plugged
0x40 – Alarm oil level in oil tank
0x80 – Pressure filter of brakes hydraulic system is plugged

Byte2:
0x01 – Oil filter of engine is plugged
0x02 – Fuel filter is plugged
0x04 – Air filter is plugged
0x08 – Alarm oil temperature in hydraulic system of chassis
0x10 – Alarm oil temperature in hydraulic system of drive cylinders
0x20 – Alarm oil pressure in engine
0x40 – Alarm coolant level
0x80 – Overflow chamber of hydraulic unit

Byte3:
0x01 – Unloader drive is ON. Unloading tube pivot is in idle position
0x02 – No operator!
0x04 – Straw walker is plugged
0x08 – Water in fuel
0x10 – Cleaning fan RPM
0x20 – Trashing drum RPM

Byte4:
0x02 – Low water level in the tank
0x04 – First rear hydraulic turned on
0x08 – Standalone engine working
0x10 – Right joystick moved right
0x20 – Right joystick moved left
0x40 – Right joystick moved front
0x80 – Right joystick moved back

Byte5:
0x01 – Brushes turned on
0x02 – Water supply turned on
0x04 – Vacuum cleaner
0x08 – Unloading from the hopper
0x10 – High Pressure washer (Karcher)
0x20 – Salt (sand) disperser ON
0x40 – Low salt (sand) level

Byte6:
0x01 – Second front hydraulic turned on
0x02 – Third front hydraulic turned on
0x04 – Fourth front hydraulic turned on
0x08 – Second rear hydraulic turned on
0x10 – Third rear hydraulic turned on
0x20 – Fourth rear hydraulic turned on
0x40 – Front three-point Hitch turned on
0x80 – Rear three-point Hitch turned on

Byte7:
0x01 – Left joystick moved right
0x02 – Left joystick moved left
0x04 – Left joystick moved front
0x08 – Left joystick moved back
0x10 – Front Power Take-Off turned on

Security state flags 8 Byte0 (LSB):
0x20 – Bit appears when any operate button in car was put
0x40 – Bit appears when immobiliSer is in service mode
0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car

Byte1:
0x01 – the key is in ignition lock
0x02 – Ignition on
0x04 – Dynamic ignition on
0x08 – Webasto
0x20 – Car closed by factory's remote control
0x40 – Factory-installed alarm system is actuated (is in panic mode)
0x80 – Factory-installed alarm system is emulated by module

Byte2:
0x01 – Parking activated (automatic gearbox)
0x10 – Handbrake is actuated (information available only with ignition on)
0x20 – Footbrake is actuated (information available only with ignition on)
0x40 – Engine is working (information available only when the ignition on)
0x80 – Reverse is on

Byte3:
0x01 – Front left door opened
0x02 – Front right door opened
0x04 – Rear left door opened
0x08 – Rear right door opened
0x10 – Engine cover opened
0x20 – Trunk door opened

Byte4:
0x01 – Car was closed by the factory's remote control
0x02 – Car was opened by the factory's remote control
0x03? – Trunk cover was opened by the factory's remote control
0x04 – Module has sent a rearming signal
0x05? – Car was closed three times by the factory's remote control
- High nibble (mask 0xF0 bit)
0x80 – CAN module goes to sleep mode

Tachograph driver card presence 1 0x00 – No driver card
0x01 – Driver1 card presence
0x02 – Driver2 card presence
0x03 – Driver1 and driver2 cards present
Driver 1 states 1 0xX0 – Break/rest
0xX1 – Availability
0xX2 – Work
0xX3 – Driving
0x0X – No time-related warning detected
0x1X – Limit #1: 15 min before 4 1/2 h
0x2X – Limit #2: 4 1/2 h reached (continuous driving time exceeded)
0x3X – Limit #3: 15 minutes before optional warning 1
0x4X – Limit #4: optional warning 1 reached
0x5X – Limit #5: 15 min before optional warning
0x6X – Limit #6: optional warning 2 reached
Driver 2 states 1

Send data with 0, if ignition is off

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

LV-CAN200/ALL-CAN300 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

LV-CAN200/ALL-CAN300 Important Information

Program Number logic change

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.
In new LV-CAN200/ALL-CAN300 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.
However, all existing program numbers stay the same, but "1" is added to the front. Device still understands the entered 3-digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - device number will turn into "1247". In Bootloader only 4-digit format is available, just add "1" to the front of the needed program number.

Example

When using older connection schemes where program number displayed as 3-digit program number:

FMB640 can prog number.png

Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of program number:

FMB640 can updater.png