ID Logger - Reference Manual

InteliDrive

ID- Mob ile Lo gg er Dat a Logg er

HW version 1.3; SW version 2.0, January 2014

REFERENCE GUIDE

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: [email protected], www.comap.cz

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 ............................................................................................................................ 23 LogicalInputs binary(BIN) 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 ID-Mobile-Logger, SW version 2.0, ©ComAp January – 2014

Page 2 of 68

Direct connection to the PC .............................................................................................................. 58 Modbus communication .................................................................................................................... 58 Event Log – h istory ........................................................................................................................... 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

ID-Mobile-Logger, SW version 2.0, ©ComAp January – 2014

Page 3 of 68

Abbreviations aid AIN Alarm Alarm list ECU Alarm list AOUT Archive BI BIN BO BOUT CAN Cd DC DM DriveConfig DriveMonitor ECU ECU alarm Fls FMI GSM modem History

InteliVision 5 CAN InteliVision 8 ID IMON InteliMonitor J1587 J1587/J1708 J1939 mhx OFF PID PPID RPM PSID RS232 Sd SID Wrn

Archive file extension for InteliDrive controller Controller or extension module Analog input General term for any active engine protection Warning, Shutdown, … etc. Controller or PC InteliMonitor screen with list of active and unaccepted alarms detected from ID controller. Controller or PC InteliMonitor screen with list of active and unaccepted alarms detected from engine ECU. Controller Analog OUTput or outputs group. Usually aid history file that contains all controller data: configuration, setpoints setting and records. Controller binary input. Controller binary inputs group. Controller binary output. Controller binary outputs group. Control Area Network – serial data link. Cool down protection, cooling period is included before engine stops. DriveConfig, PC software for InteliDrive configuration. DriveMonitor, PC software for InteliDrive monitoring (discontinued in Q3 2013). PC software for InteliDrive configuration. PC software for InteliDrive monitoring (discontinued in Q3 2013). Engine Electronic (injection) Control Unit. Alarm detected in engine electronic control unit that is received via J1939. Sensor fail alarm – prefix. Failure Mode Identifier. Modem for Global System of Mobile communication 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. ComAp color display 5 or 8 inch. InteliDrive controller. InteliMonitor, PC software for InteliDrive monitoring. PC software for InteliDrive monitoring. The J1587 bus is mainly used for redundant signals; system diagnosis and software download on after market tools. See J1587 The J1939 bus in mainly used for engine controls and engine monitoring. Extension for controller firmware (Motorola HeX file). Controller mode when power supply is switched on, but all binary outputs and start commands are disabled = engine start is blocked. J1939 Parameter Identification Assignments. J1939 Proprietary Parameter Identification Assignments. Engine Revolution Per Minute – engine speed. J1939 Proprietary Parameter Identification Assignments. Standard serial data line for PC or Modem connection (controller programming or monitoring). Shut down protection. J1939 Subsystem Identification Assignments. Warning protection.


Page 4 of 68

Document information ID-MOBILE LOGGER – REFERENCEGUIDE W RITTEN BY: ZDENEK ROJKA ©2014 COMAP LTD. KUNDRATKA 17, PRAHA 8, CZECH REPUBLIC PHONE: +420246012111, FAX: +420266316647 W EB: HTTP://WWW.COMAP.CZ, E-MAIL: [email protected]; [email protected] 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

1.9

New software features, updated functionality

30.9.2013

2.0

New software features, updated functionality

10.1.2014

4.4.2013

Clarifi cation 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. W ARNING! This type of paragraph indicates things, procedures, adjustments etc. which need high level of attention, otherwise can cause personal injury or death.

Conformity

decla rat ion 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.


Page 5 of 68

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

Software Import package ID-Mobile-Logger-2.0.idc

Files

Note

ID-Mobile-Logger-2.0.mhx

ID-Mobile-Logger firmware

ID-Mobile-Logger-2.0.aim

Default configuration archives

PC T ools 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


Page 6 of 68

General guidelines What is ID- Mobile Lo gger? 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 +80°C 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.


Page 7 of 68

Hardware Plugs for Antenna connectors LED indication

Right side male connector: BLACK

Left side male connector: BROWN Membrane – overpressure relief

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.


Page 8 of 68

Dimensions and asse 40 (1,6")

mb ly 4x bracket  6mm (ready for screw M6)

201 (7,9") 117 (4,6")

GPS

") ,1 0 (1 8 5

Maximal thickness 63mm (2.5“)

GSM, GPRS

)" 4 , (9 0 4 2

2

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


Page 9 of 68

Harnesses

ID-Mobile Logger

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

NOTE: Harnesses for ID-Mobile Logger are not compatible with ID-Mobile control unit. Connectors 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

Mating/Unmating of the connector from the header

Insert the connector until it stops in the header

Rotate the lever


Page 10 of 68

Lock it on the cover cap until it clicks

Press on the latch

Rotate the lever

Rotate the lever

ID -Mobile Service Modu

le

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

ID-Mobile

ServiceModule

Logger

Page 11 of 68

Terminals

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

25 37 A

26 38 B

Left side male connector - brown 9 10 21 27 28 29 30 31 33 34 39 40 41 42 43 44 45 46 C D E F G H J K

12

1 2 3 4

49 50 61 62 36 73 74 48 85 86 L M A B Bottom side of box

51 63 75 87 C

Right side male connector 52 53 54 55 56 64 65 66 67 68 76 79 80 88 89 90 91 92 D E F G H

black 57 58 69 70 81 82 93 J K

Left side connector - Pins function 37 38 39 40 41 42 43 44 45 46

4 AI8+ AI8AI9+ AI9AI10+ AI10AI11+ AI11+5V GND3

47 48

GND4

25 26 27 28 29 30 31 32 33 34 35 36

3 AIN AIN AIN AIN AIN AIN AIN

2 1 2 3 4 5 6 7

GND1

GND2

A B C D E F G H J K L M

13 14 15 16 17 18 19 20 21 22 23 24

+5V

1 1 2 3 4 5 6 7 8 9 10 11 12

IM 2 IN IM 2 SUP GND5

Right side connector - Pins function 85

4 RS485A

86 87 88 89 90 91 92 93 94

485COM RS485B CAN1H CAN1COM CAN1L CAN2H CAN2COM CAN2L

95 96

BAT PLUS BAT MINUS

73 74 75 76 77 78 79 80 81 82 83 84

3 BO1 BO2 BO3 BO4

RPM 1RPM 1+ IM 1 IN IM 1 SUP +VBO GND7

A

61

B C D E F G H J K L M

62 63 64 65 66 67 68 69 70 71 72


2 GND GND GND GND GND GND GND GND GND I-BUTT I-BUTT GND8

49 50 51 52 53 54 55 56 57 58 59 60

1 BIN 1 BIN 2 BIN 3 BIN 4 BIN 5 BIN 6 BIN 7 BIN 8 GND BIN +5V GND9

Page 12 of 68

83 95 L

60 72 84 96 M

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

HWVERSION1_2 (SINCE 4-2012)

BO1 BO2 BO3 BO4 +VBO

Not available

73 74 75 76 83

I-BUTT GND I-BUTT

34 33

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

70 69

Physical input/output struc

ture ID-Mobile-Logger

Sensors

3-wires

21: +5V 25: AIN1 33: GND1

3-wires

45: +5V 26: AIN2 36: GND2

I_BUTTON PROBE 70: I-Button 69: GND I-BUTT

27: AIN3 46: GND3

2-wires

Power Run Alarm Status

83: +VBO

BATT+

73: BO1 74: BO2 75: BO3 BATT-

2-wires

28: AIN4 48: GND4

2-wires

29: AIN5 12: GND5

4-wires

58: +5V 30: AIN6 31: AIN7 84: GND7

2-wires

37: AIN8+ 38: AIN8-

2-wires

39: AIN9+ 40: AIN9-

2-wires

41: AIN10+ 42: AIN10-

2-wires

43: AIN11+ 44: AIN11-

Power Supply 8-36 VDC

76: BO4

S T C A T N O C Y R A IN B

49: BIN1 61: COM 50-62: 51-63: 52-64: 53-65: 54-66: 55-67: 56-68:

BIN2 BIN3 BIN4 BIN5 BIN6 BIN7 BIN8

85: 485A 86: 485COM 87: 485B 88: CAN1H 89: CAN1COM 90: CAN1L 91: CAN2H 92: CAN2COM 93: CAN2L 82: UM1 81: IM1 72: GND8

10: UM2 9: IM2 60: GND9

Communication lines (Twisted pairs) RS485, CAN1, CAN2

SUP IM1 GND

SUP IM2 GND

IMP1 3-wires IMP2 3-wires RPM

95: BATT+ 96: BATT-


80: RPM1 79: RPM1COM

RPM1 GND

2-wires

Page 13 of 68

Analog Inputs AIN1 – AIN7 AIN1

25

AIN2

26

AIN3

27

AIN4

28

AIN5

29

AIN6

30

AIN7

31

COM

33

Analog inputs configurable for usage with current, resistance or voltage sensor. s t u p in g o l a n A

AIN8 – AIN11 AIN8+

37

AIN8-

38

AIN9+

39

AIN9-

40

AIN10+

41

AIN10-

42

AIN11+

43

AIN11-

44

s t u p in

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

g o l a n A

Binary Inputs BIN1

49

BIN-COM

61

BIN2

50

BIN-COM

62

BIN3

51

BIN-COM

63

BIN4

52

BIN-COM

64

BIN5

53

BIN-COM

65

BIN6

54

BIN-COM

66

BIN7

55

BIN-COM

67

BIN8

56

BIN-COM

68

Activation to minus of power supply.

Switching level: active ≤ 2 VDC. Sampling rate 100ms. s t u p in y r a n i B

Binary Outputs 83 y r a n i B

s t u p t u o

+VBO

73

BO1

74

BO2

75

BO3

76

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.


Page 14 of 68

RPM Input RPM1A

79

RPM1B

80

t u p n i

Use magnetic pickup.

M P R

Impulse inputs +IM1 SUP (+24VDC) 82 IM 1 IN BAT+IM 2 SUP (+24VDC)

Hardware

81 84 10

IM 2 IN

9

BAT-

12

s t u p in e ls u p Im

Use active NPN open collector sensors.

con figuration

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.


Page 15 of 68

Jumpers location RS232 GPS

s ia B +

GSM 5 8 4 S R

R 0 2 1 s ia B -

1 N A C

R 0 2 1

2 N A C

R 0 2 1

SIM CARD BOOT uP

POWER

1-2: 20 mA No jumper: 5 VDC 3-4: 2,4 kOhm 4 -3 - 2 -1

AIN1

4 -3 -2 - 1

4 - 3 -2 -1

AIN2

AIN3

1-2: No jumper: 3-4:

RUN ALARM 4 - 3 - 2 -1

AIN4

4 -3 - 2 - 1

4 - 3 -2 - 1 4 - 3 - 2 -1

AIN5

AIN6

+- 20 mA +- 1 VDC 2,4 kOhm

4 - 3 - 2 -1

4 -3 -2 - 1

4 -3 - 2 - 1

AIN8

AIN9

AIN10

GN D

STATUS

AIN7

GN D

1 13 25 37

4 - 3 -2 -1

AIN11

12 GN D 24 36 48

49 61 73 85

GN D

4

3

2

60 72 84 96

1

BOUT-BW

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

20mA  Thermocouple K Thermocouple J

0

– 2,4 k

Thermocouple L

JUMPERS GND

JUMPER OFF (NO JUMPER)

GND Related to AIN8 –AIN11

Non Isolated Isolated Thermocouples Thermocouples Ground on Thermocouple side Ground on controller side (engine)


JUMPER ON (JUMPER CLOSED)

Page 16 of 68

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 modu

les

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


Page 17 of 68

Overview of supported modes and functions: MODULE TYPE

OPERATION MODE

DESCRIPTION

SUPPORTS

TELIT CSD

GSM mode CSD (Circuit Switch Alarm SMS Data) DriveMonitor / InteliMonitor version 1.8.1 and lower via modem connection

TELIT GPRS

Customized interface version 1.8.1 and lower

For special application only

custom

TELIT 3G

Customized interface version 1.9 and higher


custom

TELIT GPRS

Customized interface version 1.9 and higher


custom

SIMCOM CSD

Alarm SMS Standard GSM mode CSD (Circuit Drive Monitor / InteliMonitor Switch Data) via modem connection

SIMCOM GPRS

GPRS network – connection via AirGate

ID-Mobile GSM

ID-Mobile 3G

ID-Mobile GPRS enables

Alarm SMS AirGate Drive Monitor / InteliMonitor via AirGate WebSupervisor

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.


Page 18 of 68

External disp lays

InteliVision 8 8” color TFT display - 800x600 pixels Operating temperature: -20 … +75°C 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 … +75°C 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.


Page 19 of 68

Comm unication li

nes

COMMUNICATIONS

ID-MOBILE-LOGGER

Direct connection USB RS485 RS232 CAN1 CAN2 GSM

1)

GPRS

1)

UMTS

1)

GPS 1) 1) Plug-in module required

RS485 5 8 4 S R

85

RS485-A

86

COM

87

RS485-B

DriveConfig DriveMonitor WinScope

USB RS485 / USB converter

USB

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 ID-Mobile / ID-Mobile-Logger CAN1 interface is dedicated to:  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 ID-Mobile / ID-Mobile-Logger CAN2 interface is dedicated to:  external displays (see Externa l d isplays )  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.


Page 20 of 68

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.


Page 21 of 68

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

M AXIMUM AVAILABLE DETAILS (USED/M AX.AVAIL.)

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

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)


Interface

Communication

Bridge

Page 22 of 68

Bin ary Inputs

(BI N)

Available configuration for Binary inputs: PROPERTY

VALUE

ECU VALUE According Available only if ECU selection selected under ECU-1

NAME PROTECTION

PROT.ACTIVE

PROT. BLOCK TYPE

DELAY

FUNCTION

DETAILS to 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

Text No Protection

Maximum 14 charts 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

Closed

Protection active if the contact is closed

Open

Protection active if the contact is open

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

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

BinInp delay 2


BinInp delay 3


Logical function

Find more details in: Logical 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.

Log ical binary inputs (LBI) Any InteliDrive controller binary input can be configured as “function” and/or “protection”.


Page 23 of 68

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 MODBUS or ECU LINK. See setpoint: Comms Setting / RS485 Mode description.


Page 24 of 68

Configure this input (or leave as it is in default) for case the RS485 mode setpoint is changed to MODBUS or ECU LINK 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


Page 25 of 68

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 1…3 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.

Bin ary Outpu ts (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. PROPERTY

VALUE

DETAILS

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.

Text

Title of the BOUT - maximum 14 charts

NAME

ECU VALUE According to selection Available only if ECU selected under ECU-1

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.


Page 26 of 68

Logical binary o

utputs (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.


Page 27 of 68

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 comes starts switching (blinking 0,5/0,5sec from opened or closed state) when any new alarm 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 1…5 InteliVision function buttons can be assigned to these five LBOs.


Page 28 of 68

Operator ID Operator identification fail output – indication is in history list only (not in Alarm list).

RemoteControl1…8 Remote control outputs can be controlled DriveMonitor/InteliMonitor – Remote switch panel.

locally

or

remotely

(via

Modem)

from

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 ID-Mobile-Logger, SW version 2.0, ©ComAp January – 2014

Page 29 of 68

Battery Volt Indication when battery voltage of the controller is out of protection limits (setpoints Basic Settings / BattV)

WrnServiceTime Output is closed when Service Time (Statistics / Service Time) counts down (= 0). Note: History record and Alarm list indication is activated as well

An alog Inpu ts (AIN ) PROPERTY

VALUE

DETAILS

NAME

Text

Maximum 14 charts

DIM

-, RPM, ppl, bps, Bar, s, V, h, min, m, °C, kPa, l, km/h, Dimension of the value %, l/h None

Non sensor is selected

0–20 mA

Current input within listed intervals

0–2400 ohm

Resistance input within listed intervals

0–5V

Voltage input within listed intervals

User

Sensor characteristic created by the user NOTE:

AIN1 – AIN7

For more details see DriveConfig – User Guide SENSOR

+-20mA

Current input within listed intervals

0–2400 ohm

Resistance input within listed intervals

+-1V


+-100mV

Millivoltage input within listed intervals

-1.0V–2,5V


AIN8 – AIN11

Thermocopl K/°C (K/°F) Predefined characteristic thermocouples

Thermocopl L/°C (L/°F)

for

usual

type

of

Thermocopl J/°C (J/°F) RESOLUTION

1; 0,1; 0,01; 0,001; 0,0001

SENSOR RANGE

0…9999

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

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

ACTIVE

WHEN

Definition of decimal point for AIN

Definition of sensor range for AIN


Page 30 of 68

BLOCK TYPE

Over Limit + Fls

Protection is active if a value is over selected limit and/or sensor fail is indicated

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%

-9999…9999

Value related to 0% of Bargraph

BARGRAPH 100%

-9999…9999

Value related to 100% of Bargraph

FUNCTION

Logical function

See more details in Logical analog inputs

Log ical ana log inp uts (LAI)

Engine Speed Logical RPM value for Engine RPM indication, overspeed protection, engine running and overload detection. RPM1 State Machine

ECU-RPM

Engine Speed LAI

Engine RPM (value)

Default configuration

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: The dimension and number of decimal points is according to the source (AIN, ECU-AIN)

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

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.


Page 31 of 68

Analog input x [L/h]

LAI: Fuel ConsAct Fuel Rate [ L/h ]

ECU

LBI: Clear TotalCons

RPM/FlowMeters

Fuel sensor

TripConsumpt [ L ]

J1939 LBI: Clear TripCons

Fuel sensor

Statistics

Impulse Input 1

Impulse Input 2

RPM/FlowMeters Imp/Unit IM1

FlowMeter IM1 [ L/h1 ]

TotalConsumpt [ L ] Time Zone x [ s ] Consump Zone x [ L ]

Pulses IM1 Imp/Unit IM2

FlowMeter IM1 [ L/h2 ] 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 virtu

al I /O periph ery

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 don’t appear on any physical output, instead of that are distributed via the CAN bus to other controllers. Each module has 4 outputs.


Page 32 of 68

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) s u b N A C r e ll ro t n o c r e t n I

TARGET (SHBIN)

TARGET (SHBIN)

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 controller’s FW or PLC:

SYSTEM START

L A C I S Y H P

Y R A N I B

S T U P N I

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

CONTROLLER STATE MACHINE

S T U P T U O L A IC G O L

T U O B H S

Intercontroller CAN bus

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 controller’s FW or PLC like any other physical binary input:


Page 33 of 68

L A IC S Y H P

Y R A N I B

S T U P N I

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

IN B H S



Together looks like this:

1 . C O N T RO L L E R

3 . CONTROLLER

2 . C O N T RO L L E R SHBIN1

SHBOUT1

SHBIN1

BOUT1

BIN1

BIN1

BOUT2

BIN2

BIN2

BIN3

BIN3

CAN2

BOUT3 BOUT4

BIN4

Logical Inputs

Sys start/stop

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

Logical Outputs

r e ll ro t n o C

BIN4

Logical Outputs

Logical Inputs

s n ito c n u F

r e ll o tr n o C

s n io t c n u F

2 N A C

Logical Outputs

Logical Inputs

r e ll o tr n o C

s n io t c n u F

Setpoints Setpoints

Setpoints

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) s u b N A C r e ll rto n o c r e t In

TARGET (SHAIN)

TARGET (SHAIN)

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 controller’s FW or PLC:


Page 34 of 68

L A C I S Y H P

G O L A N A

S T U P N I

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

S E U L A V D E R U S A E M


T U O A H S


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 controller’s FW or PLC like any other physical analog input: L A C I S Y H P

G O L A N A

S T U P IN

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

IN A H S


S E U L A V D E R U S A E M


Together looks like this: 1 .CONTROLLER

2 . CONTROLLER

SHAOUT1 AOUT1 AOUT2 AOUT3 AOUT4

3 . CONTROLLER

SHAIN 1

CAN2

SHAIN 1

AIN 1 AIN 2 AIN 3 AIN 4

AIN1 AIN2 AIN3 AIN4

Temperature X Logical Inputs

Logical Outputs Temp X

r le l o tr n o C

s n o it c n u F

Setpoints

Logical Inputs


r e ll o tr n o C

s n o ti c n u F

Setpoints


2 N A C

Logical Inputs


r e ll ro t n o C

s n o ti c n u F

Setpoints

Page 35 of 68

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.

RPM/FlowMeters Impulse Fuel sensor

Input 1

Imp/Unit IM1


Fuel sensor

Impulse Input 2

Imp/Unit IM2


Basic Va lues

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.


Page 36 of 68

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.

Bin ary CU

ID BIN Binary inputs according to configuration


Page 37 of 68

ID BOUT Binary outputs according to configuration

Log Bout

LogBout 1, 2 Logical binary functions.


Page 38 of 68

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


Page 39 of 68

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

17

Not possible to read GSM signal strength

18

CDMA modem not detected

19

No CDMA network

ID-Mobile-GPRS – not possible to connect to GPRS network ID-Mobile-GPRS – not possible to retrieve IP address ID-Mobile-GPRS – not accepted DNS IP address

6 7 8 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 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

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.


Page 40 of 68

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… Analog input x [L/h]

LAI: Fuel ConsAct Fuel Rate [ L/h ]

ECU

TripConsumpt [ L ]

J1939 LBI: Clear TripCons

RPM/FlowMeters Fuel sensor

Statistics

Impulse Input 1

RPM/FlowMeters Imp/Unit IM1

TotalConsumpt [ L ]

LBI: Clear TotalCons

FlowMeter IM1 [ L/h1 ]

Time Zone x [ s ] Consump Zone x [ L ]

Pulses IM1 Fuel sensor

Impulse Input 2

Imp/Unit IM2


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.


Page 41 of 68

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 1…6 [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 1…3 can be activated with LBI Zone x ON too.

Consump Zone 1…6 [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 1…3 can be activated with LBI Zone x ON too. E.g. for setting: Z1 Z2 RPM Start 0 RPM 0 RPM RPM End 1000 RPM 2000 RPM Fuel Start 0 L/h 100 L/h Fuel End 100 L/h 200 L/h LBI: Zone x ON OFF OFF Actual value RPM = 800 and fuel consumption = 50 L/h

Z3 1000 RPM 2000 RPM 0 L/h 100 L/h ON activates zones Z1 and Z3.

Position

Actual Lat [m] Actual GPS Latitude value (e.g. 50°6'51.463"N).

Actual Long [m] Actual GPS Longitude value (e.g. 14°28'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.


Page 42 of 68

MSL Altitude [m] Altitude above sea level in meters.

Ground Speed [km/h] Actual ground speed in km/h.


Page 43 of 68

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.


Page 44 of 68

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 Set tings

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

N : name is not changed when new archive is loaded. Check Engine name after firmware Engine 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: Step: Terminals:

[-] 1 - 500 1 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: Range: Step: Terminals:

[ RPM ] 30 - 4000 1 RPM


Page 45 of 68

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 Ke y is not applied during power switch on.

Starting RPM Dimension: Range: Step:

[ RPM ] 30 – Nominal RPM 1

RPM limit for running engine detection.

Running POil Dimension: Range: Step:

[ Bar ] 0,00 – 10,00 0,01

Oil pressure limit to be engine detected as running when no RPM pickup (or ECU RPM) is not used.

RunOnlyBlkDel Dimension: Range: Step:

[s] 0 – 60 1

Delay for Engine running Alarms activation. BINARY INPUT Physical

closed BinInp delay

Engine running state

BINARY INPUT Internal value

RunOnlyBlkDel PROTECTION

inactive

active

BinInp Delay 1 .. 3 Dimension: Range: Step:

[s] 0 – 60 1

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

Closed

BinInp delay

no change

Internal value


Page 46 of 68

BINARY INPUT physical

closed BinInp delay

BINARY INPUT Internal value DriveConfig: I/O, Property, Protection active = BINARY INPUT physical

Opened

opened BinInp delay

BINARY INPUT Internal value

ForceBlock Del Dimension: Range: Step:

[s] 0 – 60 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. closed BINARY INPUT Prot, block type = Force block BINARY INPUT FORCE BLOCK Protection

active

closed ForceBlock del

inactive

active

Batt
[V] 8,0 – 40,0 (Batt >V ) 0,1

Under voltage of controller power supply.

Batt >V Dimension: Range: Step:

[V] 8,0 (Batt
Overvoltage of controller power supply

Batt Volt Del Dimension: Range: Step:

[s] 0 – 600 1

Delay for battery voltage alarms Batt
Service Time Dimension: Range:

[h] 0 – 65535


Page 47 of 68

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 equip ment 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.

Comm s Se ttings

ControllerAddr Dimension: Range: Step:

[-] 1 - 32 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: Range:

[ bps ] 9600, 19200, 38400, 57600

Modbus interface baud rate setting

ComApPort Dimension: Range: Step:

[-] 1 – 65535, default = 23 1

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


Page 48 of 68

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: Range: Step:

[ i/L1 ] 0,0 – 6500,0 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: Range: Step:

[ i/L2 ] 0,0 – 6500,0 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.


Page 49 of 68

Fuel sensor

Impulse Input 1

Imp/Unit IM1


Fuel sensor

Impulse Input 2

Imp/Unit IM2


EvalPeriod IM1 Dimension: Range: Step:

[s] 0,1 – 10,0 0,1

Evaluation interval for measurement IMP1, default value is 0,1 s.

EvalPeriod IM2 Dimension: Range: Step:

[s] 0,1 – 10,0 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: Range:

[] HOUR, MIN, SEC

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:

[]

Range:

HOUR, MIN, SEC

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


Page 50 of 68

Analog Inputs

AIN1 Offset … AIN11 Offse t Dimension: Range: Step:

[-] -32767 - 32767 1

Adjustable offset related to analog input AIN1…AIN11.

Ac t. Calls/S MS

Warning Call Dimension: Range:


Enables or disables active calls/SMS to selected phone numbers when a Warning alarm occurs.

Shut Down Call Dimension: Range:


Enables or disables active calls/SMS to selected phone numbers when a Shut down alarm occurs.

Cool Down Call Dimension: Range:


Enables or disables active calls/SMS to selected phone numbers when a Cool down alarm occurs.

AcallCH1…3-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)

AcallCH1…3-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:

[-]


Page 51 of 68

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 doesn ’t 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.

OTE: N 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. ID-Mobile-Logger, SW version 2.0, ©ComAp January – 2014

Page 52 of 68

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: Range: Step:

[s] 0 – 14400 1

Standard history record period.

Time Stamp Del Dimension: Range: Step:

[s] 0 (Time Stamp Per) – 14400 1

Time delay after engine stop when the Time Stamp Per records are still provided.

Fast Stamp Per Dimension: Range: Step:

[s] 0 – 600 1

Faster History records are provided after any Alarm (see in Setpoints / Limits ) is activated.

Fast Stamp Del Dimension: Range: Step:

[0 min ] – 100 1

Time duration of the Fast stamp records. Alarm Engine Not running

Running Engine

No periodic records

Periodic records

Time Stamp Per

Not running Fast Stamp Del

Fast Stamp Per

Time Stamp Del

No periodic records

Time Stamp Per

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.


Page 53 of 68

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 Z1…6 Dimension: Range:

[-] 0 – RPM End Z1…6

RPM trigger – start RPM value for initiation of statistic Zone 1…6 counting. RPM source is LAI Engine Speed.

RPM End Z1…6 Dimension: Range:

[ -] RPM Start Z1…6 – Nominal RPM

RPM trigger – stop RPM value for initiation of statistic Zone 1…6 counting. RPM source is LAI Engine Speed.

Fuel Start Z1…6 Dimension: Range:

[ L/h] 0,0 – Fuel End Z1…6

Consumption trigger – start value for initiation of statistic Zone 1…6 counting. Consumption source is LAI Fuel ConsAct.

Fuel End Z1…6 Dimension: Range:

[ L/h] Fuel Start Z1…6 – 1000,0

Consumption trigger – stop value for initiation of statistic Zone 1…6 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:

RPM Start RPM End Fuel Start Fuel End

Z1 0 RPM 1000 RPM 0 L/h 100 L/h

Z2 0 RPM 2000 RPM 100 L/h 200 L/h

Z3 1000 RPM 2000 RPM 0 L/h 100 L/h

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


Page 54 of 68

Position

Home Lat Dimension:

[0° 0’ 0.000”N ]

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.000”E ]

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 Range: Step:

ion: [m] 10 – 10 000 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: Range: Step:

[s] 30 – 60000 1

Once the controller is out of Fence Radius and Fence Delay time elapsed the engine is shut down. NOTE: This setpoint isn’t 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: Range:

[ Bar ] 0,00…15,00


Page 55 of 68

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: Range: Step:

[s] 0…600 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: Range: Step:

[ Bar ] 0,00…15,00 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: Range: Step:

[ °C ] -25…130 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: Range: Step:

[s] 0…600 1

Delay for Oil Temperature protection limits Max Oil Temp A and Max Oil Temp B.

Max Cool Temp Dimension: Range: Step:

[ °C ] -25…130 1

High Coolant Temperature limit. Alarm is indicated when actual temperature value is over for time Cool Temp Del.

Cool Temp Del Dimension: Range: Step:

[s] 0…600 1

Delay for Coolant Temperature protection limits Max Cool Temp .


Page 56 of 68

BoostPressure Dimension: Range: Step:

[ kPa ] 0…500 1

Low Boost Pressure limit. Alarm is indicated when actual pressure value is below for BoostPress Del.

BoostPress Del Dimension: Range:

[s] 0…600

Step:

1

Delay for Boost Pressure protection limits BoostPressure.

Boost Temp Dimension: Range: Step:

[ °C ] -25…130 1

High Boost Temperature limit. Alarm is indicated when actual temperature value is over for Boost Temp Del.

Boost Temp Del Dimension: Range: Step:

[s] 0…600 1

Delay for Boost Temperature protection limits Boost Temp .

Exhaust Temp A / Exhaust Temp B Dimension: Range: Step:

[ °C ] -40…950 1

High Exhaust Temperature A/B limit. Alarm is indicated when actual temperature value is over for ExhaustTempDel.

ExhaustTempDel Dimension: Range: Step:

[s] 0…600 1

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


Page 57 of 68

Remote control and data logging Direct connectio

n 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 com       

municati on

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.

Eve nt 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.


Page 58 of 68

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 Max. number of [bytes] 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 aren’t 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 ID-Mobile-Logger, SW version 2.0, ©ComAp January – 2014

Page 59 of 68

 

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 Unsigned32 Read only in the long history 24389 Number of records in Unsigned32 Read only the long history

24388 24387 24386

24385

(# 87)

The youngest record in Domain the long history Older record in the long Domain history The actual record in the Domain long history

Read only

If the history is full, the value is the maximum number of records in a long history (see comm. object 24390) (# 87) (# 87)

Read only

(# 87)

Read only

Setting the read index Domain6 in a long history to record coresponding to the specified timestamp

Write only

Reads a record referenced by the current red index value in a long history (# 87) 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 doesn’t exist. Long history is cyclical records sequence, in this sense, is the closest older record after the oldest record is the youngest record; It isn’t possible to set reading index, when long history is empty (controler returns an error response). (# 87) (# 88)


Page 60 of 68

24384

24383 24382 24381

Acknowledge full indication memory for the long history Write index in the long history Read index in the long history Younger record in the long history

Binary8

Write only

(# 87) (# 89)

Unsigned32 Read only

(# 87)

Unsigned32 Read only

(# 87)

Domain

(# 87)

Read only

# 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).


Page 61 of 68

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

r Ope

2 ator

rat Ope

or 1

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.


Page 62 of 68

Booting procedure After wrong upgrade process the controller doesn’t 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.


Page 63 of 68

Booting procedure steps: 1) Connect the AT link converter to ID-Mobile-Logger: AT-Link connection port

RS232 GPS

GSM 5 8 4 S R

s ia B + R 0 2 1 s ia B -

1 N A C

R 0 2 1

2 N A C

R 0 2 1

SIM CARD BOOT uP

POWER

Boot Jumper

1-2: 20 mA No jumper: 5 VDC 3-4: 2,4 kOhm 4-3-2-1

AIN1

RUN ALARM

4 - 3 -2 - 1

4-3-2-1

4 - 3- 2 - 1

AIN2

AIN3

AIN4

1-2: No jumper: 3-4:

4 -3 - 2 - 14 - 3 - 2 - 1

AIN5

AIN6

STATUS

AIN7

+- 20 mA +- 1 VDC 2,4 kOhm

4-3-2-1

4-3 -2-1

AIN8

AIN9

G ND

4-3-2-1

GND

4- 3-2-1

AIN10 1 13 25 37

4-3-2 -1

AIN11

12 G N D 24 36 48

49 61 73 85

G ND

4

3

2

60 72 84 96

1

BOUT-BW

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


Page 64 of 68

3) Select the requested firmware

4) The upgrade will be processing

5) Follow instructions on the screen

6) Upgrading will continue

7) Follow instructions


Page 65 of 68

Technical Data Power Supply Nominal power supply Power supply range Current consumption

Battery voltage measurement tolerance RTC battery life cycle

24 VDC 8 – 36 VDC 0,34A @ 8V 0.12A @ 24 V 0.09A @ 36 V 2% at 24V 10 years

Opera ting con ditions Operating temperature Storage temperature Humidity Flash memory data retention time Protection (Dust and Water) Standard conformity Low Voltage Directive

Shock test Vibration resistance EMC compatibility

-30 to + 80 °C -40 to + 85 °C 95% without condensation 10 years IP 67

EN 61010-1:95+A1:97 EN 61000-6-2, October 2001 EN 61000-6-4, October 2001 IEC 60533, Ed. 2; 1999-11 IEC 68-2-27 IEC 60068-2-6, 5-28Hz/  1,6mm, 28-150Hz/ 5g EN61000-6-1/2/3/4, SS4631503(PL4), IEC 255-3

Dimensions Dimensions

240x200x63mm

Binary inputs Number of inputs Input impedance Input Range Switch voltage level for close contact indication Voltage level for open contact indication Minimal input signal duration

8 4,7 kΩ 0-36VDC 0-2 V 4-36 V 110 ms

Binary outputs Number of outputs Contact Max. continues current (single channel) Maximum switching voltage

4 Hi-side 0,5A 36 VDC


Page 66 of 68

Spee d p ick- up input Number of inputs Type of sensor Input impedance Minimum input voltage Maximum input voltage Minimum measured frequency Maximum measured frequency Frequency measurement tolerance

1 magnetic pick-up (connection by shielded cable is recommended) 10 kΩ 2 Vpk-pk (from 4Hz to 4kHz) 50 Veff 4 Hz 10 kHz (min. input voltage 6Vpk-pk) 1,5 %

Imp ulse input Number of inputs Type of sensor Frequency rate Minimum pulse duration Input impedance ON input voltage OFF input voltage RON max Maximum input voltage

2 NPN 0 to 60Hz 1 ms 4 kΩ < 0.8 V > 4.2V 1 kΩ 40V

Analog inputs Not electrically separated Number of inputs Resolution Jumper selectable range Maximal resistance range Maximal current range Input impedance Input impedance Resistance measurement tolerance Voltage measurement tolerance Current measurement tolerance

11 10 bits AIN1 AIN7: 20mA, VDC, 20kΩ VDC, 20kΩ AIN8 – – AIN11: 20mA,5±1 25 kΩ 22 mA 0  for mA measuring > 100 k  for V measuring  2 %  2  out of measured value  2 %  1mV out of measured value  2 %  0,5mA out of measured value

Communications

CAN bus interface Galvanically separated Maximum CAN bus length - CAN bus mode = 32C - CAN bus mode = 8C Speed - 32C - 8C Nominal impedance Cable type

200 m 900 m 250 kBd 64 kBd 120 Ω twisted pair (shielded)


Page 67 of 68

RS 485 Maximal distance Speed

1000m up to 57,6 kBd

-

ID- Mo bi le GPRS Type Frequency Bands GSM class Transmitting power GPRS CSD TCP/IP communication over GPRS Voltage supply

Simcom SIM900 GSM 850; EGSM 900, DCS 1800; PCS 1900; GSM/GPRS Small MS Class 4 (2W) at GSM 850 and EGSM 900 Class 1 (1W) at DCS 1800 and PCS 1900 multi-slot class 10 up to 14.4 kbps 8-36 VDC

ID -Mobile GSM Type Frequency Bands

GSM class Transmitting power Sensitivity

Telit GC864 GSM 850; EGSM 900, DCS 1800; PCS 1900; GSM/GPRS modem Compliant to GSM Phase 2/2+ Small MS Class 4 (2W) at GSM 850 and EGSM 900 Class 1 (1W) at DCS 1800 and PCS 1900 -107 dBm @ 850 / 900 Mhz -106 dBm @ 850 / 900 Mhz

ID- Mo bi le GPS Type Receiver type Sensitivity

Horizontal position accuracy Accuracy for Timepulse signal Velocity accuracy

U-BLOX, LEA-5H 50 Channels`GPS L1 frequency; C/A Code;GALILEO Open Service capable, GLONASS Tracking & Navigation – 162 dBm Reacquisition - 160 dBm Cold Start - 148 dBm 2,5 m RMS 30 ns 99% <60ns 0,1 m/s


Page 68 of 68

ID Logger - Reference Manual

Recommend Documents