|
|
| (12 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | 13FMB640 with LV-CAN 200 and all-can 300 can adapter
| + | {{Template:FMB640_CAN_adapters|model=FMB640}} |
| − | 13.1Purpose of Can Adapters LV-CAN200 and ALL-CAN300
| + | [[Category:FMB640 Manual| 8]] |
| − | | |
| − | 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.
| |
| − | | |
| − | Figure 63 LV-CAN
| |
| − | | |
| − | FMB640 shares the same USB port for connecting adapter and configuring device with PC.
| |
| − | LV-CAN200 and ALL-CAN300 Technical characteristics:
| |
| − | | |
| − | PARAMETER VALUE
| |
| − | Supply voltage 9 to 50V
| |
| − | Power supply current Average 10mA
| |
| − | Max (peak) 100mA
| |
| − | Working temperature -40..85 ºC
| |
| − | Max working humidity 60 % (non condensate)
| |
| − | 13.2LV-CAN200 and ALL-CAN300 program number selection
| |
| − | LV-CAN200 or ALL-CAN300 must be set to program number which depends on vehicle model. Needed program number is always written on LV-CAN200 or ALL-CAN300 mounting scheme. Please contact Your Teltonika sales manager to get latest supported vehicle list and mounting scheme for your vehicle, please provide CAR manufacturer, model and year information.
| |
| − | 13.2.1 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:
| |
| − | lvcansetprog X
| |
| − | X is new program number value.
| |
| − | CAN program number can be obtained via SMS: lvcangetprog
| |
| − | Response: “CAN Program Nr: XXX”
| |
| − | | |
| − | Get CAN info by SMS: lvcangetinfo
| |
| − | Response: “Prog: 139SWRevison: 6KernVer: 10KernVar: 49MdlID: 8884443332221110”
| |
| − | 13.2.2 Selecting LV-CAN200 and ALL-CAN300 program number manually
| |
| − | Steps to set program number:
| |
| − | Hold SWITCH down till LED stars blinking
| |
| − | Release the SWITCH
| |
| − | Then LED starts blinking and counting first digit of program number, (one blink means digit 1, two blink 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 succeded LED will blink 10 times
| |
| − | | |
| − | | |
| − | Figure 64 Adapter signaling led
| |
| − | | |
| − | | |
| − | 13.2.3 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 digits, to 4 digits 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 stays the same, it is just "1" appeared in front of them. Device still understands entered 3 digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - device will turn it into the "1247". In Bootloader it is only 4 digit format available, just add "1" in from of the needed program number.
| |
| − | | |
| − | | |
| − | | |
| − | Example:
| |
| − | | |
| − | If use oldest connection schemes where program number displayed as 3 digit program number:
| |
| − | | |
| − | | |
| − | Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 need add "1" before it:
| |
| − | | |
| − | | |
| − | | |
| − | 13.3SIMPLE-CAN - contactless CAN-BUS reader
| |
| − | | |
| − | SIMPLE-CAN is contactless adapter used to read vehicle CAN data with LV-CAN200, ALL-CAN300. If LV-CAN200 or ALL-CAN300 connection requires two CAN lines to get all data, then you need two SIMPLE-CAN readers
| |
| − | | |
| − | TECHNICAL DETAILS
| |
| − | Power supply voltage 9-63 V
| |
| − | Power supply current:
| |
| − | Mode 12V 24V
| |
| − | Active 8.3 mA 4.3 mA
| |
| − | Standby 1.6 mA 0.91 mA
| |
| − | 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 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 executed 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.
| |
| − | | |
| − | | |
| − | Figure 65 Simple can connection
| |
| − | | |
| − | After power supply connecting, LED shines continuously. It means that device waits for calibration. Calibration process has to be carried out when CAN-BUS twisted pair is tightened on SIMPLE-CAN and when the ignition is ON. Please press the switch shortly and wait for the LED to start blinking every 1 second. Automatic calibration process takes up to 10 seconds depending on the vehicle's model. Correct calibration process is confirmed by LED's every 2 seconds blink (when the CAN-BUS is active). When the CAN-BUS enters sleep mode, SIMPLE-CAN device does it also 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.
| |
| − | | |
| − | 13.4Connecting FMB640 Can adapters ALL-CAN300 and LV-CAN200
| |
| − | Connect USB Plug to FMB640 device, connect Light Vehicles Can adapter to other end of the cable.
| |
| − | Connect Light Vehicles Can adapter Pin 1 and Pin 2 to cars 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.
| |
| − | Pins 9, 10 connections are optional it depends on exact car model.
| |
| − | For exact pinout see sticker on Light Vehicles Can adapter.
| |
| − | | |
| − | | |
| − | Figure 66 LV-CAN200 Adapter connection cable pinout
| |
| − | | |
| − | | |
| − | Figure 67 ALL-CAN300 Adapter connection cable pinout
| |
| − | | |
| − | Attention! Ordered LV-CAN200 and ALL-CAN300 packaging may vary:
| |
| − | 1. Standard with mini-USB cable.
| |
| − | 2.USB PCB (female) + mini-USB cable.
| |
| − | Attention! For detailed connection diagram of adapter to light vehicle please contact Teltonika, LTD sales representative and provide CAR manufacturer, model and year information.
| |
| − | Attention! Do not swap CAN L and CAN H lines.
| |
| − | Do not swap power supply lines. Make sure that voltage do not exceeds 30V. Power supply lines should be connected at the end of installation work.
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | 13.5FMB640 Configuration with LV-CAN200 and ALL-CAN300
| |
| − | | |
| − | FMB640 shares the same USB port for connecting LV-CAN200 or ALL-CAN300 adapter and configuring device with PC.
| |
| − | FMB640 can be configured using in LVCAN tab. | |
| − | | |
| − | When FMB640 is connected to CAN adapter (Figure 68), wait 10s (Note, that car engine must be started), disconnect adapter from FMB640, and connect PC USB cable to FMB640 Device, It is very important not to disconnect FMB640 from power source during this operation, because if FMB640 is reconnected all received CAN bus data will be lost. FMB640 remembers received data from LV-CAN200 or ALL-CAN300 and at the end user will see all CAN data which is sent by adapter. Enable CAN data which needs send to server and save configuration pressing “Save to device” button.
| |
| − | To configure CAN data:
| |
| − | 1.In car, connect LV-CAN200 or ALL-CAN300 to CAN bus and to the FMB640 device (Figure 68) wait 10 seconds. Note, that car engine must be started.
| |
| − | 2.Disconnect LV-CAN200 or ALL-CAN300 from FMB640 and connect PC USB cable to FMB640 Device, It is very important not to disconnect FMB640 from power source, because then all CAN data will be lost.
| |
| − | | |
| − | | |
| − | | |
| − | Figure 68 Connect adapter LV-CAN200 to FMB640
| |
| − | | |
| − | | |
| − | | |
| − | Figure 69 Connect FMB640 to PC and configure
| |
| − | | |
| − | CAN bus data which can be read from your car is shown in “Light or ALL Vehicles Can adapter supported cars” document.
| |
| − | | |
| − | User can select which CAN data will be red from LV-CAN200 or ALL-CAN300 and directly sent to server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. Please for further information check “Light and All Vehicles Can adapter supported cars” document.
| |
| − | There are two types of operations with CAN data elements:
| |
| − | Monitoring of CAN bus data
| |
| − | CAN bus data event capturing
| |
| − | Monitoring method is used when user wants to receive CAN data on regular basis, for example every 20 seconds.
| |
| − | Event functionality is used to store additional AVL packet when state of CAN element is changing. For example Speed changes, low fuel level, engine temperate, etc.
| |
| − | Send data to server field – allows enabling CAN element so it is added to the AVL data packet and sent to the server. By default, all CAN elements are disabled and FMB640 records only GPS data.
| |
| − | It is possible to set CAN message priority: On Low Priority, On High Priority, and On Panic. Regular packets are sent as Low priority records. When low priority event is triggered, FMB640 makes additional record with indication what was the reason for that was CAN element change. When High priority is selected, module makes additional record with high priority flag and sends event packet immediately to the server by GPRS. Panic priority triggers same actions as high priority, but if GPRS fails, it sends AVL packet to server using SMS mode if SMS is enabled in SMS settings.
| |
| − | Data Acquisition Type – defines when to generate event – when value enters defined range, exits it or both, also is possible to select event which you want to generate then you change values, like crossing both values in high and low levels (Hysteresis).
| |
| − | High and Low levels – defines CAN value range. If CAN value enter or exits this range, FMB640 generates event by “Data Acquisition Type” settings. Figure 70 show example of FMB640 CAN configuration.
| |
| − | | |
| − | Figure 70 Configurator example
| |
| − | LVCAN mode (ID=903)
| |
| − | This parameter sets LVCAN/ALLCAN detection, available values: 0 – Auto Detect, 1 – LVCAN200, 2 – ALLCAN300.
| |
| − | | |
| − | Minimum value Maximum value Recommended value Goes with (depends on) parameters Value type
| |
| − | 0 2 0 U8
| |
| − | | |
| − | Send data with 0, if ignition is off. Depending on LVCAN/ALLCAN I/O parameters and ignition status, FMB640 can send locked (last known) LVCAN/ALLCAN I/O parameters values, reset values (set to 0) and active (real time) parameters values.
| |
Easy steps to install and configure following CAN adapters on FMB640 device:
Installing CAN adapter with FMB640 device
Installing LV-CAN200/ALL-CAN300/CAN-CONTROL
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/ALL-CAN300/CAN-CONTROL
- 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
- Be ready with a vehicle connection scheme that you have received from a Teltonika Sales Representative.
- Check the scheme for the current vehicle connection. Look for connectors matching PINs numbers and colors (maybe different) according to connection scheme.
- Connect CAN adapter with FMB640:
- Connect CAN adapter's MINI USB to USB of FMB640.
- Connect CAN adapter CAN wires (CAN L, CAN H) as specified in connection scheme.
| Do not swap CAN L and CAN H lines.
Not all CAN adapter wires may be used in vehicle. |
- Connect CAN adapter positive and ground wires to the vehicle power supply lines or near FMB640 power wires.
| Do not swap power supply lines.
Make sure that voltage does not exceed 30V. |
- Switch vehicle ignition to ACC position. CAN adapter LED diode on the back should start blinking.
- Configure CAN adapter to read CAN bus data or control vehicle by setting its program number - CAN Adapter configuration
LV-CAN200/ALL-CAN300 connection example. This is not a connection diagram for your vehicle. Every vehicle has a specific scheme.
CAN-CONTROL 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
- Follow the same 1, 2, 3 installation steps as with LV-CAN200/ALL-CAN300/CAN-CONTROL installation.
- 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:
- Connect CAN adapter CAN1 L to CAN L of ECAN02.
- Connect CAN adapter CAN1 H to CAN H of ECAN02.
- If CAN2 line need to be connected as specified in the connection scheme:
- Connect CAN adapter CAN2 L to CAN L of ECAN02.
- Connect CAN adapter CAN2 H to CAN H of ECAN02.
| Do not swap CAN L and CAN H lines.
Not all CAN adapter wires may be used in the vehicle. |
- 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.
- Connect CAN adapter positive and ground wires to the vehicle power supply lines or near FMB640 power wires.
| Do not swap power supply lines.
Make sure that voltage does not exceed 30V. |
- 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 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 program number in adapter Software date of CAN adapter must be newer than connection scheme date.
CAN adapter Software date can be checked:
The number of digits required to enter 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 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 command:
lvcansetprog X
Command example: lvcansetprog 11434
SMS response: LVCAN ProgNum: 11434
If during SMS command FMB640 was in 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 program number is entered press 
Save to device button that saves the entered program number into FMB640.
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, ALL-CAN300 back
For
ALL-CAN300
LV-CAN200
3 digit
|
For
ALL-CAN300
LV-CAN200
4 digit
|
For
LV-CAN200
CAN-CONTROL
5 digit
|
1. Hold SWITCH down until LED stars blinking.
|
| 2. Release the SWITCH.
|
| 3. 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.
|
| 4. Release the SWITCH, then LED starts blinking and counting second digit of program number. To stop counter, push SWITCH.
|
| 5. Release the SWITCH, then LED starts blinking and counting third digit on program number. To stop counter, push SWITCH.
|
|
|
6. Release the SWITCH, then LED starts blinking and counting fourth digit on program number. To stop counter, push SWITCH.
|
|
|
7. Release the SWITCH, then LED starts blinking and counting fifth digit on program number. To stop counter, push SWITCH.
|
| All Devices
|
8. Release SWITCH, if programming is successful LED will blink 10 times.
|
Send data with 0, if 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) parameters values or reset values to 0. When ignition is off, CAN Adapter I/O parameters values sent to 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 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
|
| lvcanfaultcodes
|
Read DTC fault codes
|
Yes
|
| CAN-CONTROL specific commands
|
| lvcanopenalldoors
|
Open [unlock] all doors
|
Yes
|
| lvcanclosealldoors
|
Close [lock] all doors
|
Yes
|
| lvcanopentrunk
|
Open [unlock] trunk
|
Yes
|
| lvcanturninglights
|
One flash of all turn lights ordered trough accidental / blinking turn light switch
|
Yes
|
CAN Adapter State Flags
CAN Adapters receive data about the states of various systems within the vehicle, and send them as flags to FMB640. FMB640 device stores these flags in hexadecimal format, as one variable. Below is a list of kept flags and how to retrieve them.
The full list of state flags is stored only by:
Only security state flags are stored by:
| 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
0x10 – Battery not charging
0x20 – AIRBAG
0x40 – EPS (Electric power steering)
0x80 – ESP (Electronic Stability Program)
Byte1:
0x01 – CHECK ENGINE
0x02 – Lights failure
0x04 – Low tire pressure
0x08 – Wear of brake pads
0x10 – Warning
0x20 – ABS
0x40 – Low Fuel
0x80 – Maintenance required
Byte2:
0x01 – ESP
0x02 – Glow plug indicator
0x04 – FAP
0x08 – Electronics pressure control
0x10 – Parking lights
0x20 – Dipped headlights
0x40 – Full beam headlights
0x80 – Front foglights
Byte3:
0x01 – Ready to drive
0x02 – Cruise control
0x04 – Automatic Retarder
0x08 – Manual retarder
0x10 – Air Conditioning
0x20 – Rear foglights
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
0x40 – Pouring chemicals turned on
0x80 – Conveyor belt turned on
Byte4:
0x01 – Salt spreaders drive wheel turned on
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
0x20 – Liquid pump turned on
0x40 – Light signal turned on
|
| Security state flags
|
8
|
Byte0 (LSB):
0x01 – CAN1 not connected, require connection
0x02 – CAN1 not connected, require connection
0x03 – CAN1 connected
0x04 – CAN2 not connected, require connection
0x08 – CAN2 not connected, require connection
0x0C – CAN2 connected
0x10 – CAN3 not connected, require connection
0x20 – CAN3 not connected, require connection
0x30 – CAN3 connected
Byte2:
0x04 – Battery charging
0x08 – Charging cable connected
0x10 – Vehicle working mode, 1- business mode, 0 - private mode
0x20 – Bit appears when any operate button in car was put. This bit is reset if the button is released
0x40 – Bit appears when immobilizer is in service mode
0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car
Byte3:
0x01 – The key is in ignition lock
0x02 – Ignition on
0x04 – Dynamic ignition on
0x08 – Webasto
0x10 – Car closed
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
Byte4:
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
Byte5:
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
Byte6:
– Low nibble (mask 0x0F value)
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
|
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. The 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 the program number displayed as 3-digit program number:
Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of the program number:
