I-CB-ICBedit-1.0

Extension module for iG/iS genset controllers

i-CB

Communication interface for integrated

Engine Control Units with CAN bus

SW version 1.0, October 2003

Prague, Czech Republic

Copyright 2003 ComAp s.r.o.

Written by: Dan Trescak and Ladislav Kadanik

ComAp s.r.o. Svetova 7 , 180 00 Praha 8, Czech RepublicTel: +420-2-6679 0611, Fax: +420-2-6631 6647

WWW: http://www.comap.cz E-mail:[email protected]

i-CB, SW version 1.0, ©ComAp – October 2003 1 i-CB-iCBEdit-1.0.pdf

Table of Contents Table of Contents .................................................................................................................................... 1 i-CB.......................................................................................................................................................... 2

General description ............................................................................................................................. 2 i-CB configuration ........................................................................................................................... 2 IS-CU configuration......................................................................................................................... 2

Terminals and dimensions .................................................................................................................. 3 LED indication................................................................................................................................. 3 i-CB CAN interface.......................................................................................................................... 3 i-CB jumpers ................................................................................................................................... 4

i-CB Wiring .......................................................................................................................................... 4 Wiring example for IS-CU SPtM ..................................................................................................... 5

i-CBEdit.................................................................................................................................................... 6 How to install i-CBEdit ? ................................................................................................................ 6 How to check i-CBEdit version? ..................................................................................................... 6

Open file .............................................................................................................................................. 7 Available database and default configuration................................................................................. 7

I-CB configuration ............................................................................................................................... 7 Editor items ..................................................................................................................................... 8

Object editor ........................................................................................................................................ 9 InteliSys configuration ....................................................................................................................... 10 Default I-CB configuration ................................................................................................................. 11

Analog inputs configuration .......................................................................................................... 11 Analog outputs configuration ........................................................................................................ 12 Binary inputs configuration ........................................................................................................... 12

Technical data ....................................................................................................................................... 13 Power supply ................................................................................................................................ 13 Operating conditions..................................................................................................................... 13 Dimensions and weight................................................................................................................. 13 CAN bus interface......................................................................................................................... 13


i-CB General description i-CB (Communication bridge) is versatile programmable interface unit between InteliSys and Engine Control Unit (ECU) like MTU, Volvo, CAT etc. with CAN bus interface. Selected engine analog values like RPM, Oil pressure etc. and binary values like (Alarm indication) are received from ECU via i-CB. It is not necessary to install and wire external units and corresponding sensors to IS-CU. IS-CU output values like Speed governor output for synchronizing can be transmitted via i-CB (CAN) to ECU. It is not necessary to make external analog wiring. IS-CU data reading: i-CB reads selected Engine data from ECU (via CAN ECU) and transmits data to IS-CU via CAN1 bus. IS-CU data transmitting: iS-CU transmits data (e.g. Speed governor output) to i-CB (via CAN 1) and i-CB transmits these data to ECU via CAN ECU. IS-CU receives data from i-CB (CAN1 messages) like from fictive IS-AIN8 and/or IS-BIN16/8 units. There are two configuration steps:

• i-CB configuration (i-CBEdit), • IS-CU external inputs/outputs (fictive IS-AIN and IS-BIN) configuration (WinEdit).

i-CB configuration i-CB must be configured at first to receive/transmit required data from/to ECU. There is separate object database for each ECU that contains all available communication objects (values). i-CB configuration means object selection from the ECU database: which objects will i-CB receive from ECU and which objects will i-CB transmit to ECU. Each communication object has associated fictive IS-AIN, IS-BIN address and input or output number. i-CBEdit is PC tool for i-CB configuration. i-CB configuration is available via RS232 port. i-CBEdit contains different ECU object databases in XML format. i-CB configuration can be saved as *.icb file. i-CB configuration is downloaded to i-CB via RS232. ICBEdit software for i-CB configuration is included in IG-6.0-IS-3.0 ComAp installation CD.

IS-CU configuration Corresponding fictive IS-AIN and IS-BIN inputs and outputs must be configured in IS-CU to receive and display values from i-CB (and ECU). There is possible to manage all IS-CU Alarm, display and History record possibilities.

i-CBCAN 1 CAN ECU

ECUIS-CU

i-CBEdit

RS23

2

RS23

2

Database-XYZ.XMLConfiguration.ICBWinEdit Configuration. AIS


Terminals and dimensions

95 mm(3,7´´)

43 mm(1,7´´)

96 m

m (3

,8´´)

LB 2

i-CB unit is DIN rail (35mm) mounted

LED indication LED Action Meaning CONTR Dark

Light Blink 0,1s/0,1s

Wrong IS-CU communication IS-CU communication OK IS-CU communication drop-out

EMS Dark Light Blink 0,1s/0,1s

Wrong ECU communication ECU communication OK ECU communication drop-out

RUN Dark Light Blink 0,1s/0,1s Blink 0,3s/0,3s

i-CB initialization Running – OK state Wrong configuration (CRC or format) Active configuration

POWER Light Power supply on

i-CB CAN interface Connector Interface CAN1 IS-CU controller (for Extension units) CAN EMS Engine Control Unit RS485/422 Engine Control Unit (Jumper option) RS232 i-CB configuration


i-CB jumpers

Jumper Meaning CAN1 Terminating resistor 120 Ω CAN EMS Terminating resistor 120 Ω P1 Factory test mode. P2 Not used P3 Not used P4 Not used P5 Not used P10 RS232 / RS 485/422 selection P15 Not used BOOT Boot jumper for software upgrade RESET Processor reset

i-CB Wiring

CAN H

CAN L

EngineControl Unit

120o

hm

IS-CU

CAN HCAN L

CA N L

CA N HCO M

CA N L

CAN HCO M

CAN H

CAN L

i-CB

CAN

1

CAN 1 CAN ECU

CAN

2

ECU

120o

hm

Connect terminating 120 ohm resistors on both CAN bus ends. There are available internal – jumper selectable resistors in i-CB. To operate i-CB: 1. Configure i-CB using i-CBEdit software. i-CB configuration associates selected values (from ECU

database) received from Engine Control Unit to selected CAN addresses to fictive IS-AIN, IS-BIN inputs and outputs.

2. Configure corresponding IS-CU addresses and tick in WinEdit. 3. Configure separate inputs and outputs in corresponding Analog, Binary inputs, outputs in WinEdit.


Wiring example for IS-CU SPtM LO

AD EMERGENCY STOP

REMOTE OFF

GEN C.B. FEED-BACKMAINS C.B. FEED-BACK

DIES

EL/G

AS E

NGIN

EGE

NERA

TOR

G

HORN

+24 V

0 VBI

NA

RY O

UTPU

TS

ALARM

GEN C.B.

Gen

erat

or C

.B.

Mai

ns C

.B.

OILACCESS LOCK

PRESTART

STAR

TER

BATT

ERY

-

+

FUEL SOLENOID

N

BI8

RPM

RPM GND

AI4

AI3

AI2

AI1

COM

AVRi +

GND

VoutR

AVRi -

AO-

AO+

ANAL

OGO

UTPU

T0

- 20

mA

AVR

iSP

EED

GO

VER

NOR

BO8

BO7

BO6

BO5BO4

BO16

BO15

BO14BO13

BO12BO11

BO10BO9BI7

BI6

BI5

BI13

BI4

BI12

BI3

BI2

BI1

N

L1

L1

L2

L2

L3

L3

BI11BI10

BI9

COM

COM

POW

ER8

- 36V

DC

BINA

RY O

UTP

UTS

BINA

RY IN

PUTS

MAI

NS (B

US)

VOLT

AG

E3

x 23

0/40

0 V

GEN

ERAT

OR

VOLT

AG

E3

x 23

0/40

0 V

GE

NER

ATO

RC

UR

RENT

0 - 5

A

COM

CAN 2

COM

CAN 1

BINA

RY IN

PUTS

BIN

ARY

OU

TPU

TS

BOO

T JU

MP

ER

RPM

ANAL

OG

INPU

TS

iS-C

U

Seria

l No.

BI15

BI14

EXT

ENSI

ON

MO

DULE

S

iS, i

G C

ONT

ROLL

ERS

& M

ON

ITO

RIN

G

RS 232 DONGLE

BO3

BO1(START)

BO2(FUEL)

Vout

SHIELD

LSM -

LSM +LO

AD

SHAR

ING

BI16

LHLH

L2l

L3k

L3l

INk

INl

L1k

L1l

L2k

RS-

232C

Inte

rfac

e

Mod

em or

PC

MAINS C.B.

ECU

LB 2

Hint: Check terminating resistors 120 ohm on both ends of CAN1 and CAN ECU. It is possible to use internal i-CB 120 ohm resistors (jumper selectable). If necessary place terminating resistors externally.


i-CBEdit i-CBEdit is Windows 98/NT/2000 based software for i-CB configuration. Hint: Use special ComAp Flash programmer for i-CB firmware upgrade. i-CBEdit is for configuration only.

How to install i-CBEdit ? i-CBEdit 1.0 is a part of IG-6.0-IS-3.0-WE-6.2 installation pack. i-CBEdit is based on Windows 98/NT/2000 or higher platform. Use PC suitable for this platform. No other special requirements are necessary. Default directory is: C:\ …Program Files \ ComAp \ WinEdit \ Tools \ ICBEDIT \ Directory contains separate icb and xml files for different interface.

How to check i-CBEdit version? Use Help – About to display current i-CBEdit version window. See an example:


Open file

This selection opens default configuration (icb) file that corresponds to Engine Control Unit e.g. MTU-MDEC-302. Link to corresponding communication object list (MTU- MDEC database) is automatic.

Available database and default configuration Following table is valid for i-CB release V1.0

ECU database i-CB configuration file ECU type DB_MTU-MDEC-303.XML MTU-MDEC-303.ICB MTU – MDEC 303 DB_MTU-MDEC-302.XML MTU-MDEC-302.ICB MTU – MDEC 302 DB_MTU-MDEC-201.XML MTU-MDEC-201.ICB MTU – MDEC 201

Database contains list of all communication objects (values include dimension and format) that can be received or transferred from/to Engine Control Unit via CAN bus. Each ECU has specific Database. Configuration file is reduced list of communication objects selected from ECU database.

I-CB configuration

I-CB configuration (icb file) contains all objects that are communicated between Engine Control Unit and i-CB. In additional defines fictive (IS-AIN, IS-BIN) units inputs numbers and addresses.


Editor items Signal type Binary

Analog Direction Input

Output Per addr Unit (fictive IS-AIN, IS-BIN)address In/Out number Fictive IS-AIN, IS-BIN input or output number Name Communication object name Dec Set this value in IS-AIN analog input configuration Dim Communication object dimension Factor Value multiplier CAN ID MUX

File read from ICB

File upload to ICB

Add object to configuration – run Object editor

Remove object from configuration

Corresponding InteliSys IS-AIN8 and IS BIN16/8 configuration is as follows (according to the object list example above).

Fictive external unit Input Communication object IS-AIN8 – Address 1 AnlInp 1_1

AnlInp 1_2 …

Engine Speed (ECU) ECU Power Supply voltage …..

IS-BIN16/8 – Address 1 BinInp 1_1 BinInp 1_2 BinInp 1_3 BinInp 1_4 BinInp 1_5 … BinOut 1_2

SS Overspeed (ECU) Combined Alarm Yellow (ECU) Combined Alarm RED (ECU) LO P/Lube Oil SS P/Lube Oil … Alarm reset

Analog output – Address 1

AnlOut 1_1 Speed demand

Note Analog output Speed demand is used to control the engine speed from iS during synchronizing, load sharing etc.


Object editor This window contains all objects available in ECU. Select required objects and set fictive IS-AIN or IS-BIN Periphery address (Per addr.) and Input, Output number.

Screen above selects Input (for i-CB and IS) Analog value P-LubeOil (ECU) from ECU. This value i-CB sends (after configuration) to InteliSys in CAN message like from IS-AIN8 (Address 1, Analog Input 1). This Analog input 1 of Address 1 must be configured in InteliSys (at least V3.0) by WinEdit (at least V 6.2). Objects can be sorted in Analog, Binary, Input, Output, … etc. columns in Object editor.


InteliSys configuration Tick i-CB and select Inputs Outputs addresses of messages from i-CB. Addresses must correspond to i-CB configuration.

It is necessary to modify configuration of Analog inputs (messages) from i-CB:

Name Up to 14 ASCII characters Dimension Set dimension corresponding to ECU database Sensor Set to i-CB analogue Range Not necessary to set Decimals Available to set Active Available to set Alarm type Available to set Block type Available to set Function Available to set


Default I-CB configuration Default I-CB archive Corresponding InteliSys archive MTU-MDEC-201.icb MTU-MDEC-302.icb MTU-MDEC-303.icb

SPtM-Plus-3.0-MDEC.ais

Default SPtM-Plus-3.0-MDEC.ais archive contains following modules configuration

Analog inputs configuration Following tables were exported from SPtM-Plus-3.0-MDEC.ais Order Module Name Dimension Sensor Range Decimals Active Alarm type Block type Function 1. CU PrimWater temp °C VDO Temp iS-CU 65535 0 Over Wrn+Sd RunOnly Group1 2. CU SecWater temp °C VDO Temp iS-CU 65535 0 Over Wrn+Sd RunOnly Group1 3. CU Oil temp °C VDO Temp iS-CU 65535 0 Over Wrn+Sd RunOnly Group1 4. CU Oil press bar VDO Pres iS-CU 65535 1 Under Wrn+Sd RunOnly Group1 1. Group1 Engine speed RPM i-CB analogue 65535 0 Over None AllTheTime RPM Pick-up2. Group1 ECU supply V V i-CB analogue 65535 1 Over None AllTheTime 3. Group1 AnlInp 1_3 - None 65535 0 Over None AllTheTime 4. Group1 AnlInp 1_4 - None 65535 0 Over None AllTheTime 5. Group1 AnlInp 1_5 - None 65535 0 Over None AllTheTime 6. Group1 AnlInp 1_6 - None 65535 0 Over None AllTheTime 7. Group1 AnlInp 1_7 - None 65535 0 Over None AllTheTime 8. Group1 AnlInp 1_8 - None 65535 0 Over None AllTheTime 1. Group2 P lube oil bar i-CB analogue 65535 2 Over None AllTheTime 2. Group2 P charge air bar i-CB analogue 65535 2 Over None AllTheTime 3. Group2 AnlInp 2_3 - None 65535 0 Over None AllTheTime 4. Group2 AnlInp 2_4 - None 65535 0 Over None AllTheTime 5. Group2 AnlInp 2_5 - None 65535 0 Over None AllTheTime 6. Group2 AnlInp 2_6 - None 65535 0 Over None AllTheTime 7. Group2 AnlInp 2_7 - None 65535 0 Over None AllTheTime 8. Group2 AnlInp 2_8 - None 65535 0 Over None AllTheTime 1. Group3 T coolant °C i-CB analogue 65535 1 Over None AllTheTime 2. Group3 T charge air °C i-CB analogue 65535 1 Over None AllTheTime 3. Group3 T intercooler °C i-CB analogue 65535 1 Over None AllTheTime 4. Group3 T lube oil °C i-CB analogue 65535 1 Over None AllTheTime 5. Group3 T fuel °C i-CB analogue 65535 1 Over None AllTheTime


6. Group3 AnlInp 3_6 - None 65535 0 Over None AllTheTime 7. Group3 AnlInp 3_7 - None 65535 0 Over None AllTheTime

Analog outputs configuration Order Module Value Low limit High limit Function 1. CU Act power 0 200 Act power 1. Group1 SpdRegOut -10 10 SpdRegOut2. Group1 -32767 32767 3. Group1 -32767 32767 4. Group1 -32767 32767 5. Group1 -32767 32767 6. Group1 -32767 32767 7. Group1 -32767 32767 8. Group1 -32767 32767

Binary inputs configuration 1. Group1 Overspd ECU Closed Shutdown AllTheTime 2. Group1 Yellow alarm Closed Warning AllTheTime 3. Group1 Red alarm Closed Shutdown AllTheTime 4. Group1 P lube oil wrn Closed Warning RunOnly Group15. Group1 P lube oil sd Closed Shutdown RunOnly Group16. Group1 BinInp 1.6 Closed No protection AllTheTime 7. Group1 BinInp 1.7 Closed No protection AllTheTime 8. Group1 BinInp 1.8 Closed No protection AllTheTime 1. Group2 Coolant level Closed Warning AllTheTime 2. Group2 ECU fail Closed Warning AllTheTime 3. Group2 BinInp 2.3 Closed No protection AllTheTime 4. Group2 BinInp 2.4 Closed No protection AllTheTime 5. Group2 Coolant T wrn Closed Warning RunOnly Group16. Group2 Coolant T sd Closed Shutdown RunOnly Group17. Group2 T Charg air Closed Warning RunOnly Group18. Group2 T lube oil wrn Closed Warning RunOnly Group11. Group3 T lube oil sd Closed Shutdown RunOnly Group12. Group3 BinInp 3.2 Closed No protection AllTheTime 3. Group3 BinInp 3.3 Closed No protection AllTheTime 4. Group3 BinInp 3.4 Closed No protection AllTheTime 5. Group3 BinInp 3.5 Closed No protection AllTheTime 6. Group3 BinInp 3.6 Closed No protection AllTheTime 7. Group3 BinInp 3.7 Closed No protection AllTheTime 8. Group3 BinInp 3.8 Closed No protection AllTheTime


Technical data

Power supply Voltage input 8-36V DC Consumption 0.1A depend on power supply

Operating conditions Operating temperature -20 ÷ +70 °C Storage temperature -30 ÷ +80 °C Humidity 85% without condensation Protection IP20 Standard conformity

Dimensions and weight Dimensions 95x96x43 mm, DIN rail (35 mm) mounted Weight 250g ????

CAN bus interface Galvanic separated Maximal CAN bus length 200m Speed 250kBd Nominal impedance 120Ω Cable type for iS connection twisted pair (shielded)

I-CB-ICBedit-1.0

Documents

Transcript of I-CB-ICBedit-1.0