not me.

something wrong i think, because i didn't lose mine and it doesen't sound like most did. but it seems that there are issues for some individuals after download regarding their particulars.(that's only based on what i've read here today.)

i'll bring the cheesecake!

mark,

there's an option for a side by side install.

i think that's what you need to do. there was some discussion earlier today on that too for further information.

plus, copy your libraries somewhere safe before you do it, and then you'll have them just in case.

ryan,

clarification: i'm certainly not suggesting you don't learn g-code. imho, anyone programming is better off having at least some understanding of it. but you probably don't have to learn it just to get a warmup for your machine.

mr2... added a stock setup and then tried to backplot an operation. even though the operation was showing a check mark in the box, i got a warning that no operation was selected.

couldn't do anything at all with the operation. this was all after i had been running mr2 all morning.

tried it a few times with no success until i actually changed something in the parameters. then the op was recognized and worked fine.

anyone else getting this.

seems like a lot of work for a warmup program.

someone will probably share if you ask, and maybe just modify a little if needed.

didn't you just ask this question regarding the toolpath display?

link to your recent post on the same question.

maybe you tried it, and it didn't work for you, if so, maybe keep trying on the original post to avoid confusion and re-asking the same thing.

from the backplot menu, select 'show path'. when the 'y' turns to a 'n', your toolpath will not be shown.

the switch is modal, so when you exit mc, whichever way it is, it will be that way when you open a new session.

wouldn't a read-only let them use the file, but not save it?

if so, it might still be modified by W.R., just not saved that way.

retrieve saved files that you have made tools in and save them(the tools) to a new or edited tool library. you may already have created all or most of the tools you need.

jeff,

if your'e convinced it's a machine issue, can you check the haas operators or programming manual. if your'e right, you should be able to nail it down and head in the right direction.

that's a drag man.

(someone had to say it! )

here's my v9 screenshot.

for me, a change of scenery is nice once in a while.

storkie, is that op manager using the 'x hook'?

trying to get this going a little bit, i don't have an interesting theme (hence the post), but i uploaded my colors to the 'text and post files and misc.'folder on the ftp as (bu-colors.rtf). it's in word format.

i did a search and didn't find anything closely regarding this. wondering if anybody else would find an option for color themes useful or desirable (similar to what you have in 'active desktop'). is there any interest in asking cnc for something like this?

until then, i think you can edit a config in wordpad to do something like this, so has anyone got a color theme they would like to share?

comments?

wouldn't different colors or levels work so you could manipulate these groups independently?

well put bruce.

randle,

i had some time to look at your file and while i didn't have any crashing problems, i did notice that your 3d wireframe path for a swept rad was quite slow on regen time. as an alternate method, i used the same wireframe (except exchanging a radius for the profile spline.)and swept a surface. using a flowline path, and posting both for comparison, the 3d was

2,552 kb, and the flowline was 690 kb. quite a difference and it showed in the verification time as well.

imho, a longer and/or more stubborn calculation is asking for trouble, and both the 3d, and highspeed paths you have seem to 'grind' more than they should have to.

that being said, i totally agree with thad regarding seemingly unneccesary workarounds, but as long as these things create problems (for me and my current hardware/abilities/whatever), i will try to figure out what works better for the time being.

hth

same here. doesen't seem to work consistently.

good luck randall.

hope things work out for you.

WOW!!!!

:choking on popcorn:

although the title may be somewhat negative, i still think this is a good thread.

this is a users forum and if crashing seems to be a problem for some, perhaps this thread can shed some light on the causes. the negativity aside, i think cnc should welcome the feedback (as they usually do) as a challenge to improve the product.

if there are a lot of crashes, or just a few, either way let the truth be told and see what shakes out.

goober, does this help?

A subprogram is an NC program that is called from the main NC program to repeat code (XYZ moves) that is repeated within an operation. Subprograms can reduce the size of the NC file. In the NCI file, the 1018 line marks the subprogram start and the 1019 line marks the subprogram end. This information is then passed to the post processor.

Important: Your post processor must be able to handle subprograms in order for this function to work. For assistance in making changes to your post processor, please contact your Mastercam dealer.

In Mastercam, subprograms fall into 2 categories: transform subprograms and non-transform subprograms. Both categories support motion with absolute positioning or incremental positioning in the subprogram.

Transform subprograms are created using Transform toolpaths. Each transformation of the selected toolpaths is a subprogram. These are the only subprograms available in Lathe. If you select the Subprogram option on the Transform toolpath parameters, each of the translations would be a subprogram.

Non-transform subprograms are created in Contour toolpath depth cuts, Pocket toolpath depth cuts, Facing toolpath depth cuts, and Circle mill toolpath depth cuts. These toolpaths can create repeating patterns that are made into subprograms. If you select the Subprogram option on the Depth cuts dialog, each of the depth cuts would be a subprogram.

Note: You cannot create tapered walls in a contour toolpath if you use subprograms.

Drill toolpaths can also create non-transform subprograms, but can be created 2 ways. If you select the Subprogram option on the Drill parameters tab, the entire drill cycle becomes a subprogram. If you choose the Enable subprograms in selected operations option on the Drill Operations dialog, the drill hole locations become the subprogram. Each drill cycle is repeated at the same hole locations.

Note: Subprograms are not yet available in auto drill or drill 5-axis toolpaths.

You can also create nested subprograms, where a toolpath that includes non-transform subprograms is transformed with subprograms. For example, a contour toolpath with depth cuts that are subprograms could be translated with subprograms.