Key Technical Specifications
| Parameter | Specification |
|---|---|
| Module Model | 3500/40M |
| Front Board P/N | 176449-01 |
| Rear I/O Board P/N | 125680-01 |
| Channel Count | 4 (configured in pairs: Ch 1&2 / Ch 3&4) |
| Input Type | Eddy current proximitors (-24 VDC sensor power) |
| Supported Functions | Radial vibration, axial displacement, differential expansion, eccentricity, REBAM |
| Sensitivity Options | 3.94 mV/μm or 7.87 mV/μm (vibration/displacement/eccentricity); 0.394 mV/μm or 0.787 mV/μm (diff. expansion) |
| Measurement Accuracy | ±0.33% of full scale (typical), max ±1% |
| Alarm Setpoints | 2 per channel (Alert / Danger), programmable delay |
| Operating Temperature | -30°C to +65°C |
| Humidity | 0–95% non-condensing |
| Dimensions (H×W×D) | 120.7 mm × 25.4 mm × 114.3 mm |
| Weight | Approx. 1.39 kg |
| Front Panel LEDs | OK, TX/RX, Bypass |
| Compliance | API 670, SIL 2 (TÜV certified) |
Product Introduction
I’ve chased more false trips on turbine skids than I care to count, and a surprising number of them trace back to a misconfigured or failing proximitor monitor. The Bently Nevada 3500/40M (176449-01) is the workhorse eddy-current input module in the 3500 machinery protection rack. It takes raw proximity probe signals — the -24 VDC sensor gap voltage — and turns them into actual engineering values: radial vibration, thrust position, differential expansion, eccentricity, or REBAM. Four channels, paired up. Channels 1 and 2 handle one measurement function, channels 3 and 4 handle another (or the same one). Each channel gets two setpoints — Alert and Danger — with programmable delay timers.The reason this module shows up on so many critical machines — gas turbines, steam turbines, compressors, large motors — is that it does one job and does it well. The SIL 2 certification means it can sit in a safety instrumented function without requiring external voting logic for basic protection. The API 670 compliance gives you the documentation trail that plant insurance auditors and classification societies want to see. One thing I’ll flag: the 176449-01 front board mates with the 125680-01 rear I/O board. If you’re sourcing a replacement, make sure you’re getting the matched pair or verify that your existing rear board is compatible. Mismatched front/rear boards are a headache I wouldn’t wish on anyone.
Quality SOP & Tech Pitfalls
The Lab Report (Pre-Shipment Protocol)
Here’s what a properly serviced 3500/40M should go through before it ships:
- Visual inspection: Check the 176449-01 front board and 125680-01 rear I/O board for corrosion, lifted pads, or rework marks under magnification. Verify part numbers and revision markings match.
- Live rack test: Install in a 3500/05 frame with proper 3500/15 power supply. Confirm the module is recognized by the 3500 Rack Configuration Software, OK LED is steady, no fault flags.
- Channel signal injection: Feed a calibrated gap voltage into each proximitors input. Verify the module reads the correct displacement value within the ±0.33% accuracy spec.
- Alarm setpoint verification: Trigger each Alert and Danger setpoint on every channel. Confirm relay association and timing delays respond correctly.
- Insulation resistance: Megger check between sensor inputs and chassis ground to confirm isolation integrity.
- ESD-safe packaging: Sealed in anti-static bag with foam support for the connector pins.
The Engineer’s Warning (Pitfalls That Cause Downtime)
- Swapping front boards without checking the rear I/O board. The 176449-01 is the front monitor board. The 125680-01 is the rear I/O board that handles the actual terminal connections and signal conditioning. They’re a matched set. I’ve seen a guy grab a “3500/40M” off a surplus shelf, plug it into his rack, and wonder why channels 3 and 4 read garbage. His old rear board was a different revision. Always verify both part numbers.
- Forgetting to photograph the configuration before pulling the module. The 3500/40M stores its config in non-volatile memory, but if you’re replacing it and the new module comes blank, you’ll need to reload from your .rak file. If you don’t have a backup, you’re rebuilding channel assignments, sensitivity settings, alarm setpoints, and delay timers from scratch. Take a screenshot of every channel’s configuration before you touch that release latch.
- Ignoring the paired channel constraint. Channels 1 and 2 must perform the same function. Channels 3 and 4 must perform the same function. You can’t put radial vibration on Ch 1 and thrust position on Ch 2. I’ve watched an engineer spend two hours fighting a configuration error because he tried to split a pair.
Installation & Configuration Guide
Phase 1: Pre-Installation
- ⚠️ Confirm machine protection status. If this module is part of an active trip circuit, coordinate with operations before removal. Pulling a live protection module without a redundant backup in place can leave the machine unprotected.
- ⚠️ Upload the current rack configuration (.rak file) from the 3500/22M TDI module using the Rack Configuration Software. Save it. Back it up to two locations.
- Photograph the module’s position in the rack, the rear I/O board wiring, and the front panel LED states.
Phase 2: Removal
- Disconnect the rear I/O board (125680-01) wiring — label every cable with its terminal designation.
- Release the front module (176449-01) from the rear I/O board by disengaging the board-to-board connector.
- Slide the front module out of the rack slot. The 3500 system supports hot-swap on powered frames, but I still recommend pulling it during a planned window if the machine protection logic depends on it.
Phase 3: Installation
- Verify the replacement front board is 176449-01 and the rear I/O board is 125680-01 (or confirm compatibility of your existing rear board revision).
- Slide the new front module into the rack slot and seat it firmly onto the rear I/O board connector.
- Reconnect all rear I/O wiring per your labeled diagram.
- Confirm the OK LED illuminates steady green.
Phase 4: Power-On & Configuration
- Connect to the 3500/22M TDI module via RS-232 or RS-422.
- Open the Rack Configuration Software and verify the module is recognized in the correct slot.
- Download your saved .rak configuration file to the rack.
- Verify each channel reads correct gap voltage and engineering units.
- Test alarm setpoints by injecting a simulated signal above Alert and Danger thresholds.
- Confirm relay outputs trip as expected per your relay association configuration.
Compatible Replacement Models
| Model | Compatibility Tier | Notes |
|---|---|---|
| 3500/40M 176449-01 (same P/N) | ✅ Drop-in Replacement | Direct match. Verify rear I/O board P/N 125680-01 compatibility. |
| 3500/40M 176449-02 | ⚠️ Software Compatible | Same 3500/40M platform but different I/O board variant (128229-01 rear). Different terminal configuration — verify wiring matches your application before substituting. |
| 3500/40_SIL-01-00 | ⚠️ Software Compatible | SIL-certified variant. Same core functionality but may require updated Rack Configuration Software version and SIL validation documentation. |
| 3500/42M (any variant) | ❌ Hardware Mod Required | Different module type (vibration/displacement/acceleration with different input types). Not a direct substitute. Requires rewiring and full reconfiguration. |
Frequently Asked Questions (FAQ)
Can I hot-swap this module without shutting down the rack?
The 3500 system is designed to support hot-swap of monitor modules in a powered frame. That said, “designed to” and “safe to” aren’t always the same thing. If this module is the sole protection for a critical trip function on a running machine, I’d argue for a planned shutdown window. Redundant configurations give you more breathing room, but verify your redundancy is actually live before you trust it.My rack shows the module but channels read zero. What’s wrong?
Nine times out of ten, it’s one of three things: the proximitors aren’t getting -24 VDC sensor power (check the rear I/O board connections), the sensitivity setting in the configuration doesn’t match your probe (3.94 vs. 7.87 mV/μm), or the rear I/O board revision doesn’t match the front board. Start with the sensor power.Can I use a 3500/42M instead of the 3500/40M?
No. The 3500/42M handles different signal types and has a different I/O board configuration. The rear terminal boards are not interchangeable. If you’re migrating from a 3500/40M to a 3500/42M, expect a full rewiring and reconfiguration effort.What software do I need to configure this module?
The Bently Nevada 3500 Rack Configuration Software. It communicates with the 3500/22M TDI module via RS-232 or RS-422 at up to 38.4K baud. The configuration file uses a .rak extension. Make sure your software version supports the firmware revision on your module.Is this module still supported by Baker Hughes?
The 3500 platform remains a widely installed base globally, but specific module revisions do reach end-of-life. I’d recommend contacting an authorized Baker Hughes / Bently Nevada distributor with your exact part number and revision to confirm current support status, spare parts availability, and any firmware migration recommendations before committing to a long-term installation.What does the Bypass LED mean?
If the Bypass LED is lit, the module has been placed in bypass mode — meaning its alarm and trip outputs are being overridden, typically during maintenance or testing. If you see this LED on during normal operation and nobody on your team put it there, something went wrong. Check your configuration software immediately.
