Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

ProductDevelopmentGuy

CNC Software
  • Posts

    385
  • Joined

  • Last visited

    Never

Everything posted by ProductDevelopmentGuy

  1. That sounds an awful lot like something we fixed in V9.1Sp2. It specifically corrected the case where one circle is inside the other. Are you up to SP2 yet? PDG
  2. You can get planar section curves on the solids by using Create/Curve/Slice. You can also use Solids/Next/Trim/ToPlane to trim the solid to some plane PDG
  3. It is a bug in some of the 5axis toolpaths that we keep thinking is fixed. There's a lot of temporary geometry creation going on in some of the 5axis functions, and we've been inadvertantly leaving them around. We'll keep trying. PDG
  4. I tried Analyze/Surfaces/TestNormals and it identified 6 strange looking surfaces. PDG
  5. Thank you Ezra. MC9RS.DLL is not a C-hook. It's accessed automatically by the Mastercam .EXEs to get dialog text and buttons, etc. And please note that the newer than V9.1 version (newer than Feb 2003) circulating out there (with the bigger spaces between the OpMgr buttons) was not modified by CNC Software, but it is indeed changed with our permission. PDG
  6. One tool you can edit a Resource .DLL with is VisualLocalize. It's what most of our foreign resellers use to translate dialogs to their native language. PDG
  7. 1) I just uploaded a new IGESIN.DLL to the Apps_files sub-folder of the Mastercam_forum folder on the forum FTP site. Please drop this into your Mastercam "APPS" subfolder and let me know if your Rhino IGES files now pass the level information across succcessfully. 2) Zero - We've been looking at your Rhino importer trimmed surface problems, but you're probably right - maybe if a few more squeaky wheels get involved, we could push it up higher on the priority stack. PDG
  8. You can also save the named levels from a part to an external file. In the Level Manager (the "Levels" button or Alt-Z) you can right click and choose "Save Named Levels". Later, when you have a new or different part, you can go in there again and choose "Get Named Levels". PDG
  9. When reading in a DWG/DXF file that contains 3D solids, we extract the SAT solid data (Autocad solids use the SAT file format internally) and run it through our SAT importer. We give you that choice so that, if you want, you could read in the SAT data separately. Most users just say 'yes' PDG
  10. Jay's right. It will work. It's not really prompting for a "point", but it's prompting for a location on the chain to start at. PDG
  11. If you've got SP2 and the SW2004 add-on installed and you still can't read it in, please e-mail it to me at [email protected] and I can take a quick look at it for you PDG
  12. Those of you who are having trouble reading in DWG/DXF solids in V9.1Sp2, please check the dates of the following files: c:(Mastercam folder)CommonDataSPA*.dll c:(Mastercam folder)CommonAppsSATIN.dll c:(Mastercam folder)CommonAppsDWGIN.dll And how did you update to SP2? PDG [ 10-30-2003, 04:30 PM: Message edited by: ProductDevelopmentGuy ]
  13. A minor diversion.... Elad - I emailed you a C-hook you can try which will attempt to join selected entities. So you can read in the Pro/E file and then invoke the C-hook and voila - all your 180 arcs are joined to make full circles where possible. Put it on the FTP site if you like it. PDG
  14. Bullines, How about .Net-Hooks? Also, regarding the VBScript Help, in the VBScript editor we provide everything you need is available in the 'Help' pulldown menu. PDG [ 10-28-2003, 04:41 PM: Message edited by: ProductDevelopmentGuy ]
  15. Or.... After you've selected your surfaces and your radius, click on Options in the menu and click 'Fillet Both Sides' on. This will search for all possible solutions and allow you to delete the ones you didn't want. Of course, if there's only one solution, it'll find that one, and you didn't have to worry about normals facing each other. PDG
  16. After seeing these posts, I was just about to put the Levels C-hook up on the FTP site, and someone beat me to it. It's zipped up in the C-Hooks subfolder. PDG [ 10-10-2003, 09:12 AM: Message edited by: ProductDevelopmentGuy ]
  17. Maybe you're having trouble because you installed Design Tracker when you didn't need to. If you've already got Inventor installed, DT is unnecessary. Try uninstalling it. PDG
  18. My simple answers: 1 - big IGES files need big Database allocations. 2 - there have been fixes for this type of thing in V9 & V9.1. Please consider updating. PDG
  19. If you mean that you're now seeing "Cannot move geometry that is used to make a solid" (or something like that) messages that you haven't seen before, there is indeed a bug in V9.1Sp1 that will make this happen more often than in V9.1. It has been corrected in V9.1Sp2. PDG
  20. JG, You still did not tell me WHEN this message comes up. Erich, Are you saying that anytime you're working with a solid you need to take those extra steps? Do either of you have other Parasolid products on your computers (SolidWorks, UG, etc)? Have either of you tried V9 yet? I don't recall any V8 bugs like this! PDG [ 09-23-2003, 01:15 PM: Message edited by: ProductDevelopmentGuy ]
  21. Actually it is a bug that has been fixed in V9.1Sp2. When I saw "Entity: Body Counted: 1704 " I realized that it looked familiar. There are 1704 solids in the file - each one gets written to a temporary SAT file in order to be read in. We were accidentally doing lots of file 'open's without any 'close's, and we found that there actually can be a limit to the number of files you can have open. PDG
  22. Please feel free to send this (very reasonable) request to [email protected]. PDG
  23. And... It always looks for a file named "SHEETAS.MC9". You can put whatever border and title geometry and/or text you want into a file of that name. Note that it assumes the template sheet is "A" size paper (8.5 x 11) and will scale accordingly to fit the requested paper size if it's not "A". PDG
  24. Did it work in Sp1 for you? When you updated V9.1 to V9.1Sp1, did you download the 'App'-related patch? What are the date and size of SATIN.DLL (in your 'Apps' sub-folder)? PDG
  25. It's in the basic AutoCAD file importer for V9.1 SP1 and SP2. The only thing we can't support yet is 2004 files with Solids in them. So if you've got AutoCAD solid entities in your file, you still will need to output as an earlier version. Contact your dealer to get SP2. PDG

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...