A01223 — CU: Sampling time inconsistent

A01223 is an alarm from the Control Unit (CU): a sampling time has just been changed — through p0115[0], p0799 or p4099 — and the CU has found the clock cycles to be inconsistent with one another. The value entered conflicts either with its permitted range or its required grid, or it cannot be reconciled with the sampling times of the other components and drive objects connected to the same DRIVE-CLiQ line. The exact reason is reported as a decimal alarm value in r2124.

• A sampling time (p0115[0], p0799 or p4099) was changed, and the check performed for this change identified an inconsistency between the clock cycles.
• Depending on the alarm value, the new value breaks a limit or a grid rule, does not fit isochronous PROFIBUS operation, or clashes with the sampling times of the nodes on the same DRIVE-CLiQ line, up to an inconsistency spanning several drive objects.

1. Check the DRIVE-CLiQ cables.
2. Set a valid sampling time in p0115, p0799 or p4099; the sampling time parameters can also be set with the automatic calculation instead of being entered by hand.
3. Use the recommended clock cycle in r0116[0...1] as the target for the corrected value.
4. When reworking the cabling, note the topology rules for connecting DRIVE-CLiQ given in the appropriate product documentation.

The drive stores the reason in r2124; read this value as a decimal number:

• 1, 2 — the value is below its minimum or above its maximum.
• 3, 5, 6, 7, 8 — the value is not a multiple of the required grid (1.25 µs, 125 µs, 250 µs, 375 µs or 400 µs).
• 4 — the value does not match isochronous PROFIBUS operation.
• 10, 21 — a special restriction of the drive object is violated, or the value has to fit the current controller sampling time of a servo or vector drive in the system (with TB30, all indices must be taken into account).
• 20 — on a SERVO with a sampling time of 62.5 µs, at most two drive objects may share one DRIVE-CLiQ line and they must all be of type SERVO.
• 30, 31, 32, 33 — the value is below 31.25 µs, 62.5 µs, 125 µs or 250 µs; 31.25 µs is not supported for SMC10, SMC30, SMI10 and Double Motor Modules.
• 40 to 46 and 52, 54, 56, 58 — the DRIVE-CLiQ line as a whole cannot support the value: the highest common denominator of the sampling times of the connected nodes is too small or differs between the components of the drive object, a chassis unit, chassis parallel unit, Active Line Module or Voltage Sensing Module (VSM) on the line forces a coarser grid, or one node's sampling time is not a multiple of the lowest sampling time on the line.
• 99 — an inconsistency between drive objects has been detected.
• 116 — the recommended clock cycle can be read in r0116[0...1].

• p0115[0] — sampling time for the supplementary functions of the drive object; one of the three values whose change triggers the clock-cycle check of A01223.
• p0799 — sampling time of the CU inputs/outputs; set it here to a value that fits the other clock cycles.
• p4099 — sampling time of the inputs/outputs; the third entry point for the value that must be corrected.
• r2124 — read the alarm value here and interpret it as a decimal number to see which rule the setting breaks.
• r0116[0...1] — shows the clock cycle recommended by the drive; use it as the target for the new sampling time.

No acknowledgement action is required. Once a valid, mutually consistent sampling time is set — and, where the cabling was touched, the DRIVE-CLiQ wiring is corrected — the alarm withdraws by itself. If it reappears immediately, the value entered is still not valid for the topology present on the DRIVE-CLiQ line.