pullo

Verified Members
  • Content count

    380
  • Joined

  • Last visited

Community Reputation

125 Excellent

2 Followers

About pullo

  • Rank
    Advanced Member

Uncategorized

  • Location
    Helsinki , Finland

Recent Profile Visitors

1,037 profile views
  1. pullo

    Backing up the quick access toolbar in 2020

    Also one should remember when playing with the Workspace file is that the this file gets saved every time you exit Mastercam , so if you are developing the QAT or some other interface detail and you have several sessions open on your computer , the last session being exited is what you will end up saving on the disk... So first exiting the newly developed session and the exiting the older version will leave you with the older version of the Workspace file... Gracjan
  2. pullo

    X5 user, new here

    X5 was the last Mcam to have the whole manual in one book/file. So if you look inside the mcam 5 directory for .pdf files , you should find a 20 meg behemoth . That will be the user manual.... I think it's under \documentation... Gracjan
  3. pullo

    MC2020 Tool Tabs

    Since they are editable , I'm sure people will find this useful . Personally , I don't use them .... GRacjan
  4. pullo

    Benchmark 3.0

    3 min 39 sec for 2020. (the official v3.0 test ) Gracjan
  5. pullo

    5 axis positive rotation

    At least on a Heidenhain this movement is set by the control . M126 code is shortest path , M127 is shortest path off. Gracjan
  6. yes, choose the line , hit RMB (Right Mouse Button) and choosing one of the three colors for wireframe, surf or solid will change the color of the line. Another method would be to choose Analyze and change the color from there, RMB is more natural and the designed method for color control in 2019.. Gracjan
  7. pullo

    New Mikron

    This is not my opinion , as to have an opinion one would have to have a good practical knowledge of what one is saying (I only know HH very well) , but someone once wrote on the CNC - arena that Heidehain is the ideal control for a 5-axis machine. With other widely used controls , not so much... Gracjan
  8. pullo

    New Mikron

    In my opinion you will be thoroughly amazed by the Heidenhain control. Yes , the code looks a bit different, but otherwise , pure pleasure to use. Gracjan
  9. pullo

    Mastercam Appearance

    This number changing was only a thing in X9 . After that came Mcam 2017 and then all the bets were off again. Gracjan
  10. Usually this happens when you are extruding splines.... When a spline has a large point count , I don't know the head count above which the parasolid kernel produces these facets. Usually I reduce the number of points in a curve using Wireframe/Refit Spline to reduce the point count. But since you say that an analysis of the curve yields an arc as an answer, I'm a little stumped.... posting a file would help to help Gracjan
  11. pullo

    Rookie Mistake

    #variable definitions swcs_name : "" #PRM20014 swcs_name1 : "" swcs_name2 : "" # to check if there are different WCS's , they should all be the same fq 53 swcs_name2 "OOPS , rogue WCS in your program!!!! " pparameter$ # Initialize variables, and Run parameter table if prmcode$ = 20014 , swcs_name = sparameter$ #WCS name pheader$ swcs_name1 = ucase(swcs_name) ptlchg0$ # Null tool change swcs_name2 = ucase(swcs_name) if swcs_name2 <> swcs_name1 , q53 ptlchg$ swcs_name2 = ucase(swcs_name) if swcs_name2 <> swcs_name1 , q53 very basic stuff for anybody who dabbles in posts Gracjan
  12. pullo

    Rookie Mistake

    In the case you presented you could have the built in warning system of checking the WCS , but since you know that it's OK, you get warned by the post , but post it out anyway knowing all is fine in THIS CASE . it*s the 50 ops where one is programmed with a different WCS than all the rest that will overwhelm You , that's where my WCS check would be worthwhile ... Gracjan
  13. pullo

    Rookie Mistake

    I would say that a demand that all the WCSs in an NC-program are identical is a pretty universal demand. So why not make your post check that all your WCSs are the same as the one specified in the first operation ? That takes you out of the check loop. I have been doing that now for many years. Gracjan
  14. jlw , wanted more info about setting up the post , so here it goes : it's a table - table , with the B-axis vector always provided by DMG as in the picture: other than that , nothing special about setting up a post for it .
  15. So it turned out that my C-150 was just one special solution for one problem , but it would not have worked in general. It turned out that by tweaking two parameters in my Camaix post I was able to output the right angles without the C shift . Gracjan

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