Why am I unable to print a Simulink model that contains blocks from the SimMechanics Blockset?

Why am I unable to print a Simulink model that contains blocks from the SimMechanics Blockset?

There seems to be a bug in printing a model that has a SimMechanics subsystem Blocks.

If I chose "all subsystems" and "with frame" in the print setting dialog box, I receive

the following error report and third page doesn't have a frame.

 --------------

 Segmentation violation detected at Tue Apr 02 16:37:41 2002

 --------------

 Configuration:

 MATLAB Version: 6.1.0.450 (R12.1)

 Operating System: Microsoft Windows NT

 Window System:Version 4.0 (Build 1381: Service Pack 6)

 Processor ID: x86 Family 6 Model 8 Stepping 10, GenuineIntel

 Virtual Machine:Java 1.1.8 from Sun Microsystems Inc.

 Register State:

 EAX = 00000000EBX = 1ee9e928

 ECX = 00000319EDX = 00000462

 ESI = 00000000EDI = 00000000

 EBP = 01498694ESP = 01498694

 EIP = 019844b6FLG = 00010293

 Stack Trace:

 [0] gui.dll:_gwr_winMethods(0, 0, 0x014986dc, 0x0172cc03) + 6 bytes

 [1] gui.dll:_wm_PixelHeightPerIn(0, 0x02f66448, 0x01981d4c, 0x02f66448) + 13 bytes

 [2] hg.dll:_convert_matlabRect(0x01498708, 0, 1, 793) + 99 bytes

 [3] simulink.dll:_gg_PaperPosition(0x02f66448, 25, 0x1ee9e928, 0x1c322298 "PaperPosition") + 640 bytes

 [4] simulink.dll:_get_param(0x1ee9e928, 0x01c83d40, 0x01498828, 0x01dc9d20) + 535 bytes

 [5] simulink.dll:struct slErrMsg_tag * __cdecl get_graph_object_param(void *,char const *,struct mxArray_tag * *) (0x1ee9e928, 0x1c322298 "PaperPosition", 0x01498828, 2) + 60 bytes

 [6] simulink.dll:struct slErrMsg_tag * __cdecl get_param_switchyard(void *,char const *,struct mxArray_tag * *)(0x1ee9dc68, 0x1c322298 "PaperPosition", 0x01498828, 0x01a25724) + 133 bytes

 [7] simulink.dll:_matl_get_param(0x1ee9dc68, 0x01498828, 1, 0x014989f0) + 580 bytes

 [8] simulink.dll:void __cdecl slFullGetParam(int,struct mxArray_tag * * const,int,struct mxArray_tag * * const)(1, 0x01498828, 2, 0x014989f0) + 24 bytes

 [snip]

Answer 1

[MathWorks Support Team]

This problem has been fixed in SimMechanics 1.1 (R13).

If you are using an earlier version, there are no known workarounds.