Why would you want to do this? You may be a drive manufacturer who needs to issue vendor unique commands in between test steps. For example, you may have a vendor unique command to read data logged within your device – this data is extracted by a vendor unique command. To extract this data after a DMM read test you would use the DMM User-Defined Command function to define your CDB, then issue it and log the data that it retrieves.

Or perhaps you aren’t a drive manufacturer, but you are testing large volumes of SATA disk drives. In between test steps like Read or Write tests you could use the DMM User-Defined Command function to issue an ATA Task Register Command to read the drives SMART data or logs.

Or you could send a SCSI LOG SENSE command and record the number of corrected write errors.

Any command can be a test step. Valid commands or invalid commands. SCSI commands, ATA Task Register commands, 48-bit Task Register commands, or ATA Passthrough commands sent through a STB High-Capacity SATA controller.

You can send as many different commands as you need to, each command is defined as a test step and inserted into a DMM test sequence. And easy to use GUI lets you quickly define all aspects of all the different command types.

As each command is issued during the DMM test execution all information about the command is logged, including error information in case of a command failure, and data collection if the command has a Data In phase. Commands with Data Out can also be defined, with the data specified within a data file.

For a detailed walkthrough example see the training videos on our training page at http://www.scsitoolbox.com/Training/

Or contact us at (720)249-2641 and we will be glad to set up a live Webex session to show you exactly how to use this powerful new feature of DMM.