Description
Key Technical Specifications
• Digital Inputs: 16 channels (for external status/alarms)
• Digital Outputs: 16 channels (for external control/annunciation)
• Ethernet Protocol: Modbus/TCP over 10/100 Base-TX
• Serial Protocol: Modbus RTU over RS232/RS422/RS485
• Max Data Rate: 115.2 kbps (Serial)
• Supported Protocols: Modicon Modbus, Bently Nevada proprietary
• Power Requirement: 12-48 VDC (Typical rack power)
• Operating Temp: -20°C to +50°C
• Storage Temp: -40°C to +70°C
• Humidity: 5% to 95% (Non-condensing)
• Mounting: DIN Rail or 3500 Rack Backplane
Product Introduction
Machinery protection data is useless if it stays trapped inside the Bently rack. The Bently 136188-02 serves as the critical translation layer between the 3500 monitoring system and your plant’s DCS or SCADA network. By supporting both Modbus TCP and RTU, it allows operators to see vibration alarms, trip states, and bypass statuses directly on their main control screens without needing a separate workstation.
Why spec this exact module? It packs 16 digital inputs and 16 digital outputs into a single gateway footprint. This means you can hardwire critical external safety interlocks directly into the 3500 system while simultaneously pushing rack health data up to the enterprise network. Honestly, at 115.2 kbps serial speeds, it’s not built for high-speed waveform streaming, but it is perfectly tuned for reliable, deterministic alarm and status polling. Bottom line—this is the bridge that keeps your machinery data visible to the rest of the plant.
Troubleshooting Quick Reference
• Modbus TCP Comm Loss | Cause: IP conflict, subnet mask error, or bad RJ45 | Relevancy: 90% | Quick Check: Ping the module; verify LED link status | Fix: Check IP config in 3500 Configuration software; swap CAT6 cable
• Digital Outputs Not Firing | Cause: Relay logic mismatch or missing rack power | Relevancy: 85% | Quick Check: Measure 24VDC at DO terminal block | Fix: Verify AND/OR logic programming in 3500 Config
• Serial RTU Timeout | Cause: Baud rate mismatch or missing termination | Relevancy: 80% | Quick Check: Check RS485 A/B wiring and end-resistor | Fix: Verify 9600/19200 baud; ensure only one termination resistor is active
• 16 DI Reading All Zeros | Cause: Common ground missing or dry contact failure | Relevancy: 75% | Quick Check: Measure voltage across DI common and active terminal | Fix: Check external 24VDC supply and field wiring continuity
• Module Won’t Boot / No LEDs | Cause: Backplane seating issue or overvoltage | Relevancy: 70% | Quick Check: Measure backplane supply at module pins | Fix: Reseat module firmly; verify 12-48VDC is within spec
Application Scenarios & Pain Points
• Refinery Compressor Stations: High EMI from massive VFDs corrupts standard serial comms. The built-in Ethernet Modbus TCP on the 136188-02 bypasses the noise floor, ensuring DCS operators never miss a critical vibration trip.
• Power Plant Steam Turbines: Complex trip logic requires external relay integration. The 16 DI/16 DO channels allow the 3500 rack to ingest ESD signals and output master alarm annunciations without adding a separate safety PLC.
• Chemical Processing Plants: Legacy DCS systems only support older serial protocols. The dual-protocol nature of this gateway lets engineers use RS485 for the old control room while migrating new HMIs to Ethernet TCP simultaneously.
BENTLY 136188-02
Compatible Replacement Models
• ✅ Drop-in Replacement: Bently 136188-02 (Exact Match). Same footprint, same 16DI/16DO I/O count, same Modbus map. Surplus pricing varies wildly (1,500 to 15,000+) depending on vendor stock and warranty.
• ⚠️ Software Compatible: Bently 136180-01 (Standard 3500/92). Same gateway family, but verify the exact I/O channel count and serial port configuration. Plan 2-4 hours to re-download the rack configuration and verify Modbus register maps.
• ❌ Hardware Incompatible: Bently 3500/22M (TDI Module). Do not attempt. The 3500/22M is the transient data interface for System 1 software, NOT a Modbus I/O gateway. Swapping these will completely break your DCS integration and requires a full rack reconfiguration.
