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:

huskermcdoogle

Verified Members
  • Posts

    1,284
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by huskermcdoogle

  1. Countersink or Counterbore? How accurate do you need the feature to be? Or is this just deburring. If it is a counterbore, Steiner Technologies Autofacers work well. Not terribly expensive.
  2. Yeah I am going through my reseller on this (OPTIPRO) at the moment, they wanted some sample files, so I am tossing a few together in how I am using this feature (one that works in X4 and one the doesn't in X5). Hopefully they do something about it, but if they don't I can't let myself get too beat up over it, afterall what can I do other than make them more aware. Thanks, Husker
  3. Yeah I can go back to X4 for most of my files, but not the one I am currently working with (too much work invested in X5 version), but for future projects I don't want to get stuck between a rock and a hard place.... Husker
  4. So what are those of us sopposed to do that just upgraded from X4 to X5 and now can't post our old programs safely in X5. I just ran into this by mistake and am now very very very very pissed becuase I cannot use a workaround like described above, way way way too many ares to make mistakes, and would take forever. I need this to work now, in fact the priject I am working on now has been posted out fine in x4 and I am leaning toward finger camming the changes that I need / most of my changes will be in the subs. Looking at the previous build date, looks like it went hairy between x5 and x5 mu1. Can they just roll another mu to fix this and any other minute details before going to X6? Guess I am going to have to roll back to X5 without the MU on it. grrrrr...
  5. Isn't it a fanuc control? Makino Professional Series Front End. Anyway if so, should be tied to #3901. There may be a pmc k parameter that you could set to automatically update this upon M30. Otherwise just add the following line immediately above your M30 #3901 = #3901 + (number to increase by). ex #3901 = #3901 + 1. Give that line a shot in MDI and it would update the parts counter. Husker
  6. I changed the precision from .00001 to .0001 and the code matches the backplot now. This seems to be the opposite to what the posts in the link were saying. Anyone have anything to comment on this. Thanks though, this gives me more footing in understanding the issue at hand for future applications with this problem. To solve it yesterday I ended up just doing a swept 2d toolpath which output the shortest code, in fact even shorter than the filtering could do with a surface finish blend toolpath (same stepover and end product result). Thanks for the help. Husker
  7. Guys I am having a wierd issue when filtering a toolpath. First off the toolpath should be following an arc path almost perfectly when doing a surface finish blend toolpath (blend is between two arcs with same xy center). Once I create the path and set the tolerance at .001 and the turn on arc filter, I will get backplot results that would be acceptable. When I post the code I get mostly line segments and very few arcs but there are a few arcs still intermingled in the code here and there. There seems to be no ryme or reason to it. What the hell am I doing wrong. Is there something in the MPMaster post that is breaking up the arcs that backplot is showing. If you have any quick ideas or would like the zip to go let me know and shoot me an email for the file if you want to take a look at it. I can make due without this toolpath for the time being but at the moment am I very frustrated that I cannot get the results that I am looking for here. [email protected] Thanks, Husker
  8. Is there a way to break up the motion with a transform toolpath rapid move to go retract xy then z? Husker
  9. Yeah that is all set up part to part. But not between tool paths. I want to go to Z home before any index or between any transform operations that have no index or tool change. The other problem is it is not splitting up the xy and z movements between subs on the approach so even if I were to put in manual entries it does me no good. Husker
  10. I have an issue running the MPMaster Post. When I am transforming toolpaths for my tombstone 4 parts verically and also rotating to a different face, it won't retract sometimes when there isn't a rotation change. Sometimes it will sometime it won't. Here is an example. code: <20-10454A-OP10> (20-10454A-OP10) (MASTERCAM - X) (MCX FILE - FAMILY - #2 - 20-10454A - PRODUCTION.MCX) (POST - MAZAK HCN 5000 - X2) (PROGRAM - 20-10454A-OP10.EIA) (DATE - MAR-08-2010) (T25 - Q04.304 - 3/8 CARBIDE EM - H25 - D25) G00 G17 G20 G40 G80 G90 G91 G28 Z0. (T25 - B0. - .690 HOLE - MILL) (TOOLPLANE NAME - TOP) N25 T25 M06 (Q04.304 - 3/8 CARBIDE EM) (MAX - Z5.0745) (MIN - Z-.8925) G00 G17 G90 G54.1 P5 B90000 X1.4865 Y1.9385 S8000 M03 G43 H25 Z5.0745 M08 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P6 X1.4865 Y1.9385 Z5.0745 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P7 X1.4865 Y1.9385 Z5.0745 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P8 X1.4865 Y1.9385 Z5.0745 M98 H1014 (COOLANT COUNTER BORES AND ANGLE CUTS 90 SIDE - 0 PARTS - B90.) (T25 - B90. - COUNTER BORES) G90 G54.1 P11 X-3.7625 Y2.5325 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P12 X-3.7625 Y2.5325 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P13 X-3.7625 Y2.5325 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P14 X-3.7625 Y2.5325 Z5.07 M98 H1015 G91 G28 Z0. (COOLANT COUNTER BORES AND ANGLE CUTS 90 SIDE - 90 PARTS - B180.) (T25 - B90. - COUNTER BORES) G00 G90 G54.1 P15 B180000 X-3.7625 Y2.5325 G43 H25 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P16 X-3.7625 Y2.5325 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P17 X-3.7625 Y2.5325 Z5.07 M98 H1015 (T25 - B90. - COUNTER BORES) G90 G54.1 P18 X-3.7625 Y2.5325 Z5.07 M98 H1015 G91 G28 Z0. (COOLANT COUNTER BORES AND ANGLE CUTES 270 SIDE - 0 PARTS - B270) (T25 - B270. - COUNTER BORES) G00 G90 G54.1 P21 B270000 X3.7625 Y1.1325 G43 H25 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P22 X3.7625 Y1.1325 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P23 X3.7625 Y1.1325 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P24 X3.7625 Y1.1325 Z1.045 M98 H1016 G91 G28 Z0. (COOLANT COUNTER BORES AND ANGLE CUTES 270 SIDE - 90 PARTS - B0.) (T25 - B270. - COUNTER BORES) G00 G90 G54.1 P25 B0 X3.7625 Y1.1325 G43 H25 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P26 X3.7625 Y1.1325 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P27 X3.7625 Y1.1325 Z1.045 M98 H1016 (T25 - B270. - COUNTER BORES) G90 G54.1 P28 X3.7625 Y1.1325 Z1.045 M98 H1016 (.690 HOLE 0 SIDE - 0 PARTS - B0.) (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P1 X1.4865 Y1.9385 Z5.0745 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P6 X1.4865 Y1.9385 Z5.0745 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P7 X1.4865 Y1.9385 Z5.0745 M98 H1014 (T25 - B0. - .690 HOLE - MILL) G90 G54.1 P8 X1.4865 Y1.9385 Z5.0745 M98 H1014 M09 M05 G91 G28 Z0. G28 X0. Y0. B0 G90 M30 Notice the lack of retract and safe approach between the first two operations (look at the sub number and offset numbers, happens twice on this tool), unlike the other operations. Is there an easy place in the post to output a retract and safe approach between transformed toolpaths only? Husker
  11. I am in full agreement here. It would make life much easier. It might be easier if the field was just tip height. So we could all run out and measure tip to full diameter length. All we would need for inputs would be tip angle and tip length. Husker
  12. Well Poop. That puts me between a rock and a hard place.... I have maint to go up to x3 for my hasp but not all of my coworkers do, so I can't go up. Well guess I have some fuel to go after updated maint for us. Husker
  13. Guys I have a file that is 200+ operations long, mostly they are all transform operations for a tombstone. Anyway, after I am in the operation parameters screen it will hang up for about 10 seconds after I close the parameters dialog. Then I can continue. This pause is really really bugging me. I also will hang for about 2 minutes when I save. The file size is about 12 MB. Is there anything I can do to improve this? When it is sitting there one of the processor meters it pegged and task manager says it is using 50% processor. X2 mr2 sp1 centrino duo quadro fx 2500m 4 gig ram Husker
  14. OK I removed the comment line in the header and it comes out good. But if I do a manual entry before my operations it goes back to not working right. Is there anyway to tie manual entries to thier own variable and not to the pcomment$. Husker
  15. Forcing doesn't really do it if I recall... I do believe that was one of the first things I tried. Do we have any other ideas? Husker
  16. Guys, I have been working on creating a post which just generates a file of sub programs. I use the program number in the operation to control the N number of the sub. That so far has been a piece of cake. The issue I am having is getting the operation comment to appear on the same line as the N number on the first operation / tool in the file. All of the subsequent operations are fine. Here is an example. I have been modifying the MPMaster post to get to where I am. I am running X2 MR2 SP1. Thanks in advance. Husker code: <TESTING> (TESTING) (MASTERCAM - X) (MCX FILE - TESTING.MCX) (POST - MAZAK HCN 5000 - X2 - NSUBS) (PROGRAM - TESTING.EIA) (DATE - SEP-14-2009) (T157 - 3/4 DRILL - H157 - D157) (T237 - 3/8 FLAT ENDMILL - H237 - D237) N0001 (T157 - 3/4 DRILL) G00 G90 X0. Y0. S356 M03 G43 H157 Z6. G17 G90 Z.1 G94 G99 G81 Z-.75 R.1 F4.28 Y2. X2. Y0. G80 Z6. M99 N0002(TAP HOLES) (T157 - 3/4 DRILL) G00 G90 X0. Y0. S356 M03 G43 H157 Z6. Z.1 G95 G99 G84 Z-.75 R.1 Q.1 F0. Y2. Y0. G80 Z6. M01 M99 N0003(CONTOUR OUTSIDE) (T237 - 3/8 FLAT ENDMILL) G00 G90 X-.9375 Y.625 S1426 M03 G43 H237 Z6. Z.1 G94 G01 Z-.5 F6.33 X-.5625 G03 X-.1875 Y1. R.375 G01 Y2. G02 X0. Y2.1875 R.1875 G01 X2. G02 X2.1875 Y2. R.1875 G01 Y0. G02 X2. Y-.1875 R.1875 G01 X0. G02 X-.1875 Y0. R.1875 G01 Y1. G03 X-.5625 Y1.375 R.375 G01 X-.9375 Z-.4 G00 Z6. M01 M99
  17. Got it working like a charm. Thanks for all of the help. This is what I ended up with. code: pdrlcommonb #Canned Drill Cycle common call, before ..... if custonoff, [ feedover = feedover/feed * 100 # put feedrate in percentage for G82 regfdpth = ((tosz_a - zabs - regfdpth)/regfdpth)*regfdpth # calculate I value for G82 ] else, [ feedover = zero regfdpth = zero ] .... pdrill$ #Canned Drill Cycle pdrlcommonb if custonoff & drlgsel = 0, [ drlgsel = 1 ] pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl, prdrlout, [if dwell$, *dwell$], *feed, regfdpth, feedover, pcan1, strcantext, e$ pcom_movea feedover, regfdpth, and custonoff, are variables that I defined, populated, and formatted from the on screen parameters. If anyone wants to know what parameters I grabbed shoot me a note. Thanks for all of the help guys, I learned a lot about post with this endeavor.
  18. "custonoff" is a variable that I declared and pass the check box parameter to. As far as using it in a logic statement that part works fine. The problem I am having is where to use the logic statement. I will try the above suggested code: pdrill$ #Canned Drill Cycle pdrlcommonb if mi2$ & drlgsel = 0, drlgsel = 1 pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl, prdrlout, [if dwell$, *dwell$], *feed, strcantext, e$ pcom_movea only this is how I will do it. code: pdrill$ #Canned Drill Cycle pdrlcommonb if custonoff & drlgsel = 0, drlgsel = 1 pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl, prdrlout, [if dwell$, *dwell$], *feed, strcantext, e$ pcom_movea I don't want to use a MI it doesn't seem as clean. For what I am doing here. The Custom Parameters Checkbox is much more appropriate. Thanks for all of the help so far. Much appreciated. I am still learning about mastercam posts as you aware. I have some C++ background and it is somewhat helpful, but some good reference literature, no matter how cryptic would be very helpful. Say for instance a list of common variables that are usable in any post by default. Having to track down a parameter that most likely is already stored in a variable, then put it in a variable is a pain in the butt. Though at least it can be done... Unlike some other cam systems.... Husker
  19. When you say mi statement you mean miscellaneous integer correct?
  20. Tried your suggestion. Didn't work. code: pdrlcommonb #Canned Drill Cycle common call, before if sav_dgcode = 81, [ if drillcyc$ = three, drlgsel = fsg1(-ss$) + drillcyc$ * two else, drlgsel = fsg2(dwell$) + drillcyc$ * two if clearflg = one & clearstrt = zero, drillref = zero else, drillref = one if absinc$, result = force(refht_i, refht_i) else, result = force(refht_a, refht_a) ] result = newfs (two, zinc) if drillcyc$ = 3, [ if mi6$, use_pitch = 1 else, use_pitch = sav_use_pitch ] pcom_moveb feed = fr_pos$ comment$ pcan pbld, n$, sgabsinc, e$ #ABSOLUTE if cuttype = one, [ initht_a = initht$ + (rotdia$ / two) #Initial Height Abs refht_a = refht$ + (rotdia$ / two) #Reference Height Abs tosz_a = tosz$ + (rotdia$ / two) #Top of Stock Abs ] if cuttype = three, #W is the current position during Gcode 11, it give refht for drill5ax [ initht_a = w$ + (initht$ - refht$) #Top of Stock Abs refht_a = w$ #Initial Height Abs tosz_a = w$ + (tosz$ - refht$) #Reference Height Abs ] if cuttype = zero | cuttype = two, [ initht_a = initht$ #Initial Height Abs refht_a = refht$ #Reference Height Abs tosz_a = tosz$ #Top of Stock Abs ] if sav_dgcode <> 100 & fmtrnd(initht_a) <> fmtrnd(prv_zabs) & opcode$ 3, #if using a ref point you need to update the XYZ coord before calling the drill cycle [ #this applies to ref points with opcode 3 only zabs = initht$ zinc = initht$ - prv_zabs sav_gcode = gcode$ if convert_rpd$ = one, [ gcode$ = one feed = maxfeedpm ipr_type = zero ] else, gcode$ = zero pbld, n$, sgabsinc, *sgcode, pxout, pyout, pfzout, e$ gcode$ = sav_gcode ] if cuttype = one, zabs = depth$ + (rotdia$ / two) #Depth Abs if cuttype = three, zabs = w$ + (depth$ - refht$) #Depth Abs if cuttype = zero | cuttype = two, zabs = depth$ #Depth Abs #INCREMENTAL (references absolute calcs) if drillref = 1, #(Inc from refth) [ initht_i = initht_a - refht_a #Initial Height Inc refht_i = 0 #Reference Height Inc tosz_i = tosz_a - refht_a #Top of Stock Inc ] else, #(Inc from initht) [ initht_i = 0 #Initial Height Inc refht_i = refht_a - initht_a #Ref Height Inc tosz_i = tosz_a - initht_a #Top of Stock Inc ] zinc = zabs - refht_a #Depth Inc if haas, [ result = nwadrs(stri,peck1$) result = nwadrs(strj,peck2$) result = nwadrs(strk,peckclr$) ] feedover = feedover/feed * 100 # put feedrate in percentage for G82 regfdpth = ((tosz_a - zabs - regfdpth)/regfdpth)*regfdpth # calculate I value for G82 pbld, n$, sgfeed, e$ if custonoff & drillcyc$ = 0, sgdrill = two Notice the if statement at the end. Is this where the problem is? Changing the value of sgdrill does not seem to change anything. My If statement logic works, so that is not the problem, at least I do not think it is....
  21. Yeah, I mentioned that earlier, but I don't want a dwell, granted I can put in a very small value, so it doesn't matter, I know myself and will forget to set a dwell as the switch whereas with the custom paramters I will not be able to forget when I go to turn it on. I would like to know how that works so that I can use it to my advantage. Plus I like to have clean gode so as to not confuse my operators. They always question codes that have not seen before.
  22. Well to put a long story short I have tried all sorts of things in that area to no avail. I can't really make out what they are trying to do in that logic right there. Can anyone shed some light on that? Esentially I need something with the logic that follows. #--- if switch on & g81 [ make g82 ] #--- I have the switch on part figured out. I grabbed that parameter and put in a variable called custonoff, But what is the Gcode stored in and what format is it in.
  23. Guys, I have been successful in getting custom drill parameters into the simple drilling cycle. Did some math and have it outputting like I want to. The issue I have is I cannot for the life of me figure out how to get it to toggle from G81 to G82 when I check the use custom parameters check box. Kinda like how the MPMaster post changes G81 to G82 when you add in a dwell in the simple drill cycle. I am using a modified MPMASTER post, modified for some formatting things but nothing major. All of the main functions from the MPMASTER post are still there and mainly untouched, except for what I added for the custom parameters so far. I am not looking for someone to do it for me, rather I am looking to learn more about post processor modifications. Through some educational nudges. I am running X2 MR2. Thanks, Husker

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