Calibration failed
Platform: Process Simulate
This message appears when dynamics calibration fails for a specific robot. The user can choose to proceed with export without calibrated dynamics for that robot, or cancel to investigate and fix the calibration issue.
Dialog shown in Resolver
Robot: {robotName}Calibration failed:{reason} Continue without calibrated dynamics?
What you can do in this dialog
- Can you continue export? Depends on your choice
- Buttons in the popup: OK, Cancel
- What happens next: OK continues. Cancel stops the current export flow.
- Next step: See impact if you continue
Impact if you continue
Choosing OK lets export continue, but no dynamics limits are recorded for the named robot at all for this run — the connector does not fall back to any prior or cached dynamics data for it. Export simply proceeds without calibrated dynamics for that robot.
How to fix it
- Read the
{reason}text in the dialog. It is one of: "The controller status changed during the calibration." (the robot's RCS connection state changed mid-run), one or more specific simulation failures (for example, the robot could not be moved to its target or start pose for a calibration move), or the generic fallback "No dynamics data could be generated. See log for details." - Restore the prerequisites your calibration sequence expects—RCS connected, correct program mode, interlocks cleared—then rerun calibration for that robot in Process Simulate.
- If the reason persists, compare controller event logs with the step where calibration stopped; cancel export until calibration passes if your gate requires it.