Professional Documents
Culture Documents
Vacon OPTE9 Dual Port Ethernet Board Manual DPD01583F UK
Vacon OPTE9 Dual Port Ethernet Board Manual DPD01583F UK
ac drives
opte9
dual port ethernet option board
installation manual
vacon • 3
TABLE OF CONTENTS
Document: DPD01583F
Release date : 2/1/18
1. Safety ...............................................................................................................6
1.1 Danger................................................................................................................................6
1.2 Warnings ............................................................................................................................7
1.3 Earthing and earth fault protection ...................................................................................8
2. OPTE9 Dual Port Ethernet - General ................................................................9
2.1 New features ....................................................................................................................10
3. OPTE9 Ethernet board technical data ............................................................11
3.1 General .............................................................................................................................11
3.2 Cables...............................................................................................................................11
4. Layout and connections..................................................................................12
4.1 Layout and connections ...................................................................................................12
4.2 LED Indications ................................................................................................................13
4.2.1 Profinet IO ........................................................................................................................14
4.3 Ethernet devices ..............................................................................................................15
4.3.1 Human to machine...........................................................................................................15
4.3.2 machine to machine.........................................................................................................16
4.4 Connections and wiring....................................................................................................17
4.4.1 Topology: Star ..................................................................................................................17
4.4.2 Topology: Daisy Chain ......................................................................................................17
4.4.3 Topology: Ring..................................................................................................................18
4.5 ACD (Address Conflict Detection) ....................................................................................24
4.6 Time synchronization .......................................................................................................25
4.6.1 Using ID 2551 ...................................................................................................................25
4.6.2 SNTP (Simple Network Time Protocol) ...........................................................................25
5. Installation.....................................................................................................26
5.1 Installation in VACON® NX..............................................................................................27
5.2 Installation in VACON® 20...............................................................................................29
5.2.1 Frames MI1, MI2, MI3 ......................................................................................................29
5.2.2 Frames MI4, MI5 ..............................................................................................................32
5.3 Installation in VACON® 20 X and 20 CP ..........................................................................35
5.4 Installation in VACON® 100 family..................................................................................37
5.5 installation in VACON® 100 X ..........................................................................................40
5.6 PC Tools ...........................................................................................................................43
5.6.1 PC tool support ................................................................................................................43
5.6.2 Updating the OPTE9 option board firmware with VACON® Loader ...............................44
5.6.3 PC Tools for VACON® NX / NCIPConfig ..........................................................................47
5.6.4 PC Tools for VACON® NX / NCDrive ...............................................................................49
5.6.5 PC Tools for VACON® 100 family and VACON® 20 / VACON® Live...............................52
6. Commissioning ..............................................................................................55
6.1 Option board menu...........................................................................................................55
6.1.1 Option board parameters.................................................................................................55
6.1.2 Option board monitoring values ......................................................................................58
6.1.3 Communication protocol .................................................................................................59
6.1.4 IP Mode and IP settings ...................................................................................................59
6.1.5 Speed and duplex .............................................................................................................60
6.1.6 Communication timeout ..................................................................................................61
6.1.7 Profinet IO - Name of Station ..........................................................................................61
6.1.8 EIP Input and Output instance .........................................................................................62
6.1.9 EIP Product code offset ...................................................................................................62
6.1.10 Mode .................................................................................................................................62
1. SAFETY
This manual contains clearly marked cautions and warnings that are intended for your personal
safety and to avoid any unintentional damage to the product or connected appliances.
Read the information included in cautions and warnings carefully.
The cautions and warnings are marked as follows:
= WARNING or CAUTION
13006.emf
1.1 Danger
The components of the power unit are live when the drive is connected to mains
potential. Coming into contact with this voltage is extremely dangerous and may
9000.emf
go out (if no keypad is attached, see the indicators on the cover). Wait additional 5
minutes before starting any work on the drive.
1.2 Warnings
Do not perform any measurements when the AC drive is connected to the mains.
13006.emf
The earth leakage current of the AC drives exceeds 3.5mA AC. According to
standard EN61800-5-1, a reinforced protective ground connection must be
ensured. See Chapter 1.3.
13006.emf
13006.emf
Only spare parts delivered by VACON® can be used.
At power-up, power break or fault reset the motor will start immediately if the
start signal is active, unless the pulse control for Start/Stop logic has been selected.
Furthermore, the I/O functionalities (including start inputs) may change if
parameters, applications or software are changed. Disconnect, therefore, the
13006.emf
13006.emf
CAUTION!
The AC drive must always be earthed with an earthing conductor connected to the earthing terminal
marked with .
The earth leakage current of the drive exceeds 3.5mA AC. According to EN61800-5-1, one or more
of the following conditions for the associated protective circuit must be satisfied:
a) The protective conductor must have a cross-sectional area of at least 10 mm2 Cu or 16
mm2 Al, through its total run.
b) Where the protective conductor has a cross-sectional area of less than 10 mm2 Cu or 16
mm2 Al, a second protective conductor of at least the same cross-sectional area must be
provided up to a point where the protective conductor has a cross-sectional area not less
than 10 mm2 Cu or 16 mm2 Al.
c) Automatic disconnection of the supply in case of loss of continuity of the protective
conductor.
The cross-sectional area of every protective earthing conductor which does not form part of the
supply cable or cable enclosure must, in any case, be not less than:
- 2.5mm2 if mechanical protection is provided or
- 4mm2 if mechanical protection is not provided.
The earth fault protection inside the AC drive protects only the drive itself against earth faults in the
motor or the motor cable. It is not intended for personal safety.
Due to the high capacitive currents present in the AC drive, fault current protective switches may
not function properly.
Do not perform any voltage withstand tests on any part of the AC drive. There is
a certain procedure according to which the tests must be performed. Ignoring
this procedure can cause damage to the product.
13006.emf
NOTE! You can download the English and French product manuals with applicable safety,
warning and caution information from
http://drives.danfoss.com/knowledge-center/technical-documentation/.
REMARQUE Vous pouvez télécharger les versions anglaise et française des manuels produit
contenant l’ensemble des informations de sécurité, avertissements et mises en garde
applicables sur le site http://drives.danfoss.com/knowledge-center/technical-documentation/
.
Every appliance connected to an Ethernet network has two identifiers: a MAC address and an IP
address. The MAC address (Address format: xx:xx:xx:xx:xx:xx) is unique for each appliance and
cannot be changed.The Ethernet board’s MAC address can be found on the sticker attached to the
board.
In a local network, IP addresses can be defined by the user as long as all the units connected to the
network are given the same network portion of the address. Overlapping IP addresses cause
conflicts between appliances. For more information about setting IP addresses, see Chapter 6.
Abbreviation Explanation
ACD Address Conflict Detection
Cyclic Redundancy Check is an error-detecting code commonly used in
CRC
fieldbusses to detect accidental changes to raw data.
Dynamic Host Configuration Protocol is used for dynamical resolving of net-
DHCP
work configuration parameters like an IP address.
FB Fieldbus
GW Gateway
HI Upper 8/16 bits in a 16/32 bit value.
LO Lower 8/16 bits in a 16/32 bit value.
LWIP Light weight TCP/IP protocol stack for embedded systems.
Modbus TCP / Simple and vendor-neutral communication protocol intended for monitoring
Modbus UDP and controlling of field devices.
PDI Process data in (Profinet IO)
PDO Process data out (Profinet IO)
Ethernet physical interface X, where X represents the number
PHY(X)
of interface
PLC Programmable Logic Controller
PNU Parameter number (Profinet IO)
Profinet is a standard for industrial automation in Ethernet network. Profi-
Profinet IO
net IO describes the exchange of data between controllers and field devices.
RPM Revolutions per minute
RSTP Rapid Spanning Tree Protocol
SNTP Simple Network Time Protocol
Abbreviation Explanation
Transmission Control Layer provides reliable, ordered and error-checked
TCP delivery of data streams between computers that are connected to a local
area network.
UTC Coordinated Universal Time
The following table shows the new features that are added in the OPTE9 Dual Port Ethernet's
firmware versions.
3.1 General
3.2 Cables
For connecting the OPTE9 devices, use only Ethernet cables that meet at least the requirements of
category 5 (CAT5) according to EN 50173 or ISO/IEC 11801.
RN ER BS
1
B C
2
11592_00
RN ER BS
A
1
11593_00
A LED indications
The table below lists possible LED combinations and their meanings. When the EtherNet/IP is
active, the option board follows CIP standard for LED indications. Therefore, the indications
described in Table 7 do not apply. See Chapter 9.1.4 "LED functionality".
Table 7. List of possible LED combinations
Protocol is communicating.
4.2.1 Profinet IO
When using the "Node Flashing Test" function, you can determine to which device you are directly
connected. For example, in Siemens S7, by using the menu command "PLC > Diagnostics/Setting >
Node Flashing Test..." you can identify the station directly connected to the PG/PC if all three LEDs
are flashing green.
1 2 3 4 5 6 7 8
Ethernet switch
Power
11594_uk
NOTE! NCDrive can be used in VACON® NXS and NXP drives via Ethernet. VACON® Live can be used
with VACON® 100 family.
NOTE! The Ethernet connection to VACON® 20, VACON® 20 X and VACON® 20 CP via the OPTE9 Dual
Port Ethernet is not yet supported.
MASTER
Real-Time Control
- Start/Stop, Direction,...
- Reference
- Feedback
1 2 3 4 5 6 7 8
Ethernet switch
Power
11595_uk
Each of these topologies has their own advantages and disadvantages. When designing the network
you must carefully consider the risks and benefits against the cost of the selected topology.
The OPTE9 supports 10/100Mb speeds in both Full- and Half-duplex modes. However, real-time
process control requires the Full-duplex mode and the 100-megabit speed. The boards must be
connected to the Ethernet network with a Shielded Twisted Pair (STP) CAT-5e cable (or better).
Use only industrial standard components in the network and avoid complex structures to minimize
the length of response time and the amount of incorrect dispatches. Because of the internal switch
in OPTE9, it does not matter in what port of the option board the Ethernet cables are connected to.
In star network, all the devices are connected to the same switch(es). This topology reduces the
damage caused by single cable failure. It would affect only to a single drive instead of them all. In
this setup, a drive will receive only broadcast/multicast messages and messages directed to this
drive.
Only one port from the OPTE9 can be connected to a switch in the star topology. Connecting both
ports to switch(es) will cause an involuntary Ethernet ring which, in this setup, will break the
network.
PLC 1 2 3 4 5 6 7 8
Power
...
11660_uk
The daisy-chaining allows you to reduce the costs for cabling and networking equipment such as
switches. The maximum number of daisy-chained boards is 32. This restriction comes from the
average latency (20 to 40 microseconds) per Ethernet switch. The drawback in the daisy chain
topology is that it increases traffic in all except the last drive. The first drive in the daisy chain sees
all the traffic in the chain. Also damage to a single cable will drop all drives behind it from the
network.
Both in daisy chain topology and in star topology, the last drive's port must not be connected back
to the same line. This would cause an involuntary Ethernet ring which will break the network.
PLC
...
11597A_uk
In some cases it is possible to use OPTE9 in a ring topology. The ring topology gains the same
reduced cabling cost as the daisy chain topology, but decreases the damage caused by a single cable
failure.
OPTE9 can be used with the following media redundancy protocols:
NOTE! Ring network sizes should be limited from what is specified in the media redundancy
protocols (usually up to 50 nodes) depending on the network load. When low I/O data intervals are
used, we recommend that ring networks should be limited to fewer than 32 devices. High load on
network can cause recovery times to increase and in worst cases to trigger a watchdog failure.
To use the RSTP protocol, add a managed Ethernet switch that supports the RSTP protocol. If a
single link is broken, the RSTP switch will notice this and start sending data from the PLC to both
directions effectively creating two daisy chains. When the link has been repaired, the switch will
notice this too and reverts back to normal operating mode. Compared to the star topology, the ring
topology adds more network traffic to almost all drives. Damage to two cables will always create an
isolated subnetwork.
In the RSTP configuration, one of the ports in the switch is "Designated Port" (DP) and the other
"Alternative Port" (AP). When the network is functioning properly, the traffic flows through the
designated port. Only the BPDU (Bridge Protocol Data Unit) packets are transferred through the AP
port. The BPDU packets are used by the switch to determine if the network is working properly. If it
detects that the BPDU packets do not go through the ring, it will change the alternative port to a
second designated port. Now the switch will send packets to both directions in the broken ring (see
Figure 8).
Each designated port has a list of MAC addresses which are behind that port. Only frames directed
to the device in the MAC list are forwarded into that designated port. The broadcast and multicast
frames are sent to all designated ports.
DP AP
Power
...
11661_uk
In the example below, the Ethernet communication will be interrupted to device number three and
other devices after that when the link is broken. The Fieldbus communication maybe faulted when
the link is broken, but when the switch enables the second designated port, the connections can be
reopened. In the RSTP protocol, it generally takes few seconds before the second designated port
will be activated. This depends on the BPDU exchange cycle, which is 2 seconds by default.
DP DP
Power
...
11662_uk
NOTE! The OPTE9 switch itself does not implement the RSTP protocol, so the network will always
need a third party switch to support it.
Configuration example
The screenshots below (Figure 9, Figure 10) show one example of configuring the RSTP in the switch
(in this case an EtherWAN switch). Port two is the designated port and port one is the alternative
port. The PLC was connected to port nine (the laptop taking the screenshots was in port 16). When
configuring your switch, refer to the switch manufacturer's manual.
The MRP is designed to react deterministically on a cable failure. This makes it suitable to be used
in process automation. One of the nodes in the network has the role of Media Redundancy Master
(MRM), which observes and controls the ring topology in order to react to network faults. Usually
this device is PLC or network switch.
The other nodes in the network are called Media Redundancy Clients (MRC), and they react on
received configuration frames from the MRM and can detect link changes on its ring ports. OPTE9
supports only MRC functionality.
The MRM and MRC have two ring ports, which take one of the following states:
• DISABLED
- All frames are dropped
• BLOCKING
- All frames are dropped, except the following frames:
a) MRP frames (e.g. MRP_test and MRP_TopologyChange)
b) Frames specified to pass ports in "Discarding" state, e.g. LLDP frames
• FORWARDING
- All frames are forwarded according to normal behaviour
The MRM sends MRP_Test frames in a configured time period to monitor the state of the ring
topology. If the MRM receives its own MRP_Test frames (network is closed), one of the ring ports is
set to FORWARDING state and the other to BLOCKED state (see Figure 11). If the MRP_Test frames
are not received by the MRM (network is open), it sets both of its ring ports to FORWARDING state
(see Figure 12).
The following figure shows an example of a MRP network, where the PLC acts as a MRM.
PLC
MRM
Forwarding Blocked
...
11713_uk
In the example below, the Ethernet communication will be interrupted to device number three and
other devices after that when the link is broken.
PLC
MRM
Forwarding Forwarding
...
11714_uk
NOTE: The OPTE9 can use MRP (as MRC) only when PROFINET IO is the selected protocol. MRP is
available in OPTE9 version V006 or later.
MRP Recovery Times and Fast MRP
MRP can be configured to send test frames with different time periods, depending on the maximum
allowed recovery time for the network. These times are set as the guaranteed time for a network of
50 nodes to recover from a ring error.
Typically, in PROFINET IO systems the recovery time is defined as 200 ms. However, the MRP
specification allows for recovery times of 500, 200, 30 and 10 ms. OPTE9 can be used in systems with
the lowest recovery time of 10 ms. This is often called “Fast MRP”.
When you use MRP in a PROFINET IO network, we suggest that you set the watchdog time of each
device in the ring to the maximum recovery time, usually 200 ms. This guarantees that a cable
failure does not interrupt the fieldbus connection.
Device Level Ring (DLR) protocol provides a means for detecting, managing and recovering from
faults in a ring-based network. It supports a single-ring topology. Multiple or overlapping rings are
not supported. Other features include "Sign on process" used to identify all ring participants and
"Neighbor check process" which allows nodes to check the health of their adjacent nodes.
One device acts as a ring supervisor, monitoring the state of the ring while other devices act as DLR
nodes. Only one device can act as an active supervisor, although backup supervisors are possible.
Nodes can be divided into Beacon- and Announce-based nodes depending on which frames the
nodes process. OPTE9 supports Announce-based functionality.
DLR nodes have three states:
• IDLE_STATE: indicating linear topology for non-supervisor nodes
• FAULT_STATE: initial state for enabled ring supervisor, or when ring fault has been detected
• NORMAL_STATE: normal function in ring topology mode
The active ring supervisor sends Beacon frames from both its ring ports once per beacon interval
(400 μs by default) to monitor the state of the ring and an Announce frame once per second. If the
Beacon frames are received back at the supervisor, one of its ports is set to blocking and the other
to forwarding state (Figure 13).
• Only the following packets are processed from the blocked port:
• Beacon frames from self and other supervisors
• Link_Status/Neighbor_Status frames
RING
SUPERVISOR
Beacon Beacon
Announce Announce
11857_uk
Figure 13. DLR ring: Network configuration when ring is closed (NORMAL_STATE)
If a network error occurs to DLR capable nodes, Link_Status frames are sent by nodes to inform the
ring supervisor immediately which port(s) have a failure (Figure 14).
ACTIVE RING
SUPERVISOR
A Link_Status frame triggers an error response in active ring supervisor, which unblocks traffic on
its previously blocked port (Figure 15). In case of an uncommon failure (for example, if cable breaks
between two non-DLR capable devices), the error is noticed from Beacon timeout value, and not
from Link_Status frames. Therefore, a recovery in a network with non-DLR capable devices can take
longer.
ACTIVE RING
SUPERVISOR
11859_uk
The ring recovers after Beacon frames again are received from both of the active ring supervisors
ring ports. Ring recovers back to its original state (Figure 13).
NOTE! DLR is active only when EtherNet/IP is the selected protocol. DLR is available in OPTE9
version V009 or later.
The OPTE9 option board implements ACD algorithm (IETF RFC 5227). The implementation includes
requirements from the EtherNet/IP protocol.
The ACD algorithm tries to actively detect if the IP address configured to this device is been used by
another device in the same network. To accomplish this, ACD sends four ARP request packets when
the device's Ethernet interface goes up or when its IP address changes. ACD prevents the use of the
Ethernet interface until the ARP probing finishes. This delays the startup of fieldbus protocols about
one second. During the delay or after it, the ACD passively checks incoming ARP messages for use
of the device's IP address. If another device with the same IP address is detected, the ACD will try
to defend its IP address with a single ARP message. If the other device with the same IP address
also supports ACD, it should stop using the address. If not, the ACD will close the Ethernet
connection and indicate the situation with LEDs. This is done according the "DefendWithPolicyB".
Other policies are not supported. If the fieldbus protocol has been active, a fieldbus fault may be
activated (depends on the fieldbus and drive application configuration).
System time in VACON® 100 family and VACON® NXP/NXS AC drives can be updated by writing 32
bit unsigned value to ID 2551. This value is seconds since 1.1.1970 (Unix time). In VACON® 100
family, the default timezone is UTC. Local time can be configured by changing the timezone and
setting the daylight saving mode. VACON® NXP/NXS AC drive does not have time settings, so value
written to this ID must be local time.
Simple Network Time Protocol enables usage of network time servers. Date and time information
is requested from the time server and set as system time. With SNTP, you can keep all devices in
your network in same time. This device acts as SNTP client. One use case for SNTP is that fault
history time stamps can now be compared between drives, enabling better fault tracing, for
example, detecting, in which order the drives were faulted. Synchronized date and time also enables
drives to automatically do programmed operations based on time information.
SNTP has two modes: Poll and Listen Only. Both also have modes where failure to update time will
generate fieldbus fault. In Poll mode, option board will request new time information periodically.
Default interval is 200 seconds. Lowest possible value is 30 seconds. This time can be adjusted from
SNTP parameters. In Listen only mode, time broadcast from server is expected every interval. You
can set two SNTP server addresses. For Poll mode, you have to define at least one SNTP server
address. You do not have to set server address in Listen Only mode, but in that case, the time
broadcasts are accepted from anyone who sends them.
When the SNTP client fails to receive time update from server within the time interval, it will first
wait (or request, depending on mode) the interval time again for the update. If it again does not
receive time update, it will change server and request (or wait for broadcast) from the second server.
If it receives the response from the second server, this server will be used until it fails. After device
restart, the SNTP will always first try the server number 1 (if its address has been defined). If the
second server also fails twice, the SNTP moves back to the server number one. If the selected mode
is Poll Fault or Listen Only Fault, a fieldbus fault is generated at this point.
SNTP also has port setting. By default, the SNTP port is 123, but you can change it. In Poll mode,
the requests are sent to this port on the time server. In Listen Only mode, the broadcasts are
listened in this port.
The SNTP monitoring values show the currently used SNTP server and the time since the last
received update. The SNTP status value tells status of the time synchronization. For example, if the
SNTP mode is Poll and you have not defined any SNTP server addresses, the SNTP status will be
"Invalid configuration (3)".
5. INSTALLATION
The VACON® OPTE9 Dual Port Ethernet option board can be used with the following VACON® AC
drives.
The VACON® 100 family AC drives are supported from the OPTE9 firmware version V003. The
process data in VACON® 100 family AC drives is 32 bit. The 32-bit process data support is planned
for later firmware release. Only 16-bit process data is supported.
EtherNet/IP support
EtherNet/IP protocol was added to OPTE9 firmware version V004. The table below shows required
minimum AC drive firmware version .
Make sure that the AC drive is switched off before an option or fieldbus board is
13006.emf
changed or added!
VACON® NX AC drive.
Install the OPTE9 Option Board in slot D or E on the control board of the AC drive.
Make sure that the grounding plate fits tightly in the clamp.
Make a sufficiently wide opening for your cable by cutting the grid as wide as
necessary.
6 Close the cover of the control unit and the cable cover.
11555A_00
11649_00
11556A_00
Connect the flat cable from the option board mounting frame to V20.
11557A_00
If a cable strain relief is required, attach the parts as shown in the figure.
11558A_00
11559A_00
11650_00
11560A_00
11561_00
1 1b: For MI5: Open the cover and release the fan connector.
11562_00
11564_00
11565_00
Attach the option board with connector PCB to V20 and connect the flex cable.
11566_00
Attach a suitable grounding plate to V20. The grounding plate is marked with
supported enclosure size.
MI 05
MI 04
11567_00
Assemble a clamp on top of the grounding plate on both sides of the option board.
11568_00
11569_00
7 8b: For MI5: Remount the fan connector and close the cover.
11570_00
11643_00
MU3 example
The relay outputs and other I/O-terminals may have a dangerous control voltage
present even when the drive is disconnected from mains.
13006.emf
7089_00
Install the option board into the slot as shown in the figure.
7090_00
Mount the option slot cover. Remove the plastic opening for the option board
terminals.
7091_00
M4x55
1
9174.emf
The relay outputs and other I/O-terminals may have a dangerous control voltage
present even when VACON® 100 family AC drive is disconnected from mains.
DANGER
Open the inner cover to reveal the option board slots (C,D,E).
3023.emf
D E
3024.emf
Then connect the cable to its appropriate OPTEC EtherCAT option board RJ-45
4 connector.
Fieldbus
cables
9202.emf
11638_00
To get access to the option board slots, remove the screws and open the cover of
the control unit.
11639_00
D E
11640_00
11641_00
Open the necessary holes in the cable entry plate. Do not open the other holes.
6 See the VACON® 100 X Installation Manual for the dimensions of the holes.
11642_00
5.6 PC Tools
Before connecting the OPTE9 option board to the network, its IP addresses must be set according
to the network. By default, the option board uses a DHCP server to get an IP address. If your network
does not have a DHCP server, you need to set an IP address manually. This can be accomplished
with the PC tools described in this chapter or with the AC drive's keypad (see Chapter 6).
For more information about IP addresses or a DHCP server, contact your network administrator.
This table describes what PC tools are supported in each AC drive type. The connection type “serial”
means a direct connection to the AC drive. The connection type “Ethernet” means a connection via
the OPTE9 Ethernet port.
5.6.2 Updating the OPTE9 option board firmware with VACON® Loader
The VACON® Loader can be downloaded from http://drives.danfoss.com website. It has been
bundled with the VACON® Live software package.
To update the option board firmware, follow the steps below.
NOTE! With VACON® 20, the baud rate 9600 must be used. With VACON® 20 X and VACON® 20 CP,
the following baud rates are supported: 9600, 19200, 38400 or 57600.
Step 2. Press 'next' and wait for the loader to find the network drives.
Then select a drive from the list and press 'Connect to Selected'. See Figure 17.
Step 3. Select the modules to be updated, press 'next' and wait until the operation is finished. See
Figure 18 and Figure 19.
NOTE! The NCIPConfig uses broadcast messages for scanning devices. Some network switches
might block the broadcast messages. In this case, each network node must be scanned separately.
Step 3. Set the option board settings.
To change the board name, select the cell in the column 'Node' and enter the name of the node.
Notice that this changes the name seen only in VACON® PC tools. PROFINET IO Name Of Station
value must be changed via protocol settings or over PROFINET IO DCP protocol.
To change the node IP settings, select the cell in the right column and enter the value according to
the network IP settings. The program will report conflicts with a red color in table cells.
To change the IP Mode, click the cell and select the desired mode from the dropdown list (Figure 22).
To commit the changes, mark the checkbox and select Configuration->Configure- from the menu.
Before using the NCDrive, you need to configure the option board IP settings with NCIPConfig. If the
option board does not have valid IP settings you will not be able to connect with the NCDrive.
Step 1. Connect your PC to the Ethernet network with an Ethernet cable.
You can also connect the PC directly to the device using a crossover cable. This option may be
needed if your PC does not support Automatic crossover function.
Step 2. In order to connect to the drive, you need to select the active drive first. Press the "Drive
Select" button (see Figure 25) to scan the network drives.
Step 3. In the "Select the active drive" dialog (see Figure 26), select the drive you want to connect to.
Then press the "Set Active Drive" button. Now you can close the dialog.
The IP information presented in the dialog comes from the option board, other information comes
from the drive.
Step 4. Press the "ON-LINE" button. The NCDrive will connect to the drive and start loading
parameter information. This will take a few minutes. See Figure 27 and Figure 28.
Step 5. To change the option board settings, navigate to the "M7Expander boards" menu and select
the slot that the OPTE9 is connected to. You can change the IP address, network mask and default
gate address in the menu item "G 7.x". After you have changed the IP settings, you need to change
"IP Mode" to "Fixed IP" in order to activate the settings.
For more information about these settings, see Chapter 6.1.
NOTE! The NCDrive software can be used with the Ethernet board in VACON® NXS and NXP drives.
NOTE! The NCDrive software is recommended to be used in LAN (Local Area Network) only.
NOTE! This feature does not work with VACON® 100 family AC drives.
5.6.5 PC Tools for VACON® 100 family and VACON® 20 / VACON® Live
VACON® Live can be used to configure the IP settings of the OPTE9 option board. VACON® Live can
be downloaded from http://drives.danfoss.com website.
To configure the IP settings of the OPTE9 option board, follow the steps below:
NOTE! VACON® 20, VACON® 20 X and VACON® 20 Cold Plate do not support VACON® Live
connection over the OPTE9 Ethernet port.
Step 1. Connect your PC to the Ethernet network with an Ethernet cable. You can also connect the
PC directly to the drive using a crossover cable. This option may be needed if your PC does not
support Automatic crossover function.
You can also connect to the VACON® 100 family AC drive by its serial port. In any case the steps
below are the same for both connections.
NOTE! You cannot use VACON® Live via the option board if the option board does not have a valid IP
address. If you change the IP settings of the option board when connected through it, VACON® Live
connection will be lost.
Step 2. Start VACON® Live. When the program starts and it asks "Select startup mode", select
"Online". The program will scan your network for compatible drives. When found, they will be added
to the list. Select the drive that the OPTE9 option board is connected to and press "Connect to
select".
NOTE! The first column is the drive's name, but the information about IP and MAC addresses come
from the option board (if the device on the list is an option board).
NOTE! Some switches block broadcast messages. In this case, each network node must be scanned
separately.
Step 3. To change the IP settings, navigate to the "5. I/O and Hardware" menu and select the slot
that the OPTE9 is connected to. You can change the IP address, network mask and default gate
address in the menu item "5.x.3 Parameters". After you have changed the IP settings, you need to
change "IP Mode" to "Fixed IP" in order to activate the settings. For more information about these
settings, see Chapter 6.1.
6. COMMISSIONING
The VACON® OPTE9 Dual Port Ethernet option board is commissioned with the control keypad by
giving values to appropriate parameters in the option board menu (or via PC tools, see Chapter 5.6
"PC Tools").
Keypad commissioning procedures and location of parameters differ a little with different AC drive
types:
• In the VACON® NXP/NXS option board, parameters are located under the menu M5
(Expander board menu).
• In the VACON® 100 family option board, parameters are located under the menu M7 (I/O and
Hardware).
The control keypad makes it possible for the user to see which expander boards are connected to
the control board and to reach and edit the parameters associated with the expander board.
The IP mode determines how the option board IP settings are set. There are three IP modes
available: DHCP, Fixed IP and DCP. By default, the option board is in DHCP mode.
IP is divided into 4 parts (octets). In the parameters menu, you can see stored IP settings, and the
monitoring values always show the currently used IP settings.
IP mode: DHCP
If a DHCP mode is selected, the option board tries to retrieve its IP settings from the DHCP server
connected to the local network. If the option board is unable to retrieve its IP settings, it sets a link-
local address as the current IP address after about one minute (for example 169.x.x.x). Changing the
IP settings (IP address, subnet mask or gateway) does not have any effect when IP mode is "DHCP".
If PROFINET IO is used and the IP settings are set via DCP protocol, the IP mode is changed to "Fixed
IP" and IP settings from DCP are taken in to use. In this IP mode, the IP settings are stored
permanently even if DCP protocol sets values as temporary.
IP mode: Fixed IP
In this mode, the IP settings are taken from the parameters, and monitoring values will always show
the same settings when the Ethernet link is up. The IP settings can be changed from the control
panel, PC tools or via fieldbus. If PROFINET IO is used and the IP settings are set via DCP protocol,
the IP settings are stored permanently even if DCP protocol sets values as temporary.
IP mode: DCP
Since firmware V008 it is also possible to set the mode to "DCP". Use this mode with PROFINET IO
as it usually uses DCP protocol for the IP settings. You can also use it with other protocols. Note that
DCP protocol itself is available in option board only when PROFINET IO is been used.
The PROFINET IO DCP protocol can be used to set temporary IP settings. This means that after the
device is restarted, the option board does not have IP settings. The PLC then must set the IP address
again before starting the communication. When temporary IP settings are set, those values are
shown only in monitoring view. Parameters will show whatever IP settings were previously stored.
When device is restarted, option board will use 0.0.0.0 as its IP address. Permanent IP settings are
always stored and used after device restart.
IP settings are locked after they have been set by using DCP protocol and can be only modified via
DCP. After device restart, IP settings can be modified from panel, PC tools etc. until they have been
set by using DCP protocol. This enables changing IP address locally even in DCP mode when, for
example, PLC is offline.
Ethernet link speed and duplex can be set by changing this parameter. We always recommend to
use "autonegotiation"-mode. Change this value only if you have very specific needs. Note that if
Ethernet link in one end is in fixed mode (for example 100Mb Full Duplex) and the other end is using
autonegotiation, the autonegotiation end can detect speed, but is unable to detect duplex. OPTE9
will revert to Half Duplex mode if autonegotiation of duplex mode fails. Communication problems
can be expected if the ends of the link are in different modes.
Note also that "100 Mb full duplex" is required for fast paced fieldbus process control. Lower speed
or half duplex will generate communication problems when shortest cycle times for process data
are used.
Possible parameter values are listed in table below.
Mode Description
Ethernet link speed and duplex are automatically detected. Default and recom-
Autonegotiation
mend mode.
10 HD 10 Mb half duplex
10 FD 10 Mb full duplex
100 HD 100 Mb half duplex
100 FD 100 Mb full duplex
Monitoring values show the current speed and duplex value. Possible values are listed in table
below.
Mode Description
Undefined Ethernet link is not up. For example cable is not connected.
10 HD 10 Mb half duplex
10 FD 10 Mb full duplex
100 HD 100 Mb half duplex
100 FD 100 Mb full duplex
6.1.6.1 Modbus
For Modbus, this value defines a time in which a message must be received (from Client in Modbus
TCP/UDP) before a fieldbus fault is generated. If timeout is set to zero, no fault is created.
See Chapter 7.4.
For these protocols, this value is considered as an additional timeout which works on top the
timeout mechanism of the protocol. When a connection loss is noticed, a fault activation is started.
If communication timeout value is zero, the fault is activated immediately, otherwise the fault
activates after a specified time. If the connection is reopened before the specified time has elapsed,
no fault is created.
See Chapter 8.5 "PROFINET IO communications and connection timeout" for more details on how a
timeout is created in OPTE9 while using PROFINET IO protocol.
See Chapter 9.1.6 "EtherNet/IP communication and connection timeout" for more details for more
details on how a timeout is created in OPTE9 while using EtherNet/IP protocol.
The Profinet IO "Name of Station" parameter can be set via VACON® Live or NCIPConfig. Other
possibility is to set this name by writing it over Ethernet with the DCP protocol. The name is empty
if no name is set, or if the name has been set as "temporary" by network device with DCP protocol.
Maximum length for this parameter is 240 characters.
Because VACON® NX, VACON® 20, VACON® 20 X and VACON® 20 CP drives do not support
parameters with string datatype, a parameter with integer value (NOS Device ID) can be used
instead. When a non-zero value is set, the option board generates the Name Of Station value using
application id and this new parameter. This integer value can then be backed up and restored when
needed. This way the AC drive can be replaced and it will retain the same Name Of Station value
after parameters are restored.
If NOS Device ID parameter is used, the option board always generates the Name Of Station value
during drive startup. The used value can be overwritten by PLC or PC tools, but the written value is
active only until the AC drive is restarted again.
For example if Multi-purpose application is used and NOS Device ID is set to '7', the Name Of Station
will be "apfiff06-7". Note that when using "NOS Device ID" if drive application changes, generated
Name Of Station value also changes.
We recommend you to use LLDP capable devices and the topology feature in (for example) Siemens
TIA Portal. This way, the PLC always sets the Name Of Station and IP settings based on devices
location in Ethernet network. This way there is no need to set manually Name Of Station or use "NOS
Device ID" parameter.
The Name Of Station value is shown in monitoring view (except for of VACON® 20, VACON® 20 X and
VACON® 20 CP). Displayed value is limited to 12 characters in VACON® NX and to 18 characters in
VACON® 100.
For example "auxpump22tower4" is shown as "..mp22tower4" in VACON® NX.
These parameters will show what instances are being used now. The instances actually used are
taken from the IO connection open request. So, although these values are parameters they act more
like monitoring values.
This value can be used to differentiate drives for the PLC program. For example, if one drive is
running a different application (with different parameters) than other drives, this offset in the
product code will enable the PLC to use a different EDS file to read those parameters from this drive.
Remember that if you change this value, you need also to change the EDS file used or change the
product code value in your EDS file.
6.1.10 Mode
The "Mode"-parameter is available only when the OPTE9 has been installed to the VACON® 100
family AC drive. When the mode is changed, the OPTE9 fieldbus protocols will emulate old C-series
option boards or VACON® 100 family internal implementations. Restart the AC drive after you have
changed this value.
6.1.10.1 Modbus
6.1.10.2 EtherNet/IP
NX Mode
• The PLC must use OPTCQ EDS instead of OPTE9.
• The AC/DC Drive Object: Parameter "Drive" mode will always return the actual drive mode.
In "normal" mode "process drive" mode value is returned when the instance number is 25.
• The Drive identifier text will be "Vacon OPT-CQ" instead of being based on the drive where
the option board is installed (for example: "Vacon 100 INDUSTRIAL").
• The Product code will be "2" instead of being based on the drive where the option board is
installed.
• The Revision number (major, minor) will be 3.5 instead of OPTE9 revision number.
• The Connection instance will be "1" instead of "103" which is used by OPTE9 and VACON®
100 family AC drive.
• The Motor Data Object: "Rated Current" attribute will return the value in units of 10
milliamperes (1.9A => 190). In Normal mode, the value unit is 100 milliamperes (1.9A => 19).
The same conversion is expected when setting the attribute value.
• The Motor Data Object: "Rated Frequency" attribute will return value with two decimals
(50.00Hz => 5000). In normal mode, the value has no decimals (50.00Hz => 50Hz). The same
conversion is expected when setting the attribute value.
6.1.10.3 PROFINET IO
NX Mode
• The PLC must use OPTCP GSDML instead of OPTE9.
• The Device id will be "1" instead of OPTE9's "2"
• The Vendor id will be "0x9500" instead of OPTE9's "0x01BA"
• The Device type text will be "OPTCP" instead of "OPTE9"
• The Telegrams will use FBSpeedReference/FBSpeedActual types instead of NSOLL_A /
NIST_A.
• The Parameter channel used with Simatic PDM will not work in NX Mode.
Vacon 100 Mode
• The PLC must use VACON® 100 family GSDML instead of OPTE9.
• The Device id will be "1" instead of OPTE9's "2"
• The Device type text will be "VACON100" instead of "OPTE9"
This value shows the OPTE9 device MAC address. The format differs between used VACON® AC
drive. In VACON® 100 family AC drives, the format is 00:11:22:33:44:55, and in VACON® NXS and
NXP, the value is 001122334455. This value is not visible in VACON® 20 family AC drives.
Example for VACON® 100 family AC drive: 00:21:99:1a:00:24
Example for VACON® NXS/NXP: 0021991a0024
This value is used to select Modbus unit identifier / slave address. When using Modbus TCP the
value 255 must be used, and this field is ignored as the IP address is used to access the correct
device. When using Modbus UDP the values and their significance is explained in table below. Values
from 1 to 247 and 255 can be set to OPTE9.
Table 16. Modbus Unit Identifier field description when using Modbus UDP
The value 0 can be used to control several devices with a broadcast message, e.g. to command all
devices to stop at the same time. This feature will also work if all devices have the unit identifier
value 255.
This value shows the current state of the active media redundancy protocol. By default, DLR protocol
is active, unless MRP protocol is turned on, in which case DLR protocol is shut down.
The values are mapped in the following way:
• 0 = No ring protocol
• 0# = Ring protocol initializing
• 1# = Ring protocol status ok
• 2# = Ring protocol failure
• #1-#3 = MPR
• #4-#6 = DLR
The value definitions and how they map to media redundancy specification states (in MRP MRC state
machine and in DLR announce based node state machine) are defined in table below.
The SNTP settings are used to enable Simple Network Time Protocol for updating date and time to
drive from network.
SNTP Mode
This parameter is used to set SNTP client mode.
Mode Description
Disabled SNTP feature is disabled
Mode Description
Poll Option board will poll with certain interval for new time from the time server
Listen Only Option board listens time updates (broadcasts) from time server
Poll Fault Same as poll-mode, but if retrieving time updates fails, a fault is generated.
Same as Listen Only-mode, but if time updates are not received, a fault is
Listen Only Fault
generated.
Server 1 and server 2 IP address
To use the SNTP in poll mode you need to set at least one server address. In Listen Only-mode, the
IP addresses can be zero, and all time broadcasts are accepted. When server address(es) are set,
only the broadcasts from the set addresses are accepted.
SNTP port
By default SNTP port is 123, but you can use this parameter to change it. In Poll-mode, the option
board sends requests to this port in the time server, and in the Listen Only-mode it listens to the
broadcasts to this port.
Time interval
This setting is used to define how often the option board should request time updates from the time
server in Poll-mode. In the Listen Only-mode, this setting defines how often the broadcasts must be
received.
Time offset - Hours and minutes
These settings are visible only in VACON® NXS and NXP family drives. When the option board is
installed to a VACON® 100 family AC drive, the drive’s internal time settings are used.
By default, the time updates from the time server are in UTC. Use these settings to change that
value to local time by adding or reducing hours and minutes stored to these parameters.
The SNTP has a few monitoring values which show current SNTP status.
SNTP status
This value shows current SNTP status. Status is Stopped when SNTP is disabled.
SNTP server IP
This value shows the IP address of the SNTP server to which the OPTE9 is trying to connect or which
is currently sending the time updates.
Last Update Time
This value shows the number of seconds since the last received time update. It shows zero until the
first received time update.
The OPTE9 option board shall support multiple communication modes to AC drive in future release.
This will, among other features, enable transmitting and receiving 16 process data items at 1 ms
interval.
Drive Control Word will always show the internal control word (FBFixedControlWord) which is
written to the drive by the option board. If the control word written by the PLC does not use
FBFixedControlWord (e.g. STW1 or CIP CW), the control word along with profile specific state
machine is used to generate the FBFixedControlWord. If the used telegram is already using
FBFixedControlWord, it is shown directly in this monitoring value. Only exception to this is that, in
the VACON® NX AC drives, the bit 15 is set/removed to indicate "Master Connection state".
The Drive Status word will always show the FBFixedStatusWord received from the drive.
The Protocol Control Word shows the value which was sent by the PLC to the option board. It will
always show protocol specific control word (ZSW1, CIP CW) if it is in the used telegram. Otherwise
the FBGeneralControlWord is shown. However, if the telegram contains only the
FBFixedControlWord, then this is shown in both control word monitoring values.
The Protocol Status word shows the value which was sent by the option board to the PLC. It will
always show protocol specific status word (STW1, CIP SW) if it is in the used telegram. Otherwise
the FBGeneralStatusWord is shown. However, if telegram contains only FBFixedStatusWord, then
this is shown in both status word monitoring values.
See telegram specific configuration in their own chapter in this document. For example for
PROFINET ST1 see Chapter 8.3.2.1 "Standard Telegram 1 and variants".
Master´s Slave
message response
Start Start
Address Address
Function Function
Data Data
CRC CRC
End End
11608_uk
On simple interfaces like RS485, the Modbus messages are sent in plain form over the network. In
this case, the network is dedicated to Modbus. When using more versatile network systems like
TCP/IP over Ethernet, the Modbus messages are embedded in packets with the format necessary
for the physical interface. In that case Modbus and other types of connections can co-exist at the
same physical interface at the same time. Although the main Modbus message structure is peer-
to-peer, Modbus is able to function on both point-to-point and multidrop networks.
Each Modbus message has the same structure. Four basic elements are present in each message.
The sequence of these elements is the same for all messages, to make it easy to parse the content
of the Modbus message. A conversation is always started by a master in the Modbus network. A
Modbus master sends a message and depending of the contents of the message a slave takes action
and responds to it. There can be more than one master in a Modbus network. Addressing in the
message header is used to define which device should respond to a message. All other nodes on the
Modbus network ignore the message if the address field does not match their own address.
If you need to contact VACON® service in problems related to Modbus TCP/UDP, send a description
of the problem together with the Drive Info File to [email protected]. If possible, also
send a "Wireshark" log from the situation if applicable.
In addition to TCP, the OPTE9 option board supports also UDP (from OPTE9 firmware version V006).
It is recommended that UDP is when reading and writing rapidly and repetitively (cyclically) same
data as in case of process data. TCP must be used for single operations, like service data (e.g.
reading or writing parameter values).
The key difference between UDP and TCP is that when using TCP each and every Modbus frame
needs to be acknowledged by the receiver (see the figure below). This adds extra traffic to the
network and more load to the system (PLC and drives) because software needs to keep track of sent
frames to make sure that they have reached their destination.
TCP, SYN
Modbus Query
Open
TCP, ACK
Close
TCP, ACK
TCP, FIN, ACK
TCP, ACK
11716_uk
Another difference between TCP and UDP is that UDP is connectionless. TCP connections are
always opened with TCP SYN messages and closed with TCP FIN or TCP RST. With UDP, the first
packet is already a Modbus query. The OPTE9 treats IP address and port combination as a
connection. If port changes, it is considered as a new connection or as a second connection if both
stay active.
When using UDP, it is not guaranteed that the sent frame reaches is destination. PLC must keep
track of the Modbus requests by using the Modbus transaction id-field. It actually must do this also
when using TCP. If PLC does not receive response in time from drive in UDP connection, it needs to
send the query again. When using TCP, the TCP/IP stack will keep resending the request until it has
been acknowledged by the receiver (see Figure 35 ). If PLC sends new queries during this time,
some of those may not be sent to network (by TCP/IP stack) until previous sent package(s) has been
acknowledged. This can cause small packet storms when the connection is resumed between PLC
and drive (See Figure 36).
11717_uk
TCP TCP
Modbus Modbus
stack stack
Packet lost
Modbus Query (2) Retransmission
Modbus Query (1)
Retransmission
Modbus Query (1,2)
Modbus Query (3)
Retransmission
Modbus Query (1,2,3)
11718_uk
Losing one packet is not a big issue because the same request can be sent again after timeout. In
TCP, the packages always reach their destination but if network congestion causes retransmissions,
those packages will most likely contain old data or instructions when they reach their destination.
• Direct control of VACON® AC drive (e.g. Run, Stop, Direction, Speed reference, Fault reset)
• Access to VACON® parameters
• VACON® status monitoring (e.g. Output frequency, Output current, Fault code)
All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item
is addressed as item number zero. For example:
• The coil known as 'Coil 1' in a programmable controller is addressed as 'Coil 0000' in the
data address field of a Modbus message.
• Coil 127 decimal is addressed as 'Coil 007E hex' (126 decimal).
• Holding register 40001 is addressed as register 0000 in the data address field of the mes-
sage. The function code field already specifies a 'holding register' operation. Therefore the
'4XXXX' reference is implicit.
• Holding register 40108 is addressed as register 006B hex (107 decimal).
The VACON® AC drives have trip counters for operation days and energy. These counters can be
reset to zero by writing value '1' to addresses defined in Table 22. Resetting the counters is not
supported in VACON® 20, VACON® 20 X or VACON® 20 CP.
Table 22. Clearing trip counters
For compatibility with OPT-CI, these registers can be cleared also by writing '1' to these coils.
Input discrete registers contain binary data (Read). See Table 23.
Table 23. Defined Input Descrete registers
The values can be read with function code 4. These are for compatibility with the OPT-CI option
board. They return the same values as holding register counterparts.
Table 24.
The values can be read with function code 3. Modbus registers are mapped to drive IDs as follows:
Table 25. Defined holding registers
Access
Address range Purpose See R/W Max R/W size
type
0001 - 2000 VACON® Application IDs 16bit Table 26 RW 30/30
2001 - 2019 FBProcessDataIN 16bit Table 27 RW 19/19
2051 - 2086 FBProcessDataIN 32bit1) Table 27 RW 36/36
2101 - 2119 FBProcessDataOUT 16bit Table 28 RO 19/0
2151 - 2186 FBProcessDataOUT 32bit1) Table 28 RO 36/0
2200 - 10000 VACON® Application IDs 16bit Table 26 RW 30/30
10501 - 10530 IDMap 16bit Figure 37 RW 30/30
10601 - 10630 IDMap Read/Write 16bit Table 29 RW 30/302)
10701 - 10760 IDMap Read/Write 32bit1) Table 29 RW 30/30
20001 - 40000 VACON® Application IDs 32bit1) Table 26 RW 30/30
40001 - 40005 Operation day counter 16bit Table 32 RO 5/0
40011 - 40012 Operation day counter 32bit1) Table 31 RO 2/0
R, Write 1 to
Resettable operation day
40101 - 40105 16bit Table 34 first index to 5/0
counter
reset
Resettable operation day
40111 - 40112 32bit Table 33 RO 2/0
counter
40201 - 40203 Energy counter 16bit Table 36 RO 3/0
40211 - 40212 Energy counter 32bit Table 35 RO 2/0
R, Write 1 to
Resettable energy coun-
40301 - 40303 16bit Table 38 first index to 3/0
ter
reset
Resettable energy coun-
40311 - 40312 32bit Table 37 RO 2/0
ter
40400 Reset fault history 16bit RW 1/1
40401 - 40430 Fault history 16bit Table 39 RO 30/0
40501 Communication timeout 16bit Table 42 RW 1/1
Fault history with 16 bit
40511-40568 16bit Table 40 RO 30/0
fault codes
Fault history with time
40601-40801 16 bit Table 41 RO 30/0
stamps
1)
These items are supported only in VACON® 100 family AC drives. Not supported in current version.
See chapter 5.
2)
In VACON® 20, VACON® 20 X / CP, the maximum R/W size for IDmap operations is 12/30.
Application IDs are parameters that depend on the drive's application. These parameters can be
read and written by pointing the corresponding memory range directly or by using the so-called ID
map (more information below). The easiest way to read a single parameter value or parameters with
consecutive ID numbers is to use a straight address. It is possible to read 30 consecutive ID
addresses. Notice that the operation will fail if even one of the consecutive IDs do not exist.
Parameters which have 32 bit value can be read from their own range. For example, if you want to
read the value for ID 864 (FB Status Word), the address must be set to 21726. This address value
comes from values: 20000 + ((ID -1) * 2). The ID value is reduced with one because of zero-based
addressing and the result is multiplied with 2 because one 32 bit value will take two (16 bit)
addresses.
Table 26. Parameter IDs
The process data fields are used to control the AC drive (e.g. Run, Stop, Reference, Fault Reset) and
to quickly read actual values (e.g. Output frequency, Output current, Fault code). The values in these
indexes can be read and written. The fields are structured as follows (continued on the next page):
Process Data Master -> Slave (max 22 bytes)
Table 27. Fieldbus Process Data IN
Address
Name Range/Type
16-bit 32-bit*
2051 = High data
2001 FB Control Word Binary coded
2052 = Low data
2002 - FB General Control Word Binary coded
2053 = High data
2003 FB Speed Reference 0…10000 (100%)
2054 = Low data
Address
Name Range/Type
16-bit 32-bit*
2055 = High data
2004 FB Process Data In 1
2056 = Low data
2057 = High data
2005 FB Process Data In 2
2058 = Low data
2059 = High data
2006 FB Process Data In 3
2060 = Low data
2061 = High data
2007 FB Process Data In 4
2062 = Low data
2063 = High data
2008 FB Process Data In 5
2064 = Low data
2065 = High data
2009 FB Process Data In 6
2066 = Low data
2067 = High data
2010 FB Process Data In 7
2068 = Low data
2069 = High data
2011 FB Process Data In 8
2070 = Low data See Chapter 11 "APPENDIX 1 -
2071 = High data PROCESS DATA"
2012* FB Process Data In 9
2072 = Low data
2073 = High data
2013* FB Process Data In 10
2074 = Low data
2075 = High data
2014* FB Process Data In 11
2076 = Low data
2077 = High data
2015* FB Process Data In 12
2078 = Low data
2079 = High data
2016* FB Process Data In 13
2080 = Low data
2081 = High data
2017* FB Process Data In 14
2082 = Low data
2083 = High data
2018* FB Process Data In 15
2084 = Low data
2085 = High data
2019* FB Process Data In 16
2086 = Low data
* Available in future release
Address
Name Range/Type
16-bit 32-bit*
2151 = High data 2152
2101 FB Status Word Binary coded
= Low data
In case of 16-bit,
2102 - FB General Status Word Binary coded
(High data)
2153 = High data
2103 FB Actual Speed 0…10000 (100.00%)
2154 = Low data
2155 = High data
2104 FB Process Data Out 1
2156 = Low data
2157 = High data
2105 FB Process Data Out 2
2158 = Low data
159 = High data
2106 FB Process Data Out 3
2160 = Low data
2161 = High data
2107 FB Process Data Out 4
2162 = Low data
2163 = High data
2108 FB Process Data Out 5
2164 = Low data
2165 = High data
2109 FB Process Data Out 6
2166 = Low data
2167 = High data
2110 FB Process Data Out 7
2168 = Low data
2169 = High data
2111 FB Process Data Out 8
2170 = Low data See Chapter 11 "APPENDIX 1 -
2171 = High data PROCESS DATA"
2112* FB Process Data Out 9
2172 = Low data
2173 = High data
2113* FB Process Data Out 10
2174 = Low data
2175 = High data
2114* FB Process Data Out 11
2176 = Low data
2177 = High data
2115* FB Process Data Out 12
2178 = Low data
2179 = High data
2116* FB Process Data Out 13
2180 = Low data
2181 = High data
2117* FB Process Data Out 14
2182 = Low data
2183 = High data
2118* FB Process Data Out 15
2184 = Low data
2185 = High data
2119* FB Process Data Out 16
2186 = Low data
* Available in future release
7.3.2.5.4. ID MAP
Using the ID map, you can read consecutive memory blocks that contain parameters whose IDs are
not in a consecutive order. The address range 10501 - 10530 is called 'IDMap', and it includes an
address map in which you can write your parameter IDs in any order. The address range 10601 -
10630 is called 'IDMap Read/Write', and it includes values for parameters written in the IDMap. As
soon as one ID number has been written in the map cell 10501, the corresponding parameter value
can be read and written in the address 10601, and so on. The address range 10701 - 10760 contains
the ID Map for 32bit values. Maximum of 30 IDs and ID values can be written and read with single
request except in VACON® 20 and 20 X/CP it is possible to access only 12 ID value items at a time.
NOTE! 32 bit data not supported in the current version. See chapter 5.
Parameters
ID Value
699 123 ID Map
700 321 Address Data: ID Address Data: ID
701 456 10501 700 10601 321
702 654 10502 702 10602 654
703 1789 10503 707 10603 258
704 987 10504 704 10604 987
705 2741
706 1147
707 258
708 3852 11609_uk
Once the ID Map address range has been initialized with the parameter IDs, the parameter values
can be read and written in the IDMap Read/Write address range address (IDMap address + 100).
Table 29. Parameter Values in 16-bit IDMap Read/Write registers
Address Data
10601 Data included in parameter ID700
10602 Data included in parameter ID702
10603 Data included in parameter ID707
10604 Data included in parameter ID704
If the ID Map table has not been initialized, all the fields show index as '0'. If it has been initialized,
the parameter IDs included in it are stored in the flash memory of the OPTE9 option board.
Table 30. Example of parameter values in 32-bit IDMap Read/Write registers
Address Data
10701 Data High, parameter ID700
10702 Data Low, parameter ID700
10703 Data High, parameter ID702
10704 Data Low, parameter ID702
Control unit operating time counter (total value). This counter cannot be reset. The values are read
only.
NOTE! The feature Operation day counter does not work with VACON® 20, VACON® 20 X or VACON®
20 CP AC drives.
Operation day counter as seconds
This counter in registers 40011d to 40012d holds the value of operation days as seconds in a 32-bit
unsigned integer.
Table 31. Operation days counter as seconds
Address Description
40011 High data
Holds the counter value as seconds.
40012 Low data
This register holds the value for resettable control unit operating time counter (trip value). The
values are read only.
For resetting this counter see Chapter 7.3.2.2 "Clearing resettable counters".
NOTE! The feature Resettable operation day counter does not work with VACON® 20, VACON® 20 X
or VACON® 20 CP AC drives.
Resettable operation day counter as seconds
This counter in registers 40111d to 40112d holds the value of resettable operation days as seconds
in a 32-bit unsigned integer.
Table 33. Resettable operation days counter as seconds
Address Description
40111 High data
Holds the counter value as seconds.
40112 Low data
This counter holds the value of total amount of energy taken from a supply network. This counter
cannot be reset. The values are read only.
Energy counter as kWh
This counter is in registers 40211d to 40212d and is a 32-bit floating point (IEEE 754) value containing
the number of kilowatt-hours (kWh) that is in the drive's energy counter. This value is read-only.
Table 35. Energy counter as kWh
Address Description
40211 High data Holds the value of energy counter in kWh. Datatype is 32 bit
40212 Low data float IEEE 754
Energy counter
These registers hold three values for the energy counter, amount of energy used, format of the
energy value and unit of the energy value.
For compatibility with VACON® 100 family internal Modbus TCP/UDP and the OPT-CI option board,
this counter is found from two different register areas: holding registers 40201d to 40203d and input
registers 201d to 203d.
Example: If energy = 1200, format = 52, unit = 1, then actual energy is 12.00 kWh.
Table 36. Energy counter
Holding Input
register register Purpose Description
address address
40201 201 Energy Amount of energy taken from a supply network.
The last number of the Format field indicates the deci-
mal point place in the Energy field.
Example:
40202 202 Format
40 = 4 number of digits, 0 fractional digits
41 = 4 number of digits, 1 fractional digit
42 = 4 number of digits, 2 fractional digits
Unit
1 = kWh
40203 203 2 = MWh Unit of the value.
3 = GWh
4 = TWh
This counter holds the value of total amount of energy taken from a supply network since the
counter was last reset. For resetting this counter see Chapter 7.3.2.2 "Clearing resettable
counters". The values are read only.
Resettable energy counter as kWh
This counter is in registers 40311d to 40312d and is a 32-bit floating point (IEEE 754) value
containing the number of kilowatt-hours (kWh) that is in the drive's resettable energy counter.
Address Description
40311 High data Holds the value of energy counter in kWh since last counter
40312 Low data reset. Datatype is 32 bit float IEEE 754
Holding Input
register register Purpose Description
address address
40301 301 Energy Amount of energy taken from a supply network.
The last number of the Format field indicates the deci-
mal point place in the Energy field.
Example:
40302 302 Format
40 = 4 number of digits, 0 fractional digits
41 = 4 number of digits, 1 fractional digit
42 = 4 number of digits, 2 fractional digits
Unit
1 = kWh
40303 303 2 = MWh Unit of the value.
3 = GWh
4 = TWh
The fault history can be viewed by reading from address 40401 onward. The faults are listed in
chronological order so that the latest fault is mentioned first and the oldest last. The fault history
can contain 29 faults at the same time. (In VACON® 20, VACON® 20 X and VACON® 20 CP it is
possible to read nine faults). For compatibility with VACON® 100 family internal Modbus TCP/UDP
and the OPT-CI option board, this counter is also found from input register area: 401d to 403d.
NOTE! Reading the fault history items is slow. Reading all 30 items at once might take up to three
seconds.
The fault history contents are represented as follows:
Holding register
Purpose Description
address
40511 Fault code 1 16-bit fault code in index 1.
40512 Sub code 1 16-bit sub code for the fault in index 1.
40513 Fault code 2 16-bit fault code in index 2.
40514 Sub code 2 16-bit sub code for the fault in index 2.
... ...
40567 Fault code 29
40568 Sub code 29
NOTE! You can read only 25 items with single request. Reading the fault history items is slow.
Reading 25 items at once might take up to three seconds.
Holding
register Purpose Description
address
40601 Fault Code 1 16 bit fault code in index 1
40602 Sub code 1 16 bit fault sub code in index 1
40603 Time stamp HI 1 32 bit timestamp in seconds high byte in index 1
40604 Time stamp LO 1 32 bit timestamp in seconds low byte in index 1
40605 Time stamp ms 1 Timestamp milliseconds in index 1
40606 Fault Code 2 16 bit fault code in index 2
... ... ...
40801 Time stamp ms 40 Timestamp millisecons in index 40
It is possible to open up to three connections to the OPTE9 option board. One of the connections
could be used for process data and other just for reading monitoring data. In most cases it is
desirable that if "monitor" connection gets disconnected, no fault is generated but when the
connection is handling the process data, a fault should be generated in the time specified.
This register address enables the user to give custom communication timeout for each connection.
If a custom timeout value is used, it must be given every time a connection is opened. Timeout can
be set only to the connection which is been used to access this register. By default the connection
uses the communication timeout value given via panel parameters.
If the cable is disconnected, a fieldbus fault is activated after the timeout period. When
communication timeout is zero, no fault is activated.
Table 42. Communication timeout register
Holding register
Purpose Description
address
Communication
40501 Connection timeout value for this connection in seconds.
timeout
Communicating
Yes Check
No
Closed
Connection closed or broken?
Broken
Has second connection with
communication timeout Yes
other than zero?
No
FAULT! No fault
7092_uk
Following these instructions, you can easily and fast set up your Modbus for use:
In the AC drive application: Choose Fieldbus as the active control place (see AC drives User's
Manual).
Message frame:
01 10 07 D0 00 03 06 00 01 00 00 13 88 C8 CB
The reply to Preset Multiple Registers message is the echo of 6 first bytes.
Answer Slave - Master:
Reply frame:
01 10 07 D0 00 03 80 85
Message frame:
01 04 08 36 00 02 93 A5
The reply to the Read Input Registers message contains the values of the read registers.
Answer Slave - Master:
Reply frame:
01 04 04 13 88 09 C4 78 E9
Message frame:
01 04 17 70 00 05 34 55
Exception response
Answer Slave - Master:
Reply frame:
01 84 04 42 C3
8. PROFINET IO
PROFINET is the Ethernet-based automation standard of PROFIBUS International for the
implementation of an integrated and consistent automation solution based on Industrial Ethernet.
PROFINET supports the integration of simple distributed field devices and time-critical applications
in (switched) Ethernet communication, as well as the integration of component-based distributed
automation systems for vertical and horizontal integration of networks.
OPTE9 implements PROFINET IO version 2.3 with conformance class B and the highest netload
class (class III), making it suitable for use in larger automation systems. OPTE9 also implements
PROFINET IO alarms system where VACON® AC drive faults are seen in bus as PROFINET IO
alarms.
S3: Switched On
ZSW1 bit 0,1 = True; 2,6 = False Ramp stop
7
6 10
14 9 8
S4: Operation
ZSW1 bit 0,1,2 = True; 6=False
NOTE! When using VACON® NX series AC drives and OPTE9 in "PROFIdrive" mode, the stop
command always follows the configured stop mode and not the stop command given from fieldbus.
NOTE! Quick stop only occurs if the application supports it. If the application does not support Quick
stop, a normal ramp stop is executed.
Action(s)
Value VACON® 100
# Bits of control word
(hex) family & VACON® 20 VACON® NXP
VACON® 20X/CP
0 - - Self-initiation is performed
OFF AND No Coast Stop AND No
None, requires that Drive is READY (ZSW1 sta-
1 Quick Stop 0x47E
tus word bit 13)
STW1 bit 0 = False; 1, 2 = True
Coast Stop OR Quick Stop
2 None
STW1 bit 1 = False OR bit 2 = False
ON
3 0x477 None
STW1 bit 0 = True
4 Coast Stop OR Quick Stop None
Action(s)
Value VACON® 100
# Bits of control word
(hex) family & VACON® 20 VACON® NXP
®
VACON 20X/CP
5 STW1 bit 1 = False OR bit 2 = False None
Enable operation Drive function is enabled, requires that Drive
6 0x47F
STW1 bit 3 = True is in fieldbus control (ZSW1 status word bit 9
Coast stop
7 0x47D Stop by coast Stop by coast Stop function
STW1 bit 1 = False
8, Quick stop
0x47B Quick stop Stop by ramp Stop function
12 STW1 bit 2 = False
Ramp stop
9 0x47E Stop by ramp Stop by ramp Stop function
STW1 bit 0 = False
Disable operation Drive function is disabled, stop by stop func-
10 0x477
STW1 bit 3 = False tion
Coast stop
11 0x47D Stop by coast Stop by coast Stop function
STW1 bit 1 = False
Standstill detected OR Disable
13, Drive function is disabled, stop by stop func-
operation 0x477
15 tion
STW1 bit 3 = False
14 ON (Re-enable operation) 0x47F Drive function is re-enabled
When choosing a telegram for PROFINET IO communication, you need to take a few things into
account, for example, if you need PROFIDrive control/status word (STW1/ZSW1) or if you could use
VACON® control/status word.
We recommend you to use STW1 when you have devices from multiple manufactures which all can
be controlled with PROFIDrive control word. This then makes writing the PLC application easier,
especially if you have PROFIDrive block ready for your PLC.
State machine for VACON® control/status word is simpler than in the PROFIDrive and therefore
controlling the drive is also easier in the PLC application. If you have only VACON® devices
controlled by your PLC over PROFINET IO, then it is better to use VACON® control/status word.
Telegram selection also affects the motor speed control. With VACON® control word, the motor
direction can be controlled with a single bit. PROFIDrive motor direction is controlled with negative/
positive values. Telegrams with PROFIDrive control/status word generally have also PROFIDrive
speed reference/actual (NIST_A/NSOLL_A). Other telegrams have VACON® speed reference/actual
(FBSpeedReference/FBSpeedActual). The main difference between these types is the integer value
which means maximum allowed motor speed (100%). In VACON® FBSpeedReference, the value is
between 0d - 10000d (100.00%) and in PROFIDrive NIST_A the value is between -16384d - 16384d.
Note also that when you use NSOLL_A, our minimum and maximum frequency parameters affect
the speed reference differently than when you use the FBSpeedReference directly. When you use
NSOLL_A, the PROFINET will give zero reference to the application until NSOLL_A exceeds the
minimum reference, but if you use the FBSpeedReference, the given value is always scaled between
the minimum and maximum frequency. For example, if the Minimum Frequency is 30 Hz and the
Maximum Frequency is 50Hz, the NSOLL_A value between 0 and 9830 will run 30Hz. If the
FBSpeedReference is used, then for example value 1000 (10%) will run 32Hz.
Telegrams contain different amount of process data items. Those vary from none to 16 items.
Process data can be 16 or 32 bits in size. Process data in VACON® NXP drives is only 16 bit, so
telegrams which use 32 bit process data have the upper 16 bits always as zero.
If you want to use more than 8 process data items, then the fieldbus option board communication
mode must be 'Fast mode with safety "black channel"', 'Fast Mode' or 'Normal Extended' mode. See
Chapter 17 "Appendix 7 - Fieldbus option board communication" for more information on the
communication mode.
Standard Telegram 1 types are used, when a standard VACON® application is used and PROFIdrive
functionality is required. These telegrams (Table 44) use PROFIdrive-defined control word, status
word, speed setpoint value and speed actual value. When using these telegrams, the process data
fields are communicated as 16-bit values.
STW1 will force edge sensitive run control.
NOTE! When board is connected to VACON® 100 family AC drive and its mode parameter is set to
“NX Mode”, the option board will use FBSpeedReference/FBSpeedActual instead of NSOLL_A/
NIST_A as backward compatibility for OPTCP option board.
* 12 and 16 process data items are available in VACON® NXP AC Drive. See chapter 17.
Name Value
Drive CW FBFixedControlWord
Drive SW FBFixedStatusWord
Protocol CW STW1
Protocol SW ZSW1
These telegrams (Table 47) use VACON®-defined control word, status word, speed setpoint value
and speed actual value to directly access the AC drive application. When using these telegrams, the
process data fields are communicated as 16-bit values.
* 12 and 16 process data items are available in VACON® NXP AC Drive. See chapter 17.
Name Value
Drive CW FBFixedControlWord
Drive SW FBFixedStatusWord
Protocol CW FBFixedControlWord
Protocol SW FBFixedStatusWord
These telegrams (Table 50) use VACON®-defined control word, status word, speed setpoint value
and speed actual value to directly access the AC drive application. The difference to vendor telegram
1 types are the added general control and status words.
NOTE! This telegram type is not supported when using VACON® 100 family AC drives. 32-bit process
data support for VACON® 100 family AC drives is added in future release.
* 12 and 16 process data items are available in VACON® NXP AC Drive. See chapter 17.
When using these telegrams, the process data fields are communicated as 32-bit values, but when
using VACON® NX or VACON® 20 family AC drives, the data is actually 16-bits and transferred in the
lower bytes.
Table 51. Process data item definition when using Vendor telegram 2
Name Value
Drive CW FBFixedControlWord
Drive SW FBFixedStatusWord
Protocol CW FBGeneralControlWord
Protocol SW FBGeneralStatusWord
These telegrams (Table 54) use PROFIdrive-defined control word, status word, speed setpoint value
and speed actual value with VACON® general control and status words for added functionality.
NOTE! This telegram type is not supported when using VACON® 100 family AC drives. 32-bit process
data support for VACON® 100 family AC drives is added in future release.
NOTE! When board is connected to VACON® 100 family AC drive and its mode parameter is set to
“NX Mode”, the option board will use FBSpeedReference/FBSpeedActual instead of NSOLL_A/
NIST_A as backward compatibility for OPTCP option board.
* 12 and 16 process data items are available in VACON® NXP AC Drive. See chapter 17.
When using these telegrams, the process data fields are communicated as 32-bit values, but when
using VACON® NX or VACON® 20 family AC drives, the data is actually 16-bits and transferred in the
lower bytes.
Table 55. Process data item definition when using Vendor telegram 3
Name Value
Drive CW FBFixedControlWord
Drive SW FBFixedStatusWord
Protocol CW STW1
Protocol SW ZSW1
Use these telegram types (Table 58) as a replacement for the OPT-CP option board, when using
"Bypass mode".
You can also use these telegram types when the PROFIdrive functionality is required and a VACON®
application with PROFIdrive state machine is activated (e.g. VACON® NX Advanced Application).
Name Value
Drive CW FBFixedControlWord
Drive SW FBFixedStatusWord
Protocol CW FBFixedControlWord
Protocol SW FBGeneralStatusWord
The following table lists the assignments of bits in the control word 1.
Table 61. Overview of the assignments of bits of the control word 1
Significance
Bit
Bit value is 1 Bit value is 0
0 ON OFF
1 No Coast Stop (no OFF2 ) Coast Stop (OFF2)
2 No Quick Stop (no OFF3) Quick Stop (OFF3)
3 Enable Operation Disable Operation
4 Enable Ramp Generator Reset Ramp Generator
5 Unfreeze Ramp Generator Freeze Ramp Generator
6 Enable Setpoint Disable Set Point
7 Fault Acknowledge (0 -> 1)
8 Not used
9 Not used
10* Control by PLC No control by PLC
11 Device-specific Device-specific
12-15 Device-specific Device-specific
*Bits in a control word do not have any effect unless bit 10 is enabled.
Bit 0: Switching ON / OFF
This bit is used in combination with other bits to enable operation of the drive. When this bit is set
to 0 during operation, the drive performs a ramp stop.
Bit 1: Coast stop command
This bit is used to request a coast stop to be executed. When it is set to 0 during operation, the drive
performs a coast stop.
Bit 2: Quick stop command
This bit is used to request a quick stop to be executed. When it is set to 0 during operation, the drive
quickly ramps down to zero speed and stops.
Significance
Bit
Bit value is 1 Bit value is 0
0 Ready to Switch On Not Ready To Switch On
1 Ready To Operate Not Ready To Operate
Operation Enabled (drive follows set-
2 Operation Disabled
point)
3 Fault Present No Fault
4 Coast Stop Not Activated (No OFF2) Coast Stop Activated (OFF2)
5 Quick Stop Not Activated (No OFF3) Quick Stop Activated (OFF3)
6 Switching On Inhibited Switching On Not Inhibited
7 Warning Present No Warning
8 Speed Error Within Tolerance Range Speed Error Out Of Tolerance Range
9 Control by PLC Requested No Control by PLC Requested
Significance
Bit
Bit value is 1 Bit value is 0
10 f Or n Reached Or Exceeded f Or n Not Reached
11 Device-specific Device-specific
12 Drive running Drive stopped
13 Drive is ready Drive is not ready
14-15 Device-specific Device-specific
Normalised 16-bit speed setpoint (containing a sign bit and a 15-bit integer).
Table 63.
Normalised 16-bit speed actual value (containing a sign bit and a 15-bit integer).
Table 64.
NOTE! When the board is connected to VACON® 100 family AC drive and its mode parameter is set
to "NX Mode", the option board will use FBSpeedActual instead of NIST_A as backward compatibility
for OPTCP option board. This means that value range is 0d-10000d. See chapter 8.3.3.10 for details.
For details about vendor control word, see Chapter 12 "APPENDIX 2 - CONTROL AND STATUS
WORD"
8.3.3.6 VACON®FBFixedStatusWord
For details about vendor status word, see Chapter 12 "APPENDIX 2 - CONTROL AND STATUS
WORD".
The FBSpeedReference value is unsigned in the range 0...10000d (0...2710h). The value 0
corresponds to MinimumFrequency and the value 10000d corresponds to MaximumFrequency.
Requested direction is indicated using bit 1 in the FBFixedControlWord. The scale of the value is
0.01%.
The FBActualSpeed value is unsigned in the range 0...10000d (0...2710h). The value 0 corresponds
to MinimumFrequency and the value 10000d corresponds to MaximumFrequency. The direction is
indicated using bit 2 in the FBFixedStatusWord. The scale of the value is 0.01%.
The Process Data variables are vendor-specific variables that can be communicated to and from the
AC drive. There can be up to eight Process Data variables communicated in a single telegram.
Values sent from the option board to the master are called ProcessDataOut variables, while the
values sent from the master to the option board are called ProcessDataIn variables. The contents
of the ProcessDataOut variables can be parameterised in the AC drive using a feature known as
Fieldbus Process Data mapping. See the AC drive's Application Manual for further details.
10109 VACON® 16-bit Process Data Array[n] An array of 16 elements. From PDI1 (index 0) to
In Unsigned16 PDI16 (index 15).
10110 VACON® 16-bit Process Data Array[n] An array of 16 elements. From PDO1 (index 0)
Out Unsigned16 to PDO16 (index 15).
The parameter describes how many RPM is
Speed physical reference
10111 Unsigned16 meant by 100% in the PROFIdrive 4.1 speed
parameter
setpoint and actual value fields.
10112 VACON® Fixed Control Word Unsigned16 Fixed control word.
10122 VACON® 32-bit Process Data Array[n] An array of 16 elements. From PDI1 (index 0) to
In Unsigned32 PDI16 (index 15).
10123 VACON® 32-bit Process Data Array[n] An array of 16 elements. From PDO1 (index 0)
Out Unsigned32 to PDO16 (index 15).
Drive operation time in seconds as 32 bit
10124 Drive operation time counter Unsigned32
unsigned integer.
Drive operation time trip counter in seconds as
Drive operation time trip coun-
10125 Unsigned32 32 bit unsigned integer. Writing zero will reset
ter
trip counter.
Drive energy counter in KWh as 32 bit float
10126 Drive energy counter Float32
(IEEE 754).
Drive energy trip counter in KWh as 32 bit float
10127 Drive energy trip counter Float32
(IEEE 754). Writing zero will reset trip counter.
List of fault history items containing: Fault
code, subcode, 32bit timestamp high word,
32bit time stamp low word and timestamp mil-
Array[n] liseconds. Maximum of faults that can be read:
10128 Fault history with time stamps
Unsigned16 40 in VACON® 100 family, 30 in VACON® NX
family and 9 in VACON® 20 family. Note that
reading the fault history items is slow. Reading
all items can take up to three seconds.
For easy access to drive parameters and monitoring values, the OPTE9 maps the PROFINET user
specific record indexes 0x0000 - 0x7FFF directly into the application IDs of the drive based on the
IEC61131 standard. Both read and write access is supported.
NOTE! The response data is in raw format. See application manual for available IDs, amount of
decimals and the unit used for the parameters.
IDs can be read/written as VACON® NX scaled values in all AC drives, or, in VACON® 100 family AC
drives, also as actual raw value.
Write command
AC drive Actual value
Slot Subslot Index Length Value (Hex)
102 2 11 94 45.00 Hz
Any 1 1
600 2 00 00 0 = OL Frequency
VACON® 100 102 4 00 06 DD D0 45.0000 Hz
1 2
family 600 4 00 00 00 00 0 = OL Frequency
Error because
response Read Parameter response Parameter
not yet available from PAP processing in the
Parameter Manager
Error bacause
response Read Parameter response
not yet available from PAP
Both indexes can be used to access PROFIdrive parameters. There is no difference in operation
between them with current implementation.
Table 72. Parameter access services
Sub-
Field name Data type Description
index
A bitmask with information about the
1 Identifier (ID) Unsigned16
parameter characteristics.
Number of array ele- For array parameters, the number of
2 Unsigned16
ments elements in the array.
If the information represented by the
FloatingPoint (IEEE parameter can be converted into a stan-
3 Standardisation factor
754) dardised form, this field contains a fac-
tor for this conversion.
Array of two Contains two index numbers for
4 Variable attribute
Unsigned8 describing the parameter information.
Array of four
5 Reserved Reserved, always 0.
Unsigned8
ASCII string, 16 char-
6 Name Symbolic name of the parameter.
acters
Array of four
7 Low limit Limit for valid values of the parameter.
Unsigned8
Array of four
8 High limit Limit for valid values of the parameter.
Unsigned8
Array of two
9 Reserved Reserved, always 0.
Unsigned8
10 ID extension Unsigned16 Not used, always 0.
Parameter number, the value of which
Normalisation refer- is used as normalisation reference for
11 Unsigned16
ence parameter the parameter whose description this
is.
Contains information about normalisa-
12 Normalisation field Unsigned16
tion of this parameter.
Parameter
Request header Parameter value(s)
address(es)
Octet
Field name Description Allowed values
number
Unique number for each
request/response pair. This
Request Refer- value is changed by the A bitmask with information about the
1
ence master for each new parameter characteristics.
request. It is mirrored by the
slave in the response.
Use 0x01 for Read requests.
2 Request ID Defines the type of request. Use 0x02 for Change requests.
Other values are not allowed.
Use 1 for OPTE9 PROFINET IO.
3 Axis Number Not used, should be set to 1.
Other values should not be used.
Requested num- Values 1 to 39 are allowed.
The number of parameters
4 ber of The value 0 is not allowed.
affected by the request.
parameters Values 40 to 255 are not allowed.
Octet
Field name Description Allowed values
number
Use 0x10 for reading/writing the value
of a parameter.
Describes which part of a Use 0x20 for reading the description of a
1 Attribute parameter should be parameter.
accessed. Use 0x30 for reading the text of a
parameter (not supported).
Other values should not be used.
Values 0 and 1 are allowed for non-array
Specifies the number of ele- parameters.
Number of ele-
2 ments that are addressed in Values 1 to 234 are allowed for array
ments
an array. parameters.
Other values should not be used.
Parameter The number of the parame- Allowed values are those of supported
3...4
number ter to be addressed. parameters, see chapter 8.4.6.2.
Defines the first array ele-
Values 0 to 65535 are allowed.
5...6 Subindex ment of the parameter to be
Other values are not allowed.
accessed.
The "Parameter number" and "Subindex" fields are two-octet fields, while the "Attribute" and "No.
of elements" fields are one-octet fields.
The parameter value field is included only in Change requests (not in Read requests). The parameter
value field consists of a two-octet parameter value header followed by a list of values. Depending
on the format of the parameter, the octet size of a single value is one, two or four octets. The total
size of the parameter value field thus depends on the format and number of values in the message.
Table 78. Parameter value
Octet
Field name Description Allowed values
number
Use 0x41 for Byte.
Use 0x42 for Word.
Describes the data type of
1 Format Use 0x43 for Double Word.
the parameter.
Value 0x44 is used for Error.
Other values should not be used.
Defines the number of val-
Number of val- Values 0 to 234 are possible. Subject to
2 ues in the parameter value
ues limitations as described below.
field.
Values 0 to 65535 are allowed.
3... Value The value of the parameter.
Other values are not allowed.
The number of values which can be transmitted in one frame has been limited to 39.
If an error occurred in the Parameter Access, the response provided by the slave is an error
response. An error response contains 4 octets as described below.
Table 79. Error response
Octet
Field name Description Allowed values
number
The slave returns 0xDE to indicate an
error read response.
Function Num- The slave returns 0xDF to indicate an
1 Operation number.
ber error write response.
Other values are not used in the Param-
eter Access.
Defines how the error infor- Always 128 in PROFIdrive.
2 Error Decode mation in the following two Other values are not used in the Param-
fields should be decoded. eter Access.
Octet
Field name Description Allowed values
number
High 4 bits indicate error
See Chapter 8.4.6.3 "PROFIdrive
3 Error Code 1 class, 4 lower bits indicate
Parameter Access errors"
error code.
4 Error Code 2 Application-specific. Always 0 in PROFIdrive.
The table below lists PROFIdrive profile 4.1 error classes and codes.
Table 80. PROFIdrive 4.1 error classes and codes
In addition to the error indications in the error response field, details about the error are provided
in the parameter value field. The third octet in the parameter value is set to 0x00 and the fourth octet
is assigned the error number, as described in Table 81.
Octet
Field name Description Allowed values
number
Unique number for each
1 Request Reference Mirrored by the slave.
request/response pair.
Uses 0x01 for successful request
parameter operation.
Uses 0x02 for successful change
Defines the type of parameter operation.
response. An error in the Uses 0x80 to indicate that an invalid
2 Response ID execution of a request is request ID was received.
indicated by setting bit 7 in Uses 0x81 for unsuccessful request
this field. parameter operation.
Uses 0x82 for unsuccessful change
parameter operation.
Other values are not used.
3 Axis Number Not used, should be set to 1. Mirrored by the slave.
Requested number The number of parameters Number of parameters in the
4
of parameters affected by the request. response. Mirrored from the request.
Parameter values are included in the response only if the request was of "Request parameter" type.
For details on the contents of this field, see Parameter value on Chapter 8.4.5.4 "Parameter value"
11753_uk
Figure 43.Screen capture from “PROFINET Master Simulator” requesting value for ID103.
Field Contents
Request reference 0x01
Request ID 0x01 = Request parameter
Axis Number 0x01
No. of Parameters 0x01
Attribute 0x10 = Value
No. of elements 0x01
Parameter Number 0x03C4 (964d)
Subindex 0x0000 (0d)
The following table contains messages sent during requesting value for PNU964.
Table 84. Messages sent and received during requesting value for PNU964
The parameter value reveals that the format of the value is "Word" (0x42), there is one value in the
response (0x01) and the actual value is 0x01BA.
Field Contents
Request reference 0x02
Request ID 0x01 = Request parameter
Axis Number 0x01
No. of Parameters 0x01
Attribute 0x10 = Value
No. of elements 0x06
Parameter Number 0x03C4 (964d)
Subindex 0x0000 (0d)
The following table contains messages sent during requesting all values for PNU964.
Table 86. Messages sent and received during requesting all values for PNU964
The returned value consists of six words (0x42 means Word, 0x06 is the number of values returned),
and the values are 0x01BA, 0x0002, 0x0064, 0x07DE, 0x0065, and 0x0001. Thus the following
information can be determined about the device:
• Manufacturer code is 0x01BA
• Drive Unit type is 0x0002
• Software version is 1.0 (0x0064 = 0100d)
• Firmware date (year) is 2014 (0x07DE)
• Firmware date (day/month) is 1/1 (0x0065 = 101d)
• The device contains one axis
Field Contents
Request reference 0x03
Request ID 0x01 = Request parameter
Axis Number 0x01
No. of Parameters 0x01
Attribute 0x10 = Value
No. of elements 0x01
Parameter Number 0x2711 (10001d)
Subindex 0x0067 (103d)
Following table contains messages sent during requesting value for ID 103.
Table 88. Messages sent and received during requesting value for ID 103
The parameter value reveals that the format of the value is "Word" (0x42), there is one value in the
response (0x01) and the actual value is 0x000A. Because this value was read from the AC drive
application, the Drive Application Manual contains details on how to interpret the value. In this
example, the Acceleration time would be one second.
Field Contents
Request reference 0x04
Request ID 0x02 = Write parameter
Axis Number 0x01
No. of Parameters 0x01
Attribute 0x10 = Value
No. of elements 0x01
Parameter Number 0x2711 (10001d)
Subindex 0x0067 (103d)
Parameter datatype 0x42 = WORD
Number of parameters 0x01
Value: HI byte 0x00
Value: LOW byte 0x28
Field Contents
Request reference 0x05
Request ID 0x02 = Write parameter
Axis Number 0x01
No. of Parameters 0x01
Attribute 0x10 = Value
No. of elements 0x01
Parameter Number 0x2711 (10001d)
Subindex 0x0067 (103d)
Parameter datatype 0x42 = WORD
Number of parameters 0x01
Value: HI byte 0x00
Value: LOW byte 0x00
Following table contains messages sent during unsuccessful writing value to ID 103.
Table 92. Messages sent and received during unsuccessful writing value to ID 103
Answer indicates an unsuccessful operation with error "Low or high limit exceeded".
Table 93. Request to write the value of parameter ID 103 and ID 104
Field Contents
Request reference 0x06
Request ID 0x02 = Write parameter
Axis Number 0x01
No. of Parameters 0x02 (two parameters, ID 103 and ID104)
Attribute 0x10 = Value
Table 93. Request to write the value of parameter ID 103 and ID 104
Field Contents
No. of elements 0x01
Parameter Number 0x2711 (10001d)
Subindex 0x0067 (103d, ID 103)
Attribute 0x10 = Value
No. of elements 0x01
Parameter Number 0x2711 (10001d)
Subindex 0x0068 (104d, ID 104)
Parameter datatype 0x42 = WORD
Number of parameters 0x01
Value 0x0028 (Value for ID 103)
Parameter datatype 0x42 = WORD
Number of parameters 0x01
Value 0x0028 (Value for ID 104)
Following table contains messages sent during writing values to ID 103 and ID 104.
Table 94. Messages sent and received during writing value to ID 103
Connection
established
Communicating
Yes
Check
No No
Has additional
Yes timeout elapsed?
Yes
FAULT!
11719_uk
The OPTE9 will set its data status to GOOD as soon as it receives valid data from the AC drive. Unless
the communication to the AC drive breaks, the data remains GOOD. The IOCS are GOOD as soon as
the option board is able to receive and handle IO data.
The OPTE9 implements PROFINET IO alarm system where VACON® faults and alarms are seen on
bus as PROFINET IO alarms. The alarms use module specific channel diagnostic and extended
channel diagnostic data. The GSDML file contains description and help texts for the alarms. Texts
are in English and Finnish. Automation systems can use these texts to display helpful diagnostics to
end users in case of faults.
The figures below show how Siemens TIA portal displays the diagnostics.
Figure 46. Siemens TIA portal - Alarm description and help text
The VACON® data (faults, alarms, infos) mapped to PROFINET IO alarms is slightly different based
on the used AC drive:
VACON® faults are mapped to PROFINET IO alarms according to the following table:
Table 96.
For example, the fieldbus timeout fault (Fault code 53) in different drives have the following channel
error codes:
Table 97.
The customized applications might use customized fault IDs which are not described in the GSDML
file. The PROFINET IO alarms are however generated for all faults that have a fault code between 0
and 1000.
9. ETHERNET/IP
9.1 General information
9.1.1 Overview
You can provide configuration support for your device by using a specially formatted ASCII file, re-
ferred to as the EDS (Electronic Data Sheet). An EDS provides information about the device config-
uration.
The information in an EDS allows configuration tools to provide informative screens that guide a
user through the steps necessary to configure a device. An EDS provides all of the information nec-
essary to access and alter the configurable parameters of a device.
OPTE9 has multiple EDS files, at least one per AC drive type. You can download the AC drive specific
EDS from Danfoss website (http://drives.danfoss.com). See also Chapter 6.1.9 "EIP Product code
offset".
EDS files are split into two formats: static and dynamic. Only difference between these types is that
the static versions list all assembly pairs and all Listen Only and Input Only connections. PLC appli-
cation development tools usually show this as a list where you can simply select the wanted pair.
But if you want to mix assembly pairs, for example to command the drive with assembly 21 and get
assembly 117 back, you can use the dynamic-version. It allows you to input manually used assembly
instances and their sizes.
The OPTE9 LEDs follow the CIP standard when the EtherNet/IP is set as the active protocol. The
LEDs on the option board are not labeled as the CIP defines. The LED labels are described in table
below.
CIP
LED label Description
definition
RN Network Status Indicator NS
ER Not used -
BS Module Status indicator MS
The Module status LED is labeled on the board as "BS". It shows the status of the module, that is, if
a fault has occurred or if the module has been configured. The MS LED functionality is described in
the table below.
The Network status LED is labeled on the board as "RN". It shows the connectivity status of the
device, that is, if there is a connection to the device, or the IP settings status. The NS LED
functionality is described in the table below.
identifiers and contain the specific meaning of the message right in the data field. This includes the
service to be performed and the specific object attribute address.
NOTE! If Class 1 connection (cyclic data) has been established, the Explicit Messages should not be
used to control the Output Data. However this restriction does not apply for the IO Data reading.
The table below contains the error codes used by the OPTE9 EtherNet/IP implementation.
46d / 2Eh Service Not Supported The object supports the service, but not for the designated
for Specified Path application path (e.g. attribute).
These are the extended status codes used when the general status code is 1.
The EtherNet/IP declares a watchdog the time within which both master and slave must send IO
back to each other. This watchdog time is a factor of the communication cycle time (cycle time x
timeout multiplier) and is set by the master. Minimum cycle time for OPTE9 EtherNet/IP is 1
millisecond.
In case of normal communication mode, 4 ms is the fastest recommended cycle time for Ethernet/
IP. Faster cycle times (1 ms and 2 ms) are recommended in Fast Mode. See chapter 6.2 for more
details.
When an IO message is not received within the watchdog time, the timeout setting value is activated
and a fault is created after it elapses. This means that the panel parameter "Communication
timeout" (refer to chapter 6.1.6) is used as an additional timeout value. The same logic applies if a
connection is closed or the cable disconnects (link loss).
Implict Connection
established
Communicating
Check
No
Yes
Yes
FAULT!
11720_uk
Figure 47. EtherNet/IP timeout logic with implicit connection (IO connection)
The explicit connections (TCP connection where PLC/user reads and writes data via CIP objects) will
generate fieldbus fault only if that connection has been used to write process data over Assembly,
Control Supervisor or AC/DC object. The explicit connection timeout is defined with TCP/IP Object's
attribute 13d "Encapsulation Inactivity Timeout".
We recommend that implicit connection is used for motor control and explicit connections for
"service data".
Communicating
Check
Yes
Yes
FAULT! Offline
11721_uk
The Identity Object provides identification of and general information about the device.
• “VACON® NX (APFIFF06)”
• “VACON® 100 (1002)”
• “VACON® 20 (1009)”
When emulating the OPTCQ option board, the OPTE9 will always return text “OPTCQ” and when
emulating VACON® 100 family AC drive: “VACON® 100”.
9.2.1.1.2. SERVICES
The Message Router Object is mandatory in all CIP devices. It provides a messaging connection
point through which a Client may address a service to any object class or instance in a target device.
Although the object is mandatory, there are no mandatory attributes or services.
The OPTE9 drive does not currently implement any of the object’s services or attributes
The communication characteristics between the applications in different devices are modelled
using Connection Objects. The entities (devices) involved in a connection are referred to as end-
points. A Connection Manager is required in some CIP networks to control the aspects of Connection
object instances.
The Connection Manager class allocates and manages the internal resources associated with both
I/O and Explicit Messaging connections.
9.2.1.3.1. SERVICES
The TCP/IP Interface Object provides an interface to configure the device’s TCP/IP settings. With this
object, you can configure, for example, the device’s IP address, network mask and so on.
In the OPTE9 product, if the “IP Address Mode” panel parameter is “Fixed IP”, the value of the
Configuration Control is 0. If the “IP Address Mode” is “DHCP”, the value of the Configuration
Control is 2.
The OPTE9 does not support BOOTP or DNS.
Instance Attribute “Physical Link Object”
This attribute identifies the object which is associated with the underlying physical communications
interface (in the case of Ethernet, for example, the IEEE 802.3 interface). The attribute consists of
two components; a Path Size, which reveals the number of UINT values in the path, and the Path
itself.
In the OPTE9, the path points to an instance of the EtherNet Link Object. The value of the Path Size
is 2 (total of four octets) and the value of the Path is 20h F6h 24h XXh, where XX is the instance
number of the EtherNet Link object.
Table 115.
Value Description
0 Disable
1-3600 Timeout in seconds
Ethernet Link Object provides interface to Ethernet link counters and attributes. With this object,
user can retrieve for example link speed.
The assembly object groups (or assembles) the attribute values into a single block of data.
Motor Data Object provides interface to the motor data attributes, for example “motor type”.
Control Supervisor Object provides an interface for drive management. You can, for example, start
and stop the motor with this object.
Value Definition
0 Vendor Specific
1 Startup
2 Not_Ready
3 Ready
4 Enabled
5 Stopping
Value Definition
6 Fault_Stop
7 Faulted
Instance Attribute “Running1”
This attribute is used to describe the run state of the drive. The value of the attribute is 1, if one of
the below conditions are fulfilled:
• The “State” attribute has the value 4 (“Enabled”) and the bit “Run1” has the value 1, or
• The “State” attribute has the value 5 (“Stopping”) and the bit “Running1” has the value 1, or
• The “State” attribute has the value 6 (“Fault_Stop”) and the bit “Running1” has the value 1
Otherwise, the value of this attribute is 0.
Instance Attribute “Running2”
This attribute is used to describe the run state of the drive. The value of the attribute is 1, if one of
the below conditions are fulfilled:
• The “State” attribute has the value 4 (“Enabled”) and the bit “Run2” has the value 1, or
• The “State” attribute has the value 5 (“Stopping”) and the bit “Running2” has the value 1, or
• The “State” attribute has the value 6 (“Fault_Stop”) and the bit “Running2” has the value 1
Otherwise, the value of this attribute is 0.
Instance Attribute “Ready”
This attribute is used to signal the state of the drive that it is ready for operation. The value of the
attribute is 1 if the value of the “State” attribute is either 3 (“Ready”), 4 (“Enabled”) or 5 (“Stopping”).
Otherwise the value of this attribute is 0.
Instance Attribute “Faulted”
This attribute is used to signal that one or several faults have occurred in the drive. The value of the
attribute is 1 if a fault has occurred and has not been acknowledged. Otherwise, the attribute has
the value 0 indicating that no faults are present.
Instance Attribute “Warning”
This attribute is used to signal that one or several warnings have appeared in the drive. The value
of the attribute is 1 if a warning has appeared and has not been acknowledged. Otherwise, the
attribute has the value 0 indicating that no warnings are present.
Instance Attribute “FaultRst”
This attribute is used to reset faults and warnings in the drive. The attribute is write-only. Changing
the value of the attribute from 0 to 1 (rising-edge) resets the faults in the drive. If the value is static
0, no reset action is started.
Instance Attribute “FaultCode”
This attribute is used to read the kind of fault which has caused the device to transition into the
“Faulted” state. In the case of multiple faults occurring simultaneously, only one code is reported.
If the device is not in the Faulted state, the FaultCode attribute indicates the fault which caused the
last transition to the Faulted state.
Instance Attribute “CtrlFromNet”
It indicates whether the run/stop control is assigned to the local interface or to this network
interface. When the value of the attribute is 0, the control is local. When the value of the attribute is
1, the run/stop control is assigned to the network interface.
9.2.1.8.2. SERVICES
The Control Supervisor Object defines a state machine for governing the behaviour of devices. The
figure below describes the states and transitions of the state machine.
Non-existent Switch Off
Switch On
Fault Detected Main Power Off
Reset Startup Faulted
Fault Reset
Initialisation Complete
Fault_Stop
Complete
Fault Detected
Not_Ready
Ready Fault
Stop
Complete Detected
Stopping
Run
Stop
Enabled
7082_UK
Figure 49. Control Supervisor State Machine
Changes to DriveMode attribute must be reflected in the “Motor Control Mode Object”. The drive will
respond with “Invalid attribute value” status code 0x09, if other values are written.
Instance Attribute “SpeedActual”
This attribute allows reading of the speed actual value. The unit of the attribute must be (RPM /
2SpeedScale), where the SpeedScale is attribute 22d.
If the SpeedScale attribute is not used by the master, the default unit [1 RPM] is assumed. This is
equivalent to the value 0 being used for the SpeedScale.
The Vendor Parameters Object is a vendor-specific object which allows the user to access any
application parameter from the drive.
9.2.2.1.2. SERVICES
Table 132.
Field Data
Service Code 0Eh
Class Code A0h
Instance Number 01h
Attribute ID XXXXh
Table 133.
Field Data
Service Code 0Eh
Class Code A0h
Instance Number YYh
Attribute ID XXh
Table 134.
Field Data
Service Code 10h
Class Code A0h
Instance Number 01h
Attribute ID XXXXh
Attribute Data Parameter-specific
Table 135.
Field Data
Service Code 10h
Class Code A0h
Instance Number YYh
Attribute ID XXh
Attribute Data Parameter-specific
The Assembly Instance Selector Object is a vendor-specific object available in the OPTCQ option
board and the OPTE9. It allows the user to get and set the input and output instances used.
The OPTE9 option board will automatically change the current assembly instances by what is
requested in the connection opening. This means that it is not mandatory to pre-set assembly
instances.
9.2.2.2.2. SERVICES
Table 137.
Field Data
Service Code 0Eh
Class Code BEh
Instance Number 01h
Attribute ID 03h or 04h
Table 138.
Field Data
Service Code 10h
Class Code BEh
Instance Number 01h
Attribute ID 03h or 04h
Attribute Data (Assembly number)
If an I/O connection has been established with a master through the Forward_Open request and a
successful response, any request to set the selected assembly through the Assembly Instance
Selector object is rejected. These attributes may only be changed when no I/O connection is
established, i.e. before the Forward_Open request.
The Motor Control Mode Object is a vendor-specific object available in the OPTE9 which more clearly
indicates to the user which motor control mode is used, and allows the user to configure this mode.
Value Description
0d Frequency control
1d Speed control
2d Torque control
9.2.2.3.2. SERVICES
Table 142.
Field Data
Service Code 0Eh
Class Code BEh
Instance Number 01h
Attribute ID 01h or 02h
Table 143.
Field Data
Service Code 10h
Class Code BEh
Instance Number 01h
Attribute ID 01h or 02h
Attribute Data (Mode number)
The Motor Control Mode Object is linked to the “DriveMode” attribute of the AC/DC Drive Object so,
that changes in one affects the values in the other.
In the OPTE9, when the following values are set to the AC/DC Drive Object “DriveMode” attribute,
the Motor Control Mode Object attributes are set to the following values:
Table 144.
*Feedback mode does not change. CIP does not define is torque control open or closed loop.
In the OPTE9, when the following values are set to the Motor Control Mode Object “ControlMode”
and “FeedbackMode” attributes, the AC/DC Drive Object “DriveMode” attribute is set as follows:
Table 145.
The Fault History Object is a vendor-specific object available in the OPTE9 and in VACON® 100 family
AC drive which allows access to the contents of the fault history over the EtherNet/IP network.
Each entry in a fault history is represented by an instance of the Fault History Object. Low instance
numbers correspond to the most recent fault entries.
The attributes FaultCode and FaultDay were changed from 8 bit to 16 bit.
Maximum number of
Drive
faults
VACON® 20
VACON® 20 X 10
VACON® 20 CP
VACON® NXP 30
VACON® NXS 30
VACON® 100 family 40
The table below contains a simple listing of supported assembly instances. You can find more
detailed description of each assembly instance in the chapters below. As the detailed descriptions
can contain exceptions based on the drive type, application version and so on, read them before
taking any assembly instance into use.
The OPTE9 supports the Output Assembly Instances 20, 21, 23 and 25, and the Input Assembly
Instances 70, 71, 73 and 75.
The control word bits are mapped to the object data according to the table below.
The status word bits are mapped to the object data according the table below.
The Speed Reference is updated to the drive only when the NetRef bit is set to 1. The torque
reference is updated to the drive only when the motor control mode is “Torque Control”.
Table 153.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Fault Run
0
Reset Fwd
20 1
(length 4)
2 Speed Reference (Low Octet)
3 Speed Reference (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW CIP Control Word
Table 155.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Fault Run Run
0 NetRef NetCtrl
Reset Rev Fwd
21 1
(length 4)
2 Speed Reference (Low Octet)
3 Speed Reference (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW CIP Control Word
Table 157.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Fault Run Run
0 NetRef NetCtrl
Reset Rev Fwd
1
23 2 Speed Reference (Low Octet)
(length 6)
3 Speed Reference (High Octet)
4 Torque Reference (Low Octet)
5 Torque Reference (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW CIP Control Word
The extended process control assembly can be used to send process reference value directly to the
application. The Process Reference value destination can be selected with the Drive Mode byte
according to the table below. This should be configured in the application as the receiving input. To
the other direction (input assembly instance 75), the ProcessDataOut1 is always mapped to the
Process Actual. Note that the process reference value is sent to the drive only when NetProc bit is
set.
The VACON® AC drives do not support the actual “Process Control”-mode. Therefore the Drive Mode
cannot be set to the Process Control by using the AC/DC Drive Object attribute, and the Drive Mode
parameter in this assembly is only used to select the process reference. With these mappings, the
Process Reference and Process Actual can be used with an application that supports the PID
control.
Table 160.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Net- Fault Run Run
0 NetRef NetCtrl
proc Reset Rev Fwd
1 Drive Mode
23 2 Speed Reference (Low Octet)
(length 6)
3 Speed Reference (High Octet)
4 Process Reference (Low Octet)
5 Process Reference (High Octet)
Table 162.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Runnin
0 Faulted
g1
70 1
(length 4)
2 Speed Actual (Low Octet)
3 Speed Actual (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 164.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Ref- Ctrl- Runnin Runnin
AtRef- Warn-
0 From- From- Ready g2 g1 Faulted
erence ing
Net Net (Rev) (Fwd)
71
(length 4) 1 Drive State
2 Speed Actual (Low Octet)
3 Speed Actual (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 166.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Ref- Ctrl- Runnin Runnin
AtRef- Warn-
0 From- From- Ready g2 g1 Faulted
erence ing
Net Net (Rev) (Fwd)
1 Drive State
73
(length 6) 2 Speed Actual (Low Octet)
3 Speed Actual (High Octet)
4 Torque Actual (Low Octet)
5 Torque Actual (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
See Chapter "9.3.1.1.4. Assembly Instance 25 – Extended Process Control Output" for details.
Table 168.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Ref- Ctrl- Runnin Runnin
AtRef- Warn-
0 From- From- Ready g2 g1 Faulted
erence ing
Net Net (Rev) (Fwd)
1 Drive State
75
(length 6) 2 Speed Actual (Low Octet)
3 Speed Actual (High Octet)
4 Process Actual (Low Octet)
5 Process Actual (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 170.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Fault Run Run
0 NetRef NetCtrl
Reset Rev Fwd
1
2 FBSpeedReference (Low Octet) in %
101 3 FBSpeedReference (High Octet) in %
(length 8)
4 FBProcessDataIn1 (Low Octet)
5 FBProcessDataIn1 (High Octet)
6 FBProcessDataIn2 (Low Octet)
7 FBProcessDataIn2 (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW CIP Control Word
Table 172.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 FBFixedControlWord (Low Octet)
1 FBFixedControlWord (High Octet)
2 FBSpeedReference (Low Octet) in %
3 FBSpeedReference (High Octet) in %
4 FBProcessDataIn1 (Low Octet)
5 FBProcessDataIn1 (High Octet)
6 FBProcessDataIn2 (Low Octet)
7 FBProcessDataIn2 (High Octet)
8 FBProcessDataIn3 (Low Octet)
111 9 FBProcessDataIn3 (High Octet)
(length 20) 10 FBProcessDataIn4 (Low Octet)
11 FBProcessDataIn4 (High Octet)
12 FBProcessDataIn5 (Low Octet)
13 FBProcessDataIn5 (High Octet)
14 FBProcessDataIn6 (Low Octet)
15 FBProcessDataIn6 (High Octet)
16 FBProcessDataIn7 (Low Octet)
17 FBProcessDataIn7 (High Octet)
18 FBProcessDataIn8 (Low Octet)
19 FBProcessDataIn8 (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW FBFixedControlWord
Table 174.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 FBFixedControlWord (Low Octet)
1 FBGeneralControlWord (High Octet)
2 FBSpeedReference (Low Octet) in %
3 FBSpeedReference (High Octet) in %
4 FBProcessDataIn1 (Low Octet)
5 FBProcessDataIn1 (High Octet)
6 FBProcessDataIn2 (Low Octet)
7 FBProcessDataIn2 (High Octet)
8 FBProcessDataIn3 (Low Octet)
128 9 FBProcessDataIn3 (High Octet)
(length 20) 10 FBProcessDataIn4 (Low Octet)
11 FBProcessDataIn4 (High Octet)
12 FBProcessDataIn5 (Low Octet)
13 FBProcessDataIn5 (High Octet)
14 FBProcessDataIn6 (Low Octet)
15 FBProcessDataIn6 (High Octet)
16 FBProcessDataIn7 (Low Octet)
17 FBProcessDataIn7 (High Octet)
18 FBProcessDataIn8 (Low Octet)
19 FBProcessDataIn8 (High Octet)
The contents of the assembly are otherwise identical to the output assembly 111, except that the
second octet of the assembly is the high octet of FBGeneralControlWord instead of
FBFixedControlWord.
Name Value
Drive CW FBFixedControlWord
Protocol CW FBGeneralControlWord
Table 176.
NOTE: Current firmware versions of VACON® 100 family and OPTE9 do not support transfering of 32
bit process data. Only the lower 16 bits are transfered.
Name Value
Drive CW FBFixedControlWord
Protocol CW FBGeneralControlWord
Table 178.
Instance Octet Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 FBFixedControlWord (Low Octet)
1 FBFixedControlWord (High Octet)
2 FBGeneralControlWord (Low Octet)
3 FBGeneralControlWord (High Octet)
4 FBSpeedReference (Low Octet) in %
5 FBSpeedReference (High Octet) in %
6 FBProcessDataIn1 (Low Octet)
151 7 FBProcessDataIn1 (High Octet)
(length 38) ... ...
20 FBProcessDataIn8 (Low Octet)
21 FBProcessDataIn8 (High Octet)
22* FBProcessDataIn9 (Low Octet)
23* FBProcessDataIn9 (High Octet)
... ...
36* FBProcessDataIn16 (Low Octet)
37* FBProcessDataIn16 (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW FBGeneralControlWord
Table 180.
Instance Octet Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Run-
0 NetRef NetCtrl Fault Reset RunRev
Fwd
1
2 FBSpeedReference (Low Octet) in %
3 FBSpeedReference (High Octet) in %
4 FBProcessDataIn1 (Low Octet)
5 FBProcessDataIn1 (High Octet)
161 ... ...
(length 36)
18 FBProcessDataIn8 (Low Octet)
19 FBProcessDataIn8 (High Octet)
20* FBProcessDataIn9 (Low Octet)
21* FBProcessDataIn9 (High Octet)
... ...
34* FBProcessDataIn16 (Low Octet)
35* FBProcessDataIn16 (High Octet)
Name Value
Drive CW FBFixedControlWord
Protocol CW CIP Control Word
Table 182.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Ref- Ctrl- Runnin Runnin
AtRef- Warn-
0 From- From- Ready g2 g1 Faulted
erence ing
Net Net (Rev) (Fwd)
1 Drive State
2 FBSpeedActual (Low Octet) in %
107
(length 8) 3 FBSpeedActual (High Octet) in %
4 FBProcessDataOut1 (Low Octet)
5 FBProcessDataOut1 (High Octet)
6 FBProcessDataOut2 (Low Octet)
7 FBProcessDataOut2 (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW CIP Status Word
Table 184.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 FBFixedStatusWord (Low Octet)
1 FBFixedStatusWord (High Octet)
2 FBSpeedActual (Low Octet) in %
3 FBSpeedActual (High Octet) in %
4 RPMSpeedActual (Low Octet) in rpm
5 RPMSpeedActual (High Octet) in rpm
6 RPM With Slip SpeedActual (Low Octet) in rpm
7 RPM With Slip SpeedActual (High Octet) in rpm
8 Reserved (=0)
... Reserved (=0)
17 Reserved (=0)
18 FBProcessDataOut1 (Low Octet)
19 FBProcessDataOut1 (High Octet)
117
20 FBProcessDataOut2 (Low Octet)
(length 34)
21 FBProcessDataOut2 (High Octet)
22 FBProcessDataOut3 (Low Octet)
23 FBProcessDataOut3 (High Octet)
24 FBProcessDataOut4 (Low Octet)
25 FBProcessDataOut4 (High Octet)
26 FBProcessDataOut5 (Low Octet)
27 FBProcessDataOut5 (High Octet)
28 FBProcessDataOut6 (Low Octet)
29 FBProcessDataOut6 (High Octet)
30 FBProcessDataOut7 (Low Octet)
31 FBProcessDataOut7 (High Octet)
32 FBProcessDataOut8 (Low Octet)
33 FBProcessDataOut8 (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBFixedStatusWord
Table 186.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 FBFixedStatusWord (Low Octet)
1 FBGeneralStatusWord (High Octet)
2 FBSpeedActual (Low Octet) in %
3 FBSpeedActual (High Octet) in %
4 FBProcessDataOut1 (Low Octet)
5 FBProcessDataOut1 (High Octet)
6 FBProcessDataOut2 (Low Octet)
7 FBProcessDataOut2 (High Octet)
8 FBProcessDataOut3 (Low Octet)
127 9 FBProcessDataOut3 (High Octet)
(length 20) 10 FBProcessDataOut4 (Low Octet)
11 FBProcessDataOut4 (High Octet)
12 FBProcessDataOut5 (Low Octet)
13 FBProcessDataOut5 (High Octet)
14 FBProcessDataOut6 (Low Octet)
15 FBProcessDataOut6 (High Octet)
16 FBProcessDataOut7 (Low Octet)
17 FBProcessDataOut7 (High Octet)
18 FBProcessDataOut8 (Low Octet)
19 FBProcessDataOut8 (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 188.
NOTE: Current firmware versions of VACON® 100 family and OPTE9 do not support transfering of 32
bit process data. Only the lower 16 bits are transfered.
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 190.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 FBFixedStatusWord (Low Octet)
1 FBFixedStatusWord (High Octet)
2 FBGeneralStatusWord (Low Octet)
3 FBGeneralStatusWord (High Octet)
4 FBSpeedActual (Low Octet) in %
5 FBSpeedActual (High Octet) in %
6 FBProcessDataOut1 (Low Octet)
157 7 FBProcessDataOut1 (High Octet)
(length 38) ... ...
20 FBProcessDataOut8 (Low Octet)
21 FBProcessDataOut8 (High Octet)
22* FBProcessDataOut9 (Low Octet)
23* FBProcessDataOut9 (High Octet)
... ...
36* FBProcessDataOut16 (Low Octet)
37* FBProcessDataOut16 (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW FBGeneralStatusWord
Table 192.
Instance Octet Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Running1 (Fwd)
Running2 (Rev)
CtrlFromNet
AtReference
RefFromNet
Warning
Faulted
Ready
0
1 Drive State
2 FBSpeedActual (Low Octet) in %
3 FBSpeedActual (High Octet) in %
167 4 FBProcessDataOut1 (Low Octet)
(length 36) 5 FBProcessDataOut1 (High Octet)
... ...
18 FBProcessDataOut8 (Low Octet)
19 FBProcessDataOut8 (High Octet)
20* FBProcessDataOut9 (Low Octet)
21* FBProcessDataOut9 (High Octet)
... ...
34* FBProcessDataOut16 (Low Octet)
35* FBProcessDataOut16 (High Octet)
Name Value
Drive SW FBFixedStatusWord
Protocol SW CIP Status Word
This section specifies how the data in the Standard Output Assemblies are mapped into VACON®
data.
FBGeneralControlWord and FBGeneralStatusWord are purely application specific. Check the used
application’s manual for description of their content.
9.3.3.2 FBFixedControlWord
If one of the “RunFwd” or “RunRev” bits in an Output Assembly has the value 1, the “Start/Stop” bit
0 in the VACON® FBFixedControlWord is set to 1. Otherwise the bit is set to 0.
If both the “RunFwd” and “RunRev” bits have the value 1, no changes are done to
FBFixedControlWord.
If the “RunRev” bit in an Output Assembly has the value 1, and the “RunFwd” bit in the assembly has
the value 0, then the “Direction” bit 1 in the VACON® FBFixedControlWord is set to 1. Otherwise the
bit is set to 0.
The “Fault Reset” bit in an Output Assembly is mapped to the “Fault Reset” bit 2 in the VACON®
FBFixedControlWord. Both bits are rising-edge sensitive.
The “NetCtrl” bit in an Output Assembly is not mapped to the “Request Fieldbus Control” bit 8 in the
VACON® FBFixedControlWord because this way you can place the drive to the IO or keypad control
while fieldbus is active.
The “NetRef” bit in an Output Assembly is not mapped to the “Request Fieldbus Reference” bit 9 in
the VACON® FBFixedControlWord.
If the EtherNet/IP communication with the master device is functional, the bit 15 in the VACON®
FBFixedControlWord is set to 1. If the communication with the master device is not working, the bit
15 in the FBFixedControlWord is set to 0.
This section specifies how the VACON® data is mapped onto the data in the Standard Input
Assemblies.
9.3.4.1 FBFixedStatusWord
The “Ready Indication” bit 0 in the VACON® FBFixedStatusWord is mapped to the “Ready” bit in an
Input Assembly which supports this bit.
The “Run/Stop Indication” bit 1 in the VACON® FBFixedStatusWord is mapped to the “Running1” and
“Running2” bits in an Input Assembly which supports these bits. The state of the Running1 and
Running2 bits depends further on the “Direction Indication” bit 2 of the VACON® FBFixedStatusWord
as follows:
Run/Stop = 0 Run/Stop = 1
Direction = X Direction = 0 Direction = 1
Running1 0 1 0
Running2 0 0 1
The “Fault Indication” bit 3 in the VACON® FBFixedStatusWord is mapped to the “Faulted” bit in an
Input Assembly which supports this bit.
The “Alarm Indication” bit 4 in the VACON® FBFixedStatusWord is mapped to the “Warning” bit in
an Input Assembly which supports this bit.
The “Setpoint Reached Indication” bit 5 in the VACON® FBFixedStatusWord is mapped to the
“AtReference” bit in an Input Assembly which supports this bit.
The selected control place is indicated in the Input Assemblies which contain the “CtrlFromNet” bit.
If the control place is assigned to fieldbus then this bit is set to 1, else it is 0.
The selected reference is indicated in Input Assemblies which contain the “RefFromNet” bit. If the
reference is assigned to fieldbus then this bit is set to 1, otherwise it is 0.
This is the reference 1 to the AC drive. The allowed scaling is from 0 to 10000. In the application, the
value is scaled in percentage of the frequency area between set minimum and maximum frequency.
In addition to the normal connection (Exclusive Owner) where certain input and output instances are
used, the PLC can also open INPUT ONLY and LISTEN ONLY connections to the drive. When using
the INPUT ONLY connection, the PLC opens a connection where it only receives data from the drive.
It does not send any commands to the drive. When opening the INPUT only connection, the PLC user
must set the output instance to 253 and the size to 0. The input instance can be selected freely. The
INPUT ONLY connection can be the only connection to the drive, where as the LISTEN ONLY
connection always requires a normal "Exclusive Owner" connection. When opening the LISTEN
ONLY connection, the PLC user must set the output instance to 254 and the size to 0. The input
instance in LISTEN ONLY connection and the Data cycle (packet rate) must match to the one used in
the Exclusive Owner connection.
Table 195.
Description Instance Size
Configuration instance 103d / 67h 0
Output instance 21d / 15h 4
Input instance 71d / 47h 4
Poor Check
communication Check cabling connections
Option board can report only Fieldbus communications fault (F53). This does not identify what
actually went wrong and why option board activated this fault. To that end, more information is now
added to fault activation. Currently this works only with VACON® 100 family AC drives.
In VACON® 100 family AC drive with default applications when fieldbus fault is activated (F53
specifically), new information is added to the faults "source"-fields if the source fields are empty.
The table below contains "source 3" additional fault codes supported by OPTE9 option board.
The Control word is composed of 32 bits. FBFixedControlWord consist of the first 16 bits. FBGen-
eralControlWord consist of the remaining 16 bits. While the functionality of FBFixedControlWord is
fixed in the VACON® standard applications, the functionality of FBGeneralControlWord is totally
application specific and can vary even in the VACON® standard applications.
The meanings of FBFixedControlWord bits are described below. Unused bits have to be set to zero.
NOTE! This table is valid for VACON® standard applications.
NOTE! There are some control word bit modifications in VACON® NXP AC drive. These modifications
are described in Table 201. Unused bits have to be set to zero.
The Status word is composed of 32 bits. FBFixedStatusWord consist of the first 16 bits. FBGen-
eralStatusWord consist of the remaining 16 bits. While the functionality of FBFixedStatusWord is
fixed in the VACON® standard applications, the functionality of FBGeneralStatusWord is totally
application specific and can vary even in the VACON® standard applications.
The meanings of FBFixedStatusWord bits are described below. Unused bits have to be set to zero.
In VACON® NX series AC drives the FBFixedStatusWord comes from firmware variable "MCStatus".
This table describes the control word bit support in different AC drives. Notice that this table is valid
only for the VACON® standard applications. Always check the application-specific status from the
application manual.
This table describes the status word bit support in different drives. Notice that this table is valid only
for the VACON® standard applications. Always check the application-specific status from the
application manual.
VACON® VACON®
VACON® VACON®
Bit Function 100 NXS/
20 20 X
family NXP
B0 Ready x x x x
B1 Run x x x x
B2 Direction x x x x
B3 Fault x x x x
B4 Alarm x x x x
B5 At reference x x x x
B6 Zero speed x x x
B7 Flux ready x x
B8 Reserved
B9 Reserved
B10 Reserved
B11 Reserved
B12 Reserved
B13 Reserved
B14 Reserved
B15 Reserved
This guide shows how to configure the communication between Siemens PLC and VACON® AC drive
by using STEP 7.
1. Create a new project. Give the project a name and click OK.
4. Install GSDML for VACON® device. Select Options-> Install GSD File…
8. Next continue inserting the required hardware to the project. Insert the rail.
11. Change the IP address and select the subnet by clicking New.
17. Change the Option board properties. Here you can change the name (Name Of Station) and board
IP settings. Use only small letters in the name. To see more information about the Name Of Station,
see Chapter 6.1.7.
This example shows how to configure the Siemens S7-300 PLC series to use the VACON® OPTE9
option board with the Siemens TIA Portal programming tool. Check your individual PLC informa-
tion. The information used in this example probably differs from the one you have.
2. Give the project a name and location and click “Create”. When the project is created, click “Proj-
ect View” from the lower left corner of the screen.
11. The configuration is complete. Follow the next steps to load the configuration to the PLC.
12. Select the connection interface from the dropdown menu (how the PC with TIA Portal is con-
nected to network with the PLC). Then click search. When the search is completed you should see
your PLC in the list. Select it and click Load.
15. When the loading is ready, click Finish. Now the PLC should start communicating with the option
board.
1. Use Device Integration manager to import the OPTE9 Dual Port Ethernet option board's EDD file.
2. Select the folder that contains the correct EDD file for your AC drive and application.
3. Click the "Integration" button. Now, you can see a green check mark for the OPTE9 Dual Port
Ethernet EDD file.
4. Insert the OPTE9 device into the network by selecting "Insert New Object" -> "Object".
5. Enter the correct IP address for the OPTE9 Dual Port Ethernet option board. Currently used IP
address can be seen from the monitor values. See Chapter 6.1.2 "Option board monitoring values".
The following tables list some of the parameters related to fieldbus control in case of VACON®
applications for the VACON® 100 family, VACON® 20 / 20X and VACON® NXP. See the application
specific manuals for more detailed information.
Parameters can be read and written by using the drive panel, PC Tools or fieldbus protocol. The
table below contains links to chapters where the ID value reading is described.
Protocol Chapter
See Chapter "7.3.2.5.1. VACON® application IDs"
Modbus
See Chapter "7.3.2.5.4. ID map"
Profinet IO See Chapter 8.4.7 "Drive parameter access using application ID"
EtherNet/IP See Chapter 9.2.2.1 "Vendor Parameters Object, Class 0xA0"
0 = Frequency
Control mode 600 1 = Speed 0 P 3.1.2.1
2 = Torque
0 = Frequency
Motor control mode 600 0 P 1.8
1 = Speed
0 = Frequency
Motor control mode 600 0 P 8.1
1 = Speed
0 = Frequency
Motor control mode 600 1 = Speed 0 P 2.6.1
2 = Torque
Use the "Controlling Fieldbus"-parameter to select the instance from which the process data is sent
to the drive application. By default the setting is in "Automatic" and the functionality (when receiving
process data from multiple sources) is application dependent.
For example, if the option board has been installed to slot E and it is used with PROFINET to control
the drive, user can select "Slot E" as value for this parameter. Now only the process data from the
option board in slot E is forwarded to the application. All other fieldbusses will still receive process
data out. With this setting it is possible to prevent that the monitoring fieldbusses accidentally write
process data in.
Table 210.
RS485 4 Only process data from VACON® 100 family internal RS 485
protocol is forwared to application
Table 210.
PROFINET IO 5 Only process data from VACON® 100 family internal PROFI-
NET IO protocol is forwared to application
EtherNet/IP 6 Only process data from VACON® 100 family internal Ether-
Net/IP protocol is forwared to application
Modbus TCP/
7 Only process data from VACON® 100 family internal Modbus
UDP TCP/UDP protocol is forwared to application
Bacnet IP 8 Only process data from VACON® 100 family internal Bacnet
IP protocol is forwared to application
Some extra parametrisation has to be made in order to control the frequency control with torque
control. The following instructions are for the VACON® 100 family and VACON® NXP application, see
the application-specific manual for more detailed information.
• Motor control mode (ID 600) should be configured to "Torque control" (2).
To configure the drive to use correct torque reference, select the parameter "Torque Reference
Selection" to ProcessDataIn1 (9). This can be done with:
- PC-tool or panel (VACON® 100 family: P 3.3.2.1, VACON® NXP: P 2.10.4) / ID 641
- Vendor Parameter Object
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1.Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the distri-
bution.
3.The name of the author may not be used to endorse or promote products derived from this soft-
ware without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The following tables describe the required components for different communication modes:
Supported system software version depends on NXP hardware version. Hardware version can be
determined reading the serial number:
Fast mode:
• 1 ms process data interval
• Available in VACON® NXP slots D and E
- Possible to run both slots simultaneously
- Have similar process data latency in both slots
• Service data latency is also reduced
- Running multiple service data queries at high interval can cause high CPU load in VACON®
NXP AC drive.
16 process data items:
• 16 process data items always require support from application
• Available in both Fast mode and Normal Extended mode
• If no support is available the process data out shall always be '0', while incoming process
data items 9-16 are discarded
The normal fieldbus communication between option board and the AC drive application is visible in
Figure 52. In normal communication both process data and service data are transferred in
succession at 5 ms interval.
Communication delay for process data can be calculated by summing all delays together:
t = t IOdatacycle + t updateinterval + 2 ⋅ t communicationdelay + t applicationcycle
Example: With fieldbus cycle time of 4 ms and application cycle of 10 ms, the delay is:
t = 4ms + 10ms + ( 2 ⋅ 5 )ms + 10ms = 34ms
NOTE: This value does not include delays of the fieldbus master, jitter in the process data cycle of
the communication protocol or resending due to electronic interference.
Process
IO Data Update Data
The fast mode decreases the communication delay between the PLC and the AC drive application
significantly by using two communication channels separately for process and service data. The
process data interval is set to 1 ms, while other data is sent acyclically. When the fast mode is
activated, the application can be synchronized to run with the communication cycle. The Fast
communication mode is visible in Figure 53. This mode also includes the ability to transfer 16
process data items.
The communication delay for process data in fast communication mode is (when application task is
synchronized with communication):
t = tIOdata cycle + tupdate interval + tapplication cycle
Example: With fieldbus cycle time of 1 ms an application cycle of 1 ms the delay is::
t =1 ms + 1 + 1 ms = 3 ms
NOTE: This value does not include delays of the fieldbus master, jitter in the process data cycle of
the communication protocol or resending due to electronic interference.
Process
IO Data Data
High Application
Cyclic task
Priority SPI SPI
x ms 1-50ms
Software 1ms 1ms
Service
UART Data
Acyclic Low Application
Priority Acyclic
task
Parameters, 50-500ms
etc.
The fast safety mode uses the same communication methods as in "Fast mode" (Figure 53), but also
transfers safety "black channel" data used by the safety fieldbus.
NOTE! This mode is automatically enabled, if an extended safety option board is connected to slot D
and the safety fieldbus is activated and cannot be set by the user. This mode is also automatically
turned off when the safety option board is removed.
Process
Data
Application
task
IO Data
1-50ms
Cyclic SPI Service
Software SPI Data
x ms 1ms 1ms Application
task
Only 50-500ms
in startup!
Option Board Drive Control Board
11724_uk
The normal extended mode uses the same communication method that is used in "Fast mode", but
reduces the communication cycle to 5ms. Therefore, the communication delay is still faster than in
"Normal mode".
This mode can be used in applications where 16 process data items are required but the lowest
possible communication delay is not needed or the increased CPU load of Fast mode to VACON®
NXP AC drives is problematic.
NOTE: This mode is automatically enabled in VACON® Applications supporting 16 process data
items.
* Fast safety mode is automatically enabled/disabled by system software. Cannot be set by user. This mode is
not supported in OPTE9 Dual Port Ethernet.
** Fast PROFIBUS mode is not supported in OPTE9 Dual Port Ethernet.
FBModeSlotX_fwu8 variables are used to select the active fieldbus option board communication
mode. If no fieldbus option board is connected to the related slot, the selection of the FBModeSlot
parameter is set to 0 = Normal mode.
Table 214. System software variables for monitoring supported communication modes
Parameter Value Default
0x00 = Not yet updated. Read again later
FBModeSlotDSupModes_fwu16 0x01 = Fieldbus communication not supported 0
0x02 = Normal mode supported
0x04 = Fast safety mode supported
0x08 = Fast mode supported
FBModeSlotESupModes_fwu16 0x10 = Fast PROFIBUS mode supported 0
0x20 = Normal extended mode supported
Table 215. System software variables for selecting the input process data slot
Parameter Value Default
0 = All slots
4 = Slot D only
FBControlSlotSelector_fwu8 5 = Slot E only 0
6 = Fast PROFIBUS D slot*
7 = Fast PROFIBUS E slot*
FBControlSlotSelector_fwu8 variable is used to select the controlling fieldbus option board slot.
When selected (other than '0'), process data is accepted only from the selected slot and all other
process data is discarded. Process data out is still updated normally to all slots.
This selector can be used to support redundant fieldbus connection. In fieldbus redundancy mode
two fieldbus option boards are installed to VACON® NXP option board slots D and E. Application
selects with FBControlSlotSelector_fwu8 variable which fieldbus option board can deliver process
data from fieldbus master to the application.
Default value for FBControlSlotSelector_fwu8 is '0' which means that process data is accepted from
both fieldbus option boards.
Document ID:
Vacon Ltd
Member of the Danfoss Group DPD01583F
Runsorintie 7 Rev. F
65380 Vaasa
Finland Sales code: DOC-OPTE9+DLUK