Add virtual reality visualization framework to block diagrams
updates the Simulink® system (model or subsystem) that the Simscape™
smimport (Simscape Multibody) function generates.
The model must be on the MATLAB® path or already open prior to calling the
You can then save, rename, modify, and run the model. When you save the resulting model, be sure to preserve the relative path between the Simulink system and the virtual world 3D file.
To update the model
four_link using the file
To update the subsystem
using the VRML file
four_link.wrl, ensure that the model that contains
the subsystem is open, then:
Update Current System
To update the current system using the file
virtualWorldFile — Virtual world file
.wrl file |
.x3d file |
Virtual world file, specified as either
.wrl extension is optional for a VRML virtual world file. If
the specified system was created with Simscape
Multibody First Generation
smimport (Simscape Multibody) function, you can specify also an
.x3dv file for the
vrphysmod adds additional blocks to visualize the
mechanical system in virtual reality. The association between mechanical system bodies
and corresponding nodes found in the virtual world 3D file is based on the name
If your model contains several VR
Sink blocks that refer to the same
function attempts to consolidate the animation signals of that virtual scene into one VR
system — Model or subsystem to be updated
Model or subsystem to be updated, created by the
smimport (Simscape Multibody) function.
The SolidWorks® VRML export filter does not preserve part instance names and the part
order in the resulting virtual world 3D file. Therefore, the association between
such parts and the corresponding bodies in the block diagram is not always an exact
match. In such cases, the function identifies nodes with partial matches and issues
warnings. To prevent these warnings, ensure that node
in the virtual world 3D file are identical to their corresponding bodies in the
Simulink model before running this function.
If you receive this warning and the set of virtual world 3D files does not originate in the SolidWorks product, ignore the message. Other supported CAD tools also generate part names with similar names, but preserve them across different export formats.
Introduced in R2009a
smimport (Simscape Multibody)