Ugh, 2 AM servo drive failures are the worst! When that overcurrent alarm screams in the middle of the night, you need a solid game plan. Here's my systematic troubleshooting flowchart that goes way beyond basic power checks:

1. Immediate Safety & Documentation - Lock out/tag out the system
- Document the exact error code and any fault history
- Check if this is a recurring issue or first occurrence

2. Mechanical Load Analysis - Check for mechanical binding or jamming in the driven equipment
- Verify proper lubrication on bearings and moving parts
- Inspect for worn gears, belts, or couplings
- Test if the load moves freely by hand (if safe to do so)

3. Motor & Drive Diagnostics - Check motor temperature (overheating can cause current spikes)
- Verify encoder/feedback system integrity
- Test motor insulation resistance
- Look for signs of bearing failure (noise, vibration)

4. Parameter & Tuning Review - Check if someone changed drive parameters recently
- Verify acceleration/deceleration settings aren't too aggressive
- Review current limit and overload protection settings
- Check for proper motor parameter configuration

5. Environmental Factors - Check for temperature changes (night cooling can affect components)
- Look for moisture or condensation issues
- Verify ventilation isn't blocked
- Check for vibration from nearby equipment

6. System Integration Check - Review PLC program for recent changes
- Check for timing issues in the control sequence
- Verify communication with other system components
- Look for external interference or grounding problems

7. Advanced Diagnostics - Use drive's built-in oscilloscope function (if available)
- Monitor current waveform during attempted operation
- Check for phase imbalance
- Test with reduced load or speed to isolate the issue

The key is working systematically from mechanical to electrical to control system issues. Most 2 AM overcurrent faults turn out to be mechanical binding, bearing failure, or parameter changes that someone made during the day shift. What specific symptoms are you seeing besides the overcurrent error?