Beckhoff CX-M930 Series User manual

AS2000
Blindtext Blindtext Blindtext
Manual | EN
CXxxxx-M930/B930
Profinet Optional Interface for CX9020, CX5xx0 and CX20xx
2/5/2021 | Version: 1.1

Table of contents
CXxxxx-M930/B930 3Version: 1.1
Table of contents
1 Notes on the documentation ....................................................................................................................5
1.1 Representation and structure of warnings.........................................................................................6
1.2 Documentation issue status ..............................................................................................................7
2 System overview PROFINET ....................................................................................................................8
2.1 Beckhoff components ........................................................................................................................8
2.2 Technical data – Profinet.................................................................................................................10
3 Connection and cabling..........................................................................................................................11
3.1 PROFINET connection ....................................................................................................................11
3.2 Cabling ............................................................................................................................................12
3.3 Topology..........................................................................................................................................13
4 TwinCAT tabs...........................................................................................................................................14
4.1 Tree view .........................................................................................................................................14
4.2 Profinet master ................................................................................................................................16
4.2.1 PROFINET....................................................................................................................... 16
4.2.2 Sync Task ........................................................................................................................ 17
4.2.3 Settings............................................................................................................................ 18
4.3 Profinet slave...................................................................................................................................19
4.3.1 PROFINET....................................................................................................................... 19
4.3.2 Sync Task ........................................................................................................................ 20
4.3.3 Device.............................................................................................................................. 21
5 Parameterization and commissioning...................................................................................................22
5.1 Searching for target systems...........................................................................................................22
5.2 Adding a PROFINET slave..............................................................................................................24
5.3 Configuring process data.................................................................................................................26
5.4 'Turning' process data......................................................................................................................27
5.5 Creating a virtual slave ....................................................................................................................28
5.6 Creating a PLC project ....................................................................................................................30
5.7 Linking variables..............................................................................................................................32
5.8 Load configuration to CX .................................................................................................................33
5.9 Adding the PROFINET master ........................................................................................................35
6 Error handling and diagnostics..............................................................................................................37
6.1 Diagnostic LEDs ..............................................................................................................................37
6.2 Box states........................................................................................................................................38
6.3 Cyclic diagnostics ............................................................................................................................39
7 Appendix ..................................................................................................................................................43
7.1 Certifications....................................................................................................................................43
7.2 Support and Service ........................................................................................................................44
8 List of tables.............................................................................................................................................45
9 List of figures...........................................................................................................................................46

Table of contents
CXxxxx-M930/B9304 Version: 1.1

Notes on the documentation
CXxxxx-M930/B930 5Version: 1.1
1 Notes on the documentation
This description is only intended for the use of trained specialists in control and automation engineering who
are familiar with applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing
and commissioning the components.
It is the duty of the technical personnel to use the documentation published at the respective time of each
installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, EtherCAT G®, EtherCAT G10®, EtherCAT P®, Safety over EtherCAT®,
TwinSAFE®, XFC®, XTS® and XPlanar® are registered trademarks of and licensed by Beckhoff Automation
GmbH.
Other designations used in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents:
EP1590927, EP1789857, EP1456722, EP2137893, DE102015105702
with corresponding applications or registrations in various other countries.
EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany
Copyright
© Beckhoff Automation GmbH & Co. KG, Germany.
The reproduction, distribution and utilization of this document as well as the communication of its contents to
others without express authorization are prohibited.
Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a
patent, utility model or design.

Notes on the documentation
CXxxxx-M930/B9306 Version: 1.1
1.1 Representation and structure of warnings
The following warnings are used in the documentation. Read and follow the warnings.
Warnings relating to personal injury:
DANGER
Hazard with high risk of death or serious injury.
WARNING
Hazard with medium risk of death or serious injury.
CAUTION
There is a low-risk hazard that can result in minor injury.
Warnings relating to damage to property or the environment:
NOTE
There is a potential hazard to the environment and equipment.
Notes showing further information or tips:
This notice provides important information that will be of assistance in dealing with the product or
software. There is no immediate danger to product, people or environment.

Notes on the documentation
CXxxxx-M930/B930 7Version: 1.1
1.2 Documentation issue status
Version Modifications
1.0 First version
1.1 Chapter "Technical data" and "PROFINET
connection" adapted.

System overview PROFINET
CXxxxx-M930/B9308 Version: 1.1
2 System overview PROFINET
2.1 Beckhoff components
PROFINET is the open Industrial Ethernet-standard of the PNO (PROFINET user organization). PROFINET
IO describes the exchange of data between controllers and field devices in several real-time classes: RT
(software-based real-time) and IRT (hardware-supported isochronous real-time). In addition, further Ethernet
traffic can be transmitted in the NRT (non-real-time) time slot of the PROFINET cycle. RT can be networked
with commercially available switches; switches with corresponding hardware support are required for IRT.

System overview PROFINET
CXxxxx-M930/B930 9Version: 1.1
Beckhoff PROFINET components
Components Comment
Embedded PCs
CX8093 Embedded PC with PROFINET RT Device fieldbus
interface
CX50xx-M930 Embedded PC with optional interface
PROFINET RT Controller
CX50xx-B930 Embedded PC with optional PROFINET RT Device
interface
EtherCAT terminals
EL6631 PROFINET IO controller
EL6631-0010 PROFINET IO device
EL6632 PROFINET-IRT controller
Bus Coupler
BK9053 PROFINET "Compact" Bus Coupler for Bus
Terminals
BK9103 PROFINET Bus Coupler for Bus Terminals
EK9300 PROFINET Bus Coupler for EtherCAT Terminals
Fieldbus Box
IL230x-B903 PROFINET Coupler Box
PC Fieldbus Cards
FC900x PCI Ethernet card for all Ethernet
(IEEE 802.3)-based protocols
FC9x51 Miniature PCI Ethernet card for all Ethernet
(IEEE 802.3)-based protocols
TwinCAT
TwinCAT PROFINET IO Controller TwinCAT as PROFINET master
TwinCAT PROFINET IO Device TwinCAT as PROFINET slave

System overview PROFINET
CXxxxx-M930/B93010 Version: 1.1
2.2 Technical data – Profinet
Optional interface M930
Technical data M930
Fieldbus Profinet RT Controller
Data transfer rate 100 Mbaud
Bus interface 2 x RJ45 switched
Bus devices max. 16 for CX9020-M930
max. 32 for CX50x0-M930
max. 64 for CX51x0-M930
max. 64 for CX20xx-M930
Properties RTClass1
Optional interface B930
Technical data B930
Fieldbus Profinet RT device
Data transfer rate 100 Mbaud
Bus interface 2 x RJ45 switched
Extendable process image 1 virtual slave in addition
max. process image 2 slaves x (1440 bytes in / 1440 bytes out)
Properties RTClass1

Connection and cabling
CXxxxx-M930/B930 11Version: 1.1
3 Connection and cabling
3.1 PROFINET connection
The latest generation of Embedded PCs can be ordered with the optional PROFINET interface (M930/B930).
Both Ethernet interfaces are switched and dependent on each other. The optional interface X300 is identified
as X300 on the devices and has as black border to identify it.
In a PROFINET slave the incoming PROFINET signal is connected to the upper port of the X300 interface.
The lower port relays the signal to further PROFINET slave devices.
Assignment of the LAN ports (X300)
PIN Signal Description
1 TD + Transmit +
2 TD - Transmit -
3 RD + Receive +
4 connected reserved
5
6 RD - Receive -
7 connected reserved
8

Connection and cabling
CXxxxx-M930/B93012 Version: 1.1
3.2 Cabling
Transmission standards
10Base5
The transmission medium for 10Base5 consists of a thick coaxial cable ("yellow cable") with a max.
transmission speed of 10Mbaud arranged in a line topology with branches (drops) each of which is
connected to one network device. Because all the devices are in this case connected to a common
transmission medium, it is inevitable that collisions occur often in 10Base5.
10Base2
10Base2 (Cheaper net) is a further development of 10Base5, and has the advantage that the coaxial cable is
cheaper and, being more flexible, is easier to lay. It is possible for several devices to be connected to one
10Base2 cable. It is frequent for branches from a 10Base5 backbone to be implemented in 10Base2.
10BaseT
Describes a twisted pair cable for 10Mbaud. The network here is constructed as a star. It is no longer the
case that every device is attached to the same medium. This means that a broken cable no longer results in
failure of the entire network. The use of switches as star couplers enables collisions to be reduced. Using
full-duplex connections they can even be entirely avoided.
100BaseT
Twisted pair cable for 100MBaud. It is necessary to use a higher cable quality and to employ appropriate
hubs or switches in order to achieve the higher data rate.
10BaseF
The 10BaseF standard describes several optical fiber versions.
Short description of the 10BaseT and 100BaseT cable types
Twisted pair copper cable for star topologies, where the distance between two devices may not exceed 100
meters.
UTP
Unshielded twisted pair
This type of cable belongs to category 3, and is not recommended for use in an industrial environment.
S/UTP
Screened/unshielded twisted pair (screened with copper braid)
Has a general screen of copper braid to reduce influence of external interference. This cable is
recommended for use with Bus Couplers.
FTP
Foiled shielded twisted pair (screened with aluminum foil)
This cable has an outer screen of laminated aluminum and plastic foil.
S/FTP
Screened/foiled-shielded twisted pair (screened with copper braid and aluminum foil)
Has a laminated aluminum screen with a copper braid on top. Such cables can provide up to 70dB reduction
in interference power.

Connection and cabling
CXxxxx-M930/B930 13Version: 1.1
STP
Shielded twisted pair
Describes a cable with an outer screen, without defining the nature of the screen any more closely.
S/STP
Screened/shielded twisted pair (wires are individually screened)
This identification refers to a cable with a screen for each of the two wires as well as an outer shield.
ITP
Industrial Twisted-Pair
The structure is similar to that of S/STP, but, in contrast to S/STP, it has only one pair of conductors.
3.3 Topology
PROFINET
Fig.1: Example for a PROFINET topology.

TwinCAT tabs
CXxxxx-M930/B93014 Version: 1.1
4 TwinCAT tabs
In TwinCAT, information and settings for the PROFINET interface are added under tabs. The main TwinCAT
tabs are described in this section. In addition, the section illustrates how the PROFINET interface is
displayed in the tree view under TwinCAT.
The tree view and the tabs for a PROFINET interface are identical under TwinCAT2 and TwinCAT3.
4.1 Tree view
A PROFINET master and a PROFINET slave are displayed as follows in the tree view:
1
2
3
In this sample the slave was linked to the master. TwinCAT was then scanned for the master, and the master
was added in TwinCAT together with the slave.
No. Description
1 Under the PROFINET master, status messages are listed as input variables
and output variables. The variables can be linked with the PLC and used for
diagnostic purposes (e.g. error codes, counters, etc.).
2 PROFINET slaves are added under the master.
Each PROFINET slave has its own input variables for diagnostic purposes,
which indicate the state of the communication. The process data is
displayed under the API (Application Process Identifier).
3 Further settings for the PROFINET master or slave can be implemented
under the tabs.
Other tabs are displayed, depending on whether the master or slave is
selected in the tree view.

TwinCAT tabs
CXxxxx-M930/B930 15Version: 1.1
A PROFINET slave and the corresponding tabs are shown as follows in the tree view:
1
2
3
No. Description
1 The process data is displayed under the API (Application Process
Identifier). The DAP (Device Access Point) is always attached by default. It
already has fixed properties from the GSDML file, suchas process data,
interface and PortSub modules.
2 Further user-defined process data are attached as additional modules under
the API. Various module types such as Byte, Word, DWord or Real are
available.
3 Further settings for the PROFINET slave can be implemented under the
tabs.
Other tabs are displayed, depending on whether slave or other entries are
selected in the tree view.
When the PLC process image is read, the variables for status messages and the variables under the API
(Application Process Identifier) can be linked with the variables from the PLC program. Double-click on a
variable name in the tree view to open the link dialog. The link variables are identified with a small arrow
icon.
Further information about TwinCAT can be found in the TwinCAT documentation on the Beckhoff website:
www.beckhoff.de

TwinCAT tabs
CXxxxx-M930/B93016 Version: 1.1
4.2 Profinet master
4.2.1 PROFINET
2
3
1
No. Description
1 All the information required for ADS communication with the PROFINET
controller is displayed here.
AMS NetID protocol: This is the NetID via which the PROFINET controller
protocol can be reached via AMS.
AMS PortNo protocol: This is the PortNo via which the PROFINET
controller protocol can be reached via AMS.
AMS NetID server: This is the NetID to which certain AMS messages are
relayed by the PROFINET driver.
AMS PortNo server: This is the PortNo to which certain AMS messages
are relayed by the PROFINET driver
2 The Topology button opens a window in which you can compare the online
topology with the offline topology.
3 You can use the Scan PNIO Devices button to search for further
PROFINET slaves. This function is only available in CONFIG mode.
After the scan for further PROFINET slaves a further window appears in
which all the devices that were found are displayed, along with additional
settings.

TwinCAT tabs
CXxxxx-M930/B930 17Version: 1.1
4.2.2 Sync Task
The PROFINET controller protocol must always be linked with a task. The set cycle time is also used for
processing the protocol. In theory, the controller can also be processed via a PLC or NC task. However, if a
PLC project, for example, is stopped (e.g. by restart or debugging), this results in the PROFINET part also
being stopped. In order to avoid such a side effect is it advisable to always create a free-running SyncTask.
1
3
2
No. Description
1 This option is enabled by default. In this case the Sync task is triggered via
the variable mapping. If several tasks are linked to the PROFINET adapter,
the task with the higher priority is always used as the Sync task.
Pay attention to the Sync task. The Sync task must correspond to the value
x2, i.e. 1 ms, 2 ms, 4 ms, 8 ms, 16 ms etc. The Sync task of the PROFINET
controller must not be set under the Sync task of a PROFINET device.
Example: If the PROFINET device operates with a 4 ms Sync task, the
Sync task of the PROFINET controller may be set to 4 ms, 8 ms, 16 ms,
etc. In this case cycle times of 1 ms or 2 ms may not be used.
2 If the Sync task is set via the mapping, note that a breakpoint results in
interruption of the task, which also affects the PROFINET communication.
You can override this behavior by using the Special Sync Task option. The
PROFINET device then uses a Sync task that runs independent of the PLC
task.
3 At this point the name, cycle time and priority for the cycle time can be set.

TwinCAT tabs
CXxxxx-M930/B93018 Version: 1.1
4.2.3 Settings
The Settings tab contains settings that directly concern the PROFINET controller.
1
2
3
4
No. Description
1 At this point you can configure the network settings for PROFINET. By
default, values for IP address, subnet and gateway are already entered, but
you can change these.
Press the Set IP settings button to apply your changes.
The selection of the address range need not correspond to the network card
settings. The PROFINET communication spreads its own net, which can be
selected here. If you change the subnet or gateway, the settings are also
applied to configured devices.
2 At this point you can set the name for the PROFINET controller. A name is
entered by default.
Press the Set System name button to apply your changes.
3 At this point you can read the VendorID and DeviceID of the controller. You
can also set the server and client UDP ports here. However, the default
settings are adequate in most cases.
4 If you activate this option, a new PROFINET controller is automatically
assigned the name of the previous controller when a device is replaced.
This allows you to easily replace a PROFINET controller in the event of a
fault.

TwinCAT tabs
CXxxxx-M930/B930 19Version: 1.1
4.3 Profinet slave
4.3.1 PROFINET
2
1
No. Description
1 All the information required for ADS communication with the PROFINET
device is displayed here.
AMS NetID protocol: This is the NetID through which the PROFINET
device protocol can be reached via AMS.
AMS PortNo protocol: This is the PortNo through which the PROFINET
device protocol can be reached via AMS.
AMS NetID server: This is the NetID to which certain AMS messages are
relayed by the PROFINET driver.
AMS PortNo server: This is the PortNo to which certain AMS messages
are relayed by the PROFINET driver
2 This button opens a window in which you can compare the online topology
with the offline topology.

TwinCAT tabs
CXxxxx-M930/B93020 Version: 1.1
4.3.2 Sync Task
The SyncTask triggers the PROFINET task and thus the speed with which the PROFINET communication
operates.
Pay attention to the system utilization rate of your Embedded PCs. The shorter the PROFINET cycle time is,
the higher the total system utilization rate will be. A very high system utilization rate can lead to an ADS
connection no longer being triggered often enough and this connection may be interrupted.
1
2
3
No. Description
1 This option is enabled by default. In this case the Sync task is triggered via
the variable mapping. If several tasks are linked to the PROFINET adapter,
the task with the higher priority is always used as the Sync task.
Pay attention to the Sync task. The Sync task must correspond to the value
x2, i.e. 1ms, 2ms, 4ms, 8ms, 16ms etc. The Sync task of the PROFINET
controller must not be set under the Sync task of a PROFINET device.
Example: If the PROFINET device operates with a 4ms Sync task, the
Sync task of the PROFINET controller may be set to 4ms, 8ms, 16ms,
etc. In this case cycle times of 1ms or 2ms may not be used.
2 If the Sync task is set via the mapping, note that a breakpoint results in
interruption of the task, which also affects the PROFINET communication.
You can override this behavior by using the Special Sync Task option. The
PROFINET device then uses a Sync task that runs independent of the PLC
task.
3 At this point the name, cycle time and priority for the cycle time can be set.