SiemensETIJohnson ControlsIFMSICKWIKABosch RexrothELKO EPHYUNDAIABBVEGAKSR KUEBLERAlfa Laval

Fault · SINAMICS G130, G150, S120, S150

F07517Drive: Encoder data set changeover incorrectly parameterized

What it means

F07517 is raised when the drive detects that the encoder data set changeover is parameterized incorrectly: in at least two drive data sets (DDS), the same motor data set (MDS) is assigned different encoder data sets (EDS) for the motor encoder. An MDS is not permitted to have different motor encoders in various DDSs, so the drive rejects this configuration with a fault. The fault value in r0949 names the two drive data sets involved, and the drive coasts down until the conflict is corrected and the fault is acknowledged.

Why it appears

  • In at least two drive data sets (DDS), one and the same motor data set (MDS) is assigned different encoder data sets (EDS) for the motor encoder — the drive does not permit an MDS to have different motor encoders in various DDSs.
  • Example of the disallowed assignment: DDS0 uses MDS 0 with encoder data set 0 (p0186[0] = 0, p0187[0] = 0), while DDS1 uses the same MDS 0 with encoder data set 1 (p0186[1] = 0, p0187[1] = 1).

What to check

  1. Read the fault value in r0949 and interpret it as a decimal number: the lower 16 bits indicate the first DDS, the upper 16 bits indicate the second DDS.
  2. In the two drive data sets named by the fault value, compare p0186 (MDS number) and p0187 (encoder 1 EDS number): the conflict is present when both DDSs use the same MDS while p0187 assigns different encoder data sets for the motor encoder.
  3. If the motor is to be operated once with one motor encoder and then with the other, set up two different MDSs in which the motor data are the same, so that each DDS has its own MDS. Example: DDS0: p0186[0] = 0, p0187[0] = 0; DDS1: p0186[1] = 1, p0187[1] = 1.
  4. Then acknowledge the fault and restart the drive as described under reset.

Reading the message value

  • The drive stores the fault value in r0949; interpret the value as a decimal number.
  • Lower 16 bits: the first DDS.
  • Upper 16 bits: the second DDS.

Parameters the manual names

  • p0186 — MDS number: shows which motor data set each drive data set uses; in the corrected assignment each DDS is given its own MDS (p0186[1] = 1 for DDS1 in the example).
  • p0187 — encoder 1 EDS number: shows which encoder data set each DDS assigns for the motor encoder; check that DDSs sharing one MDS do not assign different EDS here.
  • r0949 — fault value: read it as a decimal number to identify the first DDS (lower 16 bits) and the second DDS (upper 16 bits).

Acknowledging and restarting

The drive coasts down (OFF2) when this fault trips and must be acknowledged before it will start again. Acknowledging alone does not remove the cause: first correct the p0186/p0187 assignment as described above, then acknowledge the fault immediately and restart the drive.

The same on every family

Every manual that describes F07517 gives it the same reaction, acknowledgement and message class.

Drive familyReactionAcknowledgeMessage classComponentManual
S120, S150OFF2IMMEDIATELYError in the parameterization / configuration / commissioning procedure (18)NoneSINAMICS S120, S150 List Manual · p. 2838
G130, G150OFF2IMMEDIATELYError in the parameterization / configuration / commissioning procedure (18)NoneSINAMICS G130, G150 List Manual · p. 1574

The drives this code lives on

F07517 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 fault F07517 mean on a SINAMICS drive?

It reports that the encoder data set changeover is parameterized incorrectly: at least two drive data sets (DDS) assign different encoder data sets (EDS) for the motor encoder to the same motor data set (MDS).

How do I find the data sets that triggered F07517?

Read the fault value in r0949 as a decimal number: the lower 16 bits indicate the first DDS and the upper 16 bits the second DDS. Then compare p0186 and p0187 in those two DDSs.

How is F07517 cleared?

Set up two MDSs with the same motor data and give each DDS its own MDS — for example DDS0: p0186[0] = 0, p0187[0] = 0 and DDS1: p0186[1] = 1, p0187[1] = 1 — then acknowledge the fault and restart the drive.

Why may one motor data set not be used with two different motor encoders?

The drive does not permit an MDS to have different motor encoders in various DDSs. To run one motor with different motor encoders, the MDS must be duplicated with identical motor data so each encoder gets its own data set.

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 F07xxx group · SINAMICS manuals · Siemens manuals