How are you generating your rotations?

I think it might behoove you to start with Makino and find out from them how the info is stored and retrieved in their machine.

Your reseller. Asking for a post is not done here, you will get short shrift from the moderator(s)

Speak up we can't quite hear...seriously tho' capitalized on the forum is considered shouting... Look in your Control Definition, on the Control Topics Tree expand arcs. top l/h: Arc center type - change to Radius. You might need to restart MC.

On the whole unless someone is accurately calculating both the radial and axial chip thinning they are probably running too light a chip load to get a good finish. This results in chatter or rubbing the material with the tool (rather than cutting) and gives poor finish and reduced tool life. Try either reducing spindle speed or increasing feed rate.

No you don't have to use the solid edges. Create Curve On One Edge, and Create Curve On All Edges will give you derived geometry for the edges.

We got a Multiplex post from our reseller that was pretty functional, and according to our Mazak App. Eng. the code looked good. Of course the post was binned so I don't know much about the internals. I believe it is Postability originally, but a basic version. These are basically two spindles each with a dedicated upper turret , so the post isn't really that complicated. If we get more into offline programming (I certainly see all the benefits) the Mazaks I would probably develop my own post.

How you deal with this depends on how you are setting up your system. Sounds like you are running a 4 axis horizontal. If you are programming on center of rotation then you simply have to construct a WCS A0 for each Op. (I personally always use MC Origin as my COR) Then you generate your rotations for each Op. from its associative WCS. For each toolpath WCS goes in your WCS column, your rotation goes in Toolplane / Constuction plane columns. Are you TOP /FRONT or TOP / TOP ? Doesn't really make a difference, just curious.

Does the toolpath take off in a fairly large arc? The min toolpath radius is used for the entry arcs after the ones defined in the Linking Parameters page. I have no official knowledge but it seems to me that if you use a stepover bigger than the min toolpath rad a whole bunch of intersects and tangencies will be created with short arc segments in between. When I have encountered this it always looks to me like it has picked a segment and then gone the "wrong way" possibly because it cannot discern the correct direction due to the short arc length, which might be interpreted as a line or spline. Again this is just a guess as to what is happening.

Have a look at your step over : min toolpath radius ratio. Rule of thumb is min toolpath rad should be at least 2x the stepover. Sometimes with small cutters and stepovers it needs a bit more than 2x.

You might want to search for a thread called something like controlling Comments using buffers by djsteadman. I moves manual entries sequenced before actual operations to after the header, or where ever else you might want them. Has a separate "as comment" and "as code" for posting out G10 lines or initiating macro variables etc... Using buffers allows the larger number of characters.

I think the main problem you will have here is that most tool table logic is built to not repeat tool numbers in the list as this would be redundant. My .SET file came out of the box with repeating tool numbers, so this might give you a starting point. You need a tool list that spits out every instance of the tool and its associated depth for that particular path / operation. I have seen a few extensive threads on this (min/max output variations) with as many variations as you can imagine, don't know why you haven't been able to link to them.. Personally I just do a Prog min / max at the top just after the tool list.

You might run into problems with this method as there is no tip offset control for the surfaces using 3D contour. 3D contour is best used in a situation where you are cutting a 2D profile but want to vary the z depth to ensure complete cleanup if the z -ve limit of the part varies more than the LOC of the cutter. In this case the tip is in "air" and will not gouge due to lack of tip offset control. If you want to control gouging efficiently here it would have to be a surfacing prog which has tip offset.

You appear to have posted two completely different files. I say "appear" because there are so many ways that this can happen if the system is not set up properly. Look at your FILES tab under Machine group and make sure you have the same Files in both instances. When you post make sure all the operations you want to post are selected (checked) and that some do not disappear (go unchecked) as posting proceeds. If this happens you might have a program name problem. A file or probably zip2go would be helpful.

Couple of things you can do. You could create a surface from the solid faces in question and extend them past your current edge, select them as drive surfaces to force the toolpath over. Creating a fence surface would be another way to achieve this. On the parameters page of the toolpath there is a gap settings button (legacy surfacing toolpaths) which allow you to extend the toolpath by length and angle. Flowline would be the easiest as it doesn't require a containment boundary, but I am sure I could get an equally effective toolpath with Waterline or SFC.

Have you got the MP documentation? Have you had any formal training in MP language and editing? Not absolutely necessary, but....

Colin is a regular contributor here. He has a pro tip at the top of the Industrial page. Quote him from there to get his attention, or look out for one of his other posts. One what? Posts or Classes?

Look at the top of your posts. If you look in the revision log you should see (IHS) or (CNC) at the end of every entry. IHS indicates MPMASTER, CNC indicates CNC Generic. Get the MP documentation, you seem very interested so getting this will help fire your enthusiasm and give you a reference, although it has a tendency to be a bit dry and arcane. That's why I would recommend Colin's class. More than anything else you will learn how to use the documentation effectively. Good luck!

Probably not actually. You are guessing, which is a dangerous way to approach post editing. There are two main forms of posts. Those derived from MPMASTER available from this site. Those derived from CNC (Mastercam) generic posts, which come with the seat. They have different features and mechanisms and are not necessarily directly interchangeable. I would advise you to sign up for Colin Gilchrist's post editing introduction course. Also request the MP documentation from your reseller.

There have been a couple of threads on this. However if you want to implement you will need to know more about the posts you have access to (apparently there are at least 2).

Absolutely not, we all bring different experience and work packages. I for instance spend most of my time in Aeospace job shops where we could never get that many parts on our tombstones, so this is definitely a horses for courses situation. The more potential solutions we can give to Rich, the more likely he is to get the right solution, it might even be a combo...

Don't think you need them to actually edit code in the post . You will have to change a few switches (for things like axis rotation address output), but a lot of it is handled in the MD/CD. Is the post binned?

TOP/TOP all he way. Worked in several shops where we would prove out on VMCs and then move to a production Horizontal. MC looks like the machine axis which certainly helps me keep oriented. In aerospace non right angle rotations are so common that having "pre defined" views is of little benefit.

You can also use Gap Settings to help keep the tool down. I have also used control surfaces. just minor adjustments in containment are all that is necessary.

There have also been a number of threads to modify the N output at tool change to keep track of multiple use tools using the two options, N value = T# and N value = tool change number.