Device configuration via SMS

Quick Start Guide

2015/11
VILNIUS

0
Table of Contents
1 Preface........................................................................................................................ 2
1.1 Introduction .......................................................................................................... 2
1.2 Legal information.................................................................................................. 2
1.3 Document change log ........................................................................................... 2
2 General information ................................................................................................... 3
3 Enabling SMS configuration ........................................................................................ 4
4 SMS command “setcfg” .............................................................................................. 5
4.1 Exceptional cases .................................................................................................. 5
4.1.1 Send data without GPS fix............................................................................... 5
4.1.2 Custom ignition .............................................................................................. 7
4.1.3 CAN interface enable, mode selection ............................................................ 9
4.1.4 CAN active/silent .......................................................................................... 10
4.1.5 LCV manufacturer group............................................................................... 12
4.1.6 LCV manufacturer subgroup ......................................................................... 14
4.1.7 CAN auto baud rate ...................................................................................... 17
4.1.8 GSM Jamming configuration ......................................................................... 19
4.1.9 Parameter recalculation ............................................................................... 19
4.2 Response to “setcfg”........................................................................................... 19
5 SMS command “setioparam” .................................................................................... 20
5.1 Response to “setioparam” .................................................................................. 22
6 SMS command “getcfg” ............................................................................................ 23
6.1 Response to “getcfg” .......................................................................................... 23
7 SMS command “getioparam”.................................................................................... 24
7.1 Response to “getioparam” .................................................................................. 24
8 All configurable FM4 Device parameters .................................................................. 25

1
1 Preface
1.1 Introduction
SMS configuration solution enables users to change any configuration parameter via SMS command. User
is required to know an ID for the specific parameter and then provide a value for it. Users are now
available to change device configuration in remote locations where GPRS is unavailable. This is also very
useful for users who prefer to send configuration to their devices via SMS.

1.2 Legal information

Copyright © 2015 Ruptela. All rights reserved. Reproduction, transfer, distribution or storage of parts or
all of the contents in this document in any form without the prior written permission of Ruptela is
prohibited. Other products and company names mentioned in this document are trademarks or trade
names of their respective owners.

1.3 Document change log

Date Version Change details
2015-11-24 1.0 Initial draft

2
2 General information
Currently SMS configuration is supported by FM-Tco4, FM-Tco4 (LCV), FM-Pro4 and FM-Eco4/4+/light
devices. SMS configuration functionality mainly relays on two SMS messages:
setcfg command allows to change all parameters, however there are few exceptions.
setioparam command is used only for setup IO parameters.

Additionally, there are two SMS commands that can be used to receive the current device configuration:
getcfg command is only used to get the current status of the selected parameter.
getioparam command is only used to get the current status of the selected IO parameter.

Note
One SMS message can be 160 symbols long, so the maximum number of simultaneously transmitted
or received parameters in one SMS message is limited.

Configurable parameters
All configurable FM4 Device parameters can be found at chapter 8: “All configurable FM4 Device parameters”.

3
3 Enabling SMS configuration
SMS configuration feature is enabled/disabled in configuration tool.
1. In Authorized numbers section click on “Options” button.
2. In the “Numbers” popup window put a tick in the Enable SMS configuration check box.

Note
SMS configuration feature has to be manually enabled or disabled. This is done in the configuration tool.
This is one of the configuration parameters that cannot be changed via SMS command.

4
4
Setcfg command allows to change all parameters, except Timetable, Passwords (configuration and SMS)
and “Enable SMS configuration”. SMS can be written in lowercase and uppercase letters, because SMS
commands are not case sensitive. Only parameters provided with SMS will be changed, others will remain
the same.
Configurable parameter ID’s with possible values can be found in the “All configurable FM4 Device
parameters” chapter, at the end of this document.

Structure of the “setcfg” message

It is mandatory to enter a correct password “Password” followed by a single space “ ” symbol. Then
command “setcfg” is entered, which is again followed by a single space “ ” symbol. After that enter
parameter ID number “ID” followed by a single space “ ” symbol and parameter value “Value1”. If you
need to set few different parameters, then after the first parameter value enter a comma symbol and
add a single space symbol “, ”. Enter parameter ID number “ID2” followed by a single space “ ” symbol
and parameter value “Value2”. Continue for as many parameters as necessary. Final SMS message should
have a similar structure to the one provided below:
Password setcfg ParamID1 Value1, ParamID2 Value2, ParamID3 Value3, …

Examples
Usually parameter configuration is very straight forward as described above. Below you will find few
simple examples that illustrate this case:
Set GPRS transport protocol to “TCP”:
Password setcfg 100 0
Set IP1 to “www.kompanija.com” and IP1 Port number to “6002”:
Password setcfg 110 www.kompanija.com, 120 6002
Set IP2 to “123.000.111.222” and IP2 Port number to “13242”:
Password setcfg 111 123.000.111.222, 121 13242

4.1 Exceptional cases

4.1.1 Send data without GPS fix
Parameters for Sending data without GPS fix are enabled/disabled via value stored in a special register
(size 1 Byte). Each bit within this 1 Byte has a parameter assigned to it (see table below). Parameter is
enabled, when the corresponding bit in the register is set to 1. If bit value is 0, then the corresponding
parameter is disabled. Values for all bits have to be set with one SMS message. To do this you will have
to determine a correct decimal number and use it as a value, when using Sending data without GPS
feature (ID = 147).

5
First you have to decide what parameters you are going to use. This determines the bit pattern within
the register. Set corresponding bits to 1, all unused parameters are set to 0. Now read bit values from
this register starting from the left. You will have a number in binary format. Translate it to the number in
Decimal format. This is a number that needs to be included in the SMS message to configure the Sending
data without GPS fix.

Enable Sending data without GPS fix

Use time synchronization: NTP
Use time synchronization: GPS
Collect data without time
b7 b6 b 5 b4 b3 b2 b1 b0

1 Byte

Examples
Enable Sending data without GPS fix. Configuration with "Collect data without time" enabled and
"Use time synchronization: NTP".
Enable Sending data without GPS fix
Use time synchronization: NTP
Use time synchronization: GPS
Collect data without time

0 0 0 0 1 1 0 1
Reading register values from the left we obtain: 00001101
Number in binary format: 1101BIN
Number in decimal format: 13DEC

6
 SMS message for Sending data without GPS fix enabled, configuration with "Collect data without
time" enabled and "Use time synchronization: NTP":
Password setcfg 147 13

Sending data without GPS fix enabled, configuration with "Collect data without time" enabled.

Reading register values from the left we obtain: 00001001

Number in binary format: 1001BIN
Number in decimal format: 9DEC

SMS message for Sending data without GPS fix enabled, configuration with "Collect data without
time" enabled:
Password setcfg 147 9

4.1.2 Custom ignition

Custom ignition parameter falls under “Profile settings” parameters. It is possible to configure four
different Profiles. Having in mind “Configuration via SMS” functionality it is important to know that each
profile is represented by a single number N (N=1, 2, 3 or 4). This number is the first part of the “Profile
settings” parameter ID’s. This composite parameter ID has he following structure: NParamID. It is
mandatory to specify a profile number for each “Profile settings” parameter. All parameters and their
ID’s that fall under “Profile settings” can be found in “All configurable FM4 Device parameters” chapter,
at the end of this document.
Custom ignition functionality is enabled, when Engine detection (ID = N123) is set on “Custom”. Then
parameters for Custom ignition are enabled/disabled via value stored in a special register (size 2 Bytes).
Each bit within these 2 Bytes has a parameter assigned to it (see table below). Parameter is enabled,
when the corresponding bit in the register is set to 1. If bit value is 0, then the corresponding parameter
is disabled. Values for all bits have to be set with one SMS message. To do this you will have to determine
a correct decimal number and use it as a value for Custom ignition (ID = N105).
First you have to decide what parameters you are going to use. This determines the bit pattern within
the register. Set corresponding bits to 1, all unused parameters are set to 0. Now read bit values from
this register starting from the left. You will have a number in binary format. Translate it to the number in
Decimal format. This is a number that needs to be included in the SMS message to configure the Custom
ignition.

7
 Power supply voltage
Wheel based speed

Mov Sensor
GPS speed

DIN4
DIN3
DIN2
DIN1
RPM
b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b 3 b2 b1 b0

1 Byte 1 Byte

Examples
Custom ignition configuration with "GPS speed", "RPM" and "DIN4" enabled.

Power supply voltage

Wheel based speed

Mov Sensor
GPS speed

DIN4
DIN3
DIN2
DIN1
RPM

0 0 0 0 0 0 0 1 0 1 0 0 1 0 0 0

Reading register values from the left we obtain: 0000000101001000

Number in binary format: 101001000BIN
Number in decimal format: 328DEC

SMS message for Engine detection (ID = 123) on “Custom” and Custom ignition (ID = 105)
configuration on 2nd profile with "GPS speed", "RPM" and "DIN4" enabled:
Password setcfg 2123 4, 2105 328

Custom ignition configuration with "DIN4", "DIN3", "DIN2" and "DIN1" enabled.
Reading register values from the left we obtain: 0000000000001111
Number in binary format: 1111BIN
Number in decimal format: 15DEC

SMS message for Engine detection (ID = 123) on “Custom” and Custom ignition (ID = 105)
configuration on 2nd profile with "DIN4", "DIN3", "DIN2" and "DIN1" enabled:
Password setcfg 2123 4, 2105 15

8
 Custom ignition configuration with "Mov Sensor" enabled.
Reading register values from the left we obtain: 0000000000010000
Number in binary format: 10000BIN
Number in decimal format: 16DEC

SMS message for Engine detection (ID = 123) on “Custom” and Custom ignition (ID = 105)
configuration on 2nd profile with "Mov Sensor" enabled:
Password setcfg 2123 4, 2105 16

4.1.3 CAN interface enable, mode selection

Since there are two CAN interfaces available, configuration can be done for both of them. Configurations
for different interfaces are separated one from another by splitting associated registers in two.
Enabling and setting mode to CAN1 and CAN2 is done by entering a correct value in a mode selection
register (size 1 Byte). This time we will employ hexadecimal number notation to represent values in the
register as it is more convenient in this case. Register contains two hexadecimal numbers. One number
slot is associated with CAN1 interface, another with CAN2 (see table below).

Note
Enabling and setting mode for CAN1 and CAN2 interfaces is done with a single number in decimal format.
This number is a value for parameter ID = 201. It means that both interfaces are configured at the same
time, with one SMS message.

Decide which interface/interfaces you are going to use. This determines value pattern within the register.
There are five modes available, each represented by a different hexadecimal number from 1 HEX to 5HEX
(see “All configurable FM4 Device parameters table” for more information). Also a number 0HEX, if
interface is disabled. Choose interface/interfaces and set corresponding value/values in the register. Now
read values from this register starting from the left. You will have a number in hexadecimal format.
Translate it to the number in Decimal format. This is a number that needs to be included in the SMS
message to configure the chosen CAN interface/interfaces.
CAN2

CAN1

FHEX FHEX

1 Byte
Examples
Consider a case for a LCV profile configuration. LCV mode is represented by a number 2 HEX.
Configuration will be done for CAN2. CAN1 will be disabled. For CAN2 set corresponding number
to 2HEX and for CAN1 enter 0 HEX. Now read values from this register starting from the left. You will

9
 obtain a number in hexadecimal format. Translate it to the number in Decimal format. This is a
number that needs to be included in the SMS message to configure the chosen CAN interface.

CAN2

CAN1
2HEX 0HEX

Reading register values from the left we obtain: 20

Number in hexadecimal format: 20HEX
Number in decimal format: 32DEC

SMS message that would set CAN2 interface in “LCV” mode (CAN1 disabled):
Password setcfg 201 32

Consider a case for a “FMS” and “Tacho read” configuration. FMS mode is represented by a
number 1HEX. “FMS” will be configured for CAN2. CAN1 will be configured with “Tacho read”.
Tacho read mode is represented by a number 4HEX. For CAN2 set corresponding number in register
to 1HEX and for CAN1 enter 4HEX. Now read values from this register starting from the left. You will
obtain a number in hexadecimal format. Translate it to the number in Decimal format. This is a
number that needs to be included in the SMS message to configure the chosen CAN interface.

Reading register values from the left we obtain: 14

Number in hexadecimal format: 14HEX
Number in decimal format: 20DEC

SMS message that would set CAN2 interface to “FMS” mode, CAN1 to “Taco read” mode:
Password setcfg 201 20

4.1.4 CAN active/silent

Setting CAN1 or CAN2 on active/silent is done by entering a correct value in an active/silent regime
selection register (size 1 Byte). Hexadecimal number notation is used to represent values in the register.
Register contains two hexadecimal numbers. One number slot is associated with CAN1 interface, another
with CAN2 (see table below).

Note
Regime for CAN1 and CAN2 interfaces is configured with a single number in decimal format. This number
is a value for parameter ID = 200. It means that both interfaces are configured at the same time, with one
SMS message.

10
Decide which interface/interfaces you are going to use. This determines value pattern within the register.
There are two regimes available, each represented by a different hexadecimal number 1HEX - active and
0HEX - silent (see “All configurable FM4 Device parameters” table for more information). Choose
interface/interfaces and set corresponding value/values in the register. Now read values from this
register starting from the left. You will have a number in hexadecimal format. Translate it to the number
in Decimal format. This is a number that needs to be included in the SMS message to configure the chosen
CAN interface/interfaces.

CAN2

CAN1
FHEX FHEX

1 Byte

Note
Active/silent regime for CAN1 and CAN2 interfaces can be set only when “FMS”, “LCV” and “MobilEye”
modes are enabled.

Examples
Set CAN “active” regime for CAN2 interface and CAN “silent” to CAN1 interface. For CAN2 set
corresponding number to 1HEX and for CAN1 enter 0HEX. Now read values from this register starting
from the left. You will obtain a number in hexadecimal format. Translate it to the number in
Decimal format. This is a number that needs to be included in the SMS message to configure the
chosen CAN interface.
CAN2

CAN1

1HEX 0HEX

Reading register values from the left we obtain: 10

Number in hexadecimal format: 10HEX
Number in decimal format: 16DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201) would also be included in the message.
For now we replace this part with PramID Value.

11
 Only part that illustrates how to set CAN2 interface to “active” and CAN1 to “silent” is given with
real numbers:
Password setcfg PramID Value, 200 16

(Full example. CAN1 disabled. CAN2 interface enabled, mode set to “FMS” and regime set to
“active”. SMS would look like this: Password setcfg 201 16, 200 16).

Set CAN “active” regime for CAN1 interface and CAN “silent” to CAN2 interface. For CAN1 set
corresponding number to 1HEX and for CAN2 enter 0 HEX. Now read values from this register starting
from the left. You will obtain a number in hexadecimal format. Translate it to the number in
Decimal format. This is a number that needs to be included in the SMS message to configure the
chosen CAN interface.

Reading register values from the left we obtain: 01

Number in hexadecimal format: 1HEX
Number in decimal format: 1DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201) would also be included in the message.
For now we replace this part with PramID Value.
Only part that illustrates how to set CAN1 interface to “active” and CAN2 to “silent” is given with
real numbers:
Password setcfg PramID Value, 200 1

Password setcfg 201 1, 200 1).

4.1.5 LCV manufacturer group

Setting LCV manufacturer group to CAN1 and CAN2 is done by entering a correct value in a manufacturer
group register (size 4 Bytes). Hexadecimal number notation is used to represent values in the register.
Register contains eight hexadecimal numbers. Four number slots (2 Bytes) are associated with CAN1
interface, another 4 slots (2 Bytes) with CAN2 (see table below).

Note
Setting LCV manufacturer group for CAN1 or CAN2 interfaces is done with a single number in decimal
format. This number is a value for parameter ID = 202. It means that both interfaces are configured at
the same time, with one SMS message.

12
LCV manufacturer group and subgroup can be set for one interface only. Decide which interface you are
going to use. This determines numbers pattern within the register. There are twenty five LCV
manufacturer groups available, each represented by a different hexadecimal number from 1 HEX to 25HEX
(see “All configurable FM4 Device parameters” table for more information). Also a number 0HEX, if
interface is not configured or number slots are unused. Choose interface and set corresponding values in
the register (right most slots should be filed first). Now read values from this register starting from the
left. You will have a number in hexadecimal format. Translate it to the number in Decimal format. This is
a number that needs to be included in the SMS message to configure the chosen CAN interface.

CAN2

CAN1
FHEX FHEX FHEX FHEX FHEX FHEX FHEX FHEX

2 Bytes 2 Bytes

Examples
Consider a case for a LCV profile configuration, where CAN2 is set to “VOLVO” manufacturer
group. VOLVO is represented by a number 13HEX. Configuration will be done for CAN2. CAN1 will
be disabled. For CAN2 fill corresponding slots with number 13 HEX, unused slots should be set to
0HEX. For CAN1 enter 0HEX. Now read values from this register starting from the left. You will obtain
a number in hexadecimal format. Translate it to the number in Decimal format. This is a number
that needs to be included in the SMS message to configure the chosen CAN interface.
CAN2

CAN1

0HEX 0HEX 1HEX 3HEX 0HEX 0HEX 0HEX 0HEX

Reading register values from the left we obtain: 00130000

Number in hexadecimal format: 130000HEX
Number in decimal format: 1245184DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer subgroup
parameter (ID = 203), etc. would also be included in the message. For now we replace these
parameters with PramID1 Value1, ParamID2 Value2.
Only part that illustrates how to set manufacturer group for CAN2 interface to VOLVO (CAN1
unused) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, 202 1245184

13
 (Full example. CAN1 disabled. CAN2 interface enabled, mode set to “LCV”, auto baud rate enabled
and manufacturer set to “VOLVO”. SMS would look like this: Password setcfg 201 32, 208 16, 202
1245184).

Consider a case for a LCV profile configuration, where CAN1 is set to “FORD” manufacturer group.
FORD is represented by a number 4HEX. Configuration will be done for CAN1. CAN2 will be unused.
For CAN1 fill corresponding slot with number 4HEX, unused slots should be set to 0HEX. For CAN2
enter 0HEX. Now read values from this register starting from the left. You will obtain a number in
hexadecimal format. Translate it to the number in Decimal format. This is a number that needs to
be included in the SMS message to configure the chosen CAN interface.

Reading register values from the left we obtain: 00000004

Number in hexadecimal format: 4HEX
Number in decimal format: 4DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer subgroup
parameter (ID = 203), etc. would also be included in the message. For now we replace these
parameters with PramID1 Value1, ParamID2 Value2.
Only part that illustrates how to set manufacturer group for CAN1 interface to “FORD” (CAN2
unused) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, 202 4

(Full example. CAN2 disabled. CAN1 interface enabled, mode set to “LCV”, auto baud rate
enabled and manufacturer set to “FORD”. SMS would look like this: Password setcfg 201 2, 208
1, 202 4).

4.1.6 LCV manufacturer subgroup

Setting LCV manufacturer group is only half of the job. You also need to specify a manufacturer subgroup
for CAN1 or CAN2. Similarly, this is done by entering a correct value in a manufacturer subgroup register
(size 4 Bytes). Hexadecimal number notation is used to represent values in the register. Register contains
eight hexadecimal numbers. Four number slots (2 Bytes) are associated with CAN1 interface, another 4
slots (2 Bytes) with CAN2 (see table below).

14
Note
Setting LCV manufacturer subgroup for CAN1 or CAN2 interfaces is done with a single number in decimal
format. This number is a value for parameter ID = 203. It means that both interfaces are configured at
the same time, with one SMS message.

LCV manufacturer group and subgroup can be set for one interface only. Decide which interface you are
going to use. This determines numbers pattern within the register. Depending on manufacturer group
that is used, there are different numbers of LCV manufacturer subgroups available, each represented by
a different hexadecimal number from 1HEX to NHEX (see “All configurable FM4 Device parameters” table
for more information). Also a number 0HEX, if interface is not configured or number slots are unused.
Choose interface and set corresponding values in the register (right most slots should be filed first). Now
read values from this register starting from the left. You will have a number in hexadecimal format.
Translate it to the number in Decimal format. This is a number that needs to be included in the SMS
message to configure the chosen CAN interface.
CAN2

CAN1

FHEX FHEX FHEX FHEX FHEX FHEX FHEX FHEX

2 Bytes 2 Bytes

Examples
Consider a case for a LCV profile configuration, where CAN2 is set to “VOLVO3” manufacturer
subgroup. VOLVO3 is represented by a number 3HEX. Configuration will be done for CAN2. CAN1
will be disabled. For CAN2 fill corresponding slot with number 3HEX, unused slots should be set to
0HEX. For CAN1 enter 0HEX. Now read values from this register starting from the left. You will obtain
a number in hexadecimal format. Translate it to the number in Decimal format. This is a number
that needs to be included in the SMS message to configure the chosen CAN interface.
CAN2

CAN1

0HEX 0HEX 0HEX 3HEX 0HEX 0HEX 0HEX 0HEX

Reading register values from the left we obtain: 00030000

Number in hexadecimal format: 30000HEX
Number in decimal format: 196608DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer group parameter

15
(ID = 202), etc. would also be included in the message. For now we replace these parameters with
PramID1 Value1, ParamID2 Value2.
Only part that illustrates how to set manufacturer subgroup for CAN2 interface to “VOLVO3”
(CAN1 unused) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, 203 196608

(Full example. CAN1 disabled. CAN2 interface enabled, mode set to “LCV”, auto baud rate
enabled, manufacturer set to “VOLVO” and manufacturer subgroup set to “VOLVO3”. SMS would
look like this: Password setcfg 201 32, 208 16, 202 1245184, 203 196608).

Consider a case for a LCV profile configuration, where CAN1 is set to “FORD5” manufacturer
subgroup. FORD5 is represented by a number 5HEX. Configuration will be done for CAN1. CAN2 will
be unused. For CAN1 fill corresponding slot with number 5HEX, unused slots should be set to 0HEX.
For CAN2 enter 0HEX. Now read values from this register starting from the left. You will obtain a
number in hexadecimal format. Translate it to the number in Decimal format. This is a number
that needs to be included in the SMS message to configure the chosen CAN interface.

Reading register values from the left we obtain: 00000005

Number in hexadecimal format: 5HEX
Number in decimal format: 5DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer group parameter
(ID = 202), etc. would also be included in the message. For now we replace these parameters with
PramID1 Value1, ParamID2 Value2.
Only part that illustrates how to set manufacturer subgroup for CAN1 interface to “FORD5” (CAN2
unused) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, 203 5

(Full example. CAN2 disabled. CAN1 interface enabled, mode set to “LCV”, auto baud rate
enabled, manufacturer set to “FORD” and manufacturer subgroup set to “FORD5”. SMS would
look like this: Password setcfg 201 2, 208 1, 202 4, 203 5).

Another SMS example with a proper LCV profile configuration that includes multiple parameters
and their values is provided below. Let’s enable CAN2 interface, set vehicle manufacturer group
to “TOYOTA”, subgroup to “TOYOTA2”, CAN interface regime “CAN active”:
Password setcfg 201 32, 202 524288, 203 131072, 200 16

16
4.1.7 CAN auto baud rate
Setting auto baud rate for CAN1 or CAN2 is done by entering a correct value in an auto baud rate selection
register (size 1 Byte). Hexadecimal number notation to represent values is used. Register contains two
hexadecimal numbers. One number slot is associated with CAN1 interface, another with CAN2 (see table
below).

Note
Auto baud rate for CAN1 and CAN2 interfaces is configured with a single number in decimal format. This
number is a value for parameter ID = 208. It means that both interfaces are configured at the same time,
with one SMS message.

Decide which interface you are going to use. This determines value pattern within the register. Auto
baud rate can be enabled or disabled. Each state is represented by a different hexadecimal number 1 HEX
- enabled and 0HEX - disabled (see “All configurable FM4 Device parameters” table for more information).
Choose interface and set corresponding value in the register. Now read values from this register starting
from the left. You will have a number in hexadecimal format. Translate it to the number in Decimal
format. This is a number that needs to be included in the SMS message to configure the chosen CAN
interface/interfaces.
CAN2

CAN1

FHEX FHEX

1 Byte

Note
Enabling/disabling auto baud rate for CAN1 and CAN2 interfaces can be done only when “LCV” mode is
enabled.

Examples
Set CAN auto baud rate for CAN2 interface and CAN auto baud rate disabled for CAN1 interface.
For CAN2 set corresponding number to 1HEX and for CAN1 enter 0 HEX. Now read values from this
register starting from the left. You will obtain a number in hexadecimal format. Translate it to the
number in Decimal format. This is a number that needs to be included in the SMS message to
configure the chosen CAN interface.

17
 CAN2

CAN1
1HEX 0HEX

Reading register values from the left we obtain: 10

Number in hexadecimal format: 10HEX
Number in decimal format: 16DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer group parameter
(ID = 202) and LCV manufacturer subgroup parameter (ID = 203) would also be included in the
message. For now we replace these parameters with PramID1 Value1, ParamID2 Value2,
ParamID3 Value3.
Only part that illustrates how to enable auto baud rate for CAN2 interface (CAN1 auto baud rate
disabled) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, ParamID3 Value3, 208 16
(Full examples available in previous paragraphs.)

Set CAN auto baud rate for CAN1 interface and CAN auto baud rate for CAN2 interface disabled.
For CAN1 set corresponding number to 1HEX and for CAN2 enter 0 HEX. Now read values from this
register starting from the left. You will obtain a number in hexadecimal format. Translate it to the
number in Decimal format. This is a number that needs to be included in the SMS message to
configure the chosen CAN interface.

Reading register values from the left we obtain: 01

Number in hexadecimal format: 1HEX
Number in decimal format: 1DEC

Configuration for this parameter is usually done in conjunction with other parameters. Normally
CAN interface enable, mode selection parameter (ID = 201), LCV manufacturer group parameter
(ID = 202) and LCV manufacturer subgroup parameter (ID = 203) would also be included in the
message. For now we replace these parameters with PramID1 Value1, ParamID2 Value2,
ParamID3 Value3.
Only part that illustrates how to enable auto baud rate for CAN1 interface (CAN2 auto baud rate
disabled) is given with real numbers:
Password setcfg ParamID1 Value1, ParamID2 Value2, ParamID3 Value3, 208 1
(Full examples available in previous paragraphs.)

18
4.1.8 GSM Jamming configuration
GSM Jamming configuration is a special case where it is necessary set two parameters and their values
for this function to work properly. Few examples for such cases are provided below:
GSM Jamming configuration needs to have two parameters and their values specified in a single
SMS message. Enable DOUT1 and set to “GSM Jamming block”.
Password setcfg 551 8, 240 4

4.1.9 Parameter recalculation

In order to set some parameter to a certain value you may need to recalculate it before adding it to the
SMS message. If recalculation is necessary, you will find instructions for that in FM4 parameters table,
“Value description” column. Table is available in “All configurable FM4 Device parameters” chapter, at
the end of this document. Few examples for such cases are provided below:
Set Engine detection on 3rd profile to “Custom ignition”. It should be based on “DIN4” and “RPM”
values. Engine should be considered to be on, when voltage level at “DIND4” is high and RPM
value is higher than 500rpm. RPM value needs to be recalculated. 1bit equals 0,125 rpm, so value
that should be entered in a SMS to set 500rpm is “4000”:
Password setcfg 3123 4, 3105 15, 3105 64, 3107 4000
Eco-drive configuration. Set Overspending limit to “90” km/h, ECO-drive harsh braking limit to 2,0
m/s2. This number has to be recalculated. Limit value has to be multiplied by 10, so value for 2,0
m/s2 that should be entered in the SMS is “20”. Idling delay “360” s, Data source “ACC”. Also
configure Eco drive panel connected and Beeper Enabled:
Password setcfg 400 90, 403 20, 406 360, 411 0, 409 1, 410 1

4.2
Once you have sent the SMS command there is a number of different possible answers from the device.
These responses are sent to the same telephone number, which previously sent the SMS:
When successfully setting parameters with FM device:
“Configuration parameter(s) was set! “
Incorrect parameter setting:
“Configuration parameter(s) was NOT set! Parameter No. 1 is incorrect“.
Where parameter No is parameter ID
Unsuccessful set-up, when parameters are locked:
“Configuration parameter(s) was NOT set! Parameter No. 1 is locked“
Where parameter No is parameter order in SMS message.
If SMS configuration is disabled in configuration tool or configuration has password:
“You do not have permission to change the settings“.

19
5
Setioparam command is used only for setup IO parameters configuration. It is most suitable, when user
is not interested in modifying global configuration parameters (APN settings, Connection settings etc.).
You are not required to enter all the mandatory parameter values that are associated with the setcfg
command and this helps to reduce the overall length of the SMS message.
Full list of IO parameters and they ID numbers is available in “FMIOData+size + description.xls”. You can
find the most recent version of this document at our FTP server:
Address: ftp://dev.ruptela.com Login: ftp Password: ftp

Structure of the full “setioparam” message

It is mandatory to enter a correct password “Password” followed by a single space “ ” symbol. Then
command “setioparam” is entered, which is again followed by a single space “ ” symbol. These are the
only space symbols used in this command. After that enter parameter names and their values. There are
10 parameters: id=, profile=, enable=, level=, delta=, average=, eventon=, include=, priority=, switch=,
edge=.
Parameters and their values are separated only with comma symbols. Parameter name with equality sign
“id=” is followed by parameter value “idNumber”. After the first parameter value enter a comma symbol
“,”. Enter another parameter name with equality sign “profile=” followed by parameter value
“profileNumber”. Continue this for all necessary parameters. Final SMS message should have a similar
structure to the one provided below:
Password setioparam id=idNumber,profile=profileNumber,enable=enable,level=level,delta=delta,
average=average,eventon=eventon,include=include,priority=priority,switch=switch,edge=edge

Valid parameter values

Some parameters have a strict value rage. Only theses value can be included in the SMS message,
otherwise error will occur. These parameters are: enable, eventOn, include, priority or switch
Valid numeric values for each parameter:
Enable EventOn Include Priority Switch Edge
0 – disable 0 – Hysteresis 0 – not include 0 – Low 0 – no switch 0 – On Both
1 – enable 1 – Change data 1 – High 1 – 1st profile 1 – On rising
2 – Monitoring 1 – include data 2 – 2nd profile 2 – On falling
3 – 3rd profile
4 – 4th profile

Example
Let’s say that we want to monitor our device’s power supply voltage. Monitoring should be configured
on the 4th profile. SMS has to have the same structure as provided above. We begin the SMS by entering
a configuration password “Pasword” and the command “setioparam”. From the “FMIOData+size +

20
description.xls” spread sheet we obtain FMIO parameter ID number for the “Power Supply Voltage”. ID
number is “29”, so in the SMS message we type “id=29”. Configuration should be done for the 4 th profile
“profile=4”. For the configuration to work we must enable this parameter, so we enter “enable=1”. Our
chosen reference level is 12700 mV, we add “level=12700”. Delta, which stands for variation is set to
1000 mV, we add “delta=1000”. Averaging is set to 1000 ms, so we enter “average=1000”. Event on is set
to “Hysteresis”, add “eventon=0”. To enable “Include data only on event”, we add “include=1”. Priority
is set to “Low“ - “priority=0”. Switch to is set to “No switch” – “switch=0”. For Edge we choose “On Both”
– “edge=0”. Final result looks like this:
Pasword setioparam id=29,profile=4,enable=1,level=12700,delta=1000,average=1000,eventon=0,include=1,
priority=0,switch=0,edge=0

Mandatory parameters for the “setioparam” message

SMS with setioparam command is valid when it contains at least these three parameters and their values:
Id – parameter id number
profile - profile number (can have value from 1 to 4).
enable – can have value 1 or 0. If you enter 1 – some specific IO parameter will be enabled. If you
enter 0 – some specific IO parameter will be disabled. When the FM-device receives the SMS
where the parameter enable is set to 1, it performs a check in the current configuration to see if
parameter with the same ID is already enabled.
If parameter with the same ID was not enabled, FM-device will set this IO parameter to
the first free slot that is available.
If IO parameter with the same ID was enabled, FM-device will overwrite the IO parameter
with new values.
If FM-device finds more than one IO parameters with the same ID it will send an error
message.

Structure of the shortest possible message using “setioparam” command

Command includes only password, command “setioparam” and three mandatory parameters “id”,
“profile”, “enable”.
Password setioparam id=id,profile=profile,enable=enable

Example
Let’s say that we want to monitor our device’s battery voltage. Monitoring should be configured on the
4th profile. SMS has to have the same structure as provided above. We begin the SMS by entering a
configuration password “Pasword123” and the command “setioparam”. From the “FMIOData+size +
description.xls” spread sheet we obtain a FMIO parameter ID number for the “Battery voltage”. ID
number is “30”, so in the SMS message we type “id=30”. Configuration should be done for the 4 th profile
“profile=4”. For configuration to work we must enable this parameter, so we enter “enable=1”. Result
looks like this:
Password123 setioparam id=30,profile=4,enable=1

21
Reconfiguring an IO event
If SMS command does not define new values for level, delta, average, eventOn, include, priority, switch
or edge parameters, then their values will not be changed – old values will remain.

Configuring new IO event

Let’s say that you create a new IO event and specify values only for mandatory parameters (id, profile,
enable). In such case values for the remaining parameters will be set to default. Default values are listed
below:
Level Delta Average Event On Include Priority Switch Edge
0 0 1000 2 0 0 0 0

5.1
Once you have sent the SMS command there is a number of different possible answers from the device.
These responses are sent to the same telephone number, which previously sent the SMS:
If IO parameter was set it correct, the FM-device would answer:
„setioparam OK slot: XX“
Where ‘slot’ is the slot where the FM-device set parameter.
If all slots are full, FM-device would answer:
„setioparam ERROR, no free slots for set the I/O“
If FM-device finds more than one IO parameters with the same ID it would answer:
“setioparam ERROR, more than one I/O with same ID”
If user sent a SMS to disable (enable field = 0), and the parameter is not found as enabled, FM-
device would answer:
„setioparam ERROR, parameter is already disable“
If IO parameter was not set it correct, FM-device would answer:
„setioparam ERROR, <explanation>”
If SMS configuration is disabled in configuration tool:
„You do not have permission to change the settings“

22
6
This command is only used to get the current status of the selected parameter or parameters. Maximum
data amount for selected parameters that can be simultaneously received in one SMS message is limited
by the SMS message length (160 symbols).
Parameter ID’s with possible values can be found in the “All configurable FM4 Device parameters”
chapter, at the end of this document.

Structure of the full “getcfg” message

It is mandatory to enter a correct configuration password “Password” followed by a single space “ ”
symbol. Then command “getcfg” is entered, which is again followed by a single space “ ” symbol. After
that enter parameter ID number “ID”. If you need to get values for few different parameters, then after
the first parameter ID enter a comma symbol and add a single space symbol “, ”. Enter second parameter
ID number “ID2”. Continue for as many parameters as necessary. Final SMS message should have a similar
structure to the one provided below:
Password getcfg ParamID1, ParamID2, …

Example
Get information whether ECO-dive beeper is enabled or disabled in the configuration. SMS message
would look like this:
Password getcfg 410

6.1 getcfg
Once you have sent the SMS command there is a number of different possible answers from the device.
These responses are sent to the same telephone number, which previously sent the SMS:
When parameter ID is correct, FM-device answer:
„ID: XXX,value:XXX;“
Example: ‘ID: 96,value:1000;’
Value can be string or number.
Parameters configuration password and SMS password are not reachable with this SMS. In this case,
the device answer:
„ERROR: parameter(s) read is forbidden“
If parameter ID is invalid, answer would be:
„‘ID:XXX,value:requested ID not found;“
Example: ‘ID:556,value:requested ID not found; ’
If SMS configuration is disabled in configuration tool or configuration has password:
„You do not have permission to change the settings“

23
7
This command is only used for get the current status of the selected IO parameter.

Structure of the full “getioparam” message

It is mandatory to enter a correct configuration password “Password” followed by a single space “ ”
symbol. Then command “getioparam” is entered, which is again followed by a single space “ ” symbol.
After that enter parameter ID number “ID”. This is followed by a comma symbol and a single space symbol
“, ”. Enter a profile number “profileNumber”. In one SMS data only for one parameter can be requested.
Final SMS message should have a similar structure to the one provided below:
Password getioparam id, profileNumber

Example
Get information on Virtual Odometer configuration on the 2nd profile. SMS message would look like this:
Password getioparam 65,2

7.1 get
Once you have sent the SMS command there is a number of different possible answers from the device.
These are sent to the same telephone number, which previously sent the SMS:
If IO parameter was enabled, the FM-device would answer:
Example:
‘‘id=28,profile=3,enable=1,level=0,delta=0,average=1000,eventon=2,include=0,priority=0,switch=0,e
dge=0’’
If IO parameter was not enabled, the FM-device would answer:
„I/O ID XXX is NOT enabled“
Example: ‘I/O ID 100 is NOT enabled’.
If IO parameter ID is invalid, the FM-device would answer:
„ERROR I/O ID XXX does not exist“
Example: ‘ ERROR I/O ID 1000 does not exist’
If SMS configuration is disabled in configuration tool or configuration has password:
„You do not have permission to read the settings“

24
8 All configurable FM4 Device parameters
Parameters group one: For FM-Eco4/4+/light devices only parameters in white rows can be configured
via SMS.
Parameters group two: For FM-Tco4, FM-Tco4 (LCV), FM-Pro4 device all parameters (white and grey
rows) can be configured via SMS.

Note
Specific configuration options with parameters from group two are hardware dependent.
For example, LCV profile configuration is available only for FM-Tco4 and FM-Tco4 (LCV).

By default all numbers within this table are in decimal format. If number is in hexadecimal format it will
have a subscript (HEX) to show it. For example 15HEX.

GLOBAL PARAMETERS

ID Description Value Value description

GPRS transport
100 0, 1 0 (TCP) / 1 (UDP)
Protocol
101 APN settings: Name Any symbol Any symbol (max length 32 symbols)
102 APN settings: User Any symbol Any symbol (max length 32 symbols)
103 APN settings: Psw Any symbol Any symbol (max length 32 symbols)
Connection settings:
110-111 Any symbol Any symbol (max length 40 symbols)
IP1 and IP2 address
Connection settings:
120-121 0..65536 Any number from 0 to 65536
IP1 and IP2 port
123 Records sort 0, 1 0 (first oldest) / 1 (first newest)
Authorized numbers
130-139 Numbers Numbers (max length 16 symbols)
(10 numbers)
Authorized
numbers:
142 0, 1 0 (disable) / 1 (enable)
Enable list for voice
calls
Send I/O data with
143 0, 1 0 (disable) / 1 (enable)
v1.1 protocol
Operator list:
Any number of seconds from 0 to
144 Temporary blacklist, 0 .. 4294967295
4294967295
s
Connection settings:
145 0, 1 0 (disable) / 1 (enable)
Two server mode
Send data without
147 Configuration controlled by value stored in
GPS fix
1 byte register.

25
 Any combination of parameters can be
enabled. For this a specific number is
needed. This number is obtained, when
contemplating necessary bit arrangement in
the register. Value stored in the register is
converted from binary number to decimal
number.

More information on: Sent data without

GPS fix

Send data without

148 Any symbol Char symbol
GPS fix: NTP server
Send data without
149 GPS fix: NTP refresh 0...255 Any number of hours from 0 to 255
interval, h

Split 1 Byte register. CAN1 - 0F; CAN2 - F0.

Where F: 0HEX - silent or 1HEX - active.
Interfaces:
CAN1 and CAN2 (HEX number conversion to DEC number is
200
regime necessary. One value configures both
(silent/active) interfaces.)

More information on: CAN active/silent

Split 1 Byte register. CAN1 – 0F; CAN2-F0.

Where F has these values:

None = 0HEX,
FMS = 1HEX,
LCV = 2HEX,
Interfaces: OBD = 3HEX,
CAN1 and CAN2 TACHO = 4HEX,
201
enable, mode MOBILEYE = 5HEX,
selection
(HEX number conversion to DEC number is
necessary. One value configures both
interfaces.)

More information on: CAN interface enable,

mode selection

26
 Split 4 Bytes register.
CAN1- 0000FFFF; CAN2 -FFFF0000

Where F has these values:

None = 0HEX,
VAG= 1HEX
MERCEDES = 2HEX,
CITROEN= 3HEX,
FORD= 4HEX,
FIAT = 5HEX,
OPEL= 6HEX,
RENAULT = 7HEX,
TOYOTA = 8HEX,
TRACTOR = 9HEX,
TRUCK = 10HEX,
HYUNDAI = 11HEX,
LEXUS = 12HEX,
CAN LCV: VOLVO = 13HEX,
202 LCV manufacturer BMW = 14 HEX,
group NISSAN = 15HEX,
HONDA = 16HEX,
MITSUBISHI = 17HEX,
SUBARU = 18HEX,
CHRYSLER = 19HEX,
ISUZU = 20HEX,
SSANGYONG = 21HEX,
MAZDA = 22HEX,
KOMATSU = 23HEX,
RANGEROVER = 24HEX,
CLAAS = 25HEX,

(HEX number conversion to DEC number is

necessary. One value configures both
interfaces.)

More information on: LCV manufacturer

group

CAN LCV: Split 4 Bytes register.

203 LCV manufacturer CAN1- 0000FFFF; CAN2 - FFFF0000
subgroup
Where F has these values:

27
 1HEX; 2HEX; 3HEX; 4HEX … NHEX. None = 0HEX.
Number range depends on selected "LCV
manufacturer group"

(HEX number conversion to DEC number is

necessary. One value configures both
interfaces.)

More information on: LCV manufacturer

subgroup

CAN OBD: DTC

204 0, 1 1 – enabled / 0 - disabled
enable
CAN OBD: DTC
205 timeout interval, 30 .. 9999 Any number of minutes from 30 to 9999
min
250 baud, 500
206 CAN1 FMS: baudrate 250 baud rate / 500 baud rate
baud
250 baud, 500
207 CAN2 FMS: baudrate 250 baud rate / 500 baud rate
baud

Split 1 Byte register.

Can1 – 0F; Can2 – F0.

Where F has these values: 1HEX - enable or

CAN LCV: 0HEX -disable.
208
Autobaud
(HEX number conversion to DEC number is
necessary. One value configures both
interfaces.)

More information on: CAN auto baud rate

209 CAN OBD: Fuel type 0, 1, 2 0 – none, 1- Gasoline, 2-Diesel

NONE = 0
LLS = 1
SmartCardReader = 2
CanLog = 4
Interfaces: RFID = 5
210 0..2, 4..7, 10..12
Port A Optitemp = 6
WeightingSys = 7
TunnelChannel = 10
Carrier = 11
SpreadingSys = 12

28
 NONE = 0
LLS = 1
Thermoking = 2
SmartCardReader = 3
CanLog = 5
Interfaces: Optitemp = 6
220 0..3, 5..12
Port B RFID = 7
Garmin = 8
WeightnigSys = 9
TunnelChannel = 10
Carrier = 11
SpreadingSys = 12

NONE= 0
Interfaces: LLS = 1
260 0, 1, 2, 10
Port C J1708= 2
TunnelChannel = 10

Interfaces:
230 0, 1, 2 0-disable / 1-TCO/ 2-OBD
K-Line
0-disabled / 1-LED / 2-Buzzer / 3-blocking /
240 DOUT1 enable 0 .. 4 4-GSM jamming block (parameter ID=551
has to be set to 8 value)
0-disabled / 1-LED / 2-Buzzer / 3-blocking /
245 DOUT2 enable 0 .. 4 4-GSM jamming block (parameter ID=551
has to be set to 8 value)
Driver registration:
250 0, 1, 2 0-RFID A / 1-RFID B / 2-iButton
Registration source
Driver registration: 0-disabled / 1-Registration / 2-Mandatory
255 0, 1, 2, 3
Registration function Registration / 3-Engine lock
Driver registration:
256 0, 1 0-keep until timeout / 1-reset after send
Reset ID
DOUT registration 0-disabled / any combination of: 1-LED / 2-
257 0, 1, 2, 4, 8
outputs Buzzer / 4-Blocking / 8-GSM Jamming Block
GPS stationary
300 0, 1 0-GPS filter disabled / 1-GPS filter enabled
navigation filtering
Any hexadecimal symbol [0..9, A..F] (max
Authorized ID’s
length 16 symbols). Conversion to decimal
(330-399) (iButton list 0..9, A..F
format before adding to the SMS message is
120..189)
not needed.
ECO-drive:
400 Overspeeding limit, 0 .. 255 Any speed in km/h from 0 to 255
km/h

29
 ECO-drive: RPM
401 green band low 0 .. 10000 Any number of RPM from 0 to 10000
limit, RPM
ECO-drive: RPM
402 green band high 0 .. 10000 Any number of RPM from 0 to 10000
limit, RPM
ECO-drive: Harsh Any number from 0 to 100. Recalculation
403 braking limit, 0 .. 100 needed. Acceleration value should be
0,1m/s2 multiplied by 10. i.e.: 95 = 9.5 m/s2
ECO-drive: Extreme Any number from 0 to 100. Recalculation
404 braking limit, 0 .. 100 needed. Acceleration value should be
0,1m/s2 multiplied by 10. i.e.: 95 = 9.5 m/s2
ECO-drive: Harsh Any number from 0 to 100. Recalculation
405 acceleration limit, 0 .. 100 needed. Acceleration value should be
0,1m/s2 multiplied by 10. i.e.: 95 = 9.5 m/s2
ECO-drive: Idling
406 0 .. 65535 Any number of seconds from 0 to 65535
delay, s
ECO-drive: Cruise
407 0 .. 255 Any number from 0 to 255
control speed, km/h
409 ECO-drive: Panel 0, 1 0-disabled / 1-enabled
410 ECO-drive: Beeper 0, 1 0-disabled / 1-enabled

0 - Accelerometer
1 - CAN
2 - CAN+ACC
ECO-drive: Data
411 0..5; 128 3 -OBD
source
4 - OBD+CAN
5 - GPS
128 - Automatic data source selection

Any number from 0 to 100. Recalculation

ECO-drive: Cornering
412 0 .. 100 needed. Acceleration value should be
limit, 0,1m/s2
multiplied by 10. i.e.: 95 = 9.5 m/s2
Any hexadecimal symbol [0..9, A..F] (max
Authorized ID’s
length 16 symbols). Conversion to decimal
(440-499) (iButton list 0..9, A..F
format before adding to the SMS message is
189..250)
not needed.
500 GNSS selection 0, 1 0 (GPS) / 1 (GLONASS)
501 Connection string 0, 1 0-disabled / 1-enabled
8-GSM Jamming Block (used with
551 GSM jamming DOUT 8
parameter ID=240 or ID=245)
Operators list:
600 0 .. 20 Any number from 0 to 20
GPRS Attempt
Operators list:
601 0 .. 999999 Any number from 0 to 999999
GPRS data counter
698 Authorized ID’s 0, 1 0-disabled / 1-enabled

30
 Driver registration:
699 Deregistration 0 .. 30000 Any number of seconds from 0 to 30000
timeout, s
Operators list:
700-749 Blacklist, codes (max 0 .. 999999 Any number from 0 to 999999
50 operators)
SMS alert number
750 Numbers Numbers (max length 16 symbols)
(first)
Any hexadecimal symbol [0..9, A..F] (max
Authorized ID’s length 16 symbols). Conversion to decimal
(780-899) 0..9, A..F
(iButton list 1..120) format before adding to the SMS message is
not needed.

PROFILE SETTINGS (N is a profile number, N=1,2,3,4)

ID Description Value Value description

Operators list:
N000-N049 Valid list for profile 0 .. 999999 Any number from 0 to 999999
(max 50 operators)
Operators list:
N050 Enable priority in 0, 1 0-disabled / 1-enabled
GSM operators list
0-disabled / 1-sleep enabled / 2-deep sleep
N120 Sleep 0, 1, 2
enabled
Data collection:
N121 0, 1 0-disabled / 1-enabled
Enable
Data collection:
Any number of seconds from 0 to
N122 Time without 0 .. 4000000000
4000000000
engine, s
Data collection: 0-Always ON / 1-Ignition (DIN4) / 2-
N123 0, 1, 2, 4
Engine Movement sensor/4-Custom

Configuration controlled by value sored in 1

byte register.

Any combination of parameters can be

enabled. For this a specific number is
Engine:
N105 needed. This number is obtained, when
Custom Ignition
contemplating necessary bit arrangement in
the register. Value stored in the register is
converted from binary number to decimal
number.

More information on: Custom ignition

31
 Custom Ignition:
N106 Power supply 500 .. 65535 500-65535 mV
voltage value
Value needs to be recalculated.
Relation: 1bit proportional to 0,125rpm/bit
Custom Ignition: Example: Set RPM value to 125rpm.
N107
RPM value Calculations: 125rpm / 0,125rpm/bit = 1000
bit
Value to include in the SMS message: 1000
Value needs to be recalculated.

1 𝑘𝑚
Relation: 256 ℎ∙𝑏𝑖𝑡 proportional to 1 𝑏𝑖𝑡

Custom Ignition:
N108 Example: Set speed value to 1km/h.
Wheel based speed
ℎ∙𝑏𝑖𝑡 𝑘𝑚
Calculations: 256 ∙1 = 256 𝑏𝑖𝑡
𝑘𝑚 ℎ

Value to include in the SMS message: 256

Custom Ignition:
N109 5 .. 255 Any speed in km/h from 5 to 255
GPS speed
Coefficients: Any distance in meters from 0 to
N124 0 .. 4000000000
Distance, m 4000000000
Coefficients: Any number of seconds from 0 to
N125 0 .. 4000000000
Time with engine, s 4000000000
Coefficients:
N126 0 .. 180 Any number of degrees from 0 to 180
Radial, deg
N127 Data sending: Enable 0, 1 0-disabled / 1-enabled
Data sending:
N128 0 .. 255 Any number of records from 0 to 255
Min Records
Data sending: Any number of seconds from 0 to
N129 0 .. 4000000000
Period, s 4000000000
Data sending:
N130 0, 1 0-disabled / 1-enabled
Timetable enable
Data sending: Any number of seconds from 0 to
N132 0 .. 4000000000
Link timeout, s 4000000000
Data collection:
Any number of seconds from 0 to
N134 SD card logging 0 .. 4000000000
4000000000
interval

Main Support no.: +370 5 2045030

Polish Support no.: +48 22 2092532
Ukrainian Support no.: +380 947 107319 32
support@ruptela.com I www.ruptela.com