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:

motor-vater

Verified Members
  • Posts

    378
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by motor-vater

  1. 19 machines give or take 8 - 3 axis mostly with rotary's 5 - horizontals 6 - 5 axis All Mills All the time We have lathes to but I got a guy for that
  2. Possible from linking motion being speed up? chocking on code?
  3. I see the same behavior on our haas's all the time. I could say some not nice things about the machines but I wont. Hopefully you can use the G187 setting as mentioned above, Our machines just alarm out when I tried so I have to assume its a paid add on that we opted out of. If that doesn't work you are gonna need to play with your tolerance .0004 os pretty tight for a haas, creates alot of code and the control will chock on it.
  4. SHOT IN THE DARK, FREE ADVISE TAKE IT AT FACE VALUE Maybe parameter 19696.5,19746.4, 19754.5. All needed adjustment on my Mori's when we went to the postibility post that utilized G68.2 into a G43.4 move But getting James involved is the greatest of all moves. He has fixed more things with my machines then the actual MTB Programing Coordinate TCP.pdf
  5. DEFINITLY AXIS SUBSTATUTION. I have done this and its fun, Really only necessary in a few situations where travel limits come into play, But If you are just wanting to make YouTube videos, Axis Sub will get u the results, assuming your post is pretty good. Had no problems with my postibility.
  6. We have predator we are slowly phasing it out and have been using Fanuc's program transfer tool. Love its Awesome drag and drop capabilities. Down side is its only for Fanuc
  7. I figured my ip guys were the ones creating havoc. They have been steady locking everything down. Glad to know its just the entire Mastercam community experiencing it as well. Thank goodness for ematercam
  8. So I have always ran the model through model prep, removed history, etc than hit the file drop down , configuration and then switch mastercam from imperial to metric. It will ask if you want to scale the model answer is yes, Done. Usually I have the reverse work flow to turn metric models into Imperial though. In that case I open a new Mcam file switch to metric via same process, then import my metric model, model prep, switch to imperial, Scale Model, Yes, Done It is important to have Mastercam in the correct metric or imperial configuration before importing any model, or things get weird. If its a metric model start in metric mode, if Imperial start in imperial mode. I'm sure their are many ways, but this works 100 percent of the time for me
  9. Super old school option.... Use a Contour, then translate/rotate the contour around the radius ROTARY WORK.mp4
  10. Hey Colin, Merry Christmas my man, Definitely an ezier way, but you know me love beating my head against the wall. We do more castings as of late, So I am becoming better with everyone. I try to get them Qualified and straight into a 5 axis where I have the functionality. We are using vericut, Camplete and anything else we have to. We even got a 3D scanner, to make a raw casting STL. All of that and they are still my least favorite thing in the world. Lol
  11. cant wait to get into this thread over break, looks like a lot of good info. I have always taken the simple approach. If I have rotations going in my Horizontals, I program from COR, set matercam up with my planes associative to a point, Go back the machine do some measuring and move my point to make up for any fixturing error. It sucks but I have always been able to get within a thou. any thing tighter I'll just set up a different work offset. If you have accurate models of your tombstones, or pallets in your case, you can get it pretty good. As for castings, God I hate castings!!! But I try to fixture to datum target points and usually don't need to shift after the initial set up. All of that just to say I have been doing it wrong.. lol I Just wish our horizontals had dynamic work offsets, or Work shift error enabled, probe and go would be a God Send!
  12. thread mill, you can use a small chamfer mill and taper angle, kind fun to play with. I too was bored once. lol
  13. funny, I have been holding onto that Library since I don't even remember when, but like you I have had very few uses for it. But I no doubt will need it someday and I apricate the work that went into making it.
  14. EXACTLY!!! I have tried a model based program, and then tried to incorporate a changed version through the change recognition inside the info tab, mind you this was an experiment with a very simple model maybe 15 toolpaths just to see how to use the change recognition option and OMG did I almost loose my mind. Sounded like a great idea to learn something new until I had several hours into trying to figure it out with less then optimal results... Never again
  15. Im so glad to know I'm not alone in my decision to still use wireframe. I was afraid to tell people because I thought they would call me a Dinosaur
  16. I have seen random arrow changing direction since 2021, or at least that's when I think they changed drilling. But fortunately for my machines we use Vericut, and or Camplete. Ive actually started to venture away from using solids to generate toolpaths, Which is sad because I truly love the simplicity of it. But every time I attach a path to the model, If I modify something on the model everything attached blows up, and models need to have history removed then regenerated in the solids tree, before I can regenerate toolpaths, Sometimes you can not save because of a dirty model, and then you have to do all the above mentioned. This sucks especially as I'm heading out the door at the end of a day.
  17. YUP RANDOM FILE GROWING WITH NO CHANCE OF SHRINKING THEM BEEN GOING ON WITH US SINCE 2021. Many threads on the Mastercam form about it. My work around is if I see it growing I save all solids I need as STP then open a new Mastercam file import STP models and start over! If you allready have toolpaths you can export them then import to new file, Seriously a real PITA!!!!
  18. I am very limited on my knowledge of Macros, but have found some success over the years. Nothing for nothing in order for my macros to be able to use Goto lines and things that make them jump around they have to be saved on the machines Memory. Thats on Our Mori's with a Fanuc Control. I wasted alot of time testing in MDI and trying to write into programs that ran on DNC just to finally cave and call the Mori apps guy, He told me that I needed to save the macro into the memory and then call them from the program. Kind of how the renshaw macros work. So I tried it and now I seem to have better luck with my macros functioning as expected. This might not apply to you or anyone else but works for me.
  19. I probably would these days too. but in my defense the one I did was 40 inch's long and the fastest way to get material out was a 2 inch shell mill and a 6 inch saw. Back then I wasnt to hip on using 5 axis paths like triangular mesh locked in 3 or 4 axis, these days I would love a part like that to show up.
  20. I have done pylons like this before, I would not even hesitate to go with saw style cutters and old school toolpaths like Surface finish Contour. I think the biggest issue I see are the drilled holes at 90 deg. One of the ones we did was to big to even fit in the 5 axis, We had to stand them on their side and use a horizontal with an anglehead. Bottom line you are gonna want to dig out as much material as you can how ever you can and then (pro tip) let it rest and requalify before adding features of tolerance. This thing is going to warp... Have fun, these are the kinds of projects that you are going to learn alot
  21. Update, Test part back from inspection. I am doing something wrong in the errors page for sure... My holes were shifted + 0.028 in my X direction. Every thing else I cut seemed right... Manager loosing patience, sad because I am this close to making a life changing thing happen in our set up and they want to shut me down when I'm 0.028 from the finish line. Lol Im gonna give it one last go in the AM before everyone gets there. So any last minute suggestions are appreciated. I have my G54 set to the theoretical perfect point of Origin (which is where I am programed from in mastercam) I calculated that from the Standard G54 point kept on the control for COR) I am trying to figure out the best way to set the errors. What I am doing is setting the B axis orientation to get my part straight, then probing the center of the part to get my X while the part is in its new B location. I am using G58 to store the values. Then basically subtracting the location of my G54 from G58 to update my error Values. In todays case that was b-.101 and x .0469 and a z of -.0544. Am I doing this wrong? Any last minute help super appreciated
  22. was getting a few depending on format. I should have wrote them down, so I'm just going off memory here for now. Originally it was illegal G68 command, on the G69, then I tried moving the G54.4 above the G49/G69 and started getting an illegal WSEC error it became obvious The G54.4 P0 does not want to be before the G49/G69. So moved that back and tried some other stuff but oddly enough removing the G05 P0 gets rid of the illegal G68 alarm, but why the illegal g68 alarm on a G05 P0 has me scratching my head. Ill post some shorter cycles tomorrow for more detailed info, But I had that spindle shut down for 4 hours today playing around, so I gotta be mindful of our customers. Lol While I got you on the hook James I have a question about the error values in the Wrk setting errors. Try to imagine my part be a U shape, in the machine it is an orientation where rotating around the b axis would turn my U into a C. Now when I first load, I am probing the center of the U for my G54. Thats where the part is programmed from. But Then I must rotate my B axis to get the legs of the U even...... Still with me? Today it took -0.101 deg on the B to get there, So I enter that error into the b on my error page. My question is when I come down and reprobe the center of that U it has Moved/Followed and is now .120 shifted in my X. So do I enter that into the x on the error page aswell, or does it just know to follow cause of the b error adjustment. I ask cause I almost wonder if I should just find and set my rotational error first, then just probe the Center of my U with the B axis at -.101 to the G54 and be done with it? But as I am typing I am thinking probably not a good idea, but How do I find the theoretical perfect position of the part as it was programmed when it has to be skewed to get to that position. Probably why some would Use COR for this I think. Then all you are measuring are errors, Sorry Long winded I am and I hate to take advantage of your kindness, But Lunch on me sometime when we cross paths... Edit: Just dawned on me I can steal the theoretical perfect numbers outta mastercam, Just create a plane at COR and get the values of my Origin point and enter those into my G54. Then that should make my b and x error values valid. Maybe. LOL If that works I would never need to reprobe my G54 and could spend all my energy on the errors...

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