quote: quote: -------------------------------------------------------------------------------- Makino, Yasda, Kitamura, Mori Seiki -------------------------------------------------------------------------------- Hey!!! You forget bout me already ?? Lets not leave out Okuma Ya'll forgot about Roku-Roku. And I'd take a Fanuc control over a Heidenhan without even thinking twice about it.

About the Renshape; it's abrasive on tools and equipment, and some grades are carcinogenic, so suggest taking steps to contain the dust / chips. Otherwise it's a nice material to work with, I've nc machined many foundry patterns out of it.

I agree there are several ways to work around this bug, but after many years of bashing software developers on various BBS's and USENET, I've had a change of heart and am trying to be cooperative for once. For the time being anyway. After exchanging a few emails with Pete Rimkus at CNC Software on other MC issues, I've come to find they appreciate any effort to help them squish bugs, and in a way it's kind of rewarding. Thanks for the suggestions.

Now that I know *I'm* not doing something wrong, yep, I'll send this off to QC. Thad, yes, the "gear looking area" was EDMed. Check your email.

]AOL[ You've got mail. ]/AOL[

Since I'm on a network that's locked down tighter than a gnats sphincter, uh, no, I can't put it on the FTP site. I am willing, albeit somewhat reluctantly, to email it to several people though....

MCX-MR2 I did a search on this and found a thread dated Sept 2005 and apparently it hasn't been addressed yet. I believe it is a bug. link I wrote a ruled toolpath and the rapid height I entered in the parameters is being calculated from the system origin, not my WCS. The toolpath is fine, the moves to and from the clearance plane is not. Since the system origin is "below" my WCS, I'm glad I was paying attention else I would have buried the spindle in my work piece. Surface toolpaths, 2d contouring and 2d swept toolpaths on the same part are all fine. Anybody else see this? Or am I missing something?

dotNET framework? We got .dll errors on a fresh MR2 install yesterday. Was installed on a computer that didn't have a prior version of Mastercam installed, from the installer downloaded from mastercam.com. Once the dotNET framework was installed afterwards, the errors went away.

The problem is after the dialog boxes for Analyze -> Position or -> Distance is open. If you try to analyze another position or distance when the dialogs are open, the power keys do not work. As Thad noted, it's being fixed in the next release, so no sense in beating a dead horse IMO.

MCX-MR2 I noticed the same thing with Analyze -> Distance, I lose the ability to use the power keys after measuring the first distance. It is indeed annoying.

quote: Makino ,we use them for graphite good machinesI'll take a Roku-Roku over a Makino any day for graphite.

In the ramp contour dialog, turn "Linearize helixes" off.

quote: After showing this thread to my chief, and after showing him how the guys at CNC blame everyone but themselves for shoddy work, I now have permission to purchase a new CAM package of my choice. His conclusion is that we simply cannot afford to rely on Mastercam anymore.. So Randle, tell us (there is no us), were you born that stupid, or did your mama make you take lessons later in life? Inquiring minds would love to know.

I'm currently working on solids imported from a .dwg file, and there were not any levels named "Outer Inner". I've also had it happen on imported parasolid files from Solidworks which doesn't support levels. Had more levels strangeness this afternoon too. I've been creating some lettering (geometry, not drafting) then X-form -> Drag -> Moving it, and it ends up on a level other than the current one. I started a new .mcx file (after a system reboot)and it didn't do it in it, but upon re-opening my current job I got the same thing. It's not the same level either, it gets sequentialy higher each time.

Oops.... MCX-MR1

I haven't yet been able to nail down the sequence of operations causing it, but when working on solids, level names have been changing themselves to "Outer Inner". This is occuring on the current active level and has happend to me on different jobs, seemingly randomly. Anybody else seen this?

MCX-MR1 I just noticed that if "Select from back" is active when working on solids, that analyze dynamic selects from the back also. Unless I'm missing something, I don't believe there is an option to turn "Select from back" off when dynamicaly analyzing a solid. I had to start a solids operation to turn it off first to get the correct behavior. Is this a minor bug sighting? Or not?

quote: On your file open window, the very last button on the right, click that and click use default directories. That option isn't available in the standard Windows file open dialog box. I guess I have to consider using the Mastercam dialog box instead... clickity, click, click, clickity, click, click... Well, I considerd long enough. I use more features in the Windows dialog than I would use in the Mastercam dialog. Looks like I live with the sticky data paths for now. :-/ [ 05-02-2006, 01:59 PM: Message edited by: Bob Heininger ]

16) After doing "File -> New" , data/file paths reset to what is configured instead of where the last files were opened from.

Yes, I know how to turn them on and off. Mainly what I don't like is them moving around when the graphics area is resized when opening and closing the operations manager. If they were displayed on the status bar, they'd be in the same place at all times.

MCX Does anybody else besides me think it'd be better to have the current Gview, WCS, and T/Cplane displayed on the status bar vs in the lower left corner of the graphics area? After all, the status bar is supposed to be just that...

quote: need some help i,e how to select a drill for helicoil tap. The tap-drill size is etched on the tap.

quote: When you did the 'pick spot on geometry' step, is there something there that made the AutoCursor find a position there? What shape did you see next to the cursor when you made that selection? Yes, and, center, or endpoint, or midpoint, etc., doesn't matter. quote: It sounds like we're simply snapping to that same location again when you make the 2nd pick, since they're so close. What shape do you see next to the cursor when making that selection?A point. Check your email in a bit, I'm going to send you some screen shots. I don't have access to the ftp server, or I'd upload them there.

Pete; Perhaps you're not creating a point, but the autocursor behaves as if there is one. Simple check; Switch to iso view, unzoom a bit, set construction to 2D, cplane to top, set depth well above all geometry, analyze distance, pick spot on geometry, Mastercam displays a (phantom?) point at set depth and autocursor displays point mode when placed over it. In my opinion, that point, be it real or phantom, shouldn't be pickable.

MCX-MR1 When analyzing a distance in 2D construction Mastercam creates a temporary point as actual geometry at the current depth on the current construction plane. I noticed this while analyzing the distance between the center of a hole and a point that was just a couple thousandths off from the center of the same hole. Using autocursor to pick the center of the arc, then trying to pick the point near that center to measure the distance, Mastercam was picking the temporary point created at the center giving me a distance of 0,0 which was wrong. I've never seen this type of behavior (temporary geometry created during analyze distance/position) in any CAD or CAD/CAM system I've used, or previous versions of Mastercam, and think it should be eliminated as it's going to eventually cause somebody some trouble.