Altivar 61 - error

More documents

Recommendations

Info

Documentation structure Installation manual This manual describes: • How to assemble the drive • How to connect the drive Programming manual This manual describes: • The functions • The parameters • How to use the drive display terminal (integrated display terminal and graphic display terminal) Communication Parameters Manual This manual describes: • The drive parameters with specific information for use via a bus or communication network • The operating modes specific to communication (state chart) • The interaction between communication and local control Modbus, CANopen, Ethernet, Profibus, INTERBUS, Uni-Telway, FIPIO Modbus Plus, and DeviceNet manuals These manuals describe: • Assembly • Connection to the bus or network • Diagnostics • Configuration of the communication-specific parameters via the integrated display terminal or the graphic display terminal They describe the protocol communication services in detail. Altivar 58/58F migration manual This manual describes the differences between the Altivar 61 and the Altivar 58/58F. It explains how to replace an Altivar 58 or 58F, including how to replace drives communicating on a bus or network. 6
Presentation Magelis XBT Premium The Altivar 61 drive has been designed to meet all the configuration requirements encountered within the context of industrial communication installations. It includes the Modbus and CANopen communication protocols as standard. FTM FTM ATV 31 ATV 61 Sensors Sensors Example of configuration on CANopen bus Two integrated communication ports enable direct access to the Modbus protocol: • One RJ45 Modbus connector port 2 , located on the drive front panel, which is used to connect: • The remote graphic display terminal • A Magelis industrial HMI terminal • The PowerSuite software workshop • One RJ45 Modbus network port 1 , located on the drive’s control terminals, which is dedicated to control and signaling by a PLC or other type of controller. It can also be used to connect a display terminal or the PowerSuite software workshop. The CANopen protocol can be accessed from the Modbus network port via the CANopen adapter 3 (1). The Altivar 61 can also be connected to other networks and industrial communication buses by using one of the communication option cards: • Ethernet TCP/IP • Modbus/Uni-Telway. This card provides access to additional functions, which complement those of the integrated ports: Modbus ASCII and 4-wire RS 485 • Fipio • Modbus Plus • Profibus DP • DeviceNet • INTERBUS 2 1 3 The control section can be powered separately, thus allowing communication (monitoring, diagnostics) to be maintained even if the power supply section fails. The main communication functions of the Altivar 58 and Altivar 58F drives are compatible with the Altivar 61 (2): - Connection - Communication services - Drive behavior (profile) - Control and monitoring parameters - Basic adjustment parameters The PowerSuite software workshop supports the transfer of configurations from Altivar 58 and Altivar 58F drives to the Altivar 61. (1) If the CANopen adapter is installed, Modbus will not be available on the network port 1 . (2) Please refer to the ATV 58(F)/ATV 61 migration manual supplied on the documentation CD-ROM. 7
Page 1: Altivar 61 User's manual Communicat
Page 4 and 5: Table of Contents Measurement param
Page 8 and 9: Presentation All the drive function
Page 10 and 11: Profiles What is a profile? There a
Page 12 and 13: I/O profile Definition The behavior
Page 14 and 15: I/O profile Control word - run on s
Page 16 and 17: I/O profile Status word (ETA) bit 7
Page 18 and 19: DSP402 profile DSP402 state chart D
Page 20 and 21: DSP402 profile Quick stop active Em
Page 22 and 23: DSP402 profile "Halt" command: The
Page 24 and 25: DSP402 profile Starting sequence Th
Page 26 and 27: DSP402 profile • Check that the d
Page 30 and 31: DSP402 profile Sequence for a drive
Page 34 and 35: Command/reference switching Not sep
Page 36 and 37: Command/reference switching Channel
Page 38 and 39: Command/reference switching Referen
Page 40 and 41: Command/reference switching Assigni
Page 42 and 43: Command/reference switching DSP402
Page 44 and 45: Forced local mode Definition Forced
Page 46 and 47: Forced local Forced local mode and
Page 48 and 49: Priority stops Priority stops Prior
Page 50 and 51: Communication monitoring The Altiva
Page 52 and 53: Communication monitoring • The dr
Page 54 and 55: Communication monitoring Reaction t
Page 56 and 57:
Assignment of references from a net
Page 58 and 59:
Configuration saving and switching
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Parameter set switching The paramet
Page 68 and 69:
Parameter set switching Table of va
Page 70 and 71:
Control parameters Code Description
Page 72 and 73:
Control parameters Code Description
Page 74 and 75:
Status parameters Code Description
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Output value parameters Output valu
Page 84 and 85:
Reference parameters References (sp
Page 86 and 87:
Measurement parameters Input measur
Page 88 and 89:
Measurement parameters Code Descrip
Page 90 and 91:
I/O parameters Code Description AI1
Page 92 and 93:
I/O parameters Code Description AO3
Page 94 and 95:
Fault parameters Code Description L
Page 96 and 97:
Fault parameters Code Description C
Page 98 and 99:
Fault parameters Code Description F
Page 100 and 101:
Log parameters Code Description IP0
Page 102 and 103:
Log parameters Code Description ULP
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Identification parameters Code Desc
Page 120 and 121:
Communication parameters Code Descr
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
"Controller Inside" parameters Code
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
DSP402 standard configuration and a
Page 136 and 137:
DSP402 standard configuration and a
Page 138 and 139:
[1.1 SIMPLY START] (SIM-) Code Desc
Page 140 and 141:
[1.3 SETTINGS] (SEt-) Code Descript
Page 142 and 143:
[1.4 MOTOR CONTROL] (drC-) Code Des
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
[1.5 INPUTS / OUTPUTS CFG] (I-O-) [
Page 160 and 161:
Page 162 and 163:
[1.5 INPUTS / OUTPUTS CFG] (I-O-) C
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
[1.6 COMMAND] (CtL-) Code Descripti
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
[1.7 APPLICATION FUNCT.] (FUn-) [RE
Page 190 and 191:
[1.7 APPLICATION FUNCT.] (FUn-) [RA
Page 192 and 193:
[1.7 APPLICATION FUNCT.] (FUn-) Cod
Page 194 and 195:
[1.7 APPLICATION FUNCT.] (FUn-) [ST
Page 196 and 197:
Page 198 and 199:
[1.7 APPLICATION FUNCT.] (FUn-) [JO
Page 200 and 201:
Page 202 and 203:
[1.7 APPLICATION FUNCT.] (FUn-) [+/
Page 204 and 205:
Page 206 and 207:
[1.7 APPLICATION FUNCT.] (FUn-) [FL
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
[1.7 APPLICATION FUNCT.] (FUn-) [LI
Page 220 and 221:
Page 222 and 223:
[1.7 APPLICATION FUNCT.] (FUn-) [MU
Page 224 and 225:
[1.7 APPLICATION FUNCT.] (FUn-) [AU
Page 226 and 227:
[1.8 FAULT MANAGEMENT] (FLt-) [PTC
Page 228 and 229:
[1.8 FAULT MANAGEMENT] (FLt-) [AUTO
Page 230 and 231:
[1.8 FAULT MANAGEMENT] (FLt-) [MOTO
Page 232 and 233:
[1.8 FAULT MANAGEMENT] (FLt-) [OUTP
Page 234 and 235:
[1.8 FAULT MANAGEMENT] (FLt-) [THER
Page 236 and 237:
[1.8 FAULT MANAGEMENT] (FLt-) [UNDE
Page 238 and 239:
[1.8 FAULT MANAGEMENT] (FLt-) [IGBT
Page 240 and 241:
[1.8 FAULT MANAGEMENT] (FLt-) [FAUL
Page 242 and 243:
[1.8 FAULT MANAGEMENT] (FLt-) [TORQ
Page 244 and 245:
[1.8 FAULT MANAGEMENT] (FLt-) [AUTO
Page 246 and 247:
[1.8 FAULT MANAGEMENT] (FLt-) [DC I
Page 248 and 249:
Index of parameter names Name Code
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Index of parameter codes Code Name
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Index of parameter logic addresses
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Index of parameter CANopen addresse
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Index of parameter INTERBUS address
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Index of parameter DeviceNet addres
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390:
atv61_Parameters_EN_V1 2006-01
show all

Altivar 61 - error

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?