Hi,
TestStand is a sequence editor and test executive. As it is shipped, it doesn't "know" how to send your strings to or how to read from ECU. For that, some device drivers must be called from the steps, as in the test system there is such device capable of sending/receiving commands to ECU.
Thus, an approach is to create/use the drivers in TestStand "Custom Steps" which are calling code modules which are using device drivers to exchange data with the ECU.
These "Custom Steps" must define a "place" at TestStand level to read/write the ECU commands/responses. Since you have to compare to expected values, the "Custom Steps" may be derived out of the "Tests" built-in NI step types.
For an example on how to create your own code modules and step types, consult the "TestStand API Reference", "TestStand User Manual", the examples shipped with TestStand located in the "TestStand\Components\NI\StepTypes" and "TestStand\Examples\StepTypes" folders on your harddrive.
Regards,
Silvius.
Silvius Iancu