Description
Product Core Brief
- Model: 133323‑01
- Brand: BENTLY
- Series: 3500 Machinery Protection System (3500/92)
- Core Function: Acts as primary external communications gateway for the 3500 rack. Exposes vibration, position, speed, alarm and status data via Ethernet and multi‑port serial interfaces to DCS, PLC and host monitoring systems.
- Product Type: Communication Gateway Module
- Key Specs: 10BASE‑T Ethernet, RS232 / RS422 / RS485 serial ports | Modbus TCP / Modbus RTU | Full‑height rack slot
Note: OEM discontinued; available as new surplus and field‑tested used stock.
BENTLY 133323‑01
Key Technical Specifications
- Interfaces: 1×RJ45 Ethernet (10BASE‑T); 1×RS232 DB9; 2×isolated RS422/RS485 DB9 ports
- Supported Protocols: Modbus TCP, Modbus RTU, Bently‑host configuration protocol
- Backplane Power Draw: 210 mA @ +24 VDC (~5 W total power)
- Form Factor: Full‑height slot for 3500‑series rack
- Port Isolation: Galvanic isolation on all external communication ports
- Operating Temperature: ‑30 °C to +65 °C
- Storage Temperature: ‑40 °C to +85 °C
- Weight: 0.44 kg
- Dimensions: 241 mm × 99 mm × 24 mm
- Humidity: 5‑95 % non‑condensing
- Agency Approvals: CSA‑NRTL/C
Product Introduction
This gateway module serves as the main data export point for a 3500 rack. It collects measurement values, alert/danger status, and module health information across the rack backplane, then serves that data to external automation hosts over Ethernet or serial Modbus links.
Dual isolated RS485 ports allow redundant serial bus connections. The Ethernet port supports both Modbus TCP and direct connection for 3500 rack configuration software. It removes the need for separate external protocol converters for most turbine‑compressor plant‑system integration tasks.
QA & Testing SOP
- Incoming Inspection: Match part number and serial number against OEM documentation. Inspect DB9 and RJ45 connectors for pin damage, inspect PCB for burn marks and counterfeit marking inconsistencies. Log serial numbers for traceability.
- Live Testing: Seat inside genuine 3500 rack, apply rated backplane power. Verify OK LED status. Establish configuration‑tool connection, validate Ethernet and serial Modbus read‑back of rack measurements and alarm states for continuous 24‑hour run.
- Electrical Testing: Use Fluke 115 and insulation tester. Verify >10 MΩ isolation between communication ports and chassis ground. Confirm chassis‑to‑rack‑earth continuity.
- Firmware/Config Backup: Record exact firmware revision loaded on the unit. Capture screenshots of Modbus map, IP address and serial‑port parameters before reset. Photograph front‑panel LED layout for reference records.
- Final QC & Packaging: Place unit inside anti‑static shielding bag. Apply printed QC pass tag with test‑date stamp. Pack with shock‑absorbent foam for transit.
BENTLY 133323‑01
Installation Pitfalls & Guide
❗ Firmware Rev Mismatch: Mismatched rack and gateway firmware can create missing Modbus registers, timeouts or unresponsive ports. Match firmware revisions before commissioning.❗ Slot Location Error: This hardware requires a full‑height rack slot. Partial seating breaks backplane communication. Photograph old hardware layout prior to removal.❗ Wiring Incompatibilities: RS485 bus termination rules differ from ordinary instrument wiring. Missing or duplicate bus termination causes intermittent Modbus read errors. Cross‑reference OEM datasheet before field termination.❗ Power Draw Changes: Adding this unit increases total rack backplane load. Calculate aggregate slot‑by‑slot current consumption to avoid overloading rack power supplies.❗ ESD Dangers: Unprotected handling can damage isolated communication transceivers. Field cases show ESD‑damaged spare units valued over $2000 before power‑on. Always use grounded ESD wrist straps.
4‑step replacement guide1. Pre‑install: De‑energize rack power, don ESD wrist strap, validate firmware compatibility. Document IP address, Modbus mapping and serial‑port settings from existing unit.2. Removal: Release front‑panel latch, slide out old unit, document all external communication cable assignments.3. Install: Slide replacement firmly into full‑height slot until latch fully engages. Re‑connect Ethernet and serial cabling per datasheet pinout.4. Power‑on Test: Restore rack power, confirm OK LED status. Re‑apply network and Modbus configuration. Validate data read‑back over both Ethernet and serial links.
FAQ
Q: Does this unit support hot‑swap operation?A: No. It draws power directly from the main system backplane. Live removal creates voltage transients that can corrupt adjacent monitoring cards or damage backplane traces. Full rack power shutdown is mandatory.
Q: Can both RS485 ports run independent Modbus RTU buses?A: Yes. Each isolated RS485 port can serve separate Modbus RTU masters. Correct bus termination is required on each physical segment.
Q: What happens when gateway configuration is lost after power‑cycle?A: IP address, serial‑port parameters and Modbus mapping store in volatile memory. Power loss erases custom settings. Reload gateway configuration after power restoration.
Q: Is brand‑new factory stock available?A: Original OEM manufacturing has ceased. Available stock comes from new‑surplus or field‑tested used inventory. Lead‑times shift with lot availability.
Q: What warranty applies to surplus stock?A: Third‑party inventory carries limited‑time functional warranty covering hardware defects. It excludes damage caused by site‑side surge events, mis‑wiring, or incorrect configuration. OEM factory warranty is no longer offered.
Q: Can this gateway affect SIL‑rated rack safety functions?A: This is a data‑acquisition gateway only. It does not participate in trip‑logic voting. Safety‑critical alarm and trip decisions execute locally on monitor and relay modules. Complete safety‑system assessment remains required.
Q: Can newer‑generation gateway cards serve as drop‑in replacements?A: Physical form factor matches, but register mapping, firmware feature sets and protocol handling differ. Direct drop‑in swap is not feasible; re‑validate Modbus register tables and host‑system scaling after replacement.
