Distributed inverter box, control cabinet for wall or floor mounting (34 pages)
Summary of Contents for Siemens SINAMICS G110M
Page 3
Fundamental safety ___________________ Fieldbuses instructions ___________________ Introduction ___________________ Communication via SINAMICS PROFIBUS and PROFINET Communication via ___________________ EtherNet/IP SINAMICS G120, G120P, G120C, G120D, G110M ___________________ Fieldbuses Communication via RS485 ___________________ Communication over CANopen Function Manual ___________________ Communication via AS-i - only for G110M ___________________ Appendix...
Page 4
Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Table of contents Fundamental safety instructions ......................9 General safety instructions ....................... 9 Industrial security ........................10 Introduction ............................11 Ethernet and PROFINET protocols that are used ..............12 Communication via PROFIBUS and PROFINET ................... 15 PROFIdrive profile ........................15 3.1.1 Cyclic communication ......................
Page 6
Table of contents 3.5.4.1 Configuring the communication using SIMATIC S7 control ........... 73 3.5.4.2 Configuring the communication with a third-party control system ......... 73 3.5.4.3 Installing the GSD ........................73 3.5.5 Setting the address ........................ 74 Select telegram ........................75 Communication via EtherNet/IP ......................
Page 7
Table of contents 5.5.3 Acyclic communication (general parameter access) via BACnet ......... 152 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT........... 154 Communication over CANopen ......................159 Network management (NMT service) ................... 162 SDO services ........................165 6.2.1 Access to SINAMICS parameters via SDO ................165 6.2.2 Access PZD objects via SDO ....................
Page 8
Table of contents A.1.3.2 Cyclic communication with standard telegram 1 via PROFIBUS DP with direct data exchange ..........................228 A.1.3.3 Acyclic communication via DS47 with PROFIBUS or PROFINET ........231 Manuals and technical support .................... 235 A.2.1 Overview of the manuals ..................... 235 A.2.2 Configuring support ......................
Fundamental safety instructions General safety instructions WARNING Risk of death if the safety instructions and remaining risks are not carefully observed If the safety instructions and residual risks are not observed in the associated hardware documentation, accidents involving severe injuries or death can occur. •...
Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept.
Additional fieldbuses for SINAMICS G120P ● BACnet MS/TP ● P1 Additional fieldbuses for SINAMICS G110M ● AS-Interface Communication with the control, even when the line voltage is switched off If, in your plant or system, communication with the control system should continue to function even when the line voltage is switched off, then you must externally supply the inverter/Control Unit with 24 V DC.
Introduction 2.1 Ethernet and PROFINET protocols that are used Ethernet and PROFINET protocols that are used The inverter supports the protocols listed in the following tables. The address parameters, the relevant communication layer as well as the communication role and the communication direction are specified for each protocol.
Page 13
Introduction 2.1 Ethernet and PROFINET protocols that are used Table 2- 2 Ethernet/IP protocols Protocol Port Layer Function/description number (2) Link layer (4) Transport layer Implicit mes- 2222 (4) UDP Used for exchanging I/O data. saging This is inactive when delivered. Is activated when selecting Ether- Net/IP.
Page 14
Introduction 2.1 Ethernet and PROFINET protocols that are used Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
The inverter has the following telegrams if you have configured the "Basic positioner" function: ● Standard telegram 7, PZD-2/2 ● Standard telegram 9, PZD-10/5 ● SIEMENS telegram 110, PZD-12/7 ● SIEMENS telegram 111, PZD-12/12 ● Telegram 999, free interconnection These telegrams are described in the "Basic positioner" function manual.
Page 16
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Communication telegrams for speed control The send and receive telegrams of the inverter for closed-loop speed control are structured as follows: Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Page 17
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Abbreviation Explanation Abbreviation Explanation Control word PIST_GLATT Actual active power value, smoothed Status word M_LIM Torque limit NSOLL_A Speed setpoint 16 bit FAULT_COD Fault number NSOLL_B Speed setpoint 32 bit WARN_COD Alarm number NIST_A Speed actual value 16 bit MELD_NAMU...
Page 18
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Image 3-2 Interconnection of the receive words The telegrams use - with the exception of telegram 999 (free interconnection) - the word-by- word transfer of send and receive data (r2050/p2051). If you require an individual telegram for your application (e.g. for transferring double words), you can adapt one of the predefined telegrams using parameters p0922 and p2079.
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.1.1 Assigning control and status words Assigning control and status words Assigning control and status of words is specified in part by the definitions in the PROFIdrive profile, Version 4.1 for the "Closed-loop speed control" operating mode; the other part is assigned depending on the particular manufacturer.
Page 20
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Control word 1 (STW1) Significance Explanation Signal inter- connection Telegram 20 All other tele- in the inver- grams 0 = OFF1 The motor brakes with the ramp-down time p0840[0] = p1121 of the ramp-function generator. The r2090.0 inverter switches off the motor at standstill.
Page 21
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Significance Explanation Signal inter- connection Telegram 20 All other tele- in the inver- grams 1 = MOP down Reduce the setpoint saved in the motorized p1036[0] = potentiometer. r2090.14 CDS bit 0 Reserved Changes over between settings for different p0810 =...
Page 22
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Status word 1 (ZSW1) Significance Comments Signal inter- connection Telegram 20 All other tele- in the inver- grams 1 = Ready to start Power supply switched on; electronics initiali- p2080[0] = zed; pulses locked. r0899.0 1 = Ready Motor is switched on (ON/OFF1 = 1), no fault...
Page 23
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Control and status word 2 Control word 2 is preassigned as follows: ● Bits 0 … 11 manufacturer-specific ● Bits 12 … 15 corresponding to the PROFIdrive profile Status word 2 is preassigned as follows: ●...
Page 24
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Status word 2 (ZSW2) Bit Significance Signal interconnection in the inverter 1 = DDS active bit 0 p2081[0] = r0051.0 1 = DDS active bit 1 p2081[1] = r0051.1 Reserved Reserved Reserved 1 = Alarm class bit 0 p2081[5] = r2139.11 1 = alarm class bit 1...
Page 25
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Control and status word 3 Control word 3 is preassigned as follows: ● Bits 0 … 15 manufacturer-specific Status word 3 is preassigned as follows: ● Bits 0 … 15 manufacturer-specific Control word 3 (STW3) Bit Significance Explanation Signal interconnection...
Page 26
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Status word 3 (ZSW3) Significance Description Signal inter- connection in the inverter 1 = DC braking active p2051[3] = r0053 1 = |n_act | > p1226 Absolute current speed > stationary state detection 1 = |n_act | >...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.1.2 NAMUR message word Fault word according to the VIK-NAMUR definition (MELD_NAMUR) Table 3- 1 Fault word according to the VIK-NAMUR definition and interconnection with parameters in the inverter Bit Significance P no. 1 = Control Unit signals a fault p2051[5] = r3113 1 = line fault: Phase failure or inadmissible voltage...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.1.3 Control and status word, encoder Telegrams 3 and 4 allow the higher-level control system to directly access the encoder. Direct access is necessary, if the higher-level control is responsible for the closed-loop position control for the drive.
Page 29
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Status word encoder (G1_ZSW and G2_ZSW) Bit Significa- Explanation Signal interconnection in the inverter Bit 7 = 0 Bit 7 = 1 Function 1 1 = search for reference 1 = flying referencing to the rising edge of Telegram 3: cam 1 is active reference cam 1 is active...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.1.4 Position actual value of the encoder G1_XIST1 and G2_XIST1 In the factory setting, the inverter transfers the encoder position actual value with a fine resolution of 11 bits to the higher-level control system. Image 3-3 G1_XIST1 and G2_XIST1 The transferred encoder signal has the following properties:...
Page 31
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile The inverter transfers the position values in the same format (encoder pulse number and fine resolution) the same as G1_XIST1 and G2_XIST1. Table 3- 2 Fault code Explanation Possible cause Encoder fault One or more encoder faults.
350: SIEMENS telegram 350, PZD-4/4 352: SIEMENS telegram 352, PZD-6/6 353: SIEMENS telegram 353, PZD-2/2, PKW-4/4 354: SIEMENS telegram 354, PZD-6/6, PKW-4/4 The following values apply if you have enabled the "Basic positioner" function in the inverter: Standard telegram 7, PZD-2/2...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Freely selecting the signal interconnection of the telegram The signals in the telegram can be freely interconnected. Procedure Proceed as follows to change the signal interconnection of a telegram: 1. Using STARTER or an operator panel, set parameter p0922 = 999. 2.
Page 34
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Request and response IDs Bits 12 … 15 of the 1st word of the parameter channel contain the request and response identifier. Table 3- 3 Request identifiers, control → inverter Request identi- Description Response identifier fier...
Page 35
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Table 3- 5 Error numbers for response identifier 7 Description 00 hex Illegal parameter number (access to a parameter that does not exist) 01 hex Parameter value cannot be changed (change request for a parameter value that cannot be changed) 02 hex Lower or upper value limit exceeded (change request with a value outside the value limits)
Page 36
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Offset and page index of the parameter numbers Parameter numbers < 2000 PNU = parameter number. Write the parameter number into the PNU (PKE bit 10 ... 0). Parameter numbers ≥ 2000 PNU = parameter number - offset.
Page 37
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Telegram examples Read request: Read out serial number of the Power Module (p7841[2]) To obtain the value of the indexed parameter p7841, you must fill the telegram of the parameter channel with the following data: ●...
Page 38
● PWE2, bit 0 … 9: = 2 hex (index of parameter (DI 2 = 2)) Image 3-7 Telegram, to assign DI 2 with ON/OFF1 "Reading and writing parameters" application example Further information is provided in the Internet: Application examples (https://support.industry.siemens.com/cs/ww/en/view/29157692) Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.1.7 Slave-to-slave communication "Direct data exchange" is sometimes called "slave-to-slave communication" or "data exchange broadcast". Here, slaves exchange data without any direct involvement of the master. Example: An inverter uses the actual speed value of another inverter as its speed setpoint. Definitions ●...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.2 Acyclic communication The inverter supports the following types of acyclic communication: ● For PROFIBUS: acyclic communication via data set 47 ● For PROFINET: acyclic communication via B02E hex and B02F hex The maximum data length per request is 240 bytes.
Page 41
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Table 3- 9 Inverter response to a read request Data block Byte n Bytes n + 1 Header Reference (identical to a read request) 01 hex: Inverter has executed the read requ- est.
Page 42
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Changing parameter values Acyclic communication via DS47 with PROFIBUS or PROFINET (Page 231). Table 3- 10 Request to change parameters Data block Byte n Bytes n + 1 Header Reference 00 hex ... FF hex 02 hex: Change request 01 hex ...
Page 43
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Table 3- 12 Response if the inverter was not able to completely execute the change request Data block Byte n Bytes n + 1 Header Reference (identical to a change request) 82 hex: (Inverter was not able to completely execute the write request) 01 hex (ID of drive objects, at G120 al- Number of parameters (identical to a change...
Page 44
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Error Meaning value 1 18 hex Number of values not consistent (number of values of the parameter data to not match the number of elements in the parameter address) 19 hex Drive object does not exist (access to a drive object that does not exist) 20 hex Parameter text cannot be changed 21 hex...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.3 Diagnostics channels The inverters provide the diagnostics standardized for PROFIBUS and PROFINET. This means that it is possible to directly output faults and alarms at an HMI (control system screen). Here, PROFINET offers more functions than PROFIBUS ●...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile 3.1.3.1 Diagnostics with PROFINET PROFINET uses the channel diagnostics to transfer PROFIdrive message classes. 9000 hex Hardware/software error 900A hex Position/speed actual value incorrect or not available 9001 hex Network fault 900B hex Internal (DRIVE-CLiQ) communication error 9002 hex Supply voltage fault...
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Reading out diagnostics data The control requests the diagnostics data from the inverter using "Read data set", e.g. using a read record with index 800C hex. The following rules apply: ● 1 Message block (=ChannelDiagnosisData) if (one or several) faults of the same message class are detected at the inverter ●...
Page 48
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Note Precondition for diagnostics via PROFIBUS The master must operate in the DPV1 mode for diagnostics via Profibus. Default diagnostics The following values are decisive for the diagnostics: Ext_Diag: Group signal for diagnostics in the slave: •...
Page 49
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Status messages, module status For G120, independent of the status, for all slots “00” is always output, i.e. valid user data. Channel-related data Undervoltage Motor overload Overvoltage Commun. with controller faulted Error Safety monit.
Page 50
Communication via PROFIBUS and PROFINET 3.1 PROFIdrive profile Diagnostics alarm with DS0 / DS1 Alarm specifier Module fault 1: Fault is active and the slot is not OK 0: No fault is active 2: Fault is resolved and the slot is OK 1: Fault is active 3: Fault is resolved and the slot is not OK Channel fault present...
Communication via PROFIBUS and PROFINET 3.3 S7 communication S7 communication S7 communication allows the following: ● The inverter is controlled from a SIMATIC panel, also without control system by directly accessing the inverter via PROFIBUS or PROFINET. ● Remote maintenance by accessing the inverter with STARTER or Startdrive across network boundaries.
Page 53
Communication via PROFIBUS and PROFINET 3.3 S7 communication Settings in the inverter Procedure To adjust the settings in the inverter, proceed as follows: 1. Make the following settings and releases so that the inverter can accept commands from the panel: –...
Page 54
Communication via PROFIBUS and PROFINET 3.3 S7 communication Settings at the SIMATIC panel Procedure To adjust the settings for the panel, proceed as follows: 1. Configure the connection using WINCCflex – Enter a name for the connection – Set the value in the "Active" column to "On" –...
Page 55
Communication via PROFIBUS and PROFINET 3.3 S7 communication General information for accessing inverter parameters You must create a variable with the following structure for each parameter that you want to display or change using the SIMATIC panel: DBX DBY Z ●...
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET Communication via PROFINET You can either communicate via Ethernet using the inverter, or integrate the inverter in a PROFINET network. The inverter as Ethernet node Image 3-10 The inverter as Ethernet node The inverter in PROFINET IO operation Image 3-11 The inverter in PROFINET IO operation...
Page 57
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET General information about PROFINET You can find general information about PROFINET in the Internet: ● General information about PROFINET: Industrial Communication (http://www.automation.siemens.com/mcms/automation/en/industrial- communications/profinet/Pages/Default.aspx). ● Configuring the functions: PROFINET system description (http://support.automation.siemens.com/WW/view/en/19292127). Fieldbuses...
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET 3.4.1 Inverter with PROFINET interface The pin assignment and the connectors that you require for your inverter are listed in the following tables. You can implement either a ring or line-type topology using the two sockets at the inverter. You only require one of the two sockets at the beginning and end of a line.
RJ45, IP20: 6GK1901-1BB10-2Ax0 Information for assembling the SIMATIC NET Industrial Ethernet FastConnect RF45 plug 180 can be found on the Internet: Assembly instructions for the SIMATIC NET Industrial Ethernet FastConnect RJ45 plug (http://support.automation.siemens.com/WW/view/en/37217116/133300) 3.4.2 Integrating inverters into PROFINET Procedure To connect the inverter to a control via PROFINET, proceed as follows: 1.
● Install the most up to date STARTER version ● Install the GSDML of the inverter using “Tools/Install GSDML file" in HW Config. Configuring the communication using a non-Siemens control 1. Import the device file (GSDML) of the inverter into the engineering tool for your control system.
Page 61
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET Configure communication with STARTER STARTER provides a screen form to set the communication with the control system. Open the dialog screen form "Control_Unit/Communication/Commissioning interface" and activate the "Configure IP interfaces" tab ●...
Set p0804 = 12. The inverter writes the GSDML as zipped file (*.zip) into directory /SIEMENS/SINAMICS/DATA/CFG on the memory card. 2. Unzip the GSDML file to a folder on your computer. 3. Import the GSDML into the configuring tool of your control system.
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET 3.4.4.1 General inverter behavior when in the PROFIenergy energy-saving mode ● When the PROFIenergy energy-saving mode is active, the inverter issues alarm A08800. ● When the PROFIenergy energy-saving mode is active, the inverter does not send any diagnostic alarms.
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET 3.4.4.3 Settings and displays for PROFIenergy in the inverter Pause time ● Minimum pause time: p5602 – When the pause time, which is sent using command "Start_Pause", is equal to or greater than the value in p5602[1], then the inverter goes into the energy-saving mode.
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET 3.4.4.4 Control commands and status queries PROFIenergy control commands ● Start_Pause Dependent on the pause duration, switches into the energy-saving mode. – For p5611.2 = 0, from operating states S1 (switching on inhibited) or S2 (ready to switch on) –...
Page 66
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET ● Get_Measurement_Values The command returns the requested measured value using the measured value ID ● Get_Measurement_Values_with_object_number The command returns the requested measured values using the measured value ID and the object number. The object number corresponds to the drive object ID. Error values Table 3- 16 Error values in the parameter response...
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET 3.4.5 The inverter as Ethernet node As default setting, the inverter is set for PROFINET IO communication. Alternatively, you have the option of integrating the inverter into an Ethernet network via the PROFINET interface.
Page 68
Communication via PROFIBUS and PROFINET 3.4 Communication via PROFINET Additional options of integrating inverters into Ethernet You also have the option of integrating the inverter into Ethernet using Proneta or STEP7 in Ethernet, for example. Here is the example of the "Edit Ethernet station" screen form from Step 7, which you can use to make the required settings.
● Cyclic communication ● Acyclic communication ● Diagnostic alarms General information on PROFIBUS DP can be found in the Internet: ● PROFIBUS information (http://support.automation.siemens.com/WW/view/en/1971286) ● Installation guidelines of the PNO (http://www.profibus.com/downloads/installation-guide/) Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Communication via PROFIBUS and PROFINET 3.5 Communication via PROFIBUS 3.5.1 Inverters with PROFIBUS interface You can find the connectors and the connector assignments of the PROFIBUS DP interface in the following tables. You can implement a line-type topology using the two connectors at the inverter. You can use switches to realize other topologies.
Page 71
Communication via PROFIBUS and PROFINET 3.5 Communication via PROFIBUS Table 3- 18 Connector pin assignments Signal X126 X03, on X04, off (D Sub socket, (M12, IP57) (M12, IP57) IP20) Shield, ground connection RxD/TxD-P, receive and transmit (B/B’) CNTR-P, control signal DGND, reference potential for data (C/C’) VP, supply voltage RxD/TxD-N, receive and transmit (A/A’)
Communication via PROFIBUS and PROFINET 3.5 Communication via PROFIBUS 3.5.2 What do you need for communication via PROFIBUS? Check the communication settings using the following table. If you answer "Yes" to the questions, you have correctly set the communication settings and can control the inverter via the fieldbus.
– or from your inverter. To do this, insert a memory card into the inverter and set p0804 = 12. In this way, you will save the GSD on the memory card as (DPGSD.ZIP) compressed file in the directory /SIEMENS/SINAMICS/DATA/CFG . 2. Unzip the GSDfile in a folder on your computer.
Communication via PROFIBUS and PROFINET 3.5 Communication via PROFIBUS 3.5.5 Setting the address You set the PROFIBUS address of the inverter using the address switch on the Control Unit, in parameter p0918 or in STARTER. In parameter p0918 (factory setting: 126) or in STARTER, you can only set the address, if all address switches are set to "OFF"...
Communication via EtherNet/IP EtherNet/IP is real-time Ethernet, and is mainly used in automation technology. You have the following options of integrating SINAMICS G120 inverters into EtherNet/IP: ● You use the SINAMICS profile ● You use the ODVA AC/DC drive profile ●...
Communication via EtherNet/IP 4.1 Inverters with Ethernet/IP interface Inverters with Ethernet/IP interface The pin assignment and the connectors that you require for your inverter are listed in the following tables. You can implement either a ring or line-type topology using the two sockets at the inverter. You only require one of the two sockets at the beginning and end of a line.
Page 79
RJ45, IP20: 6GK1901-1BB10-2Ax0 Information for assembling the SIMATIC NET Industrial Ethernet FastConnect RF45 plug 180 can be found on the Internet: Assembly instructions for the SIMATIC NET Industrial Ethernet FastConnect RJ45 plug (http://support.automation.siemens.com/WW/view/en/14293080/133300) Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
You have the following options: – Load the EDS file into your control. You can find the EDS file in the Internet: EDS (https://support.industry.siemens.com/cs/ww/de/view/78026217) – If your control does not accept the EDS file, then you must create a generic module in your control: Create generic I/O module (Page 99) You have connected the inverter to the control system via EtherNet/IP.
You set the communication using parameter p8980. You have the following options Communication via the SINAMICS profile The SINAMICS profile is a drive profile for EtherNet/IP defined by Siemens, based on PROFIdrive, and is factory set in the inverters. Setting: p8980 = 0...
Communication via EtherNet/IP 4.4 Configuring communication via EtherNet/IP 4.4.2 Special issues if you wish to use the ODVA AC/DC Drive profile If you change the following parameters using STARTER or an operator panel (IOP/BOP-2), then you must switch off the inverter power supply and switch on again in order that the changes become effective.
Motor Data Object 29 hex Supervisor Object 2A hex Drive Object 32C hex Siemens Drive Object 32D hex Siemens Motor Data Object 91 hex Parameter Object Free Access (DS47) F5 hex TCP/IP Interface Object F6 hex Ethernet Link Object 1) 300 hex...
Page 84
Type Name Value/explanation UINT16 Vendor ID 1251 UINT16 Device Type - ODVA AC Drive 02 hex - Siemens Drive 12 hex UINT16 Product code r0964[1] UINT16 Revision The versions should match the EDS file UINT16 Status See the following table...
Page 85
Communication via EtherNet/IP 4.5 Supported objects Assembly Object, Instance Number: 4 hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 5 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances Table 4- 6...
Page 86
Communication via EtherNet/IP 4.5 Supported objects Table 4- 8 Instance Attribute Service Type Name Value/explanation UINT16 OpenReqs Counters UINT16 OpenFormat Rejects Counters UINT16 OpenResource Counters Rejects UINT16 OpenOther Rejects Counters UINT16 CloseReqs Counters UINT16 CloseFormat Re- Counters jects UINT16 CloseOther Rejects Counters UINT16 ConnTimeouts...
Page 87
Communication via EtherNet/IP 4.5 Supported objects Motor Data Object, Instance Number 28 hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 9 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances...
Page 88
Communication via EtherNet/IP 4.5 Supported objects Supervisor Object, Instance Number: 29 hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 11 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances Table 4- 12...
Page 89
Communication via EtherNet/IP 4.5 Supported objects Drive Object, Instance Number: 2A hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 13 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances Table 4- 14...
Page 90
U/f with independent voltage setpoint Vendor specific mode Closed-loop speed control (without encoder) Closed loop speed control Closed-torque control (without encoder) Torque control Siemens Drive Object, Instance Number: 32C hex Supported services Class Instance • Get Attribute single • Get Attribute single •...
Page 91
Communication via EtherNet/IP 4.5 Supported objects Service Name Value/explanation set, get PID Filter Time Constant p2265 technology controller actual value filter time constant set, get PID D Gain p2274 technology controller differentiation time constant set, get PID P Gain p2280 technology controller proportional gain set, get PID I Gain p2285 technology controller integral time...
Page 92
Communication via EtherNet/IP 4.5 Supported objects Siemens Motor Data Object, Instance Number: 32D hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 17 Class Attribute Service Type Name UINT16 Revision...
Page 93
Communication via EtherNet/IP 4.5 Supported objects Parameter Object, Instance Number: 91 hex Supported services Class Instance • Get Attribute single • Get Attribute single Table 4- 19 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances Table 4- 20 Instance Attribute Service...
Page 94
Communication via EtherNet/IP 4.5 Supported objects TCP/IP Interface Object, Instance Number: F5 hex Supported services Class Instance • Get Attribute all • Get Attribute all • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 21 Class Attribute Service Type...
Page 95
Communication via EtherNet/IP 4.5 Supported objects Link Object, Instance Number: F6 hex Supported services Class Instance • Get Attribute all • Get Attribute all • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 23 Class Attribute Service Type Name...
Page 96
Communication via EtherNet/IP 4.5 Supported objects Service Type Name Value/explanation UINT32 Single Collisions Structure successfully transmitted, precisely one collision UINT32 Multiple Collisions Structure successfully transmitted, several collisi- UINT32 SQE Test Errors Number of SQE errors UINT32 Deferred Transmis- First transmission attempt delayed sions UINT32 Late Collisions...
Page 97
Communication via EtherNet/IP 4.5 Supported objects Parameter Object, Instance Number: 401 hex Supported services Class Instance • Get Attribute single • Get Attribute single • Set Attribute single Table 4- 25 Class Attribute Service Type Name UINT16 Revision UINT16 Max Instance UINT16 Num of Instances Cyclic communication is established via parameter object 401.
4.6 Create generic I/O module Create generic I/O module For certain controllers, you cannot use the EDS file provided by Siemens. In these cases, you must create a generic I/O module in the control system for the cyclic communication. Procedure To do this, proceed as follows: 1.
Communication via EtherNet/IP 4.7 The inverter as an Ethernet station The inverter as an Ethernet station As default setting, the inverter is set for PROFINET IO communication. Alternatively, you have the option of integrating the inverter into an Ethernet network via the PROFINET interface.
Page 101
Communication via EtherNet/IP 4.7 The inverter as an Ethernet station Additional options of integrating inverters into Ethernet You also have the option of integrating the inverter into Ethernet using Proneta or STEP7 in Ethernet, for example. Here is the example of the "Edit Ethernet station" screen form from Step 7, which you can use to make the required settings.
Page 102
Communication via EtherNet/IP 4.7 The inverter as an Ethernet station Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Communication via RS485 5.1 Inverter with RS485 interface Inverter with RS485 interface You can find the connectors and the connector assignments of the RS485 interface in the following tables. Table 5- 2 Assignment table Inverter/Control Unit Connection via X128 X03, in X04, out (IP20) (M12, IP57)
Page 105
Communication via RS485 5.1 Inverter with RS485 interface Table 5- 3 Pin assignment Signal X128 X03, in X04, out (IP20) (M12, IP57) (M12, IP57) Not assigned RS485N, receive and transmit (-) RS485N, receive RS485N, transmit (-) RS485P, receive and transmit (+) RS485P, receive RS485P, transmit (+) 0 V, reference potential...
Communication via RS485 5.2 Integrating inverters into a bus system via the RS485 interface Integrating inverters into a bus system via the RS485 interface Connecting to a network via RS485 Connect the inverter to the fieldbus via the RS485 interface. The RS485 connector has short- circuit proof, isolated pins.
Communication via RS485 5.3 Communication via USS Communication via USS The USS protocol is a serial data link between a master and up to a maximum of 31 slaves. A master is, for example: ● A programmable logic controller (e.g. SIMATIC S7-200) ●...
Communication via RS485 5.3 Communication via USS 3. Set the inverter address. 4. Make additional changes based on the parameters listed in the following section. 5. If you are working with STARTER, backup the settings with This means that you have made the settings for communication via USS. 5.3.1.1 Setting the address You set the bus address of the inverter using the...
Communication via RS485 5.3 Communication via USS 5.3.1.2 Parameters to set communication via USS Fieldbus protocol selection p2030 = 1 (USS) Baud rate p2020 = 8, 38400 bit/s Setting range: 2400 bit/s … 187500 bit/s Fieldbus analog outputs p0791[0 … 1] Parameter to interconnect the analog outputs for control via the fieldbus Fieldbus interface USS PZD number p2022 = 2...
Communication via RS485 5.3 Communication via USS 5.3.2 Telegram structure Overview A USS telegram comprises a series of elements with a defined sequence. Each element contains 11 bits. Image 5-1 Structure of a USS telegram Telegram part Description Start delay / respon- There is always a start and/or response delay between two telegrams.
Communication via RS485 5.3 Communication via USS 5.3.3 User data range of the USS telegram The user data area consists of the following elements: ● Parameter channel (PIV) for writing and reading parameter values ● Process data (PZD) for controlling the drive. Image 5-2 USS telegram - user data structure Parameter channel...
Communication via RS485 5.3 Communication via USS 5.3.4 USS parameter channel Structure of the parameter channel Depending on the setting in p2023, the parameter channel has a fixed length of three or four words, or a variable length, depending on the length of the data to be transferred. 1.
Page 113
Communication via RS485 5.3 Communication via USS Table 5- 5 Response identifiers, inverter → control Response iden- Description tifier No response Transfer parameter value (word) Transfer parameter value (double word) Transfer descriptive element Transfer parameter value (field, word) Transfer parameter value (field, double word) Transfer number of field elements Inverter cannot process the request.
Page 114
Communication via RS485 5.3 Communication via USS Description 6B hex No change access for a closed-loop controller that is enabled. (The operating state of the inverter prevents a parameter change.) 86 hex Write access only for commissioning (p0010 = 15) (operating status of the inverter pre- vents a parameter change) 87 hex Know-how protection active, access locked...
Communication via RS485 5.3 Communication via USS Parameter contents Parameter contents can be parameter values or connector parameters. You require two words for connector parameters. You can find more information on interconnecting connector parameters in the operating instructions of the Control Unit in the section "Interconnecting signals in the inverter".
Page 116
Communication via RS485 5.3 Communication via USS Write request: Changing the automatic restart mode (p1210) Parameter p1210 defines the automatic restart mode: ● PKE, bit 12 … 15 (AK): = 7 (change parameter value (field, word)) ● PKE, bit 0 … 10 (PNU): = 4BA hex (1210 = 4BA hex, no offset, as 1210 < 1999) ●...
Communication via RS485 5.3 Communication via USS 5.3.5 USS process data channel (PZD) Description The process data channel (PZD) contains the following data depending on the transmission direction: ● Control words and setpoints for the slave ● Status words and actual values for the master. Image 5-6 Process data channel The first two words are:...
Communication via RS485 5.3 Communication via USS 5.3.6 Time-out and other errors You require the telegram runtimes in order to set the telegram monitoring. The character runtime is the basis of the telegram runtime: Table 5- 8 Character runtime Baud rate in bit/s Transmission time per bit Character run time (= 11 bits) 9600...
Page 119
Communication via RS485 5.3 Communication via USS The duration of the start delay must at least be as long as the time for two characters and depends on the baud rate. Table 5- 9 Duration of the start delay Baud rate in bit/s Transmission time per character (= 11 bits) Min.
Communication via RS485 5.4 Communication using Modbus RTU Communication using Modbus RTU Overview of communication using Modbus The Modbus protocol is a communication protocol with linear topology based on a master/slave architecture. Modbus offers three transmission modes: ● Modbus ASCII Data in ASCII code.
Communication via RS485 5.4 Communication using Modbus RTU 5.4.1 Basic settings for communication Overview Depending on the particular inverter, you have the following options when setting communication via Modbus RTU: ● Default setting 21 "USS Fieldbus" for all inverters with RS485 interface ●...
Communication via RS485 5.4 Communication using Modbus RTU 5.4.1.1 Setting the address You set the bus address of the inverter using the address switches on the Control Unit, using parameter p2021 with the BOP-2 or in STARTER. Using parameter p2021 (factory setting: 1) or using STARTER, you can only set the address, if all address switches are set to "OFF"...
Communication via RS485 5.4 Communication using Modbus RTU 5.4.1.2 Parameters for Modbus communication settings General settings Fieldbus protocol selection p2030 = 2 (Modbus) Baud rate p2020 = 7, 19200 bit/s Setting range: 4800 bit/s … 187500 bit/s Parity In the factory, the Control Unit is set for controllers with even parity You can adapt the parity at your controller using p2031: ●...
Page 124
Communication via RS485 5.4 Communication using Modbus RTU Interconnecting analog outputs If you set communication via Modbus (p2030 = 2), then the analog outputs of the inverter are internally interconnected with the fieldbus analog outputs: ● p0771[0] = 791[0] ● p0771[1] = 791[1]. The values for p0791[0] and p0791[1] are written via registers 40523 and 40524.
Communication via RS485 5.4 Communication using Modbus RTU 5.4.2 Modbus RTU telegram Description For Modbus, there is precisely one master and up to 247 slaves. The master always starts the communication. The slaves can only transfer data at the request of the master. Slave-to- slave communication is not possible.
Communication via RS485 5.4 Communication using Modbus RTU 5.4.3 Baud rates and mapping tables Permissible baud rates and telegram delay The Modbus RTU telegram requires pauses for the following situations: ● for the start identifier ● for separating the individual frames ●...
Page 127
Communication via RS485 5.4 Communication using Modbus RTU The process data are transferred into the register range from 40100 up to 40111. Note R"; "W"; "R/W" in the column Modbus access stands for read (with FC03); write (with FC06); read/write. Table 5- 11 Assigning the Modbus register to the parameters of the Control Unit Modbus...
Page 128
Communication via RS485 5.4 Communication using Modbus RTU Modbus Description Modb Unit Scaling ON/OFF text Data / parameter register factor or Value range number cess 40244 DI 4 HIGH r0722.4 40245 DI 5 HIGH r0722.5 Analog inputs 40260 AI 0 -300.0 …...
Page 129
Communication via RS485 5.4 Communication using Modbus RTU Modbus Description Modb Unit Scaling ON/OFF text Data / parameter register factor or Value range number cess 40499 PRM ERROR code 0 … 255 Technology controller 40500 Technology controller enable 0 … 1 p2200, r2349.0 40501 Technology controller MOP...
Communication via RS485 5.4 Communication using Modbus RTU 5.4.4 Acyclic communication via Modbus RTU Acyclic communication or general parameter access is realized using the Modbus register 40601 … 40722. Acyclic communication is controlled using 40601. 40602 contains the function code (always = 47 = 2F hex) and the number of the following user data.
Page 131
Communication via RS485 5.4 Communication using Modbus RTU Structure of a read request via Modbus function code 03 (FC 03) Any valid register address is permitted as the start address. Via FC 03, the control can address more than one register with one request. The number of addressed registers is contained in bytes 4 and 5 of the read request.
Page 132
Communication via RS485 5.4 Communication using Modbus RTU Structure of a write request via Modbus function code 06 (FC 06) Start address is the holding register address. Via FC 06, with one request, only precisely one register can be addressed. The value, which is written to the addressed register, is contained in bytes 4 and 5 of the write request.
Communication via RS485 5.4 Communication using Modbus RTU 5.4.6 Acyclically read and write parameter via FC 16 Via FC 16, with one request, up to 122 registers can be written to directly one after the other, while for Write Single Register (FC 06) you must individually write the header data for each register.
Communication via RS485 5.4 Communication using Modbus RTU 5.4.6.1 Read parameter Example: r0002 read acyclically Table 5- 18 Write parameter request: Reading the parameter value of r0002 from slave number 17 Byte Description Header 11 h Slave address 10 h Function code (write multiple) 0258 h Register start address...
Communication via RS485 5.4 Communication using Modbus RTU Table 5- 21 Response for unsuccessful read operation - read request still not completed Byte Description Header 11 h Slave address Number of following data bytes (20 h: 32 bytes ≙ 16 registers) 03 h Function code (read) 20 h...
Communication via RS485 5.4 Communication using Modbus RTU Table 5- 24 Response for successful write operation Byte Description Header 11 h Slave address Number of following data bytes (20 h: 32 bytes ≙ 16 registers) 03 h Function code (read) 20 h User data 0002 h...
Page 137
Communication via RS485 5.4 Communication using Modbus RTU Logical error If the slave detects a logical error within a request, it responds to the master with an "exception response". In this case, the slave sets the highest bit in the function code to 1 in the response.
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Communication via BACnet MS/TP - only CU230P-2 HVAC / BT BACnet properties In BACnet, components and systems are considered to be black boxes which contain a number of objects.
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT 5.5.1 Basic settings for communication Overview Procedure Proceed as follows to set communication via BACnet: 1. Select the default setting 110 – With STARTER: Under Control Unit/Configuration "Default setting of setpoint/command sources": 110 "BT Mac 10: BACnet MS/TP fieldbus"...
Page 140
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Setting the address You set the MAC address of the inverter using the address switches on the Control Unit, using parame- ter p2021 or in STARTER. Valid address range: 0 …...
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT 5.5.1.1 Parameters for setting communication via BACnet General settings Processing times p2024[0 … 2] p2024[0]: 0 ms … 10000 ms, maximum processing time (APDU timeout), factory setting = 1000 ms, p2024[1 …...
Page 142
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Device name - default setting, change name, restore factory setting In BACnet, the Control Unit has a unique name, which is required for identification when replacing a device etc. The device name has the following structure in the factory setting: The name is represented in the ASCII format in the 79 indices of p7610.
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Example ● AO 0 should display the value written with object ANALOG OUTPUT 0 via the control. In this particular case, no other settings are required in the inverter. ●...
Page 144
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT The inverter can simultaneously process up to 32 SubscribeCOV services. These can all refer to the same object instances - or different object instances. SubscribeCOV monitors the property changes of the following objects: ●...
Page 145
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Object properties of other object types Object Object type property Binary Binary Binary Analog Analog Analog Multi-State Octet Input Output Value Input Output Value Input String Values Object_Identifier Object_Name...
Page 146
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Binary Input Objects Instance Object name Description Possible Text active / Access Parameter values text inactive type DI0 ACT State of DI 0 ON/OFF ON/OFF r0722.0 DI1 ACT State of DI 1 ON/OFF...
Page 147
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Instance Object name Description Possible values Text Text Parameter active inactive cess type AT SET- Setpoint reached YES / NO r0052.8 POINT AT MAX Maximum speed reached YES / NO r0052.10 FREQ...
Page 148
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Analog Input Objects Object name Description Unit Range Access Parameter stance type ANALOG IN 0 AI0 input signal V/mA inverter-dependent r0752[0] ANALOG IN 1 AI1 input signal V/mA inverter-dependent r0752[1]...
Page 149
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Object name Description Unit Range Access Parameter stance type AV16 SPEED Reference speed of the inverter 6.0 … 210000 p2000 STPT 1 AV17 FREQ SP PCT Setpoint 1 (when controlling via -199.99 …...
Page 150
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Object name Description Unit Range Access Parameter stance type AV5102 FILTER TIME 0 Technology controller 0 actual 0 … 60 p11065 value filter time constant AV5103 DIFF TIME 0 Technology controller 0 differen- 0 …...
Page 151
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT Multi-State Input Objects Instance Object name Description Possible values Access type Parameter MSI0 FAULT_1 Fault number 1 See List Manual "List of faults and r0947[0] alarms" MSI1 FAULT_2 Fault number 2...
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT 5.5.3 Acyclic communication (general parameter access) via BACnet Acyclic communication or general parameter access is realized via BACnet objects DS47IN and DS47OUT. Acyclic communication uses the octet string value objects OSV0 and OSV1. Instance Object name Description...
Page 153
Communication via RS485 5.5 Communication via BACnet MS/TP - only CU230P-2 HVAC / BT If the response is still not available, then you receive the following message via the present value window of the OSV1: Table 5- 29 Read parameter content via OSV1 Byte Description 2F h...
Communication via RS485 5.6 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT P1 is an asynchronous master-slave communication between what is known as a Field Cabinet (master) and the FLN devices (slaves). FLN stands for "Floor level network". The master individually addresses the various slaves.
Page 155
Communication via RS485 5.6 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT Additional setting options Additional parameters for adapting communication via P1: Main setpoint p1070 = 2050.1 Connect the signal for the main setpoint to the communication interface Sending process data ●...
Page 156
Communication via RS485 5.6 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT Overview The subsequently listed "Point Numbers" for communication are defined using P1 in the converter. The values listed in the tables refer to SI units. Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Page 157
Communication via RS485 5.6 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Page 158
Communication via RS485 5.6 Communication via P1 - only CU230P-2 HVAC, CU230P-2 BT 1*): For reasons of compatibility, these type 1 subpoints can save COV area information. Point Number 98 RAM TO ROM was implemented in order to be able to save these in a non- volatile fashion.
Integrating an inverter in a CANopen network To integrate an inverter in a CANopen network, we recommend the EDS file on the Internet EDS (http://support.automation.siemens.com/WW/view/en/48351511). This file is the description file of the SINAMICS G120 inverter for CANopen networks. In this way, you can use the objects of the DSP 402 device profile.
Page 160
Communication over CANopen Grounding the CANopen Control Unit The CAN ground (pin 3) and the optional ground are electrically isolated from the ground potential of the system. The optional shield (pin 5) and the connector housing are connected with the ground potential of the system.
Page 161
Communication over CANopen COB ID for individual communication objects You will find the specifications for the COB IDs of the individual communication objects below: • COB ID Cannot be changed • COB ID = free Pre-assigned with 80 hex SYNC •...
Communication over CANopen 6.1 Network management (NMT service) Network management (NMT service) Network management (NMT) is node-oriented and has a master-slave topology. A node is a master or a slave. The inverter is an NMT slave, and can adopt the following states: ●...
Page 163
Communication over CANopen 6.1 Network management (NMT service) NMT states The inverter state is displayed in p8685. You can either change the inverter state via the control with an NMT telegram, using one of the command specifiers listed below, or in the inverter itself using p8685. ●...
Page 164
Communication over CANopen 6.1 Network management (NMT service) Boot-up Service The boot-up protocol indicates the state of the NMT slave after it has booted (factory setting "Pre-operational"). Bootup protocol COB ID = 700 hex + node ID 1 data byte with the value 0 is transmitted. NMT state after power up Using parameter p8684, set the state that the inverter goes into after powering up: ●...
Communication over CANopen 6.2 SDO services SDO services You can access the object directory of the connected drive unit using the SDO services. An SDO connection is a peer-to-peer coupling between an SDO client and a server. The drive unit with its object directory is an SDO server. The identifiers for the SDO channel of a drive unit are defined according to CANopen as follows.
Page 166
Communication over CANopen 6.2 SDO services Examples of object numbers Parameter Number of the inverter parameter - offset value Object number Decimal Hexadecimal ● p0010: 10 dec A hex ⇒ 200A hex ● p11000: 1000 dec 3E8 hex ⇒ 23E8 hex ●...
Communication over CANopen 6.2 SDO services 6.2.2 Access PZD objects via SDO Access to mapped PZD objects When you access objects mapped via transmit or receive telegrams, you can access the process data without additional settings. Overview Image 6-1 Access to mapped PZD setpoint objects Image 6-2 Access to mapped PZD actual value objects Example, access to object 6042 hex...
Page 168
Communication over CANopen 6.2 SDO services Access to non-mapped PZD objects When you access objects that are not interconnected via the receive or transmit telegram, you must also establish the interconnection with the corresponding CANopen parameters. Overview Image 6-4 Access to non-mapped PZD setpoint objects Image 6-5 Access to non-mapped free PZD actual value objects Image 6-6...
Communication over CANopen 6.3 PDO services PDO services Process data objects (PDO) CANopen transfers the process data using "Process Data Objects" (PDO). There are send PDOs (TDPO) and receive PDOs (RPDO). CAN controller and inverter each exchange up to eight TPDOs and RPDOs. PDO communication parameters and PDO mapping parameters define a PDO.
Page 170
Communication over CANopen 6.3 PDO services COB ID Overview: Communication over CANopen (Page 159). Calculating the COB IDs: Predefined connection set (Page 172) Transmission type For process data objects, the following transmission types are available, which you set in index 1 of the communication parameter (p8700[1] … p8707[1] / p8720[1] … p8727[1]) in the inverter: ●...
Page 171
Communication over CANopen 6.3 PDO services Image 6-8 Principle of synchronous and asynchronous transmission For synchronous TPDOs, the transmission mode also identifies the transmission rate as a factor of the SYNC object transmission intervals. The CAN controller transfers data from synchronous RPDOs that it received after a SYNC signal only after the next SYNC signal to the inverter.
Communication over CANopen 6.3 PDO services 6.3.1 Predefined connection set If you integrate the inverter using the factory setting in CANopen, the inverter receives the control word and the speed setpoint from the controller. The inverter returns the status word and the actual speed value to the controller.
Communication over CANopen 6.3 PDO services 6.3.2 Free PDO mapping Using the free PDO mapping, you configure and interconnect any process data as required as follows: ● as free objects free objects (Page 191) or ● as objects of drive profile CiA 402, corresponding to the requirements of your system for the PDO service The precondition is that the inverter is set for free PDO mapping.
Page 174
Communication over CANopen 6.3 PDO services Note Requirement for changing the OD indexes of the SINAMICS mapping parameters To allow you to change the values of the mapping parameters, you must set the COB ID of the corresponding parameter to invalid. To do this, add a value of 80000000 hex to the COB-ID.
Page 175
Communication over CANopen 6.3 PDO services Free TPDO mapping - Overview Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Communication over CANopen 6.3 PDO services 6.3.3 Interconnect objects from the receive and transmit buffers Procedure To interconnect process data, proceed as follows: 1. Create a telegram: create PDO (parameterize the PDO Com. Parameters and PDO mapping parameters). Predefined connection set (Page 172) Free PDO mapping (Page 173) 2.
Communication over CANopen 6.3 PDO services Interconnecting the send buffer The inverter sends the data from the send buffer as follows: ● p2051[0] … p2051[13] in PZD 1 … PZD 14 (indication of the actual values in r2053[0 … 13]) ●...
Page 178
Communication over CANopen 6.3 PDO services Mapping the torque limit (p1520) with RPDO1 Procedure Proceed as follows to accept the torque limit value in the communication: 1. Set the OV index for the torque limit: first free OV index from the receive data from the "Free objects" 5800 table 2.
Communication over CANopen 6.4 CANopen operating modes CANopen operating modes The inverter has the following CANopen operating modes CANopen operating mode SINAMICS Active Setting in 6502 h: Open-loop/closed-loop con- Control Unit / Value operating mode 6060 h: Display trol mode inverter the acti- p1300...
Communication over CANopen 6.5 RAM to ROM via the CANopen object 1010 Switching the CANopen operating modes You can also use parameters from other CANopen operating modes, independently from the current effective CANopen operating mode. RAM to ROM via the CANopen object 1010 Save the parameters of the inverter EEPROM using CANopen object 1010.
Communication over CANopen 6.6 Object directories Object directories 6.6.1 General objects from the CiA 301 communication profile Overview The following table lists the drive-independent communication objects. The "SINAMICS parameters" column shows the parameter numbers assigned in the converter. Table 6- 2 Drive-independent communication objects OD index Subindex...
Page 182
Communication over CANopen 6.6 Object directories OD index Subindex Object name SINAMICS para- Trans- Data Default Can be read/ (hex) (hex) meters mission type values written Number of errors: modu- p8611.65 le 8 42-49 Standard error field: p8611.66-p8611.73 SDO module 8 Number of Control Unit p8611.74 faults...
Page 183
Communication over CANopen 6.6 Object directories OD index Subindex Object name SINAMICS para- Trans- Data Default Can be read/ (hex) (hex) meters mission type values written Number of entries r0102 – Module ID p0107[0...15] 1029 Error behavior Number of error classes Communication Error p8609.0 Device profile or manu-...
Page 184
Communication over CANopen 6.6 Object directories RPDO configuration objects The following tables list the communication and mapping parameters together with the indexes for the individual RPDO configuration objects. The configuration objects are established via SDO. The "SINAMICS parameters" column shows the parameter numbers assigned in the converter.
Page 185
Communication over CANopen 6.6 Object directories Table 6- 4 RPDO configuration objects - mapping parameters Sub- Name of the object SINAMICS Data Predefined Can be index index parameters type connection set read/ (hex) (hex) written to 1600 Receive PDO 1 mapping parameter Number of mapped application objects in PDO PDO mapping for the first application object to be p8710.0...
Page 186
Communication over CANopen 6.6 Object directories Sub- Name of the object SINAMICS Data Predefined Can be index index parameters type connection set read/ (hex) (hex) written to PDO mapping for the first application object to be p8714.0 mapped PDO mapping for the second application object to p8714.1 be mapped PDO mapping for the third application object to be...
Page 187
Communication over CANopen 6.6 Object directories TPDO configuration objects The following tables list the communication and mapping parameters together with the indexes for the individual TPDO configuration objects. The configuration objects are established via SDO. The "SINAMICS parameters" column shows the parameter numbers assigned in the converter.
Page 188
Communication over CANopen 6.6 Object directories Sub- Object name SINAMICS Data Predefined Can be index index parameters type connection set read/ (hex) (hex) written Inhibit time p8724.2 Reserved p8724.3 Event timer p8724.4 1805 Transmit PDO 6 communication parameter Largest subindex supported COB ID used by PDO p8725.0 C000 06DF hex...
Page 189
Communication over CANopen 6.6 Object directories Table 6- 6 TPDO configuration objects - mapping parameters Subin- Object name SINAMICS Data type Predefined Can be index parameters connection read/ (hex) (hex) written 1A00 Transmit PDO 1 mapping parameter Number of mapped application objects in PDO PDO mapping for the first application object to be p8730.0 6041 hex...
Page 190
Communication over CANopen 6.6 Object directories Subin- Object name SINAMICS Data type Predefined Can be index parameters connection read/ (hex) (hex) written PDO mapping for the first application object to be p8734.0 mapped PDO mapping for the second application object to p8734.1 be mapped PDO mapping for the third application object to be...
Communication over CANopen 6.6 Object directories 6.6.2 Free objects You can interconnect any process data objects of the receive and transmit buffer using receive and transmit double words. ● Scaling for percentage values: – 16-bit (word): 4000 hex ≙ 100% –...
Communication over CANopen 6.6 Object directories 6.6.3 Objects from the CiA 402 drive profile The following table lists the object directory with the index of the individual objects for the drives. The "SINAMICS parameters" column shows the parameter numbers assigned in the inverter.
Page 193
Communication over CANopen 6.6 Object directories OD index Sub- Name of the object SINAMICS Transmission Data Default Can be (hex) index parameters type setting read/ (hex) written 6077 Torque actual value r0080 SDO/PDO – Velocity mode 6042 vl target velocity r8792 SDO/PDO –...
– Speed setpoint and control word – Speed actual value and status word You can find the EDS in the Internet at: EDS (electronic data sheet) (http://support.automation.siemens.com/WW/view/en/48351511) Procedure Proceed as follows to commission the CANopen interface: Connecting inverter to CAN bus (Page 195) 2.
Communication over CANopen 6.7 Integrating the inverter into CANopen 6.7.1 Connecting inverter to CAN bus Connect the inverter to the fieldbus via the 9-pin SUB-D pin connector. The connections of this pin connector are short-circuit proof and isolated. If the inverter forms the first or last slave in the CANopen network, then you must switch-in the bus- terminating resistor.
Communication over CANopen 6.7 Integrating the inverter into CANopen Modified Node ID or activate baud rate Procedure To activate the changed bus address or baud rate, proceed as follows: 1. Switch off the inverter supply voltage. 2. Wait until all LEDs on the inverter go dark. 3.
Page 197
Communication over CANopen 6.7 Integrating the inverter into CANopen Heartbeat Principle of operation The slave periodically sends heartbeat messages. Other slaves and the master can monitor this signal. In the master, set the responses for the case that the heartbeat does not come. Setting value for heartbeat Set in p8606 the cycle time for the heartbeat in milliseconds.
Communication over CANopen 6.8 Error diagnostics Error diagnostics Objects to signal and describe errors and operating states The following options are available to display errors and operating states: ● Display of the operating state using LEDs ● Display of the operating state using the alarm object (Emergency Object) –...
Page 199
Communication over CANopen 6.8 Error diagnostics Display of the operating state using the alarm object (Emergency Object) Error states are displayed using the alarm object (Emergency Object), OV index 1014 in the emergency telegram. It has the following structure: CANopen error code Bytes 0 and 1: •...
Page 200
Communication over CANopen 6.8 Error diagnostics CANopen error register (error register) You can read out the error register using the following objects: ● OV index 1001 hex ● Inverter parameter r8601 It indicates the error in byte 2 of the emergency telegram. Table 6- 9 CANopen Error Register Error Regis-...
Communication via AS-i - only for G110M General information The inverter operates based on the extended AS-i specification V3.0. The signaling is made as Manchester-coded current pulses superimposed on the 28 V supply. Decouple the 28 V supply with inductances so that the receivers can decouple the transferred messages.
Communication via AS-i - only for G110M 7.1 Setting the address Connection The following table shows the AS-i plug assignment. Further connection information is contained in the AS-Interface system manual. Overview of the manuals (Page 235) Table 7- 1 Pin assignment X03 AS-i, Function Description...
Page 203
Communication via AS-i - only for G110M 7.1 Setting the address Automatic addressing via the AS-i master Single Slave For automatic addressing, the address is specified by the AS-i master. For a Single Slave, the master checks which slave has address 0 and assigns it the next free address. This address is also written to parameter p2012.
Communication via AS-i - only for G110M 7.2 Single Slave mode Single Slave mode In Single Slave mode, four bits are available for the communication between the AS-i master and the inverter. The four bits are used to transfer process data. In parallel, the control can start a diagnostic request via AS-i.P0.
Page 205
Communication via AS-i - only for G110M 7.2 Single Slave mode Default setting 32: Modified Single Slave mode In Single Slave mode with modified addressing the control specifies the following: Control -> inverter • AS-i.DO0 -> p3330.0 = 2093.0 ON clockwise / OFF 1 •...
Communication via AS-i - only for G110M 7.3 Dual Slave mode Dual Slave mode In Dual Slave mode, eight bits are available for the communication between the AS-i master and the inverter. The eight bits are used to transfer process data. In parallel, the control can start a diagnostic request via AS-i.P0.
Page 207
Communication via AS-i - only for G110M 7.3 Dual Slave mode • AS-i.DO1 -> Data bit for the CTT2 transfer, four bytes cyclically or acyclically via PIV. The reading and writing of parameters is possible via the PIV. Because data is transferred bit-by-bit, the read and write process is very slow.
Page 208
Communication via AS-i - only for G110M 7.3 Dual Slave mode Table 7-5 Alarm and fault messages via RP0 … RP3 from the inverter to the AS-i master (Page 210). Default setting 34, slave 1 with profile 7.A.5: Control -> inverter •...
Communication via AS-i - only for G110M 7.4 Assignment tables Assignment tables Fixed speeds - Single Slave Table 7- 2 Fixed speeds via the motor control bits AS-i.DO3 AS-i.DO2 AS-i.DO1 AS-i.DO0 Response in the inverter OFF1 On + fixed speed 1 (factory setting: 1500 rpm) On + fixed speed 2 (factory setting: -1500 rpm) On + fixed speed 3 (factory setting: 300 rpm) On + fixed speed 4 (factory setting: 450 rpm)
Page 210
Communication via AS-i - only for G110M 7.4 Assignment tables Fixed speeds - Dual Slave Table 7- 4 Fixed speeds via the motor control bits and response in the inverter AS-i.DO2 AS-i.DO1 AS-i.DO0 Response in the inverter OFF1 On + fixed speed 1 (factory setting: 1500 rpm) On + fixed speed 2 (factory setting: -1500 rpm) On + fixed speed 3 (factory setting: 300 rpm) On + fixed speed 4 (factory setting: 450 rpm)
Communication via AS-i - only for G110M 7.5 Cyclic and acyclic communication via CTT2 If an acyclical request cannot be executed by the inverter, it replies with one of the following error messages. Error message Meaning No fault Invalid index Incorrect length Request not implemented Busy (the request could not be processed completely within the time window, retry...
Communication via AS-i - only for G110M 7.5 Cyclic and acyclic communication via CTT2 7.5.2 Acyclic communication - standard This type of acyclical communication supports the ID read request and the diagnostic read request. All other requests receive the "request not implemented" message response. ●...
Page 214
Communication via AS-i - only for G110M 7.5 Cyclic and acyclic communication via CTT2 Data exchange Reading data The data for the last write or exchange request is read Writing data In the event of a fault, the inverter sends the following telegram as reponse to the master: Value for PWE: Fault table from USS parameter channel (Page 112).
Appendix Communication with STEP7 This section describes the communication with a SIMATIC control system using examples. To configure the control you require the SIMATIC STEP 7 software tool with HW Config. It is assumed that you are knowledgeable about working with SIMATIC control systems and that you have a sound understanding of the STEP 7 engineering tool.
Appendix A.1 Communication with STEP7 6. Create a PROFIBUS DP network. You have created a STEP 7 project with a SIMATIC control and a PROFIBUS network. A.1.1.2 Inserting the inverter into the project There are two ways to insert an inverter into the project: ●...
Page 217
Integrated Function Manual". 2. PKW channel, if one is used. 3. Standard, SIEMENS or free telegram, if one is used. 4. Direct data exchange If you do not use one or several of the telegrams 1, 2 or 3, configure your telegrams starting with the 1st slot.
Appendix A.1 Communication with STEP7 A.1.2 Configuring PROFINET communication A.1.2.1 Configuring the controller and converter in HW Config Using an example of a SINAMICS G120 with Control Unit CU240B-2 or CU240E-2, the procedure shows how you insert the inverter into the project. Procedure Proceed as follows to configure communications between the inverter and the control system via PROFINET:...
Page 219
Appendix A.1 Communication with STEP7 8. Select your subnet. 9. Using the hardware catalog, first insert the inverter using drag & drop. 10.Insert the communication telegram. 11.Open the properties window of the inverter and enter a unique and descriptive device name for the inverter.
Page 220
Appendix A.1 Communication with STEP7 15.Enter the IP address of the controller. If you do not have the IP address readily available, you can display the participants that can be reached by clicking the "Display" button. Select the control from the list of accessible participants, and exit the screen form with OK.
Appendix A.1 Communication with STEP7 A.1.2.2 Activate diagnostic messages via STEP 7 Procedure Proceed as follows to activate the diagnostic messages of the inverter: 1. In HW Config, select the inverter. Image A-1 Highlight inverter in HW Config 2. By double clicking on slot 0 in the station window, open the property window for the inverter's network settings.
Appendix A.1 Communication with STEP7 A.1.2.3 Accessing the inverter with STARTER via STEP 7 Adapting the PROFINET interface If you wish to commission the inverter with STARTER via PROFINET, then you must address your PC and assign STARTER to the interface via which STARTER goes online with the inverter.
Page 223
Appendix A.1 Communication with STEP7 9. Open the SIMATIC Manager. 10.Assign the TCP/IP interface to "Intel(R) PRO/100 VE Network Connection" via "Tools/PG/PC interface". You have allocated your computer the IP address and the address of the subnet mask, and defined the PC interface via which STARTER goes online with the inverter. Make the inverter visible in the control If you have configured the inverter using GSDML, then in STEP 7 you must generate a reference of the inverter for STARTER.
Page 224
Appendix A.1 Communication with STEP7 7. Enter the PROFINET device name in the "General" tab. 8. Exit the screen form with OK. 9. The inverter is visible in your project. You can now call STARTER from your STEP 7 project. Call the STARTER and go online Procedure To call STARTER from STEP 7 and establish an online connection to the inverter, proceed...
Appendix A.1 Communication with STEP7 A.1.3 STEP 7 program examples Data exchange via the fieldbus Analog signals The inverter always scales signals that are transferred via the fieldbus to a value of 4000 hex. Table A- 1 Signal category and the associated scaling parameters Signal category 4000 hex ≙...
Appendix A.1 Communication with STEP7 A.1.3.1 Cyclic communication via standard telegram 1 with PROFIBUS or PROFINET The controller and inverter communicate via standard telegram 1. The control specifies con- trol word 1 (STW1) and the speed setpoint, while the inverter responds with status word 1 (ZSW1) and its actual speed.
Page 227
Appendix A.1 Communication with STEP7 Table A- 2 Assignment of the control bits in the inverter to the SIMATIC flags and inputs Bit in Significance Bit in Bit in Bit in Inputs STW1 ON/OFF1 E0.0 OFF2 OFF3 Operation enable Ramp-function generator enable Start ramp-function generator Setpoint enable Acknowledge fault...
Appendix A.1 Communication with STEP7 A.1.3.2 Cyclic communication with standard telegram 1 via PROFIBUS DP with direct data exchange Two drives communicate via standard telegram 1 with the higher-level controller. In addition, drive 2 receives its speed setpoint directly from drive 1 (actual speed). Image A-2 Communication with the higher-level controller and between the drives with direct data exchange Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Page 229
Appendix A.1 Communication with STEP7 Setting direct data exchange in the control Procedure Proceed as follows to set direct data exchange in the control: 1st In HW Config in drive 2 (subscriber), insert a di- rect data exchange object, e.g. "Slave-to-slave, PZD2".
Page 230
Appendix A.1 Communication with STEP7 You have now defined the value range for direct data exchange. In the direct data exchange, drive 2 receives the sent data and writes this into the next available words, in this case, PZD3 and PZD4. Settings in drive 2 (subscriber) Drive 2 is preset in such a way that it receives its setpoint from the higher-level controller.
Displays the read process M9.3 Displays the write process The number of simultaneous requests for acyclic communication is limited. More detailed informa- tion can be found under http://support.automation.siemens.com/WW/view /de/15364459 (http://support.automation.siemens.com/WW/vie w/en/15364459). Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Page 232
Appendix A.1 Communication with STEP7 Image A-3 Reading parameters Note With PROFINET standard function blocks (SFB) instead of system functions (SFC) With acyclic communication via PROFINET, you must replace the system functions with standard function blocks as follows: • SFC 58 → SFB 53 •...
Page 233
Appendix A.1 Communication with STEP7 Explanation of FC 1 Table A- 3 Request to read parameters Data block DB 1 Byte n Bytes n + 1 MB 40 Header Reference 01 hex: Read request 01 hex Number of parameters (m) MB 62 10 hex: Parameter value MB 58...
Page 234
Appendix A.1 Communication with STEP7 Image A-4 Writing parameters Explanation of FC 3 Table A- 4 Request to change parameters Data block DB 3 Byte n Bytes n + 1 MB 42 Header Reference 02 hex: Change request 01 hex Number of parameters MB 44 00 hex...
Installing, commissioning and maintaining the inverter. Advanced commissioning ● SINAMICS G120C operating instructions. (https://support.industry.siemens.com/cs/ww/en/view/109478830) Installing, commissioning and maintaining the inverter. Advanced commissioning ● SINAMICS G110M operating instructions (https://support.industry.siemens.com/cs/ww/en/view/109478193) Installing, commissioning and maintaining the inverter. Advanced commissioning ● Operating instructions SINAMICS G120D with CU240D-2 (https://support.industry.siemens.com/cs/ww/en/view/109477366)
Page 236
List of all parameters, alarms and faults, graphic function diagrams. ● SINAMICS G120C List Manual (https://support.industry.siemens.com/cs/ww/en/view/109477254) List of all parameters, alarms and faults, graphic function diagrams. ● SINAMICS G110M List Manual (https://support.industry.siemens.com/cs/ww/en/view/109478707) List of all parameters, alarms and faults, graphic function diagrams. ● SIMATIC ET 200pro FC-2 List Manual (https://support.industry.siemens.com/cs/ww/en/view/109478711)
Page 237
Appendix A.2 Manuals and technical support ● SIMATIC ET 200pro operating instructions (https://support.industry.siemens.com/cs/ww/en/view/21210852) Distributed ET 200pro I/O system ● SIMATIC ET 200pro motor starters manual (https://support.industry.siemens.com/cs/ww/en/view/22332388) ET 200pro motor starters ● AS-Interface system manual (https://support.industry.siemens.com/cs/ww/en/view/26250840) Finding the most recent edition of a manual...
Catalog Ordering data and technical information for SINAMICS G inverters. Catalog D31 for download or online catalog (Industry Mall): Everything about SINAMICS G120 (www.siemens.en/sinamics-g120) SIZER The configuration tool for SINAMICS, MICROMASTER and DYNAVERT T drives, motor starters, as well as SINUMERIK, SIMOTION controllers and SIMATIC technology...
A.2.3 Product Support Additional information about the product and more is available in the Internet: Product support (http://www.siemens.com/automation/service&support). This address provides the following: ● Actual product information (Update), FAQ (frequently asked questions), downloads. ● The Newsletter contains the latest information on the products you use.
Page 240
Appendix A.3 New and extended functions Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...
Index Control word 2 (STW2), 23 Control word 3 (STW3), 25 Cyclic communication, 18 AC/DC drive profile, 82 Acyclic communication, 40 Application Data exchange fieldbus, 225 Reading and writing parameters cyclically via PROFIBUS, 38 Data set 47 (DS), 40, 233 DC braking, 25 Device profile, 160 Direct data exchange, 39, 228...
Page 242
Index List Manual, 235 Questions, 239 Maximum cable length RS485 interface, 106 Modbus, 120 PROFIBUS, 72 PROFINET, 59 Scaling USS, 107 Fieldbus, 225 MELD_NAMUR (fault word according to the VIK-Namur SDO, 160, 165 definition), 27 SDO services, 165 SIMATIC, 215, 216 SIZER, 238 Network management (NMT service), 162 Status word...
Page 243
Index ZSW3 (status word 3), 26 Fieldbuses Function Manual, 01/2016, FW V4.7 SP6, A5E34229197B AC...