LA9P307

Telemecanique
Guide d'exploitation
User manual
Passerelle
Profibus DP / Modbus RTU
Gateway
Profibus DP / Modbus RTU
LA9P307
1
2
3
Contents
1. Introduction ........................................................................................................................................4
1.1. Main description......................................................................................................................4
1.2. Terminology ............................................................................................................................4
1.3. Notations.................................................................................................................................4
1.4. Abbreviations ..........................................................................................................................4
1.5. Documentation........................................................................................................................4
1.6. System overview.....................................................................................................................5
1.7. Modbus RTU characteristics...................................................................................................6
1.8. Profibus DP characteristics.....................................................................................................6
2. Installation ..........................................................................................................................................8
2.1. Acceptance .............................................................................................................................8
2.2. Monting ...................................................................................................................................8
2.3. Dimensions .............................................................................................................................8
2.4. Frontpanel overview................................................................................................................9
2.5. Power supply ..........................................................................................................................9
2.6. Installation Profibus DP side.................................................................................................10
2.6.1. Setting PPO type .....................................................................................................10
2.6.2. Profibus connector...................................................................................................10
2.6.3. Profibus address......................................................................................................10
2.6.4. Profibus baudrate ....................................................................................................10
2.6.5. Profibus termination.................................................................................................10
2.7. Installation Modbus side .......................................................................................................11
2.7.1. Modbus connector ...................................................................................................11
2.7.2. Modbus baud rate, format .......................................................................................11
2.8. LED indicators.......................................................................................................................12
3. Software configuration....................................................................................................................14
3.1. Profibus configuration tool ....................................................................................................14
3.2. Configuration of the Profibus DP slave.................................................................................14
3.3. Configuration of the general parameters ..............................................................................16
3.3.1. Modbus communication parameters .......................................................................17
3.3.2. Profibus communication parameters.......................................................................19
3.4. Configuration of the Modbus scanner...................................................................................22
3.4.1. Principle of Modbus scanner ...................................................................................22
3.4.2. Scanning periods.....................................................................................................22
3.4.3. Addresses links........................................................................................................23
4. Software operation...........................................................................................................................26
4.1. Profibus Master Input/Output area........................................................................................26
5. Software operation...........................................................................................................................27
5.1. PKW......................................................................................................................................28
5.1.1. PKW request and response.....................................................................................28
5.1.2. Bit and byte ordering of the value:...........................................................................29
5.1.3. PKW Error codes.....................................................................................................30
5.2. List of Active Slaves (LAS)....................................................................................................31
5.3. Error Code Register ..............................................................................................................31
4
1. Introduction
1.1. Main description
The Profibus / Modbus gateway LA9P307 connects the two different fieldbus networks, Profibus DP and Modbus
RTU, as a generic transparent protocol converter. This makes it possible to interface many Schneider Electric
products to a Profibus DP network.
1.2. Terminology
Throughout this document, the term "user" refers to the person or persons who are using the gateway.
As in all communication systems, the terms "input" and "output" can be ambiguous, because their meaning
depend on which end of the link is being referenced. The convention in this document is that "input" and "output"
are always being referenced to the master / scanner (PLC) end of the link.
A "output" is a command signal sent the modbus device, an "input" is a monitoring signal coming from the
Modbus device.
GATEWAY
IN
OUT
IN OUT
Profibus DP Master
Modbus slaves
1.3. Notations
All numeric hexadecimal values in this manual are presented in the following way: 16#0000
1.4. Abbreviations
Important abbreviations used in this manual:
LED Light Emitting Diode
LSB Least Significant Bit
MSB Most Significant Bit
PDP Profibus DP
1.5. Documentation
Services and parameters of Modbus devices are not explained in the present document. This information may
be delivered with the products or should be ordered separately (see catalogues).
5
1- Introduction
1.6. System overview
The Profibus DP / Modbus gateway enables a Profibus DP controller to control, monitor and configure up to 15
Modbus RTU devices on each gateway. The gateway acts as a combined Profibus DP slave and a Modbus RTU
master.
Profibus DP
GATEWAY GATEWAY GATEWAY
M
o
d
b
u
s
M
o
d
b
u
s
M
o
d
b
u
s
The gateway exchanges (writes and reads) data cyclically with the Modbus devices this called "Modbus
scanner". Each Modbus data correspond to a cyclic data of Profibus DP.
The link between these data has to be set up at configuration time by the user.
Then in run time the refreschment works automatically, no special application programm is required in the PLC
for communication.
It is also possible to access any parameter of the Modbus slaves by the PKW procedure. PKW can be used to:
- Setup, upload or download the parameters of the Modbus devices,
- To get a data which do not need a fast scan period,
- To get a data when occurs a event detected by a cyclic data.
6
1-Introduction
1.7. Modbus RTU characteristics
- RS485 communication.
- RTU protocol.
- 1200 bits/s to 19200 bits/s, configurable baudrate.
- Configurable format (startbit, stopbit, parity).
- Up to 15 Modbus RTU slaves can be connected to one gateway.
RS-485 is normally used for products that are designed to operate in industrial environments. RS-485 transfers
data with half duplex (send and receives data separately) and require 2 wires to communicate. The Gateway
supports RS-485 multidrop (addressing several slave units).
1.8. Profibus DP characteristics
The Gateway is designed according to PROFIBUS-DP EN 50 170 (DIN 19245)
- RS485 communication.
- 9600 kbit/s to 12 Mbit/s, auto-adapts to the baudrate of the master.
- Up to 99 Gateways can be connected to the master.
- Extended functions supported: User Parameter data.
The gateway can be configured to exchange 2 different sizes (PPO types) of cyclic data on Profibus DP.
The cyclic data of the gateway is divided in
- 8 bytes of parameter access function (PKW),
- A configurable amount of process data. The number of bytes depends on the profile type chosen.
The PPO type setup in the Profibus DP configurator (master side) must match the setting of the microswitches
inside the gateway.
If they dont match, the Profibus-DP network will not go online.
PPO type 1 PPO type 2
PKW 8 bytes 8 bytes
16 bytes 32 bytes Output Process
data
Command
8 words
24
bytes
16 words
40
bytes
PKW 8 bytes 8 bytes
2 bytes 2 bytes
Diagnostic
1 word 1 word
16 bytes 32 bytes
Input Process
data
Monitoring
8 words
26
bytes
16 words
42
bytes
PKW can be used to configure the gateway or the modbus devices.
7
8
2. Installation
2.1. Acceptance
Ensure that the gateway reference printed on the label of the cardboard is the same as that on the delivery note
corresponding to the purchase order.
Check that the product is complete, the cardboard must contain:
- A gateway,
- A floppy disk (Files of description .gsd and user manual).
Check that the gateway has not been damaged in transit.
2.2. Monting
Mount the gateway on a DIN-rail.
2.3. Dimensions
76.5
35
8.6
93
9
2- Installation
2.4. Frontpanel overview
2.5. Power supply
The 2-pin plug-able connector beneath the gateway is the +24VDC supply connector
Pin Name Description Note
+ +24 VDC Power Supply +24VDC (+/- 20%) ; max 150mA at 24VDC
- 0 VDC GND
Profibus
connector
Profibus
termination
Switch
Setting of
Profibus
address X 10
LED
indication for
Profibus
diagnostics
LED
indication for
Profibus
ON-LINE
LED
indication for
Profibus
OFF-LINE
Setting of
Profibus
address X 1
10
2- Installation
2.6. Installation Profibus DP side
2.6.1. Setting PPO type
To set up the PPO type:
Open the bottom cover.
Set the microswitches to desired PPO type as shown below.
PPO type 1 (default) PPO type 2
2.6.2. Profibus connector
A 9 pin standard Profibus female D-sub connector is used on the gateway.
Pin Name Function
Housing Shield Connected to PE
1 Not connected
2 Not connected
3 B-Line Positive RxD/TxD
4 RTS Request To Send
5 GND BUS Isolated GND
6 +5V BUS Isolated +5V
7 Not connected
8 A-Line Negative RxD/TxD
9 Not connected
2.6.3. Profibus address
Station address (= Node address) is configured by two rotary switches at the front of the gateway. The range for
the station address is between 0-99.
2.6.4. Profibus baudrate
The baudrate is automatically detected and adjusted to the selected baudrate on the Profibus-DP network. The
device supports baudrates up to 12Mbit/s.
2.6.5. Profibus termination
If the gateway is physically installed as the first or last unit on the network the termination switch should be set to
ON position to terminate the ends of the Profibus-DP cable.
11
2- Installation
2.7. Installation Modbus side
2.7.1. Modbus connector
The RJ45 cable should be connected to the RJ45 connector at the bottom of the gateway.
Pin Name Description Note
1
2
3
4 Gnd Ground
5 Gnd Ground
One of these terminals must be connected to ground
(It improves EMC immunity)
6
7 D(A) Transmit Data Sends Data from gateway to Modbus slaves
8 D(B) Transmit Data Sends Data to gateway from Modbus slaves
2.7.2. Modbus baud rate, format
Modbus baud rate and format are set up by software configuration.
12
2- Installation
2.8. LED indicators
Gateway and network status are indicated with three LED indicators on the front panel.
Name Colour Function
Fieldbus
Diagnostics
Red
Indicates certain faults on the Profibus DP side.
Flashing Red 1 Hz
Error in configuration: The PPO type set by the microswitches is
not equal to the PPO type set during configuration of the network.
Flashing Red 4 Hz
Error in initialisation of the Profibus DP communication ASIC.
Turned Off
No diagnostics present
ON-Line Green
Indicates that the Gateway is On-Line on the Profibus DP
network.
Steady green
Gateway is On-Line and data exchange is possible.
Turned Off
Gateway is not On-Line
OFF-Line Red
Indicates that the Gateway is Off-Line on the Profibus DP
network.
Steady red
Gateway is Off-Line and no data exchange is possible.
Turned Off Gateway is not Off-Line
13
14
3. Software configuration
3.1. Profibus configuration tool
The Profibus DP / Modbus RTU gateway has to be configured by any standard Profibus configuration tool.
The GSD file describes the properties and supported services on the gateway. The Profibus-DP Master imports
the GSD file to configure the gateway as a slave on the network.
The GSD file is available on the floppy disk provided with the gateway, the file name is "Gateway001.GSD".
The examples shown in the rest of the present document are designed with the software SyCon from the
company Hielscher and Telemecanique PLC software PL7.
3.2. Configuration of the Profibus DP slave
Configure the Profibus board (here PBY100), then launch the Profibus DP tool.
15
3- Software configuration
Chose the PPO type, which must match with the setup of the microswitches.
Then click on "Parameter Data" to access the parameters.
16
3- Software configuration
3.3. Configuration of the general parameters
The general parameters relate to Modbus and Profibus communication parameters.
The first view is not very existing. Click on "Common", then it is more user friendly.
If the default setup does not fit your application, double click to modifie a parameter. Chose between the possible
choices.
17
3- Software configuration
3.3.1. Modbus communication parameters
3.3.1.1. Modbus baudrate:
A baudrate common at all the slaves should be chosen.
3.3.1.2. Modbus format:
18
3- Software configuration
3.3.1.3. Modbus Read/Write lenght
Indicate the max number N of words for the Modbus services "Read N words" and "Write N wors". This
maximum value must be supported by all modbus slaves controlled and monitored through the gateway.
Example:
The Modbus slaves are one ATV28 and one ATS46.
Max N for ATV28 is 7.
Max N for ATS46 is 29 (decimal).
Modbus max N should not exceed 7 in this case.
Click "Dec" to see the value in decimal.
If "Modbus max N" is configured to 1, gateway only requests Read_Work and Write_Word, not Read_N_Word
nor Write_N_Word.
3.3.1.4. Modbus return time
After sending a response, some slaves take a time to switch back in reception state.
After the master has received a response from a slave, it waits during the return time before sending a new
request.
The unit is character.
3.3.1.5. Modbus management of communication errors
"Modbus timeout" is the time the master waits for the response of Modbus slaves (time base = 100 ms, default
value = 1s).
When a slave does not answer, the master retries several times "Modbus number of retrials" before it declares
the slave out of order (default value = 3).
The retrial is done in the following Modbus cycle.
When " Modbus number of retrials " equals to 0, no retrial is done.
After "Modbus reconnect time" the gateway tries to reconnect the faulty Modbus slaves (time base = 1s, default
value = 30s).
The response time on the active slaves can be delay a period of time equal to Modbus timeout multiplied by the
number of faulty Modbus slaves.
19
3- Software configuration
3.3.2. Profibus communication parameters
The management of Profibus DP communication errors are configured through 2 parameters.
The gateway checks the cyclic data sent by the master. If no data is received during the "PPO time out", the
gateway generates a Profibus communication error.
The reaction of the gateway in case of Profibus communication error depends on the parameter "PPO failure".
- "No reaction" : The gateway goes on polling Modbus slaves and sending Modbus requests.
- "Modbus polling stopped" : The gateway stops polling of the Modbus slaves. This configuration can be
chosen to trigger the watchdogs of the devices which monitor the communication on Modbus (for
example variable speed drives or starters).
- "All command reset" : The gateway goes on polling, but the cyclic commands are turned to 0. This
configuration can be used to stop devices not equipped with watchdog.
20
3- Software configuration
Note: Loss of control
Control may be lost at different level of the automation system. The configuration of the gateway is not the only
device to be considered.
PLC event: The CPU of the PLC can be stopped or fail. In these cases, the Profibus coupler remains in
order and goes on scanning the bus.
The gateway will not detect that the CPU have stopped controlling the devices.
The PLC can be configured to reset or to maintain the outputs in this case.
Example of Modicon-Telemecanique PLC configuration:
Profibus event: If the gateway is disconnected from the bus, the parameters "PPO failure" and "PPO time out"
should be used to configure the behaviour of the gateway.
Modbus event: If one or more devices are disconnected from Modbus network, the gateway cannot control
them.
The device itself have to be configured to react in case of no command is received from
Modbus.
For Telemecanique variable speed drives, if the control of communication needs to be disabled,
set bit NTO (This bit belongs to "Internal Control Register" CMI). The default value is NTO=0
(Communication monitored).
21
3- Software configuration
According to the needs of the process, the actuators have to be stopped, maintained or started in case of loss of
control.
The different devices have to be configured properly to performed the awaited behaviour.
The table below summarizes the configurations:
Event
Stop or failure of the CPU
of the PLC
Profibus disconnected Modbus disconnected
Stop
Configure the Profibus
coupler of the PLC to reset
outputs
Configure "PPO Failure" to
"All command reset"
Configure the Modbus
slaves (for Telemecanique
drives: NTO=0)
Behaviour
Maintain
Configure the Profibus
coupler of the PLC to
maintain outputs
Configure "PPO Failure" to
"No reaction"
Configure the Modbus
slaves (for Telemecanique
drives: NTO=1)
22
3- Software configuration
3.4. Configuration of the Modbus scanner
3.4.1. Principle of Modbus scanner
The gateway reads cyclically variables in the Modbus slaves, store them internally in the "Cyclic Monitoring
variables"(CMs), then copies them into Profibus DP cyclic input.
The gateway also receives Profibus DP cyclic output, stores them internally in the "Cyclic Command
variables"(CCs), and writes them cyclically in the Modbus slaves.
CMs and CCs are setup during the configuration of the gateway. Them, the Modbus scanner works
autonomously.
A certain number of data can be exchange by Modbus scanner. The size of data depends on the PPO type
chosen on Profibus.
PPO type 1 PPO type 2
Output
Command 8 words 16 words
Input
Monitoring 8 words 16 words
32 CCs and CMs can be configured by the Profibus configuration software (Hilscher , ...). But it is no use
declaring a number of CCs and CMs that exceed the maximum size of cyclic data on Profibus.
For example, if you want to exchange 2 words command (CC) and 2 words monitoring (CM) with 4 slaves, PPO
type1 is suffisant. But if you need to monitor 4 words per slave you should configured PPO type 2.
3.4.2. Scanning periods
Normal and fast scanning periods can be defined for reading (Monitoring) and writing (Command).
Name
Default
value
Possible
values
Description
Command scan period
fast
20 0 255
Period of fast scanning of cyclic command variables "CC"
Time base : 10 ms
If 0: as fast as possible
Example: value = 20 : 200ms
Command scan period
normal
200 0 255
Period of normal scanning of cyclic command variables "CM"
Time base : 10 ms
If 0: as fast as possible
Example: value = 200 : 2s
Monitoring scan period
fast
20 0 255
Period of fast scanning of cyclic monitoring variables "CM"
Time base : 10 ms
If 0: as fast as possible
Monitoring scan period
normal
200 0 255
Period of normal scanning of cyclic monitoring variables "CM"
Time base : 10 ms
If 0: as fast as possible
23
3- Software configuration
3.4.3. Addresses links
Each CM and CC is defined by 4 parameters:
- Scan period,
- Modbus slave address,
- Modbus variable address,
- Modbus variable length.
24
3- Software configuration
Maximum slave address is 15.

Variable address cannot exceed 16#FFFF or 65535.
Variable length cannot exceed 16 words.

You need to calculate the cyclic variables size to chose the PPO type.
Example: 4 slaves Command scanning of 2 words to each slave: W100 to W101
Monitoring scanning of 4 word from each slave:W10 to W13
Type Variable Period Slave address Variable address Variable length
Output CC1 Normal 1 100 2
Output CC2 Normal 2 100 2
Output CC3 Normal 3 100 2
Output CC4 Normal 4 100 2
Input CM1 Normal 1 10 4
Input CM2 Normal 2 10 4
Input CM3 Normal 3 10 4
Input CM4 Normal 4 10 4
8 words output and 16 word input are needed, PPO type 2 has to be configured.
25
26
4. Software operation
4.1. Profibus Master Input/Output area
The first eight bytes of the input and output areas are reserved for the PKW (Parameter access function) which
is described below.
The input area also has a LAS (List of Active Slaves) which is further described.
Remaining bytes are used for cyclic data where the amount of available bytes is determined by the configured
PPO type.
Data that is to be written to the Modbus RTU slaves is placed in the output area.
Data that is to be read from the Modbus RTU slaves is placed in the input area. The input area is read only.
Profibus DP master Gateway Profibus DP master Gateway
Profibus DP master output area Profibus DP master input area
Byte
Word
(PLC)
Data name Byte
Word
(PLC)
Data name
0 0
1
%QW 0
1
%IW 0
2 2
3
%QW 1
3
%IW 1
4 4
5
%QW 2
5
%IW 2
6 6
7
%QW 3
Parameter access function
(PKW output)
7
%IW 3
Parameter access function
(PKW input)
8 8
9
%QW 4
9
%IW 4
List of active Modbus slaves
(LAS)
... ...
...
%QW ...
Cyclic Command 1
(CC1)
...
%IW ...
... ...
...
%QW ...
...
%IW ...
Cyclic Monitoring 1
(CM1)
... ...
...
%QW ...
Cyclic Command 2
(CC2)
...
%IW ...
... ...
...
%QW ...
...
%IW ...
Cyclic Monitoring 2
(CM2)
... ...
...
%QW ...
Cyclic Command 3
(CC3)
...
%IW ...

%QW

%IW ...
Cyclic Monitoring 3
(CM3)
X ... ... Y ... ...
The number of PLC words for each CC and CM is equal to their length.
X and Y depend on PPO type.
27
5. Software operation
Example: 4 slaves Command scanning of 2 words to each slave: W100 to W101
Monitoring scanning of 4 word from each slave:W10 to W13
Profibus DP master Gateway Profibus DP master Gateway
Profibus DP master output area Profibus DP master input area
Byte
Word
(PLC)
Data name Byte
Word
(PLC)
Data name
0 0
1
%QW 0
1
%IW 0
2 2
3
%QW 1
3
%IW 1
4 4
5
%QW 2
5
%IW 2
6 6
7
%QW 3
Parameter access function
(PKW output)
7
%IW 3
Parameter access function
(PKW input)
8 8
9
%QW 4 W100
9
%IW 4
List of active Modbus slaves
(LAS)
10 10
11
%QW 5
CC1
Slave 1
W101
11
%IW 5 W10
12 12
13
%QW 6 W100
13
%IW 6 W11
14 14
15
%QW 7
CC2
Slave 2
W101
15
%IW 7 W12
16 16
17
%QW 8 W100
17
%IW 8
CM1
Slave 1
W13
18 18
19
%QW 9
CC3
Slave 3
W101
19
%IW 9 W10
20 20
21
%QW 10 W100
21
%IW 10 W11
22 22
23
%QW 11
CC4
Slave 4
W101
23
%IW 11 W12
24 24
25
%QW 12
25
%IW 12
CM2
Slave 2
W13
26 26
27
%QW 13
27
%IW 13 W10
28 28
29
%QW 14
29
%IW 14 W11
30 30
31
%QW 15
31
%IW 15 W12
32 32
33
%QW 16
33
%IW 16
CM3
Slave 3
W13
34 34
35
%QW 17
35
%IW 17 W10
36 36
37
%QW 18
37
%IW 18 W11
38 38
39
%QW 19
39
%IW 19 W12
40
41
%IW 20
CM4
Slave 4
W13
28
4- Software operation
5.1. PKW
5.1.1. PKW request and response
The PKW (Parameter access function) are used to handle non cyclic data in the gateway or in the slaves.
Profibus DP master Gateway
Byte
Word
(PLC)
Data name Value
0
1
%QW 0
PKE (Parameter Kennung)
Address of the data to access
2 DN (Device Number) 0: gateway, 1<=DN<=15: Modbus slave, 255= Modbus broadcast
3
%QW 1
R/W (Read / Write)
52: Read
53: Read_Array2
57: Write 58: Write_ Array2
4
5
%QW 2
Value
(byte 5 for byte type)
6
7
%QW 3
PWE (Parameter Wert) 0
0
Value
Profibus DP master Gateway
Byte
Word
(PLC)
Data name Value
0
1
%IW 0
PKE (Parameter Kennung)
Address of the accessed data
2 DN (Device Number) 0: gateway, 1<=DN<=15: Modbus slave
3
%IW 1
R/W/N (Read / Write / Error)
52: Read ok
53: Read_Array2 ok
57: Write ok
58: Write_ Array2 ok
4E: Error
4
5
%IW 2
Value
(byte 5 for byte type)
Error code
6
7
%IW 3
PWE (Parameter Wert)
0
Value
0
29
4- Software operation
5.1.2. Bit and byte ordering of the value:
If DN = 0, PKW service gives access to user parameters. User parameter type is byte, value is in byte 5, byte 4
is not used.
Bits
Bytes
7 6 5 4 3 2 1 0
4
5 7 6 5 4 3 2 1 0
In case the data is represented as a word.
Bits
Bytes
7 6 5 4 3 2 1 0
4 15 14 13 12 11 10 9 8
5 7 6 5 4 3 2 1 0
In case the data is represented as a double word.
Bits
Bytes
7 6 5 4 3 2 1 0
4 15 14 13 12 11 10 9 8
5 7 6 5 4 3 2 1 0
6 31 30 29 28 27 26 25 24
7 23 22 21 20 19 18 17 16
30
4- Software operation
5.1.3. PKW Error codes
The following codes can be returned by the Modbus nodes or the Gateway. Please note that the PKW Error
codes are not the same as the error codes in the Error Code Register.
Error code
Name Description
0 No response or corrupted
message
The Modbus node did not respond on message or the
responded message was corrupted.
1 Illegal function The function code received in the query is not an allowable
action for the slave. If a Poll Program Complete command
was issued, this code indicates that no program function
preceded it
2 Illegal data adress The data adress received in the query is not an allowable
address for the slave.
3 Illegal data value A value contained in the query data field is not an allowable
value for the slave.
4 Slave device failure An unrecoverable error occurred while the slave was
attempting to perform the requested action.
5 Acknowledge The slave accepted the request and is processing it, but a
long duration of time will be required to do so. This response
is returned to prevent a timeout error from occurring in the
master. The master can next issue a Poll Program Complete
message to determine if processing is completed.
6 Salve device busy The slave is engaged in processing a long-duration program
command. The master should retransmit the message later
when the slave is free.
7 Negative acknowledge The slave cannot perform the program function received in
the query. This code is returned for an unsuccessful
programming request using function code 13 or 14 decimal.
The master should request diagnostic or error information
from the slave.
8 Memory parity error The slave attempted to read extended memory, but detected
a parity error in the memory. The master can retry the
request, but service may be required on the slave device.
31
4- Software operation
5.2. List of Active Slaves (LAS)
All slaves that are online on the Modbus network will be shown in the LAS field of the input area.
A slave that is online is represented with a logical 1 (one). (A slave is defined as online when a cyclic operation
or a PKW-command has been successfully received by the actual slave within the configured timeout time.)
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Definition
N
o
t

U
s
e
d
S
l
a
v
e

1
5
S
l
a
v
e

1
4
S
l
a
v
e

1
3
S
l
a
v
e

1
2
S
l
a
v
e

1
1
S
l
a
v
e

1
0
S
l
a
v
e

9
S
l
a
v
e

8
S
l
a
v
e

7
S
l
a
v
e

6
S
l
a
v
e

5
S
l
a
v
e

4
S
l
a
v
e

3
S
l
a
v
e

2
S
l
a
v
e

1
These bits are really significant for the slaves for which CCs or CMs are configured.
5.3. Error Code Register
If a slave goes offline, it will be removed from the LAS, and an error code will be placed in the internal Error
Code Register of the gateway.
The error code can be accessed via PKW. The Error Code Register is read only.
Adress
Description
Adress
Description
300 (16#012C) Error code for slave address 1 308 (16#0134) Error code for slave address 9
301 (16#012D) Error code for slave address 2 309 (16#0135) Error code for slave address 10
302 (16#012E) Error code for slave address 3 310 (16#0136) Error code for slave address 11
303 (16#012F) Error code for slave address 4 311 (16#0137) Error code for slave address 12
304 (16#0130) Error code for slave address 5 312 (16#0138) Error code for slave address 13
305 (16#0131) Error code for slave address 6 313 (16#0139) Error code for slave address 14
306 (16#0132) Error code for slave address 7 314 (16#013A) Error code for slave address 15
307 (16#0133) Error code for slave address 8
32
4- Software operation
The following error codes can occur in the Error Code Register.
Please note that the error codes are not the same as the PKW error codes. (The error codes 0 to 8 are Modbus
Exception codes returned by the Modbus slaves.)
Error code
Name Description
0 No error
1 Illegal function The function code received in the query is not an allowable
action for the slave. If a Poll Program Complete command
was issued, this code indicates that no program function
preceded it
2 Illegal data adress The data adress received in the query is not an allowable
address for the slave.
3 Illegal data value A value contained in the query data field is not an allowable
value for the slave.
4 Slave device failure An unrecoverable error occurred while the slave was
attempting to perform the requested action.
5 Acknowledge The slave accepted the request and is processing it, but a
long duration of time will be required to do so. This response
is returned to prevent a timeout error from occurring in the
master. The master can next issue a Poll Program Complete
message to determine if processing is completed.
6 Salve device busy The slave is engaged in processing a long-duration program
command. The master should retransmit the message later
when the slave is free.
7 Negative acknowledge The slave cannot perform the program function received in
the query. This code is returned for an unsuccessful
programming request using function code 13 or 14 decimal.
The master should request diagnostic or error information
from the slave.
8 Memory parity error The slave attempted to read extended memory, but detected
a parity error in the memory. The master can retry the
request, but service may be required on the slave device.
9 No response No response was received from the slave before the time
out occurred.
10 (0x0A) Corrupted response Message received is corrupt or has been received with a
false checksum.
Revision 2
2001-11