Michael Wang

Founder & Mechanical Engineer

As the founder of the company and a mechanical engineer, he has extensive experience in advanced manufacturing technologies, including CNC machining, 3D printing, urethane casting, rapid tooling, injection molding, metal casting, sheet metal, and extrusion.

Table Of Contents

Explore CNC Programming & Process Engineering Guides

A coordinate that was harmless in one block can describe a completely different move after the positioning mode changes. G90 vs G91 is therefore a state tracking problem, not just a vocabulary question. In the Haas mill convention used for the examples here, G90 selects absolute positioning and G91 selects incremental positioning. The meaning must still be checked against the actual controller and machine type.

The examples below are coordinate arithmetic, not machine ready programs. They omit tooling, feeds, offsets, clearance and machine configuration. The useful habit is to read every position together with the active modes and reference system, then verify transitions and returns before motion is authorized.

What changes in G90 vs G91 positioning?

G90 references a position; G91 specifies a displacement.

On the referenced Haas mill, absolute coordinates use the active reference system, while incremental coordinates describe movement from the current position; other active modes still affect interpretation.

In absolute positioning, repeated X20 normally requests the same X location in the active coordinate system. In incremental positioning, repeated X20 requests another 20 units of X displacement each time. Haas’s G90 and G91 mill reference documents this distinction for that control family.

The reference system remains important. A work offset locates the workpiece relative to machine coordinates, while tool compensation and other transformations can influence the motion. Switching to absolute mode does not cancel all offsets or establish a safe clearance. Review the mill programming manual alongside the setup definition. A reviewer needs the machine type, active units and relevant offsets before deciding whether a coordinate describes the intended physical location.

Maintain a distinction between machine position and work coordinates in every example. The same displayed value can refer to different references, making an unqualified coordinate note difficult to review.

Mixing modes within a program

Mixing modes can be useful when a repeated displacement is easier to express incrementally and a later destination is clearer as an absolute coordinate. The risk lies in leaving a modal state active beyond the block where the programmer expected it. A following line may contain only an axis value, relying entirely on earlier state.

Mark each transition deliberately and review the first motion after it. Ask what reference that motion uses, what position the machine is assumed to occupy and whether the preceding operation can end somewhere else. An optional block, restart point or conditional branch can invalidate an assumption that was true during a simple linear reading.

Haas’s mill G code listing groups the control’s functions, but the presence of a code does not prove its behavior on another machine. Use explicit state establishment at appropriate boundaries according to the approved programming practice. Do not add a generic safety line from an unrelated controller; resetting modes without understanding the current cycle can create a different error.

Review optional paths rather than only the normal sequence. A mode established in a skipped block may never become active before a later coordinate depends on that expected state.

g90 vs g91G90 Vs G9101Coordinate modes and activeoffsets02Mixing modes within aprogram03Subprogram return positions04Review a safe verificationsequenceCheck these interfaces against the actual material, geometry and acceptance.
Related engineering checks for g90 vs g91; the worked example and drawing requirements define the actual scope.

Subprogram return positions

A subprogram may enter with modal conditions inherited from its caller and return with conditions changed by its own blocks. Unless the controller documents otherwise, do not assume the call behaves like an isolated software function that automatically restores every state. The return location and return mode need separate review.

For a repeated pattern, decide whether the subprogram expects an absolute anchor or a current position from which it makes incremental moves. Then define its exit condition: final physical position, positioning mode, active cycle and relevant compensation. A caller that assumes a different exit condition can move incorrectly even when the subprogram’s individual geometry is correct.

Check restart behavior as well. Restarting inside a subprogram can bypass the block that establishes its expected mode or offset. Haas’s mill M code documentation is useful for the control’s call and return functions, but verify the complete manual for the actual implementation. Record entry and exit contracts in the program documentation, and prove them in the approved verification environment.

A useful subprogram record includes both its expected starting position and net displacement. This exposes accumulation when a repeated call is made from a different anchor or restart point.

Blue machined plate with mounting holes and a rectangular opening
Holes, edges and mounting faces on a component can carry different functional requirements.

Review a safe verification sequence

Begin verification by identifying the specific control, machine configuration, units, offsets and program revision. Then trace the program without assuming that a familiar code has a familiar meaning. A lathe may use codes differently from a mill; Haas’s lathe programming manual demonstrates why machine type belongs in the review.

Check the transition blocks and every point at which a cycle, subprogram, optional stop or restart can change the expected state. List the intended location before and after each critical movement. This makes a hidden incremental accumulation easier to detect than reading a long series of axis values alone.

Physical prove out must follow the machine owner’s approved procedures and the manufacturer’s mill safety instructions. Simulation, graphics and a reduced speed are aids, not a universal clearance guarantee. Never infer from a simple coordinate table that a tool, holder or fixture can safely follow the same path. The complete setup and all relevant axis behavior must be included in the verification.

Verify whether the control graphics includes the specific transformation or cycle being used. A display that omits an option cannot establish the resulting physical motion for that option alone.

Units and controller compatibility checklist

Use a compact state table before reviewing coordinates. It should identify both the state that is deliberately established and the state that remains inherited. This is particularly valuable when a program is moved between machines or generated by a new postprocessor.

Item Question to resolve Typical failure to detect
Machine and control Which manual and configuration apply? Familiar code has different behavior
Units and feed What units and feed mode are active? Correct value interpreted in the wrong units
Reference system Which work offset and transformations apply? Absolute location uses an unexpected origin
Positioning mode Absolute or incremental at this block? Repeated values accumulate unexpectedly
Restart condition What setup blocks have actually executed? Necessary state establishment is skipped

For milled component planning, keep these machine process details separate from the part’s geometry. The drawing defines what must be produced; the approved setup defines how a particular machine interprets its program.

Keep the approved offset values and their measurement basis with the setup. Program text cannot reveal whether a manually entered work offset corresponds to the intended fixture location correctly.

Worked calculation or annotated toolpath example

Assume a hypothetical one dimensional review in millimeters, with no offsets changing during the example. The current work coordinate is X10. An absolute request for X30 describes a destination 20 mm farther in the positive X direction. Repeating the same absolute request leaves the intended destination at X30.

Starting again at X10, an incremental request of X20 also ends at X30. Repeating that incremental request ends at X50. The difference is 30 – 10 = 20 for the first move, then 30 + 20 = 50 for the second. Identical numerical destinations and displacements are therefore not interchangeable descriptions.

Now imagine a subprogram intended to make one X20 incremental step but called twice. Its net displacement is 40 mm unless another block changes the position. This arithmetic says nothing about clearances or executable syntax. Write the intended entry and exit coordinates beside each call, then compare them with the actual controller’s behavior before approving a machining program.

A two-axis extension of the example should track each axis independently. Matching the final X coordinate does not prove that a different Y displacement or intervening path is correct.

Simulation and first-part verification checks

A simulation should use the released postprocessed program where practical, rather than only a nominal CAM path that may not reflect the controller’s state changes. Include stock, fixture, tool and holder geometry. Check whether the simulator reproduces the relevant work offsets, subprograms and control options.

The first part measurement should then test the feature relationships that could reveal a positioning error. A pattern shifted as a group suggests a different issue from repeated spacing errors that grow across a pattern. Record datum relationships, not merely isolated diameters. Coordinate these measurements through the dimensional inspection requirements.

For multi-axis work, additional transformations and rotary behavior can make a simple absolute or incremental label insufficient. A multi-axis setup review should identify the complete reference chain and supported machine options. If the observed result differs from the predicted coordinates, investigate the state history and postprocessor assumptions before adjusting a work offset to hide the discrepancy.

When a pattern is checked, retain feature identifiers and datum alignment with the results. This distinguishes a true spacing error from a measurement setup that used a different origin.

Coordinate-measuring probe above a round component held on a fixture
Inspection must address the actual feature and datum relationship defined for acceptance.

Process documentation and handoff notes

The program handoff needs the controller version or applicable manual reference, machine type, postprocessor identity and released program revision. Include the expected work coordinate system, tool data and verification record. A list of G codes without these conditions is not enough to reproduce the operation.

Document subprogram entry and exit states in a form the next reviewer can inspect. Identify where positioning modes change and what assumptions apply at restart points. If an edit changes a mode transition, review the downstream blocks rather than checking only the edited line. Modal behavior can carry the effect far beyond the visible change.

Preserve the relationship between the machining program and the drawing revision. A coordinate update made for a revised hole pattern may require a new first part check even if its positioning modes remain unchanged. Keep numeric examples used for training separate from production files, so a helpful illustration cannot be mistaken for a released, machine verified sequence.

Changes made during prove out should return to the controlled program source. An undocumented edit at the machine can otherwise leave the next setup using an obsolete coordinate assumption.

FAQ

Does G90 always mean absolute positioning?

No universal interpretation should be assumed across all machine types and controls. On the Haas mill reference used here, it selects absolute positioning, but a code with the same number can have a different meaning on another system or machine type. Confirm the actual controller manual and configuration before editing a program. Include the machine type in any shared example, especially when transferring knowledge between milling and turning, rather than treating a code number as self explanatory.

Can a work offset change the meaning of an absolute coordinate?

An absolute coordinate is interpreted within the active reference system, so a different work offset can place the same programmed coordinate at a different physical machine location. Absolute does not necessarily mean machine zero. Check work offsets, tool compensation and any active transformations together with the positioning mode. A correct coordinate in an unexpected reference system can still produce the wrong motion. The setup sheet and verification environment need to represent the intended reference chain.

Is incremental positioning less accurate?

The mode itself does not establish the finished part accuracy. Both descriptions can represent the same intended path, while control resolution, machine behavior, offsets, setup and measurement affect the result. Incremental programming can make a repeated displacement convenient, but it also makes accumulated state important to review. Absolute programming can simplify destination checking, yet remains dependent on the active reference system. Choose the description that supports a clear, verified process rather than assigning accuracy from the mode name alone.

Conclusion

The useful distinction is destination versus displacement within a defined controller state. Read G90 and G91 together with units, work offsets, compensation and program flow. Then trace the entry and exit conditions of repeated blocks and subprograms so an inherited mode cannot turn a familiar coordinate into an unintended move.

Keep arithmetic demonstrations separate from machine ready instructions. Simulation and first part evidence must represent the actual program, setup and control behavior, including restart conditions. For a new machined part, send the drawing, material and critical feature relationships for quotation. Define the finished geometry clearly; controller specific programming and prove out should then be developed and verified as part of the manufacturing process.

{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “Does G90 always mean absolute positioning?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “No universal interpretation should be assumed across all machine types and controls. On the Haas mill reference used here, it selects absolute positioning, but a code with the same number can have a different meaning on another system or machine type. Confirm the actual controller manual and configuration before editing a program. Include the machine type in any shared example, especially when transferring knowledge between milling and turning, rather than treating a code number as self explanatory.”}}, {“@type”: “Question”, “name”: “Can a work offset change the meaning of an absolute coordinate?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “An absolute coordinate is interpreted within the active reference system, so a different work offset can place the same programmed coordinate at a different physical machine location. Absolute does not necessarily mean machine zero. Check work offsets, tool compensation and any active transformations together with the positioning mode. A correct coordinate in an unexpected reference system can still produce the wrong motion. The setup sheet and verification environment need to represent the intended reference chain.”}}, {“@type”: “Question”, “name”: “Is incremental positioning less accurate?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “The mode itself does not establish the finished part accuracy. Both descriptions can represent the same intended path, while control resolution, machine behavior, offsets, setup and measurement affect the result. Incremental programming can make a repeated displacement convenient, but it also makes accumulated state important to review. Absolute programming can simplify destination checking, yet remains dependent on the active reference system. Choose the description that supports a clear, verified process rather than assigning accuracy from the mode name alone.”}}]}