byte me

Verified Members
  • Content count

    1,536
  • Joined

  • Last visited

  • Days Won

    7

byte me last won the day on July 18

byte me had the most liked content!

Community Reputation

646 Excellent

1 Follower

About byte me

  • Rank
    Developers

Profile Information

  • Gender
    Male
  • Interests
    Programming

Uncategorized

  • Location
    earth

Recent Profile Visitors

2,703 profile views
  1. Is there a way to alter the settings of a nesting edited using drag? When parts are dragged from one sheet to another after api nesting they are outputting a tool change for each part.
  2. byte me

    o/t chess set

    2002
  3. byte me

    Mastercam Subscription

    Peace ;'D Thanks noobie, it's a cool setup, I think I could make that in my machine, the software must be tight.
  4. byte me

    Mastercam Subscription

    What kind of machine? Which software? Magic grammin, where do I sign up?
  5. byte me

    change 4th axis rotary output

    He doesn't "have to" providing code without a disclaimer/license opens you up to liability, it's best to always include something like that when providing code.
  6. byte me

    Mastercam Subscription

    I see..
  7. byte me

    Mastercam Subscription

    I'm thinking all the big players would drop Mc if they did that, making it not a worthwhile decision, offering both is the best of both worlds..
  8. byte me

    Missing default.mcam-materials?

    In Configuration -> Files, you can view the path Mastercam is pulling data from.
  9. byte me

    Post Processor coding

    Yeah I knew that going in, I was purely speaking on the User Defined varables. Yeah I was thinking more for new posts, updating existing posts using find and replace could be error prone..
  10. Hi all, I've been practicing the post processing writing a bit this weekend. I noticed the user defined names in the posts I see are a bit unclear as to what they do a lot of shortened names, For my posts that I'm writing I think I might use a camel case like we do for the chook and nethook programming. In the following example the user defines variables are written like this stringOpenParentheses : "(" #String for open parenthesis "(" stringCloseParentheses : ")" #String for close parenthesis ")" stringDelimiter : "|" #String for delimiter I think that makes it more clear to the end user what everything does. JM2c [POST_VERSION] #DO NOT MOVE OR ALTER THIS LINE# V23.00 P0 E1 W23.00 T1596718960 M23.00 I0 O1 # Post Name : CUSTOM POST # Product : Mastercam # Machine Name : MACHINE # Control Name : CONTROL # Description : MASTERCAM POST # Subprograms : YES # Executable : MP v11.0 # Post Revision : 0 # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- Break ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # -------- Start of Miscellaneous Strings -------- # stringOpenParentheses : "(" #String for open parenthesis "(" stringCloseParentheses : ")" #String for close parenthesis ")" stringDelimiter : "|" #String for delimiter # -------- End of "Miscellaneous Strings" -------- # # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- Break ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # -------- Stat of "Header Info" -------- # pheader$ #Call before start of file "%", e$ !spaces$, spaces$ = 0 spathnc$ = ucase(spathnc$) smcname$ = ucase(smcname$) stck_matl$ = ucase(stck_matl$) snamenc$ = ucase(snamenc$) stringOpenParentheses, "MCX FILE - ", *smcpath$, *smcname$, *smcext$, stringCloseParentheses, e$ stringOpenParentheses, "NC FILE - ", *spathnc$, *snamenc$, *sextnc$, stringCloseParentheses, e$ stringOpenParentheses, "MATERIAL - ", *stck_matl$, stringCloseParentheses, e$ spaces$ = prv_spaces$ # -------- End of Header Info -------- # # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- Break ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # -------- Start of "Comment Info" -------- # pcomment$ #(must call pcomment2 if booleans) pcomment2 pcomment2 #Output Comment from manual entry !spaces$, spaces$ = 0 scomm$ = ucase (scomm$) if gcode$ = 1008, stringOpenParentheses, scomm$, stringCloseParentheses, e$ #Operation comment if gcode$ = 1051, stringOpenParentheses, scomm$, stringCloseParentheses, e$ #Machine name if gcode$ = 1052, stringOpenParentheses, scomm$, stringCloseParentheses, e$ #Group comment if gcode$ = 1053, stringOpenParentheses, scomm$, stringCloseParentheses, e$ #Group name if gcode$ = 1054, stringOpenParentheses, scomm$, stringCloseParentheses, e$ #File Descriptor spaces$ = prv_spaces$ ##### Stop custom changes ##### # -------- End of "Comment Info" -------- # # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- Break ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # -------- Start of "Start Of File" Info -------- # psof$ #Start of file for non-zero tool number ##### Custom changes allowed below ##### peof0$ #End of file for tool zero peof$ #End of file for non-zero tool # -------- End of "Start Of File" Info -------- # # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- Break ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # ---------------------- ------------------------# # -------- Start of "End Of File" Info -------- # peof$ #Write the G28 A0. Line n$, "G28", "A0.", e$ #Write the % EOF Line n$, "M30", e$ #Write the M30 Line #mergesub$ #clearsub$ #mergeaux$ #clearaux$ "%", e$ #End Region # -------- End of "End Of File" Info -------- #
  11. byte me

    GPO-3 Fiberglass

    Yeah Colin is right, these jobs are best done on a routet with a dusthood, it said on google it's fibreglass reinforced laminate so watch out for chipping!
  12. byte me

    Threadmilling problem

    If you cut the feed more, maybe you wouldn't have to chase it at all? It sounds like a classic case of tool deflection.
  13. byte me

    Tool lIst with Z depth

    Very interesting, what other information are you trying to capture? I've been shoving a bunch of tool and operation data in the comments, but that has limited size..
  14. byte me

    Organizing toolpaths

    I never actually use stock models unless I have to do something special to the leftover material, there is something wrong with my setting that, when I cut slots in the side of a panel the top "skin" is missing, which makes it pretty useless...
  15. byte me

    Tool lIst with Z depth

    So is all this to write the minz/stickout of the tool in your nc file at post time?

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