Professional Documents
Culture Documents
sd6
sd6
en 11/2015 ID 442710.00
3.1 Installation PN6 is installed on the upper slot of the drive controller.
You need:
Installation work is only admissible when no voltage is present. Observe the 5
safety rules. • A Torx screwdriver TX10.
• The cover and screw included with the communication module.
Note the minimum open areas specified in the technical data during installation
to prevent the drive controller from overheating.
Protect the device against falling parts (bits or strands of wire, pieces of metal, Installation of the communication module
etc.) during installation or other work in the control cabinet. Parts with
conductive properties may result in a short circuit or device failure within the 1. Loosen the fastening screw for the dummy cover on the top of the drive
drive controller. controller.
Remove the additional covers before commissioning so that the device will not 2. Push the communication module into the drive controller on the guide
overheat. rails.
3. Push the module in so that the pin contacts are pushed into the female
WARNING! connector strip.
Danger of personal injury and material damage due to electric shock! 4. Insert the tips of the cover included with the communication module into
Always switch off all power supply voltage before working on the drive the recess in the front at an angle.
controller! Note that the discharge time of the DC link capacitors is up to 5 5. Set the cover down on the drive controller so that the tips are resting under
minutes. You can only determine the absence of voltage after this time the edge.
period. 6. Fasten the cover with the two screws.
10. Confirm with OK. 1. Mark the relevant drive controller in the project tree and click in the Wizard
section on the 1st projected axis > STOBER Drive Based application.
The application wizard opens.
2. Operation modes section:
select the required operation mode and click on Set fieldbus mapping for
operation mode.
The Set fieldbus mapping for operation mode window opens.
The most important process data for the selected operation mode is
preassigned for each transmission direction.
3. If you want to define additional process data in advance, select it for the
respective Rx and Tx channel and confirm your configuration with OK.
The process data is transferred to the Mapping dialog PROFINET >
RxPZD and PROFINET >TxPZD.
2. You can transfer a maximum of 18 parameter values via RxPZD to the 5.1.4.2 Adapt TxPZD
drive controller. Requirement:
Check the default settings and/or configure the process data according to We recommend selecting an operation mode before this step and loading the
your requirements. preassigned TxPZD via the associated "Fieldbus mapping" function in the list
A90[0] – A90[5], of the data to be transferred.
Parameter values that are transferred to the
A91[0] – A91[5], controller. Information
A92[0] – A92[5] The respective position (A90 – A92, 1st – 6th) Note that the maximum total length of the parameters to be
1st – 6th mapped has information about the associated transferred is configured in the controller.
parameter transmission order.
1. Mark the relevant drive controller in the project tree and click in the Wizard
Resulting length Total length of the data to be transferred. This must zone on the 1st projected axis > PROFINET TxPZD.
not the exceed the value saved in the controller The PROFINET TxPZD wizard opens.
(max. 72 byte). If necessary, change the type or 2. You can transfer a maximum of 18 parameter values via TxPZD to the
number of parameter values to be transferred. controller.
Check the default settings and/or configure the process data according to
your requirements.
Requirement: 1. Mark the drive controller concerned in the project tree and click on
the IGB interfaces of the drive controller are connected to each other and the Wizards > Axis > Save values.
control board is switched on (24VDC supply). The storage wizard opens.
2. Save the project configuration in the drive controller by setting A00[0] Start
1. Mark the module in the project tree under which you have recorded the
to 1: active.
drive controller concerned and click on Setting up a connection.
3. The configuration changes are only effective when the drive controller is
The connection window opens.
restarted. Click on Restart.
2. Direct connection > Column IGB IP address tab:
The restart wizard opens.
Mark the IP address you want to connect with and confirm with OK.
4. Restart the drive controller by setting A09[0] Start to 1: Active.
The assignment window opens.
5. Reestablish a connection to the drive controller.
3. For each drive controller, assign the Send to drive controller action in the
Method column, assign a drive controller in the In project column and 6. Transfer and save the project configuration to all drive controllers of your
confirm the assignment with Start. bus system.
5.2 TIA Portal: Set up PROFINET network Read IP address and subnet masks of the IO controller
A PROFINET IO system generally consists of a PROFINET IO controller and
1. Start the TIA Portal and click on Online & Diagnostics > Accessible
assigned PROFINET IO devices.
devices.
The Siemens TIA Portal offers you the option to map your real PROFINET IO
The Accessible devices window opens.
hardware environment, address all devices, parameterize the IO devices and
configure the data exchange. Type of the PG/PC Select PN/IE.
Always comply with the following sequence of steps when mapping your interface
PROFINET IO system. PG/PC Select the network connection that you use.
Note that the infrastructure of your PROFINET IO system is already set up, i.e. interface
all PROFINET system subscribers must be physically in the network. You have 2. Click on Start search.
also projected all IO devices via the DriveControlSuite and transferred the
If an online connection can be set up, all networked subscribers of
project configuration on the drive controller.
your physical PROFINET system together with the specification of the
respective device type as well as the associated IP and MAC
addresses are listed.
5.2.1 Check network addresses
Before staring your project configuration, check whether the network Read IP address and subnet masks of the IO supervisor
addresses of the IO controller and IO supervisor match each other. To be able
to establish a connection, both subscribers must belong to the same subnet. 3. IO supervisor: Click on Control Panel > Network and Sharing Center >
View your active networks in the MS Windows system environment.
Requirement: 4. Connections section: click on the relevant LAN connection.
You have already set up the infrastructure of your PROFINET IO system,
The Status of LAN connection window opens.
i.e. all PROFINET system subscribers are physically in the network.
5. General tab > Connection section: call up the Network connection details
via Details.
6. Compare the specified IP address and subnet masks of the IO supervisor
with the IO controller. Both subscribers must belong to the same subnet.
3. Hardware catalog: Select Other field devices > PROFINET IO > Drives >
STÖBER ANTRIEBSTECHNIK GmbH & Co. KG > STOBER 6th
generation drives > PN6A.
4. Drag & drop the module in the network view.
The IO device is included in your project.
5. Repeat steps 3 and 4 for all IO devices that exist in your physical
PROFINET IO system.
Requirement:
5.2.4 Configure IO controller You are in the TIA network view. The hardware catalog is open.
If necessary, you can change the preconfigured IP address and subnet
address of the IO controller. 1. Double click on the IO device of your IO system.
You will switch to the associated device view.
Requirement:
You are in the TIA network view. Define transfer volume
1. Double click on the IO controller of your IO-System.
2. Hardware catalog: Click on Catalog > Module.
You will switch to the associated device view.
You have two categories available that define the general data volume
2. Click on the General tab > General > PROFINET interface > Ethernet to be transferred.
addresses in the device properties.
3. Mark the required module and drag & drop it in the Device overview tab >
3. IP protocol section: Module column.
Use IP protocol Activate this option if not activated as the default. The input and output addresses of the IO device are generated
Set IP address in the If not active by default, activate this option and automatically.
project change the IP and subnet addresses of the IO
controller. Assign device names
7. [Optional] Section PROFINET interface > Ethernet addresses > IP Configure IO cycle
protocol:
11. Section Advanced options > Real-time settings > IO cycle > Update time:
Use IP protocol Activate this option if not activated as the default.
Automatic If the time in which the controller and device
Set IP address in the If not active by default, activate this option and
exchange IO-data should be automatically
project change the IP address of the IO device. calculated, activate this option.
8. Device view: Mark the relevant IO device and right click on Assign device Can be set If you want to calculate the update time yourself,
name. activate this option and specify the required time
The Assign PROFINET device name window opens. (units: milliseconds).
9. Click on Update list. Adapt update time If the relationship between the update time and send
when send clock time should permanently remain constant, activate
All IO devices of the defined subnet are listed together with the
changes this option.
specification of the respective device type as well as the associated IP
and MAC address. 12. Section Advanced options > Real-time settings > IO cycle > Response
10. Mark the IO device that you want to name and click on Assign name. monitoring time:
You can test your selection in advance by verifying the selected drive
Accepted update Check the default setting and change the number of
controller via "Flash LED" or via its own MAC address (read A279 PN
cycles without IO- permitted cycles without data transfer if necessary.
MAC addresses parameter).
Data
Response The response monitoring time is automatically
monitoring time calculated based on the accepted cycles; it must not
exceed 1.92 seconds.
Requirement: Requirement:
You have mapped and parameterized all subscribers of your physical You have transferred the project configuration onto the IO controller.
PROFINET IO system in your TIA project.
1. Project tree > Devices tab: open the folder of the relevant IO controller
1. Project tree > Devices tab: Mark the folder with the IO controller that you (e.g. PLC_1 [CPU 1513-1 PN]) > Online & Diagnostics > Online accesses.
selected (e.g. PLC_1 [CPU 1513-1 PN]). You will switch to the associated device view.
2. Click on Online > Download to device in the menu bar. 2. Verify the active IO controller and click on Go online.
The Extended download to device window opens. An online connection to the selected IO controller is established.
3. Section Compatible devices in target subnet: click on Start search. 3. Click on Diagnostics > Diagnostics buffer.
All IO controllers of the defined subnet are listed. 4. Events section:
4. Mark the IO controller where you want to save the project configuration the diagnostics buffer is part of the system memory of the IO controller.
and click on Load. Any error messages are output here. If no error message is present, the
If there are several I controllers in your subnet, you can test your selection communication to your PROFINET IO system is correct.
in advance by verifying the selected controller via "Flash LED". The connection between IO controllers and IO devices is projected
and a data exchange is possible.
1. Project tree > Devices tab: open the folder of the relevant IO controller
(e.g. PLC_1 [CPU 1513-1 PN]) > Program blocks.
2. Select the block in which you want to project the acyclic communication.
3. Instructions > Extended instructions > section Distributed I/O:
program the data exchange via the WRREC and RDREC function blocks.
6 More about PROFINET? Real-time data has a higher priority than standard TCP/IP data – it is assigned
priority 7 (Network Control). RT data is always preferentially handled by a
The following chapter summarizes the important terms, services and switch.
relationships concerning PROFINET.
Cyclic data as well as event-controlled messages are generally transferred via
the RT protocol.
6.1 PROFINET
PROFINET is the open standard for automation from Siemens that has been 6.2 Device classes and device addressing
developed in co-operation with the PROFIBUS user organization.
PROFINET distinguishes between various device classes and uses device
PROFINET is based on Ethernet TCP/IP – and is regarded as a further names for addressing the devices in the network.
development of PROFIBUS for applications where fast data communication via
Ethernet is essential in combination with industrial IT functions. 6.2.1 Device classes
PROFINET is standardized to IEC 61158 and IEC 61784. PROFINET uses the PROFIdrive distinguishes between the following device classes for PROFINET
Ethernet protocol IEEE 802.3 for the lower transfer levels, special protocols for IO.
real-time transfer as well as TCP/IP for network management and the transfer
of diagnostics data and alarms. IO supervisor
IT data such as statistics, programs and websites are transferred via HTTP and An IO supervisor is typically an engineering and diagnostics software that can
FTP. access all process and configuration data. A Supervisor is generally only
temporarily included in the network.
PROFINET IO
PROFINET IO is designed for the fast exchange of I/O data. IO controller
However PROFINET Ethernet communication is not capable of real-time An IO controller controls data communication, i.e. it receives process data and
operation. For this reason, PROFINET offers special real-time extensions. event-controlled messages and processes them. A programmable logic
controller generally takes the role of the IO controller (PLC, e.g. SIMATIC S7-
PROFINET IO – Real-Time (RT) 1500).
The RT protocol is the basis for data exchange for PROFINET IO, i.e.
PROFINET IO dispenses with the TCP/IP and UDP/IP transfer protocols IO device
entirely. An IO device is typically a decentrally arranged I/O field device (e.g. a SD6
RT uses the individual MAC addresses of the respective manufacturer for each drive controller) that is assigned to at least one IO controller. An IO device
device for addressing subscribers. Received telegrams can be processed very transfers process and configuration data as well as alarms. It generally
quickly; the response times are in the millisecond range. consists of modules that include individual input and output signals of the
respective process.
The stated device classes exchange parameter and configuration data via the Subnets and subnet masks - Value range
standard communication channel, process data and alarms via the real-time The formation of subnets is used to provide autonomous networks with their
channel (process data channel). own address range; each IP address is divided into a network and host
address. The subnet mask determines the place where this division occurs.
The subnet mask consists of 4 decimal numbers within the value range 0 – 255
6.2.2 Device addressing separated by a period – in the same way as the IP address.
All PROFINET IO subscribers are based on the Industrial Ethernet-Standard,
i.e. they require a unique IP address for data exchange. Conventions for device names
Observe the following conventions for the definition of device names:
To be able to address IO devices in the PROFINET IO system, they require a
• The device name must be limited to a maximum of 240 characters. Letter,
unique device name: only after the assignment of a name can an IO device be
numbers, periods and hyphens are allowed.
addressed by an IO controller.
• A component of the name, i.e. a character sequence between 2 periods,
In the course of the hardware project configuration in the TIA Portal, the IO
may have a maximum of 63 characters.
devices receive device names that are transferred to the IO controller. These
• Special characters such as umlauts, brackets, question marks, slashes,
are assigned corresponding IP addresses when starting up the IO devices.
space characters, etc. are not allowed.
For a device type from the 6th generation of STOBER drive controllers, the
• The device name must not start with a number.
stated values are written in the following parameters:
• The device name must not start with the characters "-" or "." and also must
• A274 PN IP address
not end with these.
• A275 PN Subnet mask
• The device name must not have the form n.n.n.n (n = 0...999).
• A276 PN Gateway
• The device name must not start with the character sequence "port-xyz-" (x,
The relevant STOBER-specific MAC address can be read in the drive controller
y, z = 0...9).
via parameter A279 PN MAC addresses.
• An underscore is a prohibited character.
Further information for PROFINET networking
MAC address
A MAC address consists of a fixed and a variable part. The fixed part identifies
the manufacturer and the variable part distinguishes between the individual
Ethernet subscribers and must have a unique global assignment.
6.3 PROFIdrive device profile PROFINET distinguishes between the following channels:
• IO Data CR
PROFIdrive is a profile for electric drives that was developed with the aim of
for the cyclic process data exchange (PZD channel),
standardizing the PROFIBUS and PROFINET interface across manufacturers:
• Record Data CR
data flows, telegrams, standard configurations and options to access
for the acyclic parameter transfer (PKW channel),
parameters or diagnostic data are specified in detail in PROFIdrive.
• Alarm CR
Devices from different manufactures obtain an extremely unique
for the transfer of alarms.
characterization via PROFIdrive and feature compatible behavior.
The length and structure of the process data are defined as part of the project E.. Display values Display for device and application
configuration. Currently 18 parameter values with a maximum total length of 72 F.. Terminals Analog inputs/outputs,
byte can be exchanged between controller and device for each transmission binary inputs/outputs, brake
direction. G.. Technology Depends on the application, for example
synchronous motion
6.4.3 PKW channel H.. Encoder Encoder
As well as the process data, there is different parameterization or configuration I.. Motion Settings for all movements
data that is transferred between the IO controllers and IO devices during
P.. Customer-specific For programming only (optional)
ongoing operation. This data is regarded as time-uncritical in the same as the
parameters
unique events.
Q.. Customer-specific For programming only (optional)
Parameters of a drive controller with line number 0 to 511 can be accessed as
parameters, instance-
communication objects via the PKW channel.
dependent
R.. Production data Production data for the drive controller
T.. Scope Scope parameters
U.. Protection functions Parameterization of events
Z.. Fault counter Fault counter for events
The element subdivides a parameter into subfunctions. The functions are controlled via the SIMATIC function blocks WRREC and
RDREC.
The last place identifies the individual bits, for example in control words.
6.4.3.2.1 WRREC and RDREC
Calculate parameters
WRREC and RDREC are special "instructions", i.e. code blocks that contain a
All STOBER-specific drive controllers are sorted as communication objects in
certain number of elements in a clearly defined sequence.
the parameter number range 2000hex – 5FFFhex.
A parameter number (PNU), an axis or a subindex is specified as follows. Both blocks are asynchronously operating instructions to either transfer a
"RECORD" data record to an address defined in "ID" (WRREC) or to read a
Parameter number data record from the address defined in "ID" (RDREC).
Calculation formula:
PNUdec = 8192 + 512 * group number + line number
The PNU must generally be converted from decimal to hexadecimal for use in
the IO controller.
The following numbers apply for groups:
A B C D E F G H I J K L M
0 1 2 3 4 5 6 7 8 9 10 11 12
N O P Q R S T U V W X Y Z
13 14 15 16 17 18 19 20 21 22 23 24 25
6.4.3.2.3 RECORD data record - Header "Request" and "Response" Element Data type Value, V.-range Meaning
Parameter values are generally transferred via the header of the RECORD
Subindex Word 0 – 3E80hex 0 = Parameters that are not
data record. Depending on whether this is a request or response header, the
a record or array
headers are structured differently.
Format Byte 08hex Transfer format: floating
Header "Request" point
A Request header has the following elements in the specified sequence. 41hex Transfer format: byte
Element Data type Value, V.-range Meaning 42hex Transfer format: word
Request_ Byte 00hex – FFhex Freely selectable number for 43hex Transfer format:
reference a request double word
02hex Access to parameter with a value outside of the limit BAhex Parameter service: clash with other values
values C0hex Parameter service: error in pre-read function
03hex Access to unavailable subindex (array parameter) C1hex Parameter service: error in post-write function, value has
0Bhex User level not reached already arrived
2 5
If the result is positive, RDREC element "REQ" is deleted and step 7 is
Wait for WRREC
end of send
Wait for RDREC
end of send
activated.
If RDREC reports the "Communication partner not ready" error, step 5 is
Communication
End of send reactivated.
partner not ready
If another error occurs, RDREC element "REQ" is deleted, an internal error
3 4
bit is set and step 7 is activated.
Check WRREC Send successful Send
result RDREC • 7: Check for errors or output value
The existence of internal error bits is checked.
If an error bit is present, the "ERROR" element is set, the "BUSY" element
Note that a "Read parameter value" request always starts with a write task that
contains the parameter values to be read.
6.5 Monitoring and diagnostics After an error has occurred, the defined response monitoring time first elapses
than the timeout defined in A109 starts.
6.5.1 Connection monitoring When this time elapses, the drive controller changes to the Fault device state
To prevent the drive reacting in an undesirable manner when the PROFINET and shows the 52:Communication event with the 4:PZD timeout cause on the
connection is interrupted (cable break, etc.), the arrival of the cyclic process display.
data should be monitored. Note that the event from this time is triggered cyclically until the cause is
rectified. The cycle does not depend on the time of the acknowledgement.
PROFINET provides a Response monitoring time for the connection
monitoring that defines the so-called IO cycle together with the Update time.
The update time determines the time interval in which the data is transferred
from an IO controller to the relevant IO device (outputs) and vice versa (inputs).
6.5.2 States of the bus communication
Among other things, it depends on the data volume to be transferred and is The PN6 communication module is equipped with a green RUN LED and a red
generally automatically calculated in the TIA Portal for each IO device (see ERROR LED that visualize the connection to the controller and the state of the
5.2.4 Configure IO controller). data transfer.
The response monitoring time corresponds to the number of permitted cycles In addition each of the two RJ-45 sockets has two integrated diodes – Link
without data transfer. (green) and Act (orange) – that report the connection and communication
In addition to the response monitoring time, the A109 PZD timeout parameter status as viewed by the hardware.
can be activated in the DriveControlSuite. If the timeout is activated, the drive Detailed information about the state of the bus communication can be taken
controller behaves in the event of an error as follows: from the A271 PN state or A278[5] – A278[8] PN diagnostics parameter if
necessary.
Flash, inverse IO controller activated DHCP-Signal-Service ERROR, Act and Link = • Does the SD6 – IO controller connection exist?
(90 % on, 10 % off) off • Is the drive controller correctly parameterized?
• Is the IO controller active and in RUN mode?
Flashing Connection to IO controller exists; data transfer is
• Is the 100 Mbit Full Duplex link detected?
expected
Act = off + Check hardware connection
Off No connection to IO controller
Link and ERROR = on
LEDs – RJ-45
Turkey Taiwan
STOBER Turkey STOBER Branch Office Taiwan
Istanbul Taipei City
Fon +90 212 338 8014 Fon +886 2 2216 3428
sales-turkey@stober.com sales@stober.tw
www.stober.com www.stober.tw
442710.00
24 h Service Hotline +49 7231 5823000