Simulation Interface Toolkit Vs VeriStand

[ExcelX]

I am trying to use Matlab/Simulink models on a CompactRIO real time FPGA platform to run an ac motor.  Based on my research, I have two options: Simulation Interface Toolkit and NI VeriStand.  I would like to understand what are the limitations of Simulation Interface Toolkit and why VeriStand is the preferred method here.  I would most appreciate any suggestions. Thanks in advance.

[NAKeel]

Hi ExcelX,

The core difference between the Simulation Interface Toolkit and NI VeriStand is that NI VeriStand is a configuration based tool that allows you to import simulation models, DAQ/FPGA devices, etc. and map everything together out of the box.  The Simulation Interface Toolkit requires you to build LabVIEW code around your simulation model to perform additional functions.  NI VeriStand is preferred, because applications that involve simulation are typically quite complex, and NI VeriStand can significantly reduce software development time.  Here are some resources that can help paint a clearer picture of NI VeriStand:

NI VeriStand demonstration videos:  ni.com/veristand/demos

Importing Simulation Models into NI VeriStand: http://zone.ni.com/devzone/cda/epd/p/id/6488