Key Technical Specifications
| Parameter | Value |
|---|---|
| Product Type | Remote I/O Module (RBUS) |
| Analog Input Channels | 32 (HART-enabled) |
| Safety Rating | SIL 2 (single config) / SIL 3 (1oo2 redundant) |
| Hazardous Area | ATEX II 3G Ex ec IIC T4 Gc (Zone 2) |
| ATEX Certificate | Presafe 18ATEX12094X |
| Operating Temperature | -15°C to +70°C |
| Storage Temperature | -25°C to +70°C |
| Humidity (Operating) | ≤95% RH, non-condensing |
| Protection Class | IP20 (IEC 60529) |
| Width | 158 mm |
| Depth | 87 mm |
| Weight | 1.35 kg |
| Mounting | DIN rail (35 mm, 7.5/15 mm profile) |
| MTBF (SN29500 @ 40°C) | 17 years |
| Compliance | IACS E10, DNV GL v2.4, IEC 60945, RoHS 2011/65/EU, EMC 2014/30/EU |
| Firmware Upgrade | Online (non-disruptive) |
| Diagnostics | Extended loop monitoring with per-channel current leakage detection |
Product Introduction
The KONGSBERG RMP201-8 is a 32-channel HART-enabled analog input module in the RBUS remote I/O family, built for safety-rated signal acquisition in marine dynamic positioning systems, shipboard automation (K-Chief), and industrial process control environments. It connects to RBUS controllers such as the RCU501 and RCU502 over the KONGSBERG proprietary RBUS fieldbus.Each of the 32 input channels supports HART communication transparently, meaning HART variables from smart field instruments pass through to the host system without additional configuration layers. The module carries SIL 2 certification in a single configuration and SIL 3 in a 1oo2 redundant setup — a distinction that matters when you are designing or maintaining a DP class 2 or class 3 position reference system. Extended loop monitoring runs continuously on every channel, including current leakage detection, which catches wiring degradation before it becomes a trip event.
Installation & Configuration Guide
Phase 1 — Preparation (10 min)
- Confirm the RBUS controller model (RCU501 or RCU502) and verify the RBUS segment address assignment.
- Verify the 24 VDC supply to the RBUS segment is within tolerance and stable.
- Identify the DIN-rail position for the RMP201-8. Leave adequate spacing per the KONGSBERG installation manual for heat dissipation.
- Confirm the module firmware version matches the project configuration. (Mismatched firmware is the most common cause of “module not recognized” errors after a swap.)
- Attach an ESD wrist strap before handling the module.
Phase 2 — Removal of Existing Module (5–10 min)
- If replacing a faulty RMP201-8, document the RBUS node address and channel mapping before removal.
- Disconnect field wiring from the front-panel terminals. Label each wire.
- Release the DIN-rail latch and slide the module off the rail.
- Inspect the RBUS connector pins for corrosion or bending.
Phase 3 — Installation (10 min)
- Snap the replacement RMP201-8 onto the DIN rail (35 mm, 7.5 or 15 mm profile).
- Reconnect field wiring per the documented channel map.
- Verify the RBUS connector seats fully — a partial connection will cause intermittent communication faults.
Phase 4 — Power-On & Test (10 min)
- Observe the status LEDs. The module should pass its self-test and report online status to the RBUS controller.
- Open the KONGSBERG engineering tool (e.g., K-Chief configuration or Presafe tool) and confirm the module appears in the hardware tree.
- Verify channel readings against known field values.
- If running in SIL 3 (1oo2), confirm the redundant module is also online and synchronized.
Troubleshooting Quick Reference
| Symptom | Most Likely Cause | First Check |
|---|---|---|
| Module not recognized on RBUS | Wrong node address or firmware mismatch | Verify RBUS address DIP settings; check firmware revision against project file |
| Channel reads zero or open | Field wiring disconnected or sensor fault | Measure loop current at terminal; check sensor power |
| Leakage alarm on one channel | Insulation degradation or moisture ingress | Inspect cable and terminal for moisture; measure insulation resistance |
| Intermittent communication drops | Loose RBUS connector or cable fault | Reseat connector; check RBUS segment cable continuity |
| SIL mismatch alarm | Redundant partner module offline or desynchronized | Verify both modules are online; check 1oo2 configuration in engineering tool |
| HART variables not passing through | HART pass-through not enabled for that channel | Enable transparent HART mode in channel configuration |
Dimensions, Mounting & Wiring Notes
- Form Factor: DIN-rail mounted module
- Mounting: 35 mm DIN rail (7.5 mm or 15 mm rail profile)
- Width: 158 mm
- Depth: 87 mm
- Weight: 1.35 kg
- Protection: IP20 — install inside an enclosure rated for the ambient environment
- Field Wiring: Front-panel screw terminals for 32 analog input channels
- RBUS Connection: Rear or side RBUS bus connector (verify against physical unit)
SOP Required: Incoming Inspection & Testing
1. Incoming Inspection
- Origin verification: Confirm the part number (RMP201-8) and order code (324400) match the purchase order. Cross-check the ATEX certificate number (Presafe 18ATEX12094X) on the label.
- Anti-counterfeit check: Inspect the label print quality, KONGSBERG logo placement, and serial number format. Compare against known genuine units if available.
- Physical inspection: Check for bent DIN-rail clips, damaged terminals, or signs of rework on the PCB.
- Accessories verification: Confirm any included mounting hardware or documentation matches the packing list.
2. Live Functional Testing
- Test setup: Mount on a dedicated test DIN rail with a known RBUS controller (RCU501 or RCU502).
- Power-on self-test: Apply 24 VDC and verify the module passes its internal POST without fault LEDs.
- RBUS handshake: Confirm the controller recognizes the module and reads the correct firmware version.
- Channel simulation: Inject known current or voltage signals across a sample of channels (e.g., 4 mA, 12 mA, 20 mA) and verify the controller reads correct values.
- HART pass-through test: Connect a HART communicator to one channel and verify variable readback through the RBUS.
- 24-hour soak: Run the module under continuous load for 24 hours to screen for intermittent faults.
- Test report: Generate and archive a test report with timestamp, firmware version, and channel-by-channel results.
3. Electrical Testing
- Insulation resistance: >10 MΩ at 500 VDC between channels and ground.
- Ground continuity: Verify chassis ground path.
- Hi-pot test: Perform if applicable per the module’s rated voltage class.
4. Firmware Verification
- Record the firmware version and hardware revision from the module label and RBUS diagnostic readback.
- Photograph any DIP switch or jumper settings before removal from test setup.
5. Final QC & Packaging
- QC sign-off on the test report.
- Pack in anti-static bag, sealed with bubble wrap inside a shipping carton.
- Affix “QC Passed” label with date and inspector ID.
Technical Pitfall Guide
Firmware Mismatch
A common scenario: you swap in a replacement RMP201-8 and the RBUS controller reports “module type mismatch” or refuses to download the project. This happens when the replacement has a different firmware revision than what the project file expects. Fix: update the project hardware definition to match the replacement firmware, then re-download. (Always photograph the label before removing the old module.)
DIP/Jumper Misconfiguration
The RBUS node address is set via hardware DIP switches or jumpers. If you forget to match the address to the original module, the controller will either ignore the new module or report a duplicate address fault. Always photograph the DIP settings before pulling the old module.
Terminal Incompatibility
The RMP201-8 uses specific front-panel terminal blocks. If your field wiring uses ferrules or wire gauges outside the rated range, you risk poor contact or terminal damage. Check the terminal rating before connecting.
Power Supply Capacity Margin
The RBUS segment power supply must handle the total current draw of all modules on the segment, plus a 20% margin. Adding an RMP201-8 to a fully loaded segment without recalculating the power budget can cause brownout conditions on the bus.
ESD Damage Risk
The RBUS connector and front-panel terminals are sensitive to electrostatic discharge. Always use an ESD wrist strap and mat when handling the module. A zap that does not kill the module outright can still cause latent damage that shows up months later as intermittent channel faults.
FAQ
Can I use the RMP201-8 in a non-marine industrial application?
Yes. While the module is designed and certified for marine environments (DNV GL, IEC 60945, IACS E10), its RBUS interface and I/O functionality work in any industrial application where an RBUS controller is the host. The marine certifications simply mean it has been tested to harsher environmental standards than a typical factory-floor module.What’s the difference between RMP201-8 and RMP420?
The RMP201-8 is a 32-channel HART analog input module. The RMP420 is a different module in the same RBUS family with a different channel configuration. They are not interchangeable — verify your system’s bill of materials before ordering.I’m seeing a leakage alarm on channel 17. Is the module defective?
Not necessarily. The RMP201-8 runs continuous current leakage detection on every channel. A leakage alarm usually points to insulation degradation in the field cable or moisture at a junction box — not a module fault. Measure the insulation resistance on that channel’s wiring before condemning the module.Can I hot-swap this module during live operation?
The module supports online firmware upgrades, but physical hot-swap of the module itself depends on your RBUS controller configuration and whether the channels are part of a live safety function. If the channels feed a SIL-rated trip, do not remove the module without following your plant’s safety procedure.Is this module still in production?
Verify directly with KONGSBERG or an authorized distributor. The RBUS platform is an established product line, but specific module revisions may have lifecycle status changes. Third-party suppliers may offer new surplus or refurbished units — confirm condition and warranty before purchasing.What controller do I need to run this module?
The RMP201-8 requires an RBUS-compatible controller such as the RCU501 or RCU502. It cannot operate standalone — it must be part of an RBUS segment managed by a host controller.
