yep...you can physically align your C axis (you will need to pick your origin again after), or thru basic rotation and you wont need to pick up your origin again. I used both with success (via probing cycles)

I think the idea is that if u have 2 holes machined precisely at a certain distance in a previous operation and you want to use them to align your part in a next operation, it not necessarily mean that they will be aligned along one direction(almost impossible to align them by eye). I'm guessing he's asking to align a part between 2 holes machined in a prev operation and just put the part on the table as close to the desired position and pick up the misalignment with the probe. If in his setup those 2 holes needs to be aligned along Y axis then he needs to take 90 from the resulting angle. It all depends on how those holes are in his setup. That's why as a rule you need to find the actual displacement on X and Y between holes, and use with ATAN formula, because it's practically impossible to put the part by eye on the table and the holes to be in the desired alignment. Then from here many scenarios can spawn depending on where those holes needs to be, maybe they are at 45deg( in I don't know what scenario).

What if the real distance between holes is not actually 10. T1M06(PROBE) G0X-5.Y0 G43H1Z5. G1Z-.2F50. G65P9914D.5Q.1R.1 #600=#135 (X) #602=#136 (Y) G0Z5. X5. G1Z-.2F50. G65P9914D.5Q.1R.1 #601=#135 (X) #603=#136 (Y) #605=#601-#600(X DIST BETWEEN HOLES) #606=#603-#602(Y DIST BETWEEN HOLES) #530=ATAN[#606]/[#605] ...ETC ...ETC ps..1st probed hole is on left

Correction on Tim statement TRAORI "CAN" be active in a swiveled plane (CYCLE800). You gotta deactivate the system frame for swivel head/table 1st.

It's a empty string scorn : ""

MCALL CYCLE83(1.,0.,.05,-15.,,-10.,,-.01,,,1.,1,3,.1,,,)

"You do NOT interrupt a running process to MDI an offset register."---that's a response to your scenario buddy...and to answer to that I ask you this..how you can come to this scenario in witch YOU said you want to change the cutter offs in tool register while you cutting something. You can of course...lol.. Again..lol, you don't know my experience but from your answers I see I'll smoke you in any major controller Sinumerik, HEIDENHAIN or fanuc on any aplication for them mill turn, 5x, probing, macro.....lol.. Run a 5x mill turn dual channel then we'll talk... For me if u have 30-40y experience doesnt matter 2much. You can work for that time and still not know 2much. Cheers

Bud...lol...u really didnt't like a chalange...lol..u got 2much of a ego.. "An F-Word feed value can be on any line but it MUST be on a line with a G-Code interpolation command IF there is no modal value" ----not true.. "Secondly, I was speaking about changing the VALUE in the offset register and NOT the register number."-same..you change offset value, then go mdi run D # again then run.. "It's obvious you weren't trained properly in CNC Programming or in using a FANUC control because your code looks like a bloody abortion."------lol..I see U r not trained buddy..I use 2run codes like u, and btw..u dont know how my codes looks like..but if u wanna c a sample I can providit 2u..maybe you'll learn something ...but I doubt buddy..u just venting

Same here..I dig what djstedman said..lol...most of that stuff works when you set-up a part. After thet I update my MC file and preety much stays sthat way until we deicide to improve things like different cutters machines or whatever...

"A Feed value only needs to be on a line with an interpolation G-Code"....lol...Where in the Fanuc (or any other controller) manual you read that? There are 2 things to that: 1-st If you r using for a tool just a single feed value then that's the way to go: "S2000F10.M3"...why?...easy for everyone to see and change the cutting parameters...and u cannot beat that. 2-nd If u r using different feed values for a cutter, I always have those values in the beginning of the tool change for the same reason. Me,operator or whoever, can easily see/adjust the cutting parameters for that tool Ex: #510=200.(FEED FOR ..) #511=80.(FEED FOR ..) S2000F#510M03 ……….....and again u cannot beat that. “If you have multiple features using CRC, forget about adjusting the value in the register while the machine is running.”… ..do you wanna do that?ok.. So..you run the cutter then let’s say you stop and check a feature what you just machine with that cutter then you change the tool offs and then just hit start again and continue? That’s the scenario?(that if you don’t wanna go back and re-machine the features already finished with the old value) Ok..if u do that, no one stop you, when you realize that you need to change that value, changeit in tool register, go in MDI and run just the D value again…then continue…same thing, but again ..you don’t need to have the D declared all over the program. Operators do that a lot, especially with feed val…in the middle of a tool if they wanna change the feed and they don’t want to reset, they just go in single block, stop, go MDI, new feed value, back to machining, simple. If I have different D values (rarely) for the same tool (I preffer different aproach), same thing like with feed, I put their value in some #. Sorry bud, but who gives you the right to say what’s standard practice or poor practice btw. As I pointed above for every example I give you an answer, and a better solution. Just getting stuck in one only way of doing things on bashing other ones way of doing things, if they r different then yours, don’t make u right. But don't worry there is allways room for improvement, and all our life we learning something...that if we want... Cheers

Didn't get it....did I offend someone??...lol..sorry if I did ...just look after Jim Carrey in this short clip, and u'll know why I say "sorry" to often... lol

That's how my posts look like pccdia #Cutter Compensation #Force Dxx# if prv_cc_pos$ <> cc_pos$ & cc_pos$ & mi8$=1, prv_tloffno$ = c9k sccomp if (mr1$ = 1) & (comp_type = 1), scorn if cc_pos$ & (use_g43 = 1) & (tloffno$ <> prv_tloffno$), tloffno$ ptlngth pbld, n$, [if use_g43=1,"G43", *tlngno$, pcutter_comp_new], pfzout, *scoolant, e$ pcutter_comp_new if (tool_typ$ >= 9) & (tool_typ$ <> 12) , *tloffno$, !tloffno$, Don't bother about "use_g43" var, beeing a Sinumerik hardcore fan and user, I tried to emulate on fanuc same behaviour, so I change my tool change macros on all machines so they will load at tool change the tool offs by default with H_tool# and D_tool# so in my codes there are no G43 H or D, just codes, so if the guys r changing tool # they do it in one spot, and that's it, easy and simple. You can still use different HD values but if they want they must add them. Line in tool change macro: G91 G0 G43 G#3 Z-[#[10000+#4120]+#[11000+#4120]] H#4120 D#4120

Sorry guys...I'm doing what PCRobotic wants to achieve for Fanuc Controllers for like 20y...no problems. It's very easy for operators to modify the D H values when they set-up the parts since there are only in one line. Very easy to find and change values. I also have in the previous line my RPM and feed, and they loveit like that. " S1200F45.M03 G43H1D1Z1.M08 " Cheers

Do not worry about this. When u will transfer the file in the controller all lines will be automatically renumbered by the controller.

Ok.. I assume U have a machining program for the part, so the idea is to ad in the beginning of your program a new tool=>tool sensor. How you do it is your responsibility. I was just suggesting to use those commands but may not work on your machine. I'm not there and I don't know what cycles U got on the controller. Then the actual codes for the probing are inside a subroutine which must be located in the same directory like your main program. Please familiarize yourself firs with the controller, how the subroutines work on Sinumerik. Read an operating/programming manuals. I made the subroutine for U in a zip file because for some reason i cannot attach on this forum files with extension *.spf (maybe an admin can fix that). See attachment. Cheers PROBING.zip

I assume Z0 & X0 are on part center X0 I don't know where it is that's why I create a local variable for it "X_POS" Just change the value as desired. I also assume we R working with G54 We aiming to have the small boss dia 1.7 positioned at Y0 Z-0.35 when your A=0 As U see i create a sub called "PROBING.SPF" (U create the file and paste the data in there) wich can be called from your main program. Put the "PROBING.SPF" file in same directory like your main asuming U have your main in workpieced dir. If your main is in program dir put the sub in subrutine dir. If I remember on those machines U should have a comands for bringing the probe in/out. PROBEIN/PROBEOUT If it so, your main program shoul look like that: . . . PROBEIN M01 PROBING ;U must load the subrutine ;or EXTCALL "PROBING" ;U don't load the sub PROBEOUT M01 . . . About loading or not the sub I preffer the non/loading option because I can alter the sub from the network. Remember also to ensure your probe is calibrated. ;your "sub" start from here: PROC PROBING DEF INT COUNTER, PROBING_NR DEF REAL X_POS, Y_BOSS, Z_BOSS, A_POS, A_INCR, A_ORIG X_POS=3 ;change X probing position here. PROBING_NR=2 ;number of time U want to probe the boss 4 more aquracy ;----display options: _CHBIT[10]=1 ;Display of measured result screen 0=HIDE 1=SHOW _CHBIT[11]=1 ;Acknowledgment with NC start 0=NO Acknowledge 1= Acknowledge _CHBIT[18]=0 ;1==> Measurement result screen retained until next time.. ;..measuring cycle is called on measuring cycles version 0==>No effect DATUM: G54 D1 COUNTER=0 LOOP1: REPEATB DATUM G90 G0 X=X_POS Y0 A0 Z=(3.55/2+1) _MVAR=104 _SETVAL=1.7 _ID=-(3.55/2+1) _MA=2 _KNUM=0 _PRNUM=1 _FA=5 _TSA=300 _VMS=0 _NMSP=1 CYCLE977 Y_BOSS=_OVR[6] G90 G0 X=X_POS Y=Y_BOSS Z=(3.55/2+1) _MVAR=100 _SETVAL=(1.7/2) _PRNUM=1 _MA=3 _KNUM=0 _FA=10 _TSA=300 _VMS=0 _NMSP=1 _EVNUM=0 CYCLE978 Z_BOSS=_OVR[16] IF Z_BOSS>0 A_INCR=1 ELSE A_INCR=-1 ENDIF A_POS=ACOS(Y_BOSS/0.35) A_POS=(A_POS*A_INCR)+90 A_ORIG=$P_UIFR[1,A,TR] $P_UIFR[1,A,TR]=A_ORIG+A_POS COUNTER=COUNTER+1 STOPRE IF (COUNTER<PROBING_NR) GOTOB LOOP1 REPEATB DATUM G90 G0 Z=(3.55/2+1) A0 M17 ;..ends here ...GOOD LUCK Let me know how it goes

I think I can help U here. But to fully understand the situation I need more info, dimensions, so from U to share a Mastercam file with the part in the desired position will be the best thing 2do.

Hi there. In your post initialize this variable in case it is not: fmt 2 tlrad$ #tool radius format Then at "ptlchg_com" , after your M06 add this lines: spaces$ = 0 pbld, "CHECK_RAD(", *tlrad$, ")",e$ spaces$ = 1 On machine create this user cycle called "CHECK_RAD" : PROC CHECK_RAD(REAL TOOL_RAD, REAL _TOL) DEF REAL FACTOR_SCALING DEF REAL ACTUAL_TOOL_NR DEF REAL _TOL_UP DEF REAL _TOL_DOWN IF $MN_SCALING_SYSTEM_IS_METRIC==0 FACTOR_SCALING=$MN_SCALING_VALUE_INCH ELSE FACTOR_SCALING=1 ENDIF ACTUAL_TOOL_NR=$TC_DP6[$TC_MPP6[9998,1],1] ;CAPTURE TOOL RAD IN SPINDLE IF _TOL==0 _TOL=0.254/FACTOR_SCALING ;DEFAULT VALUE FOR TOLERANCE IN MM ENDIF _TOL_UP=TOOL_RAD+_TOL _TOL_DOWN=TOOL_RAD-_TOL IF (ACTUAL_TOOL_NR>_TOL_UP)OR(ACTUAL_TOOL_NR<_TOL_DOWN) GOTOF _ALLARM _END: M17 _ALLARM:SETAL(65000) M00 ;CUTTER COMP ERROR M30 What will happen: after each tool change your post will add a line CHECK_RAD(tool_rad) where tool_rad= your active tool radius the cycle wich I made 4U will check that your posted value for that tool and the value of the actual tool in spindle differ with a default value(0.254mm /see the custom cycle.) Also you can manually modify the tolerance value by adding the new value after the tool rad like this CHECK_RAD(1,0.02) 1=tool rad to be checked 0.02= new tolerance/in current measuring system /in or mm G700 OR G710 Let me know if U have some difficulties

Just quoting someone: "Maybe you should contact your reseller".

You already have it in Machine Simulation, inside Mastercam. It's the "5XDMU_VMCTTBC". You just need a good post and you're ready to go.

1-On every operation page close to OK/CANCEL/APPLY/ HELP buttons will be nice to have a button for g-code, which will post the actual operation even if you’re inside the operation. 2- On every operation page close to OK/CANCEL/APPLY/ HELP buttons will be nice to have a button for Backploting and verifying the current operation (of course will result in regenerating the operation with the current parameters). After the Backploting or verifying is done the operation page will come back to screen. 3-On the right click menu from Operation Manager will be nice to have also the option for backploting or verifying, so when we can select some operation(s) in the Operation Manager then right/click and Backplot /Verify. Also an option for posting the selected operation(s) will be nice. 4-As we know, once you select some operations and start to backplot/verify them, you need to exit the verification mode so you will be able to backplot/verify another one. Will also be very helpful once you’re in backplot/verify mode to be able to change the selection of the active operation(s) which is backploted/verify by simply selecting them from the operation manager without exiting the backplot/verify mode. 5-On every operation page 2 buttons UP&DOWN for navigating to the previous/next operation (with regeneration if it’s required of course) without exiting and opening them from the Operation Manager. 6-I don’t remember in which previous version Of MCX on a Multiaxis toolpath we were able to change the strategy even after the regenerating. Right now this option is not available anymore. I ask before about this and I’ve been told that because how the new operation page is structured this availability is lost. It can be done, I’m sure of that, but maybe they should hire some good programmers to tweak Mastercam interface. 7-I really hope they will integrate further more Mastercam in Solidworks. I’m using it and I love it. It misses some functions (especially for geometry selection) but I’m sure in time they can go further.

I dont wanna simulate any lathe operations guys. Just milling. And I dont think it fall under the "don't ask for posts".

It's ok.I want to simulate some milling operations on that machine.

Someone have the the machine definition for Machine Simulation for this model (DMG GMX250)? Thanks.

..glad I could help man.