Key Technical Specifications

• Product Model: D138-002-002
• Manufacturer: MOOG
• Physical Color: Green
• Assigned Function: Motion Control
• Communication Protocols: IP Address, PROFIBUS-DP Station Address, CANopen Node ID
• Software Integration: MATLAB/SIMULINK integration, Transfer functions
• Trajectory Generation: Built-in motion trajectory library
• Visualization: Web-based HMI components
• Hardware Format: Plug-in License Key Module
• Associated Modules: D136-002-005, D138-002-001 (Control), D138-002-003 (System)

 

Product Introduction

You don’t plug a license key into a servo controller because you want to; you do it because the machine is sitting dead and the OEM says your software needs a specific token to run. The MOOG D138-002-002 is exactly that token. It is a hardware license module for the MSC I platform that dictates what your controller can actually do. This specific green-coded module unlocks motion control libraries, MATLAB/SIMULINK integration, and communication stacks like PROFIBUS-DP or CANopen. Without it, your expensive controller is just a very expensive paperweight.Engineers usually only care about this part when the original gets lost during a panel rebuild or the controller fails. It assigns critical network parameters like IP addresses and node IDs directly at the hardware level. I’ve seen guys spend three days troubleshooting a PROFIBUS network only to realize the new controller didn’t have the right license key installed. It is a simple piece of hardware, but it holds the digital DNA of your motion system. Just make sure you grab the green one; the gray is for basic control, and red/blue are for system functions.

Quality SOP & Tech Pitfalls

We don’t just throw these in a bag and ship them. First, we do a visual and counterfeit check under magnification to ensure the PCB and connectors are genuine MOOG. Then, we plug it into a live MSC I test rack to verify the controller actually reads the license and unlocks the motion libraries. We use a Fluke 115 to check for shorts and verify the physical pins aren’t bent or corroded. Finally, we log the specific firmware or hardware revision and seal it in anti-static packaging.Here is the brutal reality: if you lose this key, your machine stops. I once watched a plant manager sweat through his shirt because he threw away the original D138-002-002 during a cabinet upgrade, assuming the software license was all that mattered. He was wrong. The hardware key was required to push the IP address and CANopen node ID to the new controller. Also, watch out for ESD. These modules have exposed pins. If you grab it without a wrist strap on a dry winter day, you might fry the internal EEPROM, and it will look perfectly fine until you try to boot the system.

 

Installation & Configuration Guide

1. Pre-Installation: ⚠️ KILL THE POWER. Wait at least 5 minutes for the MSC I controller capacitors to discharge. Take a high-resolution photo of the existing key and its exact slot position.
2. Removal: Label the slot. Gently pull the old module straight out. Do not wiggle it side-to-side, or you will bend the backplane pins.
3. Installation: VERIFY THE COLOR. Ensure the new module is GREEN. Align the pins perfectly and push straight in until it seats flush. Forcing it will destroy the backplane connector.
4. Power-On & Testing: Restore 24V DC power. Watch the controller boot sequence. Open your MOOG configuration software and verify that the Motion Control libraries and PROFIBUS/CANopen parameters are now active and match your old settings.

Compatible Replacement Models

• ✅ D138-002-002: Exact drop-in replacement. Must be the GREEN version for Motion functions.
• ⚠️ D138-002-001: Gray version. Hardware fits, but only unlocks basic Control functions. Will NOT work for Motion or MATLAB integration.
• ❌ D138-002-003: Blue/Red version. Unlocks System functions. Not a direct replacement for motion control tasks.

 

Frequently Asked Questions (FAQ)

Can I just use a software license file instead of this physical key?
No. The MSC I platform relies on this physical hardware module to assign network parameters like IP addresses and PROFIBUS station addresses at boot time. A software file cannot do this.Will the gray D138-002-001 work as a cheaper alternative?
Absolutely not. The gray module is strictly for basic control. If your application requires motion trajectories, MATLAB integration, or specific bus communication, the controller will throw a fault and refuse to run the motion program.Is it safe to hot-swap this module while the controller is powered on?
I wouldn’t risk it. While some industrial keys are hot-swappable, the MSC I reads this module during the initial boot handshake. Pulling it while running can cause a bus fault or corrupt the controller’s volatile memory. Just power it down.What happens if I lose this key and can’t find a replacement?
You are in trouble. Without this key, the controller defaults to a crippled state. You will need to contact MOOG directly with your controller’s serial number to get a new key programmed, which can take weeks. Always keep a spare on the shelf.Does this key store my actual motion program logic?
No. It only stores the license entitlement and network configuration parameters. Your actual motion program and trajectory data live in the controller’s main CPU memory or flash. If you swap the key, your program should still be there, but you need the key to execute it.How do I know if my controller needs this specific green key?
Check the BOM (Bill of Materials) for your MSC I controller, or look at the physical key currently installed. If it says “Motion” or is green, you need the D138-002-002. If you are unsure, check the MOOG MSC I hardware manual for your specific frame size.