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:


Verified Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Manofwar last won the day on August 12 2018

Manofwar had the most liked content!

About Manofwar

  • Birthday 05/17/1993

Profile Information

  • Gender
  • Interests
    Machining, of course!


  • Location
    Fort Collins, CO

Recent Profile Visitors

1,998 profile views

Manofwar's Achievements


Apprentice (3/14)

  • Reacting Well Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges



  1. Check all fluids. Had a similar issue once on a Mazak I300 with a smooth control where the fluid had just gotten low on the thermal compensation tank.
  2. Do a search for "DPAS rating chart" you should come up with a .pdf made by DCMA. Almost everything everyone has posted falls under this document, which lines up with the verbiage you're using. "Title 1 of the Defense Production Act (DPA) of 1950 is the statutory basis for the Defense Priorities and Allocations System (DPAS). Title 1 is also one of the non-permanent provisions of the DPA that needs to be periodically reauthorized, which Congress has done in the past for periods of 1 to 5 years. The DPA provides the President with the authority to require acceptance and priority performance on contracts and orders, and to allocate materials, services, and facilities to support national defense and emergency preparedness requirements. The President has delegated his priority and allocation authority to the Department of Defense, the Department of Homeland Security, and the Department of Energy according to resource required." As you can see from the above excerpt, they can do a lot more then force you to start making a part you bid/won on. They can force historic parts on you if they can't source them from another shop(s) for some reason. DO and DX are ratings that fall under DPAS, with sub categories for different types of equipment under them. The person you talked to previously was most likely referring to a sub category under the DPAS umbrella. Hopefully the document provides some clarity.
  3. @Slick Not using MC for this. Running another CAM software at the moment. Time to run was about 6 minutes. I know from previous experience that Mastercam was pretty good with times. If you removed tool changes and other ancillary actions from the machine, the time would be about +-5% of the predicted time. (At least for the machines and posts I was using.) This would change significantly for the 5 axis paths if you were running something not COR as the machine would have much further to travel for each move.
  4. Sorry I missed the responses to this. I did get it working. @Greg Williams Program isn't built with Mcam, so I can't share a file. @?Mark FGroup alone wasn't fixing the issue. I did every combination I could think of for this. FGroup (X,Y,Z,C) still made the C axis very slow during C only moves (probably around 20% of what it should have been moving). @Slick The machine does have TRAORI and it is commanded during machining. Fix I found for this with Mark's help was to add FGref[C]=1.000 where 1 is the radial distance from center of the cylinder. Of note that both FGroup and FGref needed to be below the CYCLE832 line in order to function.
  5. Like the title says, I'm seeing issues with feedrates on a DMG Mori DMU-40 with a Siemens 840d control. Issue is during a 5x path (simple pocket routine wrapped on a cylinder and locked to 4th axis.) the machine feed during Y (or X) only moves is moving drastically faster then when C is commanded as well. The machine is running G94, I did already try FGROUP commands, but with little success. Time estimation in CAM for cycle is around 5 minutes, on machine it takes about an hour. Uncertain where the issue is. Any help would be appreciated.
  6. Hi all, trying to get a custom cycle up and working on a siemens 840d DMU 40 FD. But, I'm having some troubles with the tools orientation when running at anything that's not 0. on the B axis. The custom cycle is designed to interpolation cut a groove into the face of a part at any size and location. However, when the machine rotates the part to the angle desired, the spindle SPOS (or SP) commands don't track to cycle 800. They rotate to the absolute machine coordinates. Is there anyway to get the spindle to clock against the cycle 800 without doing the math for each rotation?
  7. It's been awhile since I used Mastercam. But I believe this has to do with whether the post supports it. You could add it to the post if you really wanted it as an option. Video on Youtube shows how it is done here. If you just need it once, the machine should support it and you can just edit the G84 line with a 'Q' telling it how deep you want per cycle.
  8. That's pretty deep for that size tap. I would switch to peck tapping. Most taps at that size only have 7mm of flute. So the odds are high that the upper portion of the tap is blocking the coolant from doing it's job. As well as the chips from escaping (on the spiral tap.) If you have tapping fluid, use it. Normally at this size I would use a roll tap to avoid the issue of chip pack, and peck tap to depth. Takes a bit longer, but better then breaking taps constantly.
  9. What material, depth, and machine are you running this on? Peck tapping may help out with this issue, as well as using a better lubricant (such as Moly tapping fluid.)
  10. Diagnostics -> Parameters. It should show you a list of options. It will probably be listed TCPC and DWO.
  11. There is a excel document that can help with these settings. Haven't run an Integrex in awhile, but I think I still have a copy of it somewhere. If you haven't got it yet, DM me and I'll see if I can get it over to you. I use to work on both the old controls and the newer controls, but I remember K124-K126 had to do with COR as well as S5 and S12 values. (this may not be valid on the Integrex machines.) If the machine was recently crashed or overloaded, you could have other issues. I had to write Pitch Error tables to the machines after problems like this. (Not a common issue, this would be last resort, and done by service. Unless you have previous experience doing this.)
  12. For all who were curious. I don't believe passing a 2D array to a Cycle is currently possible. I tried multiple ways implementing this and couldn't get it. The book doesn't list an escape character, or those listed don't work. I also tried to concatenate in a comma using a temporary place holder variable to hold the comma, this also failed. If anyone else comes up with a solution (not that it's need, more out of a fun problem) please post it. Below is how I ended coding it. 1D arrays. PFS would be run before the drill is called (hence the Boolean check at the top for running the sub) and assign values to them. IF _PFS_RAN <> 1 CALL "PFS.SPF" IF RS_Main_Loop <> 0 GOTOF ("OPERATION_"<<RS_Main_Loop) RS_Main_Loop=8 OPERATION_23: ; 04_Port_Drilling CALL "PREP_LINE.SPF" T="MIT_DRILL_3937_2D_140" M6 S970 M3 M73 M7 M161 D1 G60 IF RS_Sub_Loop <> 0 GOTOF ("Port_"<<RS_Sub_Loop) RS_Sub_Loop=2 Port_2: CYCLE800 (0,"TC8",100000,57,-2.03389,-7.33396,-1.4988,43.939,-10.892,0.,_PFS_X[2],_PFS_Y[2],0,-1) CALL "23_04_Port_Drilling_02.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_3: CYCLE800 (0,"TC8",100000,57,-1.03847,-7.3891,-0.52993,44.72,-5.648,0.,_PFS_X[3],_PFS_Y[3],0,-1) CALL "23_04_Port_Drilling_01.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_4: CYCLE800 (0,"TC8",100000,57,5.11368,4.60438,-1.19746,-33.788,31.701,109.373,_PFS_X[4],_PFS_Y[4],0,-1) CALL "23_04_Port_Drilling_07.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_5: CYCLE800 (0,"TC8",100000,57,3.80065,5.85249,-1.10746,-39.986,22.651,180.,_PFS_X[5],_PFS_Y[5],0,-1) CALL "23_04_Port_Drilling_06.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_6: CYCLE800 (0,"TC8",100000,57,2.22723,6.85471,-1.90209,-43.563,12.621,180.,_PFS_X[6],_PFS_Y[6],0,-1) CALL "23_04_Port_Drilling_05.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_7: CYCLE800 (0,"TC8",100000,57,-3.67067,6.3578,-0.78282,-40.893,-20.705,180.,_PFS_X[7],_PFS_Y[7],0,-1) CALL "23_04_Port_Drilling_04.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=RS_Sub_Loop+1 Port_8: CYCLE800 (0,"TC8",100000,57,-7.45717,-0.26041,-0.52993,1.999,-44.965,271.413,_PFS_X[8],_PFS_Y[8],0,-1) CALL "23_04_Port_Drilling_03.SPF" G00 SUPA Z=-.5 RS_Sub_Loop=0 G00 SUPA Z0. RS_Main_Loop=24
  13. This video covers the data array tables much better then I can describe it. https://youtu.be/YK8hqu3qukU You can stack CYCLE800, I just don't like that method, as additive mode can be dangerous. By using the built in X1, Y1, Z1 you position shift after calling position and rotation without having to post out multiple CYCLE800 lines or using additive mode. I'm machining 3D printed parts. Because the feature location drift a bit from print to print some features get defined as machine in place. (capture local data and machine locally.) So, I load the part, run a program to probe those feature locations, save that data to an array named _PFS[n,m] (where the array is loaded into a GUD as DEF NCK REAL _PFS[30,2] before hand) it would look like the example below. (Example only) Port 3 location X-.0067 Y.0032 ^ This data is stored from the probe as _OVR[5] for X, and _OVR[6] for Y. I store this data in the array like this: _PFS[3,0] = _OVR[5] (This stores the actual X deviation) _PFS[3,1] = _OVR[6] (This stores the Y deviation) Then later on, in the actual machining program I can call that data from the location as you would call any variable. This causes an issue because of how the data is delimited in both arrays and cycles. The array needs the comma to tell it row, column. The cycle needs it to move to the next field. In the below picture you can see what happens when the control hits the comma in the array. It sees "_PFS[1" sees a comma so it moves to the next field and types "0]" the same would happen for Y1 except it starts in the Z1 and moves outside of the range of CYCLE800's displayed fields. Hopefully this provides a clearer picture of the problem. There are other many other ways to perform this task, I just wanted to see if I could get it this way.
  14. The cycle type is not the issue. I'm using CYCLE800 as an example. The problem is passing a 2D (or 3D) array to any cycle. Cycle800 works fine from the post and on the machine. Currently I don't think this can be done. I believe only 1-dimensional array variables can be passed to cycles. I may rewrite what I'm doing to use that. However, if anyone has a solution for 2D/3D arrays being passed to cycles please post it.

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