A
A.1 Parameter list
A-848
Siemens AG 2005 All Rights Reserved
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
1735 Processor utilization
Min Standard Max Unit Data type Effective
– – – % Unsigned16 RO
... continuously displays (online) the processor utilization and provides information about the
available computation time reserves of the processor.
The processor utilization is essentially dependent on the number of axes, operating mode and
cycle setting.
P1735 > 90 %
If, after start-up (optimization), this is displayed as ”normal status”, then there is a high danger
that if additional computation time-intensive functions are selected, the processor will be over-
loaded (e.g. measuring function).
Note:
If processor utilization is too high it can be reduced by increasing the clock cycles (refer to the
index entry ”cycles”).
P1735 < 90 %
From experience, there are no problems here, so that later (e.g. when troubleshooting), supple-
mentary functions (e.g. measuring functions, trace functions) can be temporarily activated.
1736 Test, rotor position identification (SRM SLM)
Min Standard Max Unit Data type Effective
0 0 1 – Unsigned16 immed. (SRM SLM)
To check the rotor position identification, using this test function, the difference between the cal-
culated rotor position angle, and that currently used by the control, can be determined.
1 The rotor position identification test has been activated
––> the difference is entered in P1737
0 The test has been completed (initial status)
Note:
refer under the index entry ”Rotor position identification”, ”PE spindle” or ”Linear motor”
1737 Difference, rotor position identification (SRM SLM)
Min Standard Max Unit Data type Effective
– – – Degree Floating Point RO (SRM SLM)
Note:
also referfor P1736 and under the index entry ”PE spindle” or ”linear motor”
The rotor position identification is described in:
References: /FBA/, Description of Functions, Drive Functions, Section DM1
1738 No. of data backup operations in the FEPROM
Min Standard Max Unit Data type Effective
– – – – Unsigned32 RO
Note: Internal Siemens
1739 You must save in the FEPROM
Min Standard Max Unit Data type Effective
– – – – Unsigned16 RO
... displays that at least one parameter was written into and the value was not yet saved in the
non-volatile memory (FEPROM).
1 Must be saved in the FEPROM because parameters have been changed
0 Need not be saved in the FEPROM
04.05
To Next Page
Loading...
