Skip to main content

Conflicting Drive Commands

Platform: Process Simulate

A device is driven again before its previous drive command was acknowledged by a matching WaitDevice command, or the drive command is owned by a different operation than expected. Resolver needs each device drive to be paired with a WaitDevice before the device is used again, so it blocks the export.

Dialog shown in Resolver​

Modelling error! Drive command {command} at operation {operationPath} must be followed by WaitDevice command of device {deviceName} before this device can be interacted with again.

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 sequence is corrected.
  • Next step: How to fix it

Impact if you continue​

Export cannot complete while a device receives conflicting drive commands. Resolver cannot determine the device's state if a new drive starts before the previous one is completed by a WaitDevice.

How to fix it​

  1. Open the operation named in the dialog and locate the drive command for the reported device.
  2. Add the matching WaitDevice command (for the correct device, and pose where applicable) after the drive command, before the device is driven again.
  3. If the message reports a different owning operation than expected, move the drive command so it belongs to the same operation as the preceding device interaction.
  4. Save the study and re-run export.