Before installing or starting this unit for the first
time, this manual should be studied carefully to
obtain a working knowledge of the unit and or the
duties to be performed while operating and
maintaining the unit.
RETAIN THIS MANUAL WITH UNIT. This Technical
manual contains IMPORTANT SAFETY DATA and
should be kept with the unit at all times.
Before installing or operating theX-IRI GATEWAY, take
time to carefully read all the instructions contained
in this manual, all compressor manuals, and all
manuals of any other peripheral devices that may be
installed or connected to the unit.
Electricity and compressed air have the potential to
cause severe personal injury or property damage.
The operator should use common sense and good
working practices while operating and maintaining
this system. All applicable codes should be strictly
adhered to.
Maintenance must be performed by adequately
qualified personnel that are equipped with the
proper tools.
INSTALLATION
Installation work must only be carried out by a
competent person under qualified supervision.
A fused isolation switch must be fitted between the
main power supply and the product.
The X-IRI GATEWAY should be mounted in such a
location as to allow operational and maintenance
access without obstruction or hazard and to allow
clear visibility of indicators at all times.
If raised platforms are required to provide access
to the X-IRI GATEWAY, they must not interfere with
normal operation or obstruct access. Platforms and
stairs should be of grid or plate construction with
safety rails on all open sides.
•
•
•
•
•
•
•
•
OPERATION
The X-IRI GATEWAY must only be operated by
competent personnel under qualified supervision.
Never remove or tamper with safety devices, guards
or insulation materials fitted to the X-IRI GATEWAY.
The X-IRI GATEWAY must only be operated at
the supply voltage and frequency for which it is
designed.
When main power is switched on, lethal voltages are
present in the electrical circuits and extreme caution
must be exercised whenever it is necessary to carry
out any work on the unit.
Do not open access panels or touch electrical
components while voltage is applied unless it is
necessary for measurements, tests or adjustments.
Such work should be carried out only by a qualified
electrician equipped with the correct tools and
wearing appropriate protection against electrical
hazards.
All air compressors and/or other equipment
connected to the unit should have a warning sign
attached stating “THIS UNIT MAY START WITHOUT
WARNING” next to the display panel.
If an air compressor and/or other equipment
connected to the unit is to be started remotely,
attach two warning signs to the equipment stating
“THIS UNIT CAN BE STARTED REMOTELY”.
Attach one sign in a prominent location on the
outside of the equipment, and the other sign inside
the equipment control compartment.
•
•
•
•
•
•
•
The X-IRI Communication Gateway is designed to
in
terface the Intellisys Controllers on Ingersoll Rand
Compressors with a Distributed Control System (DCS),
Programmable Logic Controller (PLC), or any other
device that is capable of communicating using the
MODBUS RTU communications protocol.
SECTION 3 SAFETY PRECAUTIONS
SAFETY PRECAUTIONS
The X-IRI provides MODBUS connectivity to Ingersoll Rand controllers that do not have built-in MODBUS
capability. The X-IRI also provides address filtering and
communication buffering capabilities to protect the
integrity of the serial data network.
The X-IRI is designed to be DIN Rail mounted within the
compressor control gear enclosure but can alternatively
be mounted remotely within a separate enclosure.
3
MAINTENANCE AND REPAIR
M
aintenance, repairs or modifications must only
•
be carried out by competent personnel under
qualified supervision.
If replacement parts are required, use only genuine
•
parts from the original equipment manufacturer, or
an alternative approved source.
Carry out the following operations before opening
•
or removing any access panels or carrying out any
work on the X-IRI GATEWAY:
Isolate the X-IRI GATEWAY from the main
i.
electrical power supply. Lock the isolator in the
“OFF” position and remove the fuses.
Attach label to the isolator switch and to the
ii.
unit stating “WORK IN PROGRESS - DO NOT
APPLY VOLTAGE”. Do not switch on electrical
power or attempt to start the X-IRI GATEWAY if
such a warning label is attached.
Make sure that all instructions concerning
•
operation and maintenance are strictly followed
and that the complete unit, with all accessories and
safety devices, is kept in good working order.
The accuracy of sensor devices must be checked
•
on a regular basis. They must be calibrated when
acceptable tolerances are exceeded. Always ensure
any pressure within the compressed air system is
safely vented to atmosphere before attempting to
remove or install a sensor device.
•
The X-IRI GATEWAY must only be cleaned with a
damp cloth, using mild detergents if necessary.
Avoid the use of any substances containing
corrosive acids or alkalis.
Do not paint the control faceplate or obscure any
•
indicators, controls, instructions or warnings.
4
SECTION 4 COMPRESSOR CONNECTION AND CONTROL
Setting a MODBUS polling rate of less than 500
milliseconds will not cause a quicker response from X-IRI.
The PLC or DCS communicates to the X-IRI Gateway via
a two wire, RS-485 network utilizing the MODBUS RTU
protocol.
The X-IRI Gateway module is installed within the
compressor control cabinet and connected to the PLC or
DCS using Belden 9841 or equivalent RS-485 cable.
INTELLISYS SOFTWARE REQUIREMENTS
Each Intellisys controller must have its controller
software revision at or above a certain minimum level
to work with the IRI.
The machine types and required software EPROM
minimum version levels are listed below. Check the
machine to be connected to an IRI for the appropriate
EPROM. If the EPROM is not of the correct minimum
version level, the appropriate EPROM may be ordered
from your local Ingersoll Rand Distributor or Air Center.
Machine Type EPROM Minimum Version Level
SSR 50-450 Horsepower - 1 stage (Red Eye)2.3
SSR 50-450 Horsepower - 2 stage (Red Eye)2.3
SSR SG1.0
15-50 Horsepower1.4
Sierra 50-100 Horsepower (SE)1.2
Sierra 100-200 Horsepower (Red Eye)2.5
Sierra 125-400 HP SG1.0
Recip (Red Eye)1.6
Recip SG1.0
Nirvana SGN1.0
Nirvana SGNe CC2.0
Nirvana SGNe OF1.0
Pegasus1.0
ESA SE 22-150 KW1.6
When monitoring compressor data only, no options
are required to be installed in the Intellisys controller. If
machine control is desired, the Remote Start/Stop and
Sequence options must be installed and turned “On”.
COMPRESSOR CONNECTION AND CONTROL
T
he X-IRI Gateway module is designed to interface to
any Ingersoll Rand Intellisys controlled compressor. All
Ingersoll Rand compressors equipped with Intellisys
controllers must use this interface when communicating
with MODBUS masters.
The X-IRI gateway prevents the compressor controller
from seeing any communications that aren’t directed
toward the controller’s network address. Additionally, the
X-IRI will buffer communications so that the compressor
controller will not receive a command greater than once
every 500 milliseconds.
5
MODBUS RTU
A pause longer than 1.5 byte-times will render the
message invalid and it will be ignored.
Message data format is dependent on function and will
consist of a combination of the following elements:
1) Destination address (slave network address)
2) Function Code
3) Data start address (slave register start address)
4) Number of registers, number of bytes of data
5) Message data
6) CRC checksum
Message Destination Address
The ‘destination address’ must be correct for the ‘slave’
controller device for which the message is intended. An
address can be from 1 to 127 decimal (01Hex to 7FHex).
The SMG Box is transparent and addresses must be for the
destination ‘slave’ controller or unit. Each controller or unit
must be set with a unique address.
Slave
Address
Function
Code
Start
Address
Number of
Registers
CRC Check
Sum
220300 6F 00 02 F3 45
Slave Address = 22Hex = 34 Decimal
Message Function Codes
The message function code defines the required data
processing operation of the slave controller. Although
several types of message function codes are defined by
the MODBUS standard, only the message function code
types working directly with registers are implemented on
controller units:
03H Read Holding Register(s) – Read
06H Preset Single Register - Write
Slave
Address
Function
Code
Start
Address
Number of
Registers
CRC Check
Sum
220300 6F 00 02 F3 45
Function Code = 03 = Read Holding Register.
Any other message function code type will result in
an EXCEPTION response.
This document discusses generic MODBUS
communications and how to implement the software
specific ‘MODBUS Table’ information. MODBUS
communication formatting may differ from controller to
controller and you may require more than one ‘MODBUS
Table’.
Always check the software variant identification and
version number for a controller with the variant and
version of the ‘MODBUS Table’ supplied. In some instances
the information contained in a ‘MODBUS Table’ may not
be applicable to a controller installed with the same
software variant but a different version number.
General
MODBUS RTU (Remote Terminal Unit) is a master-slave
type protocol. An Intellisys Controller functions as the
slave device. Information requests or commands are
communicated from master to slave only through the
X-IRI.
The X-IRI will always respond to communications from a
remote master device in accordance with the MODBUS
RTU protocol standard.
The MODBUS protocol is used to communicate with
personal computers (PC), Programmable Logic Controllers
(PLC’s), or Distributed Control Systems (DCS) over the
Network port. The X-IRI only responds to two MODBUS
commands, Read Holding Register 03 (03 Hex) and Preset
Single Register 06 (06 Hex). (See Modicon MODBUS
Protocol Reference Guide, PI-MBUS-300 Rev. J or later, for
more details on MODBUS).
Communication Link
MODBUS is implemented using a two-wire RS485
industry standard communications link operating in
master-slave mode.
RS485 Serial Data Format
The RS485 MODBUS port is a 2-wire operating with an
asynchronous serial data format: 8 data bits / no parity / 1
or 2 stop bits (8,N,1 or 8,N,2) - transmitted at 9600 baud.
Message Data Format
The bytes of the MODBUS RTU message must be sent
in one message package. The RTU protocol allows for a
maximum pause of 1.5 byte-times between 2 consecutive
bytes of a message.
6
Message Data Start Address
Slave
Address
Function
Code
Start
Address
Number of
Registers
CRC Check
Sum
220300 6F 00 02 F3 45
Start Address = 6F = 40112
High-byte transmitted first followed by low-byte.
Message Data
The message data content depends on the message
function code type.
03H Read Holding Register(s)
The Number of Registers designates the 16bit integer
value that determines the size (in 16bit ‘word’ registers)
of the message data being requested. This is the number
of 16bit registers to read. This information is contained in
the ‘MODBUS Table’.
A maximum of 32 registers can be read at one time.
Slave
Address
Function
Code
Start
Address
Number of
Registers
CRC Check
Sum
220300 6F 00 02 F3 45
The example above is a request to read offline pressure
(register 40112) and online pressure (register 40113) from
X-IRI address 22(Hex)
06H Preset Single Register
The Data byte 0 byte 1 designates the value of the 16bit
integer word to be written to the Intellisys controller. This
information is contained in the ‘MODBUS Table’.
Slave
Address
Function
Code
Start
Address
DATA
byte0byte1
CRC Check
Sum
220600 6F 00 5F FE BC
The example above is a request to set offline pressure
(register 40112) to 95 through X-IRI address 22(Hex).
Message CRC Checksum
The CRC (Cyclical Redundancy Check) is a check-sum
generated by means of ‘A001H polynomial’.
Slave
Address
Function
Code
Start
Address
DATA
byte0byte1
CRC Check
Sum
220600 6F 00 5F FE BC
The CRC is two bytes containing a 16-bit binary value
(word). The CRC value is calculated by the transmitting
device that appends the CRC to the end of the message.
The receiving device recalculates the CRC value prior
to processing of a received message and compares the
result to the actual CRC value appended to the message.
If the two values do not match the message is regarded
as invalid.
The CRC is initiated by first preloading a 16bit register
to all 1’s (FFFF Hex). Then a process begins of applying
each consecutive 8bit byte of the message to the register
contents using an exclusive ‘OR’ calculation. The result is
shifted one bit in the direction of the least significant bit
(LSB), with the most significant bit (MSB) set at ‘0’. The LSB
is then examined; if ‘1’ the register content is applied to
the polynomial value ‘A001’ Hex (1010 0000 0000 0001)
using an exclusive ‘OR’ calculation - if ‘0’ no exclusive OR
takes place.
This process is repeated until eight ‘bit’ shifts have
been performed. After the eighth bit shift, the next 8bit
message byte is applied to the register contents using an
exclusive ‘OR’ calculation. The bit shift and re-calculation
process is then repeated again. When all message bytes
have been processed the final content of the 16bit
register is the message CRC value.
Only the 8bits of ‘data’ in each message character is used
for generating the CRC; start, stop and parity bits are
ignored.
When the 16bit CRC value is appended to a message,
the low order byte must be transmitted first followed by
the high order byte. An incorrect or byte reversed check
sum will render the message invalid and it will be ignored.
Slave Response Timeout
A slave controller may not answer immediately. Ensure
the ‘slave timeout’ setting of the ‘master’ device is set
to a value no less than 500ms. If the ‘slave’ device fails
to receive a valid message due to a communication
disruption, parity error, CRC error or other reasons, no
response is given and the master must process a timeout
condition in this instance. If the ‘slave’ receives a valid
message that cannot be processed an exception response
will be returned.
T
he message data start address (16bit word) designates
the initial register address location in the controller from
which the data is processed. Start address information is
contained in the ‘MODBUS Table’.
7
Message Answer From Slave to Master
Slave
Address
Function
Code
Number
ofData
Bytesto
Follow
DATA
1stRegister
byte0byte1
DATA2ndRegisterbyte2byte3
CRCCheck
Sum
01030400 5F 00 55 F3 45
The example above is a request to read offline pressure
5FHex (95) (register 40112) and online pressure 55Hex
(85) (register 40113) from X-IRI address 22(Hex).
06Hex - Preset Single Register
Slave
Address
Function
Code
Number
ofData
Bytesto
Follow
DATA1stRegisterbyte0byte1
DATA2ndRegisterbyte2byte3
CRCCheck
Sum
01030400 5F 00 55 F3 45
The example above is a request to set offline pressure
(register 40112) to 95 through X-IRI address 22(Hex).
Exception Response
If the ‘slave’ device receives a request that cannot be
processed an ‘exception response’ is given. An exception
response message consists of the following elements:
Function Code (1 byte): In a normal response, the
slave repeats the function code of the original
master request. All function codes have an MSB
(most significant bit) of 0 (values are all below 80
hexadecimal). In an exception response, the slave
sets the MSB of the function ‘code’ to 1. This makes
the ‘code’ value 80 Hex greater than the received
‘code’ value from the master.
Data (1 byte): The ‘data’ response will contain a ‘1
byte’ value exception code.
CRC Checksum (2 byte).
0190044DC3
CRCCheckSumSlaveAddressFunctionCodeErrorCode
Exception Codes:
01H Illegal Function Code - - The requested ‘code’
function is not supported.
02H Illegal Data Address - - The requested ‘data start
address’ is not supported.
03H Illegal Data Value - - The requested ‘data’ value is
not supported.
04H Function Error - - The slave cannot execute the
request or the request type is inhibited.
•
•
•
•
Troubleshooting
Problem:
No ‘slave’ response or corrupt MODBUS message
Solution:
Check that the ‘slave’ controller is set for the
anticipated slave address
Check that all ‘slave’ controllers are set with a unique
system address
Check that the controller is set for MODBUS RTU
mode (if applicable)
Check that the ‘master’ is operating in MODBUS RTU
mode
Check that the ‘master’ baud rate, parity bit and
number of stop bits are correct
Check that the ‘master ‘response timeout is set for a
minimum of 500ms
Check that the ‘master’ is implementing the specified
CRC check sum process
Check RS485 wiring polarity and security of
connections
Problem:
Last character of MODBUS message is corrupted
Solution:
Add a delay of 2ms after last character received
before releasing RTS signal
Problem:
The MODBUS master message is reflected in the
slave answer
Solution:
Inhibit RX/TX echo on ‘master’ device
communications port
•
•
•
•
•
•
•
•
•
•
•
•
•
T
he format of the ‘slave’ controller answer is similar to the
original master request format; the message data content
depends on the message function code type.
The ‘address’ and ‘code’ of the slave answer is identical
to the original request message; the address is the ‘slave’
device address and the ‘code’ is a repeat of received
function code type from the master. The remainder of the
message is dependent on the requested function code
type. The CRC checksum is re-calculated for the answer
message characters using the specified CRC process.
03H Read Holding Register(s)
8
SECTION 5 INSTALLATION
It is recommended that installation and
commissioning be carried out by an authorized and
trained product supplier.
L
E
D
#
6
L
E
D
#
7
L
E
D
#
8
L
E
D
#
9
s
c
r
e
e
n
L
2
L
1
121323
Multi485
X05
s
c
r
e
e
n
L
2
L
1
121323
MODBUS
X03
12
+
2
4
V
a
c
/
d
c
0
V
a
c
/d
c
X01
X02
X04
L
E
D
#
1
2
3
4
1
ON
OFF
6
7
8
5
1
0
1
1
1
2
9
SW1SW2SW3
L
E
D
#
2
L
E
D
#
3
L
E
D
#
5
L
E
D
#
4
Avoid mounting the X-IRI Gateway near high voltage
cables, high voltage devices or equipment or motor
starter contactors.
POWER SUPPLY
The X-IRI Gateway is powered by an external 24VDC
power supply. The AC supply voltage for the 24VDC
power supply is derived from the compressor’s 110VAC or
230VAC internal AC supply.
DC
+V.ADJ
LN
24VDC
100-240VAC
50/
60Hz
E
N
L
0VDC
+24VDC
1
2
X01
GATEWAY
LN
DC
+V.ADJ
L
N
24VDC
100-240VAC
50/60Hz
24V
AC/DC
X01
12
+24VDC
0VDC
+
-
The power specification for the X-IRI Gateway is 24VDC
(+-10%) @ 35mA, 1W
It is possible to use the same 24VDC po
wer supply to
power multiple X-IRI Gateway devices.
Wire polarity is important
INSTALLATION
UNIT LOCATION
The X
-IRI Gateway is DIN Rail mounted and can be located
within the compressor control enclosure or remotely
within a separate enclosure. X-IRI Gateway must be
located within 1000ft (10m) of the compressor controller.
9
DCS OR PLC CONNECTION
Wire polarity is important
Use 2-wire, 24 gauge (Belden 9841 or equivalent), twisted
pair, earth shielded, data cable with a total system
network length no greater than 4000ft (1219m).
COMPRESSOR IRBUS CONNECTION
1
6
2
3
5
4
RJ11
2
4
3
5
L1L2
M4Ring Tag
L1 (2)
L2 (4)
2
4
X02
For IntelliSys SGN, SGNe and Nirvana 15-30kW (20-40HP)
equipped with a Phoenix RS-485 data communications
connector, use the RJ11 Modbus cable supplied with the
X-IRI Gateway and modify as shown by removing the RJ11
Plug.
Wire polarity is important
Use 2-
wire, 24 gauge (Belden 9841 or equivalent), twisted
pair, earth shielded, data cable with a length no greater
than 1000ft (10m).
For IntelliSys “Red Eye”, SG and SE equipped with an RJ11
RS-485 data communications connection port, use the
RJ11 Modbus cable supplied with the X-IRI Gateway.
10
11
DCS OR PLC COMMUNICATIONS
50ms
RX – Data Received:
2
A valid MODBUS communication has just been
received from the DCS or PLC unit. In normal operation
this event should occur periodically depending on the
polling rate.
TX – Data Transmitted:
3
A MODBUS broadcast or message has just been
sent. To keep the link active, a MODBUS message must be
sent at least once every 10 seconds.
COMPRESSOR COMMUNICATIONS:
50ms
RX – Data Received:
4
A valid IRBUS communication has just been
received from the compressor controller. In normal
operation this event should occur at least once every ½
second.
TX – Data Transmitted:
5
An IRBUS message has just been sent to the
compressor controller. In normal operation this event
should occur at least once every ½ second.
OPERATIONAL INDICATIONS
OFFSlowFlash
ONFastFlash
L
E
D
#
6
L
E
D
#
7
L
E
D
#
8
L
E
D
#
9
Multi485
X04
L
E
D
#
2
L
E
D
#
3
L
E
D
#
5
L
E
D
#
4
MODBUS
X03
7
6
9
8
1s
MODBUSIR-BUS
At power on initialization, or when power has
been removed, all operational indicators will fast flash for
several seconds.
Normal O
6789
Normal operation function:
6
Modbus Communications with MODBUS master.
OFF
No valid communications with a MODBUS
master
ON: Valid communication with a MODBUS
master, at least one read/write operation once
every 10 seconds.
7
No function
Always OFF: no other defined function
8
No function
Always OFF: no other defined function
9
IR-BUS communication with a compressor
controller
OFF
No valid communications with the compressor
controller.
ON: IR-BUS compressor controller detected and
communication link established.
Led#2: Every flash indicates reception of a valid MODBUS
messsage from the MODBUS master.
Led#3: Every flash indicates transmission of a valid
MODBUS messsage to the MODBUS master.
Led#5: Every flash indicates transmission of a valid IRBUS
messsage to the IR-BUS compressor controller.
Led#4: Every flash indicates reception of a valid IR-BUS
message from the IR-BUS compressor controller.
peration Example:
When there is valid communication with a MODBUS
master and an IR-BUS compatible compressor controller
the main operation indicators will light up as shown
below.
12
RS485 NETWORK
RS-485 data communications and other low
voltage signals can be subject to electrical interference.
This potential can result in intermittent malfunction
or anomaly that is difficult to diagnose. To avoid this
possibility always use earth shielded cables, securely
bonded to a known good earth at one end. In addition,
give careful consideration to cable routing during
installation.
1) Never route an RS-485 data communications or low
voltage signal cable alongside a high voltage 3-phase
power supply cable. If it is necessary to cross the path of a
power supply cable(s), always cross at a right angle.
2) If it is necessary to follow the route of power supply
cables for a short distance (for example: from a
compressor unit to a wall along a suspended cable tray)
attach the RS- 485 or signal cable on the outside of an
earthed cable tray such that the cable tray forms an
earthed electrical interference shield.
3) Where possible, never route an RS-485 or signal cable
near to equipment or devices that may be a source of
electrical interference (for example: 3-phase power
supply transformer, high voltage switchgear unit,
frequency inverter drive module, radio communications
antenna).
13
14
MODBUS ADDRESS SELECTION
Each compressor connected to the MODBUS network will
have a unique assigned address, starting at compressor
1 increasing sequentially to the number of compressors
connected to the MODBUS network. The MODBUS
address is selected by using DIP switches 1, 2, 3, and 4
on SW1, and switches 1, 2, and 3 on SW2 on the X-IRI
Gateway.
SW1, 1 to4 and SW2, 1 to 3: Address Selection
The addresses are selected as shown in the following
table: (Note: ON = 1, OFF = 0 )
SW1SW1MODBUS
Address
(Decimal)
MODBUS
Address
(Hexl)1 2 3 4 1 2 3
0 0 0 0 0 0 011
1 0 0 0 0 0 011
0 1 0 0 0 0 022
1 1 0 0 0 0 033
0 0 1 0 0 0 044
1 0 1 0 0 0 055
0 1 1 0 0 0 066
1 1 1 0 0 0 077
0 0 0 1 0 0 088
1 0 0 1 0 0 099
0 1 0 1 0 0 010A
1 1 0 1 0 0 011B
0 0 1 1 0 0 012C
1 0 1 1 0 0 013D
0 1 1 1 0 0 014E
1 1 1 1 0 0 015F
0 0 0 0 1 0 01610
1 0 0 0 1 0 01711
0 1 0 0 1 0 01812
1 1 0 0 1 0 01913
0 0 1 0 1 0 02014
1 0 1 0 1 0 02115
0 1 1 0 1 0 02216
1 1 1 0 1 0 02317
0 0 0 1 1 0 02418
1 0 0 1 1 0 02519
0 1 0 1 1 0 0261A
1 1 0 1 1 0 0271B
0 0 1 1 1 0 0281C
1 0 1 1 1 0 0291D
SW1SW1
MODBUS
Address
(Decimal)
MODBUS
Address
(Hexl)
1 2 3 4 1 2 3
0 1 1 1 1 0 0301E
1 1 1 1 1 0 0311F
0 0 0 0 0 1 03220
1 0 0 0 0 1 03321
0 1 0 0 0 1 03422
1 1 0 0 0 1 03523
0 0 1 0 0 1 03624
1 0 1 0 0 1 03725
0 1 1 0 0 1 03826
1 1 1 0 0 1 03927
0 0 0 1 0 1 04028
1 0 0 1 0 1 04129
0 1 0 1 0 1 0422A
1 1 0 1 0 1 0432B
0 0 1 1 0 1 0442C
1 0 1 1 0 1 0452D
0 1 1 1 0 1 0462E
1 1 1 1 0 1 0472F
0 0 0 0 1 1 04830
1 0 0 0 1 1 04931
0 1 0 0 1 1 05032
1 1 0 0 1 1 05133
0 0 1 0 1 1 05234
1 0 1 0 1 1 05335
0 1 1 0 1 1 05436
1 1 1 0 1 1 05537
0 0 0 1 1 1 05638
1 0 0 1 1 1 05739
0 1 0 1 1 1 0583A
1 1 0 1 1 1 0593B
0 0 1 1 1 1 0603C
1 0 1 1 1 1 0613D
0 1 1 1 1 1 0623E
1 1 1 1 1 1 0633F
0 0 0 0 0 0 16440
1 0 0 0 0 0 16541
0 1 0 0 0 0 16642
1 1 0 0 0 0 16743
0 0 1 0 0 0 16844
1 0 1 0 0 0 16945
0 1 1 0 0 0 17046
1 1 1 0 0 0 17147
0 0 0 1 0 0 17248
SW1
SW2SW3
15
SW1SW1
MODBUS
Address
(Decimal)
MODBUS
Address
(Hexl)1 2 3 4 1 2 3
1 0 0 1 0 0 17349
0 1 0 1 0 0 1744A
1 1 0 1 0 0 1754B
0 0 1 1 0 0 1764C
1 0 1 1 0 0 1774D
0 1 1 1 0 0 1784E
1 1 1 1 0 0 1794F
0 0 0 0 1 0 18050
1 0 0 0 1 0 18151
0 1 0 0 1 0 18252
1 1 0 0 1 0 18353
0 0 1 0 1 0 18454
1 0 1 0 1 0 18555
0 1 1 0 1 0 18656
1 1 1 0 1 0 18757
0 0 0 1 1 0 18858
1 0 0 1 1 0 18959
0 1 0 1 1 0 1905A
1 1 0 1 1 0 1915B
0 0 1 1 1 0 1925C
1 0 1 1 1 0 1935D
0 1 1 1 1 0 1945E
1 1 1 1 1 0 1955F
0 0 0 0 0 1 19660
1 0 0 0 0 1 19761
0 1 0 0 0 1 19862
1 1 0 0 0 1 19963
0 0 1 0 0 1 110064
1 0 1 0 0 1 110165
0 1 1 0 0 1 110266
1 1 1 0 0 1 110367
0 0 0 1 0 1 110468
1 0 0 1 0 1 110569
0 1 0 1 0 1 11066A
1 1 0 1 0 1 11076B
0 0 1 1 0 1 11086C
1 0 1 1 0 1 11096D
0 1 1 1 0 1 11106E
1 1 1 1 0 1 11116F
0 0 0 0 1 1 111270
1 0 0 0 1 1 111371
0 1 0 0 1 1 111472
1 1 0 0 1 1 111573
0 0 1 0 1 1 111674
SW1SW1
MODBUS
Address
(Decimal)
MODBUS
Address
(Hexl)1 2 3 4 1 2 3
1 0 1 0 1 1 111775
0 1 1 0 1 1 111876
1 1 1 0 1 1 111977
0 0 0 1 1 1 112078
1 0 0 1 1 1 112179
0 1 0 1 1 1 11227A
1 1 0 1 1 1 11237B
0 0 1 1 1 1 11247C
1 0 1 1 1 1 11257D
0 1 1 1 1 1 11267E
1 1 1 1 1 1 11277F
MODBUS PORT SETUP SELECTION
SW1SW2
SW3
The MODBUS port setup is determined by means of DIP
switch 4 on SW2 and DIP switches 2,3 and 4 on SW3. The
selectable items are: baudrate and number of stop bits.
Parity is not selectable and fixed at “no parity”
SW2-4: Stop Bit Selection
1stopbit
2stopbits
SW3-2...4: Baudrate Selection
1200baud2400baud
48
00baud9600baud
19200baud38400baud
57600baud115200 baud
GATEWAY SOFTWARE VERSION DISPLAY
SW3-1
When DIP Switch 1 on SW3 is set to the ‘on’ possition the
LED indicators (LED 2 to 9) will show the software version:
L
E
D
#
6
L
E
D
#
7
L
E
D
#
8
L
E
D
#
9
Multi485
X04
L
E
D
#
2
L
E
D
#
3
L
E
D
#
5
L
E
D
#
4
MODBUS
X03
4
5
6789
3
2
To establish the software version number (01 to 255) add
together the ‘value’ associated with each illuminated LED.
LED # Value
6=1
7=2
8=4
9=8
2=16
3=32
5=64
4=128
Ignore LED 1 (power on indicator), located adjacent
to X01; this LED will always be on when power is applied.
For example:
1) LED 6 and 8 = ON; all others off
LED 6 = 1
LED 8 = 4
total = 5
Software Version = ‘E05’
2) LED 7 and 8 = ON; all others off
LED 7 = 2
LED 8 = 4
total = 6
Software Version = ‘E06’
3) LED 6, 7, 9 and 2 = ON; all others off
LED 6 = 1
LED 7 = 2
LED 9 = 8
LED 2 = 16
total = 27
Software Version = ‘E27’
The LED indicators will continue to display the the
software version, regardless of operation, until switch 1
on SW3 is set to the ‘off’ possition.
DIP Switch 1 on SW3 must always be set to the ‘off’
position for normal operation.
DIP Switch 1 on SW3 has no function with earlier
software versions; if the LED indicators continue to
operate normally when SW3-1 is switched on, the
software is an earlier version; update the software.
Please refer to the table on the following page to assist in
decoding the software version number.
The MODBUS address is set to the correct value
(switches 1-4 on SW1 and switches 1- 3 on SW2)
b)
The MODBUS port setup matches the MODBUS
master’s requirements. Switches 4 on SW2 and
switches 2-4 on SW3.
c)
The communication link wires from the Gateway
to the compressor controller and the MODBUS
master are connected, secure and the wire
polarities are correct (L1, L2).
2) Apply power to the X-IRI Gateway
3) Ensure communications with the compressor controller
is established – ensure indicator (9) is ON permanently.
4) Once the IR-BUS compressor controller communication
link is established the MODBUS master unit can start
operating. Any attempt from the MODBUS master to
communicate before the IR-BUS link is established will
simply result in the gateway not responding to the
MODBUS master.
5) Once the MODBUS master communicates with the
compressor controller through the gateway it should
keep on doing so at least once every 10 seconds to keep
indicator (6) from flashing.
6) In case the MODBUS master does not communicate at
least once every 10 seconds the communication link is
considered inactive: indicator (6) flashes and any earlier
commands for the compressor controller to operate in
“Host” mode are cancelled => the machine reverts back
to local start/stop and load/unload control mode.
17
SECTION 6 PARTS LIST
1
L
E
D
#
6
L
E
D
#
7
L
E
D
#
8
L
E
D
#
9
s
c
r
e
e
n
L
2
L
1
121323
Multi485
X05
s
c
r
e
e
n
L
2
L
1
121323
MODBUS
X03
12
+
2
4
V
a
c
/
d
c
0
V
a
c
/
d
c
X01
X02
X04
L
E
D
#
1
2
3
4
1
ON
OFF
6
7
8
5
1
0
1
1
1
2
9
SW1SW2SW3
L
E
D
#
2
L
E
D
#
3
L
E
D
#
5
L
E
D
#
4
2
3
DC
+V.ADJ
L
N
24VDC
100-240VAC
50/60Hz
E
N
L
0VDC
+24VDC
1
6
2
3
5
4
RJ11
2
4
3
5
M4Ring Tag
L1 (2)
L2 (4)
2
4
SECTION 7 TECHNICAL DATA
Module, Gateway
Dimensions3.8” x 3.4” x 2.2”
96mm x 85mm x 55mm
Weight0.6Ib (0.25kg)
MountingDIN, 35mm
EnclosureIP20
Supply24VDC/ac +/-15%
Power1.0VA
Temperature0°C to 46°C (32°F to 115°F)
Humidity95% RH non-condensing
131Lead/Lag Cycle Length (Hours)R/W0 – 750
132Scheduled Start (Hour)R/W0 – 23
133Scheduled Start (Minute)R/W0 – 59
134Scheduled Stop (Hour)R/W0 – 23
135Scheduled Stop (Minute)R/W0 – 59
136Modbus ProtocolR0 or 10=Off, 1=On
137Modbus AddressR1 – 247
138High Dust FilterR0 or 10=Off, 1=On
139Integral Sequencing LeadR/W0 – 30=Off, 1=On, 2=Always, 3=Never
140Integral Sequencing AddressR/W1 – 4
141Integral Sequencing TotalR/W2 – 4
142Integral Sequencing Load DelayR/W10 – 60
143Integral Sequencing Lead Change (Hours)R/W0 – 750
144Integral Sequencing Lead Change – DayR/W0 – 9See FIGURE 2-2
145Integral Sequencing Lead Change – HourR/W0 – 23
146Integral Sequencing Lead Change – MinR/W0 – 45Steps of 0, 15, 30, 45
147Separator Delta-P SensorR0 or 10=Off, 1=On
148Variable Frequency DriveR0 or 10=Off, 1=On
149Scheduled Start (Day)R/W0 - 9See FIGURE 2-2
150Scheduled Stop (Day)R/W0 - 9See FIGURE 2-2
151Remote SensorR0 or 10=Off, 1=On
250OptionsRSee FIGURE 2-2
251Unloaded Inlet VacuumR
252Software Part Number – Most SignificantRHigh Digits
253Software Part Number – Least SignificantRLow Digits
254Software Version NumberR
255Warning CodeRSee FIGURE 2-4
256-270 Alarm Code HistoryRSee FIGURE 2-4
272-286 Inlet Vacuum Alarm HistoryR
288-302 Sump Pressure Alarm HistoryR
304-318 Discharge Pressure Alarm HistoryR
320-334 Coolant Temperature Alarm HistoryR
336-350 Airend Temperature Alarm HistoryR
352-366 Discharge Temperature Alarm HistoryR
368-382 Low Ambient Coolant Temp. HistoryRLow Ambient Option
384-398 Total Hours Alarm HistoryRLess Than 10000 Hours
400-414 10000 Total Hours Alarm HistoryRMultiply by 10000
416-430 Loaded Hours Alarm HistoryRLess Than 10000 Hours
432-446 10000 Loaded Hours Alarm HistoryRMultiply by 10000
448-462 Unloaded Inlet Vacuum Alarm HistoryR
464-478 Coolant Pressure Alarm HistoryR
480-494 Dry Side Sump Pressure Alarm HistoryR
496-510 Remote Pressure Alarm HistoryR
512-526 Status Alarm HistoryRSee FIGURE 2-3
528-542 Real Time Clock Alarm History – HoursR
544-558 Real Time Clock Alarm History – MinutesR
560-574 Real Time Clock Alarm History – MonthR
576-590 Real Time Clock Alarm History – DateR
592-606 Real Time Clock Alarm History – YearR
999IRI Version NumberRReads from IRI only
Min. Cooler Out Load TempR/W30-150Low Ambient Option
(Offline + 7)
23
FIGURE 21 REGISTER 40001 STATUS / CONTROL
Bit 0: Host/Local (R/W)Bit 6: A
larm (R)
0 = Local0 = No Alarms
1 = Host1 = Alarms
Bit 1: Run/Stop (R/W)Bit 7: Warning (R)
0 = Stop0 = No Warnings
1 = Run1 = Warnings
Bit 2: Load/Unload (R/W)Bit 8: On/Off Line Mode (R)
0 = Unload0 = Not in On/Off Line Mode
1 = Load1 = On/Off Line Mode
Bit 3: Modulating (R)Bit 9: Mod/ACS or Mod Only (R)
0 = Not Modulating0 = Not in Mod/ASC Mode
1 = Modulating1 = Mod/ASC Mode
Bit 4: UnusedBits 10-12: Unused
Bit 5: Stopped in Auto Restart (R)Bits 13-15: Unit Type (R)
0 = Not Stopped in Auto Restart001 = SSR controller
1 = Stopped in Auto Restart
FIGURE 22 REGISTER CODES
Register 096: Language
Register 097: Units of Measure
0 = English 0 = °F and PSI
1 = Spanish 1 = °C and PSI
2 = Portuguese 2 = °C and Bar
3 = French 3 = °C and kPa
4 = Italian 4 = °C and kg/cm
5 = Dutch
6 = German
7 = Danish
8 = Norwegian
9 = Swedish
10 = Finnish
11 = Turkish