Description
Core Product Summary
The MOOG D138-002-012 is a D138-002-series run-time license key intended for Moog motion controllers in the M3000 automation system, including MSC I, MSC II and MSD controllers. It is a physical license component that installs in the controller’s designated “LK” license-key slot.
Moog documentation states that an MSC I, MSC II or MSD motion controller requires a license key to run and that the controller modules do not operate without a properly connected license key. For procurement and spare-parts control, the exact D138-002-012 suffix should be matched to the controller configuration and original bill of materials, because different D138-002 suffixes identify different license variants.
Key Technical Specifications
| Item | Verified Information |
|---|---|
| Manufacturer | MOOG |
| Order number | D138-002-012 |
| Product family | D138-002 license-key series |
| Product type | Run-time license key |
| Compatible controller platforms | MSC I, MSC II and MSD motion controllers |
| Associated automation system | M3000 automation system |
| Installation location | License-key slot marked “LK” on the controller |
| Operating requirement | The controller requires a properly connected license key to run |
Detailed Product Overview
The MOOG D138-002-012 belongs to Moog’s D138-002 license-key series, used with MSC I, MSC II and MSD motion controllers in the M3000 automation system. In this architecture, the license key is a required hardware entitlement: Moog’s controller documentation identifies a license key as necessary for operation and specifies installation in the controller’s “LK” license-key slot.
For an engineer or procurement team, the important distinction is between the controller hardware and its license key. The MSC or MSD controller provides the processing, I/O, communication, and motion-control functions, while the D138-002 key authorizes operation of that controller. A controller without a properly connected license key will not run, so this component is a critical configuration item rather than an optional accessory.
The “-012” suffix identifies a specific variant within the D138-002 license-key series. Because Moog’s documented license-key range includes multiple suffixes with different feature scopes, the exact suffix should be verified against the controller nameplate, system documentation, or original bill of materials before substitution. Physical similarity alone does not establish that one D138-002 variant can replace another.
Integration is straightforward in architectural terms: the key is fitted to the designated license-key slot on a compatible MSC I, MSC II, or MSD controller. The surrounding system uses the MACS development environment for application programming and configuration. When handling the key, standard electrostatic-discharge precautions and careful connector handling are appropriate for electronic control equipment.
System Compatibility & Integration Requirements
| Item / Dependency | Verified Compatibility or Requirement | Practical Note |
|---|---|---|
| Controller platforms | MSC I, MSC II and MSD motion controllers | Confirm that the installed controller is one of these M3000-family platforms before ordering. |
| Automation system | M3000 automation system | The license key belongs to the M3000 controller architecture. |
| Installation point | Controller license-key slot marked “LK” | The key must be properly connected for the controller to operate. |
| Software environment | MACS development environment | Controller applications are developed and configured through MACS. |

D138-002-012

D138-002-012
Engineering Selection Highlights
- The D138-002 numbering places this part in Moog’s license-key family for MSC I, MSC II and MSD motion controllers, so it should be treated as a controller entitlement component rather than a standalone I/O or communication module.
- Moog documentation requires a license key for operation of MSC I, MSC II and MSD controllers; a missing or incorrect key can prevent the controller from running.
- The key installs in the dedicated “LK” slot, making physical fit and correct orientation important during replacement or spare-part installation.
- The exact “-012” suffix should be checked against the controller’s original configuration, since the D138-002 series includes multiple license variants with different feature scopes.
- The M3000/MSC-R platform uses the MACS development environment, so license selection should be considered together with the application software and controller configuration.
Applications & System Role
Within an M3000 automation architecture, the MOOG D138-002-012 serves as the run-time entitlement for a compatible Moog MSC I, MSC II or MSD motion controller. It does not replace the controller, provide field I/O, or act as a network interface; its role is to enable the licensed controller to operate.
This makes the part relevant when commissioning, rebuilding, or maintaining an M3000-based motion-control cabinet. Before installation, the controller model, existing license suffix, and machine documentation should be checked so that the replacement key matches the originally specified configuration.
FAQ
What is the MOOG -012?
It is a D138-002-series run-time license key for Moog MSC I, MSC II and MSD motion controllers in the M3000 automation system.
Which controllers use this license key?
The D138-002 license-key family is documented for MSC I, MSC II and MSD motion controllers.
Where is the MOOG D138-002-012 installed?
It is installed in the license-key slot marked “LK” on the compatible Moog controller.
Is the license key required for controller operation?
Yes. Moog documentation states that MSC I, MSC II and MSD controllers require a license key and do not work without a properly connected key.
Does D138-002-012 provide I/O or fieldbus connections?
No. It is a license key, not an I/O module, communication module, or standalone controller.
Why is the exact “-012” suffix important?
The D138-002 series includes different license variants, so the suffix should match the controller’s original configuration and documentation.
Which software environment is associated with the M3000 controller system?
The M3000/MSC controller platform uses the MACS development environment for application programming and configuration.




Start Chat