I agree, there should be more conditions met than just the tool number. I like to name my probe and other special tools, and have the post 'read' the names. Then apply special conditions to each special tool. As above, the output is for T30, regardless of the actual tool at that position.

You can nest the code for T30 inside the 'else' of your code above. There is nothing 'sloppy' about nesting, just try to keep it readable for the future.

Do some research on my previous posts, you will find some interesting information for your project.

I can combine all of your posts into one workable post per machine type ( one for mills, one for lathe). I would need the existing posts, machine definitions to ensure the new post would output properly. PM me if interested.

Bear with me, I am slinging code on the fly without debugging. If you are using buffers, make sure that str0 - str11 are being passed into the buffer, so they can be retrieved. Also, to prevent empty parentheses, place a little logic like this: if strtemp <> "", str1 = "(" + strtemp + ")" do the same for all the str0 type variable assignments. HTH

I would write it like this: if breakpasses > 1, [ strtemp = brksps(60, sinput_str) # Break string str0 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str1 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str2 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str3 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str4 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str5 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str6 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str7 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str8 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str9 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str10 = "(" + strtemp + ")" strtemp = brksps(60, sinput_str) # Break string str11 = "(" + strtemp + ")" pbld, *str0, e$ pbld, *str1, e$ pbld, *str2, e$ pbld, *str3, e$ pbld, *str4, e$ pbld, *str5, e$ pbld, *str6, e$ pbld, *str7, e$ pbld, *str8, e$ pbld, *str9, e$ pbld, *str10, e$ pbld, *str11, e$ str0 = "" str1 = "" str2 = "" str3 = "" str4 = "" str5 = "" str6 = "" str7 = "" str8 = "" str9 = "" str10 = "" str11 = "" ]

The brksps function will break a string at any given point. Using the right logic, you can achieve what you desire.

To find midpoints of features like pockets or bosses, the toolpath would have pairs of probe vectors (opposite sides of the feature). The direction of the vector pairs are analyzed, so the post knows if OD or ID is being measured.

I can instruct (using keywords) the post what I am trying to measure. I could simply type 'WEB' in the comment box for the toolpath that measures a web.

I have written logic that identifies the tool as a probe, and written the code that analyzes the vector of the move. Programming is as simple as constructing vector lines where I want to probe, and programming as 3D contour.

I wrote my post to use linear movement for probing. That way I have control over approach distances and can probe vectors. The vector determines what is being measured. If the vector is purely in the Y axis, I get Y measurement.

This parameter is from the machine definition, and needs to be accessed in a different way than NCI parameters. In the pmachineinfo$ postblock, make sure this line is not commented out: if prmcode$ >= 17000 & prmcode$ < 18000, result = fprm(17000) #Run the parameter table for Machine Definition Parameters then, in fprmtbl 17000 table, type something like this: 17435 chuck_loc #Chuck Location That should get what you want. (After you define the variable you want to use, of course.) HTH

I guess I should have researched your machine, I was unaware that it was 5AX. But the same logic would apply, wherever the post would evaluate for plane change.

I would just amend the pcout block to output the Z0 move prior to rotation if the plane changes. MI and MR toggles are a pain, because I tend to forget them.

From the Windows Start menu, browse to the 3DConnexion folder. Inside, there is a driver folder. Inside that, you will find commands to stop the driver, and start the driver.