10-25-2013 07:30 AM
I have a need to integrate a Matlab/Simulink model into LabVIEW. Luckily I saw that NI has a few options. Recently NI had updated their toolkit and call it the Model Interface Toolkit and include it with Veristand 2013. So I downloaded Veristand and installed the toolkit. I then went to the Example Finder and opened the MIT User-Interface with F-14 Model to see it work.
The problem is the VI is broken, and reports "This VI or item belongs to a library that is in evaluation mode." Well yeah so what I want to evaluate it to make sure it works with my stuff before buying it, isn't that the purpose of an evaluation? This seems like a bug that VIs won't run in evaluation mode. That would be like evaluating LabVIEW but not have a run button. What good is the evaluation?
Can someone at NI help me to get a working evaluation of the Model Interface Toolkit before I decide if the product is right for our application? Thanks.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-28-2013 08:21 PM
That sure seems odd to me.
Can you verify that you have the NI LabVIEW Control Design and Simulation Toolkit installed and activated with the NI LabVIEW Model Interface Toolkit in evaluation mode?
Do other examples work?
I'll be doing some testing on my end as well to see if this is expected or not.
Please call in to your account representative if you want more information about options with the evaluation.
10-29-2013 07:21 AM
I must be missing something here. So for all other LabVIEW toolkits I've ever used, you download it and install it. During the install on the newer ones they will say, do you want to enter your serial number or just run in evaluation for a little while. I selected evaluation which gave me 7 day with the option to extend. When I launch LabVIEW it shows that the Module Interface Toolkit is installed and in Evaluation (2 days remaining at the moment). I choose to Launch LabVIEW anyway. Every example in the Example Finder that uses the Load Model function is broken. This is all examples other then the "Importing Model and Setting Light.vi" example.
I do not have the Control Design and Simulation Toolkit installed. Is it requried? I don't need to make simulations I need to control already made models which is what the Model Interface Toolkit looks like it does. Thanks.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-29-2013 07:32 AM
The F14 example does need the CD&Sim toolkit as noted in the Requirements section in the comment in the front panel. This is becuase the Model uses one of the CD&Sim solvers internally.
Try running some of the other examples which do not require the Control Design and Simulation toolkit and see if it works properly.
10-29-2013 07:39 AM
I see the requirement on the front panel, but the Example Finder only lists Model Interface Toolkit as a requirement. The Load Model.vi is the only thing broken in the example when opened.
Event the MIT Get Model Information.vi is broken. Again I will state any example using the "Load Model.vi" will be broken, because that VI is broken. It states "This VI or item belongs to a library that is in evaluation mode." in the Error List. Just dropping that VI from the palette will cause the VI to be broken.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-29-2013 04:17 PM
After replicating this I agree with your thoughts, I'm looking into why this is the case.
In the meantime you should be able to contact your account representative to work out a temporary license as I mentioned before.
10-30-2013 04:21 PM
Scratch that, I got my computer to have a proper trial license and that VI is executable. I've also confirmed that the Model Interface Toolkit is designed to be useable in evaluation mode and confirmed this with R&D.
Could you create a support ticket through your account so we can work on this more closely? It sounds like the software on your computer is the culprit here!