Even for 2020, the description and manufacturers name boxes are listed as N/A for posting.

You can orient however you want on the tool set-up page. There's neutral OD holders in the standard tool library, change the insert to a VNMG if required and change the tool angle. Check the Define Tool parameters tab to make sure the compensation and tool clearances don't do anything funky (mostly on grooving tools).

Hard to even guess without knowing more. Can you attach a Zip2go?

Received and replied. Outstanding.

All I could find on documentation on the MC site was NCI parameters from X3-X6, maybe I'm looking in the wrong area? Sent off an email anyway and until a hopefully positive response, I shall continue writing garbage code until it works by sheer will alone.

That other line would have been coming from your tool comment. Happy to see you got it working.

Not sure about the US, but up here they haven't distributed the MP documentation in quite some time.

run the debugger and watch where the post outputs the tc lines, put it in there. you won't be able to put the letters in the tool path parameters page. In the example, your post would pull it from the "Tool name" in the "Define tool" section.

Post it using the de-bugger and see where it's processing the output. Probably line 1498 in the lathe part and 1560 for the milling tools.

Did you just add the "M6", or the entire line below what was there? Just adding the "M6" had it posting the way you wanted, not sure why the whole line would go missing...

plinout #Output to NC of linear movement - feed if cc_pos$ <> prv_cc_pos$ & cc_pos$ <> zero, [pccdia, e$ pcan1, pbld, sgfeed, sgplane, "G0", sgabsinc, pwcs, pxout, pyout, pzout, pcout, strcantext, pscool, e$] else,[ pcan1, pbld, sgfeed, sgplane, *sgcode, sgabsinc, pwcs, pccdia, pxout, pyout, pzout, pcout, feed, strcantext, pscool, e$] This got it outputting mostly what you want, changing the `sgcode to *sgcode forces it to output G1/G0 every line tho, without changing it, bad things happened.

if home_type = m_one, pbld, n$, *sgcode, *toolno, e$ #line 1490 of your post if home_type = m_one, pbld, n$, *sgcode, *toolno, "M6", e$ #add the "M6" Will only be helpful if you always need an M6.

I pulled the section from the 2018 fanuc generic, do the newer ones no longer force IPM tap output? And usually, you have to pay for the post. But, you can still sell it pretty easily on the time saving of not having to edit posted code anymore.

I borked mine a bit and then saw you wanted both formats in the same program. pbld, n$, *sg28ref, "U0.", [if y_axis_mch, "V0."], "W0.", e$ toolno = t$ if home_type = m_one, pbld, [ if strlen(strtool$) < 1, n$, *sgcode, "T=", no_spc$, *toolno, e$ #because you may want to just post the tool number if there is no tool name else, n$, *sgcode, "T=", no_spc$, 34, no_spc, *strtool$, no_spc$, *toolno, no_spc$, 34, e$ #forgot the $ ] else, pbld, n$, *sg50, pfxout, pfyout, pfzout, e$

ptap$ #Canned Tap Cycle pdrlcommonb result = newfs(17, feed) # this reformat statement could be messing it up if met_tool$, [ if toolismetric, pitch = n_tap_thds$ else, pitch = (1/n_tap_thds$) * 25.4 ] else, [ if toolismetric, pitch = n_tap_thds$ * (1/25.4) else, pitch = 1/n_tap_thds$ ] pitch = pitch * speed # this section is def forcing ipm, comment this line out pbld, n$, sg94, e$ # since you don't use G94/95, comment this line out pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *pitch, !feed, strcantext, e$ pcom_movea If your ptap$ section looks like this, try making the commented modifications and run it again. I'm guessing all the post warnings you got were from the global calculation running with a null spindle speed. The !feed can probably go tho.

What does the actual code end up looking like? Is there still a G1 in the call-up, then a new line with just G0 on it?

Looks suspiciously siemens. Are the two different formats for the same machine? That's probably going to determine how you go about it and how much logic would be required. If the tool call is always in the string call format T="ABCD1234" you can change your toolno fmt line to be an empty string "" instead of "T", then your tool change line would look like: pbld, n$, *sg28ref, "U0.", [if y_axis_mch, "V0."], "W0.", e$ toolno = t$ * 100 + zero if home_type = m_one, pbld, n$, *sgcode, "T=", no_spc$, 34, no_spc, *strtool, no_spc$, *toolno, no_spc$, 34, e$ else, pbld, n$, *sg50, pfxout, pfyout, pfzout, e$ you're strtool would have to be the ABCD and set by your tool description, or make a new string variable and pull the info from somewhere else.

Is your ptoolcomment section missing? The pstrtool function just makes the comment uppercase. ptoolcomment #Comment for tool tnote = t$, toffnote = tloffno$, tlngnote = tlngno$ if tool_info = 1 | tool_info = 3, [ pstrtool #Convert strtool$ to uppercase if string is not empty scomm_fx_arg = strtool$ + sdelimiter + drs_str(2, tnote) + sdelimiter + drs_str(2, toffnote) + sdelimiter + drs_str(2, tlngnote) + sdelimiter + drs_str(2, tldia$) pcomment_out #Check comment length and output to NC file ]

CALL OCHK M5 M9 G0 X20. Z20. T020202 Y0 IF [VDIN [24]EQ 1]NLOAD M84 G0 X1.75 Z2. G0 Z.015 M93 M83 M00 (***CHEK FOR PART TO PART STOP***) G0 Z2. G0 X20 Z20 M01 GOTO NPART NLOAD M77 M84 M93 M76 G4 F8. G0 X1.75 Z2 G0 Z.05 M93 M83 G0 Z2 G0 X20 Z20 M01 GOTO NPART NPART G00 X20 Z20 G50 S1500 CALL OCHK I've been too lazy to clean this up because it works and was before my time. The M93 is the push signal, so it's probably going to be different on your control. The vdin[24] is for ejecting the stub/bar changes.

Do you mean at a tool change, in the tool table, or both? An example of what you want it to look at would help.

Thank you Colin, that's an amazing amount of help!

2020, but the post itself was one of the generics from 2018.

I've been working on getting my generic fanuc 2x lathe post to output a min overhang for boring bars and have hit a bit of a brick wall. Started by making a buffer to capture op_id, z_min and z_max, defined and formatted the variables, modified the pwrtt and tooltable post blocks and hit the G1 button. The result was wrong as the read values ended up staggered. To figure out why, I added t$ to the buffer and found that op_id 1001 was already writing tool 1 into the buffer. I tried to force all 0. if gcode$=1001, and it just repeated the next row with tool 1. I think I'm pretty close, but definitely need some help from more experienced people. IHS said they'd look at it for a charge and that the MP documentation is no longer distributed, so I'm hoping someone here can point me to what I'm missing. Snippets below. Buffer results 1001. 0. 0. 0. 1001. 0. 0. 1. 1000. 0.206 0.055 1. 1002. 0.211 0.05 4. 1000. 14.85931503 0.03004284 4. 1000. 14.85931503 12.00595716 4. 1000. 12.47595716 0.03004284 4. 1002. 12.48095716 0.00004284 6. 1002. 7.05867671 0.1 6. 1002. 7.05867671 0.1 10. 1002. 5.5 0.5 6. 1002. 14.7522132 0.03004284 6. 1002. 14.7522132 0.03004284 8. 1000. 7.07 0.03 8. 1000. 7.16667541 6.78875 8. Buffer definition #Buffer 4, z_max values # -------------------------------------------------------------------------- b4_op_id : 0 b4_zmin : 0 b4_zmax : 0 b4_tool : 0 #added to see where the values came from rc4 : 2 wc4 : 1 size4 : 0 sbufname4$ : "C:\desktop\buffer4_data.txt" fbuf 4 1 4 0 0 #Buffer 4 fmt "" 2 min_depth #z_min fmt "" 2 max_depth #z_max modified postblock and buffer read/write functions pwrtt$ #Buffer toolchange information, tooltable = 3 calls on 1003 if gcode$ = 1001, psetup pcut_cctyp if opcode$=104 | opcode$=105 | opcode$=three | opcode$=16, cc_pos$ = zero if gcode$ <> 1001, plast_recd pcur_recd if gcode$ <> 1003, cc_pos$ = zero !opcode$, !tool_op$ if gcode$ = 1003, [ size1 = rbuf (one, zero) rc1 = one if rc1 < size1, preadcur_nxt if cc_1013$ = zero, cc_pos$ = zero ] if gcode$ <> 1003, pwritbuf4 #added write buffer if t$ > 0 & gcode$ <> 1003, ptooltable pwritbuf4 #Write zmin/max if gcode$ = 1001, [ b4_op_id = gcode$ b4_tool = 0 b4_zmin = 0 b4_zmax = 0 b4_op_id = wbuf(4, wc4) ] else, b4_op_id = gcode$ b4_tool = abs(t$) b4_zmin = abs(z_min$) b4_zmax = abs(z_max$) b4_op_id = wbuf(4, wc4) preadbuf4 #read zmin/max min_depth = b4_zmin max_depth = b4_zmax Thanks for the help, I wouldn't have made it this far without this forum.

Solids Tab -> Thicken -> profit the amount you can thicken will depend on the sheet curvature.

Sounds like your computer has a SW license manager client and the shop computers don't.