What does everybody think of the new mechanism for invoking the post processor?

How many standard post come with Hypermill?

The general rule is that one complete 2.5D/3D postprocessor is supplied with each 3D CAM license for no additional cost.

The posts are driven off of OPEN MIND's rich neutral language called pof. These posts include standard canned cycle support, and single- and multi-job posting and packaging.

It is best to describe the exceptions this general rule off-line.

Multi-axis posts are available at standard prices.

AL

The new post mechanism has a field in the edit job list where you can put the name of the post processor you want to invoke and the path/name of the g-code file(s) you want to create. The option I use, lets you have the post automatically generate number-sequenced g-code files, one for each job step. There is a "create NC" check box in every job step. When you are ready to post out, all you do is invoke the "create NC" command and it will post every job step that has the create NC check box selected.

I usually make multiple parts on my mill at the same time. As an example consider 6 pieces of stock up on the bed at once. I often program job lists with over 50 job steps in them using 15-20 different tools. So you can picture the machine grabbing a tool and cutting on each part before moving on to the next part. I use a master conversational program on my mill that loops through each work coordinate and calls the g-code for each job step. I of course arrange all the job steps to minimize the number of times any particular tool is called. There is often a sequence of job steps all using the same tool. Each tool works on each part until it goes on to the next part.

Each posted g-code file has a tool change command at it's beginning. And on my mill that forces the head to return all the way up to the tool change height at the start of each job step. That is not efficient, in fact for some of my programs that can more than double the run time!

I know what you are thinking, just post out the groups of similar tool types in one g-code file. Yea,that is what I used to do but, I can do that but with this new software, it is a major PITA because they took away Tool Path Post Lite! There is no easy way to do it.

I suggest one simple solution to the problem, add a switch to the job list that lets the post processor automatically group all the contiguous similar tool posts into one g-code file. Who wouldn't want that anyway?


Dave

Dave

As you know there are 2 ways to generate nc files. Create-NC and hyperVIEW.

Sorting jobs by tool, ID and frames does exist. Optimizing by toolchange and frames also exists.

Selecting different parameters will also have an effect on the functionality of 'Create-NC' and 'hyperVIEW'

Please call me and we can talk offline

Best Regards
-doug

Open Mind added the NC-filename single-mode option so users could automatically get separate g-code files for each job step. Note that each file will always begin with an M06 command.

There may be several uses for having those separate g-code files but the use I wanted to implement is to call one tool to cut several work pieces (each at a different work coordinate) before calling the next tool. I do this to minimize the number of tool changes when manufacturing several parts at the same time.

So, what's the rub? Well, if I have several contiguous job steps all using the same tool, My machine makes a lot of wasted movements. It returns the z-axis to the tool change height every time it sees an M06, even if it already has that tool loaded. Because of that I can't really make use of the NC-filename single-mode option. That is a major bummer because it means I have to manually retype all the g-code file names and manually reissue the post every time I have to recalculate.


Dave