09-05-2013 10:39 AM
I have what I think is a silly question.
I am using LabVIEW 2012 with VeriStand 2012. When I edit a VI and save it as an lvmodel, I don't see the changes in Veristand. I wind up having to delete the model from the VeriStand project and add it again.
This is no big deal for models that have only a few inports or outports. But I am going to have much larger lists and it will be a real pain to remap every time I make an edit to the model.
I think I am missing something.
After poking around in one of the projects XML files, it looks like the issue is that there is another lvmodel file compiled for the RT target. (A cRIO 9025 in my case, but soon to be upgraded to a PXI.) So I am guessing that when I make my changes, Veristand is not making a new compile for the RT. At least not until I remove the existing model and add my model again.
Specific questions.
What is going on? Why do I have to remove and re-add models that I change?
What do I have to do to manage this? Is there a way to make changes to my models that don't require that I remap inports and outports every time?
Thanks!
09-05-2013 11:32 AM
10-17-2013 07:15 PM
I also encountered the same problem, it seems that the lvmodel file only support windows and ETS/RTX real-time platform, DLL was not recognized in Vxworks platform? Is that true?
10-17-2013 10:52 PM
Click the model in your sdf, and click the refresh button, but it can only update the model parameters, many changes can not be updated successfully.
You can save the mapings into a txt, and load it after you delete and add your model.
10-18-2013 05:16 PM - edited 10-18-2013 05:17 PM
Bryan,
LVModels can be used with VeriStand for Windows and PharLap targets only. This can be found in the LabVIEW Help Document "Using LabVIEW VIs as Models" here:
http://zone.ni.com/reference/en-XX/help/372846F-01/veristandmerge/model_from_lv/