Inteli Communication Guide 06 2008

User Manual:

Open the PDF directly: View PDF .
Page Count: 107

Download
Open PDF In Browser	View PDF

InteliCommunication Guide for ComAp Controllers

InteliGen/InteliSys-NT
IL-NT
InteliDrive
See also the InteliCommunicationGuide-February 05 document to find
the communication possibilities of InteliSys and InteliGen – the classic line

June 2008

COMMUNICATION
GUIDE

Written by Ladislav Kadaník, Martin Málek
Copyright © 2008 ComAp s.r.o.
ComAp, spol. s r.o.
Kundratka 2359/17, 180 00 Praha 8, Czech Republic
Tel: +420 246 012 111 , Fax: +420 266 316 647
E-mail: info@comap.cz, www.comap.cz

Table of Contents
Table of Contents ...............................................................................................................................................2
General Information............................................................................................................................................7
Communication between Controller and Peripherals, between Controllers ..................................................7
Communication between Controller(s) and Superior, Service or Monitoring System (Usually PC) ..............7
How to Use Different Character Sets.............................................................................................................8
Available character sets.............................................................................................................................8
How to change character sets in InteliDrive, InteliLite-NT, IC-NT .............................................................8
How to change character sets in IG/IS-NT ................................................................................................8
Controllers Communication Capabilities ............................................................................................................9
IG-NT, IG-EE..................................................................................................................................................9
IG-NTC, IG-EEC ..........................................................................................................................................10
IS-NT ............................................................................................................................................................11
IL-NT ............................................................................................................................................................11
ID-DCU.........................................................................................................................................................12
IC-NT-MINT..................................................................................................................................................13
IC-NT-SPTM.................................................................................................................................................14
Local Connection – RS232...............................................................................................................................15
Controllers................................................................................................................................................15
Controller setup........................................................................................................................................15
Equipment................................................................................................................................................15
Available software for IG/IS-NT ...............................................................................................................15
Available software for IL-NT ....................................................................................................................15
Available software for IC-NT....................................................................................................................15
Available software for ID..........................................................................................................................15
PC Software features (GenConfig, InteliMonitor, LiteEdit) ......................................................................16
PC Software features (DriveConfig, DriveMonitor)..................................................................................16
Connection speed ....................................................................................................................................16
RS232 cable ............................................................................................................................................16
Local Connection for Multiple Applications ..................................................................................................16
IG/IS-NT CAN bus connection.................................................................................................................16
ID-DCU CAN bus connection ..................................................................................................................17
I-CR Module for CAN Bus Extension ...........................................................................................................18
I-CR module functions: ............................................................................................................................18
I-CR configuration jumpers: .....................................................................................................................18
I-CR indication and diagnostic LEDs: ......................................................................................................18
CAN bus terminating 120 ohms resistors availability ..............................................................................19
Local Connection – USB ..................................................................................................................................20
Controllers................................................................................................................................................20
Equipment................................................................................................................................................20
Available software for IG/IS-NT ...............................................................................................................20
PC Software features (GenConfig, InteliMonitor) ....................................................................................20
Connection speed ....................................................................................................................................20
USB cable ................................................................................................................................................21
Remote Connection..........................................................................................................................................22
Controllers................................................................................................................................................23
Equipment................................................................................................................................................23
Available software for IG/IS-NT ...............................................................................................................23
Available software for IL-NT ....................................................................................................................23
Available software for IC-NT....................................................................................................................23
Available software for ID..........................................................................................................................23
PC Software features (GenConfig, InteliMonitor, LiteEdit) ......................................................................23
PC Software features (DriveConfig, DriveMonitor)..................................................................................24
Connection speed ....................................................................................................................................24
Modem Connection ..........................................................................................................................................25
Controllers................................................................................................................................................25
Controller setup........................................................................................................................................25
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

2

Equipment................................................................................................................................................25
Available software for IG/IS-NT ...............................................................................................................26
Available software for IL-NT ....................................................................................................................26
Available software for IC-NT....................................................................................................................26
Available software for ID..........................................................................................................................26
PC Software features (GenConfig, InteliMonitor, LiteEdit) ......................................................................26
PC Software features (DriveConfig, DriveMonitor)..................................................................................26
Connection speed ....................................................................................................................................26
Data Transfer Rates.....................................................................................................................................26
Using Local Bridge I-LB ...............................................................................................................................27
Important setpoint in the controller ..........................................................................................................27
Combined Communication - Remote and Modem.......................................................................................28
Option1: ...................................................................................................................................................28
Option2: ...................................................................................................................................................28
Combined Communication – I-LB with Maximum Configuration .................................................................29
Jumper selection tree ..............................................................................................................................29
Available combinations of I-LB modules..................................................................................................30
Addresses of Modules on CAN2 (IG/IS-NT, ID, IC-NT)...........................................................................31
Two Modem Types Connection ...................................................................................................................33
GSM Modem Configuration..........................................................................................................................33
General conditions ...................................................................................................................................33
Modem configuration ...............................................................................................................................33
Controller configuration............................................................................................................................34
Internet Ethernet Connection ...........................................................................................................................35
Controllers................................................................................................................................................35
Equipment................................................................................................................................................35
Available software for IG/IS-NT ...............................................................................................................35
Available software for ID..........................................................................................................................35
Available software for IL-NT ....................................................................................................................36
Available software for IC-NT....................................................................................................................36
PC Software features (LiteEdit) ...............................................................................................................36
PC Software features (GenConfig, InteliMonitor) ....................................................................................36
PC Software features (DriveConfig, DriveMonitor)..................................................................................36
Connection speed ....................................................................................................................................36
Connection from PC.................................................................................................................................36
One controller - RS232 connection..........................................................................................................37
Two controllers – CAN / Ethernet connection..........................................................................................37
Max four PCs can be connected to one iG-IB at once ............................................................................38
Internet Dialup Connection ...............................................................................................................................39
Controllers................................................................................................................................................39
Equipment................................................................................................................................................39
Available software for IG/IS-NT ...............................................................................................................39
Available software for ID..........................................................................................................................39
Available software for IL-NT ....................................................................................................................39
Available software for IC-NT....................................................................................................................39
PC Software features (GenConfig, InteliMonitor) ....................................................................................40
PC Software features (DriveConfig, DriveMonitor)..................................................................................40
Dialup Connection........................................................................................................................................40
One controller - RS232 ............................................................................................................................40
More controllers - CAN ............................................................................................................................40
Active Call.........................................................................................................................................................41
Controllers................................................................................................................................................41
Equipment................................................................................................................................................41
Available software for IG/IS-NT ...............................................................................................................41
Available software for ID..........................................................................................................................41
Function ...................................................................................................................................................41
Controller setting......................................................................................................................................41
Terminal attempt order for active call – ID...............................................................................................41
Terminal attempt order for active call in IG/IS-NT ...................................................................................41
Active SMS .......................................................................................................................................................42
Controllers................................................................................................................................................42
Equipment................................................................................................................................................42
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

3

Function ...................................................................................................................................................42
Controller setting......................................................................................................................................42
Terminal attempt order for SMS active call – ID......................................................................................42
Terminal attempt order for SMS active call – IG/IS-NT ...........................................................................42
Example ...................................................................................................................................................42
Active E-mail (SMS E-mail) ..............................................................................................................................43
Controllers................................................................................................................................................43
Equipment................................................................................................................................................43
Function ...................................................................................................................................................43
Controller setting......................................................................................................................................43
Terminal attempt order for SMS active call - ID.......................................................................................43
Terminal attempt order for SMS e-mail active call – IG/IS-NT ................................................................43
Sample of active e-mail (from controller) .................................................................................................44
Active call – EML-SMS ............................................................................................................................44
SMS Message Control......................................................................................................................................46
Controllers................................................................................................................................................46
Equipment................................................................................................................................................46
Features...................................................................................................................................................46
SMS message format ..............................................................................................................................46
SMS message header .............................................................................................................................46
SMS message commands.......................................................................................................................47
Terminal Connection ........................................................................................................................................51
Controllers................................................................................................................................................51
Equipment................................................................................................................................................51
Function ...................................................................................................................................................51
Modbus Connection..........................................................................................................................................52
Protocol support.......................................................................................................................................52
Protocol implemented ..............................................................................................................................52
Important Setpoints in Controller..................................................................................................................52
Modbus communication via I-LB..............................................................................................................53
Modbus Protocol Description............................................................................................................................54
Introduction ..............................................................................................................................................54
Data reading ............................................................................................................................................54
Data writing ..............................................................................................................................................55
Check field calculation .............................................................................................................................57
Data types................................................................................................................................................57
Access to dedicated communication objects of the controller.................................................................59
List of communication objects..................................................................................................................59
Communication Status .................................................................................................................................60
Controller Address .......................................................................................................................................61
Communication Protocol ..............................................................................................................................61
Write Password Setting................................................................................................................................61
Write Password Change ..............................................................................................................................61
Write Password Changing Level 1 ...............................................................................................................62
Write Password Changing Level 2 ...............................................................................................................62
Write Password Changing Level 3 ...............................................................................................................62
User Identification Number...........................................................................................................................62
Change User Alias .......................................................................................................................................63
Read Alias of One User ...............................................................................................................................63
Read Alias of All Users ................................................................................................................................63
User Administration......................................................................................................................................63
Access Attributes of All Users ......................................................................................................................64
Access Attributes of One User .....................................................................................................................64
Last Error of the Modbus Communication ...................................................................................................65
Current Time ................................................................................................................................................65
Current Date.................................................................................................................................................65
Action - Command .......................................................................................................................................65
Controller Serial Number..............................................................................................................................66
Alarm List .....................................................................................................................................................67
Remote Communication Access Code Setting ............................................................................................67
Remote Communication Access Code Changing........................................................................................67
Active Call Termination ................................................................................................................................67
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

4

Controller Identification String ......................................................................................................................68
Values Multipack ..........................................................................................................................................68
ECU Diagnostic Codes List..........................................................................................................................68
Error list....................................................................................................................................................69
How to Create Actual Communication Object List .......................................................................................70
Register Oriented Modbus in IG/IS-NT/ID, IL-NT, IC-NT (not available for IG, IS) .....................................70
Data addressing in IG/IS-NT....................................................................................................................70
Application values and setpoints .............................................................................................................70
Dedicated communication objects ...........................................................................................................72
Data reading ............................................................................................................................................73
Data writing ..............................................................................................................................................73
Alarm list reading .....................................................................................................................................73
History reading.........................................................................................................................................74
List of commands, see Start command ...................................................................................................74
Modbus Communication Examples..................................................................................................................76
Battery Voltage Reading ..............................................................................................................................76
Binary Inputs Reading..................................................................................................................................76
Alarm List Reading (only for IL-NT, IC-NT, ID, IG,IS – not for IG/IS-NT) ....................................................77
Engine State Reading ..................................................................................................................................77
Setpoint Adjusting ........................................................................................................................................77
Set Gear teeth to 126 ..............................................................................................................................77
Reading access attributes of all users from IGS-NT ...............................................................................78
Gen-set commands..................................................................................................................................79
IG/IS-NT Register Oriented Modbus Communication Examples.................................................................79
Values reading .........................................................................................................................................79
Adjusting setpoints...................................................................................................................................80
Start command, see List of commands ...................................................................................................80
Alarm list reading .....................................................................................................................................81
History reading.........................................................................................................................................81
Set and reset of RemoteControl1 binary output ......................................................................................81
Setting of Pulse Counter to 1,000,000,000 (IS-NT only) .........................................................................82
Setting of External Value to 400 (IS-NT only)..........................................................................................82
I-LB, IG-IB Communication Units .....................................................................................................................83
Local Bridge I-LB..........................................................................................................................................83
Modem support ........................................................................................................................................83
I-LB Terminals and jumpers....................................................................................................................83
IG-IB Internet Bridge ....................................................................................................................................84
Indication and Diagnostic LED’s ..................................................................................................................84
IG-IB Configuration ......................................................................................................................................85
Ethernet LAN Configuration .........................................................................................................................86
IG-IB connection to internet (Ethernet) ....................................................................................................87
Dialup Connection Configuration .................................................................................................................88
Connection to ISP ....................................................................................................................................88
Modem initialization .................................................................................................................................88
Active e-mail ............................................................................................................................................89
IG-IB Interface ..............................................................................................................................................90
IG-IB Dongle ............................................................................................................................................90
Internet Connection Diagnostics ..................................................................................................................90
How to Access IG-IB behind Firewall...........................................................................................................91
Modem Recommendations...............................................................................................................................92
Analog Modem with DC Supply ...................................................................................................................92
Recommended ISDN Modem ......................................................................................................................92
Recommended CDMA Modem ....................................................................................................................92
Recommended GSM Modems.....................................................................................................................92
GSM modem wiring notes - InteliDrive ....................................................................................................92
GSM modem wiring notes – IG/IS-NT .....................................................................................................93
GSM Modem setup ..................................................................................................................................93
Mobile Phone SIM Card Setting...................................................................................................................94
How to check SIM card DATA setting......................................................................................................94
Converters ........................................................................................................................................................95
Converter RS232 ↔ RS485.........................................................................................................................95
Recommended converters.......................................................................................................................95
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

5

Converter 230 V AC ↔ TCP/IP....................................................................................................................95
Recommended converter ........................................................................................................................95
Example ...................................................................................................................................................96
Converter USB ↔ RS232 ............................................................................................................................96
Recommended converters.......................................................................................................................96
Converter USB ↔ RS485 ............................................................................................................................96
Recommended converter ........................................................................................................................96
Converter Modbus RTU ↔ TCP ..................................................................................................................97
Converter RS-422/485 ↔ Ethernet..............................................................................................................97
Recommended converter ........................................................................................................................97
Recommended settings ...........................................................................................................................97
Isolator RS232 .............................................................................................................................................98
Recommneded isolators ..........................................................................................................................98
Radio link......................................................................................................................................................98
Recommended equipment.......................................................................................................................99
Converter Modbus RTU ↔ SNMP ...............................................................................................................99
MIB Table...............................................................................................................................................100
Converter settings..................................................................................................................................101
Controller settings ..................................................................................................................................101
Converter Modbus RTU ↔ Profibus ..........................................................................................................101
Converter settings..................................................................................................................................102
Controller settings ..................................................................................................................................107

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

6

General Information
Communication is a very wide topic. From the ComAp control systems user point of view we have to
distinguish at least following levels of communication:

Communication between Controller and Peripherals, between
Controllers
Communication between the controller and its peripherals (such as IGS-PTM, IS-AIN8…) is described in the
controller User guides.
Communication between controllers for multiple applications is also described in the User guide.
Communication between controllers and ECUs is described in Engines with ECU&Comap controllers.pdf.
For IG/IS-NT:
IGS-NT-MINT-x.y.pdf
IGS-NT-Application guide-x.y.pdf
Communication features of InteliLite-NT controllers refer in
IL-NT-AMF-x.y-Reference Guide.pdf
IL-NT-MRS-x.y-Reference Guide.pdf
IL-NT-MRS3,4-AMF8,9-x.y-Reference Guide.pdf
LiteEdit-x.y-Reference Guide.pdf
x.y stands for controller firmware version
Communication features of the classic line controllers – InteliSys and InteliGen can be found in the
InteliCommunicationGuide-February05.pdf document.

Communication between Controller(s) and Superior, Service or
Monitoring System (Usually PC)
Communication between controller(s) and superior, service or monitoring system (usually PC) is described in
this Communication guide.
There are following types of communication between controller(s) and superior system:
- Local Connection
- Remote Connection
- Modem Connection
- Internet Ethernet Connection
- Internet Dial-up Connection
- Active Call
- Active SMS
- Active e-mail
- Terminal connection
There is following communication option available for the user SW designers and third party software:
- Modbus Connection

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

7

How to Use Different Character Sets
Available character sets
Character set

IL-NT

IC-NT

ID

IG-EE
IG-NT

IG-EE
GC
IG-NT
GC

IGDISPLAY

IGDISPLAY
GC

ISDISPLAY

IVDISPLAY*

Standard
character set
+ West
European
languages +
East
European
languages
(incl. Turkish,
Russian)
Support of
graphical
X
X
#
languages
e.g. Chinese
#
Only Chinese available (in ID can be switched to other character set)
*IV-DISPLAY (InteliVision) is the new generation display unit for ComAp InteliGen NT / InteliSys NT (IGSNT) or InteliDrive (ID) controllers. More information about IV-DISPLAY you can find in InteliVision Reference
Guide.

How to change character sets in InteliDrive, InteliLite-NT, IC-NT
InteliDrive/InteliLite-NT supports all character sets mentioned in the table above so there is no need of
special software or hardware. It is only necessary to create an appropriate dictionary in DriveConfig/LiteEdit
and download it into the controller. Then the language can be selected from the controller front panel.
Consult DriveConfig/ LiteEdit and InteliDrive/InteliLite-NT Reference Guides for details.

How to change character sets in IG/IS-NT
The controllers without Graphical Characters option support all mentioned character sets without any
software or hardware modifications. It is only necessary to create an appropriate dictionary and download it
into the controller. Then it is possible to change language from the controller front panel. See GenConfig and
controller User manuals for details.
For support of graphical languages (e.g. Chinese, Japanese, Korean) it is necessary to order a “GC”
modification of the controller. The way of adding the language is then the same as for standard controllers.
IS-Display originally supports graphical character sets so there is no “GC” modification available.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

8

Controllers Communication Capabilities
IG-NT, IG-EE
The following diagram shows communication capabilities of IG-NT/IG-EE controller in full configuration.
IV-DISPLAY (InteliVision) is the new generation display unit for ComAp InteliGen NT / InteliSys NT (IGS-NT)
or InteliDrive (ID) controllers. More information about IV-DISPLAY you can find in InteliVision Reference
Guide. See pictures below:

Hint:
Used CAN addresses for modules connected to CAN2 you can see in Addresses of Modules on CAN2
(IG/IS-NT, ID) chapter.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

9

IG-NTC, IG-EEC
The following diagram shows communication capabilities of IG-NTC/IG-EEC controller in full configuration.

Hint:
Used CAN addresses for modules connected to CAN2 you can see in Addresses of Modules on CAN2
(IG/IS-NT, ID) chapter.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

10

IS-NT
The following diagram shows communication capabilities of IS-NT controller in full configuration.

IL-NT
The following diagram shows communication capabilities of IL-NT controller in full configuration.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

11

ID-DCU

Hint:
Used CAN addresses for modules connected to CAN2 you can see in Addresses of Modules on CAN2
(IG/IS-NT, ID) chapter.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

12

IC-NT-MINT
The following diagram shows communication capabilities of IC-NT-MINT controller in full configuration.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

13

IC-NT-SPTM
The following diagram shows communication capabilities of IC-NT-SPTM controller in full configuration.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

14

Local Connection – RS232
RS232
PC

Controllers
Controllers

IG-NT/
IG-EE
YES

IG-NTC/
IS-NT
IG-EEC
Connection applicable
YES
YES
RS232(1), RS232(1),
Available ports
RS232(1)
RS232(2) RS232(2)
* Available as option (IL-NT-RS232 module)

IL-NT

IC-NT

ID-DCU

YES

YES

YES

RS232*

RS232*

RS232

Controller setup
(Basic settings/Comms settings group)
Controllers
ComAp
protocol
Modbus
protocol

IG-NT/IG-EE/
IG-NTC/IG-EEC/IS-NT
RS232(1,2) mode =
DIRECT
RS232(1,2) mode =
MODBUS-DIRECT

IL-NT

IC

ID-DCU

COM1 Mode =
STANDARD
COM1 Mode =
STANDARD

COM1 Mode =
STANDARD
COM1 Mode =
STANDARD

RS232 mode =
STANDARD
RS232 mode =
MODBUS

Equipment
Controller side
Connection
PC side

Equipment needed
RS232 cable up to 10m
PC with RS232

Available software for IG/IS-NT
Software
Applicable

GenConfig
YES

InteliMonitor
YES

WinScope
YES

Third party SW
YES (MODBUS)

Available software for IL-NT
Software
Applicable

LiteEdit
YES

WinScope
YES

Third party SW
YES (MODBUS)

Available software for IC-NT
Software
Applicable

LiteEdit
YES

WinScope
YES

Third party SW
YES (MODBUS)

DriveMonitor
YES

WinScope
YES

Available software for ID
Software
Applicable

DriveConfig
YES

Third party SW
YES (MODBUS)

For software descriptions see appropriate manuals – GenConfig-x.y.pdf, InteliMonitor-x.y.pdf, DriveConfigx.y.pdf, DriveMonitor-x.y.pdf, LiteEdit-x.y.pdf.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

15

Read history

Firmware
programming

X
X
-

X
X
X

X
X
-

X
X
-

Values time
trends

Read Gen-set
values

X
X
-

Archive files
upload/download

Controller
configuration

GenConfig
InteliMonitor
LiteEdit
WinScope

On-line
Gen-set control

PC Software features (GenConfig, InteliMonitor, LiteEdit)

X
X
-

X

On-line
Engine
control

Controller
configuration

Read Engine
values

Read history

Firmware
programming

Archive files
upload/downl
oad

PC Software features (DriveConfig, DriveMonitor)

X

X
-

X

X

X
-

X
-

DriveConfig
DriveMonitor

Connection speed
Connection speed

IL-NT
Up to 38400 bps

IC
Up to 38400 bps

ID
Up to 38400 bps

IG/IS-NT
Up to 57600 bps

RS232 cable
It is recommended to use standard Null-modem cable for local connection between controller and PC,
although the three wires (TxD, RxD, GND) RS 232 connection is enough for direct controller to PC
communication:
Controller connector
D-SUB9 female
2 ------------------------3 ------------------------5 -------------------------

PC RS 232 connector
D-SUB9 female
3 TxD
2 RxD
5 GND

Local Connection for Multiple Applications
IG/IS-NT CAN bus connection
•
•

For communication with a group of IG/IS-NT controllers connect the controllers via CAN bus (CAN2)
and connect I-LB unit to this CAN bus.
CAN bus terminals on IG/IS-NT are active all the time, not depend on Dongle.

Hint:
The IG-MU module can be used to cover most of the I-LB functionality but with slower performance.
Otherwise the I-LB module is also compatible with the classic line controllers InteliSys and InteliGen but the
installation package IGS-ClassicLine-Install-6.2 must be installed (available since March 2007).

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

16

There are two separate CAN bus lines on the controller. One for connection between controllers (CAN2), the
second one (CAN1) is for external IGS-PTM, IS-AIN8, IS-BIN8/16 or IGL-RA15 modules or ECU connection.
CAN bus length is limited to 200 meters for Comms settings:CAN bus mode = 32C or to 900 meters for
Comms settings:CAN bus mode = 8C.

ID-DCU CAN bus connection
A special module ID-COM has to be used for InteliDrive to connect to other controllers. ID-COM provides
connector for intercontroller CAN bus (CAN2) and for extension modules (CAN1).

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

17

I-CR Module for CAN Bus Extension
If the distance between units is too high to fit into the 200 m limit (or 900 m for 8 controllers), CAN repeater
module (I-CR) can be used to extend it.
Typical case – in line extension:
total bus length up to 400 m – 32C mode
I-CR
A CAN B
total segment length up to 200 m

IG-NT
(1)

IG-NT
(2)

total segment length up to 200 m

IG-NT
(x)

IGNT(x+1

IG-NT
(32)

Connection of I-LB, combination of different CAN bus speeds:
I-CR
A CAN B
total segment length up to 200 m

IG-NT
(1)

IG-NT
(x)

total segment length up to 900 m

I-LB

IM (8)

This connection allows PC communication to all controllers in the system (e.g. via InteliMonitor), including a
distant InteliMains unit.

I-CR module functions:
-

Intercontroller CAN bus extension (one or more I-CR modules can be used).
Intercontroller CAN bus bus-tie bridging – makes groups of controllers in segments A and B “invisible”
one for another depending on bus-tie breaker state, keeping the PC communication (I-LB, IG-IB) in
function for all controllers.
Peripheral CAN bus extension

I-CR configuration jumpers:
P2 – Forces 250 kbps mode (32C) on CAN A, otherwise speed autodetection is used.
P3 – Forces 250 kbps mode (32C) on CAN B, otherwise speed autodetection is used.
P4 – Activates Filter mode (bus-tie bridging).
P5 – Forces alternate controller address 3 for bus-tie status reading (default controller address is 4).
P10 – If “H” network configuration used (two I-CR units), it must be switched to RS-422 mode.

I-CR indication and diagnostic LEDs:

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

18

LED
RUN

State
Lights
Flashes
Lights
Flashes

DET-A
DET-B

Lights
Flashes

CAN-A (TxC, RxC)
CAN-B (TxC, RxC)
COM (TxD, RxD)

Flashes
Flashes
Flashes

Function
Firmware is OK and running
Firmware corrupted (periodic Watchdog reset)
CAN A communication is running
CAN A communication speed autodetection is in progress (I-CR
automatically enters this mode if no CAN message received for 2 s)
CAN B communication is running
CAN B communication speed autodetection is in progress (I-CR
automatically enters this mode if no CAN message received for 2 s)
CAN A interface activity
CAN B interface activity
RS232/422 interface activity

For more detailed information about I-CR, see the Application sheet “Extending the CAN bus” or IGS-NTx.y-Installation guide.pdf..

CAN bus terminating 120 ohms resistors availability
Following communication or extension modules connected to the CAN bus have internal 120 ohm
terminating resistor that can be connected by jumper setting.
Module

120 ohm resistor
jumper

I-LB
IG-IB
ID-COM
IS-AIN8
IS-BIN16/8
IGS-PTM
IGL-RA15
I-CB
I-CR

on CAN, RS485
No
on CAN2
No
No
Yes
No
Yes
Yes

Hint:
In the case of surge hazard (connection out of building in case of storm etc.) see the “Recommended
CAN/RS485 connection” chapter of the IGS-NT-2.2-Installation guide.pdf.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

19

Local Connection – USB
USB
PC

Controllers
Controllers

IG-NT/ IG-NTC/
IG-EE
IG-EEC
Connection applicable
YES
Available ports
USB
* Available as option (IL-NT-S-USB module)

IS-NT

IL-NT

IC-NT

ID-DCU

YES
USB

YES
USB*

YES
USB*

-

Equipment
Controller side
Connection
PC side

Equipment needed
USB cable A-B
USB port

Available software for IG/IS-NT
Software
Applicable

GenConfig
YES

InteliMonitor
YES

WinScope
YES

Third party SW
YES

X
X

X
-

X
-

Values time
trends

Firmware
programming

X
-

Archive files
upload/download

Read history

X
-

Read Genset
values

GenConfig
InteliMonitor
WinScope

Controller
configuration

On-line Genset
control

PC Software features (GenConfig, InteliMonitor)

X
-

X

Connection speed
Up to 115 200 bps

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

20

USB cable
Use standard USB A-B cable (distance up to 5 meters).

! IMPORTANT !
To use USB connection it is necessary to install drivers on your PC.
The drivers can be downloaded from the website http://www.ftdichip.com/Drivers/VCP.htm.
Download the driver for your operating system and follow the enclosed instructions.
After successful installation of the driver and connection of the controller or I-LB+ to the PC the new Virtual
Communications Port appears in ComAp PC tools and it is possible to open connection via USB.
CAUTION!
Use shielded USB cable only!

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

21

Remote Connection

RS485 communication line has to be terminated by 120 ohms resistors on both ends. Follow RS485
converter user manual.
I-LB has integrated this resistor – use “485- 120Ω” jumper.
Multiple controllers wiring with RS485, see Modbus connection chapter.
I-LB unit must be switched to RS485 mode for remote direct connection by “DIRECT/MODEM” and “RS485”
jumper.
Hint:
When ADAM module is used then connect Rx, Tx-A to DATA+ and Rx, Tx-B to DATA-. Shielding connect to
ADAM GND on both sides and external 120ohm resistor between DATA+ and DATA- on ADAM side (in off
state). Internal ADAM 4520 switches: set Data format 10 bit and baud rate, see table.
Cable must not be crossed (RxD-TxD) RS232 for connection between ADAM and PC SUB9 RS232
connector wiring: 2 – 2, 3 – 3, 5 – 5, 7 – 7.
In the case of surge hazard (connection out of building in case of storm etc.), see the “Recommended
CAN/RS485 connection” chapter of the IGS-NT-2.2-Installation guide.pdf.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

22

Controllers
Controllers

IG-NT/
IG-EE
YES

IG-NTC/
IS-NT
IL-NT
IC-NT
IG-EEC
Connection applicable
YES
YES
YES
YES
Available ports
RS485(1) RS232(1)* RS232*
RS232
RS485(1)
RS485(2) RS485(2) RS485** RS485
* with external converter only (for IL-NT IL-NT-RS232 module needed)
** with IL-NT-RS232-RS485 or IL-NT-ETH-485 modules (not available yet)

ID-DCU
YES
RS232*

Equipment
Controller side
Connection
PC side

Equipment needed
- or Converter to RS485 or I-LB unit
Twisted pair
Converter to RS485

Available software for IG/IS-NT
Software
Applicable

GenConfig
YES

InteliMonitor
YES

WinScope
YES

Third party SW
YES (MODBUS)

Available software for IL-NT
Software
Applicable

LiteEdit
YES

WinScope
YES

Third party SW
YES (MODBUS)

Available software for IC-NT
Software
Applicable

LiteEdit
YES

WinScope
YES

Third party SW
YES (MODBUS)

DriveMonitor
YES

WinScope
YES

Available software for ID
Software
Applicable

DriveConfig
YES

Third party SW
YES (MODBUS)

X
X
X

X
X
-

X
X
-

Values time
trends

Firmware
programming

X
X
-

Archive files
upload/download

Read history

X
X
-

Read Genset
values

GenConfig
InteliMonitor
LiteEdit
WinScope

Controller
configuration

On-line Genset
control

PC Software features (GenConfig, InteliMonitor, LiteEdit)

X
X
-

X

Hint:
It is possible to use WinScope with I-LB local connection, i.e. I-LB connected to multiple controllers via CAN
bus and via RS232/RS485/USB to PC.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

23

Controller
configuration

Read Engine
values

Read history

Firmware
programming

Archive files
upload/downl
oad

DriveConfig
DriveMonitor

On-line
Engine
control

PC Software features (DriveConfig, DriveMonitor)

X

X
-

X

X

X
-

X
-

Connection speed
Connection speed

IL-NT
Up to 38400 bps

IC
Up to 38400 bps

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

ID
Up to 38400 bps

IG/IS-NT
Up to 57600 bps

24

Modem Connection

Hint:
Usage of Analog and GSM modems (generally different modem types) is not recommended due to possible
incompatibility.

Controllers
Controllers
Connection applicable
Available ports

IG-NT/
IG-EE
YES
RS232(1)

IG-NTC/
IG-EEC
YES
RS232(1),
RS232(2)

IS-NT

IL-NT

IC

ID-DCU

YES
RS232(1),
RS232(2)

YES

YES

YES

RS232*

RS232*

RS232

* Available as option (IL-NT-RS232 module)

Controller setup
(Basic settings/Comms settings group)
Controllers
ComAp
protocol
Modbus
protocol

IG-NT/IG-EE/
IG-NTC/IG-EEC/IS-NT
RS232(1,2) mode =
MODEM (HW) / MODEM (SW)
RS232(1,2) mode = MODBUSMDM(HW)

IL-NT

IC

ID-DCU

COM1 Mode =
MODEM
Not available

COM1 Mode =
MODEM
Not available

RS232 mode =
STANDARD
RS232 mode =
MODBUS

Equipment
Controller side
Connection
PC side

Equipment needed
Analog, ISDN or GSM modem
Phone line or GSM
Analog, ISDN or GSM modem

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

25

Available software for IG/IS-NT
Software
Applicable

GenConfig
YES

InteliMonitor
YES

Third party SW
YES (MODBUS)

Available software for IL-NT
Software
Applicable

LiteEdit
YES

Third party SW
NO

Available software for IC-NT
Software
Applicable

LiteEdit
YES

Third party SW
NO

Available software for ID
Software
Applicable

DriveConfig
YES

DriveMonitor
YES

Third party SW
YES (MODBUS)

Controller
configuration

Read Genset
values

Read history

Firmware
programming

Archive files
upload/downl
oad

GenConfig
InteliMonitor
LiteEdit

On-line
Genset
control

PC Software features (GenConfig, InteliMonitor, LiteEdit)

X
X

X
X

X
X

X
X

X*
X*

X
X

Archive files
upload/downl
oad

Firmware
programming

Read history

Read Engine
values

Controller
configuration

On-line
Engine
control

PC Software features (DriveConfig, DriveMonitor)

DriveConfig
X
X*
X
DriveMonitor
X
X
X
*Possible, but not recommended due to risk of crash of programming if the communication is lost.

Connection speed
(limited by modem used)
Connection speed

IL-NT
Up to 38400 bps

IC-NT
Up to 38400 bps

ID
Up to 38400 bps

IG/IS-NT
Up to 57600 bps

Data Transfer Rates
Real data transfer rate is limited by the lowest rate in connection, mostly it is limited by Link rate.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

26

Following table gives examples of data transfer rates. These values can differ case to case and depend on
real link conditions and modem type. Data transfer rate was increased from DDE server version 2.9.

Analog modem
GSM modem

Controller
Terminal rate
Bits per second
19200
9600

Real link rate*
Bytes per second
300 up to 1900
80 up to 900

PC
Terminal rate
Bits per second
Depends on PC
configuration

Hint:
* Real link rate is visible in DDE server window.

Using Local Bridge I-LB
I-LB has to be connected to modem via standard modem cable (full RS232) where the DSR (Data Set
Ready) signal detects modem presence (when MODEM (HW) type selected). Three-wire RS232 cable (TxD,
RxD, GND) can be used (e.g. for GSM modems) when MODEM (SW) type selected.

Hint:
The IG-MU module can be used to cover most of the I-LB functionality but with slower performance.
Otherwise the I-LB module is also compatible with the classic line controllers InteliSys and InteliGen but the
installation package IGS-ClassicLine-Install-6.2 must be installed (available since March 2007).

Important setpoint in the controller
Comms settings: Contr addr [ 1 to 32 ]
Controller identification number. Each gen-set in the group has to have its own unique number. Default value
is 1.
Hint:
When opening Direct or Modem connection to single controller , the Controller address has to correspond to
PC SW communication setup setting.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

27

Combined Communication - Remote and Modem
Option1:

Option2:

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

28

Combined Communication – I-LB with Maximum Configuration
There are more separate internal channels for NT controller connection which can operate at once (all via
CAN2):
- Local connection 1 (I-LB local address 1)
- Local connection 2 (I-LB local address 2)
- Modem connection 1 (I-LB modem address 1)
- Modem connection 2 (I-LB modem address 2)
It is necessary to select which connection type(s) a particular I-LB is using. In I-LB+ version, there is
additional USB slave port, which can be used as a local connection only, together with RS232-modem
connection. See Available combinations of I-LB modules table below.

Jumper selection tree
ComAp / ModBus – selects between ComAp PC tools (InteliMonitor, WinScope, ...) and third party PC SW
for monitoring:
-

ComAp
o Direct / Modem – selects between direct connection (via RS232 or RS485) and modem
connection type
ƒ DIRECT
• RS232 / RS485 – selection of serial communication type
• ADR1 / ADR2 – selection between two available local communication
channels; if I-LB+ is used, the USB communication automatically occupies
the other channel
ƒ MODEM
• HW / SW control – selection between modems with full interface
• ADR1 / ADR2 – selection between two available modem communication
channels; IG/IS-NT controllers only, in ID the secondary modem channel not
available
• Setting RS232 / RS485 jumper to RS232 position is obligatory

-

ModBus (not available at USB port of I-LB+, USB port always works in ComAp mode)
o

Direct / Modem – selects between direct connection (via RS232 or RS485) and modem
connection type
ƒ DIRECT
• RS232 / RS485 – selection of serial communication type

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

29

•

o

ADR1 / ADR2 – selection between two available local communication
channels; if I-LB+ is used, the USB communication automatically occupies
the other channel
ƒ MODEM
• ADR1 / ADR2 – selection between two available modem communication
channels; IG/IS-NT controllers only, in ID the secondary modem channel not
available
• Setting HW / SW control has no influence; a modem with HW control is
always expected in this mode
ModBus Rate (9600 / 19200 / 38400 / 57600 bps) – selects the communication speed when
ModBus protocol is selected, no matter if in Direct or Modem mode

Default jumper setting:
P1
CAN 120R
P2
RS485 120R
P3
1-2 RS232 / 2-3 RS485
P13 Modbus rate
P14 Modbus rate
P15 HW/SW control
P16 Comap/Modbus
P17 ADR1/ADR2
P18 Direct/Modem

Opened
Opened
1-2 (active RS232)
Opened
Opened (=9600 bps)
Opened (HW control)
Opened (Comap protocol)
Opened (ADR1)
Opened (Direct)

Available combinations of I-LB modules
There are four of communication channels available on the CAN2 link at the same time. See the connection
possibilities in the table below:
I-LB/I-LB+
module

DIRECT/
MODEM
jumper

ADR1/
ADR2
jumper

channel 1
(local con. 1)

channel 2
(local con. 2)

channel 3
(modem con. 1)

channel 4 (*)
(modem con. 2)

Connection possibilities of only I-LB or I-LB+ in following eight examples
1.
2.
3.
4.
5.
6.
7.
8.

I-LB
I-LB
I-LB
I-LB
I-LB+
I-LB+
I-LB+
I-LB+

DIRECT
DIRECT
MODEM
MODEM
DIRECT
DIRECT
MODEM
MODEM

ADR1
ADR2
ADR1
ADR2
ADR1
ADR2
ADR1
ADR2

RS232/485
RS232/485
USB
USB

RS232/485
USB
RS232/485
USB
-

RS232-modem
RS232-modem
-

RS232-modem
RS232-modem

Connection possibilities of both I-LB+ (**) or I-LB and I-LB+ couple in following four examples
I-LB
DIRECT
ADR1
RS232/485
I-LB+ MODEM
ADR1
USB
RS232-modem
I-LB
MODEM
ADR1
RS232-modem
10.
I-LB+
DIRECT
ADR1
RS232/485
USB
I-LB
MODEM
ADR1
RS232-modem
11.
I-LB+ MODEM
ADR2
USB
I-LB+ MODEM
ADR1
USB
RS232-modem
12.
I-LB+ MODEM
ADR2
USB
(*) – available for IG/IS-NT and IC-NT controllers only, not for ID, IG, IS, IL-NT
(**) – there can be max. two of I-LB+ on the CAN2 link.
9.

RS232-modem
RS232-modem

Hint:
The IG-MU module can be used to cover most of the I-LB functionality but with slower performance.
Otherwise the I-LB module is also compatible with the classic line controllers InteliSys and InteliGen but the
installation package IGS-ClassicLine-Install-6.2 must be installed (available since March 2007).

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

30

IG / IS - NT 1

CAN

I-LB
Modem
address 1

Modem
or
GSM
modem

Modem
or
GSM
modem

PC 1

CAN

I-LB
Modem
address 2

Modem
or
GSM
modem

Modem
or
GSM
modem

PC 2

CAN

I-LB
Local
address 1

RS232 / 485

CAN

I-LB
Local
address 2

RS232 / 485

CAN 2

IG / IS - NT 2

IG / IS - NT 32

PC 3

PC 4

Addresses of Modules on CAN2 (IG/IS-NT, ID, IC-NT)
Following CAN addresses are used for modules connected to CAN2 (intercontroller CAN bus). There cannot
be more modules using the same address connected at the same time.
Addresses can be changed using jumpers, configuration program or from the display - refer to the
corresponding chapter or reference guide for detailed description.

*IV-DISPLAY (InteliVision) is the new generation display unit for ComAp InteliGen NT / InteliSys NT (IGSNT) or InteliDrive (ID) controllers. More information about IV-DISPLAY you can find in InteliVision Reference
Guide.
Hint:
Please note that USB port is using its CAN address only if an external device is connected to the USB port of
I-LB+. Make sure that other device (e.g. IG-IB) is not using the same CAN address as USB port of an I-LB+,
because using USB port could interrupt CAN communication.
Hint:
Please note that adresses 1 and 2 (123, 124) are exchanged in versions IBConfig ≤ 1.5
and IBConfig ≥ 1.6 (see the table above).
IG-MU
Address 1 => CAN-address 124
Address 2 => CAN-address 123
When switched to modem mode it uses CAN-address 125.
I-LB Direct connection
Address 1 => CAN-address 124
Address 2 => CAN-address 123
I-LB Modem connection
Address 1 => CAN-address 125
Address 2 => CAN-address 122
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

31

I-LB+ when USB terminal is connected
Address 1 => CAN-address 123
Address 2 => CAN-address 124
IG-IB
Address 1 => CAN-address 124
Address 2 => CAN-address 123
Hint:
These addresses are valid for IBConfig ≥ 1.6.
IV-DISPLAY
Address 1 => CAN-address 124
Address 2 => CAN-address 123
I-RD-CAN
Address 1 => CAN-address 124
Address 2 => CAN-address 123
Example 1:

Example 2:

Hint:
In these examples IBConfig ≥ 1.6 is used for programming IG-IB.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

32

Example 3: Wrong connection – conflict of addresses:

Hint:
In this example IBConfig ≥ 1.6 is used for programming IG-IB.

Two Modem Types Connection
It is possible to connect two modems (e.g. Analog and GSM) to one controller at once to have two
independent modem channels for DATA and GSM messages.
One modem is connected via I-LB – CAN bus, the second is connected directly to RS 232 controller
interface.
When an active call is activated in the controller, the modem connected directly to the controller tries to
call/send an SMS. If this is not successful, the Active call fail alarm appears. The second modem doesn’t
then try to substitute the first one.

CAN

I-LB

CAN 2

Analog
or ISDN
modem

Analog
or ISDN
modem

PC 1

IG / IS - NT
RS232
GSM
modem

GSM
modem

PC 2

GSM Modem Configuration
General conditions
Following conditions must be fulfilled:
1. There must be GSM modem on PC and controller side (not different modem types e.g. analog and
GSM modem).
2. Data communication capability must be enabled for the SIM cards. Ask your operator for this service.
If it is not enabled, Gm_setup program which is part of controller installation package shows
“Command failure” message at the end of the log.

Modem configuration
1. Connect to the modem from your PC.
2. Run Gm_setup.exe (the program is in ../Tools/Gm_setup directory).
3. Select communication port (COM 1 - 32) and press Setup.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

33

4. Enter the SIM card PIN after you are be asked.
5. Enter SMS center address after you will be asked (ask your operator for this number).
6. If the Gm_setup writes “Setup terminated successfully” the SIM card is configured for the
communication with the controller.

Controller configuration
1. In Act.calls/SMS group of setpoints set:
ENABLED to desired type of active call depending on what level of alarm should activate the
call/SMS sending (this setting is not important if you don't want to use InteliMonitor/DriveMonitor in
Active call mode (waiting for the active call from the controller) or sending SMS in case of an alarm)
Acall-CHX-Type – choose type of active call (see a controller manual for more information)
Acall-CHX-Addr - phone number of the SIM card in the modem connected to your PC (where the
controller should call) or your email address
2. Connect the controller to the modem or I-LB that has the modem connected.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

34

Internet Ethernet Connection

Controllers
Controllers
Connection applicable
Available ports

IG-NT/
IG-EE
YES
CAN2*

IG-NTC/
IG-EEC
YES
CAN2*

IS-NT

IL-NT

IC-NT

ID-DCU

YES
CAN2*

YES
RS232**

YES
RS232/
CAN2***

YES
CAN2*

* To connect IG-IB.
** To connect IG-IB or use optional IL-NT-ETH-485 module (not available yet)
*** Used connection depends on the type of your application (MINT, SPtM, etc). For more details see
InteliCompact-NT-1.0-Reference Guide.

Equipment
Controller side
Connection
PC side

Equipment needed
InternetBridge (IG-IB) unit configured for Ethernet
connection (Ethernet connection firmware);
Internet connection with “visible” IG-IB
Ethernet
Internet connection

Available software for IG/IS-NT
Software
Applicable
* on request

GenConfig
YES

InteliMonitor
YES

InteliSupervisor
YES*

Third party SW
NO

Available software for ID
Software
Applicable

DriveConfig
YES

DriveMonitor
YES

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

Third party SW
NO

35

Available software for IL-NT
Software
Applicable

InteliMonitor
YES

LiteEdit
YES

Third party SW
NO

Available software for IC-NT
Software
Applicable

InteliMonitor
YES

LiteEdit
YES

Third party SW
NO

Read history

X

X

X

X*

Archive files
upload/downl
oad

Read Genset
values

X

Firmware
programming

Controller
configuration

LiteEdit

On-line
Genset
control

PC Software features (LiteEdit)

X

On-line
Genset
control

Controller
configuration

Read Genset
values

Read history

Firmware
programming

Archive files
upload/downl
oad

PC Software features (GenConfig, InteliMonitor)

X

X
-

X

X

X*
-

X
-

GenConfig
InteliMonitor

Archive files
upload/downl
oad

Firmware
programming

Read history

Read Engine
values

Controller
configuration

On-line
Engine
control

PC Software features (DriveConfig, DriveMonitor)

DriveConfig
X
X*
X
DriveMonitor
X
X
X
* Possible, but not recommended due to risk of crash of programming if the communication is lost.

Connection speed
Up to 3000 Bps
Hint:
IG-IB communication is typically faster than modem:
- when IG-IB is connected to controller via CAN and LAN - 3000 Bps
- when IG-IB is connected to controller via RS232 and LAN - 1200 Bps
- when IG-IB is connected to controller via CAN and Internet - ~500 Bps
- when IG-IB is connected to controller via RS232 and Internet - ~500 Bps (depends on the internet
line throughput).

Connection from PC
For connection from PC see the manual of the PC program (InteliMonitor, DriveMonitor, etc.).
Open the Open/Select connection window and set:
• Internet type of connection
• Controller address
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

36

•
•

Access code
IG-IB IP address

Note that IP address you set can be different from the IP address of iG-IB (when the iG-IB IP address is not
public). It depends on gateway setting:
IG- IB IP address

IP address
set in PC SW

Gateway IP address

IG-IB

GATEWAY

Internet

GATEWAY

PC
SW

COMPANY ETHERNET

One controller - RS232 connection
In this case no dongle is necessary.
One unit could be also connected via CAN interface.

INTERNET

ETHERNET

LED

iG-IB

IG-CU
DONGLE

1 2
MODEM
IB CONFIG

LED

3 4

RS232

5 6

CAN

Ix-NT

LED

POWER

Two controllers – CAN / Ethernet connection
The dongle must be used. The type of IG-IB dongle limits number of accessible controllers (up to 32).
Dongles for up to 3, 7, 15 and 32 controllers are available. See also IG-IB Dongle

INTERNET

ETHERNET
1 2

LED

3 4

DONGLE

iG-IB

IG-CU
DONGLE

Ix-NT
MODEM
IB CONFIG

LED

5 6

CAN

CAN2

LED

POWER

Ix-NT
CAN2

CAN BUS

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

37

Max four PCs can be connected to one iG-IB at once
Ix-NT

CAN2

IG-IB

IP=X.X.X.A

PC
PC

INTERNET

PC
PC

Ix-NT

Ix-NT

CAN2

IG-IB

IP=X.X.X.A

INTERNET

PC

max. 8x
Ix-NT

IG-IB IP=X.X.X.B

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

38

Internet Dialup Connection

Controllers
Controllers
Connection applicable
Available ports
* To connect IG-IB.

IG-NT/IG-EE
YES
CAN2*

IG-NTC/IG-EEC
YES
CAN2*

IS-NT IL-NT
YES
YES
CAN2* RS232*

IC-NT
YES
RS232*

ID-DCU
YES
CAN2*

Equipment
Controller side
Connection
PC side

Equipment needed
InternetBridge (IG-IB) unit configured for Dialup
connection (Dialup firmware); Dialup internet
connection
Ethernet
Internet connection

Available software for IG/IS-NT
Software
Applicable
* on request

GenConfig
YES

InteliMonitor
YES

InteliSupervisor
YES*

Third party SW
NO

Available software for ID
Software
Applicable

DriveConfig
YES

DriveMonitor
YES

Third party SW
NO

Available software for IL-NT
Software
Applicable

InteliMonitor
YES

LiteEdit
YES

Third party SW
NO

Available software for IC-NT
Software
Applicable

InteliMonitor
YES

LiteEdit
YES

Third party SW
NO

Hint:
For IC-NT setpoint COMx mode in Basic Settings group must be set to “MODEM” (see InteliCompact-NT1.0-Reference Guide).
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

39

Controller
configuration

Read Genset
values

Read history

Firmware
programming

Archive files
upload/downl
oad

GenConfig
InteliMonitor

On-line
Genset
control

PC Software features (GenConfig, InteliMonitor)

X

X
-

X

X

X*
-

X
-

Archive files
upload/downl
oad

Firmware
programming

Read history

Read Engine
values

Controller
configuration

On-line
Engine
control

PC Software features (DriveConfig, DriveMonitor)

DriveConfig
X
X*
X
DriveMonitor
X
X
X
* Possible, but not recommended due to risk of crash of programming if the communication is lost.

Dialup Connection
One controller - RS232
ETHERNET

RS232

LED

iG-IB

IG-CU
DONGLE

MODEM

1 2

MODEM
IB CONFIG

LED

3 4

CAN bus

IG/IS-NT
5 6

CAN

LED

POWER

More controllers - CAN
ETHERNET

RS232

LED

iGIB

3 4

DONGLE

IG/IS-NT
IG-CU
DONGLE

MODEM

1 2

MODEM
IB CONFIG

LED

5 6

CAN

POWER

LED

IG/IS-NT

CAN BUS

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

40

Active Call
Controllers
Controllers
Connection applicable

IG-NT/IG-EE
YES

IG-NTC/IG-EEC
YES

IS-NT
YES

IL-NT
NO

IC-NT
NO

ID-CU
YES

Equipment
Same as for Modem connection.

Available software for IG/IS-NT
Software
Applicable

GenConfig
NO

InteliMonitor
YES

Third party SW
YES

DriveMonitor
YES

Third party SW
YES

Available software for ID
Software
Applicable

DriveConfig
NO

Function
When active calls are activated for alarms on site (warning, shut-down…) the controller calls to the
preselected telephone number and sends the ANT, AID archive file.
Software (e.g. InteliMonitor) on the PC side must be running and waiting for active call.

Controller setting
For this type of active call set Act. calls/SMS: AcallCH1(-3)-Type = DATA, Act. calls/SMS: AcallCH1(-3)Addr = telephone number.

Terminal attempt order for active call – ID
1)
2)
3)
4)

Analog / ISDN modem connected to RS232
Analog / ISDN modem connected to I-LB
GSM modem connected to RS232
GSM modem connected to I-LB

Terminal attempt order for active call in IG/IS-NT
1) Analog/GSM/ISDN/CDMA modem connected to RS232(1)
2) Analog/GSM/ISDN/CDMA modem connected to RS232(2)*
3) Analog/GSM/ISDN/CDMA modem connected to I-LB (modem address 1)
4) Analog/GSM/ISDN/CDMA modem connected to I-LB (modem address 2)
* Available only in IG-NTC/EEC and IS-NT.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

41

Active SMS
Controllers
Controllers
Connection applicable

IG-NT/IG-EE
YES

IG-NTC/IG-EEC
YES

IS-NT
YES

IL-NT
YES

IC-NT
YES

ID-CU
YES

Equipment
side
Connection
PC side

Equipment needed
GSM Modem or I-LB + GSM Modem
GSM
GSM Mobile Phone

Function
When SMS active calls are activated for alarms on site (warning, shut-down…) the controller sends SMS
message to the predefined GSM number.

Controller setting
For this type of active call set:
Act. Calls/SMS: AcallCH1(-3)-Type = SMS
Act. calls/SMS: AcallCH1(-3)-Addr = mobil phone number
Hint:
For IL-NT controllers set:
Act Calls/SMS: Type Channel 1(2) = DISABLE/SMS/E-MAIL
Act Calls/SMS: TelNo/Addr Ch1(2) = mobil phone number

Terminal attempt order for SMS active call – ID
1) GSM modem connected to RS232
2) GSM modem connected to I-LB via CAN

Terminal attempt order for SMS active call – IG/IS-NT
1) GSM / CDMA modem connected to RS232(1)
2) GSM / CDMA modem connected to RS232(2)*
3) GSM / CDMA modem connected to I-LB (modem address 1)
4) GSM / CDMA modem connected to I-LB (modem address 2)
* Available only in IG-NTC/EEC and IS-NT.

Example
SMS in format
#Gen-set name:AL=(Wrn PrimWater temp, !Emergency stop)
is sent in case that the primary water temperature exceeded the warning limit and Emergency stop input has
been deactivated.
Hint:
For IG/IS-NT FW version 1.1 and lower and for ID controllers, character ASCII codes lower than $20 and
higher than $7F are prohibited to appear in an SMS body. If they appear, the SMS sending may be blocked
by GSM modem. I.e. those character codes are not allowed in gen-set name and all messages that can
appear in an active SMS.
In IG/IS-NT FW version 2.0 and higher, these characters are replaced by character “_”.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

42

Active E-mail (SMS E-mail)
Controllers
Controllers
IG-NT/IG-EE IG-NTC/IG-EEC IS-NT IL-NT
Connection applicable
YES
YES
YES
YES*
* Available with IG-IB or optional module IL-NT-ETH-485 (not available yet)

IC-NT
YES*

ID-CU
YES

Equipment
Controller side
Connection
PC side

Equipment needed
InternetBridge (IG-IB) unit configured for Ethernet connection
or Dialup connection
Internet
e-mail message box (GSM mobile phone for SMS e-mail)

Function
When active e-mails are activated for alarms on site (warning, shut-down…) the controller sends e-mail
message to the predefined e-mail address.

Controller setting
For this type of active call set:
Act. calls/SMS: AcallCH1(-3)-Type = E-MAIL
Act. calls/SMS: AcallCH1(-3)-Addr = email address
Hint:
For IL-NT controllers set:
Act Calls/SMS: Type Channel 1(2) = DISABLE/SMS/E-MAIL
Act Calls/SMS: TelNo/Addr Ch1(2) = mobil phone number

Terminal attempt order for SMS active call - ID
1)
2)
3)
4)
5)
6)

IG-IB connected to RS232 and internet connection currently active 1
IG-IB connected via CAN (address 2) and internet connection currently active 1
IG-IB connected via CAN (address 1) and internet connection currently active 1
IG-IB connected to RS232 and internet connection currently inactive 2
IG-IB connected via CAN (address 2) and internet connection currently inactive 2
IG-IB connected via CAN (address 1) and internet connection currently inactive 2

Terminal attempt order for SMS e-mail active call – IG/IS-NT
1)
2)
3)
4)
5)
6)
7)
8)

IG-IB connected to RS232(1) and internet connection currently active1
IG-IB connected to CAN (address 2) and internet connection currently active1
IG-IB connected to CAN (adderss 1) and internet connection currently active1
IG-IB connected to RS232(2) and internet connection currently active1
IG-IB connected to RS232(1) and internet connection currently inactive2
IG-IB connected to CAN (address 2) and internet connection currently inactive2
IG-IB connected to CAN (adderss 1) and internet connection currently inactive2
IG-IB connected to RS232(2) and internet connection currently inactive2

1–

For IG-IB connected to Internet via leased line – always active;
For IG-IB connected to Internet using dial-up connection – active only when IG-IB is connected to Internet
provider.
2–
Only for dial-up connection – when IG-IB is not connected to Internet provider.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

43

Sample of active e-mail (from controller)
Example of active E-mail for Ethernet - LAN connection
iG-IB
----------------------------------------------IP address:
192.168.1.10
Connection:
Ethernet LAN
Controller
----------------------------------------------Name:
InteliSys
Serial number: 06F20093
SW branch:
Standard
SW version:
2.7
Application:
SPtM
Appl. version: 2.7
Time:
15:21:06
Date:
13/06/03
Alarm list
----------------------------------------------!Sd SD 11
History events
----------------------------------------------0 13/06/03 15:21:05 NotReady
-1 13/06/03 15:21:02 Sd SD 11
-2 13/06/03 15:20:56 Running
-3 13/06/03 15:20:46 Started
-4 13/06/03 15:20:44 Start
-5 13/06/03 15:20:40 Ready
-6 13/06/03 15:17:18 Passw3 entered
-7 13/06/03 14:58:37 NotReady
-8 13/06/03 14:58:37 PickupFault
-9 13/06/03 14:58:37 Ready
-10 13/06/03 14:58:33 Stop
-11 13/06/03 14:58:03 Cooling
-12 13/06/03 14:58:03 RemControlUART
-13 13/06/03 14:52:11 Running
-14 13/06/03 14:52:01 Started
-15 13/06/03 14:51:59 Start
-16 13/06/03 14:51:59 RemControlUART
-17 13/06/03 14:37:27 Ready
-18 13/06/03 14:37:21 Switched On
-19 11/06/03 12:29:47 Ready
Example of active E-mail for Dialup connection
iG-IB
----------------------------------------------IP address:
192.168.1.10
Connection:
Dialup (until 10:52:05)
… the rest of message is the same as in Ethernet LAN connection example above.
Hint:
IG-IB does not respond e-mails which are sent to iG-IB mailbox.

Active call – EML-SMS
You should set Setpoints Act.cals/SMS:AcallCHx-Type = EML-SMS and specify the e-mail address of a
mobile phone if you want to send active messages from controller using SMS e-mail.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

44

The Active call – EML-SMS service informs the user of mobile phone about current items in the Alarm list.
Example of active EML-SMS
IS_ABC: B:AL=(Sd Water Temp,Wrn Water Temp,!Emerg Stop,ActCallCH1Fail)
Hint:
EML-SMS channel setting depends on local GSM provider.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

45

SMS Message Control

GSM
modem

RS 232

You can control and setup the Genset using SMS messages from your mobile phone.

Controllers
Controllers
Connection applicable

IG-NT/IG-EE IG-NTC/IG-EEC
YES
YES

IS-NT
YES

IL-NT
NO

IC-NT
NO

ID-CU
YES

Equipment
Controller side
Connection
PC side

Equipment needed
GSM Modem or I-LB + GSM Modem
GSM
GSM Mobile Phone

Controller
configuration

Read Genset
values

Read history

Firmware
programming

Archive files
upload/downl
oad

Available

On-line
Genset
control

Features

YES

YES

YES

NO

NO

NO

SMS message format
SMS message format:
• Start with # character, followed controller address, followed colon character and access code,
• Commands are comma separated,
• Commands are not case sensitive,
• Maximum message length is limited up to 160 characters,
• Controller or I-LB answers only message with valid Access code,
• Answer exceeds 160 characters is separated to more messages.

SMS message header
Every SMS must start with header in format:
#address:access command1, command2
where address
access
#
:

is controller address 1 to 32
is valid access code set-up by PC SW (up to 15 characters length),
character indicates beginning of message,
character separates controller address and access code

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

46

Hint:
For direct communication to one controller is possible skip address setting.

SMS message commands
1. Controller address
Controller address is unique controller identification number located in setpoint group Basic setting
: Contr addr [1 to 32].
Syntax:
Example:

#XX
XX … controller address [1 to 32]
#5
Message is addressed to controller with address 5.

2. Access code
InteliGen / InteliSys Access code is 15 characters length string. Access code is separated from
controller address by column.
Syntax:
Example:

#5:X
X … controller access code up to 15 characters length
#5:accesscode
Message is addressed to controller with address 5 and its access code is set to
value ‘accesscode’.

3. Read value or setpoint
Command for reading of selected value or setpoint. Return value is in appropriate numerical or string
format.
Syntax:

Example:

r XXXX (or rXXXX)
r
… command
XXXX… value or setpoint code
#5:accesscode r 8252
Reading of setpoint 8252 (8252 = Gear teeth)

Hint:
Access code can’t contain space character. Access code can be changed in InteliMonitor only.
4. Adjust setpoint
Command for adjusting of selected setpoint. Answer message contains only confirmation of
successful adjusting or appropriate error.
Syntax:

Example:
Return code:

w XXXX YYYY (or wXXXX YYYY)
w
… command
XXXX… setpoint code
YYYY… value of setpoint in appropriate format
#5:accesscode w 8252 144
Adjusting of setpoint 8252 to value 144 (8252 = Gear teeth).
ok
w_err
er_pass
er_old

…
…
…
…

adjusting setpoint was correct
adjusting setpoint was not successful
adjusting setpoint required that valid password was entered
command for adjusting was read out from SMS during GSM
modem initialization – in this case command will not be served.

5. Enter password
Password setting command. Password has to be set before adjusting of protected setpoint or calling
protected gen-set control command. Setting password command is not necessary before every
adjusting. Password is a number in range 0 to 65535 and is valid for all rest of SMS.
Syntax:

p PPPP (or pPPPP)

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

47

Example:
Return code:

p
… command
PPPP… password
#5:accesscode p 1234, w 8252 144
Setting password before adjusting protected setpoint.
ok
er_pass …

…
setting password was successful
setting password is not valid

6. Gen-set control
SMS command for invoking gen-set control command as Start, Stop, Fault reset etc.
Syntax:
c Y (or cY)
c
… command
Y
… type of operation
Y Type of operation
1
Start
2
Stop
3
Horn Reset
4
Fault Reset
5
GCB ON
6
GCB OFF

Example:

Y Type of operation
7
MCB ON
8
MCB OFF
9
GCB ON/OFF
10
MCB ON/OFF
11
Next Mode
12
Previous Mode

#5:accesscode p 1234, c1
This SMS command invokes genset Start. Password setting is needed in case of
password protection was configured for genset commands.

Return code:

ok
er_pass
c?
c_er

…
…
…
…

er_old

…

genset command was accepted
valid password was not set before executing the command
unknown genset command
gen-set command execution is not allowed in actual state (e.g.
attempt to start the genset in OFF mode).
command was read out from SMS during GSM modem
initialization – in this case command will not be served.

7. Read Alarm list
Read actual Alarm list.
Syntax:
Example:

a
a
… command
#5:accesscode a
Request of actual Alarm list.

Return code:

AL=(items of alarm list) … comma separated items of Alarm list.
Exclamation mark in front of Alarm list item indicates inverse record (still active
alarm).

Note:

1. Answer message contains at most eight items of Alarm list.
2. Alarm list is not separated to more messages.

8. Time delay
Insert time delay before serving next part of SMS command.
Syntax:

Example:

d T
d
… command
T
… time delay in sec (in range 1 to 600)
#5:accesscode d 10
Request 10 sec delay before serving next SMS command.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

48

Return code:

d_ok
d_over

…
…

time delay was successful performed
requested time delay is out of range (1 to 600 sec)

Note:

Any other SMS messages are not served during time delay!

9. Remote switches (IG/IS-NT only)
Set or reset RemoteControl1-8 output.
Syntax:

Example:
Return code:

s 1/0
s
… command
1/0 … set/reset
#5:accesscode p0, s1 1
Enters password p0 and sets RemoteControl1 output.
p_OK,s_OK

10. ExtValues (IG/IS-NT only)
Enters value to ExtValue.
Syntax:

Example:
Return code:

e xxx
e
… command
xxx … value
#5:accesscode p0, e1 50
Enters password p0 and sets ExtValue1 = 50.
p_OK,e_OK

11. Help (IG/IS-NT only)
Request for list of supported SMS command.
Syntax:
Example:
Return code:
Note:

?
#5:accesscode ?
?=(p passwd,r comm_obj,w com_obj val,c cmd_num,d sec,a,sx y,ex y,?)…...
..... list of supported SMS commands
Return code is not separated to more message.

12. Answer message
Answer message start with # character followed by Gen-set name. Colon separates this header form
return codes of SMS commands. Answer message is generated during serving of received message
and is sent in case that 160 characters or end of received message are achieved. Answer message
is sent to the originator phone number. Tree dots at the end of message indicate separation and next
following message.
Example:

#5:accesscode r8252,w8252 100,r8252
answer message
#Gen-setname: 144,ok,100

13. Examples of SMS commands
Here is following several examples of SMS messages addresses to controller IG/IS-NT with address
5, named ‘Gen-set name’. Access code in this controller is set to ‘accesscode’ and password is
‘1234’. In examples are used setpoints and values 8276 – Nomin.power, 10123 – RPM, 8315 –
Controller Mode, 8235 – binary inputs, 8296 – Gen > f.
Example 1 – reading value
SMS:
#5:accesscode r8276
Answer:
#Gen-set name:100
Example 2 – adjusting setpoint
SMS:
#5:accesscode p 1234, r8276,w8276
110,r8276

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

read value 8276

read value 8276,
write 110,
read value 8276

49

Answer:

#Gen-set name:ok,100,ok,110

Password was accepted,
read value of 8276 is 100,
writing to 8276 was ok,
new value of 8276 is 110
Password was not accepted,
read value of 8276 is 100
writing to 8276 was not successful
read value of 8276 is still 100

If wrong password sent: #Gen-set
name:p_er,100, w_pass, 100

Example 3 – Gen-set control and delay time
SMS:
#5:accesscode
r8276,c1,d30,r10123
Answer:

#Gen-set name:110,ok,d_ok,1499

Example 4 – adjusting special setpoint
SMS:
#5:accesscode r8315,w8315
0,r8315
Answer:

#Gen-set name:MAN,ok,OFF

read value 8276,
invoke gen-set command START,
delay 30 sec,
read value 10123
read value of 8276 is 110,
Gen-set command START was
accepted,
confirm delay command,
read value of 10123 is 1499

read value 8315,
write 0 (index of stringlist type),
read value 8315
read value of 8315 as string,
writing was ok,
read new value of 8315 as string

Hint:
Setpoints Stringlist type (e.g. Controller Mode) is read as string and adjusted as index of string item
in string list. e.g. Controller Mode:
Read value
[as string]
OFF
MAN
SEM
AUT
TEST

Write value [as
index]
0
1
2
3
4

Example 5 – reading and writing other type
SMS:
#5:accesscode r8235,w8296
110.2

read value 8235,
write 110.2 with decimal
point

Answer:

#Gen-set name:OIIIOOIIO,ok

read value of 8235 (binary
value),
writing was ok

Note:

1. Writing of binary setpoint is not supported.
2. Writing of setpoint with decimal point is automatically converted to appropriate
number of decimal places.

Example 6 – reading actual Alarm list
SMS:
#5:accesscode a
Answer:
#Gen-set name:AL=(!Wrn
PrimWater temp, !Wrn SecWater temp,
Batt volt)

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

read actual Alarm list
Actual Alarm list contains
three items.

50

Terminal Connection
pcANYWHERETM

IG/IS-NT
ID, IL

Modem
or
Internet

PC

InteliMonitor
DriveMonitor
LiteEdit

pcANYWHERETM
Modem
or
Internet

PC

Controllers
Controllers
Connection applicable

IG-NT/IG-EE
YES

IG-NTC/IG-EEC
YES

IS-NT
YES

IL-NT
YES

IC-NT
YES

ID-CU
YES

Equipment
Controller side
Connection
PC side

Equipment needed
Local connection + PC terminal software running
(e.g. pcANYWHERE™) + InteliMonitor installed +
modem
Phone line / internet
Modem + terminal SW

Function
This way you can remotely handle local PC and remotely start InteliMonitor or other software on local
computer and make remote software upgrade or other procedures.
See website Symantec Enterprise Solutions

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

51

Modbus Connection
Modbus protocol was implemented into the controllers to enable the customer to design its own supervision
software.

Protocol support
MODBUS supported in

IG-NT/
IG-NTC/
IS-NT
IG-EE
IG-EEC
Connection applicable
YES
YES
YES
(*) Not available for IL-NT-MRS3,4 and IL-NT-AMF8,9

IL-NT

IC-NT

ID-CU

I-LB

IG-IB

YES*

YES

YES

YES

NO

Protocol implemented
The protocol is described in chapter Modbus protocol description.

Important Setpoints in Controller
IL-NT controllers:
Basic settings: COM1 Mode [ COMAP , Modbus ]
Communication protocol switch between Standard (LiteEdit) communication protocol and controller Modbus
protocol.
InteliDrive controllers:
Basic settings: RS232 mode [ Standard , Modbus ]
Communication protocol switch between Standard (DriveMonitor) communication protocol and controller
Modbus protocol.
Basic settings: MODBUS [ 9600 , 19200 , 38400 ] bps
Selection of Modbus communication speed.
Hint:
For LiteEdit/DriveMonitor communication adjust RS232 mode = Standard.
IG/IS-NT controllers:
Comms settings:RS232(1) mode = [ MODBUS-MDM(HW), MODBUS-DIRECT ]
Comms settings:RS232(2) mode = [ MODBUS-MDM(HW), MODBUS-DIRECT ] (when RS232(2) port
available)
Comms settings:RS232(1)MBCSpd = [ 9600 , 19200 , 38400 , 57600 ] bps
Comms settings:RS232(2)MBCSpd = [ 9600 , 19200 , 38400 , 57600 ] bps
Selection of Modbus communication speed.
There are three possibilities of Modbus connection to single controller : direct via RS232, RS485 or via
Modem.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

52

Hint:
The RS232/RS485 converter is included in the IG-NTC, IG-EEC and IS-NT controllers (no external
RS232/RS485 converter is needed).

RS485 communication line has to be terminated by 120 ohms resistors at both ends – follow converter user
manual.
RS485 communication can be used for more controller monitoring and controlling via InteliMonitor.

Modbus communication via I-LB
To use I-LB Modbus communication connect Modbus jumper in I-LB unit. Additionally, you can choose the
communication speed using the speed selection jumpers. Their combination allows the speed selection of
9600 / 19200 / 38400 / 57600 bps.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

53

Modbus Protocol Description
Introduction
•

•

•

•
•
•
•
•

Direct connection:
− RS232, RS485
− 8 data bits
− 1 stop bit
− no parity
Modem connection
− 8 data bits
− 1 stop bit
− no parity
Communication speed:
− IL-NT/IC-NT: 9600 / 19200 / 38400 / 57600 bps (selectable by setpoint)
− InteliDrive: 9600 / 19200 / 38400 bps (selectable by setpoint)
− IG/IS-NT: 9600 / 19200 / 38400 / 57600 bps (selectable by setpoint)
Transfer mode RTU
Function 3 (Read Multiple Registers)
Function 6 (Write Single Register)
Function 16 (Write Multiple Registers)
The response to an incoming message depends on the communication speed. The delay is not shorter
than the time needed to send/receive 3 and ½ characters.

The complete description of Modbus communication protocol can be found in
http://modbus.org/docs/PI_MBUS_300.pdf
and
http://www.rtaautomation.com/modbustcp/files/Open_ModbusTCP_Standard.pdf.

Data reading
The function Read Multiple Registers has to be used for data reading. The terminal sends a query and from
the controller receives either the normal response containing the requested data or the exceptional response
indicating a read error. The object “Last Error of the Modbus communication” contains the Error specification.
In some cases it is possible to read just one register - depending on Object number – see Examples in
chapter Modbus Communication Examples. The single object list can be exported using PC software –
command Generate Cfg Image (Comm. Objects).
Block reading is available just for MODBUS Registers in the range 40000 ÷ 48000 – see Register oriented
Modbus.
Version of MODBUS Inteli implementation: 1.4, 16.3.2006
Query:
Byte
0
1

Meaning
Controller address
3
Communication object number
2
- upper byte (MSB)
3
- lower byte (LSB)
Communication object length expressed by the number of
4
registers
5
- upper byte (MSB)
- lower byte (LSB)
Check field CRC
6
- lower byte (LSB)
7
- upper byte (MSB)
Normal response:
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

Note
1 to 32
Function code
See List of
communication objects
Greater than 0

See Check field
calculation

54

Byte
0
1

3
4
5
6
…
L+1
L+2
L+3
L+4

Meaning
Controller address
3
Length of read data in bytes (L)
Data of the 1st register
- upper byte (MSB)
- lower byte (LSB)
Data of the 2nd register
- upper byte (MSB)
- lower byte (LSB)
Data of the last register
- upper byte (MSB)
- lower byte (LSB)
Check field CRC
- lower byte (LSB)
- upper byte (MSB)

Exceptional response:
Byte
Meaning
0
Controller address
1
131
2
2
Check field CRC
3
- lower byte (LSB)
4
- upper byte (MSB)

Note
Same as in the query
Same as in the query
Number of registers ∗ 2

See Check field
calculation

Note
Same as in the query
Function code + 128
See Error list
See Check field
calculation

Data writing
All data can be written by the function Write Multiple Registers. Data up to 2 bytes can be written by the
function Write Single Register, too. The terminal sends a query containing a written data and the controller
either confirms it (normal response) or refuses it (exceptional response).

a) Write Multiple Registers
Query:
Byte
0
1
2
3
4
5
6
7
8
9
10
…
L+5
L+6
L+7
L+8

Meaning
Controller address
16
Communication object number
- upper byte (MSB)
- lower byte (LSB)
Communication object length expressed by the number of
registers
- upper byte (MSB)
- lower byte (LSB)
Length of written data in bytes (L)
Data of the 1st register
- upper byte (MSB)
- lower byte (LSB)
Data of the 2nd register
- upper byte (MSB)
- lower byte (LSB)
Data of the last register
- upper byte (MSB)
- lower byte (LSB)
Check field CRC
- lower byte (LSB)
- upper byte (MSB)

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

Note
1 to 32
Function code
See List of
communication objects
Greater than 0

Number of registers ∗ 2

See Check field
calculation

55

Standard response:
Byte
Meaning
0
Controller address
1
16
Communication object number
2
- upper byte (MSB)
3
- lower byte (LSB)
Communication object length expressed by the number of
4
registers
5
- upper byte (MSB)
- lower byte (LSB)
Check field CRC
6
- lower byte (LSB)
7
- upper byte (MSB)
Exceptional response:
Byte
Meaning
0
Controller address
1
144
2
2
Check field CRC
3
- lower byte (LSB)
4
- upper byte (MSB)

Note
Same as in the query
Same as in the query
Same as in the query
Same as in the query

See Check field
calculation

Note
Same as in the query
Function code + 128
See Error list
See Check field
calculation

b) Write Single Register
Query:
Byte
0
1
2
3
4
5
6
7

Meaning
Controller address
6
Communication object number
- upper byte (MSB)
- lower byte (LSB)
Data
- upper byte (MSB)
- lower byte (LSB)
Check field CRC
- lower byte (LSB)
- upper byte (MSB)

Standard response:
Byte
Meaning
0
Controller address
1
6
Communication object number
2
- upper byte (MSB)
3
- lower byte (LSB)
Data
4
- upper byte (MSB)
5
- lower byte (LSB)
Check field CRC
6
- lower byte (LSB)
7
- upper byte (MSB)
Exceptional response:
Byte
Meaning
0
Controller address
1
134
2
2
Check field CRC
3
- lower byte (LSB)
4
- upper byte (MSB)
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

Note
1 to 32
Function code
See List of
communication objects

See Check field
calculation

Note
Same as in the query
Same as in the query
Same as in the query
Same as in the query
See Check field
calculation

Note
Same as in the query
Function code + 128
See Error list
See Check field
calculation

56

Check field calculation
The check field allows the receiver to check the validity of the message. The check field value is the Cyclical
Redundancy Check (CRC) based on the polynomial x16+x15+x2+1. CRC is counted from all message bytes
preceding the check field. The algorithm of CRC calculation is introduced below on an example of a C
language function.
unsigned short count_CRC(unsigned char *addr, int num)
{
unsigned short CRC = 0xFFFF;
int i;
while (num--)
{
CRC ^= *addr++;
for (i = 0; i < 8; i++)
{
if (CRC & 1)
{
CRC >>= 1;
CRC ^= 0xA001;
}
else
{
CRC >>= 1;
}
}
}
return CRC;
}

Data types
The following table contains the communication objects data types and their representation in the data part
of the communication function.
Data type

Meaning

Integer8

Signed integer – 8 bits

Number of
registers
1

Unsigned8

Unsigned integer – 8 bits

1

Integer16

Signed integer – 16 bits

1

Unsigned16

Unsigned integer – 16 bits

1

Integer32

Signed integer – 32 bits

2

Unsigned32

Unsigned integer – 32 bits

2

Binary8

Binary number – 8 bits

1

Binary16

Binary number – 16 bits

1

1

MSBx
LSBx

=
=

Data part of the communication
function 1
MSB1 = sign extension LSB1
LSB1 = comm. object value
MSB1 = 0
LSB1 = comm. object value
MSB1 = comm. object value, bits 15-8
LSB1 = comm. object value, bits 7-0
MSB1 = comm. object value, bits 15-8
LSB1 = comm. object value, bits 7-0
MSB1 = comm. object value, bits 31-24
LSB1 = comm. object value, bits 23-16
MSB2 = comm. object value, bits 15-8
LSB2 = comm. object value, bits 7-0
MSB1 = comm. object value, bits 31-24
LSB1 = comm. object value, bits 23-16
MSB2 = comm. object value, bits 15-8
LSB2 = comm. object value, bits 7-0
MSB1 = 0
LSB1 = comm. object value
MSB1 = comm. object value, bits 15-8
LSB1 = comm. object value, bits 7-0

register x, bits 15-8
register x, bits 7-0

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

57

Binary32

Binary number – 32 bits

2

Char

ASCII character

1

List

String list

1

ShortStr

ASCII string of max. length of 15
characters (zero terminated string)

8

LongStr

ASCII string of max. length of 31
characters (zero terminated string)

16

Date

Date

2

Time

Time

2

Domain

Field n bytes
C-declaratione: unsigned char x[n]

n

String

String
(Zero terminated string)

depends on
register
number

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

MSB1 = comm. object value, bits 31-24
LSB1 = comm. object value, bits 23-16
MSB2 = comm. object value, bits 15-8
LSB2 = comm. object value, bits 7-0
MSB1 = 0
LSB1 = comm. object value
MSB1 = 0
LSB1 = comm. object value
MSB1 = 1. character of the string
LSB1 = 2. character of the string
MSB2 = 3. character of the string
LSB2 = 4. character of the string
…
MSB1 = 1. character of the string
LSB1 = 2. character of the string
MSB2 = 3. character of the string
LSB2 = 4. character of the string
…
MSB1 = BCD(day)
LSB1 = BCD(month)
MSB2 = BCD(year)
LSB2 = 0
example:
MSB1 = 18 (HEX)
LSB1 = 04 (HEX)
MSB2 = 01 (HEX)
LSB2 = 0
⇒ Date = 18.4.(20)01
MSB1 = BCD(hour)
LSB1 = BCD(minute)
MSB2 = BCD(second)
LSB2 = 0
example:
MSB1 = 20 (HEX)
LSB1 = 24 (HEX)
MSB2 = 02 (HEX)
LSB2 = 0
⇒ Time = 20:24:02
MSB1
= x[0]
LSB1
= x[1]
MSB2
= x[2]
LSB2
= x[3]
…
n is even number:
MSBm-1
= x[n-2]
LSBm
= x[n-1]
n is odd number:
MSBm-1
= x[n-1]
LSBm
=0
string characters coding depends on
chosen language (8bit coding, EUC)

58

Access to dedicated communication objects of the controller
Dedicated communication objects are setpoints and commands that are protected by a password against
writing. The set of protected objects is given in the controller configuration and is fixed for a particular
controller.
IL-NT and InteliDrive Controllers
The level of protection of an object (setpoint, command) is defined by an access level. There exist 4 access
levels: 0, 1, 2, 3. Writing of an object with access level 0 doesn’t require knowledge of a password. For other
levels writing must be unblocked by entering the correct password. Entering of a password of higher
protection level unblocks writing of objects with lower access level.
Hint:
There is only 1 level of a password for IL-NT MRS3, 4 and AMF8, 9 controllers.
IG/IS-NT Controllers
In IG/IS-NT controllers it is possible to specify access levels to protected objects for 8 different users. For
each user a set of access atributes is defined and each of them has his password. The user can gain the
right for writing to 8 groups of objects with different access levels by entering his password. The objects are
assigned into groups in the controller configuration. For example setpoints in the ProcessControl group can
be configured in GenConfig on Setpoints card:

Each user has his identification number (0 – 7). User with identification number 0 has an exceptional
position. This user has access to all groups of protected objects (this access cannot be changed anyhow)
and can define groups of access atributes to other users (1 – 7), reset their password and set their name
(alias of an identification number). Entering of password must be foregone by writing of an user identification
number.

List of communication objects
Communication objects can be splitted into two groups:
1. Communication objects dependent on the application type (SSB, SPM, SPtM, MEXT, MINT, …). Their
list is stated in the Controller user guide in the section Value and setpoints codes.
2. Communication objects independent on the application type. The description of these communication
objects follows.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

59

Communication Status
Communication object number:
24571
Operation:
Read only
Data type:
Binary32
Meaning:
Bit 0
Internal terminal in InteliSys does not work (0 for other controllers)
Bit 1
Invalid controller software (based on CRC).
Bit 2
Invalid controller configuration (based on CRC).
Bit 3
In the event history is present at least one unread record.
Bit 4
P type setpoints are invalid.
P type setpoints are representing the controller setpoints. Values of these setpoints can be set from
connected terminals. If these setpoints are invalid, the application functions are blocked. Setpoints
recovery is needed.
Bit 5
R type setpoints are invalid.
R type setpoints are representing the data, that is only initialized from connected terminals, but its
updating is made by the controller itself (e.g. statistic or time and date). If these setpoints are invalid,
their change from the controller is blocked. Setpoints recovery is needed.
Bit 6
The event history was cleared.
Bit 7
The event history was filled up at least once.
Bit 8
P type setpoint change occurred (reading resets this bit).
Bit 9
R type setpoint change occurred (reading resets this bit).
Bit 10
Controller type – see the table below.
Bit 11
Alarm list not empty.
Bit 12
Alarm list change (reading resets this bit).
Bit 13
New item added into alarm list (reading resets this bit).
Bit 14
Internal controller terminal is locked up for setpoint change.
Bit 15
Invalid configuration format.
Bit 16
Diagnostic codes change (reading resets this bit, only for IL-NT /ID controllers).
Bits 20
Controller type (*)
Bit 21-17
Reserve (= 0)
Bits 22-21 Password level for Setpoints and Commands write (only for IL-NT /ID controllers).
Bit 23
Controller was initiated.
Bits 28-24 Communication module version.
Bits 29
Remote terminal is connected.
Bits 30
Controller type – see the table below.
Bits 31
Reserve (= 0)
(*) Controller type
Bit 20
0
0
0
0
1
1
1
1

Bit 30
0
0
1
1
0
0
1
1

Bit 10
0
1
0
1
0
1
0
1

Controller
InteliSys
InteliGen
IL-NT
InteliDrive
IG/IS-NT
Reserve
Reserve
Reserve

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

60

Controller Address
Communication object number:
24537
Operation:
Read, write
Data type:
Unsigned8
Meaning:
The controller address serves as an unique identification for communication with the controller. The address has to
be in the range from 1 to 32.

Communication Protocol
Communication object number:
24522
Operation:
Read, write
Data type:
Unsigned8
Meaning:
The communication protocol used for the communication through RS232 connector:
0
Company (standard) communication protocol.
1
Modbus communication protocol.
Note:
The communication protocol setup is made as a result of data updating. The write is not confirmed for the
connected (RS232) terminal.

Write Password Setting
Communication object number:
24524
Operation:
Write(/Read for IG/IS-NT)
Data type:
Unsigned16
Meaning:
Modification of the password protected setpoints is enabled by setting of the correct password. Then the
modification of the protected setpoints is unblocked for 5 minutes. With every errorless write is this time prolonged
for next 5 minutes. The writing of protected setpoints can be blocked immediately by setting an invalid password.
Supported in:
InteliGen
InteliSys
IL-NT
InteliDrive
IG/IS-NT
Hint:
For InteliGen, InteliSys, InteliDrive controllers: setpoints are protected by password of specified level (1, 2 or
3). For IG/IS-NT controllers: setpoints are protected by password of specified group (1 – 8). For IL-NT and
IC-NT there is only one password level.
See table 5 and 6 in configuration image generated by controller configuration PC tool.

Write Password Change
Communication object number:
24549
Operation:
Write
Data type:
Unsigned16
Meaning:
Writing of this object changes password of selected user. Password change is conditioned by knowledge of current
password.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

61

Supported in:
IG/IS-NT

Write Password Changing Level 1
Communication object number:
24513
Operation:
Write only
Data type:
Unsigned16
Meaning:
Writing of this object changes password of level 1 for writing of protected setpoints. Password change is
conditioned by knowledge of password of level 1 or 3.
Supported in:
InteliGen
InteliSys
InteliDrive

Write Password Changing Level 2
Communication object number:
24514
Operation:
Write only
Data type:
Unsigned16
Meaning:
The password level 2 change. The change is conditioned by the current level 2 or 3 password knowledge. With
respect to the internal controller terminal, the password has to have the value from 0 to 9999.
Writing of this object changes password of level 1 for writing of protected setpoints. Password change is conditioned by
knowledge of password of level 1 or 3.
Supported in:
InteliGen
InteliSys
InteliDrive

Write Password Changing Level 3
Communication object number:
24549
Operation:
Write only
Data type:
Unsigned16
Meaning:
The password level 3 change. The change is conditioned by the current level 3 password knowledge. With respect
to the internal controller terminal, the password has to have the value from 0 to 9999.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive

User Identification Number
Communication object number:
24470
Operation:
Write, Read
Data type:
Unsigned8
Meaning:
User identification number (0 – 7). If the user is changed, the password entered by the previous user is not valid
anymore.
Supported in:
IG/IS-NT
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

62

Change User Alias
Communication object number:
24468
Operation:
Write, Read
Data type:
ShortStr
Meaning:
Enables to change an alias (name) of selected user (object no. 24470).
Supported in:
IG/IS-NT

Read Alias of One User
Communication object number:
24460 - 24467
Operation:
Read
Data type:
ShortStr
Meaning:
Enables to read an alias (name) of one user.
Supported in:
IG/IS-NT

Read Alias of All Users
Communication object number:
24459
Operation:
Read
Data type:
8 x ShortStr
Meaning:
Enables to read an alias (name) of all users.
Supported in:
IG/IS-NT
Hint:
IG/IS-NT controllers provide 8 users definition and their password levels, i.e. each user can perform actions
allowed by his password level. User U0 (default name) always has password of the highest level. Names
(aliases) of all users can be changed. Alias is max. 15 characters long.

User Administration
Communication object number:
24472
Operation:
Write
Data type:
Domain
9 registers
Meaning:
Writing of this communication object enables to User 0 (after correct password is entered) to administrate the
users:
1. set access attributes for Users 1 – 7
2. clear password for Users 1 – 7
3. clear password for all users
4. set alias for Users 0 – 7
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

63

MSB1

Bits 3-0 = request type:
0 ⇒ set access atributes of selected user
1 ⇒ reset password of selected user
2 ⇒ reset passwords of all users (1 – 7)
3 ⇒ set alias of selected user
Bits 7-4 = user (1 - 7)

LSB1-LSB9

meaning is given by request type:
0 ⇒ set of access atributes (LSB1)
1 ⇒ not used
2 ⇒ not used
3 ⇒ user alias (LSB1-MSB9)

Supported in:
IG/IS-NT

Access Attributes of All Users
Communication object number:
24455
Operation:
Read only
Data type:
Domain
4 registers
Meaning:
MSB1
Access atributes of user 0
LSB1
Access atributes of user 1
MSB2
Access atributes of user 2
LSB2
Access atributes of user 3
MSB3
Access atributes of user 4
LSB3
Access atributes of user 5
MSB4
Access atributes of user 6
LSB4
Access atributes of user 7
Supported in:
IG/IS-NT

Access Attributes of One User
Communication object number:
24440 - 24447
Operation:
Read only
Data type:
Binary8
Meaning:
Enables to read access attributes of one user 0 – 7.
Supported in:
IG/IS-NT
Hint:
Access attributes define levels that are accessible for specific user. These are set in InteliMonitor by an
administrator.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

64

Last Error of the Modbus Communication
Communication object number:
24523
Operation:
Read only
Data type:
See Error list
Meaning:
If an error comes up when processing the Modbus terminal query, the controller returns an exceptional response.
The Modbus terminal can find out the error type by reading this communication object.
Supported in:
InteliGen

InteliSys

IL-NT

InteliDrive

IG/IS-NT

Current Time
Communication object number:
24554
Operation:
Read, write
Data type:
Time
Meaning:
Current controller time can be determined or set using this communication object.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

Current Date
Communication object number:
24553
Operation:
Read, write
Data type:
Date
Meaning:
Current controller date can be determined or set using this communication object.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

Action - Command
Communication object number:
24521
Operation:
Write only
Data type:
Unsigned16
Meaning:
An action described in the following table can be started by writing this communication object. Bits 7-0 of the
written value contain the action code and bits 15-8 contain the one‘s complement of the action code.
Action codes InteliDrive:
Action code
1
2
3

Action
Engine start
Engine stop
Horn reset

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

Value in DEC
65025
64770
64515

Value in HEX
FE01
FD02
FC03
65

Action code
4
11
12
13
17

Action
Fault reset
Command for MODE >
Command for MODE <
Clutch ON/OFF
ECU Fault Reset

Value in DEC
64260
62475
62220
60435
59415

Value in HEX
FB04
F40B
F30C
EC13
E817

Action
Engine start
Engine stop
Horn reset
Fault reset
Generator Circuit Breaker closing
Generator Circuit Breaker opening
Mains Circuit Breaker closing
Mains Circuit Breaker opening
Generator Circuit Breaker closing/opening
Mains Circuit Breaker closing/opening
Set/reset RemoteControl1-8 binary outputs

Value in DEC
65025
64770
64515
64260
64005
63750
63495
63240
62985
62730
32/
16

Value in HEX
FE01
FD02
FC03
FB04
FA05
F906
F807
F708
F609
F50A
0020/
0010

Action
Engine start
Engine stop
Horn reset
Fault reset
Generator Circuit Breaker closing
Generator Circuit Breaker opening
Mains Circuit Breaker closing
Mains Circuit Breaker opening
Generator Circuit Breaker closing/opening
Mains Circuit Breaker closing/opening

Value in DEC
65025
64770
64515
64260
64005
63750
63495
63240
62985
62730

Value in HEX
FE01
FD02
FC03
FB04
FA05
F906
F807
F708
F609
F50A

Action codes IGS-NT:
Action code
1
2
3
4
5
6
7
8
9
10
26
Action codes IL-NT:
Action code
1
2
3
4
5
6
7
8
9
10

Hint:
Also see the table of register oriented commands in Register oriented Modbus in IG/IS-NT/ID chapter and
the command examples in the Modbus communication examples chapter.

Controller Serial Number
Communication object number:
24548
Operation:
Read only
Data type:
Domain
2 registers
Meaning:
The serial number is an unique identification of a given controller.
Example: MSB1 = 07 (HEX), LSB1 = 10 (HEX), MSB2 = 00 (HEX), LSB2 = F4 (HEX) ⇒ sériové číslo:
071000F4
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

66

Alarm List
Communication object number:
24545
Operation:
Read only
Data type:
An array of 16 Unsigned16 values
Meaning:
The alarm list can contains up to 16 items. All items that have their bits 15-12 set to value F (HEX) and following
has to be ignored ! The meaning of particular item values is given according to the table 13 in the controller
description, that is generated using the Configuration image function of the configuration tool.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
Hint:
For IG/IS-NT controllers see the description at the Dedicated communication objects table.

Remote Communication Access Code Setting
Communication object number:
24534
Operation:
Write only
Data type:
Unsigned16
up to IG software version 5.1 (ig_5_1.mhx) and IS 2.1 (is_2_1.mhx)
ShortStr
from up to IG software version 5.2 (ig_5_2.mhx) and IS 2.2 (is_2_2.mhx)
Meaning:
If a terminal establishes a phone connection with the controller, it has to enter the access code to the controller at
first. Only then any data can be read or written. The access code is valid until the connection is cancelled.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

Remote Communication Access Code Changing
Communication object number:
24535
Operation:
Write only
Data type:
Unsigned16
up to IG software version 5.1 (ig_5_1.mhx) and IS 2.1 (is_2_1.mhx)
ShortStr
from up to IG software version 5.2 (ig_5_2.mhx) and IS 2.2 (is_2_2.mhx)
Meaning:
The access code serves for unblocking of the remote (phone, SMS) communication with the controller. The change
of the access code is conditioned by the write password knowledge. For IG, IS and ID controllers it is password of
level 3. For IG/IS-NT it is password of level 7 (highest level).
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

Active Call Termination
Communication object number:
24540
Operation:
Write only
Data type:
Unsigned8
Meaning:
The controller can under certain conditions (e.g. after engine shutdown) establish a connection with a remote
terminal – perform an active call. The remote terminal can after that (without access code knowledge) read the data
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

67

needed for the analysis of the issued situation. The data transfer has to be terminated by the terminal by writing this
communication object. After a successful transfer it writes the value 1, otherwise 0. If a new active call request comes
up during the data transfer, the controller doesn‘t return the normal response, but the exceptional one (communication
object 24523 has the value 237.0.0.8 – See Error list). In this case the controller doesn‘t terminate the connection, but it
awaits the request from the terminal.
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

Controller Identification String
Communication object number:
24501
Operation:
Read only
Data type:
LongStr
Meaning:
Controller identification string.
Supported in:
IL-NT
InteliGen
InteliSys

InteliDrive

IG/IS-NT

Values Multipack
Communication object number:
24502
Operation:
Read only
Data type:
Domain
n registers
Meaning:
For ID and IG/IS-NT controllers contains values defined in history record , for other controllers the object value
depends on software used – for IL-NT /IG/IS it contains Values I, II, III (Tab. 1, 2, 3 in Configuration image) and
alarm list contents (limited by one Modbus message length).
Supported in:
IL-NT
InteliGen
InteliSys
InteliDrive
IG/IS-NT

ECU Diagnostic Codes List
Communication object number:
24478
Operation:
Read only
Data type:
Domain
24 registers
Meaning:
Diagnostic codes list contains 8 items, 6 bytes each with following format:
Bit18-0
Error code – SPN, or Fault code.
Bit23-19
Error meaning – FMI code.
Bit30-24
Number of Error occurrences.
Bit31
Indication of not confirmed fail.
Bit39-32
Do not use (ComAp internal).
Bit40
Item validity; the first (= 0) means end of the list.
Bit41
Item was confirmed.
Bit47-42
Reserve (= 0)
Supported in:
IL-NT
InteliDrive

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

68

Error list
If the controller encounters an error when processing the query, it returns the exceptional response instead
of the normal one to the terminal. An exception has always the value 2 (Illegal Data Address). After receiving
the exceptional response, the terminal should read the communication object 24523 containing the last error
specification. The meaning of an error can be found out from the following table.
MSB1
(*)
0
0
0

LSB1
(*)
0
0
0

MSB2
(*)
0
2
1

LSB2
(*)
0
6
6

253
252
251
250
247
240

0
0
0
0
0
0

0
0
0
0
0
0

8
8
8
8
8
8

238
237

0
0

0
0

8
8

235

0

0

8

234
233
232
231

0
0
0
0

0
0
0
0

8
8
8
8

229
228

0
0

0
0

8
8

227
0
214
0
211
0
210
0
209
0
208
0
207
0
201
0
200
0
199
0
198
0
197
0
196
0
195
0
(*) in DEC

0
0
0
0
0
0
0
0
0
0
0
0
0
0

8
8
8
8
8
8
8
8
8
8
8
8
8
8

Meaning
No error.
Comm. Object nonexistent.
Illegal access:
Read (write) of the communication object. Object intended only for write
(read).
No more unread records in event history.
Setpoint not defined in controller configuration.
Bad write data length.
Invalid password.
Invalid controller configuration.
Operation cannot be performed now, the terminal has to repeat the request.
This error can occur when an operation with EEPROM memory (setpoint
write, history record read) is required at the same time while an internal
EEPROM write cycle takes place.
Write cannot be performed – power supply failure detected.
Another active call request is present.
This error code can be returned by the controller as the response to the
communication object. Object 24540 write – active call termination.
This error is reported by iG-MU module (Modem Bridge) in the case of a
connection failure between the module and the addressed controller. The
terminal can evaluate this error as a communication timeout with the
controller.
Write cannot be performed – periphery not responding.
Write cannot be performed – setpoint nonexistent in any periphery.
Bad access code for communication from a remote terminal.
Invalid controller address: value out of range 1 to 32 or already used. This
error is a reaction on communication object. Object 24537 write.
Undefined action. A reaction on communication object. Object 24521 write.
Action (although defined) cannot be performed. A reaction on
communication object. Object 24521 write.
Written object value is not acceptable.
Wrong access code, the connection must be terminated.
Unsufficient access rights.
The request can be submitted only by the administrator (User 0).
The administrator has entered a wrong user identification number.
Not possible to write, the communication object has forced value.
The administrator requests an unsupported operation.
Unknown fault.
Invalid register.
Reading of alarm list is locked.
Reading of history is locked.
Reading of alarm list has to be started by reading the first record.
The history record is not defined for reading of history.
It is not possible to request such number of registers.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

69

How to Create Actual Communication Object List
For IG/IS-NT controller use GenConfig menu command File – Generate Cfg Image – Generate Cfg Image
(Comm. Objects …) or Generate Cfg Image (Modbus Registers all/used) for register oriented Modbus
implementation.
For IL-NT controller use LiteEdit – Controller – Generate Cfg Image…
For InteliDrive controller use DriveConfig – File – Generate Cfg Image…
For InteliGen or InteliSys classic line controllers use WinEdit – Controller – Generate Cfg Image…

Register Oriented Modbus in IG/IS-NT/ID, IL-NT, IC-NT (not available for
IG, IS)
Available in ID-DCU-Marine since version 1.3 and in the ID-DCU-Industrial since version 2.4.
Available in IL-NT since version 1.3.

Data addressing in IG/IS-NT
Communicated data belong to one of the following groups:
Registers (*)
Register address (*)
Communicated data
40001 – 43000
0 – 2999
Application values
43001 – 46000
3000 – 5999
Application setpoints
46001 – 47168
6000 – 7167
Dedicated communication objects
(*) Registers in DEC are available in text file that can be generated from actual configuration file – see below.
Hint:
For communication use Register address = Register number – 40001 !!!
If the register number e.g. 40053 is requested the query for register address 52 has to be sent.
See examples in chapter IG/IS-NT register oriented Modbus communication examples

Application values and setpoints
The list of available application values and setpoints depends on the controller software and it can be
generated using function Generate Cfg Image (Modbus Registers) in GenConfig/DriveConfig tool.
There are three options to generate Cfg image:
Option
Comm. Objects
Modbus registers – all
Modbus Registers – used

List contains objects …
Available just for single register reading.
Including all possible extension modules.
Just from configured (used) modules.

Note:
Screen shoot above comes from GenConfig-2.3.
See part of “Modbus registers - used” export in the example below.
Header
Registers(s)
Com.Obj.
Name
Dim
Type
Len
Dec

Description
Register number.
Register address = register number – 40001 !!!
Corresponding communication object number
Communication object name
Value dimension
Value data type (see Data types)
Data length in Bytes (max. 64)
Number of decimals

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

70

Com.Obj. Name

40001
8505
40002
8506
40003
8235
40004
9107
40005
9108
40006
9109
40007
9110
40008
9111
40009
9112
40010
9113
40011
9114
40012
8239
40013
8213
40014
10124
40015
10603
40016
9155
40017
9156
40018
9157
40019
9158
43001-43008 ( 8) 8637
43009
8276
43010
8275
43011
8274
43012
10556
43013
8566
43014
10557
43015
9579
43016
10662
43017
9580
43018
10663
43019
8277
43020
9673
43021
9888
43022
9907
43023
10647
43024
8278
43025
8252
43026
8253
43027
8315

(N/A)
(N/A)
BIN
(N/A)
(N/A)
(N/A)
(N/A)
(N/A)
(N/A)
(N/A)
(N/A)
BOUT
Ubat
CPU temp
Dplus
Oil press
Water temp
Fuel level
Reload
Gen-set name
Nomin power
Nomin current
CT ratio prim
CT ratio sec
Im3/ErFlCurCTp
Im3/ErFlCurCTs
VT ratio
Vg InpRangeSel
Vm VT ratio
Vm InpRangeSel
GenNomV
GenNomVph-ph
MainsNomV
MainsNomVph-ph
VoltProtSelect
Nominal freq
Gear teeth
Nominal RPM
ControllerMode

Dim

V
°C
V
Bar
°C
%
s
kW
A
A
A
V/V
V/V
V
V
V
V
Hz
RPM

Type

Len Dec

Min

Binary#1

2

-

-

Binary#2
Integer
Integer
Integer
Integer
Integer
Integer
Integer
String0
Unsigned
Unsigned
Unsigned
List#9
Unsigned
List#9
Unsigned
List#10
Unsigned
List#10
Unsigned
Unsigned
Unsigned
Unsigned
List#11
Unsigned
Unsigned
Unsigned
List#3

2
2
2
2
2
2
2
2
16
2
2
2
1
2
1
2
1
2
1
2
2
2
2
1
2
2
2
1

1
1
1
1
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
0
-

0
-200
0
0
0
0
0
1
1
1
41
1
41
1
43
1
43
80
130
80
130
45
45
0
100
359

Max Group

- Bin inputs CU

360
800
360
100
150
100
200
32000
10000
10000
42
10000
42
5000
44
5000
44
30000
60000
30000
60000
46
65
500
4000
363

Bin outputs CU
Analog CU
Analog CU
Analog CU
Analog CU
Analog CU
Analog CU
Analog CU
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings
Basic settings

Application values (read only)

Register(s)

Value low limit
Value high limit
Group of setpoints/values

Application setpoints (read/write)

Min
Max
Group

Hint:
Depends on controller configuration there are available values transmitted from ECU via J1939 in Modbus
registers. ECU values are listed in format according the Cg Img file (not in J1939 format) see in example
below.
40053
40054
40055
40056
40057
40058
40059
40060
40061
40062
40063
40064
40065
40066

10153
10154
10155
10156
10157
10158
10159
10160
10161
10162
10163
10164
10165
10166

Engine Speed
Exhaust Temp
Boost Press
Oil Temp
Load
Fuel Rate
Actual Toque
Demand Torque
Fuel Press
Throttle Pos
CrankcasPres
Coolant Pres
Coolant Temp
Oil Press

RPM
°C
bar
°C
%
L/h
%
%
bar
%
bar
bar
°C
bar

Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer
Integer

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

2
2
2
2
2
2
2
2
2
2
2
2
2
2

0
0
2
0
0
1
0
0
2
0
2
2
0
2

0
-20
0
-20
0
0
0
0
0
0
0
0
-20
0

3000
500
500
200
125
1500
125
125
1000
100
250
500
150
1000

ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU
ECU

71

Dedicated communication objects
These objects are always available regardless of the controller software modification:
Registers (*)
46001 – 46025
46026 – 46050
46051 – 46075
46076 – 46100
46101 – 46125
46126 – 46150
46151 – 46175
46176 – 46200
46201 – 46346
46347 – 46348
46349 – 46350
46351

Register
addresses (*)
6000 – 6024
6025 – 6049
6050 – 6074
6075 – 6099
6100 – 6124
6125 – 6149
6150 – 6174
6175 – 6199
6200 – 6345
6346 – 6347
6348 – 6349
6350

Number of
registers
25
25
25
25
25
25
25
25
146
2
2
1

Access

Data type

Meaning

read
read
read
read
read
read
read
read

String
String
String
String
String
String
String
String

read/write
read/write
read/write

Time
Date
Unsigned8

2

read

Domain

6353
6354
6355
6356
6357
6358 – 6359

1
1
1
1
1
2

read
read

Unsigned8
Unsigned16

read/write
write
read/write

Integer16
Unsigned16
Unsigned32

6360
6361
6362
6363
6364
6365 – 6489
6490
6492 – 6540
6541
6542 – 6666
6667
6668 – 6692
6693 – 6717
6718 – 6742
6743 – 6767
6768 – 6792
6793 – 6817
6818 – 6842
6843 – 6867
6868 – 6892
6893 – 6917
6918 – 6942
6943 – 6967
6968 – 6992
6993 – 7017
7018 – 7042
7043 – 7067
7068 – 7167

1
1
1
1
1
125
1
50
1
125
1
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
100

write

Unsigned16

read/write
write

Unsigned8
Unsigned16

read

Domain

read

String

read

Domain

read
read
read
read
read
read
read
read
read
read
read
read
read
read
read
read

String
String
String
String
String
String
String
String
String
String
String
String
String
String
String
String

1. record in ECU alarm list (# 1) (# 8)
2. record in ECU alarm list (# 1) (# 8)
3. record in ECU alarm list (# 1) (# 8)
4. record in ECU alarm list (# 1) (# 8)
5. record in ECU alarm list (# 1) (# 8)
6. record in ECU alarm list (# 1) (# 8)
7. record in ECU alarm list (# 1) (# 8)
8. record in ECU alarm list (# 1) (# 8)
Reserved (registers not implemented)
Actual time
Actual date
Language index selected for displaying of
texts specified by data type String (# 7)
Code of the last communication fault.
See Error list
Number of records in the alarm list
Number of records in history (# 6)
Number of records in ECU alarm-list (# 8)
Index of requested history record (# 5)
Remote key
For writing: command argument
For reading: command release value (# 3)
Command (# 3)
Reserved (register not implemented)
User identification number (# 4) (# 9)
Entering of password for writing (# 4)
Reserved (register not implemented)
Values multipacket(#8)
Reserved (register not implemented)
Header of the particular history record (# 1)
Reserved (register not implemented)
Data part of the particular history record (# 2)
Reserved (register not implemented)
1. record in alarm list (# 1)
2. record in alarm list (# 1)
3. record in alarm list (# 1)
4. record in alarm list (# 1)
5. record in alarm list (# 1)
6. record in alarm list (# 1)
7. record in alarm list (# 1)
8. record in alarm list (# 1)
9. record in alarm list (# 1)
10. record in alarm list (# 1)
11. record in alarm list (# 1)
12. record in alarm list (# 1)
13. record in alarm list (# 1)
14. record in alarm list (# 1)
15. record in alarm list (# 1)
16. record in alarm list (# 1)
Reserved (registers not implemented)

46352 – 4653

6351 – 6352

46354
46355
46356
46357
46358
46359 – 46360
46361
46362
46363
46364
46365
46366 – 46490
46491
46493 – 46541
46542
46543 – 46667
46668
46669 – 46693
46694 – 46718
46719 – 46743
46744 – 46768
46769 – 46793
46794 – 46818
46819 – 46843
46844 – 46868
46869 – 46893
46894 – 46918
46919 – 46943
46944 – 46968
46969 – 46993
46994 – 47018
47019 – 47043
47044 – 47068
47069 – 47168

(*) in DEC
#1
The result of reading of an unused record is an empty string.
#2
The result of reading of an unused record is a domain with zero value.
#3
An argument must be written before writing of a command code, because immediately after the command
code has been written, the command is executed. It is recommended to write an argument and command
simultaneously, in a multiple registers write. As the argument has lower register address than command, the
required sequence is maintained. See List of commands and modbus communication examples.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

72

#4
Before entering the password for writing it is necessary to define user identification number. It is
recommended to enter user identification number and password simultaneously. Entered password stays
valid 5 minutes after the last successful writing.
#5
The latest record has index 0, older record has index -1, next record has index -2, …
#6
It is possible to read and write only in case that history reading is not locked by another terminal. Second
necessary condition is to previously write the index.
#7
Implicitly = 0.
#8
Implemented only for controllers containing ECU alarm-list.
#9
Only for IG/IS-NT controller.

Data reading
•
•
•
•
•

It is possible to use function 3 for reading (Read Multiply Registers).
It is not possible to read from the middle. The register number must correspond with the beginning of the
data object. The only exception are the objects of „multipacket values“ (registers 46367 – 46491) and
„data part of the history record“ (registers 46543 – 46667).
All read registers must be implemented. If an unimplemented register appears among the read registers,
the controller returns an error message.
Even unnamed values can be included among read registers (See Application values and setpoints –
Name = (N/A) ). The read value must be treated as meaningless.
The length of a block is 127 registers.

Data writing
•
•
•
•
•
•

For writing it is possible to use function 6 (Write Single Register) and function 16 (Write Multiply
Registers).
Using function 16 it is possible to write maximum 16 registers at once.
Data cannot be written from the middle. Register number must correspond with the beginning of the data
object. Written data must be complete to perform writing of all requested data objects.
Writing to EEPROM is executed using a queue. The queue is common for writing from all terminals. The
request for next writing is accepted in case that there is empty space in the queue. Otherwise the
controller returns an error message and the terminal must repeat the request.
All written registers must be implemented. If an unimplemented register appears among the read
registers, the controller returns an error message.
It is possible to include also unnamed registers in the written sequence (See Application values and
setpoints – Name = (N/A) ). The controller confirms this writing but writing of unnamed registers is not
performed.

Alarm list reading
It is not possible to read alarm list simultaneously from more terminals. If the terminal starts reading, the
reading is locked for other terminals. It is unlocked 5 seconds after last reading of alarm list. The locked
terminal indicates to another terminal an error message.
The whole alarm list is stored in the cache memory at the moment of locking and the following reading of
records is performed from this memory. Locking is done only while reading the first record. So the
successive reading from the first to the last record is supposed.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

73

History reading
It is not possible to read history from more terminals simultaneously. Reading must be started by writing of
an index of requested history record. If the index is not written it is not possible to read neither history header
nor data part of the record. In this case the controller returns an error message. If the terminal writes the
index of requested record, history reading is locked for other terminals (i.e. reading and writing of an index of
requested record, reading of header and data part of the record). It is unlocked 5 seconds after the last
history reading. Locked history is indicated to other terminals by an error message.
Requested history record is stored at the moment of locking in the cache memory and following reading is
performed from this memory.

List of commands, see Start command
Command Meaning

Argument (*)

Return value (*)

1

01FE0000

000001FF

OK

2

Argument has not been written

000002FE

OK

2

Argument has not been written

04FB0000
08F70000
10EF0000
other
11EE0000

000004FC
000008F8
000010F0
1
000011EF

OK
OK
OK
Wrong argument
OK

2

Argument has not been written

Close generator circuit
breaker

11EF0000

000011F0

OK

2

Argument has not been written

Open generator circuit
breaker

11F00000

000011F1

OK

2

Argument has not been written

Close/open mains circuit
breaker

12ED0000

000012EE

OK

2

Argument has not been written

Close mains circuit breaker

12EE0000

000012EF

OK

2

Argument has not been written

000012F0

OK

2

Argument has not been written
Wrong argument
OK
Not possible to perform
OK
Not possible to perform

Engine start
Engine stop
Horn reset
Fault reset
ECU Fault reset

2

Close/open generator circuit
breaker (IGS-NT)
Clutch ON/OFF (ID)

Open mains circuit breaker

02FD0000

12EF0000

5

Reset from Init state 2

other
44440000

7

Statistics reset

007C0000

8
12
13
14
25

Set kWh counter
Set kVAhr counter
Set counter of engine starts
Set runhours counter
Set counter of unsuccessful
engine starts
Set binary output
RemoteControl1-8
Reset binary output
RemoteControl1-8

New value
New value
New value
New value
New value

1
00004445
1
0000007D
1
N/A
N/A
N/A
N/A
N/A

00200000

N/A

00100000

N/A

26

2

If the controller setpoints are not valid after it is switched on, the controller goes to a blocked state. In this state it is
necessary to modify the setpoints from the controller keypad and switch off and on the controller or from the external
terminal and unblock the controller by Reset from Init state command. Another condition necessary to unblock the
application function of the controller is valid configuration.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

74

27

Log of writing of
communication objects to the
controller history

00010000
⇒ enabled
00000000
⇒ disabled
28
Reset of the controller history 00010000
record
31,32,33,34 Set pulse counters (IS-NT
XXXXYYYY
only)
(XXXX – Upper
part of a new
value;
YYYY – Lower
part of a new
value)
35,36,37,38 Set ExtValue1-4 (IS-NT only) 0002YYYY
(YYYY - new
value)

N/A

N/A
Upper value + 1
1, 2

OK
Not possible to perform

3
1, 2

OK
Not possible to perform

(*) in HEX
Hint:
The MODE< and MODE> commands have not been implemented to the register oriented modbus
commands.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

75

Modbus Communication Examples
Following examples are just for single register reading.

Battery Voltage Reading
Request: 0103201500019E0E (in HEX)
01
= Controller address
03
= Modbus function number (reading)
2015
= 2015 HEX = 8213 DEC = object number for Battery voltage
0001
= Communicastion object length expressed by the number of registers
9E0E
= CRC (see Check field calculation)
See Data reading chapter.
Example: 8123 = Battery voltage, In Tab. 3 Values III is Type=Integer and Len=2byte, that means data type
Integer16.
See Data types table (it is conversion between IG and Modbus registers): Number of (Modbus) registers for
Integer16 = 1, that means 0001.
Response 01 03 02 00F9 7806 (in HEX)
01
= Controller address
03
= The same as in query
02
= Length of read data in bytes
00F9

= object data value =249 in decimal, but 8213 object is defined with one decimal point, see
Tab. 3 (in Cfg Image – see How to create actual Communication object list chapter).
So real interpretation is 24,9 V (volts) because Dim (=dimension) of 8213 is V.
See Tab. 3.

The last part 7806 is CRC.

Binary Inputs Reading
Request 0103202B01FFC2 (in HEX)
01
= Controller address
03
= Modbus function number (reading)
202B
= 202B HEX = 8235 DEC Object number for BInpIG
01
= Communication object length - number of registers
FFC2
= CRC
Response 010302FF0279B9 (in HEX)
01
= Controller address
03
= The same as in request
02
= Data length in bytes
FF12
= Object data value (for BI= 010010001, BI2=BI5=BI9=1)
79B9
= CRC
Received two bytes object data FF12 interpretation see in the table:
F
F
1
2
X X X X X X X BI9 BI8 BI7 BI6 BI5 BI4 BI3 BI2 BI1
1 1 1 1 1 1 1 1
0
0
0
1
0
0
1
0
X = no meaning

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

76

Alarm List Reading (only for IL-NT, IC-NT, ID, IG,IS – not for IG/IS-NT)
Alarm list request: 01 03 5FE1 0010 0624 (in HEX)
01
= Controller address
03
= Modbus function number (reading)
5FE1
= 5FE1 in HEX = 24545 in DEC = Alarm list object number
0010
= 10 in HEX = 16 in DEC = communication object (Alarm list) length expressed by the
number of Modbus registers.
0624
= CRC
Response:
01
03
20
xxxx
xxxx
xxxx
XXXX

01 03 20 xxxx .......xxxx XXXX (in HEX)
= Controller address
= the same as in query
= 20 in HEX = 32 in DEC = length of read data in Bytes (sixteen two-bytes items).
= the first alarm list item in HEX, interpretation see in Tab.13 (in Cfg Image – see
“How to create actual Communication object list chapter).
= the second alarm list item, unsigned integer 16
= the 16-th alarm list item
= CRC

Hint:
Bits xxxx are arranged in the following way: 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24….

Engine State Reading
Means state of controller state machine.
State machine request: 01 03 24 1C 00 01 4F 3C
01
03
241C
0001
4F3C
Response:
01
03
02
0001
7984

(in HEX)

= Controller address
= Modbus function number (reading)
= 241C in HEX = 9244 in DEC = State machine object number (InteliSys only).
= 1 in HEX = 1in DEC = communication object length expressed by the number of Modbus
registers.
= CRC
01 03 02 0001 7984 (in HEX)
= Controller address
= the same as in query
= 2 in HEX = 2 in DEC = length of read data in Bytes.
= „Not ready“ state code.
= CRC

Setpoint Adjusting
Set Gear teeth to 126
Gear teeth setpoint is password protected,
Password = 1234,
Controller address=1
1-st step Password setting
2-rd step Data writing
Password setting command (in HEX):
01 10 5FCC 0001 02 04D2 9A04
01
10

= Controller address 1
= Function code 16 = 10 HEX

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

77

5FCC
0001
02
04D2
9A04

= Write password setting object number = 24524 = 5FCC HEX see Object list description.
= Communication object length expressed by the number of Modbus registers. See
Appendix Tab4. Setpoints, object 8252, type unsigned, Len=2 means Unsigned16. In table
Data types see for Unsigned16 is length of Modbus register = 1.
= Length of written data (Modbus registers * 2)
= Password = 1234 in DEC = 04D2 in HEX
= CRC

Standard response (in HEX):
01 10 5FCC 0001 D3E2
01
= Controller address 1
10
= Function code 16 = 10 HEX
5FCC
= Write password setting object number = 24524 in DEC
0001
= Communication object length expressed by the number of Modbus registers.
D3E2
= CRC
Data (setpoint Gear teeth) writing command (in HEX):
01 10 203C 0001 02 007E 028E
01
10
203C
0001

02
007E
028E

= Controller address 1
= Function code 16 = 10 HEX
= Gear teeth object number = 8252 in DEC = 203C in HEX
= Communication object length expressed by the number of Modbus registers. See Tab4.
Setpoints, object 8252, type unsigned, Len=2 means unsigned16. In table Data types see
unsigned16 is length of Modbus register = 1 (in Cfg Image – see chapter:
“How to create actual Communication object list”).
= Length of written data (Modbus register * 2)
= Gear teeth = 126 in DEC = 007E in HEX
= CRC

Standard response (in HEX):
01 10 203C 0001 CA05
01
= Controller address 1
10
= Function code 16 = 10 HEX
203C
= Gear teeth object number = 8252 in DEC = 203C in HEX
0001
= Communication object length expressed by the number of Modbus registers.
CA05
= CRC

Reading access attributes of all users from IGS-NT
Reading of access attributes of all users. Actual setting is following:

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

78

Request: 01 03 5F 87 00 01 26 37
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
5F 87
= Register address: 24455 DEC = 5F87 HEX
00 01
= Number of registers (
26 37
= CRC
Response: 01 03 08 FF FF 0F 0F 07 01 00 00 D1 96
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
08
= Length of read data in Bytes (in HEX)
FF
= Access levels of user U0
FF
= Access levels of user U1
0F
= Access levels of user U2
0F
= Access levels of user U3
07
= Access levels of user U4
01
= Access levels of user U5
00
= Access levels of user U6
00
= Access levels of user U7
35 64
= CRC

Gen-set commands
Use Commands codes from this Communication guide, see Action.
Example for Engine start command:
Request
01
06
5FC9
FE01
CA40

= Controller address
= Modbus Write single register command Data writing
= 5FC9 HEX = 24521 DEC = Command register, see Action
= Start command according Table Action (MSB, LSB)
= CRC

Response
01
06
5FC9
FE01
CBF0

= Controller address
= Modbus Write single register command Data writing
= 5FC9 HEX = 24521 DEC = Command register, see Action
= Start command according Table Action (MSB, LSB)
= CRC

IG/IS-NT Register Oriented Modbus Communication Examples
Values reading
Reading of oil pressure, water temperature and fuel level values:
Request: 01 03 00 0F 00 03 35 C8
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
00 0F
= Register address: Register number (40016) – 40001 = 15 = 0F HEX
00 03
= Number of registers (40016 – Oil press, 40017 – Water temp, 40018 – Fuel level)
35 C8
= CRC
Response: 01 03 06 00 27 00 2E 00 2B 35 64
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
06
= Length of read data in Bytes (in HEX)
00 27
= 27 in HEX = 39 in DEC => 3,9 Bar (Oil pressure is represented with 1 decimal in Bars)
00 2E
= 2E in HEX = 46 in DEC => 46°C (Water temperature is represented with 0 decimals in °C)
00 2B
= 2B in HEX = 43 in DEC => 43% (Fuel level is represented with 0 decimals in %)
35 64
= CRC

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

79

Adjusting setpoints
Before adjusting a protected setpoint, the user must be selected and his password must be set:
User selection:
Request: 01 06 18 DA 00 00 EC 0C
01
= Controller address
06
= Modbus function number (Write Single Register)
18 DA
= Register address: Register number (46363) – 40001 = 6362 = 18DA HEX
00 00
= User 0
EC 0C
= CRC
Writing password: 01 06 18 DB 00 00 D1 CC
01
= Controller address
06
= Modbus function number (Write Single Register)
18 DA
= Register address: Register number (46364) – 40001 = 6363 = 18DB HEX
00 00
= Password = 0
D1 CC
= CRC
Adjusting setpoints from Engine params group – Starting RPM and Starting Poil:
01 10 0B D7 00 02 01 F4 00 14 33 7D
01
= Controller address
10
= Modbus function number (Write Multiple Registers)
0B D7
= Register address of the first setpoint: Register number (43032) – 40001 = 3031 = 0BD7
HEX
00 02
= Number of registers
01 F4
= New setpoint value (Starting RPM = 500 RPM – entered value = 500, 0 Dec according to
configuration image)
00 14 = New setpoint value (Starting Poil = 2.0 Bar – entered value = 20, 0 Dec according to
configuration image)
33 7D
= CRC

Start command, see List of commands
a) Start command in two steps
To start the engine it is necessary to enter an appropriate user and his password first to enable commands, if
these are protected by level 1-7.
First an argument must be written to the controller:
01 10 18 D6 00 02 04 01 FE 00 00 A4 C9
01
= Controller address
10
= Modbus function number (Write Multiple Register)
18 D6
= Register address for command argument (46359 – 40001 = 6358 = 18D6 HEX)
00 02
= Number of registers
04
= Number of bytes that will be written
01 FE 00 00
= Command argument (see List of commands)
A4 C9
= CRC
Then the start command must be written:
01 06 18 D8 00 01 CE 91
01
= Controller address
06
= Modbus function number (Write Single Register)
18 D8
= Register address for command (46361 – 40001 = 6360 = 18D8 HEX)
00 01
= Command (see List of commands)
CE 91
= CRC
b) Start command in one step
Engine start:
01 10 18 D6 00 03 06 01 FE 00 00 00 01 95 53
01
= controller address
10
= Modbus command
18D6
= 6538 object for engine commands ... (46359 – 40001 = 6358 = 18D6 HEX)
0003
= number of modbus registers
06
= data length in bytes
01FE0000
= argument for engine start - see in (1) - List of commands
0001
= Command number - see in (1) - List of commands - 1st column.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

80

9553

= CRC

Alarm list reading
Reading of the first record in the alarm list:
Request: 01 03 1A 0C 00 19 43 1B
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
1A 0C
= Register address of the first alarm list record (46669 – 40001 = 6668 = 1A0C HEX)
00 19
= Number of registers (25)
43 1B
= CRC
Response: 01 03 32 21 2A 45 6D 65 72 67 65 6E 63 79 20 73 74 6F 70 00 … 00 25 A0
01
= Controller address
03
= Modbus function number (Write Single Register)´
32
= Length of read data in Bytes (in HEX)
21 2A 45 6D 65 72 67 65 6E 63 79 20 73 74 6F 70 = !*Emergency stop (active, not accepted alarm)
25 A0
= CRC

History reading
First an index of history record must be entered:
01 06 18 D4 00 00 CF 52
01
= Controller address
06
= Modbus function number (Write Single Register)
18 D4
= Register address of the history index (46357 – 40001 = 6356 = 18D4 HEX)
00 00
= First history record (index = 0)
CF 52
= CRC
Reading of history record header:
Request: 01 03 19 5C 00 32 03 51
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
19 5C
= Register address of history record header (46493 – 40001 = 6492 = 195C HEX)
00 32
= Number of registers (50)
03 51
= CRC
Response: 54 65 72 6D 69 6E 61 6C 20 … 20 30 34
54 65 72 6D 69 6E 61 6C
= Terminal
20 20 ...
= Space
30 34
= CRC
Reading of the data part of history record:
Request: 01 03 19 8E 00 7D E2 9C
01
= Controller address
03
= Modbus function number (Read Multiple Registers)
19 8E
= Register address of history record header (46543 – 40001 = 6542 = 198E HEX)
00 7D
= Number of registers (125)
E2 9C
= CRC
Response: 55 41 52 54 31 20 43 6F 6E 6E 65 63 74 65 64 00 …. 00
55 41 52 54 31 20 43 6F 6E 6E 65 63 74 65 64 = UART1 Connected

Set and reset of RemoteControl1 binary output
First it is necessary to enter an appropriate user and his password first to enable commands, if these are
protected by level 1-7.
First an argument must be written to the controller:
01 10 18 D6 00 02 04 00 20 00 01 14 D3
01
= Controller address
10
= Modbus function number (Write Multiple Register)
18 D6
= Register address for command argument (46359 – 40001 = 6358 = 18D6 HEX)
00 02
= Number of registers
04
= Number bytes that will be written
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

81

00 20 00 01 = Command argument (see List of commands) – 00 20 – set the output, 00 01 –
RemoteControl1 binary output
14 D3
= CRC
Then the command (26) must be written:
01 06 18 D8 00 1A 8E 9A
01
= Controller address
06
= Modbus function number (Write Single Register)
18 D8
= Register address for command (46361 – 40001 = 6360 = 18D8 HEX)
00 1A
= Command (see List of commands)
8E 9A
= CRC
It is possible to write command in one message:
01 10 18 D6 00 03 06 00 10 00 01 00 1A 6D 5E
01
= Controller address
10
= Modbus function number (Write Multiple Register)
18 D6
= Register address for command argument (46359 – 40001 = 6358 = 18D6 HEX)
00 03
= Number of registers
06
= Number bytes that will be written
00 10 00 01
= Command argument (see List of commands) – 00 10 – reset the output, 00 01 –
RemoteControl1 binary output
00 1A
= Command (see List of commands)
6D 5E
= CRC

Setting of Pulse Counter to 1,000,000,000 (IS-NT only)
Setting of Pulse Counter to 1,000,000,000:
01 10 18 D6 00 03 06 01 90 00 02 00 1F 5E 11
01
= controller address
10
= Modbus command
18D6
= 6538 object for engine commands ... (46359 – 40001 = 6358 = 18D6 HEX)
0003
= number of modbus registers
06
= data length in bytes
3B9A CA00
= 1,000,000,000 = 3B9A CA00 HEX - new value - argument to be written - see in (31)
- List of commands
001F
= Command number - see in (31) - List of commands - 1st column.
5E 11
= CRC

Setting of External Value to 400 (IS-NT only)
Setting of Ext Value 2:
01 10 18 D6 00 03 06 01 90 00 02 00 23 04 9C
01
= controller address
10
= Modbus command
18D6
= 6538 object for engine commands ... (46359 – 40001 = 6358 = 18D6 HEX)
0003
= number of modbus registers
06
= data length in bytes
0190 0002
= 400 = 0190 HEX - upper value - argument to be written - see in (36) - List of commands
0024
= Command number - see in (36) - List of commands - 1st column.
04 9C
= CRC
Note:
If at least one of the binary inputs ExtValueX up / ExtValueX down is configured for a particular ExtValueX,
then the modbus commands of external setting of ExtValueX are to be ignored.
Note:
ComAp believes that all information provided herein is correct and reliable and reserves the right to update
at any time. ComAp does not assume any responsibility for its use unless otherwise expressly undertaken.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

82

I-LB, IG-IB Communication Units
Local Bridge I-LB
Local Bridge I-LB provides connection of up to 32 InteliGen, InteliSys - NT or InteliDrive controllers.
If I-LB not available, IG-MU can be used to cover most of the I-LB functionality.

Modem support
I-LB supports Hayes compatible analog modems with baud rate 9600bps, 19200bps and 38400bps.
I-LB supports GSM modems witch baud rate 9600bps or 19200bps. Recommended GSM modems:
• Siemens M20, TC35
• Wavecom M1200/WMOD2
• FALCOM A2D
Recommended ISDN modem: Askey TAS-200E
I-LB current SW version supports:
• Analog modem Hayes compatible,
• ISDN ASKEY modem,
• GSM modem for data communication (Siemens M20, TC35 Wavecom M1200/WMOD2)
• Direct connection to PC via RS232, RS485
• I-LB+ version additionally supports USB connection
• Modbus protocol,
• Capability to connect up to four I-LB on one CAN bus (two as local bridge, two as modem bridge),
• Serve active call requested by controllers InteliGen / InteliSys – NT, InteliDrive,
• Send active SMS, receive and serve SMS via GSM modem.
• I-LB reads Number of rings setpoint from controller of lowest address during switch on and each 20
minutes (Number of rings change is not accepted immediately).
Hint:
Check I-LB sw version in InteliMonitor -> Monitor -> Controller/Archive info.
If I-LB SW version is displayed in Multiedit About window, it is shown as IG-MU v.2.2 due to backward
compatibility reasons.
The latest I-LB and IG-IB sw version description see in document HW-SW versions.

RxC

120≅

120≅

I-LB Terminals and jumpers
RxD
P7

TxC

TxD

Tx
Rx

Indication LED:
TxC, RxC
TxD, RxD
RUN
PWR

P13 P14 P15 P16 P17 P18

D2

D1

Indicates data transfer on the CAN line.
Indicates data transfer on the RS232 line.
Lights when at least one other unit is active on the CAN bus.
Blinks when no unit is communicated on the CAN bus (during detection).
Lights All the time when power supply is switched on.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

83

Jumper
P18

Note
Place jumper when I-LB is connected for modem
communication
P17
ADR1/ADR2
Place jumper to choose address 2 (for local or modem
connection).
P16
ComAp/Modbus Place jumper for Modbus communication.
P15
HW/SW control Place jumper if the modem doesn’t provide active DSR
signal.
P13/P14 Modbus rate
Place jumpers to select Modbus communication speed.
P1/P2
CAN/RS485
Place jumper to connect 120Ω terminating resistor for CAN
120Ω
bus/RS485
P7
RS485/RS232 Place jumper to select RS485 or RS232connection
Direct/Modem

Default setting
Opened
Opened
Opened
Opened
Opened
Opened
Opened

Hint:
Other I-LB jumpers are designed exclusively for factory tests.

IG-IB Internet Bridge
If more than 8 IGS-NT or other controllers are used with intercontroller CAN bus and monitored via IG-IB
or I-LB units, the reaction on commands issued from InteliMonitor or other monitoring SW can be delayed up
to several seconds. The same holds for values reading, i.e. refresh of measured power etc. in InteliMonitor
or other PC SW.
Hint:
Contact local IT manager in any case before using iG-IB.

Indication and Diagnostic LED’s
7 8

ETHERNET

LED

iG-IB

IG-CU
DONGLE

1 2
MODEM
IB CONFIG

LED

3 4
CAN

5 6
9 10

LED 1,2
LED 3,4
LED 5, 6
LED 7
LED 8
LED 9,10
LED 11

11

LED

POWER

Mode of iG-IB operation - see the table below
Modem / Config line Rx, Tx activity
IG-CU data Rx, Tx activity
Ethernet LINK (connection)
Ethernet ACT (activity)
CAN interface activity
POWER supply indication

LED1

LED2

IG-IB V2.0

Light

Dark

After power switch on = iG-IB hardware fail.
Unit has to be sent to repair.
Wrong configuration, iG-IB must be configured by IBConfig
software tool 2.0
Active IBConfig software. iG-IB does not communicate to
ETHERNET or modem.
Invalid firmware or firmware downloading
E-mail data reading from controller
E-mail data sending to internet
OK running state

Blinks together
Lights both
Blinks alternately
Light
Dark
Dark
Light
Dark both

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

84

Fast 0,1s
blink
Slow 0,3s
blink

Dark

Modem initialization

Dark

CAN bus rate detection

Hint:
Maximal length of UTP cable must be smaller than 100m to the nearest Switch/hub according to IEEE802.3
(100Base-T)

IG-IB Configuration
It is necessary to configure unit before its first use because new IG-IB from factory is not configured.
Internet Bridge can be connected to Internet
via LAN – Ethernet connector or
via dial up – MODEM connector.
Maximal length of UTP cable (between IG-IB and Switching hub) is 100m according to IEEE 802.3.
Corresponding firmware must be downloaded to IG-IB depends on required connection type.
IG-IB interface
LAN – Ethernet
Dial up – Modem

Firmvare V2.5
IG-IB-ethn_2.5.bin
IG-IB-dial_2.5.bin

For IG-IB V2.5 firmware configuration use IG-IB configuration tool (IBConfig.exe) at least V1.2 or higher.
IBConfig of V1.2 can be used for IG-IB firmware 1.0 and 1.1 as well.
For IG-IB V2.1 firmware configuration use IBConfig at least V1.4 or higher.
Hint:
You cannot update firmware in IS-Display terminal by means of IG-IB version 2.0 and lower. Available
support for IGS-NT is in IG-IB 2.1 and higher. In case you use 2.0 version, the message appears (Access
not allowed (object 24431)) because IG-IB is not able to work with IS-Display.
IG – IB jumpers:
The hardware jumpers have following meaning:
P1 – test mode – should be disconnected!
P2 – internal use – should be disconnected!
P3 – reset – should be disconnected!
Connect
iG-IB power supply,
“MODEM/IB CONFIG” RS232 interface cable to PC and
Run
software.

… \ ComAp \ TOOLS \ IBConfig \

ETHERNET

RS232

LED

3 4
CAN

iG-IB

IG-CU
DONGLE

PC

1 2

MODEM
IB CONFIG

LED

5 6

LED

POWER

Set COM port:

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

85

Set following items in IB configuration window.

Ethernet LAN Configuration

Please notice:
Setting CAN-Addr.1 was interchanged with setting CAN-Addr.2 starting with IBConfig-1.6. It means
that IG-IB’s CAN address has to be set to CAN-Addr.2, if I-LB which is set to the address ADR1 is connected
to the same CAN bus as IG-IB. Use option CAN-Addr.1 if I-LB is set to ADR2.
It is necessary to set IG-IB's CAN address using IBConfig-1.5 in this way: IG-IB’s CAN address has to be set
to CAN-Addr.1, if I-LB which is set to the address ADR1 is connected to the same CAN bus as IG-IB. Use
option CAN-Addr.2 if I-LB is set to ADR2.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

86

1

IG-IB

2
3

Gateway
Terminal IP
Addresses

IP Address
Netmask
MAC Address
Port Number
IP Address
Don’t check

4

Firmware

5

Interface

6

Message
window

7

Domain
Name
Servers
E-mail

8

9

Access
Code

RS232
CAN1
CAN2

Primary DNS
Secondary DNS
SMTP Server
IG-IB Mailbox

Ask your IT manager
Ask your IT manager
Ask your IT manager
Ask your IT manager
Ask your IT manager
Connection will be restricted to these terminal IP addresses, i.e. IGIB won’t connect to any other address.
Tick “Don’t check” if you want to allow connection to all terminal IP
addresses.
Firmware file name (*.bin) is displayed in this window when old iGIB firmware version is detected.
It is possible to select any iG-IB “*.bin“ firmware file using Locate
button.
iG-IB firmware is located in WinEdit directory \Program
files\Comap\WinEdit\Tools\IBConfig\Firmware\ *.bin.
If you check “Don’t program” checkbox, the firmware is not
downloaded (only settings).
Connection of IG-IB to controller via RS232
Connection of IG-IB to controller via CAN
Two IG-IB’s on CAN bus
Messages window contains messages regarding detected (actual)
firmware version and configuration validity.
Here you can also get information on configuration process.
If you get the “No response” message, check once more COM
setting and communication cable. If everything is OK and you still
get the “No response” message the unit must be reprogrammed in
the factory.
Get from your IT manager
Necessary only when Active e-mails are enabled in Controller. It is
used as a sender address when iG-IB sends active e-mail.
See Setpoints Act.cals/SMS: AcallCHxType = E-MAIL or EMLSMS.
Code for unblocking the remote communication with the controller.
Use InteliMonitor/DriveMonitor to enter or change access code.

IG-IB connection to internet (Ethernet)
Hint:
Your local LAN connection to the Internet is probably configured to enable access the servers located on the
Internet, but to disable access in the reverse direction.
If iG-IB is to be visible from the Internet, then your IT manager should create a communication channel on
the Internet access server.
The iG-IB uses the TCP-communication and listens at the port 23 (known as Telnet port).
Hint:
Some providers have strict requirements for e-mail iG-IB Mailbox address = existing mailbox.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

87

Dialup Connection Configuration
Use firmware V2.0 and higher for dialup connection.

Connection to ISP
There are two Internet Service Provider sets
and
.
Phone number is dialed using ATD command. The main ISP is dialed as first. The backup ISP is dialed
when it is not possible to open the main ISP connection.
IP addresses for DNS servers can be obtained from ISP (“Get from ISP”) or explicitly set in configuration.

Modem initialization
Modem must accept following ASCII characters: Escape = ASCII 43 (=character +), ASCI 13 (= CR) and
ASCII 10 (= LF). Then Following commands are sent to Modem.
1. ATZ
2. ATE0V0Q0S0=0
3. ATV0Q0X0S0=1

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

88

Active e-mail
Active e-mail can be sent only when operating modem is detected. IG-IB makes five open connection
attempts on active e-mail request. There are three attempts to sent e-mail when connection is opened.
Connection is opened for “Connection holding time” after e-mail is successfully sent.
Note for iG-IB firmware version 1.0 or 1.1 users: active e-mail sending may fail if selected SMTP server
returns a multiline responses. Use firmware version 2.0 to solve this problem.
Configuration items
1
2

3

Internet
Service
Provider
Modem

Phone Number
User Name
Password
Use RTS/CTS
Flow Control

Only when velocity auto detect is not active.

Extra Setting

RS232

Those “special” commands for modem configuration are sent to
modem during init procedure.
Connection will be restricted to these terminal IP addresses, i.e. IGIB won’t connect to any other address.
Tick “Don’t check” if you want to allow connection to all terminal IP
addresses.
Firmware file name (*.bin) is displayed in this window when old iGIB firmware version is detected
Connection to controller

CAN1

Connection to controller

CAN2

Two IG-IB’s on CAN bus
Messages window contains messages regarding detected (actual)
firmware version and configuration validity. Here you can also get
information on configuration process.
Get from your IT manager

Don’t check
Firmware

5

Interface

6

Messages
window

7

Domain
Name
Servers
E-mail

8

Get from ISP
Primary DNS
Secondary DNS
SMTP Server
IG-IB mail box

Connection
Holding Time
Keep Permanent
Connection

9

Access
Code

Check if the modem requires RTS/CTS signals.

Velocity

Terminal IP
Addresses

4

Data from local Internet provider

E-mail setting is necessary only when Active e-mails are enabled in
Controller. It is used as a sender address when iG-IB sends active
e-mail.
After e-mail is successfully sent, waiting for operator response.
If checked connection to ISP is never terminated.
It is established immediately after IG-IB is initialized. If the
communication is interrupted, it is re-established. It is necessary
that the IP address of IG-IB is static so that the PC software (e.g.
WinEdit) “knows” to which address to re-connect.
If this option is not selected, the connection to ISP is established on
request from terminal only. IP address obtained from ISP is then
sent to the terminal via email (IP address can be dynamic in this
case).
Code for unblocking the remote communication with the controller.
Use InteliMonitor/DriveMonitor to enter or change access code.

Hint:
Some providers have strict requirements for e-mail iG-IB Mailbox address = existing mailbox.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

89

IG-IB Interface
There are following connectors on iG-IB unit:
Modem / IB Config
Dongle
CAN bus
Ethernet to LAN

RS232 interface for iG-IB configuration or
Modem connection (not supported in SW version1.0)
RS232 interface to Controller or
for Dongle for multiple controllers communication (controller data are
transferred via CAN bus)
Interface to one or group of controllers (IG/IS-NT, ID)
Interface to Ethernet

IG-IB Dongle
IG-IB Dongle limits number of accessible controllers.
Following addresses must be used for given dongle type (e.g. dongle IG-IB3 enables connection to
controllers with addresses 1,2 and 3 only).
Dongle type
No dongle
Dongle IG-IB3
Dongle IG-IB7
Dongle IG-IB15
Dongle IG-IB32

Number of accessible controllers
1
2 to 3
2 to 7
2 to 15
2 to 32

Hint:
From IG-IB-2.1 the dongle sets the limit of number of connected controllers (no specific order is required). If
the controller is connected via RS232, the address 1 is supposed.

Internet Connection Diagnostics
Following method is Comap PC SW independent way how to check connection from PC via Internet to some
controller.
The basic diagnostic of iG-IB to internet connection could be done using telnet software:

1) Start telnet software
2) In telnet window write command „open xxx.xxx.xxx.xxx“
3) If the connection is OK, you should get a nontext (binary - firmware version) answer. Depending on
font you use in the telnet window correct message looks like:

the

Hint:
Telnet software is included in standard Windows installation. To run telnet use Windows Start – Run button
and write “telnet”, OK.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

90

How to Access IG-IB behind Firewall
The solution principle is shown in attached picture. All addresses in this text and in the picture are fictive and
will be different on real installation, port numbers are real. If the network software is configured as shown in
picture, users from Internet will be able to connect from Comap PC SW to address 195.122.194.89 and
communicate with IG-IB behind firewall. So in fact, we enter to PC SW different address than is configured in
IG-IB, as is correctly noted in the manual.
Needed changes are these:
1. DHCP server in private network (if used): exclude address 192.168.1.250 from the address poll which are
available to lease from this server, so that this address couldn't be assigned to any device in the network.
This will make this address available for use by IG-IB.
2. Firewall: Configure transparent proxy channel from external interface 195.122.194.89, port 23 to protected
network, internal address 192.168.1.250, port 23. This transparent proxy will do all network address
translation needed when communicating from public network with internal private network.
Port 23 on interface 195.122.194.89 should be usually free for this use, as normally is this port used for
telnet service and telnet is considered dangerous to use on firewalls.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

91

Modem Recommendations
The controller has to be connected to modem via standard modem cable where the DSR (Data Send Ready)
signal detects modem presence.
Hint:
It is recommended to use the same type of modem on the both sides (and PC) of connection.
For GSM modem proper set-up use automatic ComAp GSM set-up software from the installation package.
Setup software runs independently. In MS Windows select: Start - Program files – Comap – Tools –
Gm_setup.exe

Analog Modem with DC Supply
Devolo Microlink 56k I is designed for the industrial applications. Power supply range is 9 - 30 V AC and 9 42 V DC. See http://www.devolo.de/.

Recommended ISDN Modem
Askey TAS-200E (power supply 12 V DC)
ASUScom TA-220ST
Devolo Microlink ISDN i
Hint:
The ISDN modems must work in the X.75 or V.120 protocols. The internet connection (HDLC-PPP) does not
work.

Recommended CDMA Modem
Maxon MM-5100, 800MHz, 1xRTT
Hint:
The usage possibility depends on the network type. The only recommended CDMA modem above was
tested in Australia.

Recommended GSM Modems
Siemens M20, TC35, TC35i, ES75, MC39 (baud rate 9600 bps).
Wavecom M1200/WMOD2 (baud rate 9600 bps).
Wavecom - Maestro 20, dual 900/1800MHz.
Wavecom – Fastrack M1306B, dual 900/1800 MHz (Fastrack M1206B is NOT recommended)
FALCOM A2D, dual 900/1800MHz.

GSM modem wiring notes - InteliDrive
Modem communication of InteliDrive controllers and IG-IB is based on full modem cable connection where
all control signals RXD, TXD, GND, RTS, CTS, DSR and DCD are active and connected.
InteliDrive controllers automatically detect modem connection via RS232 - DSR (Data Set Ready) signal.
Controllers detect modem when DSR is active and direct connection when passive or not connected.
Any connected modem has to be set to active DSR after switch on and has to be connected via standard
modem cable.
Leave I-LB jumper “HW/SW control” opened for this connection.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

92

GSM modem wiring notes – IG/IS-NT
IG/IS-NT controllers provide a possibility to select whether a modem with active DSR signal (full modem
cable connection - RXD, TXD, GND, RTS, CTS, DSR and DCD control signals available) or without this
signal (3 wire connection – RxD, TxD and GND signals available) is connected.
In the controller the selection is done by Comms settings:RS232(1/2) mode setpoint.
Select MODEM (HW) for full cable connection or MODEM (SW) for 3 wire connection.
Place I-LB jumper “HW/SW control” when MODEM (SW) connection is selected.
Hint:
Make sure all signals are connected and activated in modem when it is not possible to open connection.
Some types of GSM module have jumpers select table control and handshaking signals.

TC35 Alphatech GSM modem: the first jumper from the left is closed.

GSM Modem setup
Prior to start work with GSM modem run following program for GSM proper setup.
Program writes all the necessary AT commands to configure the GSM modem properly for use with IG-CU or
IS-CU.
This program runs independent on other PC SW:
• Start MS Windows-Start-Program files – Comap – Tools – Gm_setup.exe.
• Select COM port
•
•
•

when GSM will be used with old iG-MU unit
Tick
Press Setup button
Follow commands in GSM Modem Setup window

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

93

Hint:
Selection “Modem will be used with old version of IG-MU (below 1.8)” sets GSM modem Baud rate to 38400
bps !!!
It is strongly recommended to use the same type of modem at both sides (IG and PC) of connection.
When modem TC35i does not respond for sending command SMSes, do the following:
1. Send AT+CPMS="MT","MT","MT" command via hyperterminal

or by means of RS232()MdmIni parameter.
2. Send AT+CPMS="SM","SM","SM" command via hyperterminal
or by means of RS232()MdmIni parameter.
3. Restart the modem.

Mobile Phone SIM Card Setting
Adjust SIM card on GSM modem in the following way:
• Enable data communication (it could be done by your local GSM operator),
• Set phone number SMS service center SC (recommended in international format in case of
roaming),
• Set no PIN code required.
Hint:
All SMS on SIM card will be erased during GSM modem initialization. Valid SMS on SIM card will be served
Except of adjusting and gen-set control command.
Both SIM cards must have DATA services enabled when communicating from controller to PC via two GSM
modems.

How to check SIM card DATA setting
•
•
•

Move SIM card from controller GSM modem to Mobile phone.
Call from WinEdit to this Mobile phone and check (on Mobil phone) DATA call indication of incoming
call.
If phone does not indicate DATA - solve this with your GSM operator.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

94

Converters
Converter RS232 ↔ RS485

PC

RS232
(not crossed)

ADAM
4520

A

DATA+
DATA-

B
RS485

SW1: 1 closed
(10bit)
SW2: 6 closed

IG/IS-NT
ID

I-LB
Jumper for
RS485
connected

General properties of RS232 to RS485 converters:
• Has to be set to passive DSR signal (when DSR connected) after switch on.
• No external data flow control signals are allowed – automatic data flow control required.

Recommended converters
•

•

External:
ADAM 4520,
ADVANTECH, (http://www.advantech.com/)
- DIN rail, automatic RS485 bus supervision, no external data flow
control signals, galvanic isolated, baud rate 19200 bps
- When communication is working the LED on ADAM 4520 is going
from full illumination to short darkness then again full illuminated
- When communication of IG-MU is working, PWR and RUN LEDs
full red illuminated; TxD and RxD flashing when transmitting
Internal for PC:
PCL-745B or PCL745S,
ADVANTECH, (http://www.advantech.com/)
(Dual port RS422/485 Interface card, automatic RS485 bus
supervision, no external data flow control signals, galvanic isolated,
baud rate 19200 bps)

Hint:
In the case of surge hazard (connection out of building in case of storm etc.) see the “Recommended
CAN/RS485 connection” chapter of the IGS-NT-2.2-Installation guide.pdf.

Converter 230 V AC ↔ TCP/IP
PC

ETHERNET

230 V∼

ETHERNET
ADAPTER
•
•
•

ETHERNET

IG-IB

CAN
RS232

IG/IS-NT
ID

ETHERNET
ADAPTER

For installations where IG-IB is used but internet connection is not available
The connection can be established using electric grid (230 V AC) using Ethernet/230VAC converters
Can be used for distances up to 200 meters

Recommended converter
•

Powerline Ethernet Wall Mount,
Corinex Communications (http://www.corinex.com/)

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

95

Example

230 V AC
Ethernet

Ethernet

CAN

Converter USB ↔ RS232
PC

•

USB

USB
RS232

RS232

IL,ID,
IG/IS-NT

Useful for PC/laptops without serial port

Recommended converters
•

•

•

UCAB232 Full,
ASIX (http://www.asix.cz/)
UCAB232 is designated for all standard RS232 devices (mouses,
modems, data terminals, barcode readers, serial printers) and
industrial applications. UCAB232 supports Baud rates from 300 Bd
to 250 kBaud (guaranteed) / 500 kBaud (typ.).
VPI - USS-101/111,
VPI (http://www.vpi.us/usb-serial.html)
Supports serial devices with speeds up to 230kb/sec (e.g. PDAs,
modems, scanners, etc.).
C-232-MM,
(http://www.usbgear.com/item_288.html)
The USB Serial Adapter provides instant connectivity with modems,
ISDN TAs, PDS, handheld & pocket PCs, digital cameras, POS,
serial printers, etc. It supports data rates up to 230 Kbps.

Converter USB ↔ RS485
PC
•

USB

USB
RS485

RS485

RS232

RS485
RS232

IL,ID,
IG/IS-NT

Extends distance between PC and controller up to 1200 meters

Recommended converter
•

SB485,
PaPouch elektronika
(http://www.papouch.com/)

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

96

Converter Modbus RTU ↔ TCP
Modbus
RTU
RS232

PC

RS485
RS422
Ethernet

Ethernet

IG/IS-NT
IS

Modbus
TCP

• For connecting of Modbus serial devices (e.g. Inteli controllers) to an Ethernet network

Converter RS-422/485 ↔ Ethernet
Recommended converter
• Nport 6110, MOXA (www.moxa.com)
• NPort 5110
• NPort 5130

Recommended settings
Nport6110
(Settings in Modbus Gateway Configurator – download from
http://web4.moxa.com/support/download.asp)
Card
Network settings
Modbus Settings
Advanced Modbus Settings

Modbus Serial Settings

Item
IP Configuration
Attached Serial Device type
Initial delay time
Auto Slave Unit ID
Character Timeout
Message Timeout
Modbus/TCP Exception
Interface Mode
Baud Rate
Parity
Data Bits
Stop Bit

Value
Static IP
Modbus RTU slave
1000
Enable
10
100
Yes
Select interface you are using
Select Baud rate you are using
None
8
1

Controller
IG/IS-NT
Comms settings: RS232(1) mode / RS232(2) mode* = MODBUS-DIRECT
Comms settings: RS232(1)MBCSpd / RS232(2)MBCSpd* = 9600 / 19200 / 38400
When using RS485 don’t forget to set also
Comms settings: RS485(1)conv. / RS485(2)conv.* = ENABLED
* Second RS232/485 port available only in IG-NTC/EEC and IS-NT.
IS-CU
Basic settings: RS232 mode = MODBUS
Only Baud rate 9600 bps available in IS-CU.
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

97

Isolator RS232
•
•

For galvanic separation of the line between Inteli controllers and PC
Useful when different ground potentials are present

Recommneded isolators
•

UC232,
PaPouch elektronika (http://www.papouch.com/)

The isolator UC232 can be used instead of UC232-7. The only difference is that UC232 needs external
power supply. It can be 5V stabilized or 7-17V unstabilized. The power supply voltage must be specified in
the order. Suitable 5V power supply is also available from the Papouch company.
•

UC UC232-7,
PaPouch elektronika (http://www.papouch.com/)

Recommended optical USB extension cables
•
•

Opticis M2-100-xx http://opticis.com
USB Rover 200 http://www.icron.com

Radio Link
PC

PC

ETHERNET

RS232

RL-2400E

ADAM
4571

1 km

RL-2400E

ETHERNET

IG-IB

ETHERNET RL-2400E
1 km
RL-2400E ETHERNET ADAM
4571

•
•

RS232 IG/IS-NT
ID

RS232

IG/IS-NT
ID
IL

Useful when the control room is distant from the site
Can be more economical than to hard wire it

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf
e–06-2008.pdf

98

Recommended equipment
•
•
•
•

RadioLinx RL-2400E wireless Ethernet switch, ProSoft Technology Inc.
(www.prosoft-technology.com)
ADAM-4571, ADVANTECH (www.advantech.com)
MOXA DE311, MOXA (www.moxa.com)
MOXA Nport 5230, MOXA

Converter Modbus RTU ↔ SNMP
Modbus
RTU
RS485

SNMP
manager

Ethernet

IGS-NT

Ethernet

IGS-NT

SNMP

IGS-NT

• For connection of 1-32 IG/IS-NT (stadard line) controllers to a SNMP supervision system
• Supports GET, SET, TRAP transactions

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

99

MIB Table
The MIB table contains following data objects
Read only:
Modbus
Register(s)

Com.Obj.

Name

Dim

Type*

40003

8253

Binary inputs

Binary16

40012

8239

Binary outputs

Binary16
V

Decimals

40013

8213

Ubat

Integer16

1

40016

9155

Analog inp. 1 CU

Integer16

1

40017

9156

Analog inp. 2 CU

Integer16

0

40018

9157

Analog inp. 3 CU

Integer16

0

40168

9574

ControllerMode

Unsigned16

-

40249

8192

Gen V L1-N

V

Unsigned16

0

40250

8193

Gen V L2-N

V

Unsigned16

0

40251

8194

Gen V L3-N

V

Unsigned16

0

Hz

40256

8210

Gen freq

Unsigned16

1

40261

8204

Pwr factor

Integer16

2

40262

8395

Load char

Char

40264

8202

Act power

kW

Integer16

0

40288

8195

Mains V L1-N

V

Unsigned16

0

40289

8196

Mains V L2-N

V

Unsigned16

0

40290

8197

Mains V L3-N

V

Unsigned16

0

Hz

Unsigned16

1

Unsigned16

0

Integer 32

0

40296

8211

Mains freq

43589

8207

Num starts

43587

8206

Run hours

h

46354

Num items alarmlist

Unsigned16

46669

Item 1 alarmlist

String

46694

Item 2 alarmlist

String

46719

Item 3 alarmlist

String

46744

Item 4 alarmlist

String

46769

Item 5 alarmlist

String

46794

Item 6 alarmlist

String

46819

Item 7 alarmlist

String

46844

Item 8 alarmlist

String

46869

Item 9 alarmlist

String

46894

Item 10 alarmlist

String

46919

Item 11 alarmlist

String

46944

Item 12 alarmlist

String

46969

Item 13 alarmlist

String

46994

Item 14 alarmlist

String

47019

Item 15 alarmlist

String

47044

Item 16 alarmlist

String

ControllerMode

Unsigned16

Action argument

Integer32

User identification number

Unsigned16

Read / Write
43027

8315

46359

Write only
24470

24470

24524

24524

46361

Password

Unsigned16

Action command

Unsigned16

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

100

* SNMI data types are INTEGER32 for all numerical values except “Run hours”, which is GAUGE32. The column “Type” means how
the data shall be interpreted.

Converter settings
Setup of the converter is done via TELNET at port 9999 instead of standard port 21. The default IP address
is 192.168.1.254.
To enter setup mode:
1. Connect the converter to LAN
2. Put command “telnet 192.168.1.254 9999” to the windows command line on any computer
connected to the same LAN
Setup procedure:
1. Press “0” key to change server configuration (converter IP address, netmask, gateway address etc..)
2. Press “1” key to change device configuration (read/write community, SNMP manager address*..)
3. Press “9” key to save parameters to the memory and exit setup mode
*SNMP manager address is IP address of the device the TRAPs are addressed to.

Controller settings
IG/IS-NT
Comms settings: RS232(1) mode / RS232(2) mode* = MODBUS-DIRECT
Comms settings: RS232(1)MBCSpd / RS232(2)MBCSpd* = 57600
Comms settings: RS485(1)conv. / RS485(2)conv.* = ENABLED
* Second RS232/485 port available only in IG-NTC/EEC and IS-NT.
Hint:
The converter provides communication only with controllers (addresses) that are present on startup of the
converter. It means any controller powered-up later than the converter is not recognized and supported.
The converters are supposed to work with IG/IS-NT controllers of standard line (version 2.1 and higher).

Converter Modbus RTU ↔ Profibus

IGS-NT

(RS232)
Profibus

IGS-NT

Profibus DP

Modbus
RTU
RS485

Profibus
Master

IGS-NT

• For connection of 1-32 NT line controllers to a Profibus network
• RS485 or RS232 physical layer for connection to the controller(s)
• Full Profibus-DP slave functionality according IEC61158
InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

101

•
•
•
•

244 bytes input data size (122 Modbus registers)
244 bytes output data size (122 Modbus registers)
416 bytes total
See deatils on the web page of the manufacturer:
http://www.geindustrial.com/cwc/Dispatcher?REQUEST=PRODUCTS&pnlid=6&id=p485

Converter settings
• Use EnerVista software to setup the converter. It can be downloaded from the web page
http://pm.geindustrial.com/download/download.asp?id=p485&file=1.
• To configure the converter in the Profibus network, download the description file
http://www.geindustrial.com/products/software/d485/P48509E5.zip and import it to the Profibus
configuration tool.
Follow instructions in the P485 manual while configuring the converter. The setup wizard incorporated in
the Enervista software will make the setup process much easier, but finally some manual corrections
are needed. Below are some notes specific to the connection with ComAp controllers.
1. The physical layer for Modbus communication is select table. The selected type
(RS232/RS485) and speed must be same in the P485 and controller, see Controller settings.
2. Use RS485 in case more controllers are connected to the P485.
3. A Device mentioned in the wizard represents a controller type (IG-NT, IM-NT, IS-NT). Once a
device is defined, more nodes of the same type (device) can be created easily.
4. A modbus network node represents a controller. The slave address must correspond to the
Controller address setpoint of the related controller.
5. See Modbus Connection chapter in this document for details about Modbus, register numbers,
sizes etc.
6. Use triggered update mode for writing objects (registers) to the controller. Never use
cyclic update mode!
Setup example (using wizard):
1. Select wizard.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

102

2. Select fieldbus type.

3. Select physical layer and communication parameters for Modbus.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

103

4. Define IGS-NT Device, it’s Parameters and related Modbus registers.

5. Define nodes connected to the Modbus network.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

104

6. For each node select parameters that have to be mapped to the Profibus network.

7. Save the configuration overview (the picture below is only a general example, not a real one).

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

105

8. The configuration using wizard is finished.

9. Save the configuration to a file.
10. Navigation window will appear:

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

106

11. For each write-type parameter modify the property Update mode to triggered mode and define trigger
byte address. The Profibus master must update the parameter data field first and then increase the
trigger byte value to write the parameter (register) to the controller.

12. Write the configuration to the P485 and save it also to disk as backup.

Controller settings
IG/IS-NT
Comms settings: RS232(1) mode / RS232(2) mode* = MODBUS-DIRECT
Comms settings: RS232(1)MBCSpd / RS232(2)MBCSpd* = according to converter setting
Comms settings: RS485(1)conv. / RS485(2)conv.* = according the converter setting
* Second RS232/485 port available only in IG-NTC/EEC and IS-NT.

InteliCommunicationGuide, ©ComAp – June 2008
InteliCommunicationGuide–06-2008.pdf

107



---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : Yes
Tagged PDF                      : Yes
XMP Toolkit                     : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:14:39
Producer                        : Acrobat Distiller 8.0.0 (Windows)
Company                         : doma
Source Modified                 : D:20080627140534
Creator Tool                    : Acrobat PDFMaker 8.0 pro Word
Modify Date                     : 2008:06:27 16:11:54+02:00
Create Date                     : 2008:06:27 16:08:47+02:00
Metadata Date                   : 2008:06:27 16:11:54+02:00
Document ID                     : uuid:87dbf273-dcf5-4cf9-a17c-7e9119acef7b
Instance ID                     : uuid:d4c9e0b7-1a7f-41a0-91dc-f230e8a01d36
Subject                         : 136
Format                          : application/pdf
Creator                         : Ladislav Kadanik
Title                           : 
Page Count                      : 107
Page Layout                     : OneColumn
Author                          : Ladislav Kadanik

EXIF Metadata provided by EXIF.tools