Skip to main content

Mismatching Drive Command

Platform: Process Simulate

A WaitDevice command expects the device in a different pose than the one set by the preceding drive command, or it is owned by a different operation than expected. Resolver requires the drive and wait commands to agree, so it blocks the export.

Dialog shown in Resolver​

Modelling error! WaitDevice command {command} at operation {operationPath} is executed for destination device {deviceName} but with different pose from the preceding drive command {driveCommand}.

What you can do in this dialog​

  • Can you continue export? No
  • Buttons in the popup: OK
  • What happens next: The export does not continue until the drive and wait commands match.
  • Next step: How to fix it

Impact if you continue​

Export cannot complete while a WaitDevice command expects a pose that the preceding drive command does not produce. Resolver cannot reconcile the device's expected and actual state.

How to fix it​

  1. Open the operation named in the dialog and compare the WaitDevice command with the preceding drive command for the reported device.
  2. Make the poses match — either set the WaitDevice to the pose produced by the drive command, or update the drive command to reach the expected pose.
  3. If the message reports a different owning operation than expected, move the command so both belong to the same operation flow.
  4. Save the study and re-run export.