Simulink model import error

[cabala]

Sorry for the series of recent posts but having lots of consternation and wanted to keep subjects separated. 

This is my first time using NI Linux RT so I am a bit on the learning curve. My previous two Veristand deployments back in 2014 and 2017 used Pharlap and I had very few issues in the process. 

I have LabView 2024 Q1, Veristand 2024 Q2, and Matlab 2020a (with the VeriStand Model Generation Support 24.3 toolbox installed) and am trying to deploy to an NI PXIe-8862RT. Per all the compatibility charts, this seems to be ok. I had some problems getting the compiler toolchain working (see previous post) but was finally able to get models to compile by using the legacy 2017, eclipse toolchain.

I finally backed up to the simplest thing I could think of, compiled it and I still get the same error. Here is a super simple model and the associated error. I get the same error on my main model as well. 

[ZYOng]

The VeriStand IO blocks can be placed anywhere in the subsystem hierarchy and accessed as inports/outports in VeriStand. Use Simulink IO ports for the top-level model.

See the attached example developed with VeriStand 2024 Q2, MATLAB 2021a and VeriStand Model Generation Support 24.3

[cabala]

Thanks for the reply. I replaced the Veristand inports and outports with the Simulink input and output ports but it doesn't make any difference. Still get the same model import error as whatever I compiled is fundamentally incompatible with Veristand. 

The attached reference example has .dll but my tools are outputting .so files so I wasn't able to try the attached example either. 

[cabala]

It doesn't seem this section of the community forum is very active but I'm going to follow-up regardless so future folks with issues may or may not find this information useful. 

The use of Veristand inports/outports vs the built-in Simulink input/output ports was not the issue. Maybe it's best practice to only use the Veristand ports at lower levels in the model but it doesn't cause any issues. The issue was I was not importing the model correctly. In prior older builds the .dll models (running PharLap) were imported through the System Explorer but for the newer versions I have apparently the System Explorer does not like the .so models (running NI LinuxRT) and can't be imported that way. Instead in the diagram section outside the System Explorer, you click the SW button to the left and import the .vsmodel which is like a wrapper for the .so model. When I did that the model imported without issue. Haven't deployed it yet but at least it imported. Got to get the custom device imported next.

For reference there are these two articles, similar but different. Not really clear which one applies based on your tool suite. 

Feb 23: Creating Simulation Models Using VeriStand Model Generation Support Add-On - NI

Feb 24:  Creating Simulation Models Using NI VeriStand Model Framework - NI

I love NI knowledge base articles but there is no organization to them in the slightest. 

[joshe]

Thank you for posting this information.  It will definitely help as we eventually update to this new version of VeriStand.