SimMechanics™ and PTC Creo CAD imports

1 view (last 30 days)
hal9k
hal9k on 20 May 2014
Commented: Xing gao on 21 May 2014
Hi, I am trying to follow the tutorial as described in "http://www.mathworks.com/help/physmod/sm/ug/import-robot-arm-model.html". I managed to install everything without any problem. But after I exported the model, I am able to see the block but Mechanics Explorer is unresponsive and blank all the time. I made sure that all the stl files were there as well. The command window also displays about 3 pages of error. The first few lines looks like this
"Warning: Using a default value of 0.2 for maximum step size. The simulation step size will be equal to or less than this value. You can disable this diagnostic by setting 'Automatic solver parameter selection' diagnostic to 'none' in the Diagnostics page of the configuration parameters dialog Exception in thread "AWT-EventQueue-0" javax.media.opengl.GLException: Error making context current: 2001 at com.sun.opengl.impl.windows.WindowsGLContext.makeCurrentImpl(WindowsGLContext.java:169) at com.sun.opengl.impl.windows.WindowsOnscreenGLContext.makeCurrentImpl(WindowsOnscreenGLContext.java:66) at com.sun.opengl.impl.GLContextImpl.makeCurrent(GLContextImpl.java:134)...........
and so on. I don't know if Java has anything to do with it but I have also made sure that my Java is up to date.
  7 Comments
hal9k
hal9k on 21 May 2014
Edited: hal9k on 21 May 2014
Hi Xing,
Thank you so much for your answers. I figured out that the problem was due to some JAVA related inconsistencies. When I tested from my browser (chrome) it was still showing that I was using the most recent Java. Anyways I decided to uninstall and re-install it just to see what would happen.
First I uninstalled Java completely from the control panel. Then I installed the Java from chrome (chromeinstall-7u55.exe), but when I ran the .xml files I got the same errors. Then I uninstalled it and re-installed the Java 64 bit (jre-7u55-windows-x64). When I ran the xml files, they worked like a charm.
Although I still don't know the exact reason, I think it has something to do with the compatibility between 32 bit and 64 bit Java versions that was causing the whole problem.
Xing gao
Xing gao on 21 May 2014
Hi Kiran,
It's good to know you figure it out. Java stuff is always tricky..
Thanks for letting me know the solution which can be useful for me in the future.
Regards,
-Xing

Sign in to comment.

Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!