Why does my model throw a Physical Modeling assertion when using SimMechanics 2.5 (R2006b)?
1 view (last 30 days)
Show older comments
My model crashes in R2006b with the following crash dump:
------------------------------------------------------------------------
Assertion detected at Tue Oct 03 16:27:44 2006
------------------------------------------------------------------------
Assertion failed Forced Assertion: at line 304 of file ".\compiler.cpp".
Physical Modeling Assertion
Stack Trace:
[0] bridge.dll:_mnSignalHandler(0xffffffff, 0, 0, 0x79e5a2b5) + 355 bytes
[1] bridge.dll:void __cdecl ThrowAssertion(void)(0x00d1a84c "p¨Ñ", 0x00d1a208, 0x65737341, 0x6f697472) + 131 bytes
[2] bridge.dll:void __cdecl MATLABAssertFcn(char const *,char const *,int,char const *)(0x0f50c8b8 " Forced Assertion: ", 0x0f50c8cc ".\compiler.cpp", 304, 0x0f50c8dc "Physical Modeling Assertion") + 110 bytes
[3] mechanical.mexw32:0x0f49ecd7(0x13263140, 0, 0x7a4b659b, 0x0ef89fb0 "__ehhandler$??$_Uninit_copy@PAV?..")
[4] mechanical.mexw32:0x0f4dd8f4(0x13263140, 0x00d1a894 "À¨Ñ", 0x7a473457, 0x13263140)
<SNIP>
Accepted Answer
MathWorks Support Team
on 27 Jun 2009
This bug has been fixed in Release 2007a (R2007a). For previous product releases, read below for any possible workarounds:
The model crashes because some Body blocks have unsupported Body coordinate system (CS) names (e.g., elbow/INJ). Only names provided by the dialog are supported, i.e., CS#, where # is a nonnegative integer. It is possible that you have manually edited the block parameters to unsupported body CS names (INJ, SENS, etc...).
As a workaround in SimMechanics 2.5 (R2006b), rename all the Body CS's using the block dialog.
0 Comments
More Answers (0)
See Also
Categories
Find more on Applications in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!