It just makes sense to post the files to a job setup linked folder that you want to use everytime you post a file for this job. So when you were programming another job and the operator comes in and says hey can you modify this, you make the changes to the program it and post the file, the post will post to that job's linked folder path in the job setup (currently not available) not the folder path you used last. (current scenario)     Same goes for the setup sheets. There should be a linked folder path for your setup sheets. Some users may use the setup sheet and program in the same folder some may not.   Just think of this situation - you have the same part programmed on 3 different machines. You have to remember the folder path for each machine.   To me this just seems logical and simple to implement. If the user doesn't set up a folder link in the job setup then nothing has changed from the current way the system works now. Show More

There are a lot of situations where you want to add extra "custom" information to an operation to use this in the post. If an operation has such a parameter you can let the post output different code:   Some examples to use a parameter: Coolant pressure to control a the speed of a spinjet Amount of smoothing that the control needs to apply Laser power Rotation direction preference for 3+2 Rotation angle of a turning tool (for face turning) Retract position after this specific operation Anything else you want to tell and operation ESPRIT shows the custom fields as an extra tab in the operation.   I know you can hack something to use the "notes", but you have to do all kinds of text manipulkations, its prone to error and you can see nowhere if an operation has a a note, so it stays invisable  Show More

In one of our recent meetings with the customer advisory boards, @Anonymous suggest we try and engage the community earlier on with things we are working on.  The idea station was suggested as a good place to do that.   Below is a concept to add searching to the post dialog.  What are your thoughts?   Show More

If I make multiple NC files for 1 setup I have to manually choose the filename. I can do 2 things: Choose a fixed name in the postprocessor Use the program-number from the postwindow   What I would like is a timecoded filename that contains some other options like you see in the window below. This would also make it possible to created multiple NC files with subsequent numbers.   If you also want to save time by automatically created filenames? Please vote   I also tried some intelligence in the postprocessor, but the filename is decided before any rules can kick in.   Show More

It would be great to see a  post processor option in the existing subroutine posts for the user to switch between local subroutines and external subroutines. For example, on Fanuc controllers this would toggle between a local subroutine being called with the code "M97 PXXXX" and an external subroutine being called with the code "M98 PXXXX", as well as changing the subroutine program titles from "NXXXX" (local, internal) to "OXXXX" (external). Currently I only see the option for external subroutines. Show More

How about a new field that is for Help Videos and Formulas, with pics, that can be used to auto calculate steps of toolpaths.   This way it is a quick one stop instead of trying to search out thru all the threads. ??? Show More

A Lot of times there is a situation when you need the spindle to move out of the way for removing clamps and adding fasteners to secure the part for the profiling operation ect.... removing chips, applying cutting oil for a tap. There are lots of reasons.   The only option we have now is to use the Manual NC Pass Through option. This requires the programmer to have the skill set to manually program the NC code in the Pass Thru function. As the UI note says only use pass through as a last resort.   So what I'm asking for is a Manual NC function called "Park Position" that asks the programmer for a X, Y, and Z park spindle machine position coordinates or part park position relative to the part again asking for part position coordinates. So that the post posts the code correctly eliminating the possibility of programmer error.   Example of code. G0G90G53Z0; G53Y0X-12.; M0;   May need the current tool to apply the H tool offset again upon the next approach as some machine controllers cancel the active tool length offset when using G53Z0 or G91G28Z0 retracts. Upon the cycle resuming the tool may run right into the part creating a crash without the active tool length compensation for the tool in the spindle.   This would also work for lathes parking the turret out of the way.   Some NC food for thought,   Greg Haisley     Show More