I believe he's talking about the Cimco "CNC-Calc 2" package. My guess is you'll probably need to contact your Cimco dealer or Cimco themselves at [email protected].

I agree with gcode here. If this option is similar to Nurbs of other machines/controls, you need the positions of the control points for this to function properly. I'm guessing that you cut a spline, posted it, and trying to run that code. The increments are tiny that way. And although the toolpaths may appear "correct", this is what is causing the slow feeds because the control is calculating the spline based upon the points in the program. If you don't know the points, or you're generating from an existing file, then MC can create the points for you. First determine if the spline is parametric or nurbs. If nurbs, just go " create > points > Cpts Nurbs " and select the spline. If its parametric, then you'll have to convert first. Go " modify > x to nurbs " and select the spline. Now create the control points for a nurb spline. MC will program a nurb spline if you have the control points. You can program by selecting the control points using "Contour" toolpath. Then for the selection use the "Point" method. You have to select "point" each time for each point though. Otherwise you end up going point then accidently selecting some other type of chain. PS: if you knew this already, then just ignore me

I'm with John about the info. It'll depend on the cutting dia (a little bit anyway), tool hang out, depth of thread, accuracy of the machine. Only thing is in alum., I run them alot faster. Tons of rpm (10k + if you got it) and feeds around .0015 - .0025 fpt. Single pointing a 2.5-40 thread is gonna take a while even at a moderate depth, especially if you have to slow way down due to limitations mentioned above. I'd look into getting a multi-form thread mill to reduce the number of revolutions you have to make. If the quantity is small and/or infrequent, then its not much of an issue. If you have some volume though, the cycle times are going to stack up in a hurry..

Thanks Bob.... BTW.... I "knew" about the dynamite thing... I only used it once though by accident... then proceeded to forget about it... However... you still have to change back to 'Design' for it to actually remove the machine.

Paul, read the 'other' thread.... Bob from CNC has a solution and the answer to 'why it happens'... I checked it out and it works.

Ok Bob, here goes..... Default machine is NOT checked. Shortcut command does NOT have /M, /L, or /R As long as I'm in 'Design', the slate stays clean. However, is there a way to use 'Open' without having to revert to design first?.... or having to change to design after converting/opening a new file?? Not a big issue.... just lazy.. Noticed something else though too... How do I clear out the Op manager of any machines? If you have a machine there (even without any toolpaths), switching to design doesn't remove the machine. If I'm switching machines, I have to add a machine first, then go back to the initial group and delete it. And, this is also where the Machine Group Properties has problems. Some of the stuff will not stick from the defaults. In particular the "Tool Settings/Toolpath Configuration" stuff. Several of us here are

Now that you put it that way.... I guess you are selecting it in the same way... Just "different" ... and autocursor was always shut off since the menu prompts always changed with each step ..... LMAO realizing it....

All up to date.... yep. going to the toolbar works. right click to use autocursor menu (if you have set up that way) doesn't work..

quote: To select the end point in X of a suraces. Above the ribbon bar the third icon after the XYZ positions hit that and select Endpoint now select the surafce. +1000 David.. That did it.. Rob, are you talking about forcing it from the same icon as David mentioned in the toolbar? Because that works, but using the autocursor menu doesn't (at least not for me). I can force it to endpoints, yet it still acts like 'sketch'....

jctjct, this should still work in X for solids. I just did some this a.m. But it doesn't appear to work for surfaces anymore.....

I think so too,... check out the link I gave earlier. Theres some talk on trying to figure out whats going on with this whole thing.

Not to contradict..... In V9 you could pick the endpoint of a surface without curves or lines... this doesn't work in X. even Autocursor can't find it... Can't even analyze it... Seems like you'll have to generate edges...

quote: I'll keep thinking. Thanks Thad... (and others who'll contribute)... Glad someone is,... I'm fried.. 5 or 6 "mondays" a week going on and on and on and on.....

Thad, I don't see where I can set Design as default on start up. And "none" doesn't work. It errors out and says it can't find file "none.mmd" .... My MC cam "out of the box" with it set to "mill default.mmd" or something like that...

I draw the Maj Ø as ref then draw/cut the minor Ø.

In your system defaults, go to 'Files' and check the "Mill Machine Definition". The selected item is what its pulling when you're opening your file. There is a similar thread running about this stuff. Check here...

quote: If you open up in "Design," there is no MD or CD defined. Maybe you could make that your default That would ease up one problem... but how do I get the "New" to start with design? AND.... why is it that when you go to file/open, it always pulls the default machine def in the op manager? Somebody is posting a similar issue with a Rhino file. It does this no matter what file I "get", MCX or converted...

Yes. You can do whats called reverse posting. Basically you run the NC program through a "R Post" to generate and NCI file. From there, you import the NCI file into MC, then run backplot and click on a setting to "Save as Geometry". In MC, it creates geometry from all of the toolpaths.

quote: Just click OK and see what happens. It worked for me. Thad,... my no sticko.... As I said, it sticks locally (for the file) but not for default status. You said you close MC and reopen it sticks for you... I'm thinking that the one you're changing through CD happens to also be your default CD/MD. Maybe it works like that. I'm trying to get things to stick that is not my 'default' machine. As far as the comments that Rich made.... That would totally suck if thats the case. This would mean that I need to constantly change my system default in order to use a different definition with its defaults. quote: So if you set that machine to the same as you startup machine, you should be good to go. If I spent most of my time programming the same machine/control, that would probably suffice.... but I don't. I'll program several different machines and controls on a daily basis. Some files (as I try to create multiple machine groups) all pull the same "parameters" as the first machine or default machine even though they may be all set differently. On the same notion, I don't think that keying in "File, New" should automatically pull any machine in. The first thing I often end up doing is adding the machine I want to program just so I can delete the machine MC pulled up. I think you should be able to delete all machine groups to a "clean slate" in the Op Manager and when I go to a new file, it opens up clean.

Thad, I noticed that too except..... Then I get an alarm saying that it will not modify unless I go through the MD manager. And there lies the problem. So even in CD only, I can change it, but its only effective to that file as a "local" change. It doesn't write over the machine defaults.

Add to that...... I have an issue with trying to modify operation defaults as well. I'm trying to set up posts/definitions and etc for a dozen controls. I usually just create some bogus geo, toolpath it, then check the posted code and default status. But at some point, if I pull up another machine (or say I open X and grab a machine then decide to edit it), I lose the ability to select and change the operation defaults. It doesn't show up on the control definition list. The only way I can get it back to edit it, is to close MCX, then reopen MCX and before I do anything, go right to machine definition manager.

Mark, I have the same problems with the definitions to stick as well. In particular to the tool settings pages for different machines. It only seems to pick up the settings from the machine thats in the system default for start up. My questions have gone unanswered as well as a few other users here. Can anybody help or have ideas???

quote: If I am not mistaken the EIA/ISO may have been an option On M32/T32 and newer, it should be standard. The EIA/ISO conversion output (from mazatrol) is an option. CMT works with Mazatrol and its native output (like Camaix, Griffo, Solutionware, etc.). The same RS port used for CMT can be used for the TAPE I/O. You can output Mazatrol to 3-digit Gcode, but as Integrexman said, its difficult to edit unless you understand the codes. On Fusion control, the "%" sign can be sparatic for programs. Fusion is Windows operated so it essentially pulls in a file by something similar to "copy and paste" method of Windoze. You don't necessarily need the one at the end for that matter since you can literally drag and drop programs into the Fusion control if its networked. To start DNC on mazaks is different with each control version so you'll want to check the method of operation from the user manuals (if you have the option installed).

Sorry, copied from wrong update, its more like this for X: code: plin$ # Linear line movement - at feedrate 1 ss$,e$ sgcode, pccomp, x$, y$, z$, pfr, pcan,e$

quote: Are you sure your post is using ss$ and not speed? Sounds like you're using an older post thats updated. If that's the case, you're kind of on the right track, but you need to format prev_ss if you're going to use it. Another way around this, is to place "ss" at the beginning of each cut type. For example: code: plin # Linear line movement - at feedrate 1 ss sgcode, pccomp, x, y, z, pfr, pcan Just don't 'force' it. If the speed doesn't change, it shouldn't post it. I would update to a more modern post though. The "old" language can confuse some issues with newer systems.