What it means
The drive raises A01990 when the configuration of the process data (PZD) for the USS protocol is incorrect. Depending on the drive's configuration, the same condition can also be issued as a fault. Which case applies is shown by the alarm value the drive stores in r2124, interpreted as a decimal number.
Why it appears
- The configuration of the process data (PZD) for the USS protocol is incorrect.
- Alarm value 2: the PZD amount set in p2022 is too great for the first drive object (p0978[0]).
- How many PZD items a drive object can take is determined by the number of indices in r2050/p2051.
What to check
- Read the alarm value in r2124 and interpret it as decimal.
- For alarm value 2, check the amount of USS PZD (p2022) and the maximum PZD amount (r2050/p2051) for the first drive object (p0978[0]).
- Correct p2022 so that the set PZD amount does not exceed the number of indices in r2050/p2051 for that drive object.
Reading the message value
- The alarm value is stored in r2124 and must be interpreted as a decimal number.
- 2: PZD amount (p2022) too great for the first drive object (p0978[0]).
Parameters the manual names
- r2124 — alarm value; read it (decimal) to see why the drive raised A01990.
- p2022 — number of USS PZD; check this count, it is the value that is too great for alarm value 2.
- r2050 / p2051 — IF1 PZD words (CO/CI); the number of their indices determines how many PZD items a drive object can take, so compare them with p2022.
- p0978 — list of drive objects (DO); index [0] names the first drive object the PZD amount must fit.
Acknowledging and restarting
As an alarm, A01990 requires no acknowledgement. If the drive is configured to signal the same condition as a fault instead, the manual specifies: Reaction upon F: NONE (OFF1) Acknowl. upon F: IMMEDIATELY
— the fault is then acknowledged IMMEDIATELY.
The same on every family
Every manual that describes A01990 gives it the same reaction, acknowledgement and message class.
| Drive family | Reaction | Acknowledge | Message class | Component | Manual |
|---|---|---|---|---|---|
| S120, S150 | NONE | NONE | Error in the parameterization / configuration / commissioning procedure (18) | None | SINAMICS S120, S150 List Manual · p. 2724 |
| G130, G150 | NONE | NONE | Error in the parameterization / configuration / commissioning procedure (18) | None | SINAMICS G130, G150 List Manual · p. 1498 |
The drives this code lives on
A01990 is described for G130, G150, S120, S150. These are the converters of those families in our catalogue — price on request.
Questions technicians ask
What does alarm A01990 mean on a SINAMICS drive?
The configuration of the process data (PZD) for the USS protocol is incorrect. For alarm value 2, the number of USS PZD in p2022 is too great for the first drive object (p0978[0]).
How do I fix A01990?
Read the alarm value in r2124 as a decimal number. For value 2, check the USS PZD amount (p2022) against the maximum possible — the number of indices in r2050/p2051 — for the first drive object p0978[0], and correct p2022 accordingly.
Does A01990 have to be acknowledged?
No — as an alarm it needs no acknowledgement. If the drive signals the same condition as a fault instead, it is acknowledged IMMEDIATELY.
Which parameter sets the number of USS PZD?
p2022 (Field bus USS PZD). It must not exceed the number of indices in r2050/p2051 of the first drive object (p0978[0]).
Codes next to this one
Source
Written from Siemens' own List Manuals and operating instructions; every number, designation and parameter on this page is checked against them before publication.
All SINAMICS codes: fault and alarm codes · the A01xxx group · SINAMICS manuals · Siemens manuals