FM11YX with CAN adapter ALL-CAN300

1.1 Purpose of Can Adapter ALL-CAN300

ALL-CAN300 is used to listening data from any type of transport: light vehicles, Trucks,
busses, agriculture and other special transport. With this adapter FM11YX device is able to
collect and send vehicle data.

FM11YX shares the same USB port for connecting adapter and configuring device with PC.
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)

1.2 ALL-CAN300 program number selection

ALL-CAN300 must be set to program number which depends on vehicle model.

Needed program number is always written on 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.

1.2.1 ALL-CAN300 program number configuration via SMS command

ALL-CAN300 program number can be set remotely, using SMS command:
lvcansetprog X
X is new program number value.
 1.2.2 Selecting 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 succeeded LED will blink 10 times

Figure 3 Adapter signaling led

1.3 Connecting FM11YX with Can adapter

Connect USB Plug to FM11YX device, connect ALL-CAN300 to other end of the cable.
Connect ALL-CAN300 Pin 1 and Pin 2 to cars CAN bus. CAN interface location of the
supported vehicle is described on mounting scheme.
Connect car power supply lines to Pin 3 positive, Pin 4 Negative.
Pins 9,10 connection is optional it depends on exact car model.
For exact pinout see sticker on Can adapter.

2
 Figure 4 ALL-CAN300 Adapter connection cable pinout

Attention! Ordered 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.

3
 1.4 SIMPLE-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.

After power supply connecting, LED shines continuously. It means that device awaits
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.

4
1.5 FM11YX Configuration

FM11YX shares the same USB port for connecting ALL-CAN300 adapter and configuring
device with PC.
FM11YX can be configured using configurator in LVCAN section (Figure 7).

To configure CAN data:

1. In car, connect ALL-CAN300 to CAN bus and to the FM11YX device (Figure 5), wait 10
seconds. Note, that car engine must be started.
2. Disconnect ALL-CAN300 from FM11YX, and connect PC USB cable to FM11YX Device
(Figure 6). It is very important not to disconnect FM11YX from power source, because
then all CAN data will be lost.

Connection
USB
ALL-CAN300 cable FM11YX


Figure 5 Connect adapter ALL-CAN300 to FM11YX

USB Cable
USB
PC FM11YX

Figure 6 Connect FM11YX to PC and configure

CAN bus data which can be read from your car is shown in “ ALL-CAN300supported cars”
document.

Configuration CAN data – user can select which CAN data can be read from ALL-CAN300
need to be sent to server without connection to adapter. Please note that parameters depend
on vehicle manufacturer and vehicle model. Please for further information check “ ALL-
CAN300supported 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.

5
 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 FM11YX 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, FM11YX
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,
FM11YX generates event by “Data Acquisition Type” settings. Figure 58 show example of
FM11YX CAN configuration.

Averaging constant – it is an CAN event delay parameter. In some applications there is no

need to generate events on every CAN bus date range enter/exit immediately. Sometimes it is
necessary to wait some time interval before event generating. Averaging constant allows setting
CAN event delay (averaging). If CAN value is entering or leaving predefined range, it must have
same value for Averaging constant time.

Figure 7 Configurator example

Available CAN Bus IO parameters and configuration can be found in Configurators CAN
tab (Figure7) and in next chapter “Parameters ID”.

6
 1.6 Parameters ID
When no I/O element is enabled, AVL packet comes with GPS information only. After
enabling I/O element(s) AVL packet along with GPS information contains current value(s) of
enabled I/O element. AVL packet decoding is described in “FM11YX Protocols” document. List of
available CAN bus data, parameter size, ID and value range you can find in table 1.1.

Table 1.1 ACQUIRED PARAMETRS IO IDs

Param Size Measurement a1 Remarks
Property Input Param IO ID
index (Bytes) units
ALL-CAN300 29 4 100 - -
Program number
Module ID 30 8 101 - -
Engine Work Time 31 4 102 min 1
Engine Work Time 32 4 103 min 1
(counted) *
Total Mileage 33 4 87 meters 1
Total Mileage 34 4 105 meters 1
(counted) *
Fuel Consumed 35 4 83 Ltr * 10 0.1
Fuel Consumed 36 4 107 Ltr * 10 0.1
(counted) *
Fuel Level [%] 37 1 89 proc.* 1
Fuel Level [liters] 38 2 84 Ltrs * 10 0.1
Fuel Rate 39 2 110 (Ltrs * 10) / h 0.1
AdBlue Level (percent) 40 1 111 proc. 1
AdBlue Level (liters) 41 2 112 Ltrs * 10 0.1
Engine RPM 42 2 85 - 1
43 1 114 proc. 1 Valid
Engine Load range:
0 – 125%
o
Engine Temperature 44 1 115 C x 10 0.1 signed
Accelerator Pedal 45 1 82 proc. 1
Position
Vehicle Speed 46 1 81 km/h 1
Axle 1 Load 47 2 118 kg 1
Axle 2 Load 48 2 119 kg 1
Axle 3 Load 49 2 120 kg 1
Axle 4 Load 50 2 121 kg 1
Axle 5 Load 51 2 122 kg 1
52 4 123 - - see table
Control State Flags
1.2
Agricultural 53 8 124 - - see table
Machinery Flags 1.2
Harvesting Time 54 4 125 min 1
2
Area of Harvest 55 4 126 m 1

7
 Mowing Efficiency 56 4 127 m2/h 1
Grain Mown Volume 57 4 128 kg 1
Grain Moisture 58 2 129 proc. 1
Harvesting Drum RPM 59 2 130 - -
Gap Under Harvesting 60 1 131 mm 1
Drum
61 8 132 - see table
Security State Flags
1.2
Tacho Total Vehicle 62 4 133 m 1
Distance
Trip Distance 63 4 134 m 1
Tacho Vehicle Speed 64 2 135 km/h 1
Tacho Driver Card 65 1 136 - - see table
Presence 1.2
66 1 137 - - see table
Driver1 States
1.2
67 1 138 - - see table
Driver2 States
1.2
Driver1 Continuous 68 2 139 min 1
Driving Time
Driver2 Continuous 69 2 140 min 1
Driving Time
Driver1 Cumulative 70 2 141 min 1
Break Time
Driver2 Cumulative 71 2 142 min 1
Break Time
Driver1 Duration Of 72 2 143 min 1
Selected Activity
Driver2 Duration Of 73 2 144 min 1
Selected Activity
Driver1 Cumulative 74 2 145 min 1
Driving Time
Driver2 Cumulative 75 2 146 min 1
Driving Time
Driver1 ID High 76 8 147 ASCII
Driver1 ID Low 77 8 148 ASCII
Driver2 ID High 78 8 149 ASCII
Driver2 ID Low 79 8 150 ASCII
o
Battery Temperature 80 2 151 C x 10 0.1 signed
Battery Level (percent) 81 1 152 proc. 1
NOTE:
„Total Fuel Used“ is sent to server multiplied by 10.
Example: if value was 150.5 liters, „1505“ will be sent to server.

*- Fuel consumed (counted), Total mileage (counted), Engine Work Time (counted) are
parameters, which are counted after ALL-CAN 300 is connected to CAN bus. For example:

8
Total mileage is 10000 (from CAN), ALL-CAN300 starts monitoring this parameter and at the
beginning Total mileage (counted) is 0. Vehicle drives 100 km: Total mileage increases to
10100km, Total milage (counted) is 100km. Same goes for other parameters.

Table 1.2 ALLCAN300 IO element values

Idx Description Size, AVL Value bitmasks
Bytes ID
52 Control state flags 4 123 Byte0 (LSB):
0x01 – STOP
0x02 – Oil pressure / level
0x04 – Coolant liquid temperature / level
0x08 – Handbrake system
0x10 – Battery charging
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
53 Agricultural 8 124 Byte0 (LSB):
machinery flags 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

9
 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 chasis
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
61 Security state flags 8 132 Byte0 (LSB):

10
 0x20 – bit appears when any operate button
in car was put
0x40 – bit appears when immobilizer 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 – revers 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
65 Tachograph driver 1 136 0x00 – No driver card
card presence 0x01 – Driver1 card presence
0x02 – Driver2 card presence
0x03 – Driver1 and driver2 cards present
66 Driver 1 states 1 137 0xX0 – break/rest
67 Driver 2 states 1 138 0xX1 – availability
0xX2 – work

11
 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

1.7 SMS Configuration

All ALL-CAN300 IO elements can be configured remotely via SMS command. First ID number is
always ‘2’, seconds and third ID numbers refers to specific ALL-CAN300 IO element (table 1.2).
And the last ID number refers to sections – Property; Generation Type; Low level, High level and
Averaging Constant (Table 1.3).
Here’s example:
ID 2013 – configures Accelerator Pedal position parameter “High Level”.

Table 1.2 ALL-CAN300 IO elements SMS configuration Ids range

ALL-CAN300 IO Element
Parameter Ids range
Speed 2000-2004
Accelerator pedal position 2010-2014
Total fuel used 2020-2023
Fuel level (liters) 2030-2034
Engine RPM 2040-2044
Total mileage 2050-2053
Fuel level (proc.) 2060-2064
Program number 2070-2073
Module ID 2080-2083
Engine Work Time 2090-2093
Engine Work Time (counted) 2100-2103
Total Mileage (counted) 2110-2113
Fuel Consumed (counted) 2120-2123
Fuel Rate 2130-2134
AdBlue Level (percent) 2140-2144
AdBlue Level (liters) 2150-2154
Engine Load 2160-2164
Engine Temperature 2170-2174
Axle 1 Load 2180-2184
Axle 2 Load 2190-2194
Axle 3 Load 2200-2204
Axle 4 Load 2210-2214
Axle 5 Load 2220-2224
Control State Flags 2230-2233
Agricultural Machinery Flags 2240-2243
Harvesting Time 2250-2253
Area of Harvest 2260-2263

12
 Mowing Efficiency 2270-2274
Grain Mown Volume 2280-2283
Grain Moisture 2290-2294
Harvesting Drum RPM 2300-2304
Gap Under Harvesting Drum 2310-2314
Security State Flags 2320-2323
Tachograph Total Vehicle Distance 2330-2333
Trip Distance 2340-2343
Tachograph Vehicle Speed 2350-2354
Tachograph Driver Card Presence 2360-2363
Driver1 States 2370-2373
Driver2 States 2380-2383
Driver1 Continuous Driving Time 2390-2393
Driver2 Continuous Driving Time 2400-2403
Driver1 Cumulative Break Time 2410-2413
Driver2 Cumulative Break Time 2420-2423
Driver1 Selected Activity Duration 2430-2433
Driver2 Selected Activity Duration 2440-2443
Driver1 Cumulative Driving Time 2450-2453
Driver2 Cumulative Driving Time 2460-2463

Table 1.3 ALL-CAN300 IO parameters configuration

Parameter Parameter name Available values
ID
2xx0 Priority 0 – IO element disabled
1 – Low priority
2 – High priority
3 – Panic priority
2xx1 Generation type 0 – Event on exit
1 – Event on entrance
2 – Event on both
3– Monitoring
4 – Hysteresis
5 – On change
2xx2 Low level See table 9.4 – Allowed
2xx3 High Level Values
2xx4 Averaging Constant From 0 to 232

1.8 CAN Program Number request by SMS

CAN program number can be obtained via SMS:

SMS Text: “ lvcangetprog ”

13
 1.9 Get ALL-CAN info by SMS

Full ALL-CAN information via SMS:

SMS Text: “ lvcangetinfo”
Response:
Program number, SW creation date, SW revision, Kern version, Option and its ID, Simple tacho
configuration.

Clear counted parameters value

It is possible to clear Total Mileage (counted), Engine Work Time (counted), Fuel Consumed
(counted) parameters with following SMS command.
SMS text: ”lvcanclear #”
Possible values of #:
0 – Engine work time (counted);
1 – Fuel Consumed (counted);
2 – Vehicle Mileage (counted);

1.10 References
1. ALL-CAN300 supported vehicle list;
2. Vehicle mounting scheme.

1.11 LV -CAN200/ALLAN300 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 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:

14
Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 need to add "1" before
it:

15