If the first point didn't get them, then I'm afraid not much else will. If they don't have a problem with the fact the spindle won't be turning while someone is programming there are problems.

On the first page, 1st question it asks to select all that apply but you can only select one. It gives an error if you select more than 1.

I've never heard of that type but we cut 5083-h131 here (armor plated aluminum and I treat it just like 7075.

Is 'enable power keys' activated? I turned both of those off and it works now.

"Default to fast point mode" was checked in the auto cursor options. That did the trick Thanks guys

In X3 you could select create-line-endpoints and select anywhere on an arc with tangent turned on and it would drag around the arc as you moved the mouse. In X4 it's not doing the same thing, it just snaps to the end of the arc. Am I missing a setting or is this new?

I can mess around enough to be dangerous with a post but, writing logic for toolpaths and stuff like this is new for me so thanks for the help guys

I was trying to output G0 with it. It does post it out as G0 just like Andre says it calls the 1st g code. I didn't think it checked it against the full list of options (DUH!). I changed it to *sg00 and it worked. No errors! Just so I understand it fully, I could have also just added: sgcode = 0 to the top of each drillcyc$ to get the same output correct? This would have set sgcode to 0 if I understand it correctly.

I am adding probing to my post for an Okuma OSP200 control and I can't figure out this error I'm getting. [PST:2942,1][NCI: 97]The value of the string select selection variable is out of range: 0 This is the section it is throwing an error on: code: pdrlcommonb #G113 - OD boss probe routine 8/14/2009 if drillcyc$ = 9, [ pbld, n$, slbracket, "G113 - OD BOSS PROBE PICKUP MACRO", srbracket, e$ pbld, n$, slbracket, "H = FIXTURE OFFSET TO ADJUST", srbracket, e$ pbld, n$, slbracket, "I = BOSS DIAMETER - L = Z DEPTH OF PROBE", srbracket, e$ pbld, n$, slbracket, "X = ADJUSTED X VALUE - Y = ADJUSTED Y VALUE", srbracket, e$ pbld, n$, "G113", *drl_prm1$, *drl_prm2$, *drl_prm3$, *drl_prm4$, *drl_prm5$, e$ pbld, n$, *sgcode, *drl_prm6$, e$ <------This is line 2942 where the error occurs ] It's giving me the correct value when it posts. I'm just trying to figure out why its giving me an error.

Only thing I hate with Helix Bore is the fact you have no control of where that toolpath ends. Using Helix bore to cut a 20" dia hole. and watching the dumb thing return to center

FYI The new samples and examples are up for X4. Thanks!

The way Colin describes is my preferred way of doing imports, however, I have been burned in the past doing things this way with the problems Jim describes. Not only that it likes to jumble up all the operations for some reason. So if I am trying to import operation 82 of 145 trying to find it in the list can be quite a PITA.

We use micro100 carbide split point engravers @ 20 ipm, 10000 rpm. Not much faster that what you are doing. We found that once we started going faster the tool tip started whipping. The seco would probably be your best bet for more feed.

Ya I'm gonna put in a call today to get the new ones.

Before I go bugging my reseller and getting put in the queue, are the mpmaster posts for okuma osp controls on X4 ready for the public yet? The posts I am using for X3 are way messed up when converting to X4.

That worked like a champ! There is only 1 instance of rd_params$ in the entire post and its called in the ptlchg0$ block code: ptlchg0$ #Call from NCI null tool change (tool number repeats) if op_id$ <> last_op_id, [ #rd_params$ # Read parameters - pparameter pmisccheck I commented it out and all the errors go away. I'm going to run some tests still to make sure everything is peachy. Thanks a bunch Paul

Make sure its set to 3d first.

its an mpmaster based post. from version X2 I believe and has been updated through the years to be current with X4. Is it because of 'where' I defined them? Or am I just formatting it completely wrong

code: 23 Jun 2009 11:54:24 AM - <2> - PARAMETER DATA - - Possibly incorrect parameter number detected: 0 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Job number - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 2545 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Part number - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 3636 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Customer - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 5467576 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Stock size and type - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 53757 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Part revision - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 45757 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Work order operation number - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 4567547 - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (QUESTION) Program description - OPERATION 82 NCI LINE 92. 23 Jun 2009 11:54:24 AM - <2> - RUN TIME (RESPONSE) 457547 - OPERATION 82 NCI LINE 92. The random numbers in there are just me typing to get the post output.

I get errors when I post because I use prompt questions when the post fires. Stuff like, job number, customer, part revision, etc... I thought I had it configured right but every time I post the stupid screen pops up telling me I have errors. So this is how I have it setup now: defined the variables at the top code: sjob_no : "" #Job number spart_rev : "" #Part revision spart_no : "" #Part number scust_name : "" #Customer name sstock_dol : "" #Stock size and type swo_op : "" #Work order operation number swo_com : "" #Program comment defined the questions code: fq 1 stock_typ "Predator Stock [0=Box,1=Cylindrical]" fq 2 cyl_typ "Cylindrical Stock Axis [1=X,2=Y,3=Z]" fq 3 sjob_no "Job number" fq 4 spart_no "Part number" fq 5 scust_name "Customer" fq 6 sstock_dol "Stock size and type" fq 7 spart_rev "Part revision" fq 8 swo_op "Work order operation number" fq 9 swo_com "Program description" then I ask the questions in the pheader$ section, right before the output starts. code: q3 #Job number q4 #Part number q5 #Customer q6 #stock size and type q7 #part revision q8 #work order operation number q9 #program description Then it puts those values into the header block. What did I do wrong with this formatting to make mastercam keep telling me I got errors.

Or use mastercam print and use CutePDF writer as the printer to save it as pdf. http://www.cutepdf.com/

Not mastercam specific but I'm hoping someone here can answer my question. I added a new machine type for editing posts and I setup the colors the way I wanted them. I registered the pst extension with that machine type hoping it would open those color settings when I opened a post but it's not doing it. When I open a post file it still treats it as an ISO/Milling file. Is there any way to make the setting stick with the pst extensions?

I copied mfc90.dll to in the install directory c:mcamX4 and it fired up correctly thanks Roger!

Thanks Roger I'll give it shot tonight.

Yes that was brought up by me in X2 if I remember correctly. I still don't understand the reason for those boxes to even exist if the numbers I put in it mean nothing. I'd rather not add more toolpaths to the job when all that is required is 1. So ya it still bugs me