Skip to main content

Missing Drive Command

Platform: Process Simulate

A WaitDevice command waits for a device that was never driven by a corresponding drive command. Resolver cannot resolve what the device should be waiting for, so it blocks the export.

Dialog shown in Resolver​

Modelling error! WaitDevice command {command} at operation {operationPath} is executed for destination device {deviceName} without corresponding drive command.

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 missing drive command is added.
  • Next step: How to fix it

Impact if you continue​

Export cannot complete while a WaitDevice command has no corresponding drive command. The device has no defined motion to wait for.

How to fix it​

  1. Open the operation named in the dialog and locate the WaitDevice command for the reported device.
  2. Add the missing drive command for that device earlier in the sequence, so the WaitDevice has a corresponding drive to wait for.
  3. If the drive command exists but belongs to a different operation, move it so it precedes the WaitDevice in the same flow.
  4. Save the study and re-run export.