D&S, Couple things you can do. Keep in mind I don't know what post you're using. code: define these in your strings stra "A" strc "C" the put either of these in your pcout if spindle_no <> 0, result = nwadrs(cabs,stra) else, result = nwadrs(cabs,strc) or try this if spindle_no <> 0, str_cax_abs = stra else, str_cax_abs = strc Brett

Clearly Dave and Brett have too much time on their hands if they're chirping in on forums like this one. I really have to stop doing their work for them...

Walter, You need to come to Canada and sit in an office next to Dave Thomson (aka Post Master General) for a couple years. Then you'll be all set. Brett

s.s.cheema, Welcome to the forum. We suppress output of A/B/C if all the paths posted at that particular time are on the base plane (top for VMC, front for HMC, no rotary). code: pwrtt$ # Write tool table, scans entire file, null tools are negative if rotaxis$ > 0 | rotary_type$ > 0 | mill5$ <> 0, [ sav_rot_on_x = rot_on_x output_z = no$ ] if vmc = 0 & tlplnno$ <> 2, sav_rot_on_x = rot_on_x if vmc = 1 & tlplnno$ > 1, sav_rot_on_x = rot_on_x sav_rot_on_x = rot_on_x Add the last line (sav_rot_on_x = rot_on_x). This gives rot_on_x a value other tahn 0 so the post knows to output the angles. Brett

Thad, Don't check them all. It will linearize arcs that you want left as arcs. Our tests are consistent with Jim's recommendation for selections. Linearization occurs if your checks aren't met. See the tolerances - general page in the control def and I'm sure you'll figure it out. Also, set your NC Precision to one tighter than your coordinate output. That's the tolerance that really matters here. Brett

Looks like Mark IV to me. We haven't tested the tilted planes or setup that functionality yet. IMTS threw a little wrench into to development but we'll be back on it soon. If you've got something that works, fire it over. Brett

Hymen, Setup your chucks in the job setup where you want them initially then use the part transfer when you want to change setups. Be sure to select "synch spindles" on the misc int page of each synched operation. Brett

jimspac, We use custom drill cycles for all sorts of macros. Set it up in pdrlcst then you can tee up your macro with any input from the boxes on the right side of the drill paramters page. Brett

Hymen, Parameter A18 governs the C-axis behaviour. Our post is setup to run 0-360 shortest distance so you don't get windups. Your machine is setup for 0-360 sign indicates direction. Brett

Sounds like it could be a post issue, could also be something fixed in MR2, be sure to update and try it out.

I guess I should also let everone know that we (In-House and CNC) are working on a post for the Matrix control with Mazak. Two posts actually.....for the Mark IV and the e Series. Not putting a timeline on it but we're pretty far along. I think we'll have a big push to the finish right after IMTS. Brett

McamNut, The post is setup for either standard or T32 mode. I've got a few people running the T32 mode and they are reporting back with good news. You can eval the X post setup for T32 if you like. Drop me an e-mail. Brett

Heavy, You're going to have to do more trouble shooting. The code itself as you posted doesn't look bad that I can see (hard to tell though). A couple of quick suggestions to fix these issues. Go into your control definition, under the files tab and set the keep error file to "On fatal and non-fatal errors" and set the message option to "All error messages to file". This will produce a .err file in your nci directory with all the errors encountered during posting. If you just updated the file there is a good possibility that something hasn't been defined properly in X or there is some other random error. Also, try throwing in a: "!", ~workofs$, prv_workofs$, e$ before the: if mi1$ => one & workofs$ <> prv_workofs$, line you just added. This will show you what the values are and let you know the post is at least getting to that point. If nothing is output, then the post isn't making it to this statement and you need to move the statement closer to the pwcs statement until you find the road block.

Do all your other 5-axis toolpaths produce proper code for their respective operations? Drilling acts a bit different from standard operations so some extra work is required to setup the proper values.

Lathe and WCS don't play nice together since lathe has a bunch of mapping based on toolplanes. Always use top WCS and just select toolplanes accordingly for lathe! Brett

Dan, Drop me a reminder next week and I'll hook you up. Also want to talk to you about that Mori. Brett

Hymen, What you need to do is get an evaluation copy of the post from me. It does exactly what you're talking about....and it does it perfectly! Have your reseller call me. Brett

Open up your .pst file (found in your mcamx/mill/posts directory) in your text editor. Search for rpd_typ_v7 and change it. Brett

Mick, Yeah an Okuma version is in the works. Brett

Uhhh...thanks John...appreciate you sending it around. I guess I should toss in my 2 cents. Have been doing alot of work on it even in the last few weeks so I think that means that you're all due for an update. We're going to whip up a web page a la mpmaster and document some of the functionality. Until then, if you want it please contact me directly. Looking for feedback too! Brett

Cascadeclimbr, Killer machine....enjoy it. We've got some customers with similar machines and they are loving them. We just wrote a free 3/4-axis mpmaster_makino post that supports all the SGI stuff. Drop me a line if you want it. Brett

I don't use that post but doesn't it read from the machine def? If you have a tilt about X it'll give A and a tilt about Y gives B. Brett

terry5357, Good luck with your project. Aggregate heads are great when you get them working well. Call me crazy, but I think you should just buy a custom post then you can program blindly and save a ton of time. Just a thought. Brett

Terry, The new xxxxor controls will do a tilted workplane. not sure about your dinosaur. if the control supports it, it's possible to get a post to handle it. Brett

What post are you using? Make sure you've got your NC precision set properly. In-House recommends one place tighter than your format statement. Also check that youve got the right arc checks set. CNC recommends : Length of arc, Parallel axis motion on quadrant, End point checks - round end point - break arc on failure If you set those things in your control def it'll be mint. Brett