Ni.com is currently experiencing issues that may cause some pages to fail.
Support teams are actively working on the resolution.
Ni.com is currently experiencing issues that may cause some pages to fail.
Support teams are actively working on the resolution.
07-12-2012 09:39 AM
Hello,
Bevor I ask my questions I'd like to discribe my problem:
I would like to use VeriStand on a PXI-system for simulation only. The simulation includes different types of sources such as Maltlab-Simulink-models, MultiSim-SPICE-models and LabView-code for FPGA-programming. The Simulink-models are available as a dll-file, generated with "Real-Time-Workshop" and "Simulation Tool Kid". They are need to generate duty cycles, calculated via space vector modulation and to model the performance of a special inverter. The MultiSim-model will be transformed via a special VI into LabView-code. Than I'll be able to generate VeriStand-code (tools --> NI VeriStand --> Generate....). The PWM-duty-cycles from that aforesaid matlab-dll are the input for FPGA-LabView-code. That will be the input for the gate of the tansistors of the MultiSim-model. Means, the space vector modulation generates the gate voltage and the FPGA-code get it to the ports of the inverter-model.
I'm new in programming with VeriStand and LabView. I have no Idea how I can handle that. But NI said that it is possible. So my questions are:
Is it possible to use VeriStand with more than one Costum-Device and simulate it as one whole simulation. How I can link the different files.
If not, do I have to build a LabView-Vi, where all the different sources of models are included.
Is a walkthough or a user guide available, which I can use to fix my problems.
I hope you can help me out. I need it for my bachelor thesis very fast. So thanks your your attention.
Best regards André
Solved! Go to Solution.
07-12-2012 11:41 AM
It sounds like you have all your simulink and spice models able to be converted into VeriStand models (of VIs that you can covert to lvmodel). Once you have a lvmodel you import it into the Veristand project. You can set up if the model runs at startup or not and the rate. Once you have imported your models into the lvproject you use the mapping/connections tool to map I/O from one model to another and to user channels or calculated channels if need be. once you are connected up you can create a workspace to show and control your I/O. Then you can deploy your project to a PC or RT and control/monitor via the workspace. There are serveral examples included with veristand and other on the website (I am thinking of the helicopter simulation). Good Luck!
07-13-2012 09:14 AM
Hi joshe,
I didn't see that I can include only models at the model point in the project editor. I found that mapping editor you talking about so I will try to generate my simulation and design my workspace. I thought that I need a custom device to run that simulation, but its not neccessary. That's a nother thing I didn't know. So thanks for your help. If it's not runnig, I will ask more later.
Have a nice weekend.
By Andre
07-13-2012 09:41 AM
Glad my post helped. Good luck and keep posting questions, that's how we all learn.
07-17-2012 02:06 PM - edited 07-17-2012 02:07 PM
Here is a document describing how to create compiled LabVIEW models and import them into NI VeriStand:
http://www.ni.com/white-paper/12785/en
This next link is a more general page describing multiple model environments and their support in NI VeriStand:
http://zone.ni.com/devzone/cda/epd/p/id/6488
Some additional modeling environments are supported but not necessarily listed here since this is a growing list. Additionally, since NI created an open model interface strategy called the NI VeriStand Model Framework, it may be possible to connect new types of model sources into NI VeriStand without too much work. Then the Mapping Tool, as you found, does the magic by easily setting up the logical data connections between the models. You may also easily assign each model to individual processor cores which helps with computational speed for system level simulations.