-
Posts
447 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by Zoffen
-
-
i changed a parameter and it goes the shortest rout now.
-
i tried forcing my C output to 1 degree indexing in the mach def but that had no effect.
It appears to me that the logic isn't built into my post. Can someone point me in the right direction what logic i have to add to the post. I probably have to add some variables then capture parameters from the machine definition but then where would i place this logic?
Or can someone post some of their logic out of their post for this?
thanks a bunch!
-
I've run into some weird problems with C Face contour.
I tried contouring a cirlce. Code should be simple x move in, c rotate 360 then x move out.
On this file with the circle i'm trying to contour at (center) 0,0,0 this is the code:
O00000001 G20 G52.5 T0505.00 M200 M8 G90 G0 G54 Z.155 X7.156 C0. G97 S2500 M203 Z.005 G98 G1 Z-.395 F20. X6.956 F30. C360. F494.21 C720. C1080. C1440. C1800. C2160. C2520. C2880. C3240. C3600. C3960. C4320. C4680. C5040. C5400. C5760. C6120. C6480. C6840. C7200. C7560. C7920. C8280. C8640. C9000. . ..(Code truncated for length) . C65160. C65520. C65880. C66240. C66600. C66960. X7.156 F30. G0 Z.155 M9 G28 U0. G28 W0. H0. M205 T0500 G99 M02 %
this code is obviousely not right. However if i move the center of the circle .0001 in the x direction i get code i can atleast run:
O00000001 G20 G52.5 T0505.00 M200 M8 G90 G0 G54 Z.155 X7.1562 C0. G97 S2500 M203 Z.005 G98 G1 Z-.395 F20. X6.9562 F30. C1.935 F494.2 C3.871 C5.806 C7.742 C9.677 C11.613 C13.548 C15.483 C17.419 C19.354 C21.29 C23.225 C25.161 C27.096 C29.031 C30.967 C32.902 C34.838 C36.773 C38.709 C40.644 X6.9561 C42.58 C44.515 C46.45 C48.386 C50.321 C52.257 C54.192 C56.128 C58.063 C59.999 C61.934 C63.869 C65.805 C67.74 C69.676 C71.611 C73.547 C75.482 X6.956 C77.418 C79.353 C81.289 C83.224 C85.16 C87.095 C89.031 C90.966 C92.902 C94.837 C96.773 C98.708 C100.644 C102.579 X6.9559 C104.515 C106.45 C108.386 C110.321 C112.257 C114.192 C116.128 C118.063 C119.999 C121.934 C123.87 C125.805 C127.741 C129.676 C131.612 C133.547 C135.483 C137.418 X6.9558 C139.354 C141.289 C143.225 C145.16 C147.096 C149.031 C150.967 C152.902 C154.838 C156.774 C158.709 C160.645 C162.58 C164.516 C166.451 C168.387 C170.322 C172.258 C174.193 C176.129 C178.064 C180. C181.936 C183.871 C185.807 C187.742 C189.678 C191.613 C193.549 C195.484 C197.42 C199.355 C201.291 C203.226 C205.162 C207.098 C209.033 C210.969 C212.904 C214.84 C216.775 C218.711 C220.646 X6.9559 C222.582 C224.517 C226.453 C228.388 C230.324 C232.259 C234.195 C236.13 C238.066 C240.001 C241.937 C243.872 C245.808 C247.743 C249.679 C251.614 C253.55 C255.485 X6.956 C257.421 C259.356 C261.292 C263.227 C265.163 C267.098 C269.034 C270.969 C272.905 C274.84 C276.776 C278.711 C280.647 C282.582 X6.9561 C284.518 C286.453 C288.389 C290.324 C292.26 C294.195 C296.131 C298.066 C300.001 C301.937 C303.872 C305.808 C307.743 C309.679 C311.614 C313.55 C315.485 C317.42 X6.9562 C319.356 C321.291 C323.227 C325.162 C327.098 C329.033 C330.969 C332.904 C334.839 C336.775 C338.71 C340.646 C342.581 C344.517 C346.452 C348.387 C350.323 C352.258 C354.194 C356.129 C358.065 C360. X7.1562 F30. G0 Z.155 M9 G28 U0. G28 W0. H0. M205 T0500 G99 M02 %
yet when i open a new file and do the same exact toolpath with the circle center @ 0,0,0 i get the code i actually want:
O00000001 G20 G52.5 T0100.00 M200 G90 G0 G54 Z.25 X4.6982 C0. G97 S0 M205 Z.1 G98 G1 Z0. F0. X4.4982 C180. C360. X4.6982 G0 Z.25 G28 U0. G28 W0. H0. T0100 G99 M02 %
WTF? is this a bug or is something in my file affecting this?
-
figured it out. i'm an idiot.
accidently turned on dry run
-
640T Nexus
-
so i tried some code out today. big fail(no crash of course!)
This is on a Mazak QT350M with C and live toys.
i tried a g12.1 but all i got was an illegal g code alarm. I thought i might not have that option but it lists G13.1 in the active modal commands. Do i have to have a Milling tool specified in the tool data?
Then if i MDI'd g98c180.F1000.00 the c would position to C180 quickly.
in my program however it would go MUCH slower. I looked at the F on the display and it read 10. instead of 1000. ?!?!?!
The program was ignoring/changing all my other feed rate commands too!
is there any reason why it would ignore my feedrate command? I'm ready to tear my hair out!
Could it be the way the tool is set up? I'm new to Mazaks and no one in my shop has run ISO code through the lathes, but maybe it takes the tool definitions alot more seriously in ISO mode than i thought.
the tool was defined as a drill so maybe that could be my problem? I only get limited time to play with these so i don't wanna break down our production setups.
Any help would be greatly appreciated, maybe a g12.1 milling example too
Any code examples would be exteeeeeeemly helpfull as i'm new to this machine, c-axis, and live toys. Gotta love learning through the good ole crash course!
thanks a bunch for the help, i'm gonna need it!
-
I'm wondering if there is any reason why always using g12.1(Polar Interpolation) for face contour operations would be a bad idea?
just a thought as i'm building my post.
opinions? comments?
-
found this in my post:
#C-axis variables for calculations c_axistype : 0 #1 = C axis winds-up, 2 = C axis signed absolute #3 = index positioning, 4 = shortest direction (do not set here, use string) rev_brkflag : 0 #Revolution break flag. 0 = No break, 1 = Break every 90 or 360 degrees (see plin0$) ipr_type : 0 #Feedrate for Rotary, 0 = UPM, 1 = DPM csav : 0 #Initial c axis result from pxyzcout call czero_csav : 0 #Save csav when circle at zero detected c_wnd : 0 #Calculation for c axis position tracking (abs-wind) prvc_wnd : 0 #Saved cout calculation from deg., this is cabs in mpfan rev : 0 #C axis wind-up multiplier prvfrdeg : 0 #Feedrate deg/min actual circum : 0 #Circumference ldelta : 0 #Linear distance for deg/min, linear cdelta : 0 #Total linear and angular motion for deg/min cdelta_calc : 0 #Rotation calculation cldelta : 0 #Calculation for deg/min, linear and rotary sav_rev : 0 #Saved revolution counter indx_out : c9k #Rotation direction calculation fmt 17 frdeg #Feedrate deg/min actual fmt 20 indx_mc #Rotation direction calculation
and this:
#SET BY MD - Variables to capture parameter values - use to set post switches in pset_mach rot_axis : 0 #Axis of rotation - 1=X, 2=Y, 3=Z rot_type : 0 #Rotary type - 0=signed continuous, 1=signed absolute, 2=shortest direction rot_dir : 0 #Rotary direction - CW is positive, 0 = false, 1 = true rot_index : 0 #Index or continuous - 0 = continuous, 1 = index rot_angle : 0 #Degrees for each index step with indexing spindle component_type : 0 #Component type: (See documentation for complete list - ) #0 = MACHINE #1 = STOCK_COMPONENT #2 = MISC_COMPONENT #3 = MACHINE_BASE_COMPONENT #4 = LINEAR_AXIS_COMPONENT #5 = ROTARY_AXIS_COMPONENT #6 = RECT_TABLE_COMPONENT #12 = CHUCK_COMPONENT #24 = TOOL_SPINDLE_COMPONENT #23 = ATC_COMPONENT xpos_dir : 0 #X Axis direction flag ypos_dir : 0 #Y Axis direction flag zpos_dir : 0 #Z Axis direction flag axis_label : 0 #Axis label - 1=X,2=Y,3=Z
-
Sorry, not too familiar with the MT post, did you try changing things in the MD?
yes is is set to 0-359.999 in the MD. It looks to me as if this logic isn't built in already.......
-
What post are you using?
Changing these below from zero to two worked for me...
pang_output : 2 #Angle output options, primary sang_output : 2 #Angle output options, secondary #0 = Normal angle output #1 = Signed absolute output, 0 - 360 #2 = Implied shortest direction absolute output, 0 - 360
I am using GENERIC FANUC 4X MT_LATHE post.
I cannot find pang_output and sang_output either
-
How do i limit my C axis output to 0-359.9999?
Is there a benefit to doing this at all? i feel it might be simpler code for c-x contour toolpaths.
-
Both are chained the same direction and are offset the same (right/left)
lol i tried again and they bost post the same direction now!
damn u mastercam, i guess a restart is needed sometimes.
-
I'm having some trouble with a Mazak lathe at work.
With the axis @ C0.0, if i MDI C10.0, then C5.0, the machine will go to C10.0 in the positive directions, then go to C5.0 but go all the way around in the positive direction instead of going in the negative direction.
Is there a parameter i can change to force the C to go to that absolute position in the shortest direction?
Also, how do you all like to program your c for c-x contour moves? This is all a learning experience so anything helps lol!
thankx!
-
I have two c face contour c axis toolpaths, both backplot in the same C directions but one posts out C+ and one posts out C-
Am i missing a setting in the toolpath somewhere?
I tried setting the rotary direction on the C axis in the machine definition but it didnt change anything?
what am i missing here? any help would be greatly appreciated! thanx!
-
figured it out.
i'm a retard!
you need to have subprograms active for canned cycles to work.
gotta love spending a few hours scouring your post only to find out it was just a checkbox lol!
-
I've gotten the Generic Fanuc 4ax lathe post to output canned cycles but for the life of me i havn't been able to figure out how to make a stock Fanuc 2ax lathe post to output Lathe canned cycles. It outputs all longhanded code. I have the canned cycles checked in the machine def and i have the longhand code option unchecked in the toolpath.
any help this is driving me CRAZY!
thanks a bunch!
-
Hey all,
is there a convertor to convert dimensioned solidworks files to mastercam files with MBD attached to them?
thanks!
-
how would i look for the operation type, i.e. face, rough,finish, groove.
what parameter/variable am i looking for here?
thanks a bunch!
-
still not working. would like to get this running as i have ALOT of post work to do!
any help would be greatly appreciated.
still get the same error as last time.
-
How would you post a tooltable at the end of your program right after an m30?
Tried Ptooltable at Peof but it only output the first tool????
any hints?
thanks a bunch!
-
how do you do it?
can't figure out how to creat the new geo on another level.
thanks a bunch!
Nevermind i figured it out!
-
how do you do it?
can't figure out how to creat the new geo on another level.
thanks a bunch!
-
could someone post an example of reading from a buffer file(text file) and inputting that data into the post.
thanks!
-
I'd suggest posting that question over in the Post Processor forum.
One of the Post experts should be able to assist.
sounds good. thanks!
Mazak 510c-II Spindle/tool problems
in Machining, Tools, Cutting & Probing
Posted
2006 Mazak 510C-II with a Matrix Controll.
Recently, while hogging with a 3" facemill @ around 900RPM, @ random points the spindle would start making a noise that seemed like a dying dog howling. The sound was definatly cyclic in nature. After stopping the machine to investigage and finding we couldn't reproduce the noise, we would start running the program again and all was fine untill the next day, when the noise came back. This is the same cutting parameters, they varied from 125 IPM @.050DOC to [email protected] DOC for that tool (in mild steel)
This started last week. We haven't run any new programs on the machine as now other things are acting up
Now when changing a tool, the drawbar will catch and engage the tool but the tool will not be fully seated into the taper. when u turn on the thru spindle coolant you can see it shooting out the gap between the taper and tool holder.
Any hints on to what our problem could be?
What could that noise have been? I feel it has something to do with some spinning mechanism in the drawbar assembly.
thanks for the help!