请参考以下内容:
The
history behind MPT versus Simulink data objects is based on the
regular Simulink data objects being associated with Simulink and
Simulink Coder (although it was technically called "Real-Time
Workshop" back then), and MPT data objects being associated with
the more feature-rich Embedded Coder (then called "Real-Time
Workshop Embedded Coder"). As such, the features available for MPT
data objects were essentially a superset of those available with
Simulink data objects.
Although
the MPT data objects will be obsolete, the Embedded Coder-related
features associated with them will still generally be available and
will move into Simulink data objects from the point-of-view of our
source code organization, but their accessibility will still
require an Embedded Coder license. You can actually see one example
of this in the fact that "Memory section"-related features are now
visible in Simulink data objects, provided that you have an
Embedded Coder, even though they were originally only available in
MPT data objects.
As a
general rule, use Simulink data objects wherever possible, and use
MPT data objects only when he requires a feature that is not
available in the regular Simulink data objects. The two reasons for
this are:
*
Obviously, with MPT data objects becoming obsolete, his models will
be better prepared to be upgraded when MPT data objects are no
longer available.
* His
models will be more share-able: if he shares a model with a
colleague who doesn't have Embedded Coder, that colleague will
still be able to work with the model if it uses Simulink data
objects.
简单的说,我们之后的开发趋势是用Simulink Data
Object代替MPT Object,也就是会吧MPT中的内容merger到Simulink Data中,所以建议您使用Simulink Data
Object。
最新的Data Object Properties可参考: