Luke.Hicks430
-
Posts
38 -
Joined
-
Last visited
Luke.Hicks430's Achievements
Newbie (1/14)
5
Reputation
-
Accuracy of simulation in Verify for MC 2019
Luke.Hicks430 replied to Luke.Hicks430's topic in Industrial Forum
If there is, I didn't see it. -
Accuracy of simulation in Verify for MC 2019
Luke.Hicks430 replied to Luke.Hicks430's topic in Industrial Forum
Chris, The accurate zoom button fixed it. It is odd that the simulator does not dynamically regenerate when zooming. Thank you for the tip! Nickbe, thank you for your input as well! -
Hello Friends, I recently got a new job. My old workplace had MC X6 and my new workplace has 2019. I am having trouble increasing the accuracy of the visualization in the "Verify" window. In X6, I could just go to the options and specify the tolerance I wanted. I have not been able to find a way to do that in 2019. I have noticed in 2019 that there is a "Performance-------Precision" slider which I have all the way to precision. I am trying to verify a part's surface finish toolpaths and realized that the window I was looking at was very pixelated. I have attached a picture of the simulation of a simple arc cut that turned out very pixelated. How do I increase the precision beyond what the slider can give me? Is 2019's verify less precise than X6? Many thanks!
-
Colin, Thank you for the advice, I think that is a god approach. Any tips on how to trim the corners of the stock before the Dynamic in a way that doesn't kill my tool, or just go for it as a contour? I'm pushing for MC 2018 but it's a large chunk of change for a 25-person shop. I know it's worth it, but I think the hold up is cash flow. For now I make due with X6.
-
Luke.Hicks430 changed their profile photo
-
I would love to, but I don't control the budget.
-
Has the OD Corner stepover problem been addressed with newer versions of mastercam? The main problem I run into is using high-flute-count endmills. The Imco 9fl endmill has a maximum of .05 radial DOC. This means I would have to set my dynamic toolpath to use a stepover of about .015 to not violate the .05 maximum DOC. I'm not able to use my tool to it's fullest abilities. It would be nice to have a solution to this. I'm running X6.
-
C^Millman, In that report the library is still "OPERATIONS MANAGER", which is not what I want. I want the file name. gms1, Yeah we use our setupsheets, I was just hoping for a condensed tool list that I can send out to the shop floor so they can make sure we have all the tools we need on order. Which is what I get with Tool list, I just wanted the filename on it.
-
Dum1, I am saving over my template file, so it's already directed at it (I can see the changes as I am saving the file and re-generating the tool list). I only want the file name to show up (in your example: HAAS UMC-750 5X MILL SAMPLE FILE.MCX-9) not the entire file path. The basic tool list template uses the data field "LIBNAME" to put the full file name and path in there. I've tried making a sub report in my tool list template that references "//SETUPSHEET" and used the data field "MCXFILE-SHORT" but that just generates an empty field. Thank you for trying to help me!
-
gms1, Thank you for the reply. I gave that a try, I changed the file URL, I dragged the "MCXFILE-SHORT" into the sheet fro the bound list. And still no dice. I think at this point I have determined that MC doesn't feed a file name field into the tool list report, only into a setup sheet report.
-
Thanks C^Millman, but this is a simple fix and not valuable enough to my company to pay to have the sheet updated.
-
I spoke too soon. When exporting from the tool manager it used a different template (mill-simple instead of mill-opmgr). The filename I saw was from the regular template with the "LIBNAME" data field. I changed that to MCXFILE-SHORT, and it didn't work. The interesting thing is that LIBNAME isn't a registered data entry value in the help guide. LIBNAME doesn't work for my because it's the full tile name including the path, and I don't want the path, just the filename. Any thoughts?
-
I had not tried that, that works. But why does it work when I go through tool manager and not when I right click on my toolpaths and make a tool list?
-
Hello Friends, I am editing my tool list template using ActiveReports Designer and I am running into a problem. I want to have my MCX file name in the report so that operators can see the part number and the revision level (which we put in our file name). I made a text box and input "MCXFILE-SHORT" in the DataField, but it just gives me a blank box when i create the report. I'm not sure what the problem is. Can you not put the MCX filename in a Tool List report? One thing I have noticed is that under "fields" my "bound" field says "bound error: could not find a part of the path "C:\Windows\SST\Samples\Mill\SSM.xml". Woudl this be causeing my error? If so, how do I fix it? Many thanks in advance tool list sample.pdf
-
Duplicated value in tool table
Luke.Hicks430 replied to Luke.Hicks430's topic in Post Processor Development Forum
Much appreciated! -
Duplicated value in tool table
Luke.Hicks430 replied to Luke.Hicks430's topic in Post Processor Development Forum
Colin, That fixed it! Thank you! For my education, what is "gcode$ <> 1003" commanding?
