05-13-2019 02:52 PM
Previously...
I had a few Numeric limits, Pass/Fail, and String test steps to test DMM functions. The sequence has a simulation feature wherein the wrapper VIs will run the simulation class of DMM. The simulated sequence can also be configured to Pass/Fail. A Test step passes the sequence context to the VI, the type of step is determined, and a simulated value according to limits, Test step type, and pass/fail condition is sent out to the step. Simulating values were simple and could be used by many instruments.
Now..
I created custom steps by combining with default types. Reading the step type from sequence reference now provides the name of the custom step as expected. It is unclear as to how the simulation should now be changed to accommodate the custom steps.
05-14-2019 10:24 AM
It would have helped if you had provided example code of what you do that works and what you try to do that does not work.
My guess is that your simulator has some code that is called based on the step type names using the TestStand API function TypeOf(). You just need to add more code to cover the cases covering your own custom steps. You can probably make your code generic enough that when the simulator code is called for one of your custom steps, you call the code that you created for the corresponding standard steps.