There are a few books out there which cover developing custom Macros, but you still need to understand how Productivity + processes everything. There just is no substitute for training from people who really understand the system.

I recently bought a couple of HP Z books. 1: Latest gen i9 64G RAM A2000 card Win 10 Pro It runs MC surprisingly well, even on toolpaths with lots of processing. 2: Latest gen i7 128G RAM A4000 card Win Pro 10 I don't need to get a stopwatch out to tell which is more powerful, just goes to show, MC is RAM and Cache hungry.

Have you talked to Renishaw? I have always found them to be very helpful.

One of the great features of blend is the ability to project from a different construction plane from the tool plane. I don't use it often, but this is a situation where I might try it.

The important thing is the effective chip load. The calculated chip load will likely be too light due to chip thinning. It is sometimes a little scary how fast you need to go. As JP says, more info will get a more accurate response.

Yes, you can have custom entries in x coolant. And you can get rid of some of the choices. Not sure about Before, With and After. It's been a while, I will review my x coolant code this weekend and do a post if you still haven't had any help. I am not using my posts at this job. All 5 ax with DWO at the moment.

Offset (enlarge) your boundary until it cleans up.

So, you have numbers but no labels? What happens if you remove the numbers? Make a copy of the operation and change that one and see what difference if any is in the output. Sounds like a half-baked post edit. You will need to post a Z2G to get useful help.

And it is impossible to help anyone....who knows everything already. By definition.

It's a handy work around. Just brings in what you need.

Get your design team to send you a parasolid (.x_t or .x_b). This is the most reliable transfer protocol between systems. SW assemblies are often difficult, this should solve the problem.

To be fair I interpolate holes to =/- .0001- .0002, so they are just being a bit economical with the truth. Re-probing and re-touching critical tools, might help, but I might be tempted to run Productivity+. Then you can probe for stock. This might also require re-calibrating the probe. Contact Renishaw for the straight skinny on this, I have always found them to be very straight forward. Monitoring your spindle growth through the process might just do the trick as well. Once the spindle grows, does it stay there for the rest of the shift? As long as you don't shut it down too long before starting the unattended work you might get away with it.

I have it from a reliable source that the main problem is that Haas has multiple parts sources. When you by a Mori or Matsura or other primo machines they have one type of widget, which has been selected specially to work well with all the other widgets. Haas sources the same widget from multiple companies and throws them in a big box in assembly, so the system is not as tightly regulated and also not as "tight".

Haas Z axis are notoriously unstable. I am running an UMC 750 and the spindle often grows 0.002 through the day.

I am completely shocked by this omission

If you look in the what's new section of the 2018 MP docs, you will find a list of updated parameters for the tool page. Not all the fields have associated parameters so you might have to use a different field to get the result you want.

Have you got the MP documentation?

Went with the minimum work method, I thought I remembered that you could now do this (select from Metric Tools). Thanks Ron, piece of pie (or cake depending on your national origin)

I have one metric tap in my inch file. What's the SOP?

It's been a while since I did any "oddball" formatting, but I would review that possibility for your Prog. #, it's amazing what you can do with formatting. The simplest tools are often the best, and if you can do it with formatting the chances of logic interference are minimal. Good luck, well I think no need for that now...remember dialing in your post is a marathon.

Glad you got it working, I had to bail due to work demands. If it were me (and it isn't) I would put the necessary code in peof and call that post block with the appropriate call from pretract. Not only does it simplify pretract but it puts the end of file code in a different place (the place where it was meant to go). Then you can do other things there. In my 4 ax posts, for instance, I have a table/tombstone positioning option and an angle call for convenient loading unloading (using Mi and Mr). Always try to modify the original code so everything else in the original is still functioning in its original sequence. It just makes life easier in the long run.

Just uncomment the lock un lock lines, remove the #s at the beginning. The post is not outputting those lines as long as they are "commented out"

Go to File / options in the editor (Code Expert) and open nthe document settings at the top. Check the white space box and it will show what all your "spaces" are. Dots are spaces, arrows are tabs.

Turn on the white space in the editor and make sure you have the correct number of spaces NOT tabs.