![TR-Electronic MP-200 Скачать руководство пользователя страница 137](http://html.mh-extra.com/html/tr-electronic/mp-200/mp-200_user-manual_1146662137.webp)
Printed in the Federal Republic of Germany
TR-Electronic GmbH 2016, All Rights Reserved
09/29/2020
TR-EMO-BA-GB-0022 v03
Page 137 of 153
10.10 Cyclic synchronous modes (operating modes 8, 9, 10)
These modes are implemented according to the Drive Profile CiA DSP-402.
The position offset 0x60B0 is evaluated only in the operating mode
“Cyclic sync position mode (CSP)”.
The velocity offset 0x60B1 is evaluated in the following operating modes:
-
Cyclic sync position mode (CSP)
-
Cyclic sync velocity mode (CSV)
The torque offset 0x60B2 is evaluated in all three operating modes:
-
Cyclic sync position mode (CSP)
-
Cyclic sync velocity mode (CSV)
-
Cyclic sync torque mode (CST)
The target values and offsets are evaluated only on changes. Therefore it is possible
in the CSP mode to send a target position and a velocity offset to travel smoothly
between the position set-points. However if there are no new values and the velocity
offset was not set to 0, the drive will never stop, regardless of the software position
limits 0x607D.
The status bit 11 "Internal limits active" is set, if any set-point exceeds its limits, or if
the torque reaches its limits.
The digital input bits 2
0
and 2
1
or limit switches are ignored. It is up to the responsibility
of the bus master to consider them, when it calculates the target values.
Following errors are handled in the operating modes CSP, CSV and PP (Profile
Position Mode). Also the status bit 13 "Following error" is set accordingly.
Decelerate with intermediate stop ramp is handled in the operating modes CSP, CSV,
CST and PP and controlled by means of the control bit 2 “Quick Stop” in the control
word 0x6040. The control bit 8 "Halt" is always ignored.
However currently all option codes for slowing down and stopping are ignored
completely. Instead the drive is turned off immediately.
The "interpolation time period" 0x60C2 is not yet supported.
10.11 Backup-EEPROM, runtime
All data are stored both in the main EEPROM and in the backup EEPROM. If one of
them fails, it is still possible to recover the data from the other one.
The total runtime of the device is stored every 3 minutes alternating in the main
EEPROM and the backup EEPROM. It can be read from the object 0x6508.
Every store operation to an EEPROM triggers a complete verify of both of them.
Therefore every 3 minutes the EEPROMS are completely verified, due to the updated
runtime. If invalid blocks are found, the related emergencies are set.