I put to postprocessor the variable mom_toolpath_time, and for example it give me 82 minutes. But when the program goes on the machine, it takes a lot longer - about 200 minutes..I found two reasons of this. First when we use operation who had many rapid moves - here I have a question what is the default rapid speed in Feeds and speeds rapid output? How can I change this for exapmle 2500mm/pm (can't change to G1 becouse postprocessor gives me colision movements)
Secondary reason, in a advance shapes when i use contour area (now there is a few G0 movements but the g-code is much more larger with many lines of codes). I know that machine need a slow down and acceleration on shapes to cut material but is that some way to calculate this?
Solved! Go to Solution.
Here you can set how fast rapid motions are:
(You might be also interested in Tool Change time)
Referring to second question, you can take into account also acceleration and deceleration of the machine. You can do it in ISV. Obviously first you need to provide all this data specific to your machine like: max velocity, max acceleration and deceleration etc (for each axis!). Results might be very precise!
Production: NX 12.0.1
Development: C#, Tcl/Tk, CSE
The times reported in NX (vs. in IS&V) have always been "off"
Not just for accel/decel, but other things as well.
Converted an operation from deep hole drill (G83) to regular drill (G81) (Times from the "time" column in the ONT)
G81 operation time: 30 sec.
G83 operation time: 30 sec.
To quote the old "Laugh in" TV show: "Verrryyy Interesting!"
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled