Alex Dales

  • Content count

  • Joined

  • Last visited

Community Reputation

38 Excellent


About Alex Dales

  • Rank
    Post Dev Team

Recent Profile Visitors

893 profile views
  1. in mpmaster we use have some logic to suppress toolchanges with single tool. Your post is likely to have something similar. if ntools$ = one, [ #skip single tool outputs, stagetool must be on #stagetool = m_one !next_tool$ ] Take note of the line: #stagetool = m_one setting stagetool to -1 will suppress the toolcalls. If you have a line like this without the # before, then try adding a comment to that line.
  2. The buffer is stored as a text file, so you can rename the files and change the path that the buffer reads to have multiple buffers in the same buffer number. I don't think you can change the size of the buffer with this method, so maybe best to just double up on two string buffers.
  3. Alex Dales

    Update Post from X5 to X9

    Starting with X9, the migration wizard only looks back 3 versions. so X6, X7 and X8. If you install X8 or earlier you can go all the way back to the beginning of time.
  4. n$ may not be the best variable to use since it can be used in a lot of places and might be incrementing at each location. You might be better of to create a new variable that you increment instead. Or initialize submacro at 100, and just add 1 to that variable at each instance.
  5. Thanks for the Info on this! I do all my post edits in Notepad++ and have yet to run into any of these issues. I will keep an eye out and see if I can break it when I have some free time.
  6. I haven't run into any issues when I have changed it as long as I have kept the .xml structure intact. Maybe I will have to look into this though
  7. You can edit the control text directly in the .pst file without even opening the machine or control definition. After you do this, be sure to reload the machine definition. this will reload the control text into the toolpath parameters and make it visible on the Misc real/int page. One other thing that can cause issues with the control text is the windows language. The windows language code contains a language and a region. Your control text is set as en-IN. If your windows language does not match the language in the control text then some versions of Mastercam will not recognize the control text. In MC 2020 or later, I always deliver post with en-US as the language. Mastercam 2020 fixed this language compatibility issues by allowing it to always read in en-US if the windows language is not found.
  8. Alex Dales

    NTX2000 using Mastercam

    Yeah we were really fortunate to have the opportunity to do the onsite testing along with the development on this one. Makes such a big difference, and makes me more confident the next time someone comes to us for that machine. Usually its "I don't care, just send what you have NOW", followed by 6 months of radio silence, then "It has never, ever worked!" so we gotta celebrate the wins like this NTX when we can!
  9. by recreating the plane, I mean that we remap the coordinates to the new coordinate system created by the tilted plane function. this is different and more complicated than the simplified method of pulling the values directly from the tool plane. There is lots of online resources detailing matrix rotations and other methods that could be used, but all are pretty math intensive. the vequ() function reads and writes a 3D vector or point. The way that it is being used here is to set the xabs series of variables (or the xabs point) to the x$ series of variables (the x$ point). If you wanted to remove the line xabs = vequ(x$) you could replace it with the following three lines to achieve the same outcome xabs = x$ yabs = y$ zabs = z$
  10. Alex Dales

    NTX2000 using Mastercam

    We got a customer up here in Canada who got one of these earlier this year. We set them up with a new post we developed for the machine and did some onsite testing to dial it in. They have been running smoothly with this post for the last couple months.
  11. I have written posts for similar machines, but never done an MVR personally. Usually the only entry you would have to make for the RAH would be a misc value or axis combination to indicate it is being used. The post should be capable of calculating the index angle and mapping the coordinates to the programmed plane. If you are going to attempt to do this on your own, you need to be aware of your axis orientation. X and Y motion is good, but getting the X and Y in the right direction is also important. In our posts, we recreate the plane based on the Z axis orientation to match what the machine is using, but if you are trying to keep it simple, always use toolplanes already that match the plane defined by the G180. This makes is much easier to compare the code in your backplot to the code you have generated to ensure the moves match up. Something like mpmaster that doesn't use a coordinate rotation will be able to get you pretty close just by pulling x$ values as it does. From there the main thing you need is your C-axis calculation, which can be found based on the X and Y components of the tool vector.
  12. Alex Dales

    change 4th axis rotary output

    Hi Ron, one_rev is a post switch that is used along with Signed Continuous for the formatting of the A-axis starting position. It does not overwrite the existing setting for the rotary axis type. So my above description was not entirely accurate. To be more correct, it should read: This post switch keeps the STARTING rotary axis values between 0 and 360 when using a signed continuous rotary. Here is some additional detail on one_rev and how it is not equivalent to activating Shortest Direciton, although the two are often used in place of one another. For any 3+2 toolpath with Signed Continuous and one_rev active the code will look just like Shortest Direction is active, and the code will be the same. Where you will see the difference is when crossing the 0/360 margin with a 4-axis or 5-axis cut. Shortest direction will behave as usual and remain within the 0/360 bounds. ie. A358 A359 A0 A1 With the signed continuous, even when one_rev is active, the axis will still wind up past 360 (or into negative numbers when decreasing). ie. A358 A359 A360 A361 You are still able to break out of the 0/360 limits as required (Crossing that boundary with shortest direction coordinates on a signed continuous axis will not end well). What the one_rev switch does is control the STARTING point of the rotary axis for a given toolpath, so that the FIRST point always falls in the 0/360 limits. Hopefully that all made sense, but if not left me know and I can try to provide additional detail. -Alex
  13. Alex Dales

    change 4th axis rotary output

    I just looked through the original post and I noticed that switch one_rev was active in the post. This post switch keeps the rotary axis values between 0 and 360. I suspect that was a big part of the issue here and I don't see any mention of it in this thread
  14. oh and "ZED" not "ZEE" hahaha
  15. Absolutely right. Most of the time having these in separate post blocks is completely redundant. But every now and then when we run into a custom application where it is a huge time saver. As far as standards go, all these posts are coming out of Canada.... I can tell you my height in feet and inches, but if you want that in cm I will need to I read what is printed on my drivers license. We can't all agree on one language to speak either. PS. There is a "U" in colour, and centre ends with "RE" not "ER"

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