ID Logger - Reference Manual

Copyright 2013 ComAp s.r.o.
Written by RJZD
Prague, Czech Republic

ComAp, spol. s r.o.
Kundratka 17, 180 00 Praha 8, Czech Republic
Tel: +420 246 012 111, Fax: +420 266 316 647
E-mail: support@comap.cz, www.comap.cz

REFERENCE GUIDE

InteliDrive
ID-Mobile Logger
Data Logger

HW version 1.3; SW version 2.0, January 2014

ID-Mobile-Logger, SW version 2.0, ComAp January 2014 Page 2 of 68 2

Table of contents
Table of contents ..................................................................................................................................... 2
Abbreviations....................................................................................................................................... 4
Document information ............................................................................................................................. 5
Clarification of notation ........................................................................................................................ 5
Conformity declaration ........................................................................................................................ 5
Related .................................................................................................................................................... 6
Software .............................................................................................................................................. 6
PC Tools .............................................................................................................................................. 6
Documentation .................................................................................................................................... 6
General guidelines ................................................................................................................................... 7
What is ID-Mobile Logger? .................................................................................................................. 7
Features .............................................................................................................................................. 7
Hardware ................................................................................................................................................. 8
LED indication ..................................................................................................................................... 8
Dimensions and assembly .................................................................................................................. 9
Harnesses ......................................................................................................................................... 10
ID-Mobile Service Module ................................................................................................................. 11
Terminals ........................................................................................................................................... 12
Physical input/output structure .......................................................................................................... 13
Hardware configuration ..................................................................................................................... 15
Plug in modules ................................................................................................................................. 17
External displays ............................................................................................................................... 19
Communication lines ......................................................................................................................... 20
Controller setting ................................................................................................................................... 22
Modules ............................................................................................................................................. 22
Binary Inputs (BIN) ............................................................................................................................ 23
Logical binary inputs (LBI) ................................................................................................................. 23
Binary Outputs (BOUT) ..................................................................................................................... 26
Logical binary outputs (LBO)............................................................................................................. 27
Prg. states ......................................................................................................................................... 29
Analog Inputs (AIN) ........................................................................................................................... 30
Logical analog inputs (LAI) ................................................................................................................ 31
Shared virtual I/O periphery .............................................................................................................. 32
Values .................................................................................................................................................... 36
RPM/FlowMeters ............................................................................................................................... 36
Basic Values...................................................................................................................................... 36
Engine Values ................................................................................................................................... 37
Analog CU ......................................................................................................................................... 37
Binary CU .......................................................................................................................................... 37
Log Bout ............................................................................................................................................ 38
Info .................................................................................................................................................... 39
Statistics ............................................................................................................................................ 40
Position .............................................................................................................................................. 42
Setpoints ................................................................................................................................................ 44
Password ........................................................................................................................................... 44
Basic Settings.................................................................................................................................... 45
Comms Settings ................................................................................................................................ 48
RPM/FlowMeters ............................................................................................................................... 49
Analog Inputs .................................................................................................................................... 51
Act. Calls/SMS .................................................................................................................................. 51
Date/Time .......................................................................................................................................... 52
Statistics ............................................................................................................................................ 54
Position .............................................................................................................................................. 55
Limits ................................................................................................................................................. 55
Remote control and data logging .......................................................................................................... 58


Direct connection to the PC .............................................................................................................. 58
Modbus communication .................................................................................................................... 58
Event Log history ........................................................................................................................... 58
Operator Identification ........................................................................................................................... 62
Booting procedure ................................................................................................................................. 63
Technical Data ....................................................................................................................................... 66
Power Supply .................................................................................................................................... 66
Operating conditions ......................................................................................................................... 66
Dimensions ........................................................................................................................................ 66
Binary inputs...................................................................................................................................... 66
Binary outputs ................................................................................................................................... 66
Speed pick-up input .......................................................................................................................... 67
Impulse input ..................................................................................................................................... 67
Analog inputs..................................................................................................................................... 67
Communications ............................................................................................................................... 67
ID-Mobile GPRS ................................................................................................................................ 68
ID-Mobile GSM .................................................................................................................................. 68
ID-Mobile GPS .................................................................................................................................. 68


Abbreviations

aid Archive file extension for InteliDrive controller
AIN Controller or extension module Analog input
Alarm General term for any active engine protection Warning, Shutdown, etc.
Alarm list

Controller or PC InteliMonitor screen with list of active and unaccepted
alarms detected from ID controller.
ECU Alarm list

Controller or PC InteliMonitor screen with list of active and unaccepted
alarms detected from engine ECU.
AOUT Controller Analog OUTput or outputs group.
Archive

Usually aid file that contains all controller data: configuration, setpoints
setting and history records.
BI Controller binary input.
BIN Controller binary inputs group.
BO Controller binary output.
BOUT Controller binary outputs group.
CAN Control Area Network serial data link.
Cd Cool down protection, cooling period is included before engine stops.
DC DriveConfig, PC software for InteliDrive configuration.
DM
DriveMonitor, PC software for InteliDrive monitoring (discontinued in Q3
2013).
DriveConfig PC software for InteliDrive configuration.
DriveMonitor PC software for InteliDrive monitoring (discontinued in Q3 2013).
ECU Engine Electronic (injection) Control Unit.
ECU alarm
Alarm detected in engine electronic control unit that is received via
J1939.
Fls Sensor fail alarm prefix.
FMI Failure Mode Identifier.
GSM modem Modem for Global System of Mobile communication
History

List of alarms and operational states with Reason, Date and Time and
adjustable values set that is stored in controller, can be listed from the
screen or InteliMonitor.
InteliVision 5 CAN
InteliVision 8 ComAp color display 5 or 8 inch.
ID InteliDrive controller.
IMON InteliMonitor, PC software for InteliDrive monitoring.
InteliMonitor PC software for InteliDrive monitoring.
J1587

The J1587 bus is mainly used for redundant signals; system diagnosis
and software download on after market tools.
J1587/J1708 See J1587
J1939 The J1939 bus in mainly used for engine controls and engine monitoring.
mhx Extension for controller firmware (Motorola HeX file).
OFF

Controller mode when power supply is switched on, but all binary outputs
and start commands are disabled = engine start is blocked.
PID J1939 Parameter Identification Assignments.
PPID J1939 Proprietary Parameter Identification Assignments.
RPM Engine Revolution Per Minute engine speed.
PSID J1939 Proprietary Parameter Identification Assignments.
RS232

Standard serial data line for PC or Modem connection (controller
programming or monitoring).
Sd Shut down protection.
SID J1939 Subsystem Identification Assignments.
Wrn Warning protection.


Document information
ID-MOBILE LOGGER REFERENCE GUIDE
WRITTEN BY: ZDENEK ROJKA
2014 COMAP LTD.
KUNDRATKA 17, PRAHA 8, CZECH REPUBLIC
PHONE: +420246012111, FAX: +420266316647
WEB: HTTP://WWW.COMAP.CZ, E-MAIL: INFO@COMAP.CZ; SUPPORT@COMAP.CZ

DOCUMENT HISTORY
REVISION NUMBER RELATED SW. VERSION, DESCRIPTION DATE
1.8 1.8 5.2.2013
1.8.1 rev 1 1.8.1 formal changes, new chapter 4.4.2013
1.9 New software features, updated functionality 30.9.2013
2.0 New software features, updated functionality 10.1.2014

Clarification of notation
NOTE:
This type of paragraph calls readers attention to a notice or related theme.

CAUTION!
This type of paragraph highlights a procedure, adjustment etc., which can cause a damage or
unproper function of the equipment if not performed correctly and may not be clear at first sight.

WARNING!
This type of paragraph indicates things, procedures, adjustments etc. which need high level of
attention, otherwise can cause personal injury or death.
Conformity declaration

Following described machine complies with the appropriate basic safety and health
requirement of the EC Low Voltage Directive No: 73/23 / EEC and EC
Electromagnetic Compatibility Directive 89/336 / EEC based on its design and type,
as brought into circulation by us.

NOTE:
ComAp believes that all information provided herein is correct and reliable and reserves the right to
update at any time. ComAp does not assume any responsibility for its use unless otherwise expressly
undertaken.


Related
CAUTION!
Bellow mentioned versions are valid with the issuing of this document. For available updates follow
ComAp web pages.
Software

Import package Files Note
ID-Mobile-Logger-2.0.idc ID-Mobile-Logger-2.0.mhx ID-Mobile-Logger firmware
ID-Mobile-Logger-2.0.aim Default configuration archives
PC Tools

RELATED SW. VERSION DATE
InteliMonitor 3.0.3 12.12.2013
DriveConfig 3.3.1 12.12.2013
WinScope 2.0 12.12.2013
LoggerHistoryExport 1.3 12.12.2013

Documentation

PDF FILES DESCRIPTION
ID-Mobile-Logger-2.0 New Features.pdf New Features List of ID-Mobile-Logger 2.0
DriveConfig-3.3.1 New Features.pdf New Features list of DriveConfig-3.3.1 PC tool
DriveConfig-3.3.pdf Reference guide of DriveConfig-3.3 PC tool
InteliMonitor-3.0.3 New Features.pdf New Features list of InteliMonitor-3.0.3 PC tool
Intelimonitor-3.0-Reference Guide.pdf Reference guide of InteliMonitor-3.0 PC tool
Inteli Communication Guide.pdf Communication guide for the Inteli controllers
WinScope-2.0 Reference Guide Reference guide of WinScope-2.0 PC tool


General guidelines
What is ID-Mobile Logger?
ID-Mobile Logger is a specialized data logger for engine driven mobile and industrial applications. The
Logger can read and log engine data via CAN J1939 bus and/or measure by sensors.
Features
Running-hours meter, fuel consumption indication
RS485 communication line with MODBUS
J1939 and Modbus ECU support with Input / Output configuration
Engine measurement and control by sensors and actuators or via J1939
CAN1-bus line for extension (Slave) modules and J1939
CAN2-bus line for connection of external display
Optional internal plug-in modules:
GSM (Modem connection, Active call, SMS)
GPRS (AirGate, WebSupervisor)
GPS (GEO fencing)
8 Binary inputs for contacts switching to Battery
11 Analog inputs configurable for industry standard sensors
4 Binary outputs - Hi-side switches 0,5 A with detection of broken wire
1 Frequency inputs for RPM measurement
2 Impulse inputs for rotary flow meters or other cumulative measuring
Internal configurable PLC functions: Logical functions, Comparators with delay or hysteresis,
Analog switches, Mathematical functions, Linear interpolation, Filters, PID loops with analog or
binary outputs, Counters, Timers, Delay functions
Memory size up to 220 000 records
Supported download formats: xls, csv
Operator log-in possibility
Operating temperature: 30 to +80C
Supply voltage: 8-36 VDC continuously, 6 VDC for 1s
EMC compatibility: EN61000-6-1/2/3/4, SS4631503(PL4), IEC 255-3
Vibration resistivity: IEC 60068-2-6, 5-28Hz / 1,5mm, 28-150Hz/5g,
Shock test: IEC 68-2-27
Dust and water protection IP67.


Hardware

LED indication
Power
Power supply indication is always lighted if the power supply is on.
Run
Running engine indication is lighted if the engine is running
Alarm
Incoming Alarm indication. Because no Fault reset is expected for Data Logger the new incoming
Alarm activates steady state light for 60min. Any new alarm during this 60 minutes causes 2 sec fast
blinking and prolong the Alarm LED for next 60min. Auto quitted function disable the Alarm LED after
60 minutes after the last alarm even if is still active.
Status
Full history buffer indication i.e. oldest records are lost (overwritten) without downloading. Status can
be cleared using the Logger History Export PC tool.
LED indication
Right side male
connector:
BLACK
Left side male
connector:
BROWN
Plugs for Antenna connectors
Membrane overpressure relief


Dimensions and assembly

The ID-Mobile chassis is assembled with two parts (controller case and controller cover). Both parts
are connected together with 19 bolts (2,9 x 16m).

NOTE:
The unit is completed with two screws for the delivery. The rest of screws are attached so the unit can
be completed before applying. The main reason is to be plug-in modules (GPS, GSM/GPRS) easily
applicable.

Disassembling:

Screw out 19 bolts from the bottom side of the controller case.
Gently divide controller cover and case.
Watch the GPS/GPRS antenna interconnections (if applicable).
The silicone sealing is lubricated some lube could be present in the joint.

Assembling:

Settle the silicone sealing and be sure the sealing is undamaged
Fit the controller case and cover so that both parts are matching properly in joint shells.
Firstly screw up all bolts but do not finalize
Finalize all bolts with the sequence as shown below. The maximum torque is 1 Nm

117 (4,6")
201 (7,9")
2
5
8

(
1
0
,
1
"
)
2
4
0

(
9
,
4
"
)
40
(1,6")
Maximal thickness 63mm (2.5)
4x bracket 6mm (ready for screw M6)
GPS
GSM, GPRS


Harnesses

All signals are connected via two MOLEX CMC (4x12) 48
pins connectors. Bold (power) items are connected via
MOLEX CMC stronger pins with wires crosscut about 1,5
mm2.

Available standard harnesses supplied by ComAp

NOTE:
Harnesses for ID-Mobile Logger are not compatible with ID-Mobile control unit.

Connectors

Mating/Unmating of the connector from the header

Insert the connector until it stops in the header Rotate the lever
HARNESS LENGHT
COMAP ORDER CODE
1.5 METERS ID-MOBILE HARNESS-LOG-1,5
6 METERS ID-MOBILE HARNESS-LOG-6
NOTE:
Includes:
One set of harnesses for ID-Mobile Logger:
left and right connector
cables, interconnection
cable sleeve

ITEM
COMAP ORDER CODE
SET OF CONNECTORS TERM SET ID-MOBILE
Includes:
- right and left connector (brown, black)
- accessories (pins, plugs)
NOTE:
MOLEX connector: Series 64320
ID-Mobile
Logger


Lock it on the cover cap until it clicks

Press on the latch Rotate the lever

Rotate the lever

ID-Mobile Service Module
Service module enables access to any of 96 ID-Mobile signals for measuring and simulation. It is
designed in ID-Mobile box with one meter harness tail see in blue (containing all signals) to be
connected to ID-Mobile box. Vehicle harness (see in black) is in this case connected to Service
Module.

ID-Mobile
Logger
ID-Mobile
ServiceModule


Terminals

Pins (numbering) location (four rows per 12 pins each, power pins are in bold)

Left side male connector - brown Right side male connector - black
9 10 12 1 49 50 51 52 53 54 55 56 57 58 60
21 2 61 62 63 64 65 66 67 68 69 70 72
25 26 27 28 29 30 31 33 34 36 3 73 74 75 76 79 80 81 82 83 84
37 38 39 40 41 42 43 44 45 46 48 4 85 86 87 88 89 90 91 92 93 95 96
A B C D E F G H J K L M A B C D E F G H J K L M
Bottom side of box

Left side connector - Pins function

4 3 2 1
37 AI8+ 25 AIN 1 A 13 1
38 AI8- 26 AIN 2 B 14 2
39 AI9+ 27 AIN 3 C 15 3
40 AI9- 28 AIN 4 D 16 4
41 AI10+ 29 AIN 5 E 17 5
42 AI10- 30 AIN 6 F 18 6
43 AI11+ 31 AIN 7 G 19 7
44 AI11- 32 H 20 8
45 +5V 33 GND1 J 21 +5V 9 IM 2 IN
46 GND3 34 K 22 10 IM 2 SUP
47 35 L 23 11
48 GND4 36 GND2 M 24 12 GND5

Right side connector - Pins function

4 3 2 1
85 RS485A 73 BO1 A 61 GND 49 BIN 1
86 485COM 74 BO2 B 62 GND 50 BIN 2
87 RS485B 75 BO3 C 63 GND 51 BIN 3
88 CAN1H 76 BO4 D 64 GND 52 BIN 4
89 CAN1COM 77 E 65 GND 53 BIN 5
90 CAN1L 78 F 66 GND 54 BIN 6
91 CAN2H 79 RPM 1- G 67 GND 55 BIN 7
92 CAN2COM 80 RPM 1+ H 68 GND 56 BIN 8
93 CAN2L 81 IM 1 IN J 69 GND I-BUTT 57 GND BIN
94 82 IM 1 SUP K 70 I-BUTT 58 +5V
95 BAT PLUS 83 +VBO L 71 59
96 BAT MINUS 84 GND7 M 72 GND8 60 GND9


Logger hardware versions differences
Table contains the changes between hardware version 1.1 and 1.2

NOTE:
All Binary outputs are High-side switches
maximum 0,5A

Physical input/output structure
Communication lines
(Twisted pairs)
RS485, CAN1, CAN2
Sensors
3-wires
ID-Mobile-Logger
Power Supply
8-36 VDC
Power
Run
Alarm
Status
25: AIN1
21: +5V
33: GND1
3-wires 26: AIN2
45: +5V
36: GND2
2-wires
27: AIN3
46: GND3
2-wires
28: AIN4
48: GND4
2-wires
29: AIN5
12: GND5
31: AIN7
84: GND7
4-wires
30: AIN6
58: +5V
2-wires
37: AIN8+
2-wires
39: AIN9+
60: GND9
95: BATT+
96: BATT-
49: BIN1
50-62: BIN2
51-63: BIN3
52-64: BIN4
53-65: BIN5
54-66: BIN6
55-67: BIN7
56-68: BIN8
85: 485A
86: 485COM
87: 485B
88: CAN1H
89: CAN1COM
90: CAN1L
91: CAN2H
92: CAN2COM
93: CAN2L
38: AIN8-
40: AIN9-
2-wires
41: AIN10+
2-wires
43: AIN11+
42: AIN10-
44: AIN11-
IMP1
SUP
IM1
GND
81: IM1
82: UM1
72: GND8
3-wires
IMP2
SUP
IM2
GND
9: IM2
10: UM2
3-wires
RPM
RPM1
GND
80: RPM1
79: RPM1COM
2-wires
61: COM
70: I-Button
69: GND I-BUTT
I_BUTTON PROBE
B
I
N
A
R
Y

C
O
N
T
A
C
T
S
83: +VBO
73: BO1
74: BO2
75: BO3
76: BO4
BATT+
BATT-

HW VERSION 1_1 HW VERSION 1_2
(SINCE 4-2012)
BO1
BO2
BO3
BO4
+VBO
Not available 73
74
75
76
83
I-BUTT
GND I-BUTT
34
33
70
69


Analog Inputs
AIN1 AIN7
AIN1
AIN2
AIN3
AIN4
AIN5
AIN6
AIN7
25
26
27
28
29
30
31
33 COM
A
n
a
l
o
g

i
n
p
u
t
s

Analog inputs configurable for usage with
current, resistance or voltage sensor.

AIN8 AIN11
AIN8+
AIN8-
AIN9+
AIN9-
AIN10+
AIN10-
AIN11+
37
38
39
40
41
42
43
44 AIN11-
A
n
a
l
o
g

i
n
p
u
t
s

Analog inputs configurable for usage with
current, resistance, voltage or thermocouple
sensor.

Binary Inputs
B
i
n
a
r
y

i
n
p
u
t
s
BIN1
49
BIN2 50
BIN3
51
BIN4 52
BIN5
53
BIN6 54
BIN7
55
56 BIN8
61 BIN-COM
62 BIN-COM
63 BIN-COM
64 BIN-COM
65 BIN-COM
66 BIN-COM
67 BIN-COM
68 BIN-COM

Activation to minus of power supply.

Switching level: active 2 VDC.
Sampling rate 100ms.

Binary Outputs

+VBO 83
73
74
75
76
B
i
n
a
r
y

o
u
t
p
u
t
s
BO1
BO2
BO3
BO4

Four High-side switches up-to 0,5 Amps.
+VBO is connected to BATT+
The load is grounded.

It is possible to invert channels logic in
DriveConfig.


RPM Input

RPM1A
RPM1B
79
80

R
P
M

i
n
p
u
t

Use magnetic pickup.

Impulse inputs
+IM1 SUP (+24VDC)
IM 1 IN
IM 2 IN
82
81
84
10
9
12
I
m
p
u
l
s
e
i
n
p
u
t
s
BAT-
BAT-
+IM 2 SUP (+24VDC)

Use active NPN open collector sensors.

Hardware configuration
Prior to configuration procedure the hardware jumpers has to be connected. See below available
jumpers groups.

NOTE:
Layout bellow is related to hardware version 1.3

NOTE:
Take care of correct jumper setting to avoid repeated ID Mobile box opening.


Jumpers location
uP
AIN1 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7
1 12
13 24
25 36
37 48
49 60
61 72
73 84
85 96
BOOT
GSM
GPS
RS232
POWER
RUN
ALARM
STATUS
1
2
0
R
1-2: 20 mA
No jumper: 5 VDC
3-4: 2,4 kOhm
4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1
4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1
AIN8 AIN9 AIN10 AIN11
1-2: +- 20 mA
No jumper: +- 1 VDC
3-4: 2,4 kOhm
GND GND GND GND
BOUT-BW
1
2
0
R
-
B
i
a
s
+
B
i
a
s
SIM
CARD
R
S
4
8
5
1
2
0
R
C
A
N
1
C
A
N
2
4321

JUMPERS
GND
JUMPER OFF
(NO JUMPER)
JUMPER ON
(JUMPER CLOSED)
GND
Related to AIN8 AIN11
Non Isolated
Thermocouples
Ground on controller side
Isolated Thermocouples
Ground on Thermocouple side
(engine)

JUMPERS
AIN1 AIN11
NO JUMPER JUMPER 1-2 JUMPER 3-4
AIN1 - AIN7
5 VDC 0 - 20mA 0 2,4 k
AIN8 - AIN11 1 V
100 mV
-1 V .. +2,5 V

Thermocouple K
Thermocouple J
Thermocouple L
20mA 0 2,4 k


ANOTHER JUMPERS DESCRIPTION
RS-485 120
CAN1 120
CAN2 120
Terminating 120 resistor
RS-485 BIAS, +BIAS
TX signal bias to +/- power supply
BOUT-BW Set broken wire detection of Binary
Outputs 1-4. Closed = deactivated,
Opened = activated
BOOT
System booting
Plug in modules
GPS Module
GPS module enables function of exact controller location as well as
protection against unwanted manipulation of the controller
(GeoFencing).
After installation of the module to the controller is for the basic
function no other setpoints required.
For setting of GeoFencing see Setpoints / Position

NOTE:
Recommended Antenna Order code: ANTENNA2J425.

NOTE:
For further details how to install the module see GPS Assembling document in supplement.
GSM/GPRS/3G Module
There are three plug-in modules available:
1. ID-Mobile GSM (version 1.8.1 and lower)
2. ID-Mobile GPRS
3. ID-Mobile 3G (version 1.9 and higher)
Modules have three operation modes:
1. Standard GSM mode CSD (Circuit Switch Data)
2. GPRS mode
3. 3G mode
Selection of the mode is done by setpoint (See Setpoints / Act.
Calls/SMS / Modem).

NOTE:
Recommended Antenna Order code: GSM/GPRS ANTENNA or ANTENNA2J425 (combined
GSM/GPRS/3G and GPS antenna).


Overview of supported modes and functions:

CAUTION!
For support of WebSupervisor and AirGate chose the ID-Mobile GPRS plug-in module.

NOTE:
Proper function of GPRS/GPS connection depends significantly to cell network provider. Be sure your
provider supports data transfer

CAUTION!
Disable the PIN code on the SIM card prior applying in ID-Mobile / ID-Mobile Logger

NOTE:
For further details how to install the module see GSM Assembling document in supplement.

MODULE TYPE OPERATION
MODE
DESCRIPTION SUPPORTS
ID-Mobile GSM

TELIT CSD
GSM mode CSD (Circuit Switch
Data)
version 1.8.1 and lower
Alarm SMS
DriveMonitor / InteliMonitor
via modem connection
TELIT GPRS
Customized interface
version 1.8.1 and lower
For special custom
application only
ID-Mobile 3G
TELIT 3G
version 1.9 and higher
For special custom
application only
TELIT GPRS
version 1.9 and higher
For special custom
application only
ID-Mobile GPRS
SIMCOM CSD
Standard GSM mode CSD (Circuit
Switch Data)
Alarm SMS
Drive Monitor / InteliMonitor
via modem connection
SIMCOM
GPRS
GPRS network enables
connection via AirGate
Alarm SMS
AirGate
Drive Monitor / InteliMonitor
via AirGate
WebSupervisor


External displays
InteliVision 8
8 color TFT display - 800x600 pixels
Operating temperature: -20 +75C
Front IP65 / Rear IP 20
CAN bus interface
Plug and Play structure following controller configuration
Power supply 8 36 VDC

NOTE:
Screen can be customized with ScreenEditor (SW application included in DriveConfig)

InteliVision 5 - CAN
5" color TFT display - 320 240 pixels
Operating temperature: -20 +75C
Protection IP 65
CAN bus interface
Plug and Play structure following controller configuration
Power supply: 8 -36 VDC

Supported version in ID-Mobile/ID-Mobile-Logger SW version
1.2 and higher

NOTE:
Screen can be customized with ScreenEditor (SW application included in DriveConfig)

InteliVision 17Touch

17 TFT-LCD display, 1280 x 1024 pixels
Operating temp.: -20 +60 C
Protection - IP-65/NEMA4 (front)
Connection - RS232, RS485, USB, Ethernet
Power Supply 9 30 VDC
OS: Windows Embedded Standard 7
ComAp sw: InteliMonitor.


Communication lines

RS485
RS485-A
COM
RS485-B
85
86
87
R
S
4
8
5
RS485 / USB
converter
USB
USB
DriveConfig
DriveMonitor
WinScope

ID-Mobile / ID-Mobile-Logger CAN1 interface is dedicated to:
PC interface for communication with DriveMonitor/InteliMonitor, DriveConfig and other SW.
MODBUS communication interface
CAN1
ECU (Engine Control Unit) J1939 eventually KWP2000 protocols.
I-CB
The following modules are supported even use with ID-Mobile / ID-Mobile- Logger is not typical:
IGS-PTM (8BI, 8BO, 4AI, 1AO)
IS-AIN (8 AI)
IS-BIN (16BI, 8BO)
CAN2
external displays (see External displays )
ID-Mobile Slave unit
I-LB, I-LB+,
CAN bus connection rules
Can bus line must be connected in series, from one unit to another (no star, no cable stubs, no
braches) and both ends must be terminated with 120 resistor.
COMMUNICATIONS ID-MOBILE-LOGGER
Direct connection

USB

RS485

RS232

CAN1

CAN2

GSM 1)
GPRS 1)
UMTS 1)
GPS 1)
1) Plug-in module required


There are internal 120 resistors on ID-Mobile / ID-Mobile-Logger motherboard available:

NOTE:
All controllers must be adjusted to the same CAN bus mode. Default mode for CAN1 and CAN2 bus in
ID-Mobile / ID-Mobile-Logger is 250kBd. The limitation of line for the default speed is 200m maximum.


Controller setting
SW tool for configuration of ID-Mobile / ID-Mobile-Logger controller: DriveConfig.
DriveConfig is included in the installation package.

NOTE:
For more details how to use DriveConfig see latest version of DriveConfig Reference Guide
available on ComAp webpage: http://www.comap.cz/support/download-center/type/manuals/.
Modules
Following items is possible to configure in DriveConfig Modules

MODULE
MAXIMUM AVAILABLE
(USED/MAX.AVAIL.)
DETAILS
ID-MOBILE LOGGER 1/1 ID-Mobile Logger unit - It is obligatory item.
BINARY INPUTS MODULE x/8 Binary Inputs external extension module
BINARY OUTPUTS MODULE x/8 Binary Outputs external extension module
ANALOG INPUTS MODULE x/4 Analog Inputs external extension module
ANALOG OUTPUTS MODULE x/4 Analog Outputs external extension module
SHARED BINARY INPUTS x/4 Shared virtual binary inputs periphery
SHARED BINARY OUTPUTS x/4 Shared virtual binary outputs periphery
SHARED ANALOG INPUTS x/4 Shared virtual analog inputs periphery
SHARED ANALOG OUTPUTS x/4 Shared virtual analog outputs periphery
ECU x/1 Engine Control Unit interface
ICB MODULE x/1 External Interface Communication Bridge
interface
VIRTUAL BINARY OUTPUTS x/4 Group of Virtual binary outputs
PLC x/1 PLC tool enabled
ECU LOG x/5 Extended ECU values (special programming of
esf. needed)


Binary Inputs (BIN)
Available configuration for Binary inputs:

NOTE:
Minimal input pulse duration is 120ms to be detected as valid (binary inputs sampling rate 100ms).
Adjustable delay can be configured to any binary input according to details above.

Logical binary inputs (LBI)
Any InteliDrive controller binary input can be configured as function and/or protection.
PROPERTY VALUE DETAILS
ECU VALUE
Available only if ECU
selected under ECU-1
According to
selection
ECU output can be selected as controller inputs.
Selection depends on ECU type.
Selection of ECU see Modules
NOTE:
Some ECU are not supporting this function
NAME Text Maximum 14 charts
PROTECTION No Protection No protection active with BI
Warning BIN is active
- Alarm on LED (eventually Display)
- History record
Sensor fail BIN is active:
- Indicates sensor fail
- History record
Alarm Only BIN is active:
- Alarm on LED (eventually display) only
HistRecOnly BIN is active:
- History record only
PROT.ACTIVE Closed Protection active if the contact is closed
Open Protection active if the contact is open
PROT. BLOCK TYPE All the time Protection is active all time
Force Block Protection is active with Force Block only
RunOnlyBlkDel Protection is active only if engine is running with delay
according to Setpoint Basic Setting / RunOnlyBlkDel
from start
DELAY Standard (0,5s) The input signal is delayed for 0,5s (Default setting)
BinInp delay 1 The input signal is delayed according to Setpoint:
Basic Settings / BinInp Delay 1
FUNCTION Logical function Find more details in: Logical binary inputs


Following chapter contains Logical binary inputs list (functions list) that can be configured to any
physical input.

CAUTION!
Minimal input pulse duration is 120 ms to be detected as valid (binary inputs sampling rate is 100ms).
Adjustable delay can be configured to any binary input when is used as a protection, see Basic
Settings / BinInp Delay.
Force Block
Active input blocks protections that are configured (in DriveConfig) as Property: Prot.block type= Force
Block. Corresponding setpoint is Basic Settings / ForceBlock Del.
Fault Reset
Binary input for Alarm acknowledge (edge sensing) has the same function as controller front panel
button Fault reset.

NOTE:
There is separate acknowledge for ECU Alarms see LBI ECU FltReset.
ECUComFailBlck
Active input blocks ECU communication fail. Function can be used e.g. when ECU is switched off after
engine stop.

RunIndication1 RunIndication3
Binary input can be used for engine running indication e.g. via Oil pressure contact. Active Running
indication blocks engine start (to avoid starter damage).
ECU FltReset
Binary input for ECU Alarm acknowledge (edge sensitive) has the same function as controller front
panel Fault reset button (active only in ECU Alarm list).

NOTE:
Activation of ECU Fault reset will affect InteliDrive only, no reset request is sent to ECU.
There is separate acknowledge input for Alarms see LBI Fault reset.
RS485 Mode Std
Active input switches (by rising edge) setpoint Comms Settings / RS485 Mode to STANDARD (from
other like MODBUS, ECU LINK).

CAUTION!
RS485 communication does not work when RS485 mode is changed from standard to M MO OD DB BU US S or
E EC CU U L LI IN NK K. See setpoint: Comms Setting / RS485 Mode description.


Configure this input (or leave as it is in default) for case the RS485 mode setpoint is changed to
M MO OD DB BU US S or E EC CU U L LI IN NK K from DriveMonitor. It is the way how to establish communication with
DriveMonitor.
GeoFencingEna
Ena/Disables the GeoFencing function (engine block and active alarm) when setpoint Position /
GeoFencing = BIN.INPUT.
Home Position
Active input (rising edge) moves the actual position into Position / Home Lat and Position / Home
Long setpoints.
Clear TotalCons
Active input clears the Total Consumption counter (Statistics / TotalConsumpt).
Clear TripCons
Active input clears the Trip Consumption counter (Statisctics / TripConsumpt).
BI History
Closed binary input activates one History record.
Reset OperID
Rising edge of binary input resets Operator identification number ( (Info / Operator ID) ).
TripAverageEna
Rising edge of binary input enables the Trip Average (Statistics / TripAverage) calculation for the
AverageValue (see Logical Analog Inputs - LAI).
If TripAverageEna = 1, the calculation runs.
TripAverageRes
Rising edge of binary input resets the Trip Average (Statistics / TripAverage ) calculated from
AverageValue. It can be linked with any of logical binary input (e.g. OperatorID, Start Button, Fault
Reset etc.)
If TripAverageRes = 1 the TripAverage value is reset.
TotAverageEna
Rising edge of binary input enables the Total Average (Statistics / TotalAverage) calculation for the
LAI AverageValue.
If TotalAverageEna = 1, the calculation runs.
TotAverageRes
Rising edge of binary input resets the Total Average (Statistics / TotalAverage ) calculated from
Average Value. It can be linked with any of logical binary input (e.g. OperatorID, Start Button, Fault
Reset etc.)
If TotalAverageRes = 1 the TotalAverage value is reset


AveragSpeedEna
Rising edge of binary input enables the Average Speed (Statistics / AverageSpeed) calculation for
the LAI Average Speed.
If AveragSpeedEna = 1, the calculation runs.
AveragSpeedRes
Rising edge of binary input resets the Average Speed (Statistics / AverageSpeed ) calculated from
Average Speed. It can be linked with any of logical binary input (e.g. OperatorID, Start Button, Fault
Reset etc.)
If AveragSpeedRes = 1 the AverageSpeed value is reset
Zone 13 ON
Active input starts the calculation of Time and Consumption Zones (Statistics / Time Zone x and
Statistics / Consump Zone x) regardless on setpoints Statistics / RPM Start Zx, RPM Stop Zx, Fuel
Start Zx and Fuel End Zx

NOTE:
At once the condition e.g. Time Zone 6 and Consumption Zone 6 is active and e.g. LBI Zone 1 = =
ON as well, both Zone 6 and Zone 1 statistics are calculating.
ZonesReset
Resets statistic in all zones.
Binary Outputs (BOUT)

CAUTION!
Binary outputs of ID-Mobile-Logger are dedicated for indication use only. NO power output can be
connected - maximum continuous current for single channel is 0,5 A only.

SOURCE Log Bout See Logical Binary Outputs functions
Prg. states Controller internal states
Ana protections One of the following AIN protection levels is sent as
binary signal.
L1 level 1 of protection
Fls Sensor fail
L1+Fls sensor fail or/and L1
Bin protections Protection of BIN is sent as binary signal
Binary CU State of logger BIN is sent as binary signal.
ECU State of ECU-1 BIN is sent as binary signal.
NAME Text Title of the BOUT - maximum 14 charts
ECU VALUE
Available only if ECU
selected under ECU-1
According to selection Controller output can be selected as ECU inputs.
Selection depends on ECU type.
NOTE:
Some ECU are not supporting this function
INVERTED No Inactive state BOUT = 0, active state is BOUT = 1.
Yes Inactive state BOUT = 1, active state is BOUT = 0.


Logical binary outputs (LBO)
Horn
Binary output for Horn, Buzzer alarm acoustic indication. Horn is active unlimited time (until Fault
reset is pressed/activated).
Alarm
The output closes if any alarm is activated and opens after Fault reset even if the Alarm is still active.
Common Alarm
The output closes if any Wrn, Sd, Cd, Fls, alarm is active and stays closed until all alarms disappear
and Fault reset is pressed. Output is opened when Alarm list is empty.
Common Wrn
The output closes when any Warning alarm is active. Output opens when all Wrn alarms disappear
and Fault reset is pressed (no Wrn alarm in Alarm list).
Common Sd
The output closes when any Shut-down alarm is active. Output opens when all Sd alarms disappear
and Fault reset is pressed (no Sd alarm in Alarm list).
Common Cd
The output closes when any Cool-down alarm is active. Output opens when all Cd alarms disappear
and Fault reset is pressed (no Cd alarm in Alarm list).
Common Fls
The output closes when any Sensor fail alarm is active. Output opens when all Fls alarms disappear
and Fault reset is pressed (no Fls alarm in Alarm list).
Common SdO
The output closes when any Shut-down Override alarm is active. Output opens when all SdO alarms
disappear and Fault reset is pressed (no SdO alarm in Alarm list).
CPU Ready
CPU indication output is closed when CPU is ready, opened in Init state.
Engine Running
It activates, when RPM rises above starting RPM and opens when RPM=0.
CtrlHeartBeat
Indicates correctly running firmware when cycling on/off with 0,5 sec period.
Comm AIN Fail
Output is closed when any analog extension (IS-AIN, IGS-PTM) unit does not communicate.


Comm BIN Fail
Output is closed when any analog extension (IS-BIN, IGS-PTM) unit does not communicate.
Comm AOUT Fail
Output is closed when any analog extension (IS-AOUT, IGS-PTM) unit does not communicate.
Comm BOUT Fail
Output is closed when any analog extension (IS-BIN, IGS-PTM) unit does not communicate.
Alarm Blink
Function is based on Binary output COMMON ALARM - stays closed when any alarm is active (at
least one item in Alarm list) and opens for 2 sec when any new Alarm is activated. The first activation
is delayed 2 sec. No Fault reset influence when at least one alarm is active. Output opens when Alarm
list is empty.
Logical 0
Constant value that can be configured to any input or output - mainly in PLC.
Logical 1
Constant value that can be configured to any input or output - mainly in PLC.
Alarm BlinkAct
Alarm indication:
Output starts switching (blinking 0,5/0,5sec from opened or closed state) when any new alarm
comes
Output stays closed after Fault reset when any alarm is still active
Output opens after Fault reset when no alarm is active.
FltResButtEcho
The output is closed for 1 sec when Fault reset button (e.g. from DriveMonitor is activated).
No GPS Signal
The output is active when GPS signal from any reason disappear (broken antenna, no GPS signal,
GPS module fail) even if setpoint Position / GeoFencing = DISABLED.
BO 1/2 Fail
Indication of Binary output 1 and/or Binary output 2 fail or Broken wire detection. It has to be activated
by opened jumper BOUT-BW 1 and/or 2.
BO 3/4 Fail
Indication of Binary output 3 and/or Binary output 4 fail or Broken wire detection. It has to be activated
by opened jumper BOUT-BW 3 and/or 4.
User Button 15
InteliVision function buttons can be assigned to these five LBOs.


Operator ID
Operator identification fail output indication is in history list only (not in Alarm list).
RemoteControl18
Remote control outputs can be controlled locally or remotely (via Modem) from
DriveMonitor/InteliMonitor Remote switch panel.

Prg. states
Programmable states (protections) list. Any item from the following list activates Alarm list indication.
ECU
ECU communications fail indication
SHBIN 1..4
Status of shared Binary inputs
SHAIN 1..4
Status of shared Analogue inputs
SHBinCfgErr
Shared Binary module configuration error i.e. more than one source was configured (is on the CAN2
bus).
SHAinCfgErr
Shared Analog module configuration error i.e. more than one source was configured (is on the
CAN2 bus).
UnivState 1...7
The output closes when any Warning alarm is active. Output opens when all Wrn alarms disappear
and Fault reset is pressed (no Wrn alarm in Alarm list).
PLC Message 1...8
Indication of programmable PLC state.
ECU AlarmList
Output is closed when at least one item is in ECU Alarm list.
GeoFencing
The output is active if GeoFenging is announced the actual position is out of fence
MasterCommErr
Communication with Master control unit fails.

Note:
Related to ID-Mobile Slave control unit only


Battery Volt
Indication when battery voltage of the controller is out of protection limits (setpoints Basic Settings /
Batt<V and Basic Settings / Batt>V)
WrnServiceTime
Output is closed when Service Time (Statistics / Service Time) counts down (= 0).

Note:
History record and Alarm list indication is activated as well
Analog Inputs (AIN)

NAME Text Maximum 14 charts
DIM -, RPM, ppl, bps, Bar, s, V,
h, min, m, C, kPa, l, km/h,
%, l/h
Dimension of the value
SENSOR
AIN1 AIN7
None Non sensor is selected
020 mA Current input within listed intervals
02400 ohm Resistance input within listed intervals
05V Voltage input within listed intervals
User Sensor characteristic created by the user
NOTE:
For more details see DriveConfig User Guide
AIN8 AIN11
+-20mA Current input within listed intervals
02400 ohm Resistance input within listed intervals
+-1V Voltage input within listed intervals
+-100mV Millivoltage input within listed intervals
-1.0V2,5V Voltage input within listed intervals
Thermocopl K/C (K/F)
Predefined characteristic for usual type of
thermocouples
Thermocopl L/C (L/F)
Thermocopl J/C (J/F)
RESOLUTION 1; 0,1; 0,01; 0,001; 0,0001 Definition of decimal point for AIN
SENSOR RANGE 09999 Definition of sensor range for AIN
PROTECTION No Protection No protection is active on AIN
Sensor Fail Measured value is out of sensor characteristic
Warning Activated Wrn
HistRecOnly Protection is written in the history only
ACTIVE WHEN Under Limit Protection is active if a value is under selected limit
Over Limit Protection is active if a value is over selected limit
Under limit + Fls Protection is active if a value is under selected limit
and/or sensor fail is indicated


Over Limit + Fls Protection is active if a value is over selected limit and/or
sensor fail is indicated
BLOCK TYPE All the time Protection is active all the time
Force Block Protection is active only when is set LBI Force Block
RunOnlyBlkDel Protection is active only if engine is running with delay
from start
BARGRAPH 0% -99999999 Value related to 0% of Bargraph
BARGRAPH 100% -99999999 Value related to 100% of Bargraph
FUNCTION Logical function See more details in Logical analog inputs
Logical analog inputs (LAI)
Engine Speed
Logical RPM value for Engine RPM indication, overspeed protection, engine running and overload
detection.

RPM1
Engine Speed
LAI
Engine RPM
(value)
State Machine
Default configuration
ECU-RPM

Oil Press
Logical value for oil pressure indication on displays (non-editable screen) value Engine Values / Oil
Press. Value can be used as engine Running indication.

NOTE:
The dimension and number of decimal points is according to the source (AIN, ECU-AIN)
Oil Temp
Logical value for oil temperature indication on displays (non-editable screen) value Engine Values /
Oil Temp.

NOTE:
Coolant Temp
Logical value for coolant temperature indication on displays (non-editable screen) value Engine
Values / Cool Temp.

NOTE:
Fuel ConsAct
LAI can be lined to external Fuel consumption sensor (Flowmeter) or ECU Fuel rate value. This input
is a source for Statistics calculation.


LAI:
Fuel ConsAct
Statistics
LBI: Clear TotalCons
LBI: Clear TripCons
Imp/Unit
IM1
RPM/FlowMeters
Pulses IM1
Impulse
Input 1
Analog input x [L/h]
Fuel sensor
ECU
J1939
Fuel Rate [ L/h ]
FlowMeter IM1 [ L/h1 ]
Imp/Unit
IM2
Fuel sensor
Impulse
Input 2
TotalConsumpt [ L ]
Time Zone x [ s ]
Consump Zone x [ L ]
TripConsumpt [ L ]
RPM/FlowMeters
Pulses IM1

TempComp AIN8 .. TempComp AIN11
Temperature correction for AIN8 AIN11 if Thermocouple are used. E.g. TempComp AIN8 =
compensation temperature for AIN8.
Average Value
LAI is a source for Statistics / TripAverage and Statistics / TotalAverage calculation.
Average Speed
LAI is a source for Statistics / AverageSpeed calculation.
Shared virtual I/O periphery
It is often required that certain signals be brought to all controllers in the group. For example binary
signals: System Start/Stop, Common Shutdown signal etc. Sometimes analog signals are required as
well, like engine room temperature signal, where too high temperature can cause the nominal power
of all gen-sets in the room to be reduced (power derating function).
ID-Mobile-Logger can be used for data logging of signals connected to this equipment or use this
sophisticated system of shared virtual modules, where one controller is a signal server and the other
controllers are recipients of this signal. The signals are distributed via the CAN bus which typically
interconnects all the controllers on one site.
Configuration
These virtual modules can be added / removed like any other HW module in DriveConfig / card
Modules. Then they appear in the list of inputs or outputs in the card I/O.
SHBOUT/SHAOUT modules
They behave like standard output modules, but the signals assigned to them dont appear on any
physical output, instead of that are distributed via the CAN bus to other controllers. Each module has 4
outputs.


SHBIN/SHAIN modules
They behave like standard input modules, i.e. you can assign any logical input signal that is available
in the controller to them, or configure a protection based on their activity. Each module has 4 inputs.
SHBOUT + SHBIN modules
There are four channels (4 groups of 4 binary inputs/outputs) available for binary signal sharing. Each
channel can have its source (SHBOUT module) in different controller. All other controllers can be
configured as the recipients of this channel (SHBIN module).

SOURCE
(SHBOUT)
TARGET
(SHBIN)
TARGET
(SHBIN)
TARGET
(SHBIN)
I
n
t
e
r
c
o
n
t
r
o
l
l
e
r

C
A
N

b
u
s

Hint:
If more controllers are selected to be the source for one channel, only the controller with the lowest
CAN address is taken into account, and all controllers report a SHBinCfgErr message in Alarmlist.

The picture below shows the principle of the SHBOUT module. It can distribute the forwarded states of
physical binary inputs, or some signals created inside the controllers FW or PLC:

P
H
Y
S
I
C
A
L
B
I
N
A
R
Y
I
N
P
U
T
S
CONTROLLER
STATE
MACHINE
L
O
G
I
C
A
L

I
N
P
U
T
S
L
O
G
I
C
A
L

O
U
T
P
U
T
S
S
H
B
O
U
T
Intercontroller CAN bus
SYSTEM START

In this particular example, the SYSTEM START signal which should command the start / stop for all
the controllers on the site, is transferred from the terminal (physical binary input) to the SHBOUT
module.

All other controllers on the site should be configured in the way that the signal is picked up in the same
position (1-4) where it has been assigned to in SHBOUT module. The signal is then picked up from
the module and can be used by the controllers FW or PLC like any other physical binary input:


P
H
Y
S
I
C
A
L
B
I
N
A
R
Y
I
N
P
U
T
S
CONTROLLER
STATE
MACHINE
L
O
G
I
C
A
L

I
N
P
U
T
S
L
O
G
I
C
A
L

O
U
T
P
U
T
S
S
H
B
I
N

Together looks like this:
SHBOUT1
1
1. CONTROLLER 2. CONTROLLER
CAN2
Sys start/stop
C
A
N
2
3. CONTROLLER
BOUT
BOUT4
BOUT3
BOUT2
SHBIN1
BIN1
BIN4
BIN3
BIN2
SHBIN1
BIN1
BIN4
BIN3
BIN2
C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
Setpoints
Logical
Inputs
Logical
Outputs
C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
Setpoints
Logical
Inputs
Logical
Outputs
C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
Setpoints
Logical
Inputs
Logical
Outputs
SHAOUT + SHAIN modules
There are four channels (four group of 4 analog inputs/outputs) available for analog signal sharing.
The channel can have its source (SHAOUT module) only in one controller. All other controllers can be
configured as the recipients of this channel (SHAIN module).

SOURCE
(SHAOUT)
TARGET
(SHAIN)
TARGET
(SHAIN)
TARGET
(SHAIN)
I
n
t
e
r
c
o
n
t
r
o
l
l
e
r

C
A
N

b
u
s

Hint:
If more controllers are selected to be the source for the analog channel, only the controller with the
lowest CAN address is taken into account, and all controllers report a SHAinCfgErr message in
Alarmlist.

The picture below shows the principle of the SHAOUT module. It can distribute the forwarded values
of externally measured (physical) analog inputs, as well as the values measured or computed inside
the controllers FW or PLC:


P
H
Y
S
I
C
A
L

A
N
A
L
O
G

I
N
P
U
T
S
CONTROLLER
STATE
MACHINE
L
O
G
I
C
A
L

I
N
P
U
T
S
M
E
A
S
U
R
E
D

V
A
L
U
E
S
S
H
A
O
U
T

All other controllers on the site should be configured in the way that the value is picked up in the same
position (1-8) where it has been assigned to in SHAOUT module. The value is then picked up from the
module and can be used by the controllers FW or PLC like any other physical analog input:

P
H
Y
S
I
C
A
L

A
N
A
L
O
G

I
N
P
U
T
S
CONTROLLER
STATE
MACHINE
L
O
G
I
C
A
L

I
N
P
U
T
S
M
E
A
S
U
R
E
D

V
A
L
U
E
S
S
H
A
I
N

Together looks like this:

C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
SHAOUT1
AOUT 1
AOUT 2
AOUT 3
AOUT 4
Setpoints
1 . CONTROLLER
C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
SHAIN1
AIN 1
AIN 2
AIN 3
AIN 4
Setpoints
2 . CONTROLLER
CAN2
Temperature X
C
A
N
2
Temp X
Temp X
Logical
Inputs
Logical
Outputs
Logical
Inputs
Logical
Outputs
3 . CONTROLLER
C
o
n
t
r
o
l
l
e
r
F
u
n
c
t
i
o
n
s
SHAIN1
AIN 1
AIN 2
AIN 3
AIN 4
Setpoints
Temp X
Logical
Inputs
Logical
Outputs


Values
RPM/FlowMeters
FlowMeter IM1
Calculated value of universal flow, default volume unit is L/h1. Volume unit can be modified by user in
DriveConfig - Translator. For correct calculation it has to correspond with volume unit of setpoints
IMP/Unit IM1 and TPresUnit IM1.
FlowMeter IM2
Calculated value of universal flow, default volume unit is L/h2. Volume unit can be modified by user in
DriveConfig - Translator. For correct calculation it has to correspond with volume unit of setpoints
IMP/Unit IM2 and TPresUnit IM2.
Pulses IM1
Counter of impulses in impulse input INP1.
Pulses IM2
Counter of impulses in impulse input INP2.
Imp/Unit
IM1
RPM/FlowMeters
Pulses IM1
Impulse
Input 1
Fuel sensor FlowMeter IM1 [ L/h1 ]
Imp/Unit
IM2
Fuel sensor
Impulse
Input 2
Pulses IM1

Basic Values
Engine RPM
Actual value RPM what can be sourced from different sources: RPM1, ECU-RPM or physical Analog
input (depends on configuration Logical Analog Input Engine Speed).
RPM
Value of physical RPM1 input (pin 79 and 80.


Engine Values
Oil Press
Oil Pressure [Bar] what can be sourced by different input set to Logical Analog Input Oil Press. Oil
Press value can be used as engine Running indicator, see Setpoints / Basic Settings / Running Poil.
Oil Temp
Oil Temperature [C] what can be sourced by different input set to Logical Analog Input Oil Temp.
Cool Temp
Coolant Temperature [C] can be sourced by different input set to Logical Analog Input Collant Temp.
Analog CU
Values are shown and titled according to configuration AIN1 AIN11:

and
Battery Volt
Voltage of the battery (Power source for the controller).
CPU Temp
Processor temperature of the controller.
Binary CU
ID BIN
Binary inputs according to configuration


ID BOUT
Binary outputs according to configuration

Log Bout
LogBout 1, 2
Logical binary functions.


RemoteControl
Remote control switches status.

Info
Engine State
Engine state: Running, Not Running, Ready to Start, Cranking, Cooling etc.
PasswordDecode
This code together with controller S/N is needed if controller password is forgotten.
Operator ID
Identification number of the operator what is read from Operator Key.
SW Version
SW version of the controller.
SW Branch
SW branch identification.
ECU DiagSource
Indication of ECU diagnostic codes source. Typically: None, J1939-DM1, J1939-KWP, J1587-DTC,
MODBUS.
GSMSignalLevel [%]
Indicating quality of GSM signal.
GSM Diag Code:
Troubleshooting diagnostic code for ID-Mobile GSM/GPRS module


Code Description Code Description
0 OK. No error. 11
SIM card is locked (Possibly PIN code required, PIN
needs to be deactivated) or unknown status of SIM
locking
1 Not possible to hang up. 12 No GSM signal
2 ID-Mobile-GPRS is switched off 13 Not possible to read the SIM card parameters
3 ID-Mobile-GPRS is switched on 14
GSM modem did not accepted particular initialization
command, possibly caused by locked SIM card
4 ID-Mobile-GPRS error in initialization 15 Unknown modem
5 ID-Mobile-GPRS not possible to set the APN 16 Bad answer to complement initialization string
6
ID-Mobile-GPRS not possible to connect to
GPRS network
17 Not possible to read GSM signal strength
7
ID-Mobile-GPRS not possible to retrieve IP
address
18 CDMA modem not detected
8
ID-Mobile-GPRS not accepted DNS IP
address
19 No CDMA network
9 Error in modem detection 20 Unsuccessful registration to CDMA network
10 Error in initialization of analog modem 255 Only running communication is needed to indicate
AirGate Diag
AirGate troubleshooting diagnostic code

AirGate ID
Identification number generated by AirGate server to establish connection with: DriveMonitor,
InteliMonitor, WebSupervisor.

CAUTION!
Connection via AirGate is supported with ID-Mobile GPRS module only (ID-Mobile GSM module does
NOT support AirGate).
Modem Status
Indication of modem state:
----- after controller initialization
Trying modem active, trying to establish connection
Ready modem ready, communication with mode
Trying modem active, trying to establish connection
Ready modem ready, communication with modem is ok
m ok.
Statistics
Run Hours [h]
Engine running hours.
Code Description
1
Controller registered, waiting for authorization
2
Not possible to register, controller blacklisted
3
Not possible to register, server has no more capacity
4
Not possible to register, other reason
5
Controller registered and authorized


Run Seconds [s]
Engine running seconds.
NOTE:
Total run time = Run Hours + Run Seconds
Service Time [h]
Time to next service/maintenance period. This value can be set by setpoint Basic Settings / Service
Time.
TotalConsumpt [liters]
Total consumption is calculated from source set in LAI Fuel ConsAct. It can be analog input or ECU
value (for conversion to right range and dimension can be used User Curves) or impulse inputs IMP1
or IMP2 (recalculated with parameter Imp/Unit IM1 or Imp/Unit IM2). The value can be reseted by LBI
ClearTotalCons or set to user value with InteliMonitor/DriveMonitor from menu Monitor Set
Statistics
TripConsumpt [liters]
Total consumption is calculated from source set in LAI Fuel ConsAct. It can be analog input or ECU
value (for conversion to right range and dimension can be used User Curves) or impulse inputs IMP1
or IMP2 (recalculated by parameter Imp/Unit IM1 or Imp/Unit IM2). The value can be reseted by LBI
ClearTripCons or set to user value via InteliMonitor/DriveMonitor from menu Monitor Set Statistics
LAI:
Fuel ConsAct
Statistics
LBI: Clear TotalCons
LBI: Clear TripCons
Imp/Unit
IM1
RPM/FlowMeters
Pulses IM1
Impulse
Input 1
Analog input x [L/h]
Fuel sensor
ECU
J1939
Fuel Rate [ L/h ]
Imp/Unit
IM2
Fuel sensor
Impulse
Input 2
TotalConsumpt [ L ]
Time Zone x [ s ]
Consump Zone x [ L ]
TripConsumpt [ L ]
RPM/FlowMeters
Pulses IM1

TripAverage
Trip Average Value calculates the arithmetic average of common value if the calculation is activated
with LBI TripAverageEna as long the value is reseted with LBI TripAverageRes. Input for average
value calculation is set in LAI AverageValue. Common for average value calculation is e.g. RPM,
Pressure, Temperatures. For reset is commonly used e.g. OperatorID, Start Button, Fault Reset etc.
TotalAverage
Total Average Value calculates the arithmetic average of common value if the calculation is activated
with LBI TotalAverageEna as long the value is reseted with LBI TotalAverageRes. Input for average
value calculation is set in LAI AverageValue. Common for average value calculation is e.g. RPM,
Pressure, Temperatures. For reset is commonly used e.g. OperatorID, Start Button, Fault Reset etc.


AverageSpeed
Average Speed calculates the arithmetic average of common value if the calculation is activated with
LBI AverageSpeedEna as long the value is reseted with LBI AverageSpeedRes. Input for average
value calculation is set in LAI Average Speed (e.g. GroundSpeed, Speed from ECU, Dashboard
Speed etc.). For reset is commonly used e.g. OperatorID, Start Button, Fault Reset etc.
Time Zone 16 [s]
Time spent in configured zone. Each statistic zone is defined with Engine RPM and Fuel consumption
(see setpoints in group Statistics). For calculation into defined zone has to be fulfilled both conditions:
RPM Start Z1 < actual RPM < RPM End Z1 and Fuel Start Z1 < actual Fuel Consumption < Fuel End
Z1. Calculation to Zone 13 can be activated with LBI Zone x ON too.
Consump Zone 16 [L]
Fuel consumption in configured zone. Each statistic zone is defined with Engine RPM and Fuel
consumption (see setpoints in group Statistics). For calculation into defined zone has to be fulfilled
both conditions: RPM Start Zx < actual RPM < RPM End Zx and Fuel Start Zx < actual Fuel
Consumption < Fuel End Zx. Calculation to Zone 13 can be activated with LBI Zone x ON too.

E.g. for setting:
Z1 Z2 Z3
RPM Start 0 RPM 0 RPM 1000 RPM
RPM End 1000 RPM 2000 RPM 2000 RPM
Fuel Start 0 L/h 100 L/h 0 L/h
Fuel End 100 L/h 200 L/h 100 L/h
LBI: Zone x ON OFF OFF ON
Actual value RPM = 800 and fuel consumption = 50 L/h activates zones Z1 and Z3.
Position
Actual Lat [m]
Actual GPS Latitude value (e.g. 506'51.463"N).
Actual Long [m]
Actual GPS Longitude value (e.g. 1428'54.269"E).
HomePosDist [m]
Distance from Home position in meters. Home position is set by setpoints Position Home Lat and
Home Long.
Error Lat [m]
Latitude error in meters.
Error Long [m]
Longitude error in meters.
SatelitesUsed [-]
Number of used GPS satellites.


MSL Altitude [m]
Altitude above sea level in meters.
Ground Speed [km/h]
Actual ground speed in km/h.


Setpoints
Password
There are three levels of password protection.
0. User level allows change of non-protected setpoints only
1. Operator level allows change of setpoints protected by Operator level
2. Master level allows change of setpoints protected by Operator and Master level
3. Supervisor highest level allows all setpoints or configuration changes, firmware upgrade.
Hint:
Grey color of setpoint in InteliMonitor indicate the setpoint is password protected.
EnterPassword
Password is max. five-digit number. All three levels password can be from InteliMonitor / DriveMonitor
- menu: Monitor -> Change password

Any password can be changed once that level password or higher has been entered.
Access code
Access Code is used for remote access to the controller - via modem, Internet, AirGate. It can be
changed from InteliMonitor / DriveMonitor - menu: Monitor -> Change access code It can be up to
16 ASCII characters. At first the Password3 has to be entered before the new Access code can be
changed.


Commands protection
Commands password protection protects following commands from InteliMonitor / DriveMonitor menu:
ClearStatistics, EngRun Hours, RemoteSwitch, SetHomePosition, TotalConsumption and
TripConsumption. To set commands protection from DriveConfig / card Commands.

Basic Settings
Engine Name
Dimension: [ - ]
Range: max. 15 characters

User defined name, used for controller identification at remote phone or mobile connection.
Engine name has to be entered manually using DriveConfig / DriveMonitor / InteliVision software.

NOTE:
Engine name is not changed when new archive is loaded. Check Engine name after firmware
upgrade.
Engine Type
Dimension: [ - ]
Range: max. 15 characters

User defined name, used for controller identification at remote phone or mobile connection.
Engine type has to be entered manually using DriveConfig / DriveMonitor / InteliVision software.

Gear Teeth
Dimension: [ - ]
Range: 1 - 500
Step: 1
Terminals: 79 - 80

Number of teeth on the engines flywheel for the pick-up related to RPM input . Internal value Engine
speed is in default connected to RPM input if there is no other configuration to ECU or PLC function.
Nominal RPM
Dimension: [ RPM ]
Range: 30 - 4000
Step: 1 RPM
Terminals:


Nominal engine speed, base for Over-speed protection limit.
Oper ID Alarm
Dimension: [ - ]
Range: DISABLED, WARNING

Incorrect identification of Operator ID with Operator Key:
DISABLED No alarm is activated with new start.
WARNING Warning Operator ID is recorded to history when Operator Key is not applied
during power switch on.
Starting RPM
Dimension: [ RPM ]
Range: 30 Nominal RPM
Step: 1

RPM limit for running engine detection.
Running POil
Dimension: [ Bar ]
Range: 0,00 10,00
Step: 0,01

Oil pressure limit to be engine detected as running when no RPM pickup (or ECU RPM) is not used.
RunOnlyBlkDel
Dimension: [ s ]
Range: 0 60
Step: 1

Delay for Engine running Alarms activation.
BINARY INPUT
Physical
closed
BINARY INPUT
Internal value
BinInp delay
Engine running
state
RunOnlyBlkDel
PROTECTION
inactive active

BinInp Delay 1 .. 3
Dimension: [ s ]
Range: 0 60
Step: 1

Binary input protection is activated when input is closed for longer time than BinInp delay.
DriveConfig: I/O, Property, Protection active = Closed
BINARY INPUT
BinInp delay
physical
BINARY INPUT
Internal value
no change


BINARY INPUT
BinInp delay
physical
BINARY INPUT
closed
Internal value

BINARY INPUT
BinInp delay
physical
BINARY INPUT
Internal value
DriveConfig: I/O, Property, Protection active = Opened
opened

ForceBlock Del
Dimension: [ s ]
Range: 0 60
Step: 1

Delay for Force block protection activation after Binary input Force block is opened. Protection
deactivation is without delay. Protection is activated/deactivated independent on engine running or not
running state.
BINARY INPUT
ForceBlock del
FORCE BLOCK
Protection
closed
BINARY INPUT
Prot, block type = Force block
closed
active
active
inactive

Batt <V
Dimension: [ V ]
Range: 8,0 40,0 (Batt >V) )
Step: 0,1

Under voltage of controller power supply.
Batt >V
Dimension: [ V ]
Range: 8,0 (Batt <V) ) 40,0 V
Step: 0,1

Overvoltage of controller power supply
Batt Volt Del
Dimension: [ s ]
Range: 0 600
Step: 1

Delay for battery voltage alarms Batt <V and Batt <V. .
Service Time
Dimension: [ h ]
Range: 0 65535


Step: 1

Running hours down counter is decremented when engine is running. Service alarm is indicated in
Alarm list and History record activated when counter reach zero. Service time setpoint is actual
counter value.

NOTE:
Once the service time has elapsed the Service time will have to be adjusted to non-zero value (at least
for 30sec) to clear the alarm and begin a new countdown.
LB/UART Log
Dimension: [ - ]
Range: DISABLED, ENABLED

Set if in history is saved event Access Set when equipment is logged to WebSupervisor:
ENABLED = there is regularly written record to history, when equipment is logged to
WebSupervisor
DISABLED = there is written no record to history, when equipment is logged to WebSupervisor.
Comms Settings
ControllerAddr
Dimension: [ - ]
Range: 1 - 32
Step: 1

Controller CAN bus and RS-485 identification number. Each controller has to have its own unique
number. When opening connection to the controller (using PC monitoring/control SW), the Controller
address has to correspond to the setting in PC SW.
RS485 Mode
Dimension: [ - ]
Range: STANDARD, MODBUS, ECU LINK

Communication protocol selection:
STANDARD - InteliDrive (DriveMonitor, DriveConfig) communication protocol.
MODBUS - Modbus RTU protocol.
ECU LINK - ECU communication via RS485.
MODBUS
Dimension: [ bps ]
Range: 9600, 19200, 38400, 57600

Modbus interface baud rate setting
ComApPort
Dimension: [ - ]
Range: 1 65535, default = 23
Step: 1

Port number for ComAp communication over ID-Mobile-GPRS (AirGate)


APN Name
Dimension: [ - ]

Access point name (APN) for mobile network communication. This information shall provide
GSM/GPRS operator. E.g. Vodafone UK: pp.Vodafone.co.uk.
APN UserName
Dimension: [ - ]

User name for APN access point for GPRS network connection. This information shall provide
GSM/GPRS operator. E.g. Vodafone UK: web.
APN UserPass
Dimension: [ - ]

User password for APN access point for GPRS network connection. This information shall provide
GSM/GPRS operator. E.g. Vodafone UK: web.
AirGate IP
Dimension: [ - ]
Default: airgate.comap.cz

IP address of AirGate server.
DNS IP
Dimension: [ - ]
Default: 8.8.8.8

IP address of Domain Name Server.

RPM/FlowMeters
Imp/Unit IM1
Dimension: [ i/L1 ]
Range: 0,0 6500,0
Step: 0,1

Set number of impulses in IMP1 what corresponds to volume unit L1. Concrete volume unit is possible
to specify in DriveConfig - Translator by change dimension L1.
Imp/Unit IM2
Dimension: [ i/L2 ]
Range: 0,0 6500,0
Step: 0,1

Set number of impulses in IMP2 what corresponds to volume unit L2. Concrete volume unit is possible
to specify by Translator in Drive Config by change dimension L2.


Imp/Unit
IM1
Pulses IM1
Impulse
Input 1
Fuel sensor FlowMeter IM1 [ L/h1 ]
Imp/Unit
IM2
Fuel sensor
Impulse
Input 2
Pulses IM1

EvalPeriod IM1
Dimension: [ s ]
Range: 0,1 10,0
Step: 0,1

Evaluation interval for measurement IMP1, default value is 0,1 s.
EvalPeriod IM2
Dimension: [ s ]
Range: 0,1 10,0
Step: 0,1

Evaluation interval for measurement IMP2, default value is 0,1 s.
TPresUnit IM1
Dimension: [ ]
Range: HOUR, MIN, SEC
Presentation time interval for measurement number of impulses IMP1 and calculation of FlowMeter
IM1. Default value is HOUR. If setting is changed to different value (MIN or SEC), in DriveConfig -
Translator has to be set manually dimensions L/h and L/h1 to correct value!
TPresUnit IM2
Dimension: [ ]

Presentation time interval for measurement number of impulses IMP2 and calculation of FlowMeter
IM2. Default value is HOUR. If setting is changed to different value (MIN or SEC), in DriveConfig -
Translator has to be set manually dimensions L/h and L/h2 to correct value!
FlowIntTimUnit
Dimension: [ ]

Presentation time interval for calculation of statistics values: TotalConsumpt and TripConsumpt. For
correct calculation it has to be set to same value as TPresUnit IM1 or TPresUnit IM2 what is used for
consumption measurement (set in LAI Fuel ConsAct).


Analog Inputs
AIN1 Offset AIN11 Offset
Dimension: [ - ]
Range: -32767 - 32767
Step: 1

Adjustable offset related to analog input AIN1AIN11.
Act. Calls/SMS
Warning Call
Dimension: [ - ]

Enables or disables active calls/SMS to selected phone numbers when a Warning alarm occurs.
Shut Down Call
Dimension: [ - ]

Enables or disables active calls/SMS to selected phone numbers when a Shut down alarm occurs.
Cool Down Call
Dimension: [ - ]

Enables or disables active calls/SMS to selected phone numbers when a Cool down alarm occurs.
AcallCH13-Type
Dimension: [ - ]
Range: DISABLED, DATA, SMS

For active call are available 3 channels. Each can be set:
DISABLED - Channel is disabled
DATA - Standard analog, GSM or ISDN modem connection to DriveMonitor.
SMS - Channel sends SMS message. Only when is GSM modem connected.
Example of SMS:
AL=(Sd Water Temp,Wrn Water Temp,!Emerg Stop,ActCallCH1Fail)
AcallCH13-Addr
Dimension: [ - ]
Range: Phone number

Phone numbers for 3 active channels used for data connection or SMS. For GSM numbers use either
national format (i.e. like number you will dial if you want to make a local call) or full international format
with "+" character followed by international prefix in the beginning.
Num Rings AA
Dimension: [ - ]


Range: 1 30

Number of rings prior to open modem connection from PC to controller. The change is accepted after
controller is switched on or when modem is connected to controller.
A.C.Multiplier
Dimension: [ - ]
Range: 1 250

Number of attempt to open the active call data connection when the phone line is engaged. Timeout
for connection is 90 sec and after 120 sec controller starts the next attempt. Incoming calls are
blocked during the time the controller is trying to send an active call type. This setting doesnt refer
number of attempt to send SMS (it is fixed = 5 attempts).
Modem
Dimension: [ - ]
Range: TELIT 3G, TELIT GPRS, SIMCOM CSD, SIMCOM GPRS

Selection of internal modem mode:
TELIT 3G: UMTS modem, support only fundamental data connectivity and sending SMS. AirGate
and WebSupervisor support is not included!
TELIT GPRS: for special custom application only.
SIMCOM CSD: module works as standard GSM modem enabling CSD (Circuit Switch Data)
connection to controller with InteliMonitor / DriveMonitor and sending alarm SMS.
SIMCOM GPRS: module for GPRS communication of controller with InteliMonitor / DriveMonitor
via AirGate and with WebSupervisor.

NOTE:
UMTS, GPRS and CSD services has to be provided by your mobile operator for successful operation.
Any software update of the controller is not supported via wireless connection. Software update can
be done via direct connection only.
Date/Time
Time
Dimension: [ hh:mm:ss ]

System (controller) time can be modified here. The system time is stored in a battery-backup RTC
circuit and normally need not to be adjusted except initial setting and occasional corrections. The
system date and time is used for the exercise timers as well as for the history log. Each record in the
history log contains a date/time stamp.

NOTE:
If the system date and time get incorrect after the controller has been switched off for longer time, it
may indicate the backup battery needs to be replaced.
Date
Dimension: [ dd:mm:yyyy ]

System date can be modified here. The system date is stored in a battery-backup RTC circuit and
normally does not need to be adjusted except initial setting. The system date and time is used for the
exercise timers as well as for the history log. Each record in the history log contains a date/time
stamp.


NOTE:
If the system date and time get incorrect after the controller has been switched off for longer time, it
may indicate the backup battery needs to be replaced.
Time Stamp Per
Dimension: [ s ]
Range: 0 14400
Step: 1

Standard history record period.
Time Stamp Del
Dimension: [ s ]
Range: 0 (Time Stamp Per) ) 14400
Step: 1

Time delay after engine stop when the Time Stamp Per records are still provided.
Fast Stamp Per
Dimension: [ s ]
Range: 0 600
Step: 1

Faster History records are provided after any Alarm (see in Setpoints / Limits ) is activated.
Fast Stamp Del
Dimension: [ min ]
Range: 0 100
Step: 1

Time duration of the Fast stamp records.
Engine
Not running
Running Engine Not running
Time Stamp Per
Time Stamp Del
Alarm
Fast Stamp Per
Fast Stamp Del
Time Stamp Per
No periodic
records
Periodic records
No periodic
records
No Alarm

HistoryEntries
Dimension: [ - ]
Range: ALL TIME, RUNNING ONLY, BI HISTORY

The history can be forced to list as follow:
ALL TIME: History records are active all time
RUNNING ONLY: History is recorded when engine is running only
BI HISTORY: History record is forced when LBI BI History is activated.


SummerTimeMod
Dimension: [ - ]
Range: DISABLED, WINTER, SUMER, WINTER-S, SUMMER-S

Summer/Winter time applied:
DISABLED: Automatic switching between summer and wintertime is disabled.
WINTER (SUMMER): Automatic switching between summer and wintertime is enabled set
to winter (summer) season.
WINTER-S (SUMMER-S): same as above modified for southern hemisphere.

Statistics
RPM Start Z16
Dimension: [ - ]
Range: 0 RPM End Z16

RPM trigger start RPM value for initiation of statistic Zone 16 counting. RPM source is LAI Engine
Speed.
RPM End Z16
Dimension: [ -]
Range: RPM Start Z16 Nominal RPM

RPM trigger stop RPM value for initiation of statistic Zone 16 counting. RPM source is LAI Engine
Speed.
Fuel Start Z16
Dimension: [ L/h]
Range: 0,0 Fuel End Z16

Consumption trigger start value for initiation of statistic Zone 16 counting. Consumption source is
LAI Fuel ConsAct.
Fuel End Z16
Dimension: [ L/h]
Range: Fuel Start Z16 1000,0

Consumption trigger stop value for initiation of statistic Zone 16 counting. Consumption source is
LAI Fuel ConsAct.

For calculation into defined zone has to be fulfilled both conditions: RPM Start Zx < actual RPM <
RPM End Zx and Fuel Start Zx < actual Fuel Consumption < Fuel End Zx. E.g. for setting:

Z1 Z2 Z3
RPM Start 0 RPM 0 RPM 1000 RPM
RPM End 1000 RPM 2000 RPM 2000 RPM
Fuel Start 0 L/h 100 L/h 0 L/h
Fuel End 100 L/h 200 L/h 100 L/h

Actual value RPM = 800 and fuel consumption = 50 L/h activates zones Z1.


Position
Home Lat
Dimension: [0 0 0.000N ]

Reference point latitude for GeoFencing function. It can be set manually or with LBI Home Position -
active input (rising edge) moves the actual position into Position / Home Lat and Position / Home
Long setpoints.
Home Long
Dimension: [0 0 0.000E ]

Reference point longitude for GeoFencing function. It can be set manually or with LBI Home Position -
active input (rising edge) moves the actual position into Position / Home Lat and Position / Home
Long setpoints.
Fence Radius
Dimens ion: [ m ]
Range: 10 10 000
Step: 1

Maximal allowed distance in meters from Home position (Home Lat and Home Long). Once the
controller is out of Fence Radius, Wrn GeoFencing is announced and history record is written
immediately.
Fence Delay
Dimension: [ s ]
Range: 30 60000
Step: 1

Once the controller is out of F Fe en nc ce e R Ra ad di iu us s and F Fe en nc ce e D De el la ay y time elapsed the engine is shut down.

NOTE:
This setpoint isnt functional in ID-Mobile-Logger.
Geo Fencing
Dimension: [ - ]
Range: DISABLED, ENABLED, BI.INPUT

Activates/deactivates Geo Fencing functionality:
ENABLED: GeoFencing is enabled
DISABLED: GeoFencing is disabled
BIN.INPUT: GeoFencing is enabled when by Binary input GeoFencingEna is closed.
Limits

All limits and protection types are configurable in DriveConfig
Min OilPress A / Max OilPress A
Dimension: [ Bar ]
Range: 0,0015,00


Step: 0,01

Low/High Oil pressure A limit. Alarm is indicated when actual pressure value is outside limit for time
Oil Press Del. .
Oil Press Del
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Oil Press protection limits Min OilPress A, Max OilPress A, Min OilPress B and Max OilPress
B.
Min OilPress B / Max OilPress B
Dimension: [ Bar ]
Range: 0,0015,00
Step: 0,1

Low/High Oil pressure B limit. Alarm is indicated when actual pressure value is outside limit for time
Oil Press Del. .
Max Oil Temp A/ Max Oil Temp B
Dimension: [ C ]
Range: -25130
Step: 1

High Oil Temperature A/B limit. Alarm is indicated when actual temperature value is over limit for time
Oil Temp Del. .
Oil Temp Del
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Oil Temperature protection limits Max Oil Temp A and Max Oil Temp B.
Max Cool Temp
Dimension: [ C ]
Range: -25130
Step: 1

High Coolant Temperature limit. Alarm is indicated when actual temperature value is over for time
Cool Temp Del. .
Cool Temp Del
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Coolant Temperature protection limits Max Cool Temp .


BoostPressure
Dimension: [ kPa ]
Range: 0500
Step: 1

Low Boost Pressure limit. Alarm is indicated when actual pressure value is below for BoostPress Del. .
BoostPress Del
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Boost Pressure protection limits BoostPressure.
Boost Temp
Dimension: [ C ]
Range: -25130
Step: 1

High Boost Temperature limit. Alarm is indicated when actual temperature value is over for Boost
Temp Del. .
Boost Temp Del
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Boost Temperature protection limits Boost Temp . .
Exhaust Temp A / Exhaust Temp B
Dimension: [ C ]
Range: -40950
Step: 1

High Exhaust Temperature A/B limit. Alarm is indicated when actual temperature value is over for
ExhaustTempDel. .
ExhaustTempDel
Dimension: [ s ]
Range: 0600
Step: 1

Delay for Exhaust Temperature protection limits Exhaust Temp A and Exhaust Temp B.


Remote control and data logging
Direct connection to the PC
ID-Mobile-Logger can be connected directly with PC via RS485 interface. Hence there is required
convertor to interface available in standard PC RS485 / RS232 or RS485 / USB.
Hint:
Note that not all USB/RS232 converters are working with DriveConfig and InteliMonitor / DriveMonitor.

Recommended USB/RS232 converters:
ASIX - UCAB232E (http://www.asix.cz/)
VPI - USS-101/111 (http://www.vpi.us/usb-serial.html)
C-232-MM (http://www.usbgear.com/item_288.html).
Modbus communication
Direct connection: RS485
Speed: 9600/19200/38400/57600 bps set from InteliMonitor / DriveMonitor setpoint Comms
Settings - MODBUS
Transfer mode RTU
Function 3 (Read Multiply Registers)
Function 6 (Write Single Register)
Function 16 (Write Multiply Registers)
The response to an incoming message is sent with minimum 4.096 ms delay after message
reception

The complete description of Modbus communication protocol can be found in Modbus Protocol
Reference Guide PI-MBUS-300 and Open Modbus Specification Release 1.0. Both documents are
available from web site at http://www.modicon.com/openmbus/ .
Communication object vs. Register
All the data intended for communication has its representation as communication objects in the
controller. The communication object is represented by the n-byte array in the controller memory and
identified by the unique 16-bit communication object number. The register, according to Modbus
communication protocol, represents a two-byte data and in communication functions is referenced by
16-bit register address. Further in the description of communication functions the communication
object number will always be used as a register address and length of the communication object
will be expressed by number of registers. Just one communication object can be read or written
by one communication function.
Hint:
It is possible to download actual ID-Mobile-Logger communication object and MODBUS register from
DriveConfig menu File -> Generate Cfg Image.
Event Log history
ID-Mobile-Logger has two separated memory for history records: Event History and Long History.
Event History
Short event history what is available on-line from InteliMonitor/DriveMonitor. This list is available via all
possible connections RS485, GSM/GPRS, AirGate. The length of this history is limited to max. about
100 records. Exact number of available records is done by defined list of values in DriveConfig
History.


Long History
The history for long time logging information. There is recorded same list of values as in Event History,
list is set in DriveConfig History. The length of Long History is done by size of record (number and
type of logged values):
Max. record size
[bytes]
Max. number of
records about
16 524 000
32 262 000
64 131 000
128 65 000
256 32 000

Because of the large amount of information, records arent available on-line via
InteliMonitor/DriveMonitor software. Long History has to be downloaded locally for off-line analysis
using the software LoggerHistoryExport.

There can be downloaded complete history records or only records from selected date range. History
records can be saved in XLS or CSV format. For more information see LoggerHistoryExport reference
guide.

Another possibility how to read Long History is use ComAp communication library what is
implemented using .NET 4.5 and is usable under Mono framework on Linux machines. Library
consists of 2 DLLs


ComAp.InteliServer.Base.dll
o Base library
ComAp.InteliServer.LowLevel.dll
o Implementation of a simple API.

Base library serves as a base for every other library that implements the real communication. Current
version supports communication over InternetBridge and Air Gate server.
Users do not use the Base library directly. Instead, LowLevel or another implementation must be used.
Reference help is provided in the forat of MSDN help (.chm).

Low level API implementation
Low level API provides easy access to basic commands:
Open/Close connection
Read communication object
Write communication object
Write command
Access to access key table, value storage and metadata.

All functions are implemented as asynchronous with callback on completion. Callback event
arguments contain data to fully identify what has completed.

Working with values
Communication with ComAp controller is based on reading and writing of so called communication
objects. Users must know the number of communication object that represents a value.

Metadata (struct ComObjMetadata)
The type system of controllers supports only simple data types. For convenience, it is possible to
register a metadata to communication object numbers for each controller and the library will transform
raw values to real values. Available transformations contain for example division of raw value or
mapping strings to values for string lists.

Interface description for read long history
24390 Max. number of records
in the long history
Unsigned32 Read only (# 87)
24389 Number of records in
the long history
Unsigned32 Read only If the history is full, the value is the
maximum number of records in a long
history (see comm. object 24390)
(# 87)
24388 The youngest record in
the long history
Domain Read only (# 87)
24387 Older record in the long
history
24386 The actual record in the
long history
Domain Read only Reads a record referenced by the current
red index value in a long history
(# 87)
24385 Setting the read index
in a long history to
record coresponding to
the specified timestamp
Domain6 Write only Set the read index in a long history at the
value coresponding to the given timestamp.
Adjusted index will match the record with the
given timestamp or the closest older record,
if the record with the timestamp doesnt
exist.
Long history is cyclical records sequence, in
this sense, is the closest older record after
the oldest record is the youngest record;
It isnt possible to set reading index, when
long history is empty (controler returns an
error response).
(# 87)
(# 88)


24384 Acknowledge full
indication memory for
the long history
Binary8 Write only (# 87)
(# 89)
24383 Write index in the long
history

24382 Read index in the long
history

24381 Younger record in the
long history

# 87
A long history is cyclical sequence of records. At the same time can preserve the history of the
number of records the value of the communication object 24390. Current number of records may be
obtained by reading the communication object 24389. Writing the new record will occupy the first free
item or overwrites (if history is full), the oldest entry. It is supposed that the history will be read starting
at the youngest record (communication object 24388) or record done by written timestamps (see
communication objects 24385 and 24386). Read follow records are made rereading the older record
(communication object 24387). After reading the oldest record follows the reading of the youngest
recording.
The value of read record may be invalid entry (bits 15 to 12 = 1111). Such a record should be ignored.

Operations performed with the communication objects 24385-24388 controller can reject with error
code:
0x080000F0 ... operation must be repeated
0x06010000 ... access denied - empty history

Operations performed with the communication objects 24382-24390 controller can reject with error
code:
0x080000F7 ... Invalid controller configuration

Operations performed with the communication object 24384 controller can reject with error code:
0x080000E3 ... invalid value

# 88
Format of timestamps entered by writing the communication object 24385:
[0] day (BCD)
[1] month (BCD)
[2] yer (BCD)
[3] hour (BCD)
[4] minute (BCD)
[5] second (BCD)

# 89
Format value of the communication object 24384:
b0 1 = acknowledgment indicator of full memory for a long history
b7-1 reserve (= 0).


Operator Identification
The Operator Key sets are available (as option) on request with maximal number of 255 operator IDs.

O
p
e
r
a
to
r
1
O
p
e
ra
to
r 2

Automatic iButton reading procedure:
The reading starts by touching the iButton to Probe. The probe is connected to pins 70 and 69,
see Physical input/output structure.
There is 5 sec timeout after successful reading when the iButton has to be removed before next
reading starts
Removing iButton during the reading procedure cause invalid code.
iButton code is displayed as value Operator ID (in group Info) and can be used for identification in
history or PLC

The valid iButton code is disabled to ##### indication after engine is stopped. The engine
running state is indicated on box green Run LED.
The valid iButton code can be reseted by LBI Reset Oper ID.


Booting procedure
After wrong upgrade process the controller doesnt respond (No LEDs are on), the only one way how
to upload the correct firmware is with using the Booting procedure
The ID-Mobile-Logger has no protection which is blocking incorrect FW of Mobile platform (ID-Mobile
firmware to ID-Mobile-Logger Hardware).

CAUTION!
Be sure the correct firmware is uploaded to the hardware

For booting is needed AT-link converter (ComAp product):

and standard null modem serial cable for connection AT link converter with PC - RS232 or
RS232/USB converter.


Booting procedure steps:

1) Connect the AT link converter to ID-Mobile-Logger:

uP
AIN1 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7
1 12
13 24
25 36
37 48
49 60
61 72
73 84
85 96
BOOT
GSM GPS
RS232
POWER
RUN
ALARM
STATUS
1
2
0
R
1-2: 20 mA
No jumper: 5 VDC
3-4: 2,4 kOhm
4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1
4-3-2-1 4-3-2-1 4-3-2-1 4-3-2-1
AIN8 AIN9 AIN10 AIN11
1-2: +- 20 mA
No jumper: +- 1 VDC
3-4: 2,4 kOhm
GND GND GND GND
BOUT-BW
1
2
0
R
-
B
ia
s
+
B
ia
s
SIM
CARD
R
S
4
8
5
1
2
0
R
C
A
N
1
C
A
N
2
4321
AT-Link
connection port
Boot Jumper

2) File/Firmware upgrade and Cloning/FW upgrade (default configuration)


3) Select the requested firmware

4) The upgrade will be processing

5) Follow instructions on the screen

6) Upgrading will continue

7) Follow instructions


Technical Data
Power Supply
Nominal power supply 24 VDC
Power supply range 8 36 VDC
Current consumption 0,34A @ 8V
0.12A @ 24 V
0.09A @ 36 V
Battery voltage measurement tolerance 2% at 24V
RTC battery life cycle 10 years
Operating conditions
Operating temperature -30 to + 80 C
Storage temperature -40 to + 85 C
Humidity 95% without condensation
Flash memory data retention time 10 years
Protection (Dust and Water) IP 67

Standard conformity
Low Voltage Directive EN 61010-1:95+A1:97
EN 61000-6-2, October 2001
EN 61000-6-4, October 2001
IEC 60533, Ed. 2; 1999-11
Shock test IEC 68-2-27
Vibration resistance IEC 60068-2-6, 5-28Hz/ 1,6mm, 28-150Hz/ 5g
EMC compatibility EN61000-6-1/2/3/4, SS4631503(PL4), IEC 255-3

Dimensions
Dimensions 240x200x63mm

Binary inputs
Number of inputs 8
Input impedance 4,7 k
Input Range 0-36VDC
Switch voltage level for close contact indication 0-2 V
Voltage level for open contact indication 4-36 V
Minimal input signal duration 110 ms

Binary outputs
Number of outputs 4
Contact Hi-side
Max. continues current (single channel) 0,5A
Maximum switching voltage 36 VDC


Speed pick-up input
Number of inputs 1
Type of sensor magnetic pick-up (connection by shielded cable is
recommended)
Input impedance 10 k
Minimum input voltage 2 Vpk-pk (from 4Hz to 4kHz)
Maximum input voltage 50 Veff
Minimum measured frequency 4 Hz
Maximum measured frequency 10 kHz (min. input voltage 6Vpk-pk)
Frequency measurement tolerance 1,5 %
Impulse input
Number of inputs 2
Type of sensor NPN
Frequency rate 0 to 60Hz
Minimum pulse duration 1 ms
Input impedance 4 k
ON input voltage < 0.8 V
OFF input voltage > 4.2V
R
ON
max 1 k
Maximum input voltage 40V
Analog inputs
Not electrically separated
Number of inputs 11
Resolution 10 bits
Jumper selectable range AIN1 AIN7: 20mA, 5 VDC, 20k
AIN8 AIN11: 20mA, 1 VDC, 20k
Maximal resistance range 25 k
Maximal current range 22 mA
Input impedance 0 for mA measuring
Input impedance > 100 k for V measuring
Resistance measurement tolerance 2 % 2 out of measured value
Voltage measurement tolerance 2 % 1mV out of measured value
Current measurement tolerance 2 % 0,5mA out of measured value

Communications
CAN bus interface
Galvanically separated
Maximum CAN bus length
- CAN bus mode = 32C 200 m
- CAN bus mode = 8C 900 m
Speed
- 32C 250 kBd
- 8C 64 kBd
Nominal impedance 120
Cable type twisted pair (shielded)


RS 485
Maximal distance 1000m
Speed up to 57,6 kBd
-
ID-Mobile GPRS
Type Simcom SIM900
Frequency Bands GSM 850; EGSM 900, DCS 1800; PCS 1900;
GSM/GPRS
GSM class Small MS
Transmitting power Class 4 (2W) at GSM 850 and EGSM 900
Class 1 (1W) at DCS 1800 and PCS 1900
GPRS multi-slot class 10
CSD up to 14.4 kbps
TCP/IP communication over GPRS
Voltage supply 8-36 VDC
ID-Mobile GSM
Type Telit GC864
Frequency Bands GSM 850; EGSM 900, DCS 1800; PCS 1900;
GSM/GPRS modem
Compliant to GSM Phase 2/2+
GSM class Small MS
Transmitting power Class 4 (2W) at GSM 850 and EGSM 900
Class 1 (1W) at DCS 1800 and PCS 1900
Sensitivity -107 dBm @ 850 / 900 Mhz
-106 dBm @ 850 / 900 Mhz

ID-Mobile GPS
Type U-BLOX, LEA-5H
Receiver type 50 Channels`GPS L1 frequency; C/A
Code;GALILEO Open Service capable, GLONASS
Sensitivity Tracking & Navigation 162 dBm
Reacquisition - 160 dBm
Cold Start - 148 dBm

Horizontal position accuracy 2,5 m
Accuracy for Timepulse signal RMS 30 ns
99% <60ns
Velocity accuracy 0,1 m/s

ID Logger - Reference Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ID Logger - Reference Manual

Uploaded by

Copyright:

Available Formats

Copyright 2013 ComAp s.r.o.

You might also like