I'm hoping someone here has an answer: My first is.... This has been an issue since X9: I cannot open .asm files. No its not the solid edge software, the other programmers can open .asm files no problem. I can open .par files just fine, but its the .asm files that are the issue. Also... in 2017... my default printer does not match what I have set to default in the printers list. 2017 keeps resetting back to a Fax and not the printer I want to use.... not sure how to fix this.

Been using the ribbon bar and right mouse menu items that is customized to my needs. 2017 is so much more slower than X9. Saves slower, loads slower, loads parts slower. I did find the rotate planes icon and made it a ribbon button for ease of use. Printer defaults keep resetting every time I load mastercam 2017. When loading solid models, 2017 doesn't load the default machine.

This is very true, we do practice trepanning and use it often as needed. However, we are drilling 4.8" deep on a blank slug. Anyway.... results are in! Machine survived..... wow. 300RPM .002 IPR Spindle load: 23% Y servo load 75% ( 67% just sitting doing nothing ) Z servo load 64% it worked out pretty good.

304 / 304L SS Well... can't helix bore with an OTM drill nor pre-drilling as they don't recommend such applications. We do have a Y axis. I'll let you all know how this drill performs - will start cutting chips within the hour or so

Ah wow.... interesting. From what the machinist tells me, we've been using the 1.85" Seco drill without any issues on the machine. He did say the servo loads were pretty low, didn't really pay attention to them. I did verbally slap him for that lol, but this Puma is a 2015 model and on their brochure, they've updated a lot of their hardware on these so I would imagine the 3100 is a heavy duty lathe... hmmm We did however use a 3.875 dia OTM drill on the Doosan Mynx 7500 with ease on a cylinder part to bore a hole out for the lathe.

I have a stainless cylinder that is 9" od x 4.4 long solid block and would like to try to attempt drilling with a 2.875 OTM drill.... Question is.... will the turret break trying to handle that big of a drill or? I know the machine has 887 ft/lbs of torque on the spindle... but I wondered if anyone else has suggestions? I do need to bore to 7.11 ID.... -JD

Thats over complicating things........ sigh how does edit even work if its not selectable? I even highlighted the plane i wanted to edit and that wasn't working? Would i have to create another plane and edit it? it seems like a waste of more time than needed.... because simply clicking on a button in X9 to rotate planes was extremely simple and easy to do....

Our tool library is on the company network drives. Most of us share the tools so it makes sense for all of us to pull the right tools for the right machine and where they're supposed to be... that way it should eliminate "personal preferences".... /shrug Other than that.... I noticed one important tool missing: "Rotate planes" did they remove that / re-name it / or what?

...And they say 2017 is supposed to be the most stable bug free version evah! It takes too long to navigate in 2017 to do the tool paths I want to do compared to X9. 2017 crashes / locks up when I try to add separators to the right mouse button in a sub-drop down menu that has 19+ different icons. Its funny how the way MS word is fine with me, but when it comes to Mcam 2017... i've went back to X9 after programming one part. Clearly CNC software doesn't know the meaning of KISS.

Thx for all the information guys lol... I added a M05 on the G28 line.... there really is no loss of time with the M05 in program. Boss thinks its a Kaizen and wanted me to fill out a form, I told him its not. The amount of idiots I work with cause me to scratch my head in disgust. ( story for another day)

I fixed the first line description to what it does now without M19. my answer to the last question in the quote is yes - it was provided as default We've had the machine for 11 months - I'd presume it is a little older than that, but not much. However when I add M19 in the program itself, the spindle stops and orientates itself before M01. At tool change, the spindle does not rev up due to the M19 being in the NC program. Without the M19, the spindle behaves as stated in the quote. I think a M05 would be better than M19 in the NC program itself. Modifying the post file is the easy part tho.

Yea - all on me, I get that.... hah I did try the above mention and it wouldn't behave the way I wanted it to behave. Like it wasn't reading the M05 or something? Is there a certain spot in the program where it needs to be?

Would you happen to know where I can find that?

It does... and orientates for tool change. I wonder if it does more harm than good...

We've recently got a new machine about a year ago - a Doosan Mynx 7500... I'm wondering if anyone runs their machines in a certain way or there is a requirement for a M19 in the program to reduce wear + tear on the spindle? As in.... the code below is how we run it: During tool change, the spindle revs up to the previous RPM then orientates automatically. The machinist has been putting M19 in the program as shown below: What I'm wondering is if both of the two quotes above will damage the spindle or? If a M05 is required to follow immediately after M09, then whats what we'll have to do if we want the spindle to last without issues.

Well... one of the older guys (a dinosaur) wants to do it, he doesn't realize it would add time. I like the random tools as it is and its fine the way it is. Been running random for 11.5 years now and neither style bothers me all that much. I guess some people don't like it so the next time he brings it up, i'll just tell him to "suck it up buttercup".

Thanks guys!

So i could use the codes from the haas and change the g65 to m165?

Is there a way to change the parameters in the Doosan so we can get rid of random tools? We would like to match up the pocket and tools...

Would anyone happen to know any G codes to make the Doosan Mynx probe work so we can add it into our programs for ease of use instead of having to navigate thru edit -> reset -> GUI -> probe -> and so on.... We are able to do this for the HAAS, but Doosan? We've been running the machine for 9 months and I was hoping if anyone knew of a better way of doing things for it? Or a macro if any? -JD

Would anyone know of a custom canned drill cycle that does exactly what it should do and not having to manually type in all the codes? Here is what I want to do: a combination of G83 and G73: Drill will start at ref z.1 plane then rapid in Z-1.3" to eliminate air cutting time in a pre-drilled hole. Drill will start the G73 cycle for 1" then return to ref plane to clear chips then resume cutting from the previous spot at G73 for another inch and repeat till it achieves the 7" depth. Make sense? -JD

Would anyone happen to know the exact max speed per gear for this machine? I'm struggling finding this information =\ -JD

I lost the post somewhere, but I was wondering how do I go about creating custom viewsheets for standard planes? I mean as an example, we have 4th axis work at the normal 0, 90, 180, 270 planes and I want to save those then later import them... Does anyone have a step by step instructions for me somewhere if its not too much trouble? Thanks! -JD

Well... for my 100th post.... Good luck with Mcam! It can be a pain sometimes. Then again, this place is basically why I come here for all sorts of help n advice =D Most of the times, I get awesome answers =) Heck i spent 6 hours on a saturday experimenting with post processors at home till the point where I just gave up after trying so hard to understand how it works and what does what. It actually helps to understand some of that in case you need it. =) Those 6 hours paid off today at work when I decided on a whim to test out if our HAAS VF-6 can actually run g94 and g95 - which to my surprise it can so, my hopefulness shot way up since i renamed a Doosan post and control file over to the HAAS and well... they both are very identical with the exception of M29 and G13, so I made minor corrections and applied JParis' formula and wow.... life just got so much easier. I did a simulation on the new program first to see if any alarms appeared, then I dry ran the program off the side... then cut the part last. I'm happy to say it worked. So now... theres 5 years worth of HAAS programs >.< that need converted into the new format, then again... that is a small price to pay in the long run. Merry Milling! -JD

As funny as you think this may be, JLW, i'm learning mind you. @ JParis: thanks! That worked! I was trying to divide but the division formula wasn't working.