SEW-Eurodrive MOVIDRIVE compact MCF Manual
  1. Manuals
  2. Brands
  3. SEW-Eurodrive Manuals
  4. Inverter Drive
  5. MOVIDRIVE compact MCF
  6. Manual
SEW-Eurodrive MOVIDRIVE compact MCF Manual

SEW-Eurodrive MOVIDRIVE compact MCF Manual

Serieal communication
Hide thumbs
Table of Contents

Advertisement

Quick Links

Edition
®
MOVIDRIVE
Serial Communication
11/2001
Manual
1053 1610 / EN

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MOVIDRIVE compact MCF and is the answer not in the manual?

Questions and answers

Related Manuals for SEW-Eurodrive MOVIDRIVE compact MCF

Summary of Contents for SEW-Eurodrive MOVIDRIVE compact MCF

  • Page 1 Edition ® MOVIDRIVE Serial Communication 11/2001 Manual 1053 1610 / EN...
  • Page 2 SEW-EURODRIVE...

  • Page 3: Table Of Contents

    Contents 1 Important Notes...................... 4 2 Introduction ......................5 Overview of serial interfaces ................5 Technical data....................8 MOVILINK® and system bus ................. 9 3 Installation ......................12 System bus (SBus) installation ..............12 RS-485 interface installation ................ 14 RS-232 interface installation ................ 16 4 RS-485 Communication ..................

  • Page 4: Important Notes

    Important Notes • This manual does not replace the detailed operating instructions! • Installation and startup only by trained personnel observing applicable ® accident prevention regulations and the MOVIDRIVE operating instructions! Documentation • Read through this manual carefully before you commence installation and startup of ®...

  • Page 5: Introduction

    Overview of serial interfaces Introduction Overview of serial interfaces ® The following serial interfaces are provided as standard with MOVIDRIVE drive inverters for serial communication: 1. System bus (SBus) = CAN bus to CAN specification 2.0, parts A and B. 2.
  • Page 6 Overview of serial interfaces ® MOVIDRIVE System bus (SBus): compact ® compact • The system bus (SBus) is routed to terminals X10:5/7 in MOVIDRIVE MCF/MCV/MCS4_A drive inverters. • The system bus (SBus) is routed to terminals X10:7/8 and X10:10/11 in ®...
  • Page 7 Overview of serial interfaces USS21A (RS-232 Startup, operation and service are possible from the PC via the serial interface. The and RS-485) SEW MOVITOOLS software is used for this purpose. It is also possible to transfer ® parameter settings to several MOVIDRIVE drive inverters via PC.

  • Page 8: Technical Data

    Technical data Technical data System bus (SBus) Standard CAN specification 2.0 parts A and B Baud rate either 125, 250, 500 or 1000 kbaud, factory setting 500 kbaud ID range 3 – 1020 Address can be set with parameter P813: 0 – 63 Number of process fixed setting: 3 PD data words...

  • Page 9: Movilink® And System Bus

    MOVILINK® and system bus ® MOVILINK and system bus ® ® MOVILINK This document provides a detailed description of the MOVILINK serial interface ® protocol protocol for the RS-485 interfaces of MOVIDRIVE drive inverters. You can control the inverter and set its parameters via the RS-485 interface. However, please bear in mind that this communications variant is a proprietary communication system for low-end applications.
  • Page 10 MOVILINK® and system bus System bus The SBus is a CAN bus in accordance with the CAN specification 2.0, parts A and B. It ® (SBus) supports all services in the SEW MOVILINK unit profile. In addition, you can exchange plus®...
  • Page 11 MOVILINK® and system bus ® The MOVIDRIVE drive inverter offers you numerous diagnostic options for startup and service purposes. An easy-to-use diagnostics tool is provided in the MOVITOOLS/ SHELL PC software. This software makes it possible to call up a detailed display of the bus and unit status as well as setting all drive parameters.

  • Page 12: Installation

    System bus (SBus) installation Installation System bus (SBus) installation Only when P816 "SBus baud rate" = 1000 kbaud: ® compact MCH42A units with other MOVIDRIVE ® Do not combine MOVIDRIVE units in the same system bus combination. The units are allowed to be mixed at baud rates ≠ 1000 kbaud. ®...
  • Page 13 System bus (SBus) installation ® MOVIDRIVE compact MCHS4_A Control unit Control unit Control unit X10: X10: X10: System bus high SC11 System bus high SC11 System bus high SC11 System bus low System bus low System bus low SC12 SC12 SC12 Reference potential Reference potential...

  • Page 14: Rs-485 Interface Installation

    RS-485 interface installation RS-485 interface installation ® MOVIDRIVE The RS-485 interface is routed to terminals X13:10/11 and, in parallel, to the TERMINAL MD_60A option slot. The RS-485 interface can only be accessed via the TERMINAL option slot when the "serial interface type USS21A" option is attached. RS-485 connection via terminals X13:10/11 Control unit Control unit...
  • Page 15 RS-485 interface installation ® USS21A serial • With MOVIDRIVE MD_60A drive inverters, the RS-485 interface can also be interface accessed using the "serial interface type USS21A" option. ® • With MOVIDRIVE compact drive inverters, the RS-485 interface can only be accessed using the "serial interface type USS21A"...

  • Page 16: Rs-232 Interface Installation

    RS-232 interface installation RS-232 interface installation ® ® With MOVIDRIVE MD_60A and MOVIDRIVE compact, the RS-232 interface can only be accessed using the "serial interface type USS21A" option. RS-232 • Use a shielded standard interface cable for connecting to the RS-232 interface. connection Important: 1:1 cabling PC COM 1-4...

  • Page 17: Rs-485 Communication

    Telegrams RS-485 Communication Telegrams Telegram traffic Both cyclical and acyclical data exchange are used in drive engineering. Cyclical telegrams via the serial interface are used in automation applications, particularly for drive control. The master station must ensure cyclical data exchange in this case. Cyclical data Cyclical data exchange is used predominantly for controlling the inverters via the serial exchange...
  • Page 18 Telegrams Telegram The entire data exchange is performed using only two types of telegram. It involves the structure master sending a request containing data to the inverter, in the form of a request telegram. The inverter answers with a response telegram. When word information (16- bit) is sent within the user data, the high byte is always sent first and the low byte last.
  • Page 19 Telegrams Start pause (idle) The master must observe a start pause of at least 3.44 ms before sending the start character SD1 (02 ) so that the inverter can definitively identify the start of a request telegram. This pause prevents the bit combination 02 , which may also occur in the user data, from being erroneously interpreted as the start character.

  • Page 20: Addressing And Transmission Process

    Addressing and transmission process Addressing and transmission process Address byte The address byte always specifies the slave address regardless of the data direction. (ADR) Therefore, the ADR character in a request telegram specifies the address of the inverter which is to receive the request. In the opposite direction, the master can tell from which inverter the response telegram was sent.
  • Page 21 Addressing and transmission process Group addressing Each inverter possesses an adjustable group address in addtion to its individual (multicast) address. This setup enables the user to form groups with various stations and then address the individual stations in a group simultaneously using the group address. No response telegram is sent back to the master in the case of group addressing.
  • Page 22 Addressing and transmission process Broadcast address The broadcast address 255 permits a broadcast to all inverter stations. The request telegram sent out by the master to broadcast address 255 is received by all inverters, but they do not reply. Consequently, this addressing variant is predominantly used for transferring setpoints.
  • Page 23 Addressing and transmission process Structure and length of user data PDU type (TYP) The TYP byte describes the structure and the length of the user data which succeed it (protocol data unit or PDU). Fig. 18 shows the structure of the type byte..Idle...
  • Page 24 Addressing and transmission process ACYCLICAL PDU types in ACYCLICAL transmission: transmission Telegram PDU length TYP byte PDU name Description length in in bytes bytes 8 bytes parameter channel + 1 process data PARAM + 1PD word 1 process word 8 bytes parameter channel + 2 process data PARAM + 2PD words 2 process data words...
  • Page 25 Addressing and transmission process Block check character BCC ® Transmission The transmission reliability of the MOVILINK protocol is improved by the combination reliability of character parity and block parity. This involves setting the parity bit for each character of the telegram in such a way that the number of binary ones, including the parity bit, is even.
  • Page 26 Addressing and transmission process Transmission An asynchronous serial transmission procedure is used. This is supported by the UART process components of digital technology which are generally and commonly employed. This ® means the MOVILINK protocol can be implemented on almost all controls and master modules.
  • Page 27 Addressing and transmission process Transmission The transmission rate is 9600 baud. The communication link is monitored by the master rate and and the inverter themselves. The master monitors the response delay time; the inverter transmission monitors the receipt of cyclical request telegrams from the master. mechanisms Response delay A response delay time is generally programmed on the higher-level master system.
  • Page 28 Addressing and transmission process Processing the The inverter only processes request telegrams which have been received without errors request/response and are correctly addressed. The following reception errors can be recognized: telegrams • Parity error • Character frame error • Character delay time exceeded with request telegram •...

  • Page 29: Data Contents And Pdu Types

    Data contents and PDU types Data contents and PDU types Data contents The data content of the request and response telegram is structured with a process data ® area and a parameter channel in accordance with the MOVILINK communication and unit profile.
  • Page 30 Data contents and PDU types The handshake bit (bit 6) is used in cyclical transmission variant as an acknowledgement bit between the control and the inverter. In this variant, the parameter channel is transmitted cyclically, with the process data if necessary. For this reason, implementation of the service in the inverter has to be triggered by edge control using the handshake bit 6.
  • Page 31 Data contents and PDU types Description of the Bits 0 – 3 of the management byte define the individual parameter services. The parameter following parameter services are possible, although they are not supported by all services inverters. No service This coding signals that there is no parameter service. Read parameter A drive parameter is read in this parameter service.
  • Page 32 Data contents and PDU types Conversion index: The conversion index is used for converting the transmitted parameter value into a basic SI unit. Coding is performed in line with the sensor/actuator systems profile of the Profibus User Organization (PNO). Example: Drive parameter: P131 Ramp t11 UP CW Quantity index:...
  • Page 33 Data contents and PDU types The inverter now processes the read service and sends the service confirmation back by setting the handshake bit to an equal value. Byte 0: Management Service identifier: 0001 = Read Data length: 11 = 4 bytes Handshake bit: Must be changed with every new job.
  • Page 34 Data contents and PDU types Parameter setting Fig. 22 takes the example of the WRITE service to illustrate a parameter setting with cyclical PDU procedure between the control and the inverter concerning a cyclical PDU type. To types simplify the sequence, only the management byte of the parameter channel is shown. Higher level automatic system Drive Inverter (Slave)
  • Page 35 Data contents and PDU types Sample application ® Control via three In this example, the inverter (e.g. MOVIMOT ) is controlled via three process data process data words with PDU type 5 (3PD acyclical). The master sends three process output data words words (PO) to the inverter.
  • Page 36 Data contents and PDU types ® PDU types List of PDU types supported by MOVIDRIVE inverters: PDU type Name PARAM + 1PD cyclical 1PD cyclical PARAM + 2PD cyclical 2PD cyclical PARAM + 3PD cyclical 3PD cyclical PARAM + 0PD cyclical PARAM + 1PD acyclical 1PD acyclical PARAM + 2PD acyclical...

  • Page 37: System Bus (Sbus)

    Slave data exchange via MOVILINK® System Bus (SBus) ® Slave data exchange via MOVILINK ® Communication via MOVILINK incorporates the data exchange of parameter and ® process data telegrams. The MOVIDRIVE unit can communicate as master or slave in this process. As master, the unit can actively initiate a data exchange of parameter and process data plus®...
  • Page 38 Slave data exchange via MOVILINK® Creating the The following table shows the relationship between the type of telegram and the address ® identifiers when the identifiers for SBus MOVILINK telegrams are created: Identifier Telegram type 8 × SBus address + 3 Process output data telegram (PO) 8 ×...
  • Page 39 Slave data exchange via MOVILINK® Process data Process data telegrams are comprised of a process output and a process input data telegrams telegram. The process output data telegram is sent from the master to a slave; it contains the setpoint values for the slave. The process input data telegram is sent from the slave to the master and contains the actual values of the slave.
  • Page 40 Slave data exchange via MOVILINK® Parameter Parameter telegrams are made up of a parameter request telegram and a parameter telegrams response telegram. The parameter request telegram is sent by the master in order to read or write a parameter value. It consists of the: •...
  • Page 41 Slave data exchange via MOVILINK® Parameter The following parameters have to be set for communication via the SBus: settings Par. Name Setting Meaning 100 Setpoint source SBus The inverter gets its setpoint from the SBus. The inverter gets its control commands from 101 Control signal source SBus the SBus.

  • Page 42: Setting Parameters Via The Can Bus

    Setting parameters via the CAN bus Setting parameters via the CAN bus ® ® The MOVIDRIVE drive inverter supports the "MOVILINK parameter channel" and the ® "MOVILINK parameter channel-SYNC" with the SBus. Master control ® MOVILINK parameter channel ® MOVILINK parameter channel SYNC CAN bus 01025BEN Fig.
  • Page 43 Setting parameters via the CAN bus Management of The entire parameter setting sequence is coordinated with byte 0: "Management" byte. the parameter This byte is used for providing important service parameters such as service identifier, telegram data length, version and status of the service performed. The following table shows that bits 0 –...
  • Page 44 Setting parameters via the CAN bus Data range The data are located in byte 4 to byte 7 of the parameter telegram. This means up to 4 bytes of data can be transmitted per service. The data are always entered with right- justification, i.e.
  • Page 45 Setting parameters via the CAN bus Procedure for Taking the example of the WRITE-SYNC service, Fig. 32 represents a process of setting setting parameters parameters between the control and the drive inverter via CAN. To simplify the with CAN sequence, Fig. 16 only shows the management byte of the parameter telegram. While the control is preparing the parameter telegram for the WRITE-SYNC service, the drive inverter receives sync telegrams and receives and sends back process data telegrams.
  • Page 46 Setting parameters via the CAN bus Return codes for In the event of an incorrect parameter setting, the drive inverter sends back various parameter setting return codes to the master which set the parameters. These codes provide detailed information about the cause of an error. All of these return codes are structured in accordance with DIN 19245 P2.

  • Page 47: Master Data Exchange Via Movilink

    Master data exchange via MOVILINK® ® Master data exchange via MOVILINK ® plus® MOVILINK commands can be sent via IPOS in order to send parameter or process data telegrams to other stations. The command for implementing a parameter and/or process data exchange is MOVLNK. The Movilink (...) command is not multimaster-capable.
  • Page 48 Master data exchange via MOVILINK® plus® IPOS sample The command structure is initialized first. The following table shows a sample command program structure: MOVLNK Ml Name Value Meaning Ml.BusType Use of the SBus Ml.Address Slave address Ml.Format Parameter data and 3 process data items Ml.Service Read parameter data Ml.Index...
  • Page 49 Master data exchange via MOVILINK® plus® IPOS program sequence 05300AXX ® Fig. 33: Master data exchange via MOVILINK The parameter response and process input data are updated after the Movilink (...) command has been performed, provided there was no error during the transfer. If an error did occur, this event is signaled in the return code by a value other than zero.

  • Page 50: Master/Slave Operation Via The Sbus

    Master/slave operation via the SBus Master/slave operation via the SBus Please also read the description of parameter group P75_ "Master-Slave function" in the ® MOVIDRIVE System Manual for more information about master/slave operation. Master/slave operation can be performed via the SBus. It involves the master sending the setpoint value and the control word to the slaves every millisecond using an SBus group telegram.

  • Page 51: Data Exchange Via Variable Telegrams

    Data exchange via variable telegrams Data exchange via variable telegrams ® General Unit parameters and process data can be exchanged between units via MOVILINK information Both the transfer frame and the identifiers are defined on the CAN bus. Variable telegrams were introduced in order to create an open CAN bus interface. With the variable telegrams, there is a free choice of the identifier with which the telegrams are sent and the 8 bytes of data on the CAN bus are used for the content of two variables.
  • Page 52 Data exchange via variable telegrams Example for assignment of the CAN identifiers Inverter 1 (SBus) Inverter 2 (SBus) MOVILINK slave MOVILINK slave SBus address SBus address SBus group address SBus group address SBus sync. ID SBus sync. ID MOVILINK master MOVLNK to inverter 2 System bus (SBus) 02254BEN...
  • Page 53 Data exchange via variable telegrams The following relationship results from the previous table: 1. The identifiers shown on a gray background in the table (transmit identifiers) are no longer allowed to be used for variable transmit objects within this bus line. 2.
  • Page 54 Data exchange via variable telegrams Cyclical sending Command: _SBusComDef (SCD_TRCYCL, TrCycle) of variable (For a detailed description → MOVIDRIVE ® plus® IPOS manual) telegrams This command sets up a cyclical variable service which sends a variable telegram with a set identifier at cyclical intervals. Cyclical data transmission is started using the _SBusCommOn ( ) command and interrupted with a program stop.
  • Page 55 Data exchange via variable telegrams Receiving Command: _SBusComDef (SCD_REC, Rec) variable (For a detailed description → MOVIDRIVE ® plus® IPOS manual) telegrams This command sets up a variable read service which receives a variable telegram with a set identifier. Initialization of the objects is started using the _SBusCommOn ( ) command and interrupted with a program stop.
  • Page 56 Data exchange via variable telegrams Sending acyclical Command: _SBusComDef (SCD_TRACYCL, TrAcycl) variable (For a detailed description → MOVIDRIVE ® plus® IPOS manual) telegrams This command sets up an acyclical variable write service which sends a variable plus® telegram with a set identifier within an IPOS program cycle.
  • Page 57 Data exchange via variable telegrams Transfer formats and examples MOTOROLA Telegram 1: format 05301AXX Fig. 36: Example of SCOM with MOTOROLA format, telegram 1 ® MOVIDRIVE Serial Communication...
  • Page 58 Data exchange via variable telegrams Telegram 2: 05387AXX Fig. 37: Example of SCOM with MOTOROLA format, telegram 2 ® MOVIDRIVE Serial Communication...
  • Page 59 Data exchange via variable telegrams In the example, a variable telegram (= telegram 1) with a length of 8 bytes (i.e. 2 variables) and object number 1 is sent from unit 1 every 100 ms and received by unit 2. A second variable telegram (= telegram 2) with a length of 8 bytes (i.e.
  • Page 60 Data exchange via variable telegrams INTEL format Telegram 1: 02258BDE Fig. 39: Example of SCOM with INTEL format, telegram 1 ® MOVIDRIVE Serial Communication...
  • Page 61 Data exchange via variable telegrams Telegram 2: 05388AXX Fig. 40: Example of SCOM with INTEL format, telegram 2 In the example, a variable telegram (= telegram 1) with a length of 8 bytes (i.e. 2 variables) and object number 1 is sent from unit 1 every 100 ms and received by unit 2. A second variable telegram with a length of 8 bytes (i.e.

  • Page 62: Project Planning Example For Sbus

    Project planning example for SBus Project planning example for SBus Settings The following settings have to be made: • Number of drive inverters: 4 • Process data length: 3 • Baud rate: 500 kbit/s Inverter 1 Inverter 3 Inverter 4 Inverter 2 CAN bus master control...
  • Page 63 Project planning example for SBus IDs on the CAN In this combination, the IDs listed below are occupied on the CAN bus: SBus Drive inverter Telegram type address Process output data telegram (PO) Process input data telegram (PI) Process output data telegram synchronized (PO-sync) Parameter request telegram Parameter response telegram Process output data telegram (PO)

  • Page 64: Operation And Service

    Startup problems with the SBus Operation and Service Startup problems with the SBus • No communication on the SBus: Timeout or no response 1. SBus cable incorrect or not connected. 2. System bus high and system bus low reversed. 3. Not all stations are communicating at the same baud rate: Setting with parameter P816.

  • Page 65: Return Codes For Parameter Setting

    Return codes for parameter setting Return codes for parameter setting In the event of an incorrect parameter setting, the drive inverter sends back various return codes to the master which set the parameters. These codes provide detailed information about the cause of the error. All of these return codes are structured in accordance with EN 50170.
  • Page 66 Return codes for parameter setting Additional code The additional code contains the SEW-specific return codes dealing with incorrect parameter settings of the drive inverter. They are sent back to the master in "Error class 8 = Other error." The following table shows all possible codings for the additional code. Add.

  • Page 67: P60

    P6.. Explanation of the table header P60. P600 Parameter List Explanation of the table header The meanings of the entries in the table header are as follows: Par. no. = Parameter number used in MOVITOOLS/SHELL or the DBG11A. Parameter = Parameter name Index = 16-bit index for addressing the parameter via interfaces.

  • Page 68: Complete Parameter List, Sorted By Parameter Numbers

    P6.. Complete parameter list, sorted by parameter numbers P60. P600 Complete parameter list, sorted by parameter numbers ® Note that the following parameter list applies to MOVIDRIVE MD_60A and ® compact drive inverters. MOVIDRIVE ® MD_60A only are indicated by • after •...
  • Page 69 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 06. Binary outputs option Binary output DO10 8352 20A0 N/RW 0 – 22, step 1 Binary output DO11 8353 20A1 N/RW 0 –...
  • Page 70 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. Error t-1 8367 20AF N/RO Input terminals 1..6 8372 20B4 N/RO Bit 0 = DI00 – Bit 5 = DI05 Input terminals (opt.) 1..8 8377 20B9...
  • Page 71 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. Error t-4 8370 20B2 N/RO Input terminals 1..6 8375 20B7 N/RO Bit 0 = DI00 – Bit 5 = DI05 Input terminals (opt.) 1..8 8380 20BC...
  • Page 72 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 1.. Setpoints/ramp generators 10. Setpoint selection 0 = BIPOL./FIX.SETPT 1 = UNIPOL/FIX.SETPT 2 = RS-485 3 = FIELDBUS 4 = MOTOR POT Setpoint source 8461 210D...
  • Page 73 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 0 = 0 1 = 1 S pattern t12 8475 211B N/RW 2 = 2 3 = 3 0 –...
  • Page 74 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 16. Fixed setpoints 1 -5000000 – -0, step 200 Internal setpoint n11 [rpm] 8489 2129 rps N/RW 150000 0 –...
  • Page 75 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 2.. Controller parameters 20. Speed control P gain speed controller 8495 212F N/RW 2000 100 – 32000, step 10 0 –...
  • Page 76 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 3.. Motor parameters 30. Limits 1 Start/stop speed 1 [rpm] 8515 2143 rps N/RW 60000 0 – 150000, step 200 Minimum speed 1 [rpm] 8516 2144 rps...
  • Page 77 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 4.. Reference signals 40. Speed reference signal Speed reference value [rpm] 8539 215B rps N/RW 1500000 0 – 5000000, step 200 Hysteresis [rpm] 8540 215C rps...
  • Page 78 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 6.. Terminal assignment 60. Binary inputs basic unit 0 = NO FUNCTION 1 = ENABLE/RAP.STOP 2 = CW/STOP 3 = CCW/STOP 4 = n11/n21 5 = n12/n22...
  • Page 79 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 62. Binary outputs basic unit 0 = NO FUNCTION 1 = /ERROR 2 = READY 3 = OUTP. STAGE ON 4 = ROT.
  • Page 80 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 7.. Control functions 70. Operating modes 0 = VFC 1 1 = VFC 1 & GROUP 2 = VFC 1 & HOIST 3 = VFC 1 &...
  • Page 81 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 8.. Unit functions 80. Setup 0 = NO Factory setting 8594 2192 R/RW 1 = YES Parameter lock 8595 2193 N/S/RW 0 See menu no.
  • Page 82 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 87. Process data description 0 = NO FUNCTION 1 = SPEED 2 = CURRENT 3 = POSITION LO 4 = POSITION HI 5 = MAX.
  • Page 83 P6.. Complete parameter list, sorted by parameter numbers P60. P600 Index Unit/index Par. Parameter Access Default Meaning / value range Abbr. Sz. 93. IPOS Special functions Override 8637 21BD N/RW See menu no. 152 or index 8488 94. IPOS Encoder 0 = MOTOR ENC.

  • Page 84: Quantity And Conversion Index

    P6.. Quantity and conversion index P60. P600 Quantity and conversion index Quantity and conversion index from the PNO sensor/actuator profile Quantity Physical quantity Unit Abbreviation Conversion index index Dimensionless Meter Millimeter Length Kilometer Micrometer µm Square meter Area Square millimeter Square kilometer Cubic meter Volume...
  • Page 85 P6.. Quantity and conversion index P60. P600 Quantity Physical quantity Unit Abbreviation Conversion index index Cubic meter/second m3/s Cubic meter/minute m3/min Cubic meter/hour m3/h Volume rate of flow Liter/second Liter/minute l/min Liter/hour Kilogram/second kg/s Gram/second Tonne/second Gram/minute g/min Mass rate of flow Kilogram/minute kg/min Tonne/minute...
  • Page 86 P6.. Quantity and conversion index P60. P600 Conversion index A (conversion factor) 1/A (reciprocal conversion factor) B (offset) etc. 1.E-3/60 = 1.667 E-5 6.000 E+4 1/60 = 1.667 E-2 6.000 E+1 1.E+3/60 = 1.667 E+1 6.000 E-2 1.667 E-2 1.E-3/3600 = 2.778 E-7 3.6 E+6 1/3600 = 2.778 E-4 3.6 E+3...

  • Page 87: Index

    Index Acyclical data exchange Notes, important Address byte Overview of serial interfaces Block check character, creating Broadcast Parameter channel, management Broadcast address Parameter list - 0.. Display values - 1.. Setpoints/ramp generators CAN bus identifier - 2.. Controller parameters CAN identifiers, assignment example - 3..
  • Page 88 System bus, general description Technical data USS21A serial interface Transfer formats, INTEL format Transfer formats, MOTOROLA format Transmission process Transmission rate Transmission reliability Universal addressing USS21A USS21A serial interface, technical data Variable message, acyclical sending Variable message, cyclical sending Variable message, receiving Variable messages Warning instructions ®...
  • Page 92 SEW-EURODRIVE GmbH & Co · P.O. Box 3023 · D-76642 Bruchsal/Germany · Phone +49-7251-75-0 Fax +49-7251-75-1970 · http://www.sew-eurodrive.com · sew@sew-eurodrive.com...

This manual is also suitable for:

Movidrive seriesMovidrive compact mcs_4aMovidrive compact mcvMovidrive md_60a

Table of Contents