MC-Basic:element.POSITIONERRORDELAY/zh-hans

From SoftMC-Wiki
< MC-Basic:element.POSITIONERRORDELAY
Revision as of 03:41, 27 October 2017 by Chi (talk | contribs) (Created page with "{{Languages}} {{MC-Basic |SHORT FORM= <''axis''>.PEDel |SYNTAX= <''axis''>.PositionErrorDelay = <''value''><br> ?<''axis''>.PositionErrorDelay |AVAILABILITY= All versions ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
语言: [[::MC-Basic:element.POSITIONERRORDELAY|English]]  • [[::MC-Basic:element.POSITIONERRORDELAY/zh-hans|中文(简体)‎]]

This property returns the delay, as a number of AnyBus cycles, between a position command and the position feedback for the calculation of the position error.

Typically this delay includes:

  • At least one motion bus sample for sending the command position to the drive.
  • Time used for motion preparation (micro-interpolation), typically it is one sample but could be less depends on the drive manufacturer.
  • At least one sample for sending the feedback position from the drive.

If using micro interpolation on the drive, this delay may change from 2 cycles (no micro interpolation) to 3 (with micro interpolation).

This properly must be explicitly changed when switching the micro interpolation mode on the drives. Otherwise, an erroneous position error is calculated.

Depending on drive manufacturer and type of the motion bus the sending and receiving delays can vary.

NOTE-Info.svgNOTE
It is important to note that the timing of internal feedback sampling inside the drive is not taken into account In all of the calculation we assume that position feedback is taken at the start of the motion bus sample, although it might be not true.

Short form

<axis>.PEDel

Syntax

<axis>.PositionErrorDelay = <value>

?<axis>.PositionErrorDelay

Availability

All versions

Type

Double (was Long in previous fw versions)

Range

1 to 32

Units

Motion-Bus cycle times

Default

2 (Assuming no microinterpolation)

Scope

Task or Terminal

Limitations

To set the value within a task, the element must be attached to that task (using the ATTACH command) and disabled (element.ENABLE = 0)

Examples

Axis
A1.PEDel = 3

Group
G1.PEdel =3

See Also