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:

Nickjones818

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Nickjones818's Achievements

Newbie

Newbie (1/14)

  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Hello, I'm not sure if this is the correct place to post this (ha ha, get it), but curious if its possible to adjust within the post the peck clearance on Advanced drill toolpaths. Being a sort of long hand drill cycle, it looks like values are driven directly from the NCI, so I'm not sure its even possible through the post, but figured id ask.
  2. Im not 100 Percent sure exactly which one this is based on.... Thank you, Collin, I'm still pretty new at all this, and I could not get this method to work. I don't have those specific post blocks in my post. I have prwttparm_custom and pparamter_custom. not sure if that makes a difference. (Are those blocks encrypted in the .psb file perhaps??) Anyhow, After combing through the MP reference guide once more I was able to use Opinfo(10042,0) This allowed the program number I assigned to be posted into the header of the program regardless of the toolpath operation I chose to start with. (which was my issue) pheader_custom #Customizable portion of header hour = int(time$) min = int((time$ - hour)* 100) if hour > 12, hour = hour - 12 if hour = 0, hour = 12 if year$ < 2000, year$ = year$ + 2000 prm_prog = opinfo(10042, 0) #Prog Number Lookup "%", pe spaces$ = 0 sprogname$ = ucase(sprogname$) *prm_prog, pspc1, scomm_str, sprogname$, scomm_end, pe #Was progno$, pspc1, scomm_str, sprogname$ <---- spathnc$ = ucase(spathnc$) smcname$ = ucase(smcname$) sextpst$ = ucase(sextpst$) I went ahead and kept the formatted variable, however, I imagine I could have just updated progno$. Does this approach present any issues? I can't seem to find any at the moment, but that doesn't mean they are not there.
  3. This is an MP Post, it's for a single turret lathe with live tooling and sub-spindle. We purchased from our reseller with a foundation for our specific machine, but have added a lot of functionality to fine-tune to our needs. The Chuck operations function very well and as intended when placed below a general lathe or mill toolpath.....but if you place a part handling toolpath first, the path still functions as intended, but you're left with a header that doesn't output the intended program number, its left null, I believe do to the NCI not outputting a 1001 line. I could place a point toolpath first, just to reposition the machine as sort of a dummy operation that will output what my post looks like it will need to assign the attended value to progno$.... and fix this issue like that, but I'm curious to know more about this, or if there is a workaround that can be explored?
  4. We own a Doosan 2600SYII Dual Spindle lathe here, and Long story short the first operation after a Manual entry is a Lathe Chuck operation. We are repositioning the sub so that we may use it as a Tailstock. In doing so...I'm noticing the NCI is not outputting a value for progno$ (NCI Line 1001) for this operation. pchuck$->pheader$->progno$......no value for progno$ to pull from....has anyone ran into this? any solutions i can explore?

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

×
×
  • Create New...