Status window / cutting conditions

Volkov · 2005-02-17 09:06:00

When turning on "cutting conditions' graph to be displayed i can see some extremums (max values of some parameters).
How to determine the location into NC program according to the extremum (or any other point of graph)? Now the information about time and parameter value only available:

Volkov · 2005-03-24 09:56:00

Doesn't anybody know how to use specified information?
What practical meaning have this feature?

bamiller · 2005-03-25 13:51:13

I have a question along the same line. When I run these graphs, many times portions of the program are running at the max/min allowable value of the parameter. The scary thing is, when the values are changed dramatically, they still seem to go to the changed value. Our standard feed rate is around 800mm/min on HSM, which we use on most smaller cutters (1.0mm). Sometimes we run this way, without optimized files, but we are not breaking cutters or anything, and get good life from a cutter, so I question the validity of the graph. My hope is also that we can look at what point in the program is having the extreme values, and see what is cutting at this point, as a learning tool, but I can not put my finger on what the problem is with the values. Our normal min feed rate in Optipath is 400mm/min, but I see instances where if I turn it down to 50mm/min, Optipath still will dip down to these feed rates at times for chip load/MRR values. We end up no where near our recommendations from our cutter supplier.

Also, seems like to run the graphs takes an extraordinary amount of processing power. Does Vericut have a min. system requirement they recommend for this function?

GeneG · 2005-03-26 00:14:15

Customers use this information differently, however, the general purpose is to provide graphical information about what is happening with the tool in the workpiece. I have found this feature valuable for learning what cutting conditions are encountered, as well as how programmers vary feed rates for differing cutting conditions and what upper/lower limits are.

Yes, it can (and probably will) have a negative impact on performance to have this window open constantly during processing. It would be better to open the Status window at the start to get an idea of what is going on, then close it and run a portion of a tool path, then reopen it later to get more data. I use the same technique with the scrolling tool path window (Info > Toolpath).

Pointers:
1.) Displaying 2-4 graphs seems to be managable. However, too many graphs can be difficult to follow (may look more like a seismograph during an earthquake).
2.) Make sure your graph Min/Max values suit what you are watching. For example, if you expect cut depth not to exceed 20 mm, try setting the Max value to something slightly more, such as 25 mm. That way if the graph spikes to the top you know you're "in over your head".

Finally, I agree that the graph would be even more useful if linked to the tool path (thanks for the suggestion). This would facilitate fast and easy identification of tool path records responsible for graph "problems". An enhancement request will be entered for this. The Toolpath Review window demonstrates some of this behavior, and has been received quite well by VERICUT users. --Gene

VERICUT Users' Forum

#1 2005-02-17 09:06:00

Status window / cutting conditions

#2 2005-03-24 09:56:00

Re: Status window / cutting conditions

#3 2005-03-25 13:51:13

Re: Status window / cutting conditions

#4 2005-03-26 00:14:15

Re: Status window / cutting conditions

Board footer