id logger - reference manual

8/11/2019 ID Logger - Reference Manual

1/68

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

ComAp, spol. s r.o .Kundratka 17, 180 00 Praha 8, Czech RepublicTel: +420 246 012 111, Fax: +420 266 316 647

E-mail: [email protected] , www.comap.cz

REFERENCE GUIDE

InteliDrive

ID-Mob i le Lo gg erData Logg er

HW version 1.3; SW version 2.0, January 2014


2/68

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

Table of contents

Table of contents ..................................................................................................................................... 2 Abbreviations....................................................................................................................................... 4

Document information ............................................................................................................................. 5 Clarification of notation ........................................................................................................................ 5 Conformity declaration ........................................................................................................................ 5

Related .................................................................................................................................................... 6 Software .............................................................................................................................................. 6 PC Tools .............................................................................................................................................. 6 Documentation .................................................................................................................................... 6

General guidelines ................................................................................................................................... 7 What is ID-Mobile Logger? .................................................................................................................. 7 Features .............................................................................................................................................. 7

Hardware ................................................................................................................................................. 8 LED indication ..................................................................................................................................... 8 Dimensions and assembly .................................................................................................................. 9 Harnesses ......................................................................................................................................... 10 ID-Mobile Service Module ................................................................................................................. 11 Terminals ........................................................................................................................................... 12 Physical input/output structure .......................................................................................................... 13 Hardware configuration ..................................................................................................................... 15 Plug in modules ................................................................................................................................. 17 External displays ............................................................................................................................... 19 Communication lines ......................................................................................................................... 20

Controller setting ................................................................................................................................... 22 Modules ............................................................................................................................................. 22 Binary Inputs (BIN) ............................................................................................................................ 23 Logical binary inputs (LBI) ................................................................................................................. 23 Binary Outputs (BOUT) ..................................................................................................................... 26 Logical binary outputs (LBO)............................................................................................................. 27 Prg. states ......................................................................................................................................... 29

Analog Inputs (AIN) ........................................................................................................................... 30 Logical analog inputs (LAI) ................................................................................................................ 31 Shared virtual I/O periphery .............................................................................................................. 32

Values .................................................................................................................................................... 36 RPM/FlowMeters ............................................................................................................................... 36 Basic Values...................................................................................................................................... 36 Engine Values ................................................................................................................................... 37

Analog CU ......................................................................................................................................... 37 Binary CU .......................................................................................................................................... 37 Log Bout ............................................................................................................................................ 38 Info .................................................................................................................................................... 39 Statistics ............................................................................................................................................ 40 Position .............................................................................................................................................. 42

Setpoints ................................................................................................................................................ 44 Password ........................................................................................................................................... 44 Basic Settings.................................................................................................................................... 45 Comms Settings ................................................................................................................................ 48 RPM/FlowMeters ............................................................................................................................... 49

Analog Inputs .................................................................................................................................... 51 Act. Calls/SMS .................................................................................................................................. 51 Date/Time .......................................................................................................................................... 52 Statistics ............................................................................................................................................ 54

Position .............................................................................................................................................. 55

Limits ................................................................................................................................................. 55 Remote control and data logging .......................................................................................................... 58


3/68


Direct connection to the PC .............................................................................................................. 58 Modbus communication .................................................................................................................... 58 Event Log history ........................................................................................................................... 58

Operator Identification ........................................................................................................................... 62 Booting procedure ................................................................................................................................. 63 Technical Data ....................................................................................................................................... 66

Power Supply .................................................................................................................................... 66 Operating conditions ......................................................................................................................... 66 Dimensions ........................................................................................................................................ 66 Binary inputs...................................................................................................................................... 66 Binary outputs ................................................................................................................................... 66 Speed pick-up input .......................................................................................................................... 67 Impulse input ..................................................................................................................................... 67

Analog inputs..................................................................................................................................... 67 Communications ............................................................................................................................... 67 ID-Mobile GPRS ................................................................................................................................ 68 ID-Mobile GSM .................................................................................................................................. 68 ID-Mobile GPS .................................................................................................................................. 68


4/68


Abbrevia t ions

aid Archive file extension for InteliDrive controller AIN Controller or extension module Analog input Alarm General term for any active engine protection Warning, Shutdown, etc. Alarm list Controller or PC InteliMonitor screen with list of active and unaccepted

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

alarms detected from engine ECU. AOUT Controller Analog OUTput or outputs group. Archive Usually aid file that contains all controller data: configuration, setpoints

setting and history records.BI Controller binary input.BIN Controller binary inputs group.BO Controller binary output.BOUT Controller binary outputs group.CAN Control Area Network serial data link.Cd Cool down protection, cooling period is included before engine stops.DC DriveConfig, PC software for InteliDrive configuration.

DMDriveMonitor, PC software for InteliDrive monitoring (discontinued in Q32013).

DriveConfig PC software for InteliDrive configuration.DriveMonitor PC software for InteliDrive monitoring (discontinued in Q3 2013).ECU Engine Electronic (injection) Control Unit.

ECU alarm Alarm detected in engine electronic control unit that is received viaJ1939.

Fls Sensor fail alarm prefix.FMI Failure Mode Identifier.

GSM modem Modem for Global System of Mobile communicationHistory List of alarms and operational states with Reason, Date and Time and

adjustable values set that is stored in controller, can be listed from thescreen or InteliMonitor.

InteliVision 5 CANInteliVision 8 ComAp color display 5 or 8 inch.ID InteliDrive controller.IMON InteliMonitor, PC software for InteliDrive monitoring.InteliMonitor PC software for InteliDrive monitoring.J1587 The J1587 bus is mainly used for redundant signals; system diagnosis

and software download on after market tools.J1587/J1708 See J1587

J1939 The J1939 bus in mainly used for engine controls and engine monitoring.mhx Extension for controller firmware (Motorola HeX file).OFF Controller mode when power supply is switched on, but all binary outputs

and start commands are disabled = engine start is blocked.PID J1939 Parameter Identification Assignments.PPID J1939 Proprietary Parameter Identification Assignments.RPM Engine Revolution Per Minute engine speed.PSID J1939 Proprietary Parameter Identification Assignments.RS232 Standard serial data line for PC or Modem connection (controller

programming or monitoring).Sd Shut down protection.

SID J1939 Subsystem Identification Assignments.Wrn Warning protection.


5/68


Document information

ID-MOBILE LOGGER REFERENCE GUIDEWRITTEN BY : ZDENEK ROJKA 2014 COM AP LTD.KUNDRATKA 17, P RAHA 8, CZECH REPUBLIC P HONE : +420246012111, FAX : +420266316647WEB : HTTP ://WWW .COMAP .CZ , E -MAIL: INFO @ COMAP .CZ; SUPPORT @ COMAP .CZ

DOCUMENT HISTORY

REVISION NUMBER R ELATED SW . VERSION , DESCRIPTION DATE

1.8 1.8 5.2.2013

1.8.1 rev 1 1.8.1 formal changes, new chapter 4.4.2013

1.9 New software features, updated functionality 30.9.20132.0 New software features, updated functionality 10.1.2014

Clarif icat ion of notat ionNOTE : 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 orunproper function of the equipment if not performed correctly and may not be clear at first sight.

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

Conformi ty dec lara tion

Following described machine complies with the appropriate basic safety and healthrequirement of the EC Low Voltage Directive No: 73/23 / EEC and ECElectromagnetic 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 toupdate at any time. ComAp does not assume any responsibility for its use unless otherwise expresslyundertaken.
http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]://www.comap.cz/


6/68


Related

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

Software

Import package Files Note

ID-Mobile-Logger-2.0.idc ID-Mobile-Logger-2.0.mhx ID-Mobile-Logger firmware

ID-Mobile-Logger-2.0.aim Default configuration archives

PC Tools

RELATED SW . VERSION DATE

InteliMonitor 3.0.3 12.12.2013

DriveConfig 3.3.1 12.12.2013

WinScope 2.0 12.12.2013

LoggerHistoryExport 1.3 12.12.2013

Documenta t ion

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


7/68


General guidelines

What is ID-Mobile Lo gger?ID-Mobile Logger is a specialized data logger for engine driven mobile and industrial applications. TheLogger 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 orbinary 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 +8 0C 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.


8/68


Hardware

LED indica t ion

PowerPower supply indication is always lighted if the power supply is on.

RunRunning engine indication is lighted if the engine is running

AlarmIncoming 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 fastblinking and prolong the Alarm LED for next 60min. Auto quitted function disable the Alarm LED after60 minutes after the last alarm even if is still active.

StatusFull history buffer indication i.e. oldest records are lost (overwritten) without downloading. Status canbe cleared using the Logger History Export PC tool.

LED indication

Right side maleconnector:

BLACK

Left side maleconnector: BROWN

Plugs for Antenna connectors

Membrane overpressure relief


9/68


10/68


Harnesses

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

mm2.

Available standard harnesses supplied by ComAp

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

Connectors

Mating/Unmating of the connector from the header

Insert the connector until it stops in the header Rotate the lever

HARNESS LENGHT COMAP ORDER CODE

1.5 METERS ID-MOBILE HARNESS-LOG-1,5

6 METERS ID-MOBILE HARNESS-LOG-6

NOTE : Includes:One set of harnesses for ID-Mobile Logger:

left and right connector cables, interconnection cable sleeve

ITEM COMAP ORDER CODE

S ET OF CONNECTORS TERM SET ID-MOBILE

Includes:- right and left connector (brown, black)- accessories (pins, plugs)

NOTE : MOLEX connector: Series 64320

ID-MobileLogger


11/68


Lock it on the cover cap until it clicks

Press on the latch Rotate the lever

Rotate the lever

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

ID-MobileLogger

ID-MobileServiceModule


12/68


Terminals

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

Left side male connector - brown Right side male connector - black9 10 12 1 49 50 51 52 53 54 55 56 57 58 60

21 2 61 62 63 64 65 66 67 68 69 70 7225 26 27 28 29 30 31 33 34 36 3 73 74 75 76 79 80 81 82 83 8437 38 39 40 41 42 43 44 45 46 48 4 85 86 87 88 89 90 91 92 93 95 96 A B C D E F G H J K L M A B C D E F G H J K L M

Bottom side of box

Left side connector - Pins function

4 3 2 137 AI8+ 25 AIN 1 A 13 138 AI8- 26 AIN 2 B 14 239 AI9+ 27 AIN 3 C 15 340 AI9- 28 AIN 4 D 16 441 AI10+ 29 AIN 5 E 17 542 AI10- 30 AIN 6 F 18 643 AI11+ 31 AIN 7 G 19 744 AI11- 32 H 20 845 +5V 33 GND1 J 21 +5V 9 IM 2 IN46 GND3 34 K 22 10 IM 2 SUP47 35 L 23 1148 GND4 36 GND2 M 24 12 GND5

Right side connector - Pins function

4 3 2 185 RS485A 73 BO1 A 61 GND 49 BIN 186 485COM 74 BO2 B 62 GND 50 BIN 287 RS485B 75 BO3 C 63 GND 51 BIN 388 CAN1H 76 BO4 D 64 GND 52 BIN 489 CAN1COM 77 E 65 GND 53 BIN 590 CAN1L 78 F 66 GND 54 BIN 691 CAN2H 79 RPM 1- G 67 GND 55 BIN 792 CAN2COM 80 RPM 1+ H 68 GND 56 BIN 893 CAN2L 81 IM 1 IN J 69 GND I-BUTT 57 GND BIN94 82 IM 1 SUP K 70 I-BUTT 58 +5V95 BAT PLUS 83 +VBO L 71 5996 BAT MINUS 84 GND7 M 72 GND8 60 GND9


13/68


Logger hardware versions differencesTable contains the changes between hardware version 1.1 and 1.2

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

Phys ica l input /ou tput s t ruc ture

Communication lines(Twisted pairs)RS485, CAN1, CAN2

Sensors

3-wires

ID-Mobile-Logger

Power Supply8-36 VDC

PowerRun

AlarmStatus

25: AIN121: +5V

33: GND1

3-wires 26: AIN245: +5V

36: GND2

2-wires 27: AIN346: GND3



31: AIN784: GND7

4-wires 30: AIN658: +5V

2-wires 37: AIN8+

2-wires 39: AIN9+

60: GND9

95: BATT+96: BATT-

49: BIN1

50-62: BIN251-63: BIN352-64: BIN453-65: BIN554-66: BIN655-67: BIN756-68: BIN8

85: 485A86: 485COM87: 485B88: CAN1H89: CAN1COM90: CAN1L91: CAN2H92: CAN2COM93: CAN2L

38: AIN8-

40: AIN9-

2-wires 41: AIN10+

2-wires 43: AIN11+

42: AIN10-

44: AIN11-

IMP1SUP

IM1GND81: IM182: UM1

72: GND83-wires

IMP2SUPIM2GND

9: IM210: UM2

3-wires

RPMRPM1GND

80: RPM179: RPM1COM 2-wires

61: COM

70: I-Button

69: GND I-BUTT

I_BUTTON PROBE

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

83: +VBO

73: BO1

74: BO2

75: BO3

76: BO4

BATT+

BATT-

HW VERSION 1_1 HW VERSION 1_2(S INCE 4-2012)

BO1BO2BO3BO4+VBO

Not available 7374757683

I-BUTTGND I-BUTT

3433

7069


14/68


15/68


RPM Input

RPM1A

RPM1B

79

80

R P M

i n p u

t

Use magnetic pickup.

Impulse inputs

+IM1 SUP (+24VDC)

IM 1 IN

IM 2 IN

82

81

84

10

9

12 I m p u

l s e

i n p u

t s

BAT-

BAT-

+IM 2 SUP (+24VDC)

Use active NPN open collector sensors.

Hardware con figurat ionPrior 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.


16/68


Jumpers location

uP

AIN1 AIN2 AIN3 AIN4 AIN5 AIN6 AIN7

1 1213 2425 3637 48

49 6061 7273 8485 96

BOOT

GSMGPSRS232

POWER

RUN

ALARM

STATUS

1 2 0 R

1-2: 20 mANo jumper: 5 VDC3-4: 2,4 kOhm

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

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

AIN8 AIN9 AIN10 AIN11

1-2: +- 20 mANo jumper: +- 1 VDC3-4: 2,4 kOhm

GND GND GND GND

BOUT-BW

1 2 0 R

- B i a s

+ B i a s

SIMCARD

R S 4 8 5

1 2 0 R

C A N 1

C A N 2

4 3 2 1

J UMPERS GND

J UMPER OFF(NO J UMPER )

J UMPER ON(J UMPER CLOSED )

GNDRelated to AIN8 AIN11

Non IsolatedThermocouples

Ground on controller side

Isolated ThermocouplesGround on Thermocouple side

(engine)

J UMPERS AIN1 AIN11

NO J UMPER J UMPER 1-2 J UMPER 3-4

AIN1 - AIN7 5 VDC 0 - 20mA 0 2,4 k

AIN8 - AIN11 1 V100 mV

-1 V .. +2,5 V

Thermocouple KThermocouple JThermocouple L

20mA 0 2,4 k


17/68


ANOTHER J UMPERS 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 BinaryOutputs 1-4. Closed = deactivated,Opened = activated

BOOT System booting

Plug in modu les

GPS ModuleGPS module enables function of exact controller location as well asprotection against unwanted manipulation of the controller(GeoFencing).

After installation of the module to the controller is for the basicfunction 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 ModuleThere are three plug-in modules available:

1. ID-Mobile GSM (version 1.8.1 and lower )2. ID-Mobile GPRS3. ID-Mobile 3G (version 1.9 and higher )

Modules have three operation modes:1. Standard GSM mode CSD (Circuit Switch Data)2. GPRS mode3. 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 (combinedGSM/GPRS/3G and GPS antenna).


18/68


19/68


External disp lays

InteliVision 88 color TFT display - 800x600 pixelsOperating temperature: -20 +75C Front IP65 / Rear IP 20CAN bus interfacePlug and Play structure following controller configurationPower supply 8 36 VDC

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

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

Supported version in ID-Mobile/ID-Mobile-Logger SW version

1.2 and higherNOTE : 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, EthernetPower Supply 9 30 VDCOS: Windows Embedded Standard 7ComAp sw: InteliMonitor.


20/68


Comm unica t ion l ines

RS485

RS485-A

COM

RS485-B

85

86

87 R S 4 8 5

RS485 / USBconverter

USB

USB

DriveConfigDriveMonitor

WinScope

ID-Mobile / ID-Mobile-Logger CAN1 interface is dedicated to: PC interface for communication with DriveMonitor/InteliMonitor, DriveConfig and other SW. MODBUS communication interface

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

CAN2ID-Mobile / ID-Mobile-Logger CAN2 interface is dedicated to:

external displays (see External d i sp lays ) ID-Mobile Slave unit I-LB, I-LB+,

CAN bus connection rulesCan bus line must be connected in series, from one unit to another (no star, no cable stubs, no

braches) and both ends must be terminated with 120 resistor.

COMMUNICATIONS ID-MOBILE -LOGGER

Direct connection

USBRS485RS232CAN1CAN2

GSM 1)

GPRS 1)

UMTS 1)

GPS 1)1) Plug-in module required


21/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 inID-Mobile / ID-Mobile-Logger is 250kBd. The limitation of line for the default speed is 200m maximum.


22/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 Guideavailable on ComAp webpage: http://www.comap.cz/support/download-center/type/manuals/ .

ModulesFollowing items is possible to configure in DriveConfig Modules

MODULE MAXIMUM AVAILABLE (USED /MAX.AVAIL .) DETAILS

ID-MOBILE LOGGER 1/1 ID-Mobile Logger unit - It is obligatory item.

B INARY INPUTS MODULE x/8 Binary Inputs external extension module

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

S HARED BINARY INPUTS x/4 Shared virtual binary inputs periphery

S HARED BINARY OUTPUTS x/4 Shared virtual binary outputs periphery

S HARED ANALOG INPUTS x/4 Shared virtual analog inputs periphery

S HARED ANALOG OUTPUTS x/4 Shared virtual analog outputs periphery

ECU x/1 Engine Control Unit interface

ICB MODULE x/1 External Interface Communication Bridgeinterface

VIRTUAL B INARY OUTPUTS x/4 Group of Virtual binary outputs

PLC x/1 PLC tool enabled

ECU LOG x/5 Extended ECU values (special programming ofesf. needed)
http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/


23/68


Bin ary Inputs (BIN) Available configuration for Binary inputs:

NOTE : Minimal input pulse duration is 120ms to be detected as valid (binary inputs sampling rate 100ms).

Adjustable delay can be configured to any binary input according to details above.

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

P ROPERTY VALUE DETAILS

ECU VALUE Available only if ECUselected under ECU-1

According toselection ECU output can be selected as controller inputs.Selection depends on ECU type.Selection of ECU see Modules NOTE : Some ECU are not supporting this function

NAME Text Maximum 14 charts

P ROTECTION No Protection No protection active with BI

Warning BIN is active- Alarm on LED (eventually Display)- History record

Sensor fail BIN is active:- Indicates sensor fail- History record

Alarm Only BIN is active:- Alarm on LED (eventually display) only

HistRecOnly BIN is active:- History record only

P ROT .ACTIVE Closed Protection active if the contact is closed

Open Protection active if the contact is open

P ROT . BLOCK TYPE All the time Protection is active all time

Force Block Protection is active with Force Block only

RunOnlyBlkDel Protection is active only if engine is running with delayaccording to Setpoint Basic Setting / RunOnlyBlkDel from start

DELAY Standard (0,5s) The input signal is delayed for 0,5s (Default setting)

BinInp delay 1 The input signal is delayed according to Setpoint:Basic Settings / BinInp Delay 1



FUNCTION Logical function Find more details in: Logical binary inputs


24/68


Following chapter contains Logical binary inputs list (functions list) that can be configured to anyphysical 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= ForceBlock. Corresponding setpoint is Basic Settings / ForceBlock Del .

Fault ResetBinary input for Alarm acknowledge (edge sensing) has the same function as controller front panelbutton 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 afterengine stop.

RunIndication1 RunIndication3Binary input can be used for engine running indication e.g. via Oil pressure contact. Active Runningindication blocks engine start (to avoid starter damage).

ECU FltResetBinary input for ECU Alarm acknowledge (edge sensitive) has the same function as controller frontpanel 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 (fromother like MODBUS, ECU LINK ).

CAUTION !

RS485 communication does not work when RS485 mode is changed from standard to MMOO DDBBUUSS orEE CC UU LLIINNKK. See setpoint: Comms Setting / RS485 Mode description.


25/68


Configure this input (or leave as it is in default) for case the RS485 mode setpoint is changed toMMOO DDBBUUSS or EE CC UU LLIINNKK from DriveMonitor. It is the way how to establish communication withDriveMonitor.

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 / HomeLong setpoints.

Clear TotalCons Active input clears the Total Consumption counter ( Statistics / TotalConsumpt ).

Clear TripCons Active input clears the Trip Consumption counter ( Statisctics / TripConsumpt ).

BI HistoryClosed binary input activates one History record.

Reset OperIDRising edge of binary input resets Operator identification number ((Info / Operator ID )).

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

TripAverageResRising 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 , FaultReset etc.)If TripAverageRes = 1 the TripAverage value is reset.

TotAverageEnaRising edge of binary input enables the Total Average ( Statistics / TotalAverage ) calculation for theLAI AverageValue .If TotalAverageEna = 1, the calculation runs.

TotAverageResRising 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, FaultReset etc.)If TotalAverageRes = 1 the TotalAverage value is reset


26/68


AveragSpeedEnaRising edge of binary input enables the Average Speed ( Statistics / AverageSpeed ) calculation forthe LAI Average Speed .If AveragSpeedEna = 1, the calculation runs.

AveragSpeedResRising 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, FaultReset etc.)If AveragSpeedRes = 1 the AverageSpeed value is reset

Zone 13 ON Active input starts the calculation of Time and Consumption Zones (Statistics / Time Zone x andStatistics / Consump Zone x ) regardless on setpoints Statistics / RPM Start Zx , RPM Stop Zx , FuelStart 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.

ZonesResetResets 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 beconnected - maximum continuous current for single channel is 0,5 A only.


S OURCE Log Bout See Logical Binary Outputs functions

Prg. states Controller internal states

Ana protections One of the following AIN protection levels is sent asbinary signal.L1 level 1 of protectionFls Sensor failL1+Fls sensor fail or/and L1

Bin protections Protection of BIN is sent as binary signal

Binary CU State of logger BIN is sent as binary signal.

ECU State of ECU-1 BIN is sent as binary signal.

NAME Text Title of the BOUT - maximum 14 charts

ECU VALUE Available only if ECUselected under ECU-1

According to selection Controller output can be selected as ECU inputs.Selection depends on ECU type.NOTE : Some ECU are not supporting this function

INVERTED No Inactive state BOUT = 0, active state is BOUT = 1.

Yes Inactive state BOUT = 1, active state is BOUT = 0.


27/68


Logica l b inary o u tputs (LBO)

HornBinary output for Horn, Buzzer alarm acoustic indication. Horn is active unlimited time (until Faultreset is pressed/activated).

AlarmThe output closes if any alarm is activated and opens after Fault reset even if the Alarm is still active.

Common AlarmThe output closes if any Wrn, Sd, Cd, Fls, alarm is active and stays closed until all alarms disappearand Fault reset is pressed. Output is opened when Alarm list is empty.

Common WrnThe output closes when any Warning alarm is active. Output opens when all Wrn alarms disappearand Fault reset is pressed (no Wrn alarm in Alarm list).

Common SdThe output closes when any Shut-down alarm is active. Output opens when all Sd alarms disappearand Fault reset is pressed (no Sd alarm in Alarm list).

Common CdThe output closes when any Cool-down alarm is active. Output opens when all Cd alarms disappearand Fault reset is pressed (no Cd alarm in Alarm list).

Common FlsThe output closes when any Sensor fail alarm is active. Output opens when all Fls alarms disappearand Fault reset is pressed (no Fls alarm in Alarm list).

Common SdOThe output closes when any Shut-down Override alarm is active. Output opens when all SdO alarmsdisappear 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 RunningIt activates, when RPM rises above starting RPM and opens when RPM=0.

CtrlHeartBeatIndicates correctly running firmware when cycling on/off with 0,5 sec period.

Comm AIN FailOutput is closed when any analog extension (IS-AIN, IGS-PTM) unit does not communicate.


28/68


29/68


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

RemoteControl18 Remote control outputs can be controlled locally or remotely (via Modem) fromDriveMonitor/InteliMonitor Remote switch panel.

Prg. statesProgrammable states (protections) list. Any item from the following list activates Alarm list indication.

ECUECU communications fail indication

SHBIN 1..4Status of shared Binary inputs

SHAIN 1..4Status of shared Analogue inputs

SHBinCfgErrShared Binary module configuration error i.e. more than one source was configured (is on the CAN2bus).

SHAinCfgErrShared Analog module configuration error i.e. more than one source was configured (is on theCAN2 bus).

UnivState 1...7The output closes when any Warning alarm is active. Output opens when all Wrn alarms disappearand Fault reset is pressed (no Wrn alarm in Alarm list).

PLC Message 1...8Indication of programmable PLC state.

ECU AlarmListOutput is closed when at least one item is in ECU Alarm list.

GeoFencingThe output is active if GeoFenging is announced the actual position is out of fence

MasterCommErrCommunication with Master control unit fails.

Note:Related to ID-Mobile Slave control unit only


30/68


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

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


NAME Text Maximum 14 charts

DIM -, RPM, ppl, bps, Bar, s, V,h, min, m, C, kPa, l, km/h,%, l/h

Dimension of the value

S ENSOR

AIN1 AIN7

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 userNOTE : For more details see DriveConfig User Guide

AIN8 AIN11

+-20mA Current input within listed intervals

0 2400 ohm Resistance input within listed intervals

+-1V Voltage input within listed intervals

+-100mV Millivoltage input within listed intervals

-1.0V 2,5V Voltage input within listed intervals

Thermocopl K/C (K/F) Predefined characteristic for usual type ofthermocouplesThermocopl L/C (L/F)

Thermocopl J/C (J/F)

RESOLUTION 1; 0,1; 0,01; 0,001; 0,0001 Definition of decimal point for AIN

S ENSOR R ANGE 09999 Definition of sensor range for AIN

P ROTECTION No Protection No protection is active on AIN

Sensor Fail Measured value is out of sensor characteristic

Warning Activated Wrn

HistRecOnly Protection is written in the history only

ACTIVE WHEN Under Limit Protection is active if a value is under selected limit

Over Limit Protection is active if a value is over selected limit

Under limit + Fls Protection is active if a value is under selected limitand/or sensor fail is indicated
http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/http://www.comap.cz/support/download-center/type/manuals/


31/68


Over Limit + Fls Protection is active if a value is over selected limit and/orsensor fail is indicated

BLOCK T YPE 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 delayfrom start

BARGRAPH 0% -99999999 Value related to 0% of Bargraph

BARGRAPH 100% -99999999 Value related to 100% of Bargraph

FUNCTION Logical function See more details in Logical analog inputs

Log ical analog inp uts (LAI)

Engine SpeedLogical RPM value for Engine RPM indication, overspeed protection, engine running and overloaddetection.

RPM1

Engine Speed

LAIEngine RPM

(value)

State Machine

Default configuration

ECU-RPM

Oil PressLogical value for oil pressure indication on displays (non-editable screen) value Engine Values / OilPress. 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 TempLogical value for oil temperature indication on displays (non-editable screen) value Engine Values /Oil Temp.


Coolant TempLogical value for coolant temperature indication on displays (non-editable screen) value EngineValues / Cool Temp.


Fuel ConsActLAI can be lined to external Fuel consumption sensor (Flowmeter) or ECU Fuel rate value. This inputis a source for Statistics calculation.


32/68


LAI:Fuel ConsAct

Statistics

LBI: Clear TotalCons

LBI: Clear TripCons

Imp/UnitIM1

RPM/FlowMeters

Pulses IM1

ImpulseInput 1

Analog input x [L/h]

Fuel sensor

ECUJ1939Fuel Rate [ L/h ]

FlowMeter IM1 [ L/h1 ]

Imp/UnitIM2

Fuel sensor

ImpulseInput 2

TotalConsumpt [ L ]

Time Zone x [ s ]

Consump Zone x [ L ]

TripConsumpt [ L ]

RPM/FlowMeters

Pulses IM1


TempComp AIN8 .. TempComp AIN11Temperature correction for AIN8 AIN11 if Thermocouple are used. E.g. TempComp AIN8 =compensation temperature for AIN8.

Average ValueLAI is a source for Statistics / TripAverage and Statistics / TotalAverage calculation.

Average Speed

LAI is a source for Statistics / AverageSpeed calculation.

Shared vir tu al I/O per iph eryIt is often required that certain signals be brought to all controllers in the group. For example binarysignals: System Start/Stop, Common Shutdown signal etc. Sometimes analog signals are required aswell, like engine room temperature signal, where too high temperature can cause the nominal powerof 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 thissophisticated system of shared virtual modules, where one controller is a signal server and the othercontrollers are recipients of this signal. The signals are distributed via the CAN bus which typicallyinterconnects all the controllers on one site.

ConfigurationThese virtual modules can be added / removed like any other HW module in DriveConfig / cardModules. Then they appear in the list of inputs or outputs in the card I/O.

SHBOUT/SHAOUT modulesThey behave like standard output modules, but the signals assigned to them dont appear on anyphysical output, instead of that are distributed via the CAN bus to other controllers. Each module has 4outputs.


33/68


SHBIN/SHAIN modulesThey behave like standard input modules, i.e. you can assign any logical input signal that is availablein the controller to them, or configure a protection based on their activity. Each module has 4 inputs.

SHBOUT + SHBIN modulesThere are four channels (4 groups of 4 binary inputs/outputs) available for binary signal sharing. Eachchannel can have its source (SHBOUT module) in different controller. All other controllers can beconfigured as the recipients of this channel (SHBIN module).

SOURCE(SHBOUT)

TARGET(SHBIN)

TARGET(SHBIN)

TARGET(SHBIN)

I n t e r c o n

t r o

l l e r

C A N

b u s

Hint:If more controllers are selected to be the source for one channel, only the controller with the lowestCAN 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 ofphysical binary inputs, or some signals created inside the controllers FW or P LC:

P H Y S I C A L

B I N A R Y

I N P U T S

CONTROLLERSTATE

MACHINE

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

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

S H B O U T

Intercontroller CAN bus

SYSTEM START

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

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


34/68


P H Y S I C A L

B I N A R Y

I N P U T S

CONTROLLERSTATE

MACHINE


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

Intercontroller CAN bus S H B I N

Together looks like this:

SHBOUT11

1 . CONTROLLER 2 . CONTROLLER

CAN2

Sys start/stop C A N 2

3 . CONTROLLER

BOUT

BOUT4

BOUT3

BOUT2

SHBIN1

BIN1

BIN4

BIN3

BIN2

SHBIN1

BIN1

BIN4

BIN3

BIN2

C o n

t r o

l l e r

F u n c t

i o n s

Setpoints

LogicalInputs

LogicalOutputs

C o n

t r o

l l e r

F u n c t

i o n s

Setpoints

LogicalInputs

LogicalOutputs

C o n

t r o

l l e r

F u n c t

i o n s

Setpoints

LogicalInputs

LogicalOutputs

SHAOUT + SHAIN modulesThere 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 beconfigured as the recipients of this channel (SHAIN module).

SOURCE(SHAOUT)

TARGET(SHAIN)

TARGET(SHAIN)

TARGET(SHAIN)

I n t e r c o n

t r o

l l e r

C A N

b u s

Hint:If more controllers are selected to be the source for the analog channel, only the controller with thelowest 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 valuesof externally measured (physical) analog inputs, as well as the values measured or computed inside

the controllers FW or PLC:


35/68


P H Y S I C A L

A N A L O G

I N P U T S

CONTROLLERSTATE

MACHINE


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

Intercontroller CAN bus S H A O U T

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

P H Y S I C A L

A N A L O

G

I N P U T S

CONTROLLERSTATE

MACHINE


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

Intercontroller CAN bus

S H A I N

Together looks like this:

C o n

t r o

l l e r

F u n c t

i o n s

SHAOUT1 AOUT 1 AOUT 2 AOUT 3 AOUT 4

Setpoints

1 . CONTROLLER

C o n

t r o

l l e r

F u n c t

i o n s

SHAIN 1

AIN 1 AIN 2 AIN 3 AIN 4

Setpoints

2 . CONTROLLER

CAN2

Temperature X

C A N 2

Temp X

Temp X

LogicalInputs

LogicalOutputs

LogicalInputs

LogicalOutputs

3 . CONTROLLER

C o n

t r o

l l e r

F u n c t

i o n s

SHAIN 1

AIN1 AIN2 AIN3 AIN4

Setpoints

Temp X

LogicalInputs

LogicalOutputs


36/68


37/68


Engine Values

Oil Press Oil Pressure [Bar] what can be sourced by different input set to Logical Analog Input Oil Press . OilPress value can be used as engine Running indicator, see Setpoints / Basic Settings / Running Poil.

Oil TempOil Temperature [C] what can be sourced by different input set to Logical Analog Input Oil Temp .

Cool TempCoolant 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 VoltVoltage of the battery (Power source for the controller).

CPU TempProcessor temperature of the controller.

Bin ary CU

ID BINBinary inputs according to configuration


38/68


ID BOUTBinary outputs according to configuration

Log Bou t

LogBout 1, 2Logical binary functions.


39/68


RemoteControlRemote control switches status.

Info

Engine StateEngine state: Running, Not Running, Ready to Start, Cranking, Cooling etc.

PasswordDecodeThis code together with controller S/N is needed if controller password is forgotten.

Operator IDIdentification number of the operator what is read from Operator Key.

SW VersionSW version of the controller.

SW Branch

SW branch identification.

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


40/68


Code Description Code Description

0 OK. No error. 11SIM card is locked (Possibly PIN code required, PINneeds to be deactivated) or unknown status of SIMlocking

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 initializationcommand, possibly caused by locked SIM card

4 ID-Mobile-GPRS error in initialization 15 Unknown modem

5 ID-Mobile-GPRS not possible to set the APN 16 Bad answer to complement initialization string

6 ID-Mobile-GPRS not possible to connect toGPRS network 17 Not possible to read GSM signal strength

7 ID-Mobile-GPRS not possible to retrieve IPaddress 18 CDMA modem not detected

8 ID-Mobile-GPRS not accepted DNS IPaddress 19 No CDMA network

9 Error in modem detection 20 Unsuccessful registration to CDMA network

10 Error in initialization of analog modem 255 Only running communication is needed to indicate

AirGate Diag AirGate troubleshooting diagnostic code

AirGate IDIdentification 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 doesNOT support AirGate).

Modem StatusIndication 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.

Stat is t ics

Run Hours [h]

Engine running hours.

Code Description

1 Controller registered, waiting for authorization2 Not possible to register, controller blacklisted3 Not possible to register, server has no more capacity4 Not possible to register, other reason5 Controller registered and authorized


41/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 / ServiceTime.

TotalConsumpt [liters]Total consumption is calculated from source set in LAI Fuel ConsAct . It can be analog input or ECUvalue (for conversion to right range and dimension can be used User Curves) or impulse inputs IMP1or IMP2 (recalculated with parameter Imp/Unit IM1 or Imp/Unit IM2). The value can be reseted by LBIClearTotalCons or set to user value with InteliMonitor/DriveMonitor from menu Monitor SetStatistics

TripConsumpt [liters]Total consumption is calculated from source set in LAI Fuel ConsAct . It can be analog input or ECUvalue (for conversion to right range and dimension can be used User Curves) or impulse inputs IMP1or IMP2 (recalculated by parameter Imp/Unit IM1 or Imp/Unit IM2). The value can be reseted by LBIClearTripCons or set to user value via InteliMonitor/DriveMonitor from menu Monitor Set Statistic s

LAI:Fuel ConsAct

Statistics

LBI: Clear TotalCons

LBI: Clear TripCons

Imp/UnitIM1

RPM/FlowMeters

Pulses IM1

ImpulseInput 1

Analog input x [L/h]

Fuel sensor

ECUJ1939Fuel Rate [ L/h ]


Imp/UnitIM2

Fuel sensor

ImpulseInput 2

TotalConsumpt [ L ]

Time Zone x [ s ]

Consump Zone x [ L ]

TripConsumpt [ L ]

RPM/FlowMeters

Pulses IM1


TripAverageTrip Average Value calculates the arithmetic average of common value if the calculation is activatedwith LBI TripAverageEna as long the value is reseted with LBI TripAverageRes . Input for averagevalue 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.

TotalAverageTotal Average Value calculates the arithmetic average of common value if the calculation is activatedwith LBI TotalAverageEna as long the value is reseted with LBI TotalAverageRes . Input for averagevalue 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.


42/68


AverageSpeed Average Speed calculates the arithmetic average of common value if the calculation is activated withLBI AverageSpeedEna as long the value is reseted with LBI AverageSpeedRes . Input for averagevalue calculation is set in LAI Average Speed (e.g. GroundSpeed, Speed from ECU, DashboardSpeed etc.). For reset is commonly used e.g. OperatorID, Start Button, Fault Reset etc.

Time Zone 16 [s] Time spent in configured zone. Each statistic zone is defined with Engine RPM and Fuel consumption(see setpoints in group Statistics). For calculation into defined zone has to be fulfilled both conditions:RPM Start Z1 < actual RPM < RPM End Z1 and Fuel Start Z1 < actual Fuel Consumption < Fuel EndZ1. Calculation to Zone 13 can be activated with LBI Zone x ON too.

Consump Zone 16 [ L]Fuel consumption in configured zone. Each statistic zone is defined with Engine RPM and Fuelconsumption (see setpoints in group Statistics). For calculation into defined zone has to be fulfilledboth conditions: RPM Start Zx < actual RPM < RPM End Zx and Fuel Start Zx < actual Fuel

Consumption < Fuel End Zx . Calculation to Zone 13 can be activated with LBI Zone x ON too.E.g. for setting:

Z1 Z2 Z3RPM Start 0 RPM 0 RPM 1000 RPMRPM End 1000 RPM 2000 RPM 2000 RPMFuel Start 0 L/h 100 L/h 0 L/hFuel End 100 L/h 200 L/h 100 L/hLBI: Zone x ON OFF OFF ON

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

Pos i t ion

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

Actual Long [m] Actual GPS L ongitude value (e.g. 1428'54.269"E).

HomePosDist [m]Distance from Home position in meters. Home position is set by setpoints Position Home Lat andHome Long .

Error Lat [m]Latitude error in meters.

Error Long [m]Longitude error in meters.

SatelitesUsed [-]Number of used GPS satellites.


43/68


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

Ground Speed [km/h]

Actual ground speed in km/h.


44/68


Setpoints

PasswordThere are three levels of password protection.0. User level allows change of non-protected setpoints only1. Operator level allows change of setpoints protected by Operator level2. Master level allows change of setpoints protected by Operator and Master level3. Supervisor highest level allows all setpoints or configuration changes, firmware upgrade.Hint:Grey color of setpoint in InteliMonitor indicate the setpoint is password protected.

EnterPasswordPassword 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 bechanged from InteliMonitor / DriveMonitor - menu: Monitor - > Change access code It can be up to16 ASCII characters. At first the Password3 has to be entered before the new Access code can bechanged.


45/68


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

Basic Sett ings

Engine NameDimension: [ - ]Range: max. 15 characters

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

NOTE : Engine name is not changed when new archive is loaded. Check Engine name after firmwareupgrade.

Engine TypeDimension: [ - ]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 TeethDimension: [ - ]Range: 1 - 500Step: 1Terminals: 79 - 80

Number of teeth on the engines flywheel for the pick-up related to RPM input . Internal value Enginespeed is in default connected to RPM input if there is no other configuration to ECU or PLC function.

Nominal RPMDimension: [ RPM ]Range: 30 - 4000

Step: 1 RPMTerminals:


46/68


Nominal engine speed, base for Over-speed protection limit.

Oper ID AlarmDimension: [ - ]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 RPMDimension: [ RPM ]Range: 30 Nominal RPM Step: 1

RPM limit for running engine detection.

Running POilDimension: [ Bar ]Range: 0,00 10,00Step: 0,01

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

RunOnlyBlkDelDimension: [ s ]Range: 0 60Step: 1

Delay for Engine running Alarms activation.

BINARY INPUTPhysical

closed

BINARY INPUTInternal value

BinInp delay

Engine runningstate

RunOnlyBlkDel

PROTECTION inactive active

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

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

BINARY INPUT

BinInp delay physical

BINARY INPUT

Internal valueno change


47/68


BINARY INPUT


BINARY INPUT

closed

Internal value

BINARY INPUT


BINARY INPUT

Internal value

DriveConfig: I/O, Property, Protection active = Opened

opened

ForceBlock DelDimension: [ s ]Range: 0 60Step: 1

Delay for Force block protection activation after Binary input Force block is opened. Protectiondeactivation is without delay. Protection is activated/deactivated independent on engine running or notrunning state.

BINARY INPUTForceBlock del FORCE BLOCK

Protection

closed

BINARY INPUTProt, block type = Force block

closed

active activeinactive

Batt V )) Step: 0,1

Under voltage of controller power supply.

Batt >VDimension: [ V ]Range: 8,0 ( Batt


48/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 actualcounter value.

NOTE : Once the service time has elapsed the Service time will have to be adjusted to non-zero value (at leastfor 30sec) to clear the alarm and begin a new countdown.

LB/UART LogDimension: [ - ]Range: DISABLED, ENABLED

S et 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 Set t ings

ControllerAddrDimension: [ - ]Range: 1 - 32Step: 1

Controller CAN bus and RS-485 identification number. Each controller has to have its own uniquenumber. When opening connection to the controller (using PC monitoring/control SW), the Controller

address has to correspond to the setting in PC SW.

RS485 ModeDimension: [ - ]Range: STANDARD, MODBUS, ECU LINK

Communication protocol selection: STANDARD - InteliDrive (DriveMonitor, DriveConfig) communication protocol. MODBUS - Modbus RTU protocol. ECU LINK - ECU communication via RS485.

MODBUSDimension: [ bps ]Range: 9600, 19200, 38400, 57600

Modbus interface baud rate setting

ComApPortDimension: [ - ]Range: 1 65535, default = 23Step: 1

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


49/68


APN NameDimension: [ - ]

Access point name (APN) for mobile network communication. This information shall provideGSM/GPRS operator. E.g. Vodafone UK: pp.Vodafone.co.uk .

APN UserNameDimension: [ - ]

User name for APN access point for GPRS network connection. This information shall provideGSM/GPRS operator. E .g. Vodafone UK: web .

APN UserPassDimension: [ - ]

User password for APN access point for GPRS network connection. This information shall provide

GSM/GPRS operator. E .g. Vodafone UK: web .

AirGate IPDimension: [ - ]Default: airgate.comap.cz

IP address of AirGate server.

DNS IPDimension: [ - ]Default: 8.8.8.8

IP address of Domain Name Server.

RPM/FlowMeters

Imp/Unit IM1Dimension: [ i/L1 ]Range: 0,0 6500,0Step: 0,1

Set number of impulses in IMP1 what corresponds to volume unit L1. Concrete volume unit is possibleto specify in DriveConfig - Translator by change dimension L1.

Imp/Unit IM2Dimension: [ i/L2 ]Range: 0,0 6500,0Step: 0,1

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


50/68


Imp/UnitIM1

Pulses IM1

ImpulseInput 1

Fuel sensor FlowMeter IM1 [ L/h1 ]

Imp/UnitIM2

Fuel sensorImpulseInput 2

Pulses IM1


EvalPeriod IM1Dimension: [ s ]Range: 0,1 10,0Step: 0,1

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

EvalPeriod IM2Dimension: [ s ]Range: 0,1 10,0Step: 0,1

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

TPresUnit IM1Dimension: [ ]

Range: HOUR, MIN, SECPresentation time interval for measurement number of impulses IMP1 and calculation of FlowMeterIM1. 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 IM2Dimension: [ ]Range: HOUR, MIN, SEC

Presentation time interval for measurement number of impulses IMP2 and calculation of FlowMeterIM2. 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!

FlowIntTimUnitDimension: [ ]Range: HOUR, MIN, SEC

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


51/68


52/68


Range: 1 30

Number of rings prior to open modem connection from PC to controller. The change is accepted aftercontroller is switched on or when modem is connected to controller.

A.C.MultiplierDimension: [ - ]Range: 1 250

Number of attempt to open the active call data connection when the phone line is engaged. Timeoutfor connection is 90 sec and after 120 sec controller starts the next attempt. Incoming calls areblocked during the time the controller is trying to send an active call type. This setting doesn t refernumber of attempt to send SMS (it is fixed = 5 attempts).

ModemDimension: [ - ]Range: TELIT 3G, TELIT GPRS, SIMCOM CSD, SIMCOM GPRS

Selection of internal modem mode: TELIT 3G: UMTS modem, support only fundamental data connectivity and sending SMS. AirGate

and WebSupervisor support is not included! TELIT GPRS: for special custom application only. SIMCOM CSD: module works as standard GSM modem enabling CSD (Circuit Switch Data)

connection to controller with InteliMonitor / DriveMonitor and sending alarm SMS. SIMCOM GPRS: module for GPRS communication of controller with InteliMonitor / DriveMonitor

via AirGate and with WebSupervisor.

NOTE :UMTS, GPRS and CSD services has to be provided by your mobile operator for successful operation.

Any software update of the controller is not supported via wireless connection. Software update canbe done via direct connection only.

Date/Time

TimeDimension: [ hh:mm:ss ]

System (controller) time can be modified here. The system time is stored in a battery-backup RTCcircuit and normally need not to be adjusted except initial setting and occasional corrections. Thesystem date and time is used for the exercise timers as well as for the history log. Each record in thehistory 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, itmay indicate the backup battery needs to be replaced.

DateDimension: [ 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 theexercise timers as well as for the history log. Each record in the history log contains a date/timestamp.


53/68


NOTE : If the system date and time get incorrect after the controller has been switched off for longer time, itmay indicate the backup battery needs to be replaced.

Time Stamp Per

Dimension: [ s ]Range: 0 14400Step: 1

Standard history record period.

Time Stamp DelDimension: [ s ]Range: 0 ( Time Stamp Per )) 14400Step: 1

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

Fast Stamp PerDimension: [ s ]Range: 0 600Step: 1

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

Fast Stamp DelDimension: [ min ]Range: 0 100Step: 1

Time duration of the Fast stamp records.

EngineNot running Running Engine Not running

Time Stamp Per

Time Stamp Del

Alarm

Fast Stamp Per

Fast Stamp Del

Time Stamp Per

No periodicrecords

Periodic recordsNo periodicrecords

No Alarm

HistoryEntriesDimension: [ - ]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.


54/68


SummerTimeModDimension: [ - ]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.

Stat is t ics

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

RPM trigger start RPM value for initiation of statistic Zone 1 6 counting. RPM source is LAI EngineSpeed.

RPM End Z16Dimension: [ -]Range: RPM Start Z16 Nominal RPM

RPM trigger stop RPM value for initiation of statistic Zone 1 6 counting. RPM source is LAI EngineSpeed.

Fuel Start Z16Dimension: [ L/h]Range: 0,0 Fuel End Z16

Consumption trigger start value for initiation of statistic Zone 1 6 counting. Consumption source isLAI Fuel ConsAct.

Fuel End Z16Dimension: [ L/h]Range: Fuel Start Z16 1000,0

Consumption trigger stop value for initiation of statistic Zone 1 6 counting. Consumption source isLAI Fuel ConsAct.

For calculation into defined zone has to be fulfilled both conditions: RPM Start Zx < actual RPM Generate Cfg Image.

Event Log h i s toryID-Mobile-Logger has two separated memory for history records: Event History and Long History.

Event HistoryShort event history what is available on-line from InteliMonitor/DriveMonitor. This list is available via allpossible 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.
http://www.asix.cz/http://www.asix.cz/http://www.asix.cz/http://www.vpi.us/usb-serial.htmlhttp://www.usbgear.com/item_288.htmlhttp://www.usbgear.com/item_288.htmlhttp://www.usbgear.com/item_288.htmlhttp://www.modicon.com/openmbus/http://www.modicon.com/openmbus/http://www.modicon.com/openmbus/http://www.modicon.com/openmbus/http://www.usbgear.com/item_288.htmlhttp://www.vpi.us/usb-serial.htmlhttp://www.asix.cz/


59/68


Long HistoryThe 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 andtype of logged values):

Max. record size[bytes]

Max. number ofrecords about

16 524 00032 262 00064 131 000

128 65 000256 32 000

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

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

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


60/68


ComAp.InteliServer.Base.dllo Base library

ComAp.InteliServer.LowLevel.dllo 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 implementationLow 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 eventarguments contain data to fully identify what has completed.

Working with valuesCommunication with ComAp controller is based on reading and writing of so called communicationobjects . 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 toregister a metadata to communication object numbers for each controller and the library will transformraw values to real values. Available transformations contain for example division of raw value ormapping strings to values for string lists.

Interface description for read long history24390 Max. number of records

in the long historyUnsigned32 Read only (# 87)

24389 Number of records inthe long history

Unsigned32 Read only If the history is full, the value is themaximum number of records in a longhistory (see comm. object 24390)(# 87)

24388 The youngest record inthe long history

Domain Read only (# 87)

24387 Older record in the longhistory


24386 The actual record in thelong history

Domain Read only Reads a record referenced by the currentred index value in a long history

(# 87)24385 Setting the read indexin a long history torecord coresponding tothe specified timestamp

Domain6 Write only Set the read index in a long history at thevalue coresponding to the given timestamp.

Adjusted index will match the record with thegiven timestamp or the closest older record,if the record with th e timestamp doesntexist.Long history is cyclical records sequence, inthis sense, is the closest older record afterthe oldest record is the youngest record;It isnt possible to set reading index, whenlong history is empty (controler returns anerror response).

(# 87)(# 88)


61/68


24384 Acknowledge fullindication memory forthe long history

Binary8 Write only (# 87)(# 89)

24383 Write index in the longhistory

Unsigned32 Read only (# 87)

24382 Read index in the long

history

Unsigned32 Read only (# 87)

24381 Younger record in thelong history


# 87 A long history is cyclical sequence of records. At the same time can preserve the history of thenumber of records the value of the communication object 24390. Current number of records may beobtained by reading the communication object 24389. Writing the new record will occupy the first freeitem or overwrites (if history is full), the oldest entry. It is supposed that the history will be read startingat the youngest record (communication object 24388) or record done by written timestamps (seecommunication 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 youngestrecording.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 errorcode:0x080000F0 ... operation must be repeated0x06010000 ... access denied - empty history

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

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

# 88Format 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)

id logger - reference manual

Documents