Invertek Drives Optidrive E3 ODE-3 Series User manual

User Guide
FIELDBUS User Guide
1
2
3
4
5
6
7
8
9
10
About This Document
Fieldbus Connectivity
Parameter Configuration
for Fieldbus Operation
Modbus RTU
CAN
Ethernet Connection
Internal Webserver
Ethernet/IP Communication
Modbus TCP
Fieldbus Gateways
11
Control & Status Registers
12
Technical Data (External Interface)
FIELDBUS
User Guide
About This Document
Fieldbus Connectivity
Parameter Configuration
Parameter Configuration
for Fieldbus Operation
Modbus R
CAN
Ethernet Connection

2 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
1. About This Document
...................... 4
1.1. Compatibility
.................................. 4
1.2. Intended Audience
............................ 4
1.3. Additional Documentation
...................... 4
2. Fieldbus Connectivity
...................... 5
2.1. Overview
..................................... 5
3. Parameter Configuration for Fieldbus
Operation
..................................
6
3.1. Overview
..................................... 6
4. Modbus RTU
.............................. 8
4.1. Overview
..................................... 8
4.2. Hardware Connection
......................... 8
4.3. Modbus RTU Configuration Parameter
........... 10
4.4. Modbus RTU Status & Control Holding Registers
. . 10
4.5. Parameter Access
............................. 10
4.6. Modbus RTU Indirect Parameter Access
.......... 10
5. CAN
..................................... 23
5.1. Overview
..................................... 11
5.2. CAN Communication Configuration Parameter
... 11
5.3. CAN COB-ID
................................ 11
5.4. PDO Default Mapping
......................... 12
5.5. PDO Transmission Type
. . . . . . . . . . . . . . . . . . . . . . . . . 12
5.6. CAN Specific Object Table
.................... 12
5.7. Parameter Access
.............................. 13
5.8. Additional Status Indices
....................... 13
6. Ethernet Connection
....................... 14
6.1. Available Interface Options
..................... 14
6.2. External Interface
.............................. 14
6.3. Internal Interface for IP66 Drives
................ 16
6.4. Optional Interface for Compact 2 Basic Drives
... 17
6.5. Drive Parameter Settings
. . . . . . . . . . . . . . . . . . . . . . . . 17
7. Internal Webserver
........................ 18
7.1. Overview
..................................... 18
7.2. Default Login
.................................. 18
7.3. Web Server Contents
.......................... 18
7.4. Changing the IP Address
. . . . . . . . . . . . . . . . . . . . . . . . 20
7.5. Creating an Additional User Account for Limited
Access
...........................................
21
8. Ethernet/IP Communication
................ 22
8.1. Overview
..................................... 22
8.2. Operation
.................................... 22
8.3. Usage Requirement
............................ 22
8.4. Operation
.................................... 23
8.5. Process Data Exchange (cyclic communication)
... 23
8.6. Configuring the Scanner
....................... 23
8.7. Advanced connection methods
.................. 40
8.8. Parameter data transfer
........................ 41
8.9. Trouble Shooting
.............................. 43
9. Modbus TCP
.............................. 45
9.1. Overview
..................................... 45
9.2. Usage Requirement
............................ 45
9.3. Operation
.................................... 45
9.4. Trouble Shooting
.............................. 45
10. Fieldbus Gateways
....................... 47
10.1. Gateway Concept
............................ 47
10.2. Gateway Included Components
............... 47
10.3. Gateway Installation
.......................... 47
10.4. Subnetwork Connection
...................... 48
10.5. Gateway Memory Mapping
.................. 49
10.6. Controlling the Optidrive(s)
.................... 50
10.7. Profibus DP Gateway Features – OD-PROFB-IN
. 51
10.8. DeviceNet Gateway Features – OD-DEVNT-IN
. 52
10.9. Diagnostics and Troubleshooting
............... 53
11. Control & Status Registers
................. 54
11.1. Control Registers
.............................. 54
11.2. Standard Status Registers
...................... 55
11.3. Extended Status Registers
...................... 56
11.4. Additional Modbus RTU Registers / CAN Index
Data – Control & Monitoring
.......................
57
12. Technical Data (External Interface)
......... 61
12.1. Environmental
................................ 61
4.1. Overview
.....................................
8
4.2. Hardware Connection
.........................
8
4.3. Modbus RTU Configuration Parameter
...........
10
4.4. Modbus RTU Status & Control Holding Registers
. .
10
4.5. Parameter Access
.............................
10
4.6. Modbus RTU Indirect Parameter Access
..........
10
5. CAN
.....................................
23
5.1. Overview
.....................................
11
5.2. CAN Communication Configuration Parameter
...
11
5.3. CAN COB-ID
................................
11
5.4. PDO Default Mapping
.........................
12
5.5. PDO Transmission Type
. . . . . . . . . . . . . . . . . . . . . . . . .
12
5.6. CAN Specific Object Table
....................
12
5.7. Parameter Access
..............................
13
5.8. Additional Status Indices
.......................
13
6. Ethernet Connection
.......................
14
6.1. Available Interface Options
.....................
14
6.2. External Interface
..............................
14
6.3. Internal Interface for IP66 Drives
................
16
6.4. Optional Interface for Compact 2 Basic Drives
...
17
6.5. Drive Parameter Settings
17
9. Modbus TCP
..............................
9.1. Overview
.....................................
9.2. Usage Requirement
............................
9.3. Operation
....................................
9.4. Trouble Shooting
..............................
10. Fieldbus Gateways
.......................
10.1. Gateway Concept
............................
10.2. Gateway Included Components
...............
10.3. Gateway Installation
..........................
10.4. Subnetwork Connection
......................
10.5. Gateway Memory Mapping
..................
10.6. Controlling the Optidrive(s)
....................
10.7. Profibus DP Gateway Features – OD-PROFB-IN
.
10.8. DeviceNet Gateway Features – OD-DEVNT-IN
.
10.9. Diagnostics and Troubleshooting
...............
11. Control & Status Registers
.................
11.1. Control Registers
..............................
11.2. Standard Status Registers
......................
11.3. Extended Status Registers
......................
11.4. Additional Modbus RTU Registers / CAN Index
Data – Control & Monitoring

Version 1.02 | Fieldbus Guide | 3www.invertekdrives.com
Copyright Invertek Drives Ltd © 2021
All rights reserved. No part of this User Guide may be reproduced or transmitted in any form or by any means, electrical or
mechanical including photocopying, recording or by any information storage or retrieval system without permission in writing from the
publisher.
This document is the “original instructions” document. All non-English versions are translations of the
“original instructions”.
The contents of this document are believed to be correct at the time of printing. In the interest of a commitment to a policy of
continuous improvement, the manufacturer reserves the right to change the specification of the product or its performance or the
contents of the User Guide without notice.
Fieldbus Guide Issue 02 (10/21)
Invertek Drives Ltd adopts a policy of continuous improvement and whilst every effort has been made to provide accurate and up to
date information, the information contained in this User Guide should be used for guidance purposes only and does not form the part
of any contract.

4 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
1
About This Document
1. About This Document
1.1. Compatibility
This Document is for use with the following firmware versions:
Optidrive E3: Version 3.11
Optidrive Compact 2 Basic: Version 2.07
This document provides information regarding parameters and programming for all Invertek Drives’ Optidrive E3 product families
including the Optidrive E3 based Compact 2 Basic units.
For information regarding installation and technical data, refer to the relevant Installation Guide document.
Invertek Drives Ltd adopts a policy of continuous improvement and whilst every effort has been made to provide accurate and up to
date information, the information contained in this User Guide should be used for guidance purposes only and does not form the part
of any contract.
The information in this user guide relates to the functionality of the firmware version as stated above. Prior versions of firmware may not
fully support all functions as described. If necessary, firmware updates may be carried out using Optitools Studio PC software.
1.2. Intended Audience
This document provides an overview of the parameters and functions of the Optidrive product ranges and provides the necessary
technical information to allow competent users to understand the functions of the parameters.
1.3. Additional Documentation
This document forms part of a package of documents intended to provide information about the Optidrive product range. Related
documents are shown in the table below.
Product Range Optidrive E3 ODE-3-… Optidrive Compact 2-Basic OPC-2-…E
Enclosure IP20 IP66 All
Version All ABCD All
Quick Start Guide EN
DE
SP
FR
PT
IT
PO
EN
DE
SP
FR
PT
IT
PO
EN
DE
Declaration of Conformity EN EN
Installation Guide EN
DE
SP
FR
PT
IT
PO
EN
DE
Parameter List EN
DE
SP
FR
PT
IT
PO
Fieldbus Guide EN
DE
SP
FR
PT
IT
PO
The information in this user guide relates to the functionality of the firmware version as stated above. Prior versions of firmware may not
fully support all functions as described. If necessary, firmware updates may be carried out using Optitools Studio PC software.
1.2. Intended Audience
This document provides an overview of the parameters and functions of the Optidrive product ranges and provides the necessary
technical information to allow competent users to understand the functions of the parameters.
1.3. Additional Documentation
This document forms part of a package of documents intended to provide information about the Optidrive product range. Related
documents are shown in the table below.
Product Range
Optidrive E3 ODE-3-…
Optidrive Compact 2-Basic OPC-2-…E
Enclosure
IP20
IP66
All
Version
All
ABCD
ABCD
ABCD
ABCD
All
Quick Start Guide
EN
DE
SP
FR
PT
IT
PO
EN
DE
SP
FR
PT
IT
PO
EN
DE
Declaration of Conformity
EN
EN
Installation Guide
EN
DE
SP
FR
PT
IT
PO
EN
DE

Version 1.02 | Fieldbus Guide | 5www.invertekdrives.com
2
Fieldbus Connectivity
2. Fieldbus Connectivity
2.1. Overview
The following fieldbus networks are supported:
Fieldbus
Network
Requires Option Supported
Communication Type Refer to Section
For
Compact 2
For Optidrive
E3 IP20
For Optidrive
E3 IP66
Modbus RTU Built In R/W Holding Registers 4. Modbus RTU
CAN Built In 2 x PDO & SDO 5. CAN
Ethernet/IP - - “-EIP“ Cyclic & Acyclic 6. Ethernet Connection and
8. Ethernet/IP Communication
Modbus TCP - - “-MTP“ R/W Holding Registers 6. Ethernet Connection
Profibus DP OD-PROFB-IN Cyclic Control Only 10. Fieldbus Gateways
DeviceNet OD-DEVNET-IN Cyclic Control Only 10. Fieldbus Gateways
2
Profibus DP
OD-PROFB-IN
Cyclic Control Only
10. Fieldbus Gateways
DeviceNet
OD-DEVNET-IN
Cyclic Control Only
10. Fieldbus Gateways

6 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
3
Parameter Configuration for Fieldbus Operation
3. Parameter Configuration for Fieldbus Operation
3.1. Overview
The following parameters are used to configure any fieldbus connection. Refer to the Programming Guide for further information.
Parameters are explained more fully in the Programming Guide.
3.1.1. Parameter P-12: Control Source
The fieldbus interfaces may be used to monitor information from the drive regardless of where the control commands originate.
If it is required to control the drive through the fieldbus interface, the following parameter should be adjusted as shown.
Reference: P-12 Function: Control Source Selection
Setting Function Description
3 Fieldbus Mode Control via Modbus RTU or Ethernet using the internal Accel / Decel ramp parameters.
Recommended setting for all fieldbus except CAN.
4 Fieldbus Mode Control via Modbus RTU or Ethernet with Accel / Decel ramps determined by the fieldbus.
7 CAN open Control Control via CAN (RS485) using the internal Accel / Decel ramp parameters. Recommended setting.
8 CAN open Control Control via CAN (RS485) interface with Accel / Decel ramps updated via CAN.
NOTE When P-12 = 3, 4, 7, or 8 an enable signal must still be provided at the control terminals, digital input 1.
3.1.2. P-36 Communication Configuration
Reference: P-36 Function: Serial Interface Configuration
Index 1 Function: Address / Node ID
For Modbus RTU: Defines the Node Address
For CAN: Defines the Node ID
For Ethernet: Setting 1 MUST be used
Index 2 Function: Baud Rate
Setting Baud Rate Fieldbus
09.6 Modbus RTU.
For Ethernet communication, 115,2kbps must be selected.
119. 2
238.4
357.6
4115 . 2
5125 CAN
6250
7500
81000
Recommended setting for all fieldbus except CAN.
4 Fieldbus Mode
4 Fieldbus Mode
Control via Modbus RTU or Ethernet with Accel / Decel ramps determined by the fieldbus.
7 CAN open Control
7 CAN open Control
Control via CAN (RS485) using the internal Accel / Decel ramp parameters. Recommended setting.
8 CAN open Control
8 CAN open Control
Control via CAN (RS485) interface with Accel / Decel ramps updated via CAN.
NOTE
When P-12 = 3, 4, 7, or 8 an enable signal must still be provided at the control terminals, digital input 1.
3.1.2. P-36 Communication Configuration
Reference: P-36
Function: Serial Interface Configuration
Index 1
Function: Address / Node ID
For Modbus RTU: Defines the Node Address
For CAN: Defines the Node ID
For Ethernet: Setting 1 MUST be used
Index 2
Function: Baud Rate
Setting Baud Rate Fieldbus
Setting Baud Rate Fieldbus
Setting Baud Rate Fieldbus
0
9.6
Modbus RTU.
For Ethernet communication, 115,2kbps must be selected.
1
19. 2
2
38.4
3
57.6
4
115 . 2
5
125
CAN
6
250
7
500
8
1000

Version 1.02 | Fieldbus Guide | 7www.invertekdrives.com
3
Parameter Configuration for Fieldbus Operation
Index 3 Function: Modbus RTU Communication Loss Detection
Communication loss protection for Modbus RTU is selected here. For CAN, refer to the Fieldbus Guide for information.
Setting Display Timeout Action
00 Disabled
1t 30 30ms
Trip (Coast Stop)
2t 100 100ms
3t 1000 1s
4t 3000 3s
5r 30 30ms
Ramp to Stop
6r 100 100ms
7r 1000 1s
8r 3000 3s
9t 10000 10s
Trip (Coast Stop)10 t 30000 30s
11 t 60000 60s
12 r 10000 10s
Ramp to Stop13 r 30000 30s
14 r 60000 60s
Parameter P-36 is a compound parameter with multiple indices. The indices are displayed sequentially when accessing the parameter through
a keypad or separately in Optitools Studio. The data from all indices is stored within the drive memory as a single WORD. When accessing this
value through a fieldbus network, the data format is as follows:
Reference: P-63 Function: Modbus RTU Mode Selection
E3 IP20, IP66NS Minimum: Maximum: 1 Default: 0 Scaling: 1 = 1
E3 IP66S
Compact 2 Basic
Fieldbus Information: CAN Index: 20A3h Modbus Register: 191 Format: UINT Units: N/A
Description:
Setting Function Description
0 Standard
All Modbus RTU telegrams are valid regardless of the destination address. In this case, communication loss
detection is only activated when no valid Modbus RTU data is present on the network for the time period selected
in P-36 regardless of the intended destination address. This is intended for larger Modbus RTU networks with
several noes where there may be some time delay between Modbus transactions specifically intended for the drive
however transactions intended for other network devices will be present.
1 Advanced
Only Modbus RTU telegrams intended for the specific node address are valid. Communication loss protection will
activate if no Modbus RTU message intended for the specific drive node address is received within the time limit set
in P-36. This mode is intended for use in small networks and must be used with any other Fieldbus network type
e.g. Modbus TCP, Ethernet/IP.
t 10000
10s
Trip (Coast Stop)
t 30000 30s
t 30000 30s
t 60000 60s
t 60000 60s
r 10000
10s
Ramp to Stop
r 30000 30s
r 30000 30s
r 60000 60s
r 60000 60s
Parameter P-36 is a compound parameter with multiple indices. The indices are displayed sequentially when accessing the parameter through
a keypad or separately in Optitools Studio. The data from all indices is stored within the drive memory as a single WORD. When accessing this
value through a fieldbus network, the data format is as follows:
Reference: P-63
Function: Modbus RTU Mode Selection
E3 IP20, IP66NS Minimum:
E3 IP20, IP66NS Minimum:
Maximum: 1
Default: 0
Scaling: 1 = 1
E3 IP66S
Compact 2 Basic
Fieldbus Information:
CAN Index: 20A3h Modbus Register: 191 Format: UINT
CAN Index: 20A3h Modbus Register: 191 Format: UINT
CAN Index: 20A3h Modbus Register: 191 Format: UINT
Units: N/A
Description:
Setting Function Description
Setting Function Description
Setting Function Description
0 Standard
0 Standard
All Modbus RTU telegrams are valid regardless of the destination address. In this case, communication loss
detection is only activated when no valid Modbus RTU data is present on the network for the time period selected
in P-36 regardless of the intended destination address. This is intended for larger Modbus RTU networks with
several noes where there may be some time delay between Modbus transactions specifically intended for the drive
however transactions intended for other network devices will be present.
1 Advanced
1 Advanced
Only Modbus RTU telegrams intended for the specific node address are valid. Communication loss protection will
activate if no Modbus RTU message intended for the specific drive node address is received within the time limit set
in P-36. This mode is intended for use in small networks and
must
be used with any other Fieldbus network type
e.g. Modbus TCP, Ethernet/IP.

8 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
4
Modbus RTU
4. Modbus RTU
4.1. Overview
Modbus RTU communication is supported using Function Codes 03 Read Holding Registers and 06 Write Single Holding Register.
All internal registers are Holding registers. There are no other register types present within the drive.
Registers 1 to 4 only support Function Code 16 Write multiple Holding Registers.
Modbus RTU communication is enabled by default for Read access.
To control the drive through Modbus RTU, parameter P-12 should be set to 3 or 4. Refer to the programming guide for further
information on the parameter settings.
When an external Modbus RTU device is used to control the drive, Digital Input 1 acts to provide a local enable / disable signal.
The drive will not operate unless digital input 1 is ON. Additional functions may be assigned to other input terminals. Refer to the
Installation guide for details of the digital Input function assignments that are possible.
4.2. Hardware Connection
4.2.1. Optidrive E3 IP20
Optidrive E3 IP20 models have a built in RJ45 connector which provides the interface for Modbus RTU connection.
1CAN-
2CAN+
30 Volts
4
Optibus / Remote Keypad / PC Connection
5 Optibus / Remote Keypad / PC Connection +
6+24 Volt
7-RS485 (Modbus RTU)
8+RS485 (Modbus RTU)
Warning:
This is not an Ethernet connection. Do not connect
directly to an Ethernet port.
4.2.2. Optidrive E3 IP66
Optidrive E3 IP66 models have two RJ45 connectors fitted under the terminal cover as shown below. The connectors are parallel
allowing simple connection between multiple drives.
L1 L3 EMCL2/N UVW
1 2 3 4 5 6 7 8 9 10 11
I0I0I I0I0I
1CAN-
2CAN+
30 Volts
4
Optibus / Remote Keypad / PC Connection
5 Optibus / Remote Keypad / PC Connection +
6+24 Volt
7-RS485 (Modbus RTU)
8+RS485 (Modbus RTU)
Warning:
This is not an Ethernet connection. Do not connect
directly to an Ethernet port.
4.2. Hardware Connection
4.2.1. Optidrive E3 IP20
Optidrive E3 IP20 models have a built in RJ45 connector which provides the interface for Modbus RTU connection.
1
CAN-
2
CAN+
3
0 Volts
4
Optibus / Remote Keypad / PC Connection
5
Optibus / Remote Keypad / PC Connection +
6
+24 Volt
7
-RS485 (Modbus RTU)
8
+RS485 (Modbus RTU)
Warning:
This is not an Ethernet connection. Do not connect
directly to an Ethernet port.
4.2.2. Optidrive E3 IP66
Optidrive E3 IP66 models have two RJ45 connectors fitted under the terminal cover as shown below. The connectors are parallel
allowing simple connection between multiple drives.
1
CAN-

Version 1.02 | Fieldbus Guide | 9www.invertekdrives.com
4
Modbus RTU
4.2.3. Optidrive Compact 2 Basic
Suitable Motor Types
Optidrive Compact 2 Basic drives also include the RJ45 connector with the same layout as Optidrive E3 units shown above.
Additionally, the Modbus RTU interface is also present on terminals as follows:
Terminal 7: 0V
Terminal 10: Modbus RTU +
Terminal 11: Modbus RTU -
15
1
4.2.4. General
All Invertek drive’s support the RS485 3-wire connection method for Modbus RTU according to the network specification. The three
wires are essential to transfer data and maintain common potential between all nodes. For drives that have an RJ45 connector an
optional interface connector providing terminals to connect to a Modbus RTU network is available, part number OPT-2-BNTSP-IN.
Modbus RTU
RS485 Controller
RS485+
RS485-
0 Volt / Common
Ground
NOTES
• Use 3 or 4 Conductor Twisted Pair Cable
•RS485+ and RS485- must be twisted pair
• Ensure the network taps for the drive
are kept as short as possible
• Using Option OPT-2-BNTSP-IN is
preferred
•Terminate the network cable shield at
the controller only. Do not terminate at
the drive!
•0Volt common must be connected
across all devices and to reference 0 Volt
terminal at the controller
•Do not connect the 0V Common of the
network to power ground
RS485+
RS485-
0 Volt / Common
Shield
OPT-2-BNTSP-IN
OPT-2-BNTSP-IN
12 3
RS485+ 0 Volt / Common
Connection to the
drive through the
option
OPT-2-BNTSP-IN
RS485-
Pin 3 –0Volt / Common
Pin 7 –RS485- (Modbus RTU)
Pin 8 –RS485+ (Modbus RTU)
RJ45 connector pinout
Direct connection to the drive
through the built-in RJ45 port
1 2 3 4 5 6 7 8
12345678
4.2.5. Control Terminal Connection
4.2.4. General
All Invertek drive’s support the RS485
3-wire
connection method for Modbus RTU according to the network specification. The three
wires are essential to transfer data and maintain common potential between all nodes. For drives that have an RJ45 connector an
optional interface connector providing terminals to connect to a Modbus RTU network is available, part number OPT-2-BNTSP-IN.
Modbus
RTU
485 Contr
oller
NOTES
• Use 3 or 4 Conductor
Tw
isted
Pa
ir Cable
•R
S485+ and RS485- must be twis
te
d pair
• Ensu
re
the network
ta
ps f
or the drive
are
ke
pt as short as possible
• Using Option OPT-2-BNTSP-IN is
pr
ef
erred
•T
ermina
•Termina•T
te
the network cable
shield at
the cont
ro
ller only
. Do not termina
te
at
the drive!
•0
Vo
lt common
must be connec
te
d
acr
oss all devices and to
re
fe
re
nce 0
Vo
lt
t
erminal at the cont
ro
ller
•D
o not connect the 0V Common of the
network to power gr
ound
OP
T-
2-
BNTS
P-
IN
OP
OP
OP
OP
T-
OP
T-
2-
OP2-
T-
2-
T-
2-
2-
BNTS
2-
BNTS
BNTS
BNTS
BNTS
BNTS
P-
BNTS
P-
P-
IN
P-
IN
IN
IN
IN
IN
IN
IN
IN
12
3
RS485+
0 Volt / Common
0 Volt / Common
0 Volt / Common
0 Volt / Common
Connection to th
e
drive
through the
option
OPT-2-BNTSP-IN
RS485-
Pin
3
–0
Volt
/ Common
Pin
7
–
RS485- (Modbus
RTU)
Pin
8
–
RS485+ (Modbus
RTU)
RJ45 connector pinout
RJ45 connector pinout
RJ45 connector pinout
RJ45 connector pinout
Di
re
ct connection to the drive
through
the built-in
RJ45 port
1 2 3 4 5 6 7
8
1
2
3
3
4
4
5
6
7
7
8
8

10 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
4
Modbus RTU
4.3. Modbus RTU Configuration Parameter
Refer to section 3. Parameter Configuration for Fieldbus Operation on page 6.
4.4. Modbus RTU Status & Control Holding Registers
Modbus RTU status holding registers are shown in section 11. Control & Status Registers on page 54.
Holding Register 1 – 4 are used for drive control.
Additional Holding registers provide status information which may be read from the drive.
Modbus Master devices differ between different manufacturers and so it may be necessary to review the documentation for the
specific Master device being used to understand the correct addressing method to access Holding Registers, e.g.
Some devices use zero based addressing
o In this case the first Holding Register address is Holding Register 0
o Subtract 1 from the Holding Register number shown in the documentation.
Some devices recognise Holding Registers with a 40000 prefix
o In this case the first Holding Register may be 40000 or 40001
o Add the appropriate prefix and if necessary, subtract the offset.
4.5. Parameter Access
All User Adjustable parameters are accessible by Modbus RTU using the corresponding Holding Register. The register number
associated to each parameter is shown in the Programming Guide document along with any specific information about how the value
is scaled or stored.
Parameter values may be read from the drive or written to, depending on the operating mode of the drive – some parameters cannot
be changed whilst the drive is enabled.
4.6. Modbus RTU Indirect Parameter Access
In addition to Direct Access, Indirect Read / Write access to all user adjustable parameters is supported using a simple method as
detailed below. This is achieved using the following two Modbus registers.
4.6.1. Register 44: Drive Parameter Index
This index value will be used by register 45 to carry out parameter read and write function.
If the value is set to a parameter number that does not exist in the drive, an exception response will be received.
4.6.2. Register 45: Drive Parameter Value
When reading this register, the value represents the value of the parameter specified by register 44.
When writing to this register, the value will be written to the drive parameter number specified by register 44.
If the value written to a parameter is outside of the parameter range, an exception response will be received.
4.6.3. Parameter Read Method
To read a parameter, firstly write the parameter number to register 44, then read the value from register 45, e.g. to Read the Value of
P - 01.
Write 1 to Register 44.
Read the Value of Register 45.
4.6.4. Parameter Write Method
Writing parameter values can be achieved by the same method, however, register 45 is used to write the parameter value after the
parameter number has been selected using Register 44, e.g. to Write a Value of 60.0Hz to parameter P-01.
Write 1 to Register 44.
Register 45 will return the present value of P-01, which can be Read if required.
Referring to the Programming Guide, apply any scaling necessary
o In this case, 60.0Hz = 3600.
Write the scaled value to Register 45. P-01 now changes to 60.0Hz, or an exception code may be returned.
In th
is case the first Holding Register may be 40000 or 40001
A
dd the appropriate prefix and if necessary, subtract the offset.
4.5. Parameter Access
All User Adjustable parameters are accessible by Modbus RTU using the corresponding Holding Register. The register number
associated to each parameter is shown in the Programming Guide document along with any specific information about how the value
is scaled or stored.
Parameter values may be read from the drive or written to, depending on the operating mode of the drive – some parameters cannot
be changed whilst the drive is enabled.
4.6. Modbus RTU Indirect Parameter Access
In addition to Direct Access, Indirect Read / Write access to all user adjustable parameters is supported using a simple method as
detailed below. This is achieved using the following two Modbus registers.
4.6.1. Register 44: Drive Parameter Index
This index value will be used by register 45 to carry out parameter read and write function.
If the value is set to a parameter number that does not exist in the drive, an exception response will be received.
4.6.2. Register 45: Drive Parameter Value
When reading this register, the value represents the value of the parameter specified by register 44.
When writing to this register, the value will be written to the drive parameter number specified by register 44.
If the value written to a parameter is outside of the parameter range, an exception response will be received.
4.6.3. Parameter Read Method
To read a parameter, firstly write the parameter number to register 44, then read the value from register 45, e.g. to Read the Value of
Write 1 to Register 44.
Read the Value of Register 45.
4.6.4. Parameter Write Method

Version 1.02 | Fieldbus Guide | 11www.invertekdrives.com
5
CAN
5. CAN
5.1. Overview
The CAN communication profile is implemented according to the specification DS301 version 4.02 of CAN in automation
(www.can-cia.de). Specific device profiles such as DS402 are not supported.
CAN communication is enabled by default however to use any control functions parameter P-12 must be set to 7 or 8. Refer to the
Programming Guide for further Information.
5.2. CAN Communication Configuration Parameter
The CAN communication baud rate can be set by using parameter P-36. Available baud rates are: 125kbps, 250kbps, 500kbps,
1Mbps. (with default settings as 500kbps).
The Node ID is set up through drive address parameter P-36 as well with the default value of 1.
5.3. CAN COB-ID
The following default COB-ID and functions are supported:
Type COB-ID Function
NMT 000h Network management.
Sync 080h Synchronous message.
COB-ID can be configured to other value.
Emergency 080h + Node address Emergency message.
PDO1 (TX) 180h + Node address Process data object.
PDO1 is pre-mapped and enabled by default.
COB-ID can be configured to other value.
PDO2 is pre-mapped and disabled by default.
Transmission mode, COB-ID and mapping can be configured.
PDO1 (RX) 200h + Node address
PDO2 (TX) 280h + Node address
PDO2 (RX) 300h + Node address
SDO (TX) 580h + Node address SDO channel can be used for drive parameter access.
SDO (RX) 600h + Node address
Error Control 700h + Node address Guarding and Heartbeat function are supported.
COB-ID can be configured to other value.
NOTE
The SDO channel only supports expedited transmission.
A maximum of 2 Process Data Objects (PDO) are supported.
o All PDOs are pre-mapped; however, PDO2 is disabled by default
o The table below gives the default PDO mapping information.
Customer configuration (mapping) will NOT be saved during power down. This means that the CAN configuration will restore to
its default condition each time the drive is powered up.
The following default COB-ID and functions are supported:
Type
COB-ID
Function
NMT
000h
Network management.
Sync
080h
Synchronous message.
COB-ID can be configured to other value.
Emergency
080h + Node address Emergency message.
080h + Node address Emergency message.
PDO1 (TX)
180h + Node address Process data object.
180h + Node address Process data object.
PDO1 is pre-mapped and enabled by default.
COB-ID can be configured to other value.
PDO2 is pre-mapped and disabled by default.
Transmission mode, COB-ID and mapping can be configured.
PDO1 (RX)
200h + Node address
PDO2 (TX)
280h + Node address
PDO2 (RX)
300h + Node address
SDO (TX)
580h + Node address
SDO channel can be used for drive parameter access.
SDO (RX)
600h + Node address
Error Control
700h + Node address
Guarding and Heartbeat function are supported.
COB-ID can be configured to other value.
The SDO channel only supports expedited transmission.
A maximum of 2 Process Data Objects (PDO) are supported.
All PDOs are pre
-mapped; however, PDO2 is disabled by default
he table below gives the default PDO mapping information.
ustomer configuration (mapping) will
NOT
be saved during power down. This means that the CAN configuration will restore to
its default condition each time the drive is powered up.

12 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
5
CAN
5.4. PDO Default Mapping
Objects
No.
Mapped
Object Length Mapped Function Transmission Type For information on the values
RX
PDO1
1 2000h Unsigned 16 Control word
254
Valid immediately
Refer to section 11.1.
Control Registers on
page 54
2 2001h Integer 16 Frequency setpoint
3 2003h Unsigned 16 User ramp reference
4 0006h Unsigned 16 Dummy
TX
PDO1
1 200Ah Unsigned 16 Drive status register
254
Send after receiving
RX PDO 1
Refer to section 11.1.1.
Drive Control Word
PDO0 on page 54
2 200Bh Integer 16 Motor speed Hz
3 200Dh Unsigned 16 Motor current
4 2010h Integer 16 Drive temperature
RX
PDO2
1 0006h Unsigned 16 Dummy
254
2 0006h Unsigned 16 Dummy
3 0006h Unsigned 16 Dummy
4 0006h Unsigned 16 Dummy
TX
PDO2
1 2011h Unsigned 16 DC bus voltage
254
2 2012h Unsigned 16 Digital input status
3 2013h Integer 16 Analog input 1 (%)
4 2014h Integer 16 Analog input 2 (%)
5.5. PDO Transmission Type
Various transmission modes can be selected for each PDO. For RX PDO, the following modes are supported:
Transmission Type Mode Description
0 – 240 Synchronous The received data will be transferred to the drive active control register when the next sync
message is received.
254, 255 Asynchronous The received data will be transferred to the drive active control register immediately without delay.
For TX PDO, the following modes are supported:
Transmission Type Mode Description
0 Acyclic synchronous TX PDO will only be sent out if the PDO data has changed and PDO will be transmitted on
reception of SYNC object.
1-240 Cyclic synchronous TX PDO will be transmitted synchronously and cyclically. The transmission type indicates the
number of SYNC object that are.
254 Asynchronous TX PDO will only be transferred once corresponding RX PDO has been received.
255 Asynchronous TX PDO will only be transferred anytime if PDO data value has changed.
5.6. CAN Specific Object Table
Index Sub Index Function Access Type PDO Map Default Value
1000h 0 Device Type RO U32 N 0
1001h 0 Error Register RO U8 N 0
1002h 0 Manufacturer Status Register RO U16 N 0
1005h 0 COB-ID Sync RW U32 N 00000080h
1008h 0 Manufacturer Device Name RO String N ODE3
1009h 0 Manufacturer Hardware Version RO String N x.xx
100Ah 0 Manufacturer Software Version RO String N x.xx
100Ch 0 Guard Time (1ms) RW U16 N 0
100Dh 0 Lifetime Factor RW U8 N 0
1014 h 0 COB-ID EMCY RW U32 N 00000080h+Node ID
1015 h 0 Inhibit Time Emergency (100µs) RW U16 N 0
RX
PDO2
254
2 0006h Unsigned 16
2 0006h Unsigned 16
2 0006h Unsigned 16
Dummy
3 0006h Unsigned 16
3 0006h Unsigned 16
3 0006h Unsigned 16
Dummy
4 0006h Unsigned 16
4 0006h Unsigned 16
4 0006h Unsigned 16
Dummy
TX
PDO2
1 2011h Unsigned 16 DC bus voltage
1 2011h Unsigned 16 DC bus voltage
1 2011h Unsigned 16 DC bus voltage
1 2011h Unsigned 16 DC bus voltage
254
2 2012h Unsigned 16 Digital input status
2 2012h Unsigned 16 Digital input status
2 2012h Unsigned 16 Digital input status
2 2012h Unsigned 16 Digital input status
3 2013h Integer 16 Analog input 1 (%)
3 2013h Integer 16 Analog input 1 (%)
3 2013h Integer 16 Analog input 1 (%)
3 2013h Integer 16 Analog input 1 (%)
4 2014h Integer 16 Analog input 2 (%)
4 2014h Integer 16 Analog input 2 (%)
4 2014h Integer 16 Analog input 2 (%)
4 2014h Integer 16 Analog input 2 (%)
5.5. PDO Transmission Type
Various transmission modes can be selected for each PDO. For RX PDO, the following modes are supported:
Transmission Type Mode
Transmission Type Mode
Description
0 – 240
Synchronous
The received data will be transferred to the drive active control register when the next sync
message is received.
254, 255 Asynchronous The received data will be transferred to the drive active control register immediately without delay.
254, 255 Asynchronous The received data will be transferred to the drive active control register immediately without delay.
254, 255 Asynchronous The received data will be transferred to the drive active control register immediately without delay.
For TX PDO, the following modes are supported:
Transmission Type Mode
Transmission Type Mode
Description
0
Acyclic synchronous
TX PDO will only be sent out if the PDO data has changed and PDO will be transmitted on
reception of SYNC object.
1-240 Cyclic synchronous
1-240 Cyclic synchronous
TX PDO will be transmitted synchronously and cyclically. The transmission type indicates the
number of SYNC object that are.
254
Asynchronous TX PDO will only be transferred once corresponding RX PDO has been received.
Asynchronous TX PDO will only be transferred once corresponding RX PDO has been received.
255
Asynchronous TX PDO will only be transferred anytime if PDO data value has changed.
Asynchronous TX PDO will only be transferred anytime if PDO data value has changed.
5.6. CAN Specific Object Table

Version 1.02 | Fieldbus Guide | 13www.invertekdrives.com
5
CAN
Index Sub Index Function Access Type PDO Map Default Value
1016 h 0 Consumer Heartbeat Time No. of entries RO U8 N 1
1 Consumer Heartbeat Master Node & Time RW U32 N 0
1017 h 0 Producer Heartbeat Time (1ms) RW U16 N 0
1018 h
0 Identity Object No. Of entries RO U8 N 4
1 Vendor ID RO U32 N 0x0000031A
2 Product Code RO U32 N Drive Dependent
3 Revision Number RO U32 N x.xx
4 Serial Number RO U32 N Drive Dependent
1200h
0 SDO Parameter No. Of entries RO U8 N 2
1 COB-ID Client -> Server (RX) RO U32 N 00000600h+Node ID
2 COB-ID Server -> Client (TX) RO U32 N 00000580h+Node ID
1400h
0 RX PDO1 comms param. no. of entries RO U8 N 2
1 RX PDO1 COB-ID RW U32 N 40000200h+Node ID
2 RX PDO transmission type RW U32 N254
1401h
0 RX PDO2 comms param. no. of entries RO U8 N 2
1 RX PDO2 COB-ID RW U32 N C0000300h+Node ID
2 RX PDO2 transmission type RW U8 N 0
1600h
0 RX PDO1 1 mapping / no. of entries RW U8 N 4
1 RX PDO1 1st mapped object RW U32 N 20000010h
2 RX PDO1 2nd mapped object RW U32 N 20010010h
3 RX PDO1 3rd mapped object RW U32 N 20030010h
4 RX PDO1 4th mapped object RW U32 N 00060010h
1601h
0 RX PDO2 1 mapping / no. of entries RW U8 N 4
1 RX PDO2 1st mapped object RW U32 N 00060010h
2 RX PDO2 2nd mapped object RW U32 N 00060010h
3 RX PDO2 3rd mapped object RW U32 N 00060010h
4 RX PDO2 4th mapped object RW U32 N 00060010h
1800h
0 TX PDO1 comms parameter number of entries RO U8 N 3
1 TX PDO1 COB-ID RW U32 N 40000180h+Node ID
2 TX PDO1 transmission type RW U8 N 254
3 TX PDO1 Inhibit time (100µs) RW U16 N 0
1801h
0 TX PDO2 comms param no. of entries RO U8 N 3
1 TX PDO2 COB-ID RW U32 N C0000280h+Node ID
2 TX PDO2 transmission type RW U8 N 0
3 TX PDO2 Inhibit time (100µs) RW U16 N 0
1A00h
0 TX PDO1 mapping / no. of entries RW U8 N 4
1 TX PDO1 1st mapped object RW U32 N 200A0010h
2 TX PDO1 2nd mapped object RW U32 N 200B0010h
3 TX PDO1 3rd mapped object RW U32 N 200D0010h
4 TX PDO1 4th mapped object RW U32 N 20100010h
1A01h
0 TX PDO2 mapping / no. of entries RW U8 N 4
1 TX PDO2 1st mapped object RW U32 N 20110010h
2 TX PDO2 2nd mapped object RW U32 N 20120010h
3 TX PDO2 3rd mapped object RW U32 N 20130010h
4 TX PDO2 4th mapped object RW U32 N 20140010h
5.7. Parameter Access
All user adjustable parameters are accessible through the CAN communication interface. The Programming Guide document provides
the Index for each parameter along with any scaling or information how the data for each parameter is stored.
5.8. Additional Status Indices
Further additional status Indices are present in the drive. These are described in section 11. Control & Status Registers on page 54.
1400h
1
RX PDO1 COB-ID
RW
U32
N 40000200h+Node ID
N 40000200h+Node ID
2
RX PDO transmission type
RW
U32
N
254
0 RX PDO2 comms param. no. of entries
0 RX PDO2 comms param. no. of entries
RO
U8 N
U8 N
2
1
RX PDO2 COB-ID
RW
U32
N C0000300h+Node ID
N C0000300h+Node ID
2
RX PDO2 transmission type
RW
U8 N
U8 N
0
1600h
0 RX PDO1 1 mapping / no. of entries
0 RX PDO1 1 mapping / no. of entries
RW
U8 N
U8 N
4
1
RX PDO1 1st mapped object
RW
U32
N
20000010h
2
RX PDO1 2nd mapped object
RW
U32
N
20010010h
3
RX PDO1 3rd mapped object
RW
U32
N
20030010h
4
RX PDO1 4th mapped object
RW
U32
N
00060010h
0 RX PDO2 1 mapping / no. of entries
0 RX PDO2 1 mapping / no. of entries
RW
U8 N
U8 N
4
1
RX PDO2 1st mapped object
RW
U32
N
00060010h
2
RX PDO2 2nd mapped object
RW
U32
N
00060010h
3
RX PDO2 3rd mapped object
RW
U32
N
00060010h
4
RX PDO2 4th mapped object
RW
U32
N
00060010h
1800h
0 TX PDO1 comms parameter number of entries
0 TX PDO1 comms parameter number of entries
RO
U8 N
U8 N
3
1
TX PDO1 COB-ID
RW
U32
N 40000180h+Node ID
N 40000180h+Node ID
2
TX PDO1 transmission type
RW
U8 N
U8 N
254
3
TX PDO1 Inhibit time (100µs)
RW
U16
N
0
0 TX PDO2 comms param no. of entries
0 TX PDO2 comms param no. of entries
RO
U8 N
U8 N
3
1
TX PDO2 COB-ID
RW
U32
N C0000280h+Node ID
N C0000280h+Node ID
2
TX PDO2 transmission type
RW
U8 N
U8 N
0
3
TX PDO2 Inhibit time (100µs)
RW
U16
N
0
1A00h
0
TX PDO1 mapping / no. of entries
RW
U8 N
U8 N
4
1
TX PDO1 1st mapped object
RW
U32
N
200A0010h
2
TX PDO1 2nd mapped object
RW
U32
N
200B0010h

14 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
6
Ethernet Connection
6. Ethernet Connection
6.1. Available Interface Options
Ethernet interfaces are optionally available for Optidrive E3 and Optidrive Compact 2 products which support either Ethernet/IP
protocol or Modbus TCP protocol. Part numbers for these interfaces are shown in the table below. The correct interface should be
selected according to the drive type.
Drive Family Interface Type Ethernet/IP Interface
Model Code
Modbus TCP Interface
Model Code
Optidrive E3 IP20 External Option OPT-2-ETHEG-IN OPT-3-MTPEG-IN
Optidrive E3 IP66 Internal Option Drive Model Code + “-EIP“ Drive Model Code + “-MTP“
Optidrive Compact 2 Plug in Option OPT-2-ETHIG-IN OPT-2-MTPEG-IN
6.2. External Interface
6.2.1. Layout
ERROR LED Indicator
COMM LED Indicator
Module Status LED
Network Status LED
COMM ERROR
P1 Ethernet P2
D1
MS
NS
D2
Serial Port D1
Serial Port D2
Ground Tab
Ethernet Port P2
Ethernet Port P1
6.2.2. Labelling
There are two labels:
Top Label:
Provides the MAC ID for the module
Side Label:
Provides, the model code and
serial number data
COMM ERROR
P1 Ethernet P2
D1
MS
NS
D2
6.2. External Interface
6.2.1. Layout
ERROR LED Indicator
COMM LED Indicator
Module Status LED
Network Status LED
COMM ERROR
COMM ERROR
P1 Ethernet P2
D1
MS
NS
D2
Serial Port D1
Serial Port D2
Ground Tab
Ethernet Port P2
Ethernet Port P1
6.2.2. Labelling
There are two labels:
Top Label:
COMM ERROR
COMM ERROR
D1
D2
COMM ERROR
COMM ERROR
COMM ERROR

Version 1.02 | Fieldbus Guide | 15www.invertekdrives.com
6
Ethernet Connection
6.2.3. Mechanical Installation
The Ethernet IP interface is intended for mounting inside a control cabinet adjacent to the drive.
The unit should be mounted in a vertical position only, on a flat, flame resistant, vibration free mounting.
The unit must be installed in a pollution degree 1 or 2 environment only.
Use the module as a template to mark the locations for drilling the mounting screws.
Drill and tap the holes as required.
Secure the unit to the backplate using suitable screws, 1Nm.
COMM ERROR
P1 Ethernet P2
D1
MS
NS
D2
C
A
D
B
A B C D Weight
mm in mm in mm in mm in g oz
89 3.50 76 2.99 47 1.85 31 1.22 65 2.29
Mounting Bolts
Metric UNF
M4 #8
P1 Ethernet P2
MS
NS
A
B
C
D Weight
D Weight
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
mm in mm in mm in mm in g oz
89 3.50
76
2.99 47
2.99 47
1.85
31
1.22
65 2.29
65 2.29
Mounting Bolts
Metric UNF
Metric UNF
M4
#8

16 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
6
Ethernet Connection
6.2.4. Electrical Installation
WARNING! Do not connect Ethernet devices to ports D1 or D2. They may be damaged!
Power supply to the module is provided from the connected drive via the RJ45 connection.
WARNING! Do not use cross over cables! Cables must be pin to pin connected!
COMM ERROR
P1 Ethernet P2
D1
MS
NS
D2
GND
Ethernet Network
WARNING!
One Drive only on this port!
No additional network connection
Max cable length: 3 metres
W
ARNING!
One de
vice only on this port!

External Keypad

Optistick Smart

PC Connection Kit
No additional net
work connection
Max cable length:
25 metres
Ground tab – Observe the recommended grounding procedure for the fieldbus network and if necessary, connect this tab to ground
where required.
6.3. Internal Interface for IP66 Drives
6.3.1. Layout – Internal Interface
L1 L3 EMCL2/N UVW
1 2 3 4 5 6 7 8 9 10 11
I0I0I I0I0I
IOIOI: Dual serial ports.
WARNING! Do not connect Ethernet devices here!
These ports are for external serial connection of
remote keypad and PC connection only!
Port P1: Primary Ethernet port
Port P2: Secondary Ethernet Port
6.3.2. Labelling – Internal Interface
The MAC address of the device is shown below the ports.
COMM ERROR
COMM ERROR
P1 Ethernet P2
MS
NS
D2
GND
Ethernet Network
One Drive only on this port!
No additional network connection
Max cable length: 3 metres
PC Connection Kit
No additional net
work connection
Max cable length:
25
metres
Ground tab – Observe the recommended grounding procedure for the fieldbus network and if necessary, connect this tab to ground
where required.
6.3. Internal Interface for IP66 Drives
6.3.1. Layout – Internal Interface
1 2 3 4 5 6 7 8 9
10
10 10
11
I0I0I I0I0I
IOIOI: Dual serial ports.
WARNING
! Do not connect Ethernet devices here!
These ports are for external serial connection of
remote keypad and PC connection only!

Version 1.02 | Fieldbus Guide | 17www.invertekdrives.com
6
Ethernet Connection
6.4. Optional Interface for Compact 2 Basic Drives
6.4.1. Installation
The Ethernet/IP interface is mounted underneath the control pod.
Remove the control pod as described in the Compact 2 installation guide.
Locate the Ethernet/IP interface in the slot below the control pod.
Refi t the control pod.
6.4.2. Layout
MAC Address shown here
P1: Primary Ethernet Port
P2: Secondary Ethernet Port
WARNING! Do not connect Ethernet cables to the
RJ45 port on the control Pod!
6.5. Drive Parameter Settings
6.5.1. Overview
The following parameter settings are required in the drive. For further description of the drive parameters, refer to the drive user guide.
Drive Type Optidrive E3 (ODE-3-…) Setting
Parameter
Drive Address P-36 Index 1 1
Modbus RTU Baud Rate P-36 Index 2 115.2kbps
Modbus RTU Data Format N/A N-1
Communication Loss Reaction P-36 Index 3 As required
Command Source Selection P - 12 Select for Fieldbus Control if control of the drive operation is required
P1: Primary Ethernet Port
P2: Secondary Ethernet Port
WARNING
! Do not connect Ethernet cables to the
RJ45 port on the control Pod!
6.5. Drive Parameter Settings
6.5.1. Overview
The following parameter settings are required in the drive. For further description of the drive parameters, refer to the drive user guide.
Drive Type
Optidrive E3 (ODE-3-…)
Setting
Parameter
Drive Address
P-36 Index 1
1
Modbus RTU Baud Rate
P-36 Index 2
115.2kbps
Modbus RTU Data Format
N/A
N-1
Communication Loss Reaction
P-36 Index 3
As required
Command Source Selection
P - 12
Select for Fieldbus Control if control of the drive operation is required

18 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
7
Internal Webserver
7
Internal Webserver
7. Internal Webserver
7.1. Overview
A web server interface is present in all Ethernet based fieldbus interfaces and can be accessed using the IP address or host name.
Default IP address: 192.168.1.253.
Hostname: OPCxxxxxxxxxx, where xxxxxxxxxx = ‘PR ID’ value shown on the top product label as described in section 6.2.2.
Labelling on page 14 or 6.3.2. Labelling – Internal Interface on page 16.
The IP address and Host Name may be reconfigured by the user via the Web Server or Ethernet/IP Class 0xF4.
7.2. Default Login
To access to the web server:
Open a web browser on your connected PC.
Enter the module IP address in the address bar.
Default admin login details:
o Username: Admin
Password: Serial Number of the module (see product label as described in section 6.2.2. Labelling on page 14 or 6.3.2.
Labelling – Internal Interface on page 16.)
7.3. Web Server Contents
The web server contains 7 pages as described below.
7.3.1. System
Information about the Module and Primary Protocol is displayed. This information is Read Only.
7.3.2. Users
Information about user’s accounts is displayed.
Default admin login details:
Username:
Admin
assword:
Serial Number
of the module (see product label as described in section
6.2.2. Labelling on page 14
or
6.3.2.
Labelling – Internal Interface on page 16
.)
7.3. Web Server Contents
The web server contains 7 pages as described below.
7.3.1. System
Information about the Module and Primary Protocol is displayed. This information is Read Only.
7.3.2. Users

Version 1.02 | Fieldbus Guide | 19www.invertekdrives.com
7
Internal Webserver
7
Internal Webserver
7.3.3. Network (IP Address and Network Settings)
Information about network adapter configuration is displayed.
7.3.4. DiagLink (Ethernet Configuration Message)
Information about the serial communication settings to the drive are displayed.
7.3.5. Network (Ethernet Network Statistics)
Statistic information about the ethernet connections is displayed.
7.3.4. DiagLink (Ethernet Configuration Message)
Information about the serial communication settings to the drive are displayed.
7.3.5. Network (Ethernet Network Statistics)
Statistic information about the ethernet connections is displayed.

20 | Fieldbus Guide | Version 1.02 www.invertekdrives.com
7
Internal Webserver
7
Internal Webserver
7.4. Changing the IP Address
Go to Network settings screen:
The IP address can be assigned to the module manually by the User (Fixed or Static IP Address) or automatically by the DHCP Server.
The default configuration method is Fixed IP address.
7.4.1. Automatically (DHCP) Assigned IP Address
To automatically (DHCP) assign an IP address to the module please select DHCP mode in the Configuration Method and
confirm changes by clicking APPLY NEW VALUES.
NOTE A power cycle is necessary after changing the network settings. Please click REBOOT button at the top left corner or power
cycle the module!
The IP address can be assigned to the module manually by the User (Fixed or Static IP Address) or automatically by the DHCP Server.
The default configuration method is Fixed IP address.
7.4.1. Automatically (DHCP) Assigned IP Address
To automatically (DHCP) assign an IP address to the module please select
DHCP
mode in the
Configuration Method
and
confirm changes by clicking
APPLY NEW VALUES
.
NOTE
A power cycle is necessary after changing the network settings. Please click REBOOT button at the top left corner or power
cycle the module!