Simulation Module v2.0

[Dr Tallman]

Does anyone have any experience using the Simulation Translator (found in Simulation Module v2.0) to convert MatLab Simulink models to LabView? I am trying to convert the PHYSBE model which can be found at...

Physbe Model

Besides creating messy vi's with many broken wires, it created two sub vi's called

"CGD vectorSelectorNode.vi" which are password protected. They are the two white vi's in the diagram above. I cannot find anything helpful in the NI documentation. I would appreciate any insight. Thank you. btw, I am using LV 8.0.

Richard Tallman

Associate Professor

The Ohio State University

[reed]

Hi Richard,

I am one of the developers of the Simulation Translator, so hopefully I can offer some insight.

Have you installed the patch for the translator for the Simulation Module 2.0? It can be found here: http://digital.ni.com/softlib.nsf/websearc...62571250070D3EE

It should help with some of the broken wires, in particular. The subVIs just perform the correct selection operation, given the input indicies. They should not be password protected and I've filed a bug report to that effect.

HTH,

-Reed

[Dr Tallman]

Reed, Thank you for your help. I was unaware of the update. After rerunning the translation, the wires that were broken before appear to be fixed although several new broken wires have appeared.

I suspect that the CGD vectorSelectorNode.vi is the culprit. Thanks again.

Richard

[reed]

Richard,

I took a look at that model and the problem seems to be that the summation node with a single vector input performs a vector summation. The LabVIEW Simulation summation node does not work like that, yet. To fix those broken wires in that VI, I think you can replace the two summation nodes that are fed directly by the CGD vectorSelectorNode subVIs with the Add Array Elements node from the Numeric palette. There also appears to be a bug with the selector translation that is not creating a vector of indicies to pass into the 'i' term of the CGD vectorSelectorNode subVI. You'll need to create that to get the correct output. I've filed bug reports on all these issues. Thanks for bringing them to my attention.

-Reed