Thanks Colin. I changed the rpar to rparsngl the output values are all 0. now. pwrttparam$ #Pre-read parameter data #"pwrttparam", ~prmcode$, ~sparameter$, e$ if prmcode$ = 20007 & use_tl_hldr, tmp1 = rparsngl(sparameter$, 13) if prmcode$ = 20002, str_mfgcode = sparameter$ if prmcode$ = 20003, str_chuck = sparameter$ if prmcode$ = 20004, tempf1 = rparsngl(sparameter$, 12) pparameter$ #Parameter Read if prmcode$ = 20004, tempf1 = rparsngl(sparameter$, 12) if prmcode$ = 20007 & use_tlength = one, temp1 = rparsngl(sparameter$, 3) if prmcode$ = 20007 & use_tl_hldr, tmp1 = rparsngl(sparameter$, 13) if prmcode$ = 20002, str_mfgcode = sparameter$ if prmcode$ = 20003, str_chuck = sparameter$

No errors in the UpdatePost.log

Anyone???

I'm updating a post from X6 to X9. Generic Fanuc 5X Router.pst. Using G10 L10 to set tool length and I'm missing something. Please help. I'm trying to call from nci 20007 line, parameters 12 and 13. For the first tool change the nci is: 20007 0. 2.65 2.65 2.65 0.261 1.055 0.9 0 100. 26. 0 2.65 4.45 Posted code is: (T5 .261 DAGGER DRILL) (TOOL HEIGHT = 3.55) ---------------- should be 7.1--from holders parameters NCI 20007 12 & 13 (T1 3/16 OSG BNC) (TOOL HEIGHT = 2.) ---------------- should be 5.873 G90 G10L2P1X85.662Y16.653Z-65.634B0C0 G10 L10 P5 R3.55 (.261 DAGGER DRILL) ----------------should be R7.1 G10 L10 P1 R2. (3/16 OSG BNC) ---------------- should be 5.873 From the post: # Parameter Data # -------------------------------------------------------------------------- tmp1 : 0 # Holder and Overall Tool Length Values tmp2 : 0 tmp3 : 0 # Overall Value tmp4 : 0 tmp5 : 0 tmp6 : 0 tmp7 : 0 # Holder Value fmt "" 2 set_length # Tool Set Length Holder + tool overall pwrtt$ #Pre-read NCI file if t$ > zero & t$ <> prv_t$, [ t_n = t$ spaces$ = zero sopen_prn, *t_n, 32, *strtool$, sclose_prn, e$ if str_mfgcode <> sblank, [ str_mfgcode = ucase(str_mfgcode) sopen_prn, *str_mfgcode, sclose_prn, e$ str_mfgcode = sblank ] if str_chuck <> sblank, [ str_chuck = ucase(str_chuck) sopen_prn, *str_chuck, sclose_prn, e$ str_chuck = sblank ] set_length = (tmp3 + tmp7) subout$ = three g10_p = tempf10 g10_r = set_length + tool_set "G10 L10", 32, *g10_p, 32, *g10_r, 32, sopen_prn, *strtool$, sclose_prn, e$ subout$ = zero sopen_prn, "TOOL HEIGHT = ", *set_length, sclose_prn, e$ *e$ spaces$ = prv_spaces$ !t$ ] pwrttparam$ #Pre-read parameter data #"pwrttparam", ~prmcode$, ~sparameter$, e$ if prmcode$ = 20007 & use_tl_hldr, tmp1 = rpar(sparameter$, 13) if prmcode$ = 20002, str_mfgcode = sparameter$ if prmcode$ = 20003, str_chuck = sparameter$ if prmcode$ = 20007, tempf1 = rpar(sparameter$, 12) pparameter$ #Parameter Read if prmcode$ = 20007, tempf1 = rpar(sparameter$, 12) if prmcode$ = 20007 & use_tlength = one, temp1 = rpar(sparameter$, 3) if prmcode$ = 20007 & use_tl_hldr, tmp1 = rpar(sparameter$, 13) if prmcode$ = 20002, str_mfgcode = sparameter$ if prmcode$ = 20003, str_chuck = sparameter$

Thanks Ron, That worked great.

Can anyone help me force the G code on every feed line? Generic Fanuc 3 axis mill post. I've been poking around in plinout and pcirout but can't seem to make it work. Thanks

And all I wanted was some help with a macro.

Dan.W, M109 is the ticket. Just tested this. Works great. G103 P1 N1 #505= 0. (Clear the variable) N5 M109 P505 (Are you awake? Y or N) IF [ #505 EQ 0. ] GOTO5 (Wait for a key) IF [ #505 EQ 89. ] GOTO10 (Y) IF [ #505 EQ 78. ] GOTO20 (N) GOTO1 ; (Keep checking) N10 (A Y was entered) M30 N20 ( A N was entered) G103

Thanks for the replies. Guitar, I'll give that a try. I'm proving out a new process on a machine that can't probe and want to "error proof" the setup. Same fixture mounts two ways on the 4th. Once the process is proven, I'll move it to the production machine, and probe the fixture for correct setup. Thanks again!

How do I use the keyboard input for the "Y" "N"?

Hi Kevin, long time no see. Care to expand that?

Sorry, I would like to program a Manual Entry Toolpath that will stop the program "M00" and ask for input from the operator. "Is the dust collection on? Y or N" ...or any other question. If the operator inputs "Y" then Cycle Start the program will continue. If the operator inputs "N" then Cycle Start the program will rewind or goto another command. How do I code that?

Hi All, How do I, on a Haas control, require the operator to answer Y or N to a question before allowing the program to continue? Thanks Keith

Thank you, I'll give both options a try in my copious amounts of spare time. I love this forum!

I do, Renishaw NCTS.

Great idea! Care to share how you did it? I'd love to have that in my posts.

Unfortunatly, what I know about macros might fill a thimble. This one is a Haas.

Thanks Joe788, But can I point the Renishaw macro to the variable for comparison? I want it to fault out if the operator to uses the wrong length tool.

In an effort to insure the operator has loaded the correct length tool, I'm using the following in the header of the program. /G10 L10 P9 R-24.716 (3/8 BULL ENDMILL 0.02 RAD) /M6T9 /G65 P9862 B3. D9. H.03 I.375 J.012 R.375 T9. The G10 line sets the desired tool length in the offset register. The H.03 in the tool measure line allows .03 error, anything over .03 errors out. Block skips allow the operator to skip the tool measure for subsequent parts. Measuring 10 tools adds 2 min. to the 15 min. cycle time. "Rant begins." Today, the operator ran the first part with block delete off, and got a good part. On the second part he started the program, which read the G10, and when it moved to measure the tool, he stopped hit reset, turned block delete on and restarted the program. This overwrote the measured offset value with desired and scrapped 3 parts. "Rant ends." I should have seen that coming. My bonehead mistake. Anyone have a better way to double check that the physical tool length is within a given value without the risk? Thanks Keith

Would a macro have the same end result, and will it function with a probe?

Anyone know if it is possible/feasible to retrofit a Haas 5 axis with a controller that will use dynamic offsets? According to Haas; they don't have any way to upgrade a VF6TR. I'm hoping for something that does not involve jacking up the radiator cap and driving a new machine under it;) Thanks

How about posting each tool group as an incremental sub program, then use a point toolpath followed by a manual entry calling the subs?

Yea, I'm thinking a 72" VTL with a multi axis, multi spindle pneumatic peck head??? Any idea of who would be the best bet on building it?

I use a manual entry toolpath to set the work offsets. After the part and setup are proven repeatable, I insert the manual entry as the first toolpath. If for any reason they need changing, it's a simple matter of editing the toolpath, regen, and repost. In the manual entry parameters, enter "G1 L2 P1 X*** Y*** Z*** A*** C***" to set G54 and check NCI output method "As Code"

Hi All. Anyone out there have a recommendation for a machine builder to build a machine to drill umpteen thousand small holes inside a large contoured cylinder?