Was doing some documentation and parameter stuff today and figured I'd share. FANUC gets a bad rap for a number of reasons, many reasons are self inflicted, however that doesn't take away from the power that is available on machines with Custom MACRO B. Nearly everyone knows G10 (FANUC's key to write to tool offsets, work offsets, parameters, etc...). It's not the only way though; Another way to write/access work offsets; Common(EXT) [#_WZCMN[1]]=-10.1234 (WRITES -10.1234 TO THE COMMON WORK OFFSET FOR X) [#_WZCMN[2]]=-8.7654 (WRITES -8.7654 TO THE COMMON WORK OFFSET FOR Y) [#_WZCMN[3]]=-16.5432 (WRITES -16.5432 TO THE COMMON WORK OFFSET FOR Z) [#_WZCMN[4]]=-1.234 (WRITES -1.234 TO THE COMMON WORK OFFSET FOR THE 4TH AXIS) [#_WZCMN[5]]=54.321 (WRITES 54.321 TO THE COMMON WORK OFFSET FOR THE 5TH AXIS) G54 [#_WZG54[1]]=-10.1234 (WRITES -10.1234 TO G54 FOR X) [#_WZG54[2]]=-8.7654 (WRITES -8.7654 TO G54 FOR Y) [#_WZG54[3]]=-16.5432 (WRITES -16.5432 TO G54 FOR Z) [#_WZG54[4]]=-1.234 (WRITES -1.234 TO G54 FOR THE 4TH AXIS) [#_WZG54[5]]=54.321 (WRITES 54.321 TO G54 FOR THE 5TH AXIS) G55 [#_WZG55[1]]=-10.1234 (WRITES -10.1234 TO G55 FOR X) [#_WZG55[2]]=-8.7654 (WRITES -8.7654 TO G55 FOR Y) [#_WZG55[3]]=-16.5432 (WRITES -16.5432 TO G55 FOR Z) [#_WZG55[4]]=-1.234 (WRITES -1.234 TO G55 FOR THE 4TH AXIS) [#_WZG55[5]]=54.321 (WRITES 54.321 TO G55 FOR THE 5TH AXIS) G54.1P1 [#_WZP1[1]]=-10.1234 (WRITES -10.1234 TO G54.1 P1 FOR X) [#_WZP1[2]]=-8.7654 (WRITES -8.7654 TO G54.1 P1 FOR Y) [#_WZP1[3]]=-16.5432 (WRITES -16.5432 TO G54.1 P1 FOR Z) [#_WZP1[4]]=-1.234 (WRITES -1.234 TO G54.1 P1 FOR THE 4TH AXIS) [#_WZP1[5]]=54.321 (WRITES 54.321 TO G54.1 P1 FOR THE 5TH AXIS) Tool offset registers (Memory C by var. name – D-Comp – Param. #5004.2=1): These registers may be read from and or written to. H-GEO H-WEAR D-GEO D-WEAR T1 [#_OFSHG[1]] [#_OFSHW[1]] [#_OFSDG[1]] [#_OFSDW[1]] T2 [#_OFSHG[2]] [#_OFSHW[2]] [#_OFSDG[2]] [#_OFSDW[2]] T998 [#_OFSHG[998]] [#_OFSHW[998]] [#_OFSDG[998]] [#_OFSDW[998]] Tool offset registers (Memory C by var. name – R-Comp – Param. #5004.2=0): These registers may be read from and or written to. H-GEO H-WEAR R-GEO R-WEAR T1 [#_OFSHG[1]] [#_OFSHW[1]] [#_OFSRG[1]] [#_OFSRW[1]] T2 [#_OFSHG[2]] [#_OFSHW[2]] [#_OFSRG[2]] [#_OFSRW[2]] T998 [#_OFSHG[998]] [#_OFSHW[998]] [#_OFSRG[998]] [#_OFSRW[998]] Pretty much everything has a name. In the FANUC Series 30i-MODEL B Common to Lathe System/Machining Center System OPERATOR'S MANUAL B-64484EN_03 they can be found in the Custom Macro section. HTH

We have lathe files and mill files. 3 axis and 5 axis parts are in the same file. On a machine like that I would put it all in one file. But there are times when multiple files are easier.

This is one of those "opinion" things. There won't be 100% concensus. Myself, I've always preferred to have ONE single file when possible no matter how many machines I am running the part on. There are exceptions to that but that is my preference. HTH

The #19703-#19705 parameters are for when the top center of the pallet are not perfectly mechanically aligned with the intersections of X, Y, and Z centers of rotation respectively. So for example on a Matsuura MAM72-100H which is a horizontal 5-Axis we have an X, Y, Z, and an A, and B rotary configuration. A rotates around X, and B rotates around Y. A is the primary tilt axis and B is the secondary rotary axis. #19700 = COR X #19701 = COR Y #19702 = COR Z #19703 = NOT APPLICABLE to machines with A Axis #19704 = Distance from COR Y to the top of the pallet. #19705 = Distance from COR Z to the intersection of the imaginary centerline of the rotating pallet. These parameters HAVE to be correct. If they are wrong, you will chase part deviation until the cows come home and you may never get it. When I'm troubleshooting these issues I get a Master tool... a REAL one not some end mill stuck in a sidelock endmill adapter. The one I use is a BigKaiser BigPlus Master Tool traceable back to NIST. I use ONLY a BigPlus because I want to eliminate variables. A non dual contact tool is a variable. I don;t like variables. They add to the confusion of solving problems... but I digress. Next I measure the Master tool in the machine's tool measurement system. If it is less than 4µm, then I call it good. If it's more than that I recalibrate until it's between 0 and 4µm. I say 4µm because that's the standard accuracy of most tool measurement systems. Once that's judged to be good then I look at the flatness of the table at home. If it's off at all in the tilt or rotary axis I'll reset the 0 on those axes. If it's off more than spec in the theoretical axis I call service. If things are good so far, then I get out the granite square and test bar and check squareness, perpendicularity, etc... if after all that, things are judged to be within spec, then I start figuring out which axes are off. Like I said previously, Z is the usual culprit... at least for the majority of the error. 187.9µm sure seems like an awful lot of deviation. When the machine was new were the head and the saddle in two separate pieces then assembled onsite? Anything over 100µm throws up a red flag for me and I start checking machine geometry at that point to make sure somebody didn't miss something somewhere. The values that go into the WSEC Table will be the amount of error that is present between the perfect location, tilt, rotation, and orientation of the part/origin and the actual location(x, y, z), tilt(a), rotation(b), and orientation(c) of the part/origin in addition to the tilt (A) and rotary (B) angles at which the error(s) were measured. Using the WSEC table or not will depend entirely on the situation and type of error present. If I only have X, Y, Z, and secondary rotary error, I'll typically just use my G54/Work Offset. If I've got primary tilt axis error or theoretical rotary axis error then I will use my WSEC table. The values going into #19703-#19705 will depend on the kinematics of the machine. I'll speak only to table/table configuration machines here; A/B kinematic machines will have values in #19704 and #19705 A/C kinematic machines will have values in #19704 and #19705 B/C kinematic machines will have values in #19703 and #19705 The codes you're asking about are NOT Nigata specific functions/codes. They are FANUC functions/codes. They should be present it your yellow FANUC Manuals. #19700-#19705 information is in the Parameter Manual (30i/31i-B Series - B-64490EN_03) G43.4, G54.4, and G68.2 are in the FANUC Common to Machining Center/Lathe Operator Manual(s) (30i/31i-B Series - B-64484EN_03) HTH

I know I've been using named stuff for at least 20 years best I can recall. Whatever you OSP guys gotta tell yourselves. I thought everyone knew it... until Monday and a long time customer was getting hammered by... you guessed it, a local Okuma rep so I had to put that rook in his place. Best to remain silent than to speak and remove all doubt as my man Ben Franklin once said. That would be awesome.

From that Docs page @crazy^millman listed, I just want to highlight that we have videos that explain all the standard misc values used in our post engine https://postability.com/miscvalues

it is more a fact of the linear bearings not getting enough lube while machining small arcs. if you machine a slot only on x with toroid moves the bearings will run out of lube on the y axis very fast. because the bearings are only moving a few thou on the y axis and it is not enough t movement to get fresh lube in there. it has nothing to do with the smoothing of the tool paths. It is the size of the movements. The machine needs distance to get fresh lube in the bearings.

Glad my boss doesn't see that chart. He thinks we should get 85 % up time on the one mill we have. Good luck when we do short runs, mostly prototype, fixtures have to be designed and made and a nite guy that doesn;t show up half the time. I do all the programming, tool orders ect. And to top it off. IM RETIRING SEPT 15. i'M DONE HERE!!

Oh man. I love AE chest offs

I've had a call into the methods tech department from about 8 months ago why our new Yasda won't tap a hole. Maybe I should call them back....

Dude, I'm going to build a Post that outputs some crazy code, just to mess with people!