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:

Daniel_E

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Daniel_E

  1. Thanks for your input. I was considering this method but have started down a different but very similar path. I may end up changing my plans. I think my current plan is essentially the same as what you are suggesting, but rather than output the entire nc file with "markers", I was thinking I would write to the buffer for each path as it is processed (with the total path length output as the last record). This means that all motion postblocks that would normally output to NC, will now be outputting to buffer instead. After each path is completely output to the buffer (pretract probably), I would first access the final record to get the path info I need, output as needed based upon that info, then directly output from the buffer to NC for the actual motion toolpath. After this, it would repeat until complete. Does this sound reasonable to you?
  2. What I need to know is the machined path length for each individual contour (chain of entities) within the program. It would be great if there was an op parameter that contained this data but I've not been able to find one. So, I've already successfully worked out the logic to calculate this without any difficulty....the problem is doing it BEFORE the output. The reason for this is an attempt to simplify and automate the programming of our laser. I would like to know the length of the path because this data would change our decision about what power settings to use (primarily for heat control reasons).
  3. Hi. I'm new to this forum and I see a lot of really good stuff here. I'm hoping someone can help with my situation. Sorry to dig up an old thread, but this is the only reference I've been able to find to the problem I'm trying to solve. The partial quote above mentions that when MP performs the NCI pre-read, that the motion calls are ignored. I have an application where I would like to analyze the actual tool path geometry before posting the final program. Is there a way to do this? When reading MP documentation, it states that the "Entire" NCI is processed....which may not be true. Any input would be much appreciated. Daniel

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...