FM1100 User Manual

V5.17
*This version is suitable for device with universal FM11YX firmware
v.01.27.xx and later versions
 Table of contents
1 INTRODUCTION .......................................................................................................................... 7
1.1 ATTENTION ............................................................................................................................. 7
1.2 INSTRUCTIONS OF SAFETY ........................................................................................................... 7
1.3 LEGAL NOTICE ......................................................................................................................... 8
1.4 ABOUT DOCUMENT ................................................................................................................... 8
2 BASIC DESCRIPTION.................................................................................................................... 8
2.1 PACKAGE CONTENTS.................................................................................................................. 8
2.2 BASIC CHARACTERISTICS ............................................................................................................. 9
2.3 TECHNICAL FEATURES .............................................................................................................. 10
2.4 ELECTRICAL CHARACTERISTICS .................................................................................................... 12
2.5 ABSOLUTE MAXIMUM RATINGS ................................................................................................. 13
3 CONNECTION, PINOUT, ACCESSORIES ...................................................................................... 13
3.1 HOW TO INSERT SIM CARD INTO FM1100 DEVICE: ........................................................................ 13
3.2 INSTALLING FM1100 DRIVERS .................................................................................................. 15
3.3 NAVIGATE LED ...................................................................................................................... 16
3.4 STATUS LED ......................................................................................................................... 16
3.5 SOCKET 25 ......................................................................................................................... 16
3.6 USB ................................................................................................................................... 17
3.7 ACCESSORIES ......................................................................................................................... 18
4 FIRMWARE ............................................................................................................................... 21
4.1 UPDATING FIRMWARE USING USB CABLE ..................................................................................... 21
5 OPERATIONAL BASICS .............................................................................................................. 23
5.1 OPERATIONAL PRINCIPALS ........................................................................................................ 23
5.2 SLEEP MODES ........................................................................................................................ 23
5.2.1 Sleep mode ................................................................................................................ 23
5.2.2 Deep Sleep mode........................................................................................................ 23
5.3 VIRTUAL ODOMETER ............................................................................................................... 24
5.4 FEATURES ............................................................................................................................. 24
5.4.1 Scenarios ................................................................................................................... 24
5.4.2 Trip ............................................................................................................................ 26
5.4.3 Geofencing................................................................................................................. 26
5.4.4 iButton list ................................................................................................................. 26
5.5 CONFIGURATION ............................................................................................................... 26
5.6 CONFIGURATOR ..................................................................................................................... 26
5.7 READ RECORDS* .................................................................................................................... 29
5.8 SYSTEM SETTINGS ................................................................................................................... 30
5.9 RECORDS SETTINGS ................................................................................................................. 32
5.10 GSM SETTINGS, GPRS PART ................................................................................................... 33
5.11 GSM SETTINGS, SMS PART .................................................................................................... 33
5.12 GSM SETTINGS, OPERATOR LIST*............................................................................................. 34
5.13 DATA ACQUISITION MODE SETTINGS ......................................................................................... 36
5.14 FEATURES SETTINGS .............................................................................................................. 40
5.14.1 Scenarios settings..................................................................................................... 41
5.14.2 Trip settings ............................................................................................................. 42
5.14.3 Geofencing settings .................................................................................................. 44
5.14.4 SMS events............................................................................................................... 46
5.14.4.1 SMS events configuration ................................................................................................ 48
5.15 I/O SETTINGS ...................................................................................................................... 51
5.15.1 Monitoring ............................................................................................................... 54
5.15.2 Event Generating ..................................................................................................... 54
5.15.3 Hysteresis................................................................................................................. 55

2
6 SMS COMMAND LIST................................................................................................................ 55
6.1 SMS COMMAND LIST .............................................................................................................. 56
6.1.1 getstatus.................................................................................................................... 57
6.1.2 getweektime .............................................................................................................. 57
6.1.3 getops........................................................................................................................ 58
6.1.4 getcfgtime ................................................................................................................. 58
6.1.5 getgps........................................................................................................................ 58
6.1.6 ggps........................................................................................................................... 58
6.1.7 getver ........................................................................................................................ 58
6.1.8 getinfo ....................................................................................................................... 59
6.1.9 getio .......................................................................................................................... 59
6.1.10 readio #.................................................................................................................... 60
6.1.11 setdigout ## Y1 Y2.................................................................................................... 60
6.1.12 setdigoutX Z Y .......................................................................................................... 60
6.1.13 getparam ####......................................................................................................... 60
6.1.14 setparam #### ......................................................................................................... 60
6.1.13. getparam 1271 X/212 X........................................................................................... 60
6.1.14. setparam 1271 X/212 X ........................................................................................... 60
6.1.15 readops # ................................................................................................................. 60
6.1.16 flush #,#,#,#,#,#,# ..................................................................................................... 61
6.1.17 sn # .......................................................................................................................... 61
6.1.18 setkey # # ................................................................................................................. 61
6.1.19 delkey #.................................................................................................................... 61
6.1.20 banlist ...................................................................................................................... 62
6.1.21 crashlog ................................................................................................................... 62
6.1.22 faultcodes ................................................................................................................ 62
6.1.23 dtcinfo ..................................................................................................................... 63
7 DEBUG MODE........................................................................................................................... 63
8 PARAMETER LIST ...................................................................................................................... 64
8.1 PARAMETERS VALUE TYPES........................................................................................................ 64
8.2 SYSTEM PARAMETERS .............................................................................................................. 64
8.2.1 Sleep Mode (ID=1000) ................................................................................................ 64
8.2.2 Sleep timeout (ID=200) ............................................................................................... 64
8.2.3 Analog Input value range (ID=1001) ........................................................................... 64
8.2.4 Stop Detection Source (ID=1002) ................................................................................ 64
8.2.5 Static Navigation (ID=1003)........................................................................................ 65
8.2.6 Ignition Source (ID=1004) ........................................................................................... 65
8.2.7 Ignition detection (ID=1920) ....................................................................................... 66
8.2.8 Ignition detection timeout (ID=1921) .......................................................................... 66
8.2.9 Power Voltage High Level (ID=1005) ........................................................................... 66
8.2.10 Power Voltage Low Level (ID=1006) .......................................................................... 66
8.2.11 Records Saving/Sending (ID=201) ............................................................................. 67
8.2.12 GNSS System (ID=202) .............................................................................................. 68
8.2.13 NSS fix Timeout (ID=1007) ........................................................................................ 68
8.2.14 Enable NTP – network time synchronization (ID=1008).............................................. 68
8.2.15 GNSS fix timeout for the time synchronization (ID=1007) .......................................... 68
8.3 RECORDS PARAMETERS ............................................................................................................ 68
8.3.1 Sorting (ID=1010) ....................................................................................................... 68
8.3.2 Active Data Link Timeout (ID=1011) ............................................................................ 68
8.3.3 Server Response Timeout (ID=1012)............................................................................ 69
8.4 GSM PARAMETERS ................................................................................................................. 69
8.4.1 GPRS content activation (ID=1240) ............................................................................. 69
8.4.2 APN Name (ID=1242) ................................................................................................. 69
8.4.3 APN username (ID=1243) ........................................................................................... 69
8.4.4 APN Password (ID=1244) ............................................................................................ 70
8.4.5 Domain (ID=1245) ...................................................................................................... 70

3
 8.4.6 Target Server Port (ID=1246) ...................................................................................... 70
8.4.7 Protocol (ID=1247) ..................................................................................................... 70
8.4.8 Always online (ID=1248) ............................................................................................. 70
8.4.9 SMS Login (ID=1252) .................................................................................................. 71
8.4.10 SMS Password (ID=1253) .......................................................................................... 71
8.4.11 SMS data sending settings (ID=1250) ........................................................................ 71
8.4.12 SMS Data send week time schedule (ID=1273) .......................................................... 71
8.4.13 Authorized phone numbers (ID=1260-1269) .............................................................. 71
8.4.14 SMS Event PreDefined Numbers (ID=150-159) .......................................................... 72
8.4.15 Operator List (ID=1271 X) ........................................................................................ 72
8.4.16 Black Operator list (ID= 1272 X) ................................................................................ 72
8.5 DATA ACQUISITION MODES PARAMETERS..................................................................................... 72
8.5.1 Home Network GSM operator code “Vehicle on STOP” parameters ............................. 72
8.5.1.1 Min Period (ID=1540) ........................................................................................................ 72
8.5.1.2 Min Saved Records (ID=1543) ............................................................................................ 73
GPRS Week Time (ID=1545) .......................................................................................................... 73
8.5.1.3 Send Period (ID=1544) ....................................................................................................... 73
8.5.1.4 GPRS Week Time (ID=1545) ............................................................................................... 73
8.5.2 Home Network GSM operator code “Vehicle MOVING” parameters ............................ 73
8.5.2.1 Min Period (ID=1550) ........................................................................................................ 73
8.5.2.2 Min Distance (ID=1551) ..................................................................................................... 74
8.5.2.3 Min Angle (ID=1552).......................................................................................................... 74
8.5.2.4 Min Speed (ID=1556) ......................................................................................................... 75
8.5.2.5 Min Speed Source (ID=1557) ............................................................................................. 75
8.5.2.6 Min Saved Records (ID=1553) ............................................................................................ 75
8.5.2.7 Send Period (ID=1554) ....................................................................................................... 76
8.5.2.8 GPRS Week Time (ID=1555) ............................................................................................... 76
8.5.3 Roaming Network GSM operator code “Vehicle on STOP” parameters ........................ 76
8.5.3.1 Min Period (ID=1560) ........................................................................................................ 76
8.5.3.2 Min Saved Records (ID=1563) ............................................................................................ 76
8.5.3.3 Send Period (ID=1564) ....................................................................................................... 76
8.5.3.4 GPRS Week Time (ID=1565) ............................................................................................... 77
8.5.4 Roaming Network GSM operator code “Vehicle MOVING” parameters ....................... 77
8.5.4.1 Min Period (ID=1570) ........................................................................................................ 77
8.5.4.2 Min Distance (ID=1571) ..................................................................................................... 77
8.5.4.3 Min Angle (ID=1572).......................................................................................................... 77
8.5.4.4 Min Speed (ID=1576) ......................................................................................................... 77
8.5.4.5 Min Speed Source (ID=1577) ............................................................................................. 78
8.5.4.6 Min Saved Records (ID=1573) ............................................................................................ 78
8.5.4.7 Send Period (ID=1574) ....................................................................................................... 78
8.5.4.8 GPRS Week Time (ID=1575) ............................................................................................... 79
8.5.5 Unknown Network GSM operator code “Vehicle on STOP” parameters ....................... 79
8.5.5.1 Min Period (ID=1580) ........................................................................................................ 79
8.5.5.2 Min Saved Records (ID=1583) ............................................................................................ 79
8.5.5.3 Send Period (ID=1584) ....................................................................................................... 79
8.5.5.4 GPRS Week Time (ID=1585) ............................................................................................... 79
8.5.6 Unknown Network GSM operator code “Vehicle MOVING” parameters ...................... 79
8.5.6.1 Min Period (ID=1590) ........................................................................................................ 79
8.5.6.2 Min Distance (ID=1591) ..................................................................................................... 80
8.5.6.3 Min Angle (ID=1592).......................................................................................................... 80
8.5.6.4 Min Speed (ID=1596) ......................................................................................................... 80
8.5.6.5 Min Speed Source (ID=1597) ............................................................................................. 80
8.5.6.6 Min Saved Records (ID=1593) ............................................................................................ 81
8.5.6.7 Send Period (ID=1594) ....................................................................................................... 81
8.5.6.8 GPRS Week Time (ID=1595) ............................................................................................... 81
8.6 FEATURES PARAMETERS ........................................................................................................... 81
8.6.1 Green driving scenario (ID=1890)................................................................................ 81
8.6.2 Green Driving digital output control (ID=1891)............................................................ 81
8.6.3 Green Driving source (ID=1909) .................................................................................. 81
8.6.4 Max Acceleration Force (ID=1892) .............................................................................. 82
8.6.5 Max Braking Force (ID=1893) ..................................................................................... 82

4
 8.6.6 Max Cornering Force (ID=1894) .................................................................................. 82
8.6.7 Overspeeding scenario (ID=1895) ............................................................................... 82
8.6.8 Over Speeding digital output control (ID=1896) .......................................................... 82
8.6.9 Max allowed speed (ID=1897) .................................................................................... 82
8.6.10 Jamming scenario (ID=1898) .................................................................................... 83
8.6.11 Jamming digital output control (ID=1899) ................................................................. 83
8.6.12 Jamming sensitivity (ID=1900) .................................................................................. 83
8.6.13 Jamming Timeout (ID=1901)..................................................................................... 83
8.6.14 Jamming Pulse duration (ID=1902) ........................................................................... 83
8.6.15 Immobilizer scenario (ID=1903) ................................................................................ 84
8.6.16 Immobilizer digital output control (ID=1904)............................................................. 84
8.6.17 iButton list checking (ID=1905) ................................................................................. 84
8.6.18 Immobilizer ignition off timeout (ID=1906) ............................................................... 84
8.6.19 iButton detect (ID=1907) .......................................................................................... 84
8.6.20 iButton detect digital output control (ID=1908) ........................................................ 84
8.6.21 Trip (ID=1280) .......................................................................................................... 85
8.6.22 Start Speed (ID=1281)............................................................................................... 85
8.6.23 Ignition Off Timeout (ID=1282) ................................................................................. 85
8.6.24 Trip Continuous distance counting (ID=1283) ............................................................ 85
8.6.25 Remember iButton ID (ID=1284) ............................................................................... 85
8.6.26 Odometer value (ID=1285) ....................................................................................... 86
8.6.27 Geofencing ............................................................................................................... 86
8.6.27.1 Frame border (ID=1020) .................................................................................................. 86
8.6.27.2 Geofence Zone #1 Shape (ID=1030) ................................................................................. 86
8.6.27.3 Geofence Zone #1 Priority (ID=1031) ............................................................................... 86
8.6.27.4 Geofence Zone #1 Generate Event (ID=1032) ................................................................... 86
8.6.27.5 Geofence Zone #1 Longitude (X1) (ID=1033) .................................................................... 87
8.6.27.6 Geofence Zone #1 Latitude (Y1) (ID=1034) ....................................................................... 87
8.6.27.7 Geofence Zone #1 Longitude (X2) (ID=1035) .................................................................... 87
8.6.27.8 Geofence Zone #1 Latitude (Y2) (ID=1036) ....................................................................... 87
8.6.28 AutoGeofencing ....................................................................................................... 88
8.6.28.1 Enable/Disable (ID=1101) ................................................................................................ 88
8.6.28.2 Activation Timeout (ID=1102) .......................................................................................... 88
8.6.28.3 Deactivate by (ID=1100) .................................................................................................. 88
8.6.28.4 AutoGeofence event Priority (ID=1103)............................................................................ 88
8.6.28.5 AutoGeofence event generating (ID=1104) ...................................................................... 88
8.6.28.6 Radius (ID=1105) ............................................................................................................. 89
8.6.29 iButton List (ID=3500-3999 ) ..................................................................................... 89
8.7 I/O PARAMETERS ................................................................................................................... 89
8.7.1 I/O#1 property parameter (ID=1300) .......................................................................... 89
8.7.2 I/O#1 priority (ID=1301) ............................................................................................. 89
8.7.3 I/O#1 High level (ID=1302) ......................................................................................... 90
8.7.4 I/O#1 Low level (ID=1303) .......................................................................................... 90
8.7.5 I/O#1 logic operand (ID=1304).................................................................................... 90
8.7.6 I/O#1 averaging length (ID=1305) .............................................................................. 91
8.8 SMS EVENT CONFIGURATION .................................................................................................... 92
8.8.1 I/O#1 element SMS event configuration (ID=100) ....................................................... 92
8.9 LV-CAN PARAMETERS............................................................................................................. 97
8.9.1 LVCAN mode (ID=1600) .............................................................................................. 97
8.9.2 Send data with 0, if ignition is off (ID=1601)................................................................ 97
FM1100 WITH LV-CAN200 AND ALL-CAN300 CAN ADAPTERS...................................................... 97
8.10 PURPOSE OF CAN ADAPTERS LV-CAN200 AND ALL-CAN300 ....................................................... 97
8.11 LV-CAN200 AND ALL-CAN300 PROGRAM NUMBER SELECTION ..................................................... 98
8.11.1 LV-CAN200 and ALL-CAN300 program number configuration via SMS command ....... 99
8.11.2 Selecting LV-CAN200 and ALL-CAN300 program number manually.......................... 100
8.12 CONNECTING FM1100 CAN ADAPTERS ALL-CAN300 AND LV-CAN200 ....................................... 100
8.13 SIMPLE-CAN – CONTACTLESS CAN-BUS READER..................................................................... 101
8.14 FM11 CONFIGURATION ....................................................................................................... 102

5
 PARAMETERS ID ........................................................................................................................ 106
8.15 SMS CONFIGURATION ......................................................................................................... 113
8.16 CAN PROGRAM NUMBER REQUEST BY SMS ............................................................................. 116
8.17 GET CAN INFO BY SMS ....................................................................................................... 116
8.18 CLEAR COUNTED PARAMETERS VALUE ...................................................................................... 116
9 MOUNTING RECOMMENDATIONS ......................................................................................... 117
9.1 CONNECTING WIRES ............................................................................................................. 117
9.2 CONNECTING POWER SOURCE ................................................................................................. 117
9.3 CONNECTING IGNITION WIRE .................................................................................................. 117
9.4 CONNECTING GROUND WIRE .................................................................................................. 117
9.5 CONNECTING ANTENNAS ........................................................................................................ 118
9.6 MODULE INSTALLATION ......................................................................................................... 118
10 CHANGE LOG ........................................................................................................................ 119

6
1 INTRODUCTION
1.1 Attention
Do not disassemble the device. If the device is
damaged, the power supply cables are not isolated or
the isolation is damaged, before unplugging the power
supply, do not touch the device.
All wireless data transferring devices produce
interference that may affect other devices which are
placed nearby.

The device must be connected only by qualified

personnel.

The device must be firmly fastened in the predefined

location.

The programming must be performed using a second

class PC (with autonomic power supply).

The device is susceptible to water and humidity.

Any installation and/or handling during a lightning

storm are prohibited.

FM1100 has USB interface;

Please use cables provided with FM1100 device.
Teltonika is not responsible for any harm caused by
using wrong cables for PC <-> FM1100 connection.

1.2 Instructions of safety

This chapter contains information on how to operate FM1100 safely. By following these
requirements and recommendations, you will avoid dangerous situations. You must read these
instructions carefully and follow them strictly before operating the device!
The device uses a 10 V...30 V DC power supply. The nominal voltage is 12 V DC. The
allowed range of voltage is 10 V...30 V DC.
To avoid mechanical damage, it is advised to transport the FM1100 device in an impact-
proof package. Before usage, the device should be placed so that its LED indicators are visible,
which show the status of operation the device is in.
When connecting the connection (2x5) cables to the vehicle, the appropriate jumpers of
the power supply of the vehicle should be disconnected.
Before dismounting the device from the vehicle, the 2x5 connection must be disconnected.

7
 The device is designed to be mounted in a zone of limited access, which is inaccessible for
the operator. All related devices must meet the requirements of standard EN 60950-1.
The device FM1100 is not designed as a navigational device for boats.

1.3 Legal Notice

Copyright © 2012 Teltonika. All rights reserved. Reproduction, transfer, distribution or
storage of part or all of the contents in this document in any form without the prior written
permission of Teltonika is prohibited.
Other products and company names mentioned here may be trademarks or trade names
of their respective owners.
The manufacturer reserves the right to make changes and/or improvements at any time in
design, functionality, parameters and electrical characteristics without any prior notice and
without incurring obligations.

1.4 About document

This document contains information about the architecture, possibilities, mechanical
characteristics, and configuration of the FM1100 device.
Acronyms and terms used in document
PC – Personal Computer.
GPRS – General Packet Radio Service
GNSS – Global Navigation Satellite System
GSM – Global System for Mobile Communications
SMS – Short Message Service
AC/DC – Alternating Current/Direct Current
I/O – Input/Output
Record – AVL data stored in FM1100 memory. AVL data contains GNSS and I/O information
AVL packet - data packet that is being sent to server during data transmission. AVL packet
contains from 1 to 50 records.

2 BASIC DESCRIPTION
FM1100 is a terminal with GNSS and GSM connectivity, which is able to determine the
object’s coordinates and transfer them via the GSM network. This device is perfectly suitable for
applications, which need location acquirement of remote objects. It is important to mention that
FM1100 has additional inputs and outputs, which let you control and monitor other devices on
remote objects. FM1100 also has a USB port for device status log output and entering
configurations.

2.1 Package contents 1

The FM1100 device is supplied to the customer in a cardboard box containing all the
equipment that is necessary for operation. The package contains:
FM1100 device;
Input and output power supply cable with a 2x5 connection pins;
GNSS antenna;

1
Package content depends on Order Code, and can be customized by customer needs.

8
 GSM antenna;
USB cable;
A card containing URL to download FM1100 device drivers and Configurator software.

2.2 Basic characteristics

GSM / GPRS features:
• Teltonika TM11Q quad band module (GSM 850 / 900 / 1800 / 1900 MHz);
• GPRS class 10;
• SMS (text, data).

GNSS features (3 possible GNSS modules):

• TG1000, 33 channel receiver;
• Up to -165 dBm sensitivity.

Hardware features:
• Cortex®-M3 processor;
• 1 MB internal Flash memory (16 MB optional);
• Built-in movement sensor.

Interface features:
• Power supply: 10 ÷ 30V;
• USB port;
• 3 digital inputs;
• 1 analog input;
• 2 open collector digital outputs;
• 1Wire® temperature sensor
• 1Wire® iButton
• LEDs indicating device status.

Special features:
• Any element event triggers (external sensor, input, speed, temperature, etc.);
• Highly configurable data acquisition and sending;
• Multiple Geo-fence areas;
• Sleep mode;
• Deep sleep mode;
• Configurable scenarios available;
• Real-time process monitoring;
• Authorized number list for remote access;
• Firmware update over GPRS or USB port;
• Configuration update over GPRS, SMS or USB port;
• TCP/IP or UDP/IP protocol support;
• 8000 record storing.
• Radio frequency jamming detection.

9
 Optional features (enable with FM1100M):
• The memory can save up to 50,000 records;
• Offline working mode;
• Records exporting using USB;

Overvoltage protection (new devices with order code FM1100 Vxxxxx):

Description Voltage Duration

Normal operation 10-30V Unlimited
Protection turns on, device turns off. 34V Unlimited
Maximum voltage <70V Unlimited
Maximum voltage impulse 90V 5 mili seconds

2.3 Technical features

Part name Physical specification Technical details

Navigation LED LED Power supply 10...30 V DC
2W Max
Modem LED LED Energy consumption:
GNSS GNSS antenna connector MCX GPRS: 150 mA r.m.s Max.,
Nominal: average 65 mA r.m.s,
GSM antenna connector SMA
GNSS Sleep: average 28 mA,
GSM female outer shell, female inner
Deep Sleep: average less than
pin
4 mA2
Tyco Micro MATE-N-LOK™ Operation temperature:
Socket 2x5
4-794628-0 or similar -25⁰C ... +55⁰C
Storage temperature:
-40⁰C ... +70⁰C
USB Mini USB socket Storage relative humidity 5 ... 95 % (no
condensation)
Table 1. FM1100 specifications

2
When in Deep Sleep mode no data storing and sending is activated.

10
Figure 1 FM1100 view & dimensions (tolerance ±2mm)

11
 2.4 Electrical characteristics
VALUE
Min. Typ. Max. Unit
CHARACTERISTIC DESCRIPTION

Supply Voltage:
Supply Voltage (Recommended Operating Conditions) 10 30 V
Digital Output (Open Drain grade):
Drain current (Digital Output OFF) 120 uA
Drain current (Digital Output ON,
300 mA
Recommended Operating Conditions)
Static Drain-Source resistance (Digital
300 mOhm
Output ON)
Digital Input:
Input resistance (DIN1, DIN2, DIN3) 15 kOhm
Input Voltage (Recommended Operating Supply
0 V
Conditions) voltage
Input Voltage threshold (DIN1) 7,5 V
Input Voltage threshold (DIN2, DIN3) 2,5 V
Analog Input:
Input Voltage (Recommended Operating
0 10 V
Conditions), Range1
Input resistance, Range1 120 kOhm
Measurement error 1,43 %
Additional error ±12 mV
Input Voltage (Recommended Operating
0 30 V
Conditions) Range2
Input resistance, Range2 146,7 kOhm
Measurement error 1,75 %
Additional error ±36 mV
Output Supply Voltage 1-Wire:3
Supply Voltage 3,3 3,6 V
Output inner resistance 7 Ohm
Output current (Uout > 3.0V) 30 mA
Short circuit current (Uout = 0) 130 mA

3
1-wire Supply voltage PIN is dedicated for 1-wire devices ONLY, do not use it for any other purpose.

12
 Note: Analog Input error margin can increase if temperature varies. If Analog
input is not connected FM1100 will still measure certain numbers and it
cannot be 0. This measurement is influenced by hardware components.

2.5 Absolute Maximum Ratings

VALUE
Min. Typ. Max. Unit
CHARACTERISTIC DESCRIPTION
Supply Voltage (Absolute Maximum Ratings) -32 32 V
Drain-Source clamp threshold voltage (Absolute
36 V
Maximum Ratings), (Idrain = 2mA)
Digital Input Voltage (Absolute Maximum Ratings) -32 32 V
Analog Input Voltage (Absolute Maximum Ratings) -32 32 V

3 CONNECTION, PINOUT, ACCESSORIES

3.1 How to insert SIM card into FM1100 device:


Gently open FM1100 case using screwdrivers

13
  
Remove FM1100 case Insert SIM card as shown

 Step for FM1100M+2SIM version:

Insert SIM cards as shown. Lower slot is for
SIM 1, upper slot is for SIM2.

 
Attach top housing cover Device is ready

14
3.2 Installing FM1100 drivers
Software requirements:
• Operating system 32-bit and 64-bit: Windows XP with SP3 or later, Windows Vista,
Windows 7.
• MS .NET Framework V3.5 or later (http://www.microsoft.com).

Drivers:
Please download Virtual COM Port drivers from Teltonika website:
http://avl1.teltonika.lt/downloads/FM11YX/vcpdriver_v1.3.1_setup.zip
Installing drivers:
Extract and run VCPDriver_V1.3.1_Setup.exe. This driver is used to detect FM1100 device
connected to the computer. Click 'Next' in driver installation window (figures below):

Figure 2 Driver installation window

This will launch device driver installation wizard. In the following window click ‘Next’
button again:

Figure 3 Driver installation window

Setup will continue installing drivers and will display a window about successful process at
the end. Click 'Finish' to complete setup:

15
 Figure 4 Driver installation window

You have now installed drivers for FM1100 device successfully.

3.3 Navigate LED

Behaviour Meaning
Permanently switched on GNSS signal is not received
Blinking every second Normal mode, GNSS is working
Off GNSS is turned off because:
• Deep sleep mode
Or
• GNSS antenna short circuited

3.4 Status LED

Behaviour Meaning
Blinking every second Normal mode
Blinking every 2 seconds Deep sleep mode
Blinking fast for a short time Modem activity
Blinking fast constantly Boot mode
Off • Device is not working
Or
• Device firmware being flashed

3.5 Socket 25

DIN 1 (IGNITION) 5 10 Ucc_DALLAS

DIN 2 4 9 DIN 3
OUT 1 3 8 DATA_DALLAS
OUT 2 2 7 AIN 1
VCC (1030)V DC(+) 1 6 GND(VCC(1030)V DC)(-)
Figure 5 2x5 socket pinout

16
Pin
Pin Name Description
Nr.
1 VCC (1030)V DC (+) Power supply for module. Power supply range (10...30) V DC
2 OUT 2 Digital output. Channel 2. Open collector output. Max. 300mA.
3 OUT 1 Digital output. Channel 1. Open collector output. Max. 300mA.
4 DIN 2 Digital input, channel 2
5 DIN 1 Digital input, channel 1 DEDICATED FOR IGNITION INPUT
6 GND(VCC(1030)V DC)(-) Ground pin. (1030)V DC ( ― )
7 AIN 1 Analog input, channel 1. Input range: 0-30V/0-10V DC
8 DATA_DALLAS Data channel for Dallas 1-Wire® devices
9 DIN 3 Digital input, channel 3
10 Ucc_DALLAS + 3,8 V output for Dallas 1-Wire® devices. (max 20mA)
Table 2. Socket 2x5 pinout description

3.6 USB
Mini USB connector

Figure 6 Mini USB type B connector

FM1100 connected to PC creates an STM Virtual COM Port, which can be used as a system
port (to flash firmware and configure the device):

Figure 7 COM-Ports

17
3.7 Accessories

Note: Teltonika does not provide any additional equipment like panic buttons,
door sensors or others.

1 – Wire devices
One of the realized features FM1100 is 1-Wire® data protocol, which enables connection
of thermometer (DS1820, DS18S20 and DS18B20) and I-Button type: DS1990, DS1991, DS1994,
DS1993, DS1992, DS1982, DS1995, DS1985, DS1996, DS1986, DS1971, DS1963L, DS1921, DS1973,
DS1904, DS1972, DS1977, DS2413, DS1922/1923, DS1990A, DS1982U, DS1985U, DS1986U
(Figures 8 and 9 show FM1100 and 1-wire® device connection schemes).

Left row of pins 1

U1 Right row of pins
J1
1W. PWR 2
1
(FM1100 – pin10) 3
J3
4
Vpp (+5 Volts DC) –
1W. Data
2 power source for
(FM1100 – pin8) J2 1
external digital
1
2
sensor
GND
3 Output from external
(FM1100 – pin6) 2
digital sensor
Digital Input 4
Figure 8 Digital thermometer DS1820 and TTJ100 connection scheme

18
 Figure 9 I-Button DS1990A connection scheme

Fuel Tank sensors

A fuel tank level sensor exists in most cars, which shows the
approximate fuel level in the driver’s indicator panel. It is possible
to connect FM1100 Analog input to it (if sensor returns analogue
signal proportional to fuel level). Figure shows the connection
scheme to the FM1100 and fuel tank sensor. After the connection
to the tank fuel level sensor, calibration is needed. Calibration is
needed because most fuel tank sensors are not linear. Calibration
is performed by measuring voltage dependence on volume of fuel
in tank.
Figure 10 Fuel sensor scheme

Alarm buttons, door sensors, etc.

Alarm buttons, door sensors, ignition, etc. return two states: high or low voltage. Digital
inputs are used to read this information. Figure below shows how to connect alarm button, door
sensor, etc.

Figure 11 Panic button connection

19
 In cases when sensor output signal is negative, an additional relay has to be installed to
convert negative signal to positive.

Figure 12 Inverting relay connection

Immobilizer relay
When connected as shown below, FM1100 disables engine starter when output is ON.
More details about relays can be found below

Figure 13 Immobilizer relay connection

Relays
An ordinary automotive relay is used to invert input signal or to immobilize engine starter.
Note, that they are available as 12 V or 24 V.

Figure 14 Automotive relay pinout

20
4 FIRMWARE
4.1 Updating firmware using USB cable

FM1100 functionality is always improving, new firmware versions are developed.

Current module firmware version can be retrieved from Configurator.

Connect FM1100 to PC with the USB cable. Launch “Firmware Updater”, select COM port
to which device is connected, click connect, and when IMEI and Firmware version fields are filled,
start the update. Device needs some time to send IMEI and Firmware version, so do not be afraid
if IMEI will not show up immediately, disconnect and after 1-2 minutes try to connect again.
When starting update device will open link with updater. With link open device downloads
firmware and starts installing. Wait thru all these screens as in Figure 16 for firmware to update.
Update process may take up to several minutes.

Figure 15. FM1100 firmware updater screen

21
 Figure 16. Firmware updating processes

When you see a green table like in Figure 16, it means that the firmware is flashed to
FM1100 successfully. You may now close the update window and start using your FM1100
device.

22
5 OPERATIONAL BASICS
5.1 Operational principals
FM1100 module is designed to acquire records and send them to the server. Records
contain GNSS data and I/O information. Module uses GNSS receiver to acquire GNSS data and is
powered with four data acquire methods: time-based, distance-based, angle-based and speed-
based method. Note, that if FM1100 loses connection to GNSS satellites, it continues to make
records, however coordinate in these records remains the same (last known coordinate).
Method’s details are described in section 5.13. All data is stored in flash memory and later can be
sent via GPRS or SMS. GPRS mode is the most preferred data sending mode. SMS mode is mostly
used in areas without GPRS coverage or GPRS usage is too expensive.
GPRS and SMS settings are described in later sections. FM1100 communicates with server
using special data protocol. Data protocol is described in device protocols documentation.
FM1100 can be managed by SMS commands. SMS Command list is described in SMS
COMMAND LIST section. Module configuration can be performed over TCP or via SMS.
Configuration parameters and modes are described in device protocols documentation. Please
contact Teltonika sale manager to find out more about protocols documentation purchase.

5.2 Sleep modes

5.2.1 Sleep mode

FM1100 is able to go to sleep mode after configurable Sleep timeout. This timeout (defined
period) starts counting when device is in STOP mode. After timeout is reached and all conditions
for sleep mode are met, device goes to sleep mode. While in sleep mode, FM1100 turns GNSS
module off and it is not making new periodic records. Only event records is being recorded with
last known coordinate and sent to AVL server. As a result power usage decreases allowing saving
vehicle battery.

FM1100 can enter sleep mode if ALL of these conditions are met:
• FM1100 has to be configured to work in Sleep mode and Sleep timeout is reached;
• Device must be synchronized time with GNSS satellites;
• No movement by movement sensor is detected;
• Ignition (configured Ignition Source) is off;

FM1100 exits sleep mode when if ONE of following conditions are true:
• Movement by movement sensor is detected;
• Ignition (configured Ignition Source) is turned on;
• USB cable is connected;

5.2.2 Deep Sleep mode

While in deep sleep mode, FM1100 sets GPS receiver to sleep mode and highly reduces
power consumption of GSM/GPRS module. Records with last known coordinate are being saved
and sent to AVL server :

23
 • GSM/GPRS module is turned on to send data and after that it is turned off
again
• If always online feature is activated it sends data over open link
Power usage is decreased to save vehicle’s battery. Note, that power saving depends on
two configurable parameters: send period and min. record saving period.

FM1100 can enter deep sleep mode if ALL of these conditions are met:
• FM1100 has to be configured to work in Deep Sleep mode and Sleep timeout set;
• Device must be synchronized time with GNSS satellites;
• No movement by movement sensor is detected;
• Ignition (configured Ignition Source) is off;
• USB cable detached;
• “Min. Record Saving Period” (Data Acquisition Mode settings) must be bigger value
than “Sleep timeout” plus “Active Data Link Timeout” parameter.
• “Send period” (Data Acquisition Mode settings) must be bigger value than “Sleep
timeout” plus “Active Data Link Timeout” parameter.

FM1100 exits deep sleep mode when if ONE of following conditions are true:
• Movement by movement sensor is detected;
• Ignition (configured Ignition Source) is turned on;
• USB cable is connected;

Note: In order to save GPRS traffic records saved in deep sleep mode do not
contain below listed I/O elements information:
PDOP, HDOP, Odometer, Speedometer, iButton ID, Cell ID, Area Code,
Temperature and GNSS power

5.3 Virtual odometer

Virtual odometer is used to calculate traveled distance in FM1100 as a separate I/O
element. When FM1100 detects movement, it starts counting distance using GNSS signal: every
second it checks current location and calculates distance between current and previous point. It
keeps adding these intervals until it is time to make a record, then FM1100 records its location
and adds odometer value, which is equal to the sum of all distances, measured every second.
When record is made, odometer resets to zero and distance calculation starts all over again.
Virtual odometer (total distance) as an I/O element can be also used with Trip feature, read
chapters 5.4.2 and 5.14.2 for more details.

5.4 Features
Using available features can greatly increase FM1100 usability options.

5.4.1 Scenarios
Four scenarios are available on FMA110 device.

24
 Green driving, Over speeding, Jamming detection and Immobilizer scenarios can be used to
manage digital output 1 and digital output 2. A single digital output can be controlled by a few
scenarios. However, it is not recommended to configure Immobilizer and other scenarios on the
same digital output.

Green Driving Scenario. Helps to inspect driver and prevent about harsh driving. Green
driving source can be GPS or accelerometer. Scenario continuously monitors: accelerating force,
braking force and cornering angles depending on build in accelerometer or depending on GPS.
The device inspects driver if needed. Monitoring sensitivity is configurable. The scenario can
control DOUT to alert the driver, with, for example, a buzzer or an LED.
To save GPRS traffic Green Driving event will be generated (included into sent records)
only when FMA120 measured values are higher than those set in configuration, without
additional I/O settings.

To prevent generating false events, harsh acceleration and harsh braking is monitored only
when following conditions are fulfilled:
• Ignition is ON (configured Ignition Source = 1)
• Vehicle speed is equal or higher than 10km/h
Harsh cornering is monitored only when following conditions are fulfilled:
• Ignition is ON (configured Ignition Source = 1)
• Vehicle speed is equal or higher than 30km/h

Note: Green Driving Scenario is a factor on various cars and various drivers
testing phase and can be subject to changes. Teltonika is constantly working
on improvement of the functionality of the devices, and strongly recommends
using the latest version of the firmware.

Over Speeding Scenario. Helps to inspect the driver and prevent exceeding the fixed speed
limit. The scenario can control DOUT to alert the driver, with, for example, a buzzer or an LED.

Jamming scenario. Radio jamming is the (usually deliberate) transmission of radio signals
that disrupt communications by decreasing the signal to noise ratio. When jamming detection is
enabled, FMA110 informs (with buzzer or LED, connected to DOUT) driver about jamming event.
Jamming can be deactivated with iButton.

Immobilizer Scenario. Vehicle can be used only if an iButton is connected and it passes the
security check. The scenario can control DOUT to alert the driver, with, for example, a buzzer or
LED. iButton list checking parameter lets the user use this scenario for authorization. The
parameter allows up to 50 unique iButton owners (specified in the iButton list) to be authorized
to use the vehicle.

25
 Note: In order for Immobilizer scenario with enabled iButton list checking to
work properly, at least 1 iButton ID must be written to the iButton list.

iButton detect scenario. If iButton is read, scenario activates configured DOUT for 500 ms.
Second activation will be available only when iButton I/O element value goes back to 0, or
another iButtob is read.

5.4.2 Trip
Trip customizable feature enables user extended monitoring of performed trips (from
engine start at present location to engine stop at arrived location), log their start and stop points,
view driven total distance4. Event will be generated (included into send records) only when trip
starts and finishes.

Note: Scenarios and Trip features are activated (DOUTs are activated) only if
ignition (configured Ignition Source) is on.

5.4.3 Geofencing
Geofencing is another feature which is highly customizable and can detect wherever car
enters or leaves customized areas. More about Geofencing can be read in 5.14.3 chapter.
Auto Geofencing feature if enabled is activated automatically by turning off car ignition
(configured Ignition Source). Next time before driving user has to disable Auto Geofencing with
iButton or by turning on ignition. In case of theft car leaves Auto Geofencing zone without
authorization FM1100 device automatically sends high priority record to AVL application.

5.4.4 iButton list

iButton list is used to enter authorized iButton ID codes, which are used to authenticate
driver in Immobilizer scenario, Auto Geofencing options and DOUT deactivation in Jamming
scenario.

5.5 CONFIGURATION

5.6 Configurator
New FM1100 module has default factory settings. Settings should be changed according to
your application and your GSM operator information.
FM1100 configuration is performed via FM1100 Configurator program. Contact sales
manager to get the latest FM1100 Configurator version. FM1100 configurator operates on
Microsoft Windows OS and uses MS .Net Framework 3.5 or higher. Please ensure that MS .Net

4
Continuous Trip distance is counted only for ONE trip. If trip is finished (stop point is detected), trip distance
resets to 0 (zero). Next trip will start counting from the begining.

26
Framework 3.5 or later is installed on your PC before starting configurator. Latest MS .Net
Framework version can be downloaded from official Microsoft web page.
Module configuration is performed over USB cable. Configuration process starts from
starting FM1100 Configurator program and then connecting to FM1100 device via Connect
button located on the top left corner of configurator. If connected successfully IMEI, Version
fields which were empty, now are filled with certain numbers depending on Modem IMEI and
firmware version of your device (figure below).
FM1100 has one user editable profile, which can be loaded from device, and saved. User
can also revert to default settings, by pressing Load Defaults button. After any modification of
configuration settings it has to be saved to FM1100 device, otherwise it will not be written to
device.
FM1100 has 2 configuration modes: Recommended Configuration (Figure 17) and
Advanced Configuration (Figure 18).

Figure 17 Recommended Configuration window

Recommended Configuration mode uses predefined data acquisition values. In this
configuration mode it is only required to enter network parameters. In Advanced Configuration
mode FM1100 is more configurable.

27
 Figure 18 Advanced Configuration window

FM1100 Configurator is divided into main areas: 1 – main button area, 2 – information
area, 3 –settings menu, 4 – parameters and values menu, 5 – recommended configuration
values.
Button 6 is used to change between configuration modes.

Main Buttons description:

‘Connect’ – connects device
‘Load’ – reads configuration parameters from FM1100 Flash memory.
‘Save’ – saves configuration parameters to FM1100 Flash memory.
‘Load Defaults’ – loads default FM1100 settings that later can be modified. This procedure
must be performed before entering new parameters.
‘Save to File…’ – allows user to save currently entered settings to .XML or bin file, for later
usage.
‘Load from File…’ – allows user to load configuration saved in .XML or bin extension file.
‘Reset device’ – reboots FM1100 and displays processor firmware version.

Additional Buttons description:

‘SIM PIN’ - allows to enter PIN code if inserted SIM card has activated PIN code security.
Note that PIN code can be entered 2 times.
‘Add Keyword’ / ‘Change Keyword’ / ‘Switch Security Off’– buttons are used to protect
configurator from unauthorized access to configuration.

28
 Keyword is 4 – 10 symbol length. If keyword is set, every time user reconnects FM1100 to
USB port, user will be asked to provide valid keyword when connecting FM1100 to configurator.
User is given 5 attempts to enter keyword. After entering valid keyword, counter resets to 5.
Keyword can be saved in configuration file via configurator, if you choose to save it as a .bin file.
Configuration keyword can be changed or removed via SMS.
If user disconnects FM1100 using ‘Disconnect’ button and does not disconnect from USB
port, after reconnecting using ‘Connect’ button, configurator does not ask for keyword.

ATTENTION! If you have entered a keyword, disconnected from the

configurator and then later connected again, you will need to enter the
keyword that you have entered previously. If you have forgotten it, please
contact your local sales manager.

5.7 Read records*5

When the FM1100M is working in offline mode, it can save up to 50,000 records. Since
these records are not sent to the server, they can be downloaded directly to connected
computer using USB connection. When you connect FM1100M device, FM11YX Configurator
appears with additional option "Read Records” (Fig. 19).

Figure 19 FM11YX Configurator window with FM1100M connected

After device is switched on, you have to wait 3 minutes for device to startup. Only then it is
possible to download records. If the memory is fully filled, the records reading may take several
minutes. After reading records, all records are deleted from the device memory. Data records are

5
Functionality available only with FM1100M version!

29
stored in a binary file on your PC. You can upload these records from file to TAVL server and
access all the data from TAVL.

ATTENTION! New functionality is available only with FM1100M version. Check

for correct version on your FM1100M sticker as it is shown below. In the upper
right corner there has to be M symbol indicating FM1100M version.

TAVL client application lets user to use the

following features:
• Import data file saved from the
device to the TAVL;
• Preview track of the imported data;
• Generate reports of the imported
data.

Figure 20 FM1100M sticker

More details on how to use TAVL application please refer to “TAVL3 application user
manual v1.4” documentation or its later versions.
FM1100M version can be still used as a standard FM1100. It can be configured to acquire
and send data to server. It will be possible to store up to 100’000 data records if GSM is not
available at the moment. It will send data later when GPRS is available again. Note that
FM1100M can have memory full of records. In such a case it will start deleting oldest records in
order to save new ones. Sending all the data records to server may take some time. Sending
100’000 records for FM1100M may take for about 21 hour (exact time may differ depending on
GPRS/server load).

5.8 System settings

System settings have 7 configurable parameters:
• Deep sleep settings, where user can turn deep sleep on or off;
• Analog Input Settings, where user can choose analog input range 10 V or 30 V,
depending on needed accuracy (lower range gives higher accuracy of
measurements), and input voltage;
• Object Motion Detection Settings, where user can configure 3 ways how FM1100
will detect stopped movement, and change its working mode (for working modes,
read section 5.13)
• Static navigation settings, where user can turn static navigation on or off;
• Records Settings, where user can enable or disable records when GPS is not
available (no time synchronization);
• GNSS Settings, where user can choose satellite system and time synchronization via
NTP (Network Time Protocol)

30
 • Ignition Source sets ignition triggered functionalities to be triggered by:
o Power Voltage (if voltage is between High Voltage Level and Low Voltage
Level the ignition is considered to be turned on);
o Digital Input (DIN1 ON – ignition on, DIN1 OFF – ignition off);
o Movement (if accelerometer/movement sensor detects movement then
ignition is on, if movement stops – ignition is off).

Stop Detection Vehicle on Stop mode Vehicle Moving mode

Source
Ignition If ignition (configured Ignition If ignition (configured Ignition
(recommended) Source) is logic low Source) is logic high
Msensor (movement Internal movement sensor does Internal movement sensor detects
sensor) not detect movement movement
GNSS GNSS fix is available and vehicle GNSS fix is available and vehicle
speed is lower than 5 km/h speed is higher than 5 km/h
While GNSS fix is unavailable, Object Motion Detection Settings are
working like in Msensor mode

Static Navigation Mode is a filter, which filters out track jumps when the object is
stationary. If Static navigation filter is disabled, it will apply no changes on GNSS data. If Static
navigation filter is enabled, it will filter changes in GNSS position if following conditions are met:

• Ignition OFF is detected by Ignition source (DIN1 or External Voltage);

• No movement is detected by Movement sensor;
• Vehicle speed (measured by GPS) is less than 4 km/h;
• Vehicle does not move away from the last stop point more than 200 meters.

31
 Figure 24 System settings configuration

Also if Power Voltage is chosen as ignition source there is possibility to choose manual
ignition detection or automatic ignition detection. For manual ignition user has to choose power
voltage levels by himself. For automatic ignition FMA110 device detects system voltage and
automatically detects ignition. In 12 V systems ignition is on when voltage is between 13,2 – 16 V
and for 24 V systems ignition is detected when voltage is between 27 – 32 V.

5.9 Records settings

Here user can modify if FM1100 device will send newest records first, meaning, that the
most important thing is to know recent position of car, older records are being sent right after
newest records arrive to AVL application.
Activate Data Link Timeout is used to set timeout of link between FM1100 and AVL
application termination. If FM1100 has already sent all records it waits for new records before
closing link. If new records are generated in the period of this timeout, and minimum count to

32
send is reached, they are sent to AVL application. This option is useful when GSM operator
charge for link activation.
Server Response Timeout is used to set time period waiting for response from server side.

Figure 25 Records settings configuration

5.10 GSM settings, GPRS part

‘GPRS’ defines main parameters for FM1100: GSM operator APN and GPRS username and
password (optional – depending on operator), destination server IP and port, and allows to set
protocol used for data transfers – TCP or UDP
Some operators use specific authentication for GPRS session – CHAP or PAP. If any of these
is used, APN should be entered as ‘chap:<APN>’ or ‘pap:<APN>’. I.e. if operator is using APN
‘internet’ with CHAP authentication, it should be entered as ‘chap:internet’. Information
about APN and authentication type should be provided by your GSM operator.

Figure 26 GPRS configuration

Always online mode – never close link to server if enabled, even in deep sleep.

5.11 GSM settings, SMS part

Essential fields in ‘SMS’ part are ‘Login’ and ‘Password’. The login and password are used
with every SMS sent to FM1100. If login and password are not set, in every SMS sent to FM1100
device two spaces before command have to be used (<space><space><command>).
Command structure with set login and password:
<login><space><password><space><command>, example: “asd 123 getgnss”
Phone numbers have to be written in international standard, without using “+” or “00”
signs in prefix. If no numbers are entered, configuration and sending commands over SMS are
allowed from all GSM numbers.
SMS data sending settings – enable or disable periodic data and event SMS usage. This
setting does not affect replies to SMS request messages – answers are always sent back to
sender telephone number.
FM1100 can send binary SMS with 24-coordinates-in-one-SMS. It is used in areas where no
GPRS coverage is available. Module collects data and sends to server binary SMS containing

33
information about last 24 collected points. SMS sending schedule is set in SMS Week Time tab.
24-Coordinates SMS decoding is described in device protocols documentation. Please contact
Teltonika sale manager to find out more about protocols documentation purchase.

Figure 27 SMS configuration

Note: A mobile phone will not understand and SMS with binary code, so sending
it to a mobile phone is useless. When sending a binary SMS to a phone number,
which is a server phone number, the server can interpret and understand binary
code, so the data can be read and you can view it on the server.

SMS login and password and authorized number list are used to protect FM1100
module from unauthorized access. Module accepts messages only from a list of
authorized numbers and with proper module login and password. Numbers must
be without “+” or “00” prefix. If no authorized numbers are entered, module
accepts messages from all numbers.

5.12 GSM settings, Operator list*6

Operators list – FM11 can work in different modes (use different settings) according to the
operator list defined. Operator list is used for Data Acquisition Mode switching (see chapter

6
Functionality available only with FM1100 with one SIM version!

34
5.13 Data Acquisition Mode settings for more details). Modes are changed based on GSM
operator FM11 is connected to.

Figure 28 Operator list configuration

If operator list is left empty, it will allow using GPRS to any GSM operator. Please note that
FM1100 will work in Unknown mode only (make sure it is configured to allow data sending –
GPRS context is enabled).
Operator Blacklist. Operator BlackList Functionality algorithm:
Device tries to connect to an operator with the strongest signal. It will prioritize operators which
are specified in the operator list. If no operators from the operator list are available, the device
will try to connect to an operator from the blacklist. If the device connects to an operator from
the blacklist, it will not be allowed to connect to the internet or send SMS messages. If no
suitable operator is found on both lists, the device will try to connect to a remaining available
operator with the strongest signal. The brief functionality is shown in diagram below:

35
 Figure 24 Black operator list functionality

Figure 25 Black operator list configuration

5.13 Data Acquisition Mode settings

Data Acquisition Modes are an essential part of FM1100 device, it is also highly
configurable.
By configuration user defines how records will be saved and sent. There are three different
modes: Home, Roaming and Unknown. All these modes with configured data acquisition and

36
send frequencies depend on current GSM Operator defined in Operator list (see section 5.12)
and are switched when GSM operator changes (e.g. vehicle passes through country boarder).
If current GSM operator is defined as Home Operator, device will work in Home Data
Acquisition mode, if current operator is defined as Roaming Operator, device will work in
Roaming Data Acquisition mode, and if current operator code is not written in Operator list (but
there is at least one operator code in the operator list), device will work in Unknown Acquisition
mode.
This functionality allows having different AVL records acquire and send parameters values
when object is moving or stands still. Vehicle moving or stop state is defined by Stop Detection
Source parameter. There are 3 ways for FM1100 to switch between Vehicle on Stop and Vehicle
Moving modes see section 5.7.
FM1100 allows having 6 different modes. Operational logic is shown in Figure 29.

If there are no operator codes entered into operator list, FM1100 will work in
Unknown network mode ONLY.

Figure 29 Data Acquisition Mode configuration

Operator search is performed every 15 minutes. Depending on current GSM operator,

Home, Roaming or Unknown mode can be changed faster than every 15 minutes. This process is
separate from operator search. Movement criteria are checked every second.

37
 Figure 30 Data Acquisition Mode – Home configuration

Figure 31 Data Acquisition Mode- Roaming configuration

Figure 32 Data Acquisition Mode- Unknown configuration

‘Min Period’

‘Min Saved Records’ defines minimum number of coordinates and I/O data that should be
transferred with one connection to server. If FM1100 does not have enough coordinates to send
to server, it will check again after time interval defined in ‘Sending Period’

Send period – GPRS data sending to server period. Module makes attempts to send
collected data to server every defined period. If it does not have enough records (depends on
parameter Min. Saved Records described above), it tries again after defined time interval.

38
 GPRS Week Time tab – most GSM billing systems charge number of bytes (kilobytes)
transmitted per session. During the session, FM1100 makes connection and transmits data to a
server. FM1100 tries to handle the session as much as possible; it never closes session by itself.
Session can last for hours, days, weeks or session can be closed after every connection in certain
GSM networks – this depends on GSM network provider. GPRS Context Week Time defines
session re-establish schedule if session was closed by network. New GPRS context is opened if
time is 10 minutes till time checked in table. Therefore if all boxes are checked, FM1100 is able to
open new connection anytime. At scheduled time match FM1100 checks for GPRS session
activity. If GPRS session is alive, FM1100 sends data to server according to Send period
parameter. If it is not, FM1100 checks if it is able to re-establish the session.

Figure 33 GPRS Week Time configuration

Device checks if the time between last saved record and current time is equal or higher
than Time based acquire interval. If so, FM1100 saves record to memory. If not, FM1100 checks
if the distance from last record to current record is equal or higher than Distance based acquire
interval. If so, saves the record to memory. If not and speed is higher than 10km/h, then FM1100
checks if angle difference between last record and current record is equal or higher than Angle
based acquire value. If so, saves the record to memory. The last data acquisition state checks if
alteration between last record speed and present speed is higher than defined. If so, FM110
saves record to the memory. These checks are performed every second.

Note: Keep in mind that FM1100 operates in GMT:0 time zone, without
daylight saving.

39
FM1100 is able to collect records using three methods at the same time: time, distance and angle
based data acquisition:
Time based data acquiring (Min. period) – records are being acquired every time when defined
interval of time passes. Entering zero disables data acquisition depending on time.
Min. time period

Distance based data acquiring (Min. distance) – records are being acquired when the distance
between previous coordinate and current position is greater than defined parameter value.
Entering zero disables data acquisition depending on distance.
Min. distance

Angle based data acquiring (Min. angle) – records are being acquired when angle difference
between last recorded coordinate and current position is greater than defined value. Entering
zero disables data acquisition depending on angle.

Min. angle

Speed based data acquiring (Min. speed delta) – records are being acquired when speed
difference between last recorded coordinate and current position is greater than defined value.
Entering zero disables data acquisition depending on speed.

5.14 Features settings

For more information about available Scenarios, Trip, Geofencing and iButton list, refer to
5.4 chapter.

40
 5.14.1 Scenarios settings
In Scenarios window four different scenarios are available to use. More than one scenario
can manage the same DOUT. If DOUT Control is disabled, scenarios can only generate events
without digital output activation.

Figure 34 Scenarios configuration

Digital Output (open drain grade) usage in scenarios:

• Green Driving
DOUT1/DOUT2 (optional) is ON for:
▪ 3sec. if detected value is over (0; 30] % from preconfigured allowed value
▪ 5sec. if detected value is over (30; 50] % from preconfigured allowed value
▪ 7sec. if detected value is over (50; -] % from preconfigured allowed value
After period of time DOUT1/DOUT2 is turned OFF.

• Over Speeding
If Dout Control is disabled, scenario only generate events without digital output activation.
If Dout Control is enabled DOUT1/DOUT2 (optional) is ON, while vehicle speed exceeds the
parameter value. DOUT1/DOUT2 remains active until current speed decreases below the
parameter value.
• Jamming Detection
When this scenario is enabled and device modem is being jammed, then a low priority
event is generated. Jamming functionality allows to set Jamming Sensitivity to Low, Medium or
High. Jamming Timeout, Jamming Dout control and Jamming Pulse Duration can be configured. If
Jamming Pulse Duration is > 0, then jamming is activated (digital output will be activated for this
time period and will be deactivated after time expires). If jamming ends before timeout occurs,
then timeout countdown will reset. Jamming can be deactivated with iButton. When jamming

41
event is detected and DOUT is activated it can be deactivated with iButton. If iButton list is not
empty, then digital output can be deactivated only with authorized iButton.
• Immobilizer
If Dout Control is disabled, scenario will only generate events without digital output
activation. If Dout Control is enabled DOUT1/DOUT2 (optional) turns ON if Ignition turns ON
(configured Ignition Source =1). After iButton ID is read (any iButton is attached), DOUT1/DOUT2
turns OFF. After iButton identification, Ignition (configured Ignition Source) can be turned OFF
(configured Ignition Source =0) for no longer than 30 seconds, otherwise immobilizer must be
repeated. If iButton list checking parameter is enabled, authorization will be successful only if
attached iButton is specified in the iButton list.

5.14.2 Trip settings

Trip window offers user to configure Trip feature. If Trip is enabled configuration of
parameters are enabled.
Start Speed – GNSS speed has to be greater than the specified Start Speed in order to
detect Trip Start.
Ignition Off Timeout – timeout to wait if ignition (configured Ignition Source) was off, to
detect Trip stop.
• Continuous distance counting – Not or Continuous can be chosen. For this feature I/O Trip
distance must be enabled.

If I/O Trip distance is enabled and Continuous distance counting variable is set to
Continuous, Trip distance is going to be counted continuously (from Trip start to Trip stop). This
value is written to I/O Trip distance value field. When Trip is over and next Trip begins, Trip
distance value is reset to zero. When the next trip starts counting continuously starts from the
beginning again.
If I/O Trip distance is enabled and Continuous Distance Counting variable is set “Not”, then
the distance is going to be counted only between every record made. This value is written to I/O
Trip distance value field and reset to zero every new record until Trip stops. If later all Trip
distance values are summed up manually, the user gets the distance driven during the whole
period of the Trip.

Figure 35 Trip configuration

42
 Figure 36 Trip continuous distance counting parameter example

Continuous odometer. Continuous odometer calculates the distance if Total Distance I/O
element is enabled. Odometer Value is constantly saved to flash memory every 30 seconds, but
counted every second. After power is turned off, odometer value saved in flash does not reset.
Start odometer value with can be set using configurator („set“ button) or SMS/GPRS
(setparam/getparam) commands. This parameter can not be configured via TCP config. If this
value is not set, FMA110 starts counting from 0. Continuous odometer works irrespective of the
Trip functionality.

Figure 36 Continuous odometer setting in configurator.

Remember iButton functionality. If Remember iButton ID while trip detected and Trip
parameters are enabled, ignition is on and iButton is attached, then FMA110 remembers iButton
ID. iButton ID is saved and sent to server with every record. If new iButton is attached during the

43
trip, FMA110 remembers new iButton ID. FMA110 forgets iButton ID after ignition is off and trip
ignition off timeout is reached.

Figure 37 Remember iButton parameter in configurator

5.14.3 Geofencing settings

FM1100 has 5 configurable Geofence zones and it can generate an event when defined
Geofence zone border is crossed.
Frame border – frame border is an additional border around Geofence zone. It is additional
area around defined zone used to prevent false event recording when object stops on the border
of the area and because of GNSS errors some records are made inside area and some – outside.
Event is generated only when both borders are crossed. See figure 36 for details: track 1 is
considered to have entered the area while track 2 is not.

Track Nr. 2

Track Nr. 1

Figure 37 Geofence border

Shape – can be rectangle or circle

Priority – priority of Geofence event: low, high or panic. These levels define priority of
event information sending to server. See I/O element description for more details about
priorities.

44
 Generate event (On entrance, On exit, On Both) – choose when record will be generated;
X1 – geofence zone left bottom corner X coordinate (longitude);
Y1 – geofence zone left bottom corner Y coordinate (latitude);
X2 or R – geofence zone upper right corner X coordinate (longitude) or radius of circle
when Circular zone is used (radius in meters);
Y2 – geofence zone upper right corner Y coordinate (latitude);

Figure 38 Geofence configuration

AutoGeofencing settings
AutoGeofence – the last known position after movement = off. If your car’s being
taken away – you can be notified. The shape and size of the geofence zones are
parameters. When object will leave geofence zone device will trigger an asynchronous
message.
AutoGeofencing option can be configured by following parameters visible in Figure 38
below.
Activate – Enable or Disable AutoGeofence functionality.
Activation TMO – Time period before Geofence is activated after vehicle stops.
Deactivate By:
Ignition – If ignition (configured Ignition Source) becomes high it will disable
AutoGeofenze Zone.
iButton – if iButton is attached it will disable AutoGeofence Zone.
Edit iButton List – if list is not empty, attached iButton is tested against an iButton list, if
match is found AutoGeofence zone is disabled.
Priority – Priority of generated event, which will be applied to saved record.
Exit Event – Event generation on Geofence exit.

45
 On Both – Event generation on Geofence exit.

Note that AutoGeofencing does not require entering coordinates, instead it requires GNSS
visibility. If vehicle stopped and activation timeout has passed, an AutoGeofence will be created
around vehicle’s last position with set Radius value. AutoGeofence event generation works the
same as Geofencing mentioned above.

Figure 39 Autogeofence configuration

Note: FM1100 operates GMT:0 time without daylight saving.

5.14.4 SMS events

SMS events functionality allows FM1100 to send a configured SMS when an event is
triggered. This event can be triggered by:
• Green Driving
• OverSpeeding
• Jamming
• Authorized Driving
• Immobilizer
• Trip start/stop
• Geofence
• AutoGeofence
• I/O event

When any of the above events is triggered, FM1100 sends a configured SMS message to a
defined phone number. If SMS events is activated, but there are no numbers defined in SMS
events PreDefined Numbers list (figure 39), then the device will not send any messages.
SMS events can be activated in FM11YX configurator GSM→ SMS -> SMS events (figure 39).

46
 Figure 40 SMS Events PreDefined Numbers list and SMS events activation settings

The sent SMS messages format is according to:

“Date Time EventText”

For example, if FM1100 is configured to send an SMS, when Digital Input 1 reaches High level,
with priority High and configured to generate event on both range enter and exit (figure 40),
then the sent SMS is:

“2012/6/7 12:00:00 Digital Input 1”

47
 Figure 41 Configured Digital Input 1 SMS event

The SMS Text field can be altered and any text can be entered. Maximum message length is 40
symbols (numbers, letters and symbols in ASCII, except for comma “,”).

ATTENTION!
If FM1100 is in Deep Sleep mode and SMS event occurs with LOW priority
(which does not wake up FM1100), then the device does not send the message.
It is saved in device memory until it wakes up from Deep Sleep mode and GSM
modem starts working normally. After it wakes up, all the messages that are
saved in memory will be sent, but keep in mind that only 10 messages can be
saved in memory – all other messages will not be saved, until there is room in
device memory.

5.14.4.1 SMS events configuration

Scenarios

To configure SMS events for scenarios, open Scenarios window and Enable desired scenario.
Then go to GSM ->SMS -> SMS events window and activate SMS event for Enabled scenario.
Figure 41 shows how to enable Green Driving and Authorized Driving SMS Events. Note, that
Green Driving can’t work together with Over Speeding and Authorized Driving can’t work
together with Immobilizer scenario– only one of them could be enabled. After enabling SMS
events, different message texts can be written for different scenarios.

48
 Figure 42 Scenarios SMS event configuration

When any of the scenarios events occurs, a text message will be sent to the predefined number.

Trip

In order to configure Trip SMS events click on Trip window and Enable Trip feature (figure 42).
Then go to GSM -> SMS -> SMS Events settings and Enable Trip SMS event. After enabling SMS
Events (figure 43), trip event will be triggered and message sent, when Trip starts (GNSS speed
exceeds the speed in Start Speed (ex. 5 km/h) and when Trip stops, that is ignition is turned off
longer then the time written in Ignition Off Timeout (ex. 60 seconds).

Figure 43 Trip Start/Stop SMS event configuration

49
 Figure 44 Trip Start/Stop SMS event configuration

Geofence

Geofence SMS event is triggered and message sent when the device exits and/or enters a
configured Geofence zone. The Geofence zone must be configured to generate an event On Exit,
On Enter or On Both (figure 44). If No Event is selected, then it is not possible to turn on SMS
events. If several zones are created then SMS events can be turned on separately for each zone
entering different text message.

Figure 45 Geofence SMS event configuration

50
AutoGeofence

SMS events for AutoGeofence are configured the same as in Geofence. AutoGeofence is next to
Geofence configuration (figure 45), for SMS events configuration, go to GSM -> SMS -> SMS
Events.

Figure 46 AutoGeofence SMS event configuration

I/O events

FM1100 sends SMS event message when a configured I/O property enters and/or exits its
configured High/Low boundaries or Hysteresis event generation is chosen (Monitoring does not
generate event, so SMS event could not be configured). Every IO element SMS event can be
configured to send individual message to different numbers.

Figure 47 I/O SMS event configuration

5.15 I/O settings

When no I/O element is enabled, AVL packet comes with GNSS information only. After
enabling I/O element(s) AVL packet along with GNSS information contains current value(s) of
enabled I/O element.

51
 Permanent I/O elements
(are always sent to server if enabled)
Nr. Property Name Description
1 Digital Input Status 1 Logic: 0 / 1
2 Digital Input Status 2 Logic: 0 / 1
3 Digital Input Status 3 Logic: 0 / 1
4 Analog Input 1 Voltage: mV, 0 – 30 V
5 GSM level GSM signal level value in scale 1 – 5
6 Speed Value in km/h, 0 – xxx km/h
7 External Power Voltage Voltage: mV, 0 – 30 V
States: 0 – GPS module is turned off, 2 – working,
but no fix, 3 – working with GPS fix, 4 – GPS module
8 GNSS Power is in sleep state, 5 – antenna is short circuit. Do not
try to use this parameter to see if antenna is
disconnected.
9 Dallas Temperature 10 * Degrees ( °C ), -55 - +115, if 3000 – Dallas error
10 iButton ID iButton ID number
11 0 – home on stop, 1 – home on move, 2 – roaming
Data Mode on stop, 3 – roaming on move, 4 – unknown on stop,
5 – unknown on move
12 Digital output 1 state Logic: 0 / 1
13 Digital output 2 state Logic: 0 / 1
14 PDOP Probability * 10; 0-500
15 HDOP Probability * 10; 0-500
16 Trip distance Distance between two records: m
0 – not deep sleep mode, 1 – GNSS sleep mode, 2 –
17 Sleep mode
deep sleep mode
18 Cell ID GSM base station ID
Location Area code (LAC), it depends on GSM
19 Area Code operator. It provides unique number which assigned
to a set of base GSM stations. Max value: 65536
20 Movement Sensor 0 – not moving, 1 – moving.
21 GSM operator Code Currently used GSM Operator code
22 Ignition Ignition status indication. Logic: 0 / 1
23 Total distance Total distance: m
Eventual I/O elements
(generate and send record to server only if appropriate conditions are met)
Nr. Property Name Description
24 Geofence zone 01 Event: 0 – target left zone, 1 – target entered zone
25 Geofence zone 02 Event: 0 – target left zone, 1 – target entered zone
26 Geofence zone 03 Event: 0 – target left zone, 1 – target entered zone
27 Geofence zone 04 Event: 0 – target left zone, 1 – target entered zone
28 Geofence zone 05 Event: 0 – target left zone, 1 – target entered zone
29 Auto Geofence Event: 0 – target left zone, 1 – target entered zone

52
 30 Trip 1 – trip start, 0 – trip stop
31 Immobilizer 1 – iButton connected
32 Authorized driving 1 – authorized iButton connected
1 – harsh acceleration, 2 – harsh braking, 3 – harsh
33 Green driving type
cornering
Harsh acceleration, braking or cornering – g*100
34 Green driving value
(value 123 -> 1.23g)
At over speeding start km/h, at over speeding end
35 Over Speeding
km/h
36 LVCAN Speed Value in km/h, 0 – 250 km/h
LVCAN Accelerator pedal
37 Value range: 0-100 %
position
LVCAN Total fuel used Value range: 0- 99999999 liters*
„Total Fuel Used“ is sent to server multiplied by 10.
38
Example: if value was 150.5 liters, „1505“ will be
sent to server.
39 LVCAN Fuel level (liters) Value range: 0-100 liters
Value range: 0-8200 rpm; value in rounds per
40 LVCAN Engine RPM
minute.
41 LVCAN Vehicle distance Value range: 0-2145000000 meters
42 LVCAN Fuel level (proc.) Value range: 0-100 %
43 LVCAN Program number Value range: 0-999
There are two types of operations with Permanent I/O elements: simple
monitoring and event generating. Monitoring method is used when current I/O
information needed with regular GNSS coordinates. Event generating method is
used when additional AVL packet is needed when current value of I/O exceeds
predefined High and Low levels. I/O settings allow defining I/O event criteria.

Figure 48 I/O settings

Enabled or disabled field – allows enabling I/O element so it is added to the data packet
and is sent to the server. By default all I/O element are disabled and FM1100 records only GNSS
coordinates.
Priority (AVL packet priority) can be low, high or panic. Regular packets are sent as Low
priority records. When low priority event is triggered, FM1100 makes additional record with
indication that the reason for that was I/O element change. When High priority is selected,
module makes additional record with high priority flag and sends event packet immediately to

53
the server by GPRS. Panic priority triggers same actions as high priority, but if GPRS fails, it sends
AVL packet using SMS mode if SMS is enabled in SMS settings.
High and Low levels – define I/O value range. If I/O value enters or exits this range, FM1100
generates event. “Generate event” parameter defines when to generate event – when value
enters defined range, exits it or both.
Averaging constant – it is an I/O event delay parameter. In some applications there is no
need to generate events on every I/O range enter/exit immediately. Sometimes it is necessary to
wait some time interval before event generating. Averaging constant allows setting I/O event
delay (averaging). If I/O value is entering or leaving predefined range, it must have same value
for Averaging constant time. 1 Averaging constant value equals about 100 miliseconds. In Deep
Sleep mode there is no Averaging.
Note. Firmware version 01.10.09 rev.1 – 01.10.xx Averaging constant value of Ibutton I/O
element equal for 1 second.
Note: I/O element’s “Movement sensor” Averaging constant is interpreted as
Start Move Timeout in seconds (from 1 to 59).
Start Move Timeout – is a time interval required for movement sensor to be in
the moving state, to consider vehicle as moving.

5.15.1 Monitoring
I/O monitoring starts after enabling I/O element and setting up I/O parameters as it is
shown below:

Figure 49 I/O settings

5.15.2 Event Generating

Events happen when the value of enabled I/O intersects thresholds (enter, exit or on both)
predefined by High and Low level thresholds. Table below defines all available values of I/O
settings.

Setting Value
Priority low, high
High level maximum threshold
Low level minimum threshold
Generate event on interval enter, on interval exit, on both enter and exit
Average constant 1 – 232 (4 Bytes)

54
 Figure 50 Digital Input event generation example

5.15.3 Hysteresis

Figure 51 Hysteresis parameter configuration

I/O elements can generate events according to hysteresis algorithm. If I/O event operand
“Hysteresis” is selected, events will be generated as it is shown in the illustration below (I/O
speed is taken as I/O value example):

Figure 52 Event generation according hysteresis algorithm

6 SMS COMMAND LIST

Read chapter 5.11 to know how to construct a proper SMS message and send it to FM1100
device. All commands are case sensitive. While FM1100 operates in Deep Sleep mode and user
tries to send SMS message it cannot arrive to FM1100 device, because GSM/GPRS module is
disabled most of the time (wake up depends on Send Period parameter). FM1100 will receive
the SMS when it wakes up (exits deep sleep mode).

55
6.1 SMS command list
Command Description Response
getstatus Modem Status information Yes
getweektime Current device time, Day of Week and amount of minutes Yes
passed since start of week
getops List of currently available GSM operator Yes
getcfgtime Date and Time of last successful configuration Yes
ggps Google Map Link information Yes
getgps Current GPS data and time Yes
cpureset Reset CPU No
resetprof Reset all FLASH1 profile configuration to default profile No
getver Device / Modem / Code version information Yes
getinfo Device runtime system information Yes
deleterecords Delete all records saved on FLASH No
getio Readout digital inputs and outputs Yes
readio # Readout digital input value according entered ID, # - ID Yes
value
setdigout ## Y1 Y2 set digital outputs Yes
0 – OFF, 1 – ON
Y1 – timeout for DO1
Y2 – timeout for DO2
setdigoutX Z Y set selected digital output Yes
X – number of Digital output (1 – digital output 1; 2 –
digital output 2)
Z – activate(1)/deactivate(0)
Y – activation/deactivation timeout
getparam # Readout parameter value according entered ID. Yes
# - ID value.
setparam # # Set parameter value according entered ID and Value. Yes
1.# - ID value.
2.# - New Parameter Value
getparam 1271 X X values can be 1,2,3. Yes
flush #,#,#,#,#,#,# Initiates all data sending to specified target server No
1.# - IMEI
2.# - APN
3.# - LOGIN
4.# - PASS
5.# - IP
6.# - PORT
7.# - MODE (0-TCP/1-UDP)
readops # 1 – send first 20 operator codes, 2 – send from 21st to 40th
operator codes, 3 – send all other operator codes
sn # Static navigation, 1 – enable, 0 – disable Yes
setkey # # Set a new configuration keyword Yes

56
 1. # - Old Keyword
2. # - New Keyword
delkey # Delete configuration keyword Yes
banlist Banned operators information Yes
crashlog Device last information before unexpected reset Yes
delete_all_sms Deletes all SMS No
lvcangetprog CAN Program Number request by SMS Yes
lvcansetprog # Set LVCAN program number Yes
lvcangetinfo Get LV-CAN info by SMS Yes
getcontsens Get IDs of connected temperature sensors Yes
faultcodes Read DTC Yes
dtcinfo DTC information Yes

6.1.1 getstatus
Response details Description
Data Link Indicate module connection to server at the moment: 0 – Not
connected, 1 – connected
GPRS Indicate if GPRS is available at the moment
Phone Voice Call status: 0 – ready, 1 – unavailable, 2 – unknown, 3 –
ringing, 4 – call in progress, 5 – asleep
SIM SIM Status: 0-ready, 1-pin, 2-puk, 3-pin2, 4-puk2
OP Connected to GSM Operator: numerical id of operator
Signal GSM Signal Quality [0-5]
NewSMS Indicate if new message received
Roaming 0 – Home Network, 1 – roaming
SMSFull SMS storage is full? 0 – ok, 1 – SMS storage full
LAC GSM Tower Location Area Code
Cell ID GSM Tower Cell ID Code

Example: Data Link: 0 GPRS: 1 Phone: 0 SIM: 0 OP: 24602 Signal: 5 NewSMS: 0 Roaming: 0
SMSFull: 0 LAC: 1 Cell ID: 864

6.1.2 getweektime
Response details Description
Clock Sync Indicates system clock synchronization status. 0 – System is not
synchronized, 1 – System synchronized
DOW Day Of Week – indicates current day of week starting from 1 –
Monday, 2 – Tuesday, etc.
Time Indicates current GMT time
WeekTime Indicates time in minutes starting from Monday 00:00 GMT

Example: Clock Sync: 1 DOW: 4 Time 12:58 Weektime: 6538

57
 6.1.3 getops
Response details Description
LIST Returns list of current available allowed operators.

Example: (2,”LT BITE GSM”,”BITE”,”24602”),(3,”TELE2”,”TELE2”,”24603”)

6.1.4 getcfgtime
Response details Description
Date/Time Returns last performed configuration date and time.

Example: Last Configuration was performed on: 2010.4.15 5:45:19

6.1.5 getgps
Response details Description
Gps Indicates valid (1) or invalid (0) Gps data
Sat Count of currently available satellites
Lat Latitude (Last good Latitude)
Long Longitude (Last good Longitude)
Alt Altitude
Speed Ground speed, km/h
Dir Ground direction, degrees
Date Current date
Time Current GMT time

Example: GPS:1 Sat:7 Lat:54.71473 Long:25.30304 Alt:147 Speed:0 Dir:77 Date: 2007/8/24
Time: 13:4:36

6.1.6 ggps
Response details Description
D Date
T Time
S Actual Speed
C Latitude (Last good Latitude), Longitude (Last good Longitude)
Url Google Maps Link

Example: D:2013/7/4 T:0:0:0 S:0 C:0, 0 Url: http://maps.google.com/?q=0,0&om=1speed:0

6.1.7 getver
Response details Description
Code Ver Firmware version
Device IMEI IMEI
Device ID Device ID is used to detect by server which type of configuration
to load

58
 Bootloader Ver Bootloader Version
Modem App Ver Version of modem application (veiks: nuo 00.05.14)
Revision Firmware revision

Example: Code Ver:01.06.15 Rev:1 Device IMEI:353976010139156 Device ID:000001

Bootloader Ver: 01.09 Modem APP Ver:TM11Q_R_01.00.03.03_002

6.1.8 getinfo
Response details Description
INI Device Initialization Time
RTC RTC Time
RST Restart Counter
ERR Error Counter
SR Number of Sent Records
BR Number of broken records
CF Profile CRC Fail counter
FG Failed GPRS counter
FL Failed link counter
UT UPD Timeout counter
SMS Sent SMS Counter
NOGPS No GPS Timer
GPS GPS receiver state. 0 – OFF, 1 – restarting, 2 – ON but no fix, 3 –
ON and operational, 4 – sleep mode
SAT Average satellites
RS Reset Source Identification
1 – Low Power, 2 – W Watchdog, 3 – I Watchdog, 4 – Software
reset, 5 – Power On, 6 – Pin Reset
MD Data Mode state. 0 – Home and Stop, 1 – Home and Moving, 2 –
Roaming and Stop, 3 – Roaming and Moving, 4 – Unknown and
Stop, 5 – Unknown and Moving
RF Records Found – number of records in the memory.

Example: INI:2013/10/11 8:44 RTC:2013/10/11 8:59 RST:1 ERR:0 SR:0 BR:0 CF:0 FG:0 FL:0
UT:0 SMS:1 NOGPS:0:14 GPS:2 SAT:0 RS:3 MD:4 RF:0

6.1.9 getio
Response details Description
DI# Digital Input state
AIN# Analog Input state
DO# Digital Output state

Example: DI1:0 DI2:0 DI3:0 AIN:0.0611 DO1:0 DO2:0

59
 6.1.10 readio #
Response details Description
ID I/O element ID
Value I/O Element value

Example: I/O ID:3 Value:0

6.1.11 setdigout ## Y1 Y2
Sets digital outputs to ON or OFF state (for some time if needed). Value is written as a row
for OUT1 and OUT2 values.
Example: ‘setdigout 01 0 5’ will set OUT2 to high level for 5 seconds, while OUT1 to low
level.
To ignore one digital output value and make ON/OFF state only to another digital output
enterany question mark.
Example: ‘setdigout ?1’ will set OUT2 to high level for indefinite period of time while OUT1
remains as it was set before.

6.1.12 setdigoutX Z Y
Sets selected digital output to on or OFF state for a defined period of time.
Example: ‘setdigout2 1 5’ will set DOUT2 to high level for 5 seconds.

6.1.13 getparam ####

Read parameter value. ID consists of 3 or 4 digits. Detailed list of parameters and IDs can
be found in chapter number 8 “Parameter List”
Example: ‘getparam 1245’ command will request server IP address.

6.1.14 setparam ####

Sets new value for parameter. ID consists of 3 or 4 digits. Detailed list of parameters and
IDs can be found in chapter number 8 “Parameter List”
Example: ‘setparam 1245 127.0.0.1’ will change configured IP address.

6.1.13. getparam 1271 X/212 X

X values can be 1,2,3.
If X = 1, Operator codes from 0-19 are read from configuration and sent via SMS.
If X = 2, Operator codes from 20-39 are read from configuration and sent via SMS.
If X = 3, Operator codes from 40-49 are read from configuration and sent via SMS.
If X = any other, Operator codes from 0-19 are read from configuration and sent via SMS.

6.1.14. setparam 1271 X/212 X

If X is from 0 to 49, X means index of operator code which has to be configured. Up to 20
operator codes may be configured in 1 SMS. Example: Setparam 1271 16 24602,24603,24605
,here 16th, 17th and 18th operator codes are set. Note! Other operator codes are left unchanged
in the configuration.

6.1.15 readops #
Send from device Operator List.

60
 1 – send first 20 operator codes, 2 – send from 21st to 40th operator codes, 3 – send all
other operator codes.

6.1.16 flush #,#,#,#,#,#,#

Initiates all data sending by GPRS to specified target server. Comma separated parameters
go as numbered:
1.# - IMEI
2.# - APN
3.# - GPRS LOGIN
4.# - GPRS PASSWORD
5.# - IP
6.# - PORT
7.# - MODE (0-TCP/1-UDP)
Parameters are separated by comma (no spaces needed). In case you don’t need to enter
parameter (Login/Pass) – do not put space, simply put comma and write next parameter.

Example: opa opa flush 353976012555151,banga,,,212.47.99.62,12050,0

Response details Description

FLUSH SMS Accepted FLUSH SMS Accepted
# records found on FLASH Number of records found on FLASH
Minimum Records to Send: # Number of minimum saved records to send
GPRS Enabled: # State of the GPRS connection, 0 – disabled; 1 – enabled
Time Sync: # Indicates time synchronization on the device, 0 – not
synchronized; 1 – synchronized

Example: FLUSH SMS Accepted. 11 records found on FLASH. Minimum Records to Send: 1.
GPRS Enabled: 1. Time Sync: 1.

6.1.17 sn #
Enables or disables Static navigation. 1 – enable, 0 – disable.

6.1.18 setkey # #
Changes device current configuration keyword.
Example: opa opa setkey 0101 3333
Here 0101 is an old keyword, 3333 is a new keyword.

If the keyword was not set, new keayword can be set using the same command.
Example: opa opa setkey 3333
Here 3333 is a new keyword

6.1.19 delkey #
Deletes device current configuration keyword.

61
 6.1.20 banlist
Gives a list of all banned operators.
Example when no operators are banned: 0000.00s.0.000

6.1.21 crashlog
Gives the last information before the device has crashed for unexpected reasons. It is
useful when the device acts unexpectedly or restars for unexplained reasons.
Example if no unexpected reset: “Crash: “
Example if unexpected reset was detected: “Crash: 3051,3052,3053”.

6.1.22 faultcodes
Command faultcode reads accurate vehicle fault code

Answer format:
(TYPE OF CONTROLLER):(ERROR type)(ERROR Code).

- “TYPE OF CONTROLLER”:
1. ENGINE CONTROLLER
2. ABS CONTROLLER
3. SRS CONTROLLER
4. TCM CONTROLLER
5. BCM CONTROLLER
- “ERROR type”
- “ERROR Code”.
Example:

ALL-CAN300 detected 4 DTC codes:

- ABS controller C0300;
- ENGINE controller P0300;
- SRS controller B0200;
- TCM controller U0100

Device answer:
„2:C0300,1:P0300,3:B0200,4:U0100“

If no faults are detectedin vehicle, the answer will be:

“No fault codes detected.”

Fault codes are written in international format, so it is easy to decript it.

A few links which help to decript DTC error codes:
http://www.totalcardiagnostics.com/support/Knowledgebase/Article/View/21/0/generic
manufacturer-obd2-codes-and-their-meanings
http://www.engine-codes.com/
http://www.obd-codes.com/trouble_codes/

62
6.1.23 dtcinfo
Command dtcinfo gives DTC information

“DTC information” possible answers:

- Ignition is off (DTC reading is not possible);
- DTC not supported by the program/compilation;
- Communication error;
- Communication error –diagnostic computer connected;
- Communication error –engine is working;

Module detects # DTC error codes (# -Number of DTC codes)

7 Debug mode
FM1100 is able to transmit its current state when connected to PC using USB cable. It is
used to detect errors and provide information to possible solutions when operating as
unexpected. Download Terminal from:
http://avl1.teltonika.lt/Downloads/Software/Terminal.zip.

After launching terminal choose baud rate 115200 and hardware control – none. Select
COM port which is assigned to “Virtual COM Port”. Click on ‘Start Log’ button and save a new file.
Then click ‘Connect’ to start receiving messages from FM1100.

Also you can log NMEA data directly. To get NMEA data, simply enter the following
command into the command field: .log_nmea:1$0a.

Figure 5 Terminal window for logging

63
8 Parameter List
8.1 Parameters value types
S8 – Signed Char
S8[n] – String of n Char
U8 – Unsigned Char
U16 – Unsigned Short
S32 – Signed Integer
U32 – Unsigned Integer
U64 – Unsigned Long Long Integer

8.2 System parameters

8.2.1 Sleep Mode (ID=1000)

Device has two sleep modes: sleep and deep sleep mode. While sleep is disabled (value 0)
module will never enter sleep mode, in sleep mode (value 1) module reduces level of power
usage by turning GNSS module to sleep, in deep sleep mode (value 2) module turns GNSS
module to sleep and switch GSM module off (note, that FM1100 do not receive SMS while in
deep sleep).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - U8

8.2.2 Sleep timeout (ID=200)

Sleep timeout is time after which FM1100 goes to sleep or deep sleep if other
requirements are met. It is measured in minutes.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
1 3000 - U8

8.2.3 Analog Input value range (ID=1001)

Analog input measuring resolution and range can be defined as 0…10V (value 0) or 1…30V
(value 1).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.2.4 Stop Detection Source (ID=1002)

Device can operate and change its working mode according to motion detection source:
ignition (value 0), movement sensor (value 1), GPS (value 2).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - U8

64
 8.2.5 Static Navigation (ID=1003)
When static navigation is enabled, FM1100 filters out GPS jumps, when it is not moving.
When it is disabled, it does not make any changes to collected GPS data.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 1 U8

8.2.6 Ignition Source (ID=1004)

Device can operate and change its working mode according to motion detection source:
Power Voltage (value 0), Digital Input 1 (value 1), movement (value 2).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

Ignition detection (ID=1920)

If ignition source is Power
voltage device can operate in 2
different ignition detection
regimes - Manual (value 0) and
Auto (value 1). In manual
regime power voltage high and
power voltage low levels need
to be set. In auto regime device
automatically detects system
voltage (6V, 12V or 24V) and
detects ignition according
default voltage ranges.
Minimum Maximum Recommended Goes with (
0 2 - value value value U8 param
Error! Reference
0 1 - Ignition dete
(ID=

8.2.7 Ignition detection

timeout (ID=1921)
When ignition source is
selected as Power Voltage and
Ignition detection is set as auto,
ignition timeout need to be set.
Minimum Maximum Recommended Goes with (
value value value param
0 65536 10 Error! Reference

65
 Ignition
(ID=
Power Voltage High Level
(ID=1005)
Power Voltage Low Level
(ID=1006)

8.2.8 Ignition detection (ID=1920)

If ignition source is Power voltage device can operate in 2 different ignition detection
regimes - Manual (value 0) and Auto (value 1). In manual regime power voltage high and power
voltage low levels need to be set. In auto regime device automatically detects system voltage (6V,
12V or 24V) and detects ignition according default voltage ranges.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Error! Reference source not found.
0 1 - Ignition detection timeout U8
(ID=1921)

8.2.9 Ignition detection timeout (ID=1921)

When ignition source is selected as Power Voltage and Ignition detection is set as auto,
ignition timeout need to be set.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Error! Reference source not found.
0 65536 10 Ignition detection U8
(ID=1920)

8.2.10 Power Voltage High Level (ID=1005)

When ignition source is selected as Power Voltage High level for ignition detection must be
set.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Ignition Source (ID=1004)
0 30000 - Power Voltage Low Level U16
(ID=1006)

8.2.11 Power Voltage Low Level (ID=1006)

When ignition source is selected as Power Voltage High level for ignition detection must be
set.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

66
 Ignition Source (ID=1004)

Ignition detection (ID=1920)

If ignition source is Power
voltage device can operate in 2
different ignition detection
regimes - Manual (value 0) and
Auto (value 1). In manual
regime power voltage high and
power voltage low levels need
to be set. In auto regime device
automatically detects system
voltage (6V, 12V or 24V) and
detects ignition according
default voltage ranges.
Minimum Maximum Recommended Goes with (
value value value param
Error! Reference
0 30000 - U16
0 1 - Ignition dete
(ID=

8.2.12 Ignition detection

timeout (ID=1921)
When ignition source is
selected as Power Voltage and
Ignition detection is set as auto,
ignition timeout need to be set.
Minimum Maximum Recommended Goes with (
value value value param
Error! Reference
0 65536 10 Ignition
(ID=
Power Voltage High Level
(ID=1005)

8.2.13 Records Saving/Sending (ID=201)

This parameter describes when records can be saved and sent to server: after position fix
(value = 0), always (value = 1), after time sync (value = 2).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 0 U8

67
 8.2.14 GNSS System (ID=202)
This parameter sets Satellite System, available values: 0 – GNSS (all available); 1 – GPS only;
2 – GLONASS only.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 0 U8

8.2.15 NSS fix Timeout (ID=1007)

This parameters defines GNSS fix Timeout for time synchronization via NTP.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
1 259200 - U8

8.2.16 Enable NTP – network time synchronization (ID=1008)

This parameter activates NTP network time synchronization, available values: 0 – disable,
1- enable.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
0 1 1 U8

8.2.17 GNSS fix timeout for the time synchronization (ID=1007)

Defines the time when GNSS fix is timeout and network time synchronization protocol is
activated. The input value contains time in seconds
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 259200 - U32

8.3 Records parameters

8.3.1 Sorting (ID=1010)

Record sorting parameter is responsible for record sorting order. Value of 0 arranging data
starting from newest, while value of 1 arranging data starting from oldest.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.3.2 Active Data Link Timeout (ID=1011)

Defines for how many seconds device will keep connection to the server after successful
data transfer while waiting for a new record.
Minimum Maximum Recommended Goes with (depends on) Value

68
 value value value parameters type
0 259200 - U32

8.3.3 Server Response Timeout (ID=1012)

Defines time period (in seconds) for server response to sent records.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
1 300 - U8

ATTENTION! Some GSM operators may disconnect the device from an

active data link if the device doesn’t send any data for a very long time, even if
active data link timeout is set to maximum value. The amount of time that an
operator keeps the link open depends solely on the operator. For example, if
active data link timeout is set to maximum, 259200 seconds (72 hours), and the
device sends data to server every 86400 seconds (24 hours), the operator might
disconnect the link earlier and the device will have to connect to the server anew.
This may cost extra, depending on the operator GPRS data charge. It is strongly
recommended, when using active data link timeout, that data sending to the
server should not be very rare (24 hours or more). If data sending is more
frequent, then the operator will not disconnect the device form the server.

8.4 GSM parameters

8.4.1 GPRS content activation (ID=1240)

Parameter allows or does not allow GPRS usage. If GPRS is not allowed value is 0, if GPRS is
allowed value is 1.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
APN Name (ID=1242)
0 1 - APN username (ID=1243) S8
APN Password (ID=1244)

8.4.2 APN Name (ID=1242)

Parameter defines GPRS Access Point Name.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
GPRS content activation (ID=1240)
32 char
Empty - APN username (ID=1243) S8[32]
string APN Password (ID=1244)

8.4.3 APN username (ID=1243)

Parameter defines APN username. In case operator does not use username for login,
value should be empty.

69
 Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
GPRS content activation (ID=1240)
30 char
Empty - APN Name (ID=1242) S8[30]
string APN Password (ID=1244)

8.4.4 APN Password (ID=1244)

Parameter defines APN password. In case operator does not use password for login, value
should be empty.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
GPRS content activation (ID=1240)
30 char
Empty - APN Name (ID=1242) S8[30]
string APN username (ID=1243)

8.4.5 Domain (ID=1245)

Parameter defines AVL data destination server IP address. Example: 212.47.99.62

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
31 char GPRS content activation (ID=1240)
0 - S8[16]
string Target Server Port (ID=1246)

8.4.6 Target Server Port (ID=1246)

Parameter defines AVL data destination server port number. Example: 12050
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
GPRS content activation (ID=1240)
Empty 65535 - U16
Domain (ID=1245)

8.4.7 Protocol (ID=1247)

Parameter defines GPRS data transport protocol. Module can use TCP or UDP transport
protocol to send data to server. For TCP protocol value is 0, for UDP protocol value is 1.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - GPRS content activation (ID=1240) U8

8.4.8 Always online (ID=1248)

Parameter allows keeping the link with a server open all the time. If Always online mode is
not allowed value is 0, if it is allowed value is 1.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type

70
 0 1 - S8

8.4.9 SMS Login (ID=1252)

User login is used to ensure module security. Used in every SMS that is sent to device.
Example: ba321
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Empty 5 char - SMS Password (ID=1253) S8[5]

8.4.10 SMS Password (ID=1253)

User password is used to ensure module security. Used in every SMS that is sent to device.
Example: ab123
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Empty 5 char - S8[5]

8.4.11 SMS data sending settings (ID=1250)

Parameter allows or does not allow sending AVL data using binary SMS. If SMS use is not
allowed value is 0 and 1 if SMS use is allowed.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
SMS Data send week time
0 1 - S8
schedule (ID=1273)

8.4.12 SMS Data send week time schedule (ID=1273)

Parameter defines SMS data sending according to week time schedule. This parameter is
used to set data sending on selected week days and hours. Minimum time step is 10 minutes.
Example value: 7F,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
For more information read 8.5.1.4 “Schedule parameter format”.

8.4.13 Authorized phone numbers (ID=1260-1269)

If at least one number is entered then only those number can send messages to device.
Number must be entered without “+” or “00”.
Example: 370XXXXXXXX
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
1 digit 16 digits - S8[17]
If SMS data sending is enabled (ID=1250) first value in a list is server GSM number. The SMS with
24 coordinates is sent to this number.

Deleting Authorized phone numbers: do no write any value is configuration SMS command.
Example: setparam 1260

71
 8.4.14 SMS Event PreDefined Numbers (ID=150-159)
In this field are written GSM numbers, to which will be sent “Event SMS” text message.
Number must be entered without “+” or “00”.
Example: 370XXXXXXXX
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
1 digit 16 digits - S8[17]

8.4.15 Operator List (ID=1271 X)

Parameter defines operator list. According to this list module selects operating profile.
GSM operator codes are comma separated. First in a list is Home Operator Code, then Preferred
Roaming Operator Codes are written.
X defines starting position that is changed: If X is from 0 to 49, X means index of operator
code which has to be configured. Up to 20 operator codes may be configured in 1 SMS. Example:
setparam 1271 16 24602,24603,24605
Here 16th, 17th and 18th operator codes are set. Note! Other operator codes are left
unchanged in the configuration.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
Empty 7 digits - U32

8.4.16 Black Operator list (ID= 1272 X)

Parameter defines the operator list. X defines the starting position that will be changed: If
X is between 0 and 49, X shows the index of the operator code from the blacklist (the operator
code has to be previously configured in the list). Up to 20 blacklist operator codes may be
configured in 1 SMS. Example: setparam 1272 16 24602,24603,24605.
Here 16th, 17th and 18th black operator codes are set. Note! Other operator codes are left
unchanged in the configuration.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
Empty 7 digits - U32

8.5 Data Acquisition Modes parameters

8.5.1 Home Network GSM operator code “Vehicle on STOP” parameters

8.5.1.1 Min Period (ID=1540)
This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type

72
 0 2592000 - U32

8.5.1.2 Min Saved Records (ID=1543)

This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1544).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
1 255 1 GPRS Week Time (ID=1545) U8

8.5.1.3 Send Period (ID=1544)

This parameter indicates frequency (time interval in seconds) of sending data to server.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

0 2592000 - Min Saved Records (ID=1543) U32

GPRS Week Time (ID=1545)
8.5.1.4 GPRS Week Time (ID=1545)
This parameter manages when it is allowed to open GPRS context. When module starts it is
prohibited to open the context. When modem’s GPRS context is closing (for example changing
network) it is allowed to open it only at a defined time. It is possible to allow connections every
10 minutes up to once per day.
Example value: 7F,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
Schedule parameter format:
Time is defined as 19 byte array (‘getparam’ 1545 returns 20 bytes). First byte of array
defines week days; the rest 18 bytes define timestamps with 10 minute interval. In first byte, first
bit (LSB) defines if module should connect to GPRS (send SMS) on Monday, second bit – on
Tuesday and so on up to seventh bit – which means Sunday. Eighth bit (MSB) is not used. If bits
value is 0 then device is not allowed to open GPRS context, but if it is already open – does not
close it. If value is 1 it will work as day minutes are defined in rest of the bytes. Day’s minutes are
defined by 18 bytes (144 bits). Every nth bit (beginning from the first bit (LSB) and ending 18 bytes
8th bit (MSB)) indicates every 10th minute of the day (day has 1440 minutes).
Sample: GPRS will be allowed on Monday to Friday at 8:00 and 16:00 GMT. The following
value should be configured:
00011111 00000000 00000000 00000000 000000000 00000000 00000000 00000001 00000000 00000000
00000000 00000000 00000000 000000001 00000000 00000000 00000000 00000000 00000000
Red bits indicate that GPRS will be allowed every day except Saturdays and Sundays. Blue
bits indicate 480 and 720 minutes (480min = 8h and 720min = 16h). So the parameter value
should be: 1F,00,00,00,00,00,00,01,00,00,00,00,00,01,00,00,00,00,00
It should be sent as UTF8 encoded string.

8.5.2 Home Network GSM operator code “Vehicle MOVING” parameters

8.5.2.1 Min Period (ID=1550)
This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.

73
 Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

Min Distance (ID=1551)

Min Angle (ID=1552)

0 2592000 - U32

Min Speed (ID=1556)

GPRS Week Time (ID=1555)

8.5.2.2 Min Distance (ID=1551)

This parameter indicates distance in meters in order to acquire new record. Record is
stored when the distance between previous records is greater than parameters value. If value is
0 it means no records by min distance will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1550)

Min Angle (ID=1552)

0 65535 - U32

Min Speed (ID=1556)

GPRS Week Time (ID=1555)

8.5.2.3 Min Angle (ID=1552)

This parameter indicates angle in degrees in order to acquire new record. If angle
difference between last recorded coordinate and current position is greater than defined value,
new record is stored. This parameter is operational, when speed is higher than 10km/h. If value
is 0 it means no records by min angle will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1550)

Min Distance (ID=1551)

0 180 - U16
Min Speed (ID=1556)

GPRS Week Time (ID=1555)

74
8.5.2.4 Min Speed (ID=1556)
This parameter indicaes speed difference in order to acquire new record. If speed
difference between last recorded coordinate and current position is greater than defined value,
new record is stored. If value is 0 it means no records by min distance will be saved. Minimum
value of Min Speed parameter is 10 km/h.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1550)

Min Distance (ID=1551)

0 255 10 Min Angle (ID=1552) U16

Min Speed Source (ID=1557)

GPRS Week Time (ID=1555)

8.5.2.5 Min Speed Source (ID=1557)

This parameter defines Source for speed difference calculation: 0 – GPS, 1 – LVCAN
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1550)

Min Distance (ID=1551)

0 1 0 Min Angle (ID=1552) U8

Min Speed (ID=1556)

GPRS Week Time (ID=1555)

8.5.2.6 Min Saved Records (ID=1553)

This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1554).

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type

75
 Min Period (ID=1550)

Min Distance (ID=1551)

1 255 1 Min Angle (ID=1552) U8

Min Speed (ID=1556)

GPRS Week Time (ID=1555)

8.5.2.7 Send Period (ID=1554)

This parameter indicates frequency (time interval in seconds) of sending data to server.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2592000 - U32
GPRS Week Time (ID=1555)

8.5.2.8 GPRS Week Time (ID=1555)

Read chapter 8.5.1.4.

8.5.3 Roaming Network GSM operator code “Vehicle on STOP” parameters

8.5.3.1 Min Period (ID=1560)

This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2592000 - U32
8.5.3.2 Min Saved Records (ID=1563)
This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1564).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
1 255 1 GPRS Week Time (ID=1565) U8

8.5.3.3 Send Period (ID=1564)

This parameter indicates frequency (time interval in seconds) of sending data to server.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Saved Records (ID=1563)
0 2592000 - U32
GPRS Week Time (ID=1565)

76
8.5.3.4 GPRS Week Time (ID=1565)
Read chapter 8.5.1.4.

8.5.4 Roaming Network GSM operator code “Vehicle MOVING” parameters

8.5.4.1 Min Period (ID=1570)

This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Distance (ID=1571)
Min Angle (ID=1572)
0 2592000 - Min Speed (ID=1576) U32

GPRS Week Time (ID=1575)

8.5.4.2 Min Distance (ID=1571)

This parameter indicates distance in meters in order to acquire new record. Record is
stored when the distance between previous records is greater than parameter’s value. If value is
0 it means no records by min distance will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1570)
Min Angle (ID=1572)
0 65535 - Min Speed (ID=1576) U32

GPRS Week Time (ID=1575)

8.5.4.3 Min Angle (ID=1572)

This parameter indicates angle in degrees in order to acquire new record. If angle
difference between last recorded coordinate and current position is greater than defined value,
new record is stored. This parameter is operational, when speed is higher than 10km/h. If value
is 0 it means no records by min angle will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1570)
Min Angle (ID=1572)
0 180 - Min Speed (ID=1576) U16

GPRS Week Time (ID=1575)

8.5.4.4 Min Speed (ID=1576)

This parameter indicaes speed difference in order to acquire new record. If speed
difference between last recorded coordinate and current position is greater than defined value,

77
new record is stored. If value is 0 it means no records by min distance will be saved. Minimum
value of Min Speed parameter is 10 km/h.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1570)
Min Distance (ID=1571)
Min Angle (ID=1572)
0 255 10 Min Speed Source (ID=1577) U16

GPRS Week Time (ID=1575)

8.5.4.5 Min Speed Source (ID=1577)

This parameter defines Source for speed difference calculation: 0 – GPS, 1 – LVCAN
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1570)
Min Distance (ID=1571)
Min Angle (ID=1572)
0 1 0 Min Speed (ID=1576)
U8

GPRS Week Time (ID=1575)

8.5.4.6 Min Saved Records (ID=1573)

This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1574).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1570)
Min Distance (ID=1571)
Min Angle (ID=1572)
1 255 1 Min Speed (ID=1576)
U8

GPRS Week Time (ID=1575)

8.5.4.7 Send Period (ID=1574)

This parameter indicates frequency (time interval in seconds) of sending data to server.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Saved Records (ID=1573)
0 2592000 - U32
GPRS Week Time (ID=1575)

78
8.5.4.8 GPRS Week Time (ID=1575)
Read chapter 8.5.1.4.

8.5.5 Unknown Network GSM operator code “Vehicle on STOP” parameters

8.5.5.1 Min Period (ID=1580)

This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2592000 - U32

8.5.5.2 Min Saved Records (ID=1583)

This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1584).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
1 255 1 U8
GPRS Week Time (ID=1585)

8.5.5.3 Send Period (ID=1584)

This parameter indicates frequency (time interval in seconds) of sending data to server.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Saved Records (ID=1583)
0 2592000 - U32
GPRS Week Time (ID=1585)

8.5.5.4 GPRS Week Time (ID=1585)

Read chapter 8.5.1.4.

8.5.6 Unknown Network GSM operator code “Vehicle MOVING” parameters

8.5.6.1 Min Period (ID=1590)
This parameter indicates time interval in seconds in order to acquire new record. If value is
0 it means no records by min period will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Distance (ID=1591)
Min Angle (ID=1592)
0 2592000 - Min Speed (ID=1596) U32
Min Speed Source (ID=1597)
GPRS Week Time (ID=1595)

79
8.5.6.2 Min Distance (ID=1591)
This parameter indicates distance in meters in order to acquire new record. Record is
stored when the distance between previous records is greater than parameter’s value. If value is
0 it means no records by min distance will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1590)
Min Angle (ID=1592)
0 65535 - U32
Min Speed (ID=1596)
GPRS Week Time (ID=1595)

8.5.6.3 Min Angle (ID=1592)

This parameter indicates angle in degrees in order to acquire new record. If angle
difference between last recorded coordinate and current position is greater than defined value,
new record is stored. This parameter is operational, when speed is higher than 10km/h. If value
is 0 it means no records by min angle will be saved.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1590)
Min Distance (ID=1591)
0 180 - U16
Min Speed (ID=1596)
GPRS Week Time (ID=1595)

8.5.6.4 Min Speed (ID=1596)

This parameter indicaes speed difference in order to acquire new record. If speed
difference between last recorded coordinate and current position is greater than defined value,
new record is stored. If value is 0 it means no records by min distance will be saved. Minimum
value of Min Speed parameter is 10 km/h.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1590)
Min Distance (ID=1591)
0 255 1 Min Angle (ID=1592) U16
Min Speed Source (ID=1597)
GPRS Week Time (ID=1595)

8.5.6.5 Min Speed Source (ID=1597)

This parameter defines Source for speed difference calculation: 0 – GPS, 1 – LVCAN
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1590)
Min Distance (ID=1591)
0 1 0 Min Angle (ID=1592) U8
Min Speed (ID=1596)
GPRS Week Time (ID=1595)

80
8.5.6.6 Min Saved Records (ID=1593)
This parameter defines minimum number of records in one data packet that can be sent to
server. It has higher priority than Data Send Period (ID=1594).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Min Period (ID=1590)
Min Distance (ID=1591)
1 255 1 Min Angle (ID=1592) U8
Min Speed (ID=1596)
GPRS Week Time (ID=1595)

8.5.6.7 Send Period (ID=1594)

This parameter indicates frequency (time interval in seconds) of sending data to server. In
order to send data to server GPRS parameters must be enabled
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

0 2592000 - Min Saved Records (ID=1593) U32

GPRS Week Time (ID=1595)

8.5.6.8 GPRS Week Time (ID=1595)

Read chapter 8.5.1.4.

8.6 Features Parameters

8.6.1 Green driving scenario (ID=1890)

This parameter lets enable/disable Green driving scenario. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.6.2 Green Driving digital output control (ID=1891)

This parameter defines digital output control on Green Driving scenario. 0 – disable, 1 –
DOUT1, 2 – DOUT2.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - Green driving scenario (ID=1890) U8

8.6.3 Green Driving source (ID=1909)

This parameter defines green driving scenario source. 0 – GPS, 1 – Accelerometer.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

81
 0 1 - Green driving scenario (ID=1890) U8

8.6.4 Max Acceleration Force (ID=1892)

It is max allowed acceleration force which can be reached while accelerating without
triggering harsh acceleration event.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0.25 0.85 0.25 Green driving scenario (ID=1890) Float

8.6.5 Max Braking Force (ID=1893)

It is max allowed braking force which can be reached while braking without triggering
harsh braking event.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0.25 0.85 0.35 Green driving scenario (ID=1890) Float

8.6.6 Max Cornering Force (ID=1894)

It is max allowed cornering force which can be reached while cornering without triggering
harsh cornering event.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0.1 1.0 0.3 Green driving scenario (ID=1890) U16
Reference for Max Cornering Force values:
• 0,4 – 0,45 G force – items that are left on the back seat start to slide to the side while the
car is on turn;
• 0,75 – 0,95 G force – most of the cars loose grip on turn (normal environment conditions).

8.6.7 Overspeeding scenario (ID=1895)

This parameter enables/disables Overspeeding scenario. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.6.8 Over Speeding digital output control (ID=1896)

This parameter defines digital output control on Overspeeding scenario. 0 – disable, 1 –
DOUT1, 2 – DOUT2.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - Overspeeding scenario (ID=1895) U8

8.6.9 Max allowed speed (ID=1897)

This parameters defines max allowed speed on Overspeeding scenario.

82
 Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 260 - Overspeeding scenario (ID=1895) U8

8.6.10 Jamming scenario (ID=1898)

This parameter enables/disables Jamming scenario. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.6.11 Jamming digital output control (ID=1899)

This parameter defines digital output control on Jamming scenario. 0 – disable, 1 – DOUT1,
2 – DOUT2.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - Jamming scenario (ID=1899) U8

8.6.12 Jamming sensitivity (ID=1900)

This parameter defines Jamming sensitivity. 0 – low sensitivity (50 RSSI), 1 – medium
sensitivity (30 RSSI), 2 – high sensitivity (10 RSSI).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 3 - Jamming scenario (ID=1899) U8

8.6.13 Jamming Timeout (ID=1901)

This parameter represents DOUT turning on timeout when jamming is detected.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Jamming scenario (ID=1899)
0 65535 60 Jamming digital output control U16
(ID=1899)

8.6.14 Jamming Pulse duration (ID=1902)

This parameter defines the Jamming Pulse duration after which DOUT is turned on.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Jamming scenario (ID=1899)
0 65535 0 Jamming digital output control U16
(ID=1899)

83
8.6.15 Immobilizer scenario (ID=1903)
This parameter lets enable/disable Immobilizer scenario. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.6.16 Immobilizer digital output control (ID=1904)

This parameter defines digital output control on Immobilizer scenario. 0 – disable, 1 –
DOUT1, 2 – DOUT2.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
0 2 - Immobilizer scenario (ID=1903) U8

8.6.17 iButton list checking (ID=1905)

This parameter enables/disables iButton list chenking. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Immobilizer scenario (ID=1903)
0 1 - U8
iButtons list (ID=3500-3999 )

8.6.18 Immobilizer ignition off timeout (ID=1906)

This parameter represents ignition off timeout, after which DOUT is turned on.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Immobilizer scenario (ID=1903)
Immobilizer digital output
5 65353 30 U8
control (ID=1904)
iButtons list (ID=3500-3999 )

8.6.19 iButton detect (ID=1907)

This parameter enables/disables iButton detect scenario. 0 – disable, 1 – enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
iButton detection digital output
0 1 - U8
control (ID=1908)

8.6.20 iButton detect digital output control (ID=1908)

This parameter defines digital output control on iButton detect scenario. 0 – disable, 1 –
DOUT1, 2 – DOUT2.

84
 Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
iButton detect scenario
0 2 - U8
(ID=1907)

8.6.21 Trip (ID=1280)

This parameter enables ability to detect START and STOP of the trip.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - U8

8.6.22 Start Speed (ID=1281)

This parameter represents speed, which is detected as minimum speed to indicate TRIP
START and generate event.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 255 - Trip (ID=1280) U8

8.6.23 Ignition Off Timeout (ID=1282)

This parameter represents timeout to wait if ignition is off in order to detect TRIP STOP and
generate event.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 65535 - Trip (ID=1280) U16

8.6.24 Trip Continuous distance counting (ID=1283)

For this feature I/O#11 Trip distance must be enabled. If I/O Trip distance is enabled, and
Continuous distance counting variable is set to Continuous (value 1), TRIP distance is going to be
counted continuously (from TRIP start to TRIP stop) and shown as I/O Trip distance value.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Trip (ID=1280)
0 1 - I/O#11 – Trip Distance (ID = 1410- U8
1415)

8.6.25 Remember iButton ID (ID=1284)

This parameter enables/disables Remember iButton ID functionality. 0 – disable, 1 –
enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Trip (ID=1280)
0 1 - U8
iButton List (ID=3500-3999 )

85
8.6.26 Odometer value (ID=1285)
This parameter represents start odometer value.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#27 – Total distance (ID=1130-
0 - - U8
1135)

8.6.27 Geofencing
In this chapter it is explained how to get all parameters for the first Geofence zone (all ID
numbers are for the 1st zone). And at the end of the chapter (part 8.6.10) is presented a table
with the IDs of all the rest Geofence zones.

8.6.27.1 Frame border (ID=1020)

Geofence border thickness, measured in meters.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1000000 1000 All Geofencing parameters U32

8.6.27.2 Geofence Zone #1 Shape (ID=1030)

Geofence shape parameter can be: circle – value 0; rectangle – value 1.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 - All Geofencing parameters U8

8.6.27.3 Geofence Zone #1 Priority (ID=1031)

Parameter defines Geofence priority: 0 is low, 1 – high, 2 – panic;
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 2 - All Geofencing parameters U8

8.6.27.4 Geofence Zone #1 Generate Event (ID=1032)

Generate event on:
a) No event – value 0
b) On entering zone – value 1;
c) On exiting zone – value 2;
d) On both – value 3;
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 3 - All Geofencing parameters U8

86
8.6.27.5 Geofence Zone #1 Longitude (X1) (ID=1033)
Parameter has two meanings dependent on zone shape. If shape is a rectangle, then
ID=10333 is left down corner X coordinate. If shape is a circle, then ID=1033 is center of that
circle X coordinate.
Sample value: 25.30528
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
-180 180 - All Geofencing parameters Float

8.6.27.6 Geofence Zone #1 Latitude (Y1) (ID=1034)

Parameter has two meanings dependent on zone shape. If shape is a rectangle, then
ID=1034 is left down corner Y coordinate. If shape is a circle, then ID=1034 is center of that circle
Y coordinate.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
-90 90 - All Geofencing parameters Float

8.6.27.7 Geofence Zone #1 Longitude (X2) (ID=1035)

Parameter has two meanings depending on zone shape. If shape is a rectangle, then
ID=1035 is right upper corner X coordinate. If shape is a circle, then ID=1035 is radius of circle
with center of ID=1033 and ID=1034.

For rectangle:
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
-180 180 - All Geofencing parameters Float

For circle:
Minimum Maximum Recommend Goes with (depends on) Value
value value ed value parameters type
0 1000000 1000 All Geofencing parameters Float

8.6.27.8 Geofence Zone #1 Latitude (Y2) (ID=1036)

If shape is rectangular, then ID=1036 is right upper corner Y coordinate. If shape circle,
ID=1036 is not used.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
-90 90 - All Geofencing parameters Float
Other 4 GeoFence zone’s parameters have the same logic as shown in GeoFence Zone #1.
GeoFence Geofence
Zone Zone’s
Number parameters

87
 1 1030-1036
2 1040-1046
3 1050-1056
4 1060-1066
5 1070-1076

8.6.28 AutoGeofencing
8.6.28.1 Enable/Disable (ID=1101)
Enable – value 1; disable – value 0;
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 1 U8

8.6.28.2 Activation Timeout (ID=1102)

Parameter represents AutoGeofencing activation timeout in seconds.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 65535 60 Enable/Disable (ID=1101) U16

8.6.28.3 Deactivate by (ID=1100)

Parameter defines Autogeofence deactivation source. Value 1 is dedicated for attached
iButton, value 0 – for Ignition.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Enable/Disable (ID=1101)
0 1 - U8
iButton List (ID=3500-3999 )

8.6.28.4 AutoGeofence event Priority (ID=1103)

Parameter defines AutoGeofence event priority: 0 is low, 1 – high;
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Enable/Disable (ID=1101)
0 1 1 AutoGeofence event generating
U8
(ID=1104)

8.6.28.5 AutoGeofence event generating (ID=1104)

Generate event: 0 – no event, 1 – on entering zone; 2 – on exiting zone; 3 – on both;
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Enable/Disable (ID=1101)
0 3 2 AutoGeofence event Priority U8
(ID=1103)

88
8.6.28.6 Radius (ID=1105)
Parameter represents radius of circle with center device coordinates after activating
AutoGeofence feature.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
Enable/Disable (ID=1101)
0 1000000 100 U32
Deactivate by (ID=1100)

8.6.29 iButton List (ID=3500-3999 )

Read 5.4.4.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
FFFFFFFF Immobilizer scenario (ID=1903)
0 - U64
FFFFFFFF iButtons list checking (ID=1905)
8.7 I/O parameters
I/O properties are additional data sources which are recorded along with usual GPS data.

8.7.1 I/O#1 property parameter (ID=1300)

Parameter defines I/O property value. Possible values: enabled (1), disabled (0).
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type

I/O#1 priority (ID=1301)

I/O#1 High level (ID=1302)

0 1 - S8
I/O#1 Low level (ID=1303)
I/O#1 logic operand (ID=1304)
I/O#1 averaging length (ID=1305)

8.7.2 I/O#1 priority (ID=1301)

Parameter defines I/O property type of priority: 0 is low, 1 – high, 2 – panic.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#1 property parameter
(ID=1300)

0 2 0 I/O#1 High level (ID=1302) S8

I/O#1 Low level (ID=1303)

I/O#1 logic operand (ID=1304)

89
 I/O#1 averaging length (ID=1305)

8.7.3 I/O#1 High level (ID=1302)

Parameter defines high value of triggered I/O property. This parameter is used to set
thresholds for I/O properties to generate events.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#1 property parameter (ID=1300)

I/O#1 priority (ID=1301)

-2147483647 2147483647 1 S32
I/O#1 Low level (ID=1303)
I/O#1 logic operand (ID=1304)
I/O#1 averaging length (ID=1305)

8.7.4 I/O#1 Low level (ID=1303)

Parameter defines low value of triggered I/O property. This parameter is used to set
thresholds for I/O properties to generate events.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#1 property parameter (ID=1300)

I/O#1 priority (ID=1301)

-2147483647 2147483647 0 S32
I/O#1 High level (ID=1302)
I/O#1 logic operand (ID=1304)
I/O#1 averaging length (ID=1305)

8.7.5 I/O#1 logic operand (ID=1304)

Parameter defines when event is sent: 0 – on range exit, 1 – on range entrance, 2 – both,
3 – monitoring, 4 – hysteresis, 5 – on changes.

90
 Minimal Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#1 property parameter
(ID=1300)

I/O#1 priority (ID=1301)

0 4 3 S8
I/O#1 High level (ID=1302)

I/O#1 Low level (ID=1303)

I/O#1 averaging length (ID=1305)

8.7.6 I/O#1 averaging length (ID=1305)

Parameter defines I/O property sample length to average. If no averaging needed default
value is 1.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
I/O#1 property parameter
(ID=1300)

I/O#1 priority (ID=1301)

0 2592000 1 S32
I/O#1 High level (ID=1302)

I/O#1 Low level (ID=1303)

I/O#1 logic operand (ID=1304)

Other I/O property elements can be configured in same logic. All I/O element parameters
are listed in the next table.

I/O element
I/O Element Number
parameters
Digital Input 1 1300-1305
Digital Input 2 1310-1315
Digital Input 3 1320-1325
Analog Input 1 1330-1335
Digital Output 1 1340-1345
Digital Output 2 1350-1355
GNSS PDOP 1360-1365
GNSS HDOP 1370-1375
External Voltage 1380-1385
GNSS Power 1390-1395
Movement Sensor 1400-1405
Trip Distance 1410-1415
GSM Operator 1420-1425

91
 Speed (Km/h) 1430-1435
iButton ID 1440-1445
Mode 1450-1455
GSM Signal 1460-1465
Deep Sleep 1470-1475
Cell ID 1480-1485
Area Code 1490-1495
Dallas Temperature 1 1500-1505
Reserved 1510-1515
Reserved 1520-1525
Reserved 1530-1535
Reserved 1110-1115
Ignition 1120-1125
Total Distance 1130-1135
Reserved IO1 1140-1145
Reserved IO2 1150-1155
LLS Fuel1 1720- 1725
LLS Temp1 1730- 1735
LLS Fuel2 1740- 1745
LLS Temp2 1750- 1755
LLS Fuel3 1760- 1765
LLS Temp3 1770- 1775
LLS Fuel4 1780- 1785
LLS Temp4 1790- 1795
LLS Fuel5 1800- 1805
LLS Temp5 1810- 1815
Dallas Temperature 2 1820- 1825
Dallas Temperature 3 1830- 1835
Dallas Temperature 4 1840- 1845
Dallas Temperature ID 1 1850- 1855
Dallas Temperature ID 2 1860- 1865
Dallas Temperature ID 3 1870- 1875
Dallas Temperature ID 4 1880- 1885

8.8 SMS event configuration

8.8.1 I/O#1 element SMS event configuration (ID=100)

Command sets SMS warning on I/O#1 element.
SMS Format: setparam X Y,W,Z
X – ID
Y – Enable/Disable (1/0)
W – Telephone number INDEX (See 8.4.18 SMS Event Predefined Numbers paragraph, ID
150 – INDEX 0; ID151 – INDEX 1, …)
Z – SMS Text

92
 Example: “setparam 100 1,5,Digital Input 1 Event!”

Other I/O element SMS events can be configured in same logic. All I/O element SMS event
IDs are listed in the next table.
LV-CAN200 is configured
Element name (default SMS Event
ID
Text)
Digital Input 1 100
Digital Input 2 101
Digital Input 3 102
Analog Input 1 103
Digital Output 1 104
Digital Output 2 105
GNSS PDOP 106
GNSS HDOP 107
External Voltage 108
GNSS Status 109
Movement Sensor 110
Trip distance 111
GSM Operator 112
Speed 113
iButton ID 114
Data Mode 115
GSM Signal 116
Deep Sleep 117
Cell ID 118
Area Code 119
Dallas Temperature 1 120
Ignition 125
Total Distance 126
Reserved 127
Reserved 128
LVC Vehicle Speed 129
LVC Accelerator Pedal Position 130
LVC Fuel Consumed 131
LVC Fuel Level (liters) 132
LVC Engine RPM 133
LVC Total Mileage 134
LVC Fuel Level (percent) 135
LVC Program Number 136
Green Driving 137
OverSpeeding 138
Jamming detection 139
Immobilizer 140
Trip 141

93
 Geofence Zone 1 142
Geofence Zone 2 143
Geofence Zone 3 144
Geofence Zone 4 145
Geofence Zone 5 146
AutoGeofence 147

ALL-CAN300 configured
Element name (default SMS Event Text) ID
Digital input 1 100
Digital input 2 101
Digital input 3 102
Analog input1 103
Digital output 1 104
Digital output 2 105
GNSS PDOP 106
GNSS HDOP 107
External voltage 108
GNSS Status 109
Movement sensor 110
Trip Distance 111
GSM operator code 112
Speed 113
iButton ID 114
Data mode 115
GSM signal 116
Deep Sleep 117
GSM Cell ID (CID) 118
GSM Location Area Code (LAC) 119
Dallas Temperature 1 120
Digital input 4 121
Analog input 2 122
Battery voltage 123
Battery current 124
Ignition 125
Total distance 126
Reserved for future use 127
Reserved for future use 128
LVCAN Vehicle Speed 129
LVCAN Accelerator pedal position 130
LVCAN Fuel Consumed 131
LVCAN Fuel level (liters) 132
LVCAN Engine RPM 133
LVCAN Total Mileage 134

94
LVCAN Fuel level (percent) 135
LVCAN Program number 136
Green Driving 137
Overspeeding 138
Jamming detection 139
Immobilizer 140
Trip 141
Geofence 1 142
Geofence 2 143
Geofence 3 144
Geofence 4 145
Geofence 5 146
AutoGeofence 147
LVC ModuleID 210
LVC Engine Work time 211
LVC Engine Work time(counted) 212
LVC Total Mileage (counted) 213
LVC Fuel Consumed (counted) 214
LVC Fuel Rate 215
LVC AdBlue Level (percent) 216
LVC AdBlue Level (liters) 217
LVC Engine Load 218
LVC Engine Temperature 219
LVC Axle 1 Load 220
LVC Axle 2 Load 221
LVC Axle 3 Load 222
LVC Axle 4 Load 223
LVC Axle 5 Load 224
LVC Control State Flags 225
LVC Agricultural Machinery Flags 226
LVC Harvesting Time 227
LVC Area of Harvest 228
LVC Mowing Efficiency 229
LVC Grain Mown Volume 230
LVC Grain Moisture 231
LVC Harvesting Drum RPM 232
LVC Gap Under Harvesting Drum 233
LVC Security State Flags 234
LVC Tacho Total Vehicle Distance 235
LVC Trip Distance 236
LVC Tacho Vehicle Speed 237
LVC Tacho Driver Card Presence 238
LVC Driver1 States 239
LVC Driver2 States 240

95
LVC Driver1 Continuous Driving Time 241
LVC Driver2 Continuous Driving Time 242
LVC Driver1 Cumulative Break Time 243
LVC Driver2 Cumulative Break Time 244
LVC Driver1 Duration Of Selected Action 245
LVC Driver2 Duration Of Selected Action 246
LVC Driver1 Cumulative Driving Time 247
LVC Driver2 Cumulative Driving Time 248
RFID 250
LLS Fuel1 251
LLS Temp1 252
LLS Fuel2 253
LLS Temp2 254
LLS Fuel3 255
LLS Temp3 256
LLS Fuel4 257
LLS Temp4 258
LLS Fuel5 259
LLS Temp5 260
LVC Driver1 ID High 262
LVC Driver1 ID Low 263
LVC Driver2 ID High 264
LVC Driver2 ID Low 265
LVC Battery Temperature 266
LVC Battery Level 267
LVC Door Status 268
LVC DTC Errors 269
Dallas Temperature 2 270
Dallas Temperature 3 271
Dallas Temperature 4 272
Dallas Temperature 1 ID 273
Dallas Temperature 2 ID 274
Dallas Temperature 3 ID 275
Dallas Temperature 4 ID 276
LVCAN_SlopeOfArm 277
LVCAN_RotationOfArm 278
LVCAN_EjectOfArm 279
LVCAN_HorizontalDistArmVechicle 280
LVCAN_HeightArmAboveGround 281
LVCAN_DrillRPM 282
LVCAN_AmountOfSpreadSaltSquareMeter 283
LVCAN_BatteryVoltage 284
LVCAN_AmountSpreadFineGrainedSalt 285
LVCAN_AmountSpreadCoarseGrainedSalt 286

96
 LVCAN_AmountSpreadDiMix 287
LVCAN_AmountSpreadCoarseGrainedCalcium 288
LVCAN_AmountSpreadCalciumChloride 289
LVCAN_AmountSpreadSodiumChloride 290
LVCAN_AmountSpreadMagnesiumChloride 291
LVCAN_AmountSpreadGravel 292
LVCAN_AmountSpreadSand 293
LVCAN_WidthPouringLeft 294
LVCAN_WidthPouringRight 295
LVCAN_SaltSpreaderWorkHours 296
LVCAN_DistanceDuringSalting 297
LVCAN_LoadWeight 298
LVCAN_RetarderLoad 299
LVCAN_CruiseTime 300
LVACN_CNG Status 301
LVCAN_CNG Used 302
LVCAN_CNG Level 303
LVCAN Oil level 304

8.9 LV-CAN parameters

8.9.1 LVCAN mode (ID=1600)

This parameter sets LVCAN/ALLCAN detection, available values: 0 – Auto Detect, 1 –
LVCAN200, 2 – ALLCAN300.

Minimum Maximum Recommended Goes with (depends on) Value

value value value parameters type
0 2 0 U8

8.9.2 Send data with 0, if ignition is off (ID=1601)

This parameter enables/disables data sending with 0 value, if ignition is off. 0 – disable, 1-
enable.
Minimum Maximum Recommended Goes with (depends on) Value
value value value parameters type
0 1 1 U8

FM1100 with LV-CAN200 and ALL-CAN300 Can Adapters

8.10 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 FM1100 device is able to collect and send vehicle data.

97
 ALL-CAN300
U
LV-CAN200 Connection SB FM11YX
cable

USB Cable
U
PC SB FM11YX

Figure 53 connection block diagram

FM1100 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)

8.11 LV-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.

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.

98
 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:

8.11.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.

99
 8.11.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 the SWITCH, then LED starts blinking and counting fourth digit on program
number
• To stop counter push SWITCH
• Release SWITCH, if programming is succeded LED will blink 10 times

Figure 54 Adapter signaling led

8.12 Connecting FM1100 Can adapters ALL-CAN300 and LV-CAN200

Connect USB Plug to FM1100 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 connection is optional it depends on exact car model.

100
 For exact pinout see sticker on Light Vehicles Can adapter.

Figure 55 LV-CAN200 Adapter connection cable pinout

Figure 56 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.

8.13 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

101
 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.

8.14 FM11 Configuration

FM1100 shares the same USB port for connecting LV-CAN200 or ALL-CAN300 adapter and
configuring device with PC.
FM1100 can be configured using “SCAN” function or “Offline Configuration” (Figure 58)

102
 SCAN function – is in use when FM1100 is connected to CAN adapter (Figure 57), then wait
10s (Note, that car engine must be started), disconnect adapter from FM1100, and connect PC
USB cable to FM1100 Device (Figure 57). It is very important not to disconnect FM1100 from
power source during this operation, because if FM1100 is reconnected all received CAN bus data
will be lost. FM1100 remembers received data from LV-CAN200 or ALL-CAN300 and at the end of
the procedure when “SCAN” button is pressed, user will see all CAN data which is sent by
adapter. Enable CAN data which needs send to server and save configuration pressing “Save”
button.

To configure CAN data:

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

LV-CAN200 Connection
U
All-CAN300 cable SB FM1100

Figure 57 Connect adapter LV-CAN100 to FM1100

Figure 58 Connect FM1100 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.

Offline configuration – 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

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

104
 Figure 59 Configurator example

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

Send data with 0, if ignition is off. Depending on LVCAN/ALLCAN I/O parameters and
ignition status, FMA110 can send locked (last known) LVCAN/ALLCAN I/O parameters values,
reset values (set to 0) and active (real time) parameters values. When ignition is off,
LVCAN/ALLCAN I/O parameters values sent to server are:

Speed reset
Accelerator pedal position reset
Total fuel used lock
Fuel level (liters) lock
Engine RPM reset
Total mileage lock
Fuel level (proc.) lock
Program number lock
Module ID lock
Number of DTC reset
Engine Work Time lock
Engine Work Time (counted) lock
Total Mileage (counted) lock
Fuel Consumed (counted) lock

105
 Fuel Rate reset
AdBlue Level (percent) 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

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 “FMXXXX Protocols” document. List of
available CAN bus data, parameter size, ID and value range you can find in table 9.1 and 9.2.

106
 Table 9.1 ACQUIRED LV- CAN200 PARAMETRS IO ID
Category name Param index (signal) name Size Param IO Value range
(Bytes) ID
65265 – Cruise 0 Vehicle Speed 1 81 0-250 km/h
Control/Vehicle Speed
61443 – Electronic 1 Accelerator 1 82 0-100 %
Engine Controller #2 Pedal Position

65257 – Fuel 2 Total Fuel Used 4 83 0-99999999 liters*

Consumption
65276 – Dash Display 3 Fuel Level [liters] 2 84 0-255 liters
61444 – Electronic 4 Engine RPM 2 85 0-8200 rpm
Engine Controller #1
65217 – High Resolution 5 Vehicle Distance 4 87 0-2145000000 meters
Vehicle Distance
65276 – Dash Display 6 Fuel Level [%] 1 89 0-100 %
Program number 7 LV-CAN200 4 100 0-999
Program number
o
8 Engine 1 115 C x 10
Engine Temperature
temperature
Door Status 9 Door status 2 90 Min – 0, Max – 16128 **
CNG Status 10 CNG Status 1 190
CNG Used 11 CNG Used 4 191
CNG Level 12 CNG level 2 192
Oil level 13 Oil level 1 193

NOTE:
* „Total Fuel Used“ is sent to server multiplied by 10.
Example: if value was 150.5 liters, „1505“ will be sent to server.
** 0 - all doors are closed,
256 - front felt door is opened,
512 - front right door is opened,
1024 - rear left door is opened,
2048 - rear right door is opened,
4096 – hood is opened,
8192 – trunk is opened,
16128 – all doors are opened or combinations of values.

Table 9.2 ACQUIRED ALL-CAN300 PARAMETRS IO ID

Param Param IO Measurement a1 Remarks
Property Input Size (Bytes)
index ID units
ALL-CAN300 29 4 100 - -
Program number
Module ID 30 8 101 - -
Engine Work Time 31 4 102 min 1

107
 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 40 1 111 proc. 1
(percent)
AdBlue Level (liters) 41 2 112 Ltrs * 10 0.1
Engine RPM 42 2 85 - 1
43 1 114 proc. 1 Valid range:
Engine Load
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
9.2.1
Agricultural 53 8 124 - - see table
Machinery Flags 9.2.1
Harvesting Time 54 4 125 min 1
Area of Harvest 55 4 126 m2 1
2
Mowing Efficiency 56 4 127 m /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
9.2.1
Tacho Total Vehicle 62 4 133 m 1
Distance

108
 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 9.2.1
66 1 137 - - see table
Driver1 States
9.2.1
67 1 138 - - see table
Driver2 States
9.2.1
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 81 1 152 proc. 1
(percent)
Number of DTC 82 1 160 - -

NOTE:
„Total Fuel Used“ is sent to server multiplied by 10.
Example: if value was 150.5 liters, „1505“ will be sent to server.

Table 9.2.1 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

109
 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
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

110
 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):
Every two bits in this byte correspond to a different
CAN bus number.
00 – CAN not connected, connection not
required
01 – CAN connected, but currently module not
received data
10 – CAN not connected, require connection
11 – CAN connected

111
 Example: Byte0 - 0F hex – 00001111 binary
CAN4, CAN3, CAN2, CAN1
Byte1:
Not used
Byte2:
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.
Byte3:
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
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 – revers 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:
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

112
 Byte7:
Not used
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
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

8.15 SMS Configuration

CAN Bus IO elements can be configured remotely via SMS command. First ID number is
always ‘2’, seconds ID number is always ‘0’. Third ID number refers to specific LV-CAN200 or ALL-
CAN300 IO element (table 9.3). And the last ID number refers to sections – Property; Generation
Type; Low and High levels (Table 9.4).
Here’s example:
ID 2013 – configures Accelerator Pedal position parameter “High Level”.

Table 9.3 LV-CAN200 and ALL-CAN300 IO elements SMS configuration Ids range
ALL-CAN300 and LV-CAN200 IO Elements 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

113
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
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
Door status 2530-2534
LVCAN DTC Errors 2540-2544
LVCAN Slope Of Arm 2550-2554
LVCAN Rotation Of Arm 2560-2564
LVCAN Eject Of Arm 2570-2574
LVCAN Horizontal Dist. Arm Vehicle 2580-2584
LVCAN Height Arm Above Ground 2590-2594
LVCAN Drill RPM 2600-2604
LVCAN Amount Of Spread Salt Square
2610-2614
Meter
LVCAN Battery Voltage 2620-2624
LVCAN Amount Spread Fine Grained
2630-2634
Salt
LVCAN Amount Spread Coarse
2640-2644
Grained Salt
LVCAN Amount Spread DiMix 2650-2654
LVCAN Amount Spread Coarse
2660-2664
Grained Calcium

114
 LVCAN Amount Spread Calcium
2670-2674
Chloride
LVCAN Amount Spread Sodium
2680-2684
Chloride
LVCAN Amount Spread Magnesium
2690-2694
Chloride
LVCAN Amount Spread Gravel 2700-2704
LVCAN Amount Spread Sand 2710-2714
LVCAN Width Pouring Left 2720-2724
LVCAN Width Pouring Right 2730-2734
LVCAN Salt Spreader Work Hours 2740-2744
LVCAN Distance During Salting 2750-2754
LVCAN Load Weight 2760-2764
LVCAN Retarder Load 2770-2774
LVCAN Cruise Time 2780-2784

Table 9.4 LV-CAN200 and 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.5 – Allowed
2xx3 High Level Values
2xx4 Averaging Constant From 0 to 232

Table 9.5 LV-CAN200 and ALL-CAN300 IO parameters allowed values

LV-CAN200 IO Element Minimum Maximum
value value
Speed 0 250
Accelerator pedal position 0 100
Total fuel used 0 99999999
Fuel level (liters) 0 100
Engine RPM 0 8200
Vehicle distance 0 2145000000
Fuel level (proc.) 0 100
Program number 0 999

115
8.16 CAN Program Number request by SMS

CAN program number can be obtained via SMS:

SMS Text: “ lvcangetprog ”
Response: “CAN Program Nr: XXX”

8.17 Get CAN info by SMS

Full LV-CAN information via SMS:

SMS Text: “lvcangetinfo”
Response:
“Prog: 139
SWRevison: 6
KernVer: 10
KernVar: 49
MdlID: 8884443332221110”

8.18 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 x”
Possible values of x:
0 – Engine work time (counted);
1 – Fuel Consumed (counted);
2 – Vehicle Mileage (counted);

116
9 MOUNTING RECOMMENDATIONS
9.1 Connecting Wires
• Wires should be connected while module is not plugged in.
• Wires should be fastened to the other wires or non-moving parts. Try to avoid heat
emitting and moving objects near the wires.
• The connections should not be seen very clearly. If factory isolation was removed while
connecting wires, it should be applied again.
• If the wires are placed in the exterior or in places where they can be damaged or exposed
to heat, humidity, dirt, etc., additional isolation should be applied.
• Wires cannot be connected to the board computers or control units.

9.2 Connecting Power Source

• Be sure that after the car computer falls asleep, power is still available on chosen wire.
Depending on car, this may happen in 5 to 30 minutes period.
• When module is connected, be sure to measure voltage again if it did not decrease.
• It is recommended to connect to the main power cable in the fuse box.

9.3 Connecting Ignition Wire

• Be sure to check if it is a real ignition wire – power does not disappear while starting the
engine.
• Check if this is not an ACC wire (when key is in the first position, most electronics of the
vehicle are available).
• Check if power is still available when you turn off any of vehicles devices.
• Ignition is connected to the ignition relay output. As alternative, any other relay, which
has power output, when ignition is on, may be chosen.

9.4 Connecting Ground Wire

• Ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.
• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.
• For better contact scrub paint from the place where loop is connected.

PAY ATTENTION! Connecting the power supply must be carried out in a

very low impedance point on-board vehicle network. These points in the car
are the battery terminals. Therefore, we recommend connecting the power of
FM1100 (wire GND and POWER) directly to the battery terminals. Another valid
option is to connect the wires to the main POWER cable inside the fuse box (if
there is none, then to the power supply where the fuses of vehicle’s computer
are), wire GND must be connected in a special point, designed to connect GND
vehicle computer. Connecting the GND at an arbitrary point to the mass of the
car is unacceptable, as static and dynamic potentials on the line GND will be
unpredictable, which can lead to unstable FM1100 and even its failure.

117
9.5 Connecting Antennas
• When placing antennas avoid easily reached places.
• Avoid GNSS antenna placement under metal surfaces.
• Avoid placing FM1100 device near car radio, speakers or alarm systems.
• GNSS antenna must be placed so its state is as horizontal as possible (if antenna is leant
more than 30 degrees, it is considered incorrect mounting).
• GNSS antenna cable cannot be bent more than 80 degrees.
• GNSS antenna must be placed sticker facing down

Figure 60 Correct GNSS antenna mounting

It is recommended to place GNSS antenna behind dashboard as close to the window as

possible. A good example of GNSS antenna placement is displayed in a picture below (area
colored green).

Figure 61 Correct placement of FM1100

9.6 Module Installation

• Module should not be seen or easily reached.
• Module should be firmly fixed to the surface or cables.
• Module cannot be fixed to heat emitting or moving parts.
• SIM card should be inserted in the module while the connector is plugged off (while
module has no power).

118
10 CHANGE LOG

Versio
Nr. Date Comments
n
1 2011-04-15 0.3 Preliminary draft release.
2 2011-04-20 0.4 Preliminary draft release update.
3 2011-04-21 0.5 Preliminary draft release update.
4 2011-04-26 0.6 Preliminary draft release update.
5 2011-04-27 0.7 Preliminary draft release update.
6 2011-05-12 0.8 Preliminary draft release update.
7 2011-05-27 0.9 Preliminary draft release update.
8 2011-06-02 0.10 Preliminary draft release update.
9 2011-06-21 0.11 Preliminary draft release update.
10 2011-07-28 0.12 Preliminary draft release update.
11 2011-08-18 0.13 Preliminary draft release update.
12 2011-10-19 0.14 TTJ connection scheme update.
13 2011-11-02 0.15 Static Navigation mode added.
14 2011-12-19 0.16 Geofence zone #1 event configuration values corrected
15 2012-01-12 0.17 -Immobilizer relay description change (3.7)
-“GPS Power” I/O element added on I/O elements list (5.14)
-“Green Driving value” in bytes changed (5.14)
-Other minor changes
16 2012-02-02 0.18 Corrections in “Terminal” screen.
17 2012-02-03 0.19 Corrected Min Max Values of (Active Data Timeout, APN,
APN Username, Operator list, Min Period, Min send period,
start speed, max cornering velocity, frame border, For Circle
X2, High level, Low level, Average), name from Max Conering
Angle to Max Angular Velocity, enable/disable,
autogeofencing parameters values. Added new SMS
command readops #,
18 2012.03.16 1.0 Release. Changes in style. Minor changes in description.
Numeration of tables and figures corrected. Added “PAY
ATTENTION” box for Connecting Power Source and Ground
Wire. Screenshot changes. Updated “GPS features”.
Updated SMS command list.
19 2012.06.13 1.1 Fixed errors on pages 50-62
20 2012.06.14 1.2 SMS Event functionality added
21 2012.07.03 1.21 Detailed description of SMS Event functionality
22 2012.09.24 1.22 Minor changes
23 2012.09.27 1.23 ID value fixed
24 2012.10.02 1.24 Minor changes
25 2012.10.17 1.25 SMS Event configuration over SMS added
26 2012.10.18 1.26 Operational principals, Sleep modes paragraphs modified.

119
 Sleep mode parameter ID edited.
27 2012.10.26 1.27 Chapter 6.1.7 SMS command “getinfo” description update
Fixed parameters IDs in chapters 8.5.6.1, 8.5.6.2 and 8.5.6.3.
28 2013.01.17 1.28 FM1100M and FM1100M+2SIM versions support added.
29 2013.03.13 1.29 AIN measurement error and additional error values added.
30 2013.07.18 1.31 Updated I/O settings.
31 2013.10.01 1.32 Removed unused RILS system description.
32 2013.10.15 1.33 Corrections in chapter 6 and chapter 8.
33 2013.10.17 1.34 Colours added in chapter 8.5.1.4
34 2013.10.22 1.35 Changed max sleep timeout value.
35. 2013.12.06 1.36 Minor changes
36. 2013.12.12 1.37 Minor change in paragraph 8.8.1
37. 2013.12.23 1.38 Minor changes in paragraph 5.2 SLEEP MODES
38. 2014.01.29 1.39 Minor changes on command getweektime description.
39. 2014.02.26 1.40 Minor changes in chapter 4.1
40. 2014.03.10 1.41 Protocols information corrected;
41. 2014.03.18 1.42 Added more detailed GPS power parameter description.
42. 2014.03.26 1.43 Edited I/O element description table in chapter 5.16
43. 2014.06.04 1.45 Change pic. Immobilizer relay connection
44 2014.08.05 1.46 Updated Autogeofencing information.
45 2014.09.29 1.47 Added system parameter GNSS. Added note, about ibutton
averaging.
46 2014.10.06 1.48 Recovered GGPS and GetGPS sms commands.
47 2014.11.07 1.49 Added note for deleting authorized phone numbers.
Added GNSS System SMS configuration description.
48 2015.02.23 1.50 Added overvoltage description
49 2015.05.20 2.00 New version release for new base firmware 01.11.xx:
Added Ignition Source description;
New SMS configutation Ids;
New SMS Events; Added LV-CAN200 description;
50 2015.05.25 2.01 LV-CAN200 power supply voltage correction
51 2015.06.12 2.02 Ignition Source SMS IDs correction
52 2015.06.22 2.03 Port and Protocol SMS ID correction
53 2015.06.23 2.04 Minor changes
54 2015.07.13 2.05 Minor correction
55 2015.07.16 2.06 Features dependence on configured Ignition Source
description added.
56 2015.07.24 2.07 Operator List configuration SMS ID correction
57 2015.08.06 2.08 SMS events updated. I/O element parameters numbers
correction
58 2015.09.14 2.09 Maximum number of records in memory correction
59 2015.10.05 3.00 New version release for new base firmware 01.14.xx:
Returned back old SMS configuration Ids
60 2015.10.05 3.01 Minor correction; removed dual SIM description

120
61 2015.10.08 3.02 Jamming detection description added
62 2015.10.22 3.03 Minor LV-CAN sms command value correction
63 2015.12.28 4.01 New version release for new base firmware 01.17.xx:
Added data acqusition settings parameters MinSpeed and
MinSpeedSource descriptions, and sms configuration IDs.
Some figures updated. Minor corrections.
64 2015.12.30 4.02 Minor corrections

65 2016.04.21 4.03 Updated info about Static Navigation feature;

Updated info about LVCAN I/O elements size and data
structure.
66 2016.07.2 5.00 New version release for new base firmware 01.19.xx:
Added new time sychronization via NTP (Network Time
Protocol)
Added ALL-CAN300 documentation with IO ID

67 2016-08-22 5.01 Corrected Virtual COM Port driver download link

68 2016-09-14 5.02 LV-CAN200 I/O description update

69 2016-10-05 5.03 Updated ALLCAN300 information

Added ALLCAN300 IO element values table
Added NTP parameter information.
70 2016-10-27 5.04 Added SMS commands for configuration keyword.

71 2016-11-16 5.05 Corrected SMS event configuration Ids.

72 2017-01-05 5.06 Added SIMPLE-CAN documentation

73 2017-02-08 5.07 Added parameter ID to change LVCAN mode.

74 2017-02-09 5.08 Setdigout command description updated

75 2017-03-20 5.09 New version release for new base firmware 01.24.xx
Always online mode description added, ID added;
Black operator list description and IDs added;
Scenarios: Green driving, Overspeeding, Jamming detection,
Immobilizer descriptions and IDs updated;
Continuous odometer description added;
Remember iButton functionality description added;
New I/O element 16 Total distance (Virtual odometer)
added;
setdigoutX Z Y description added;
GNSS fix Timeout parameter ID added;
Parameter “Odometer value” name was changed to “Trip

121
 distance”;
Added 4 TTJ ID I/O elements, “getcontsens” command
added;
LVCAN description updated: Send data with 0, if ignition is
off, new I/O elements: Door Status detection and Reserved
for future use added;
Reference Max Cornering Force values description added.
76 2017-03-21 5.10 LVCAN mode and Send data with 0, if ignition is off
parameters Ids added.

77 2017-04-07 5.11 Corrected energy consumption in Deep Sleep value;

Trip distance (ID=1285) renamed to Odometer value
(ID=1285);
I/O GNSS power description updated.
78 2017-05-25 5.12 Updated LVCAN200 and ALLCAN300 description.
79 2017-06-07 5.13 Maximum message length for SMS events changed to 40
symbols.
80 2017-07-27 5.14 New version release for new base firmware 01.27.xx
Updated DeepSleep description;
Added iButton detect scenario description;
Added Immobilizer ignition off timeout parameter ID;
Added command „setkey“ description;
Updated readable iButton amount, IDs;
Added new ALL-CAN parameter “Numbers of DTC“;
Added supported iButton types list;
Added new LVOVAN parametre “Oil level”.
81 2017-08-18 5.15 SMS command “setdigout“ description modified;
Green driving scenario description modified.
Data acquisition mode min speed description modified;
Permanent I/O elements table modified;
LV-CAN200 parameters ID description modified.
82 2017-10-31 5.16 ALL-CAN300 Security state flags description improved;
Information about program numbers changes added;
Dallas temeprature ID and dallas temperture parameters IDs
modified;
Record saving/sending parameter description modified;
Green driving source paremeter modified.
83 2018-02-15 5.17 Green Driving Scenario description modified;
Scenario settings jamming detection description is modified;
Ignition detection and ignition detection timeout
parameters description added.

122