Kongsberg RCU501 Remote Controller Unit Rev 1.1.2

Kongsberg RCU501

Key Technical Specifications

• Processor: High-performance embedded controller for real-time marine applications
• Supply Voltage: Dual 24 V DC inputs for power redundancy
• Communication:
  • 2 x Ethernet ports (10/100 Mbps) for R-Net/K-Net connectivity
  • 2 x CANbus ports for I/O module expansion
  • RS-232 / RS-485 serial ports for third-party integration
• Mounting: Standard DIN rail or specialized Kongsberg subrack
• Diagnostic Display: Front-panel status LEDs (Power, Run, Error, Net Activity)
• Environment: Type approved for bridge, engine room, and pump room installations
• OS Compatibility: Kongsberg proprietary real-time operating system

Installation & Configuration Guide

Phase 1: Pre-Installation

Estimated time: 15 minutes

⚠️ Marine Safety Protocol:

1. This unit often serves as a node for Dynamic Positioning (DP) or Engine Monitoring. Ensure the system is in “Manual” or “Independent” mode.
2. In a redundant setup, ensure the “B” controller is healthy before touching the “A” unit to prevent a total system blackout.
3. Verify the Revision Number (1.1.2). Kongsberg RCU501 units must have compatible revisions to sync correctly in a redundant pair.

Preparation:

• Laptop with Kongsberg Maintenance Pro or K-Set software.
• Shielded Ethernet cables (Cat5e or higher).
• Anti-static wrist strap.

Phase 2: Removal

Estimated time: 10 minutes

1. Power Isolation: Switch off both 24 V DC supply breakers. Confirm 0 V with a multimeter at the Phoenix connectors.
2. Network Disconnection: Unplug the R-Net Ethernet cables. Label them “Net A” and “Net B” to prevent cross-connection.
3. I/O Cables: Disconnect CANbus and Serial terminal blocks.
4. Unit Release: Use a flathead screwdriver to release the DIN rail clip at the bottom and tilt the RCU501 upwards.

Phase 3: Installation

Estimated time: 15 minutes

1. Mounting: Secure the RCU501 onto the DIN rail. Ensure there is at least 30 mm of vertical space for heat dissipation.
2. Earthing: Ensure the RCU501 chassis ground is bonded to the cabinet earth bar. Marine systems are highly sensitive to “floating” grounds.
3. Reconnect Cables:
   • Plug in the Ethernet cables (check for the “click” to ensure locking).
   • Re-insert the 24 V power terminals.
   • Connect CANbus and Serial links.

Phase 4: Power-On & Testing

Estimated time: 45 minutes

1. Boot Sequence: Apply power. The “Power” LED should be solid green, and the “Run” LED should blink during the boot sequence (approx. 60 seconds).
2. IP Addressing: Use the Maintenance Pro tool to assign the correct IP address and Node ID. In Kongsberg systems, the Node ID is critical for the RCU to pull its configuration from the Master Station.
3. Firmware Sync: If replacing one unit in a redundant pair, use the “Sync” function to ensure the new RCU501 matches the firmware and application version of its partner.
4. Function Test: Verify that I/O values (temperatures, pressures, or thruster commands) are updating on the operator station.

Customer Cases & Industry Applications

Case 1: DP Class 2 OSV Recovery in West Africa

Situation: A Platform Supply Vessel (PSV) reported a “Controller Communication Failure” on its K-Pos DP system. The master RCU501 (Rev 1.1.2) had suffered a hardware fault due to a power surge after a generator malfunction.

Task: The vessel lost its DP2 redundancy. Without a functional RCU, the vessel was forced to leave the platform safety zone, incurring heavy daily penalties and delaying offshore cargo operations.

Action: We shipped a New Surplus RCU501 Rev 1.1.2 from our stock via priority air freight to Luanda, Angola. We provided the specific boot-up sequence instructions to ensure the new node synchronized with the existing K-Pos network.

Result: The onboard ETO replaced the unit and performed a network sync. The DP system regained full redundancy within 4 hours of the part arriving on board. The vessel resumed its contract, avoiding over $100,000 in potential off-hire fees.

Frequently Asked Questions (FAQ)

Q1: Can I replace a Rev 1.1.2 with a later revision (e.g., Rev 2.x)? A: Technically risky. While the hardware may fit, Kongsberg RCU revisions often involve different internal chipsets or memory maps. Swapping versions in a redundant pair without a full system software upgrade can lead to “Split Brain” scenarios where the two units cannot communicate. I recommend sticking to the 1.1.2 revision for a plug-and-play experience.

Q2: Does the RCU501 store the application software? A: The RCU501 stores the operating system and the local application in its internal flash memory. However, it typically downloads the most recent “Running” configuration from the operator station or master controller upon joining the network.

Q3: My RCU501 “Error” LED is flashing red. What does it mean? A: A flashing red LED usually indicates a Configuration Mismatch or a Communication Timeout on the CANbus side. Check your I/O module health and ensure the Node ID is set correctly in the software.

Q4: Is “New Surplus” safe for Kongsberg maritime equipment? A: Yes. Kongsberg equipment is built to military-grade standards. “New Surplus” units are typically kept as spares in climate-controlled environments. They offer the same MTBF (Mean Time Between Failures) as a factory-new unit but are available for immediate shipment—critical when a ship is in port for a limited time.

Q5: How do I handle the licensing for a replacement unit? A: Kongsberg licenses are usually tied to the System ID (the vessel’s hardware key). Replacing an RCU node usually does not require a new license, provided the Node ID and System ID remain unchanged.