Showing results for 
Search instead for 
Did you mean: 

No signal available from simulink model in Veristand 2021

Go to solution

I'm currently using Simulink (Matlab 2020A) models in Veristand 2021 SP2 on Linux-RT targets.

At first, we reused models from the Simulink toolchain for Veristand 2020 SP3, that builds a single .SO file, and loading model into vssdf explorer.

Now we have update the toolchain for Veristand 2021 SP2, that builds an .SO along with a .VSMODEL. In this case, the .VSMODEL must be loaded from the system definition view (not the vssdf explorer).


The problem is : although trying a lot of things, we found no way to include the signals that where present with the previous toolchain.


Please tell me where is the magic option, Thx in advance.

0 Kudos
Message 1 of 7
Accepted by topic author thumble

For .vsmodel's, VeriStand 2023 Q2 is the first version to support importing signals as VeriStand channels, so the behavior you observe currently is expected If you are unable to update to VeriStand 2023 Q2, which could be quite understandable, here are my suggestions:


  • Do you require signal access in VeriStand for debugging purposes or are you trying to map signals to other VeriStand channels like HW I/O?
    • If for debugging purposes, VeriStand 2021 R3 was the first version to support debugging a deployed and running model from Simulink via External Mode. VeriStand 2021 R3 only supported TCP/IP mode, so you could not view signals in referenced models however. In VeriStand 2023, we added XCP support so you can now view signals in referenced models as well.
    • If you are trying to either debug in VeriStand or use the signals as channels, you would need to move the signals to the top-level of your model and assign as an outport.
  • If you are unable to update to 2023 Q2 and the above suggestions are too cumbersome, VeriStand Model Framework is compatible with 2020A and still can produce a .so like you used in previous versions. While Model Framework is not getting new features and Simulink version support, it still is functional in newer versions of VeriStand. 
NI Product Owner
0 Kudos
Message 2 of 7

Thanks for the quick reply.


The purpose is only for debugging, but because of some issue with MAX we reverted from R3 to R2.


So, the latest solution would be the better in our case, but I wonder if I can install the model support for VS2020, since the hosting PC is running (and has to run) VS2021R2 and knowing I need also the MINGW compiler to build code for another embedded coder target.


0 Kudos
Message 3 of 7

Apologies for the delay.


Agreed, if you are unable to upgrade, then continuing to leverage Model Framework is likely the best choice for your scenario. We continue to support Model Framework, but there will be a limitation on Simulink version compatiblity Generally speaking, you can compile models in older versions and use those models in newer versions of VeriStand. The one caveat starts in VeriStand 2021 with windows models, since we changed from a 32-bit Windows engine to 64-bit that release.


Out of curiosity, what was the issue with NI-MAX that forced you to revert? Typically, we recommend customers upgrade to the latest minor release for a given version of VeriStand due to the added features, bug fixes, and continued support.

NI Product Owner
0 Kudos
Message 4 of 7

Hello, the person In charge of that point has left the company but I forward the question. I will reply ASAP.


I still have the concern of : can I nstall the model support for VS2020, since the hosting PC is running (and has to run) VS2021R2 and knowing I need also the MINGW compiler to build code for another embedded coder target. I fear to spoil my Veristand or Matlab installation.

0 Kudos
Message 5 of 7

This depends on what target OS you are compiling for

  • If compiling models for Windows, you must compile 64-bit libraries for VeriStand >= 2021. Before that version, only 32-bit Windows libraries were supported. Notably, the mingw addon you may be familiar with only supports building 64-bit binaries, so that is not the version compatible with VeriStand 2020
    • Note: you can likely install that compiler for your other targets, and then still use the MVSC++ 2017 compiler compatible with VeriStand 2021. The tricky part would be mixing and matching two different mingw.
  • For NILRT, it should not matter. VeriStand has supported 64-bit binaries for both versions and we use gcc to compile. 


NI Product Owner
0 Kudos
Message 6 of 7
I finally got a response. The person rememebers that the upgade to R3 updated some features of the LV system to their 2022 version and one big issue was the unability installing the LinuxRT targets using the MAX tool. This make us fear about probable side effects on our already developped custom devices
0 Kudos
Message 7 of 7