Identify the coordinate mismatch
In RobotStudio 2021, a target created for Rob2 can appear correctly in World coordinates and produce a valid MoveL path, yet synchronization with RAPID can generate an unexpected position in the target's CONST declaration. The reported case shows the intended World Y position as 2345 while RAPID receives the different Y value shown under the target's Parent reference.
| Inspection point | Observed result | Diagnostic meaning |
|---|---|---|
| Target in the station | Position appears correct | The visible station geometry alone does not expose the mismatch. |
| Modify Position: World | Coordinates are correct | This is the intended absolute position. |
| Modify Position: Parent | Y coordinate differs | This is the coordinate set observed in the generated RAPID CONST. |
| New target and path | Mismatch returns after synchronization | Deleting and recreating the target does not remove the underlying reference condition. |
Separate confirmed behavior from the suspected cause
The confirmed behavior is that the target has World and Parent representations, and synchronization uses the Parent-referenced values in the generated RAPID data. The evidence does not identify which station object supplies that parent reference or whether the condition was introduced by copying, changing, or saving an earlier station version.
A stale or unintended parent relationship is therefore a working hypothesis, not a confirmed RobotStudio defect. The fact that a newly created target reproduces the result suggests that the relevant state may exist above the individual target, such as in the active station structure or selected reference context. Determine the actual parent selection before changing RAPID coordinates manually.
Diagnose and verify the reference context
- Select the affected Rob2 target in the Targets and Paths browser and open Modify Position.
- Record the World position, then select Parent in the reference-coordinate drop-down and compare every component. Treat any difference as a coordinate-reference issue rather than a path-geometry issue.
- Check whether newly created Rob2 targets inherit the same Parent selection and discrepancy. Reproduction on a new target confirms that target deletion is not an effective correction.
- Before synchronizing, verify that the selected parent or reference context is the one intended for the RAPID target. The evidence does not provide the correct parent name, so do not substitute a guessed reference.
- Synchronize the station to RAPID and compare the generated CONST position with both recorded coordinate sets. Accept the result only if it matches the coordinate representation required by the robot program.
Do not overwrite only the RAPID Y value as the primary fix. A later station-to-RAPID synchronization can restore the Parent-referenced value while the underlying reference mismatch remains.
FAQ
Why does RobotStudio generate different RAPID target coordinates?
In the reported RobotStudio 2021 case, the World position is correct but the Parent position differs, and synchronization generates the RAPID CONST from the Parent-referenced figures.
Why does deleting and recreating the RobotStudio target not fix it?
A new Rob2 target and MoveL path reproduce the mismatch after synchronization. This indicates that the condition is not stored only in the deleted target and requires inspection of the inherited parent or reference context.
How do I verify a RobotStudio parent-coordinate problem?
Open Modify Position, record the World and Parent values, synchronize to RAPID, and compare the generated CONST against both sets. If RAPID matches Parent instead of the required World representation, correct the reference context before accepting the synchronization.