Alex Dales

Administrators
  • Content count

    42
  • Joined

  • Last visited

Community Reputation

28 Excellent

3 Followers

About Alex Dales

  • Rank
    Post Dev Team

Recent Profile Visitors

798 profile views
  1. Alex Dales

    update postprocessor

    You can also check out the Migration Wizard to update your machine and control definition files if needed.
  2. Hi Joey, Try looking for pcomment$ or pcomment2 instead. pcomment$ can be called multiple times by a single comment$ call and is used to read in comments, manual entries, machine name, etc. If you write a string variable using scomm$ when gcode$ is 1008 that will save out the operation comment. mpmaster already does this using a variable called scomm_sav to prevent the operation comment from being output in the header of the post, and move it to the first toolchange. You might even be able to get away with calling scomm_sav in pbore2$ where you currently have comment$. Just note that this will only work correctly if your operation comment is a single line. If you want multi-line support you will need use a buffer to store out the comments, in which case I would recommend going through your reseller to get a dedicated post developer like me to take care of it for you Alex
  3. you can use the dot3 MP function. result = dot3(a,b) where a and b are the first variable of two different unitized 3D vectors. In this case you will want to use the tool vectors of the two drill points you want to measure in between. since the vectors are unitized, the denominator of the formula above will collapse to 1. Thus the angle between would be the cosine of result.
  4. Alex Dales

    Operation Name

    Our IKE posts also come with support for a generic HTML Setup sheet. There is support for some minor customization with these setup sheets. I have attached a screenshot of one I just generated from a part I had on my system.
  5. Alex Dales

    Operation Name

    Here at the in-House post department we have recently created a c-hook that allows us to pull the cycle time that is shown in the Mastercam backplot. This .dll is only compatible with our IKE posts, and is currently available for no additional charge to users of those posts. This is a fairly new feature, but all IKE posts sold since the release of this c-hook will have support for it. As far as I am aware, the only other way to get a semi-accurate time when posting is quote cumbersome. You need to measure the feedrate and distance of each move, the distance from the home position, the acceleration/deceleration, toolchange, etc. Basically have the post simulate and time everything in the background and spit out the time it finds. I have never gone through and done this personally, but I have worked on a few posts where this was setup. My understanding is that it can provide fairly accurate time estimates with the right amount of tweaking. I would not recommend trying this unless you are very experienced with posts and have a lot of time on your hands.
  6. Alex Dales

    In House IKE Post Processors

    With IKE posts the Tool plane orientation does not matter. We use the Z-axis orientation only and map all XY motion as needed. Makes programming much easier. I agree with you on the vector programming. I works great most of the time, but I don't trust the machine to move the same direction the post is calculating. I have seen some crashes and bad motion in vector mode that could have been avoided using rotary angles.
  7. Alex Dales

    In House IKE Post Processors

    We are really excited about the new products we have been working on in the Post Department at In-House. IKE (Pronounced to rhyme with Mike) is our new generic post engine that we have had in circulation for the last few years. It is designed to solve for any kinematics that is defined in the machine definition. We also in include calculation options for any coordinate output style, ie. TCP, Tilted Work Plane, Trunnion shifts. We have a large library of IKE posts developed for most available controllers. Each of these controller-specific posts supports the various machine functions such as G43.4 and G68.2 for Fanuc, or TRAORI and CYCLE800 for Siemens. We also have IKE posts for Lathe machines, which has its own great features like a much more intuitive part handling section for machines with sub spindles. Our IKE posts also contain a little-known secret - A free generic setup sheet that can be generated when posting the code. IKE+ is our new interface for code free post editing of IKE posts. It offers customization of all the things mentioned above, and so, so much more, with even more control and customization coming down the pipe. While it is still in a fairly early stage of development, we are currently only offering IKE+ to resellers. I would love to so some Beta testing in the near future to benefit from the knowledge and experience we have on this forum, so stay tuned for that.
  8. Alex Dales

    How long to get a new post?

    Here is a link to our post request form. https://www.emastercam.com/post-request/ If you fill this out we normally submit a quote to the reseller the same day, or early the next day depending on when it received. Delivery times on new post can very based on the complexity of the machine. Usually about a week. Quick changes and rush scenarios often also get expedited. I will message you directly through eMastercam to continue this discussion.
  9. Alex Dales

    DYNAMIC WORK OFFSET

    DWO on a Haas Next Gen Control is G254. Is is disabled using G255. It basically just shifts your coordinate system as the part moves. So if you touch off your G54 on the corner of the part then swing out your trunnion, you can active G254 then go to X0 Y0 Z0 and you tool tip will land back on that same corner, no matter what angles the trunnion is at. It is used with 3+2 operations. This Haas video also shows the datum tracking with TCP very well.
  10. Hi Leon, I am not completely sure what sort of output you are looking for but if you are using an MPMASTER style post, I would point you towards tseqno in the general output settings at the top of the post. tseqno : 0 #Output sequence number at toolchanges when omitseq = yes #0=off, 1=seq numbers match toolchange number, 2=seq numbers match tool number
  11. Hi Alan, We discussed this via email, but if anyone else come across this issue, we discussed a solution to use cuttype = 0 to indicate lathe toolpaths and set dia_mult to 2 for those, and 1 for all others. Cheers, Alex
  12. This is something I have done before. You can use the op_id$ variable in ptlchg0$ to check for a new operation along with the misc value to trigger this. You can call the ptlchg$ post block to force a full toolchange and then use the ex$ command to exit ptlchg0$ to avoid posting out a full toolchange and a null toolchange in the same instance. I would recommend you have your post provider and/or Mastercam reseller get involved to ensure the post mods are done correctly.
  13. Alex Dales

    Heidenhain 530 4th axis

    You can adjust your limits (middle left) or set your axis type (bottom right) to match your machine's rotary. The TNC also uses a M126 to enable shortest path on the machine which corresponds to shortest direction axis type on this page.
  14. Alex Dales

    Endless C-Axis Swiveling

    Your C-axis value is calculated from your tool vector. If your tool is tilted off very slightly, the post calculates the C-axis value that allows for that tool vector. When tools are near vertical you can end up getting large c-axis movements. If your machine has a vector mode and/or a smoothing mode you might be able to use that. Otherwise, you are relying on the physical rotary positions that are calculated. You could change what is being calculated by programming in 3-axis mode, or by adding a side angle/led-lag angle the tilt the tool away from vertical and avoid the instability.
  15. Alex Dales

    Approach after unwind problem

    That is not what is occurring in this case. If the A was much closer to zero and we were going from C0 to C180 then we would have that issue. The C0 and C180 are not the issue in this case. Here we are hitting the machine's limit at A30 and changing solutions to A-30. I have heard of machines in vector mode will run into this limit and move the machine from A30 C0 to A-30 C180 with the tool down, which does not end well. We are avoiding that here by send the machine home in Z before calling the new A and C. Thanks, keep me updated. I agree, I am not a big fan of the motion either. I doubt this is the issue, as the start of the tool path is using G43.4 and not crashing. Always a good thing to check though, as it could have enough clearance on the first but not the second.

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