Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:


Verified Members
  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Interests
    Rock climbing, process improvement, computers, etc.


  • Location
    Sherwood, OR

Recent Profile Visitors

467 profile views

cncgotoguy's Achievements


Newbie (1/14)



  1. It looks like this topic has been covered in another thread The name of it is "Post help / manual entry" I'm going to read about it there, shows how to separate the two, since Comment$ is holding both right now.
  2. Thanks guys, that gets me closer. It's putting the tool comments up there as well. It would work, but I would prefer the tool comments to be under the tool change.
  3. It seems like the manual entry code should come after the previous operation and before the next, but it is being entered after the next tool change. Is this how it normally goes? Seems like it should be placed between the operations as it is in the operations tree.
  4. Thanks for the reply Colin, Always appreciate your input and see you have some Youtube videos uploaded. Gonna give those a view. Using MCAM 2020. Post is as old as I can remember, updated each time we updated MCAM, and a few different hands in there. All hacks including me. I did the following to get it to work. Copy and pasted the parameter 15346 to the post block below and gave it a new variable name. Colin, I like the idea of exiting the post. I've always just put an error in the NC code that won't run on the machine. this sounds like a better way.
  5. Trying to grab the variable for what compensation type is being used and throw a warning if Reverse Wear or Control type are used. I tried pulling the variable comp_type in, but it is staying the same for all and doesn't even match the first tool path correctly. Anybody got any ideas how to get this to work? Much appreciated for reading.
  6. Thanks everybody, especiialy Zaffin_D for the help on this. I went with the following code and got it to work. Probably not the prettiest code around fmt 4 modulo_result fmt 4 int_a fmt 4 int_n fmt 4 remainder modulo_result : 0 int_a : 0 int_n : 10 remainder : 0 p_modulo int_a = speed modulo_result = int_a / int_n modulo_result = int(modulo_result) modulo_result = modulo_result * int_n remainder = int_a - modulo_result if remainder <>0, result=mprint(ssingledigitspindle) If remainder <>0, "(TOOLPATH SPINDLE SPEED ENDS IN SINGLE DIGIT)", e$ Then I ran the post block p_modulo after each toolchange.
  7. 2020 Mcam I see some string functions to convert the number to a string, then break the string into pieces. We don't want to round. We want the posted file to be exactly the same as the source file.
  8. Our spindles don't like when we have a speed ending in a single digit, that isn't 0. We do however want the posted code to match the mastercam file Any idea the best way to throw a warning at posting to let the programmer know the spindle speed needs to be rounded?
  9. The infrastructure was there in the post. Got it working. Looks like all the tool definitions need to be edited for this to work. Does this have an effect on old files? Got these notifications when I pulled the edited machine definition into an old file. Attached is the text file with the errors. New Style Coolant Compatibility issue.txt
  10. I want to be able to set the coolant type under the tool parameters. We want thru tool coolant and flood on most tools, but some we want flood only. M26 for thru tool coolant and M8 for flood. Does anybody know what the easiest way to do this is? Under the General Machine Parameters/"coolant Commands", we have the box checked for "Support coolant using coolant value in post-processor"
  11. Thanks Jeff, I actually want to get a certain number of characters in the beginning and then capture the revision and the operation. I was going to set a specific way (fixed character length) to name the operation number and revision, so there would be a left over number of characters for the PN. I would need it to go to the first underscore and grab the characters after up until the next underscore and save that as the revision, then grab the characters after the next underscore and store it as the operation.
  12. Is there logic built in to look through a string and be able to truncate the string when it encounters a certain character? I see you wrote "trick". Not sure if that is an indication it isn't easily done? We have a machine that requires a line at the beginning that has 16 characters max. I would like to extract part of the part number and the entire revision and operation. For example: NC file name: 980-1000001258-56286_A_OP1.NC would like the line at the beginning of the program to show: 980-100000_A_OP1
  13. Thanks Jeff. That worked. Here is the postblock and the added forced variables if someone else has this problem. prdrlout #R drill position if cuttype = one, *refht_a = refht$ + (rotdia$ / two) else, *refht_a = refht$ *refht_i = refht$ - initht$ if cuttype = three, *refht_a = w$ if absinc$ = zero, *refht_a, !refht_i else, *refht_i, !refht_a
  14. Thanks Jeff! That makes sense. Do you know which variables on which to put the (*)? prdrlout #R drill position if cuttype = one, refht_a = refht$ + (rotdia$ / two) else, refht_a = refht$ refht_i = refht$ - initht$ if cuttype = three, refht_a = w$ if absinc$ = zero, refht_a, !refht_i else, refht_i, !refht_a This is the code that is posted. % O0001(TWO DRILL CYCLES.NC) ( DOUBLE BORE CYCLE TEST ) (OKUMA) (NOT PROVEN) ( 04 / 08 / 19 ) (PROGRAMMED TO CENTER LINE OF CUTTER) N10 G20 N20 G90 G80 G40 G94 G17 G0 N30 N7 G116 T7 G15 H01 ( .249 REAMER HOLE .249/.2498 TOOL - 7 DIA. OFF. - 7 LEN. - 7 DIA. - .249 ) N40 G0 G90 X0. Y0. N50 S1069 M3 N60 G56 H7 Z1. M8 N70 G71 Z1. N80 G76 X0. Y0. Z-1. R.1 Q5. F6.4 M53 N90 G00 N100 G71 Z1. N110 G76 X0. Y0. Z-1. R.1 Q5. F6.4 M53 N120 G76 X2.2417 Y.7523 Z-1. Q5. F6.4 M53 N130 G00 N140 G76 X2.2417 Y.7523 Z-1. Q5. F6.4 M53 N150 G00 N160 M5 N170 M9 N180 G0 G90 Z20. N190 G0 G90 Y20. N200 M30 N210 %
  15. I'm using the custom drill cycle to create a double fine boring cycle. When there is only one hole, it works fine, but when there are additional holes, it doesn't post out the retract value. for one hole, It uses the postblock pdrlcst$ and outputs the retract value through the postblock prdrlout for the additional hole, it uses the postblock pdrlcst_2$, and even though I have the postblock prdrlout, it won't read it Looking to get the R value in all lines that have the G76 Here is the section of the post pdrlcst$ #Custom drill cycles 8 - 19 (user option) #Use this postblock to customize drilling cycles 8 - 19 pdrlcommonb pcan1, pbld, n$, "G76", pfxout, pfyout, pfzout, pcout,*prdrlout, *shftdrl$, dwell$, *feed, *sgdrlref, strcantext, e$ pcom_movea pbld, n$, "G00", e$ pdrlcommonb pcan1, pbld, n$, "G76", pfxout, pfyout, pfzout, pcout,*prdrlout, *shftdrl$, dwell$, *feed, *sgdrlref, strcantext, e$ pcom_movea pdrlcst_2$ #Custom drill cycles 8 - 19, additional points (user option) pdrlcommonb pcan1, pbld, n$, "G76", pfxout, pfyout, pfzout, pcout,*prdrlout, *shftdrl$, dwell$, *feed, *sgdrlref, strcantext, e$ pcom_movea pbld, n$, "G00", e$ pdrlcommonb pcan1, pbld, n$, "G76", pfxout, pfyout, pfzout, pcout,*prdrlout, *shftdrl$, dwell$, *feed, *sgdrlref, strcantext, e$ pcom_movea

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us