Features:
- IC600BF940 extends an RPU system with a second I/O transmitter.
- A board jumper selects whether the module generates a Status Byte.
- Disabled Status Byte generation prevents the Channel 1 R256 conflict.
IC600BF940 is the transmitter version specified when conventional Series Six I/O must use Expanded Channel 1 in a Redundant Processor Unit installation.
An on-board jumper enables or disables status-byte generation, allowing the transmitter to avoid consuming R256 when that register is required by RPU transfer functions.
Correct use depends on the connected CPU versions, scan-time configuration, RPU firmware, and arithmetic-control-board compatibility documented for the redundant system.
Apter Power can quote and source the General Electric IC600BF940 I/O Transmitter Module, provide the applicable manufacturer documentation, and assist with status-byte, Expanded Channel 1, RPU configuration, and replacement planning.
General Electric IC600BF940 Local I/O Transmitter Module Manuals, Datasheets, Links
RPU and CPU compatibility requirements
- CPU version: Both processors connected to the RPU must be version 103 or later.
- Short scan times: Systems below 150 ms can use pre-Revision F firmware or Revision G and later with the documented JP8 setting.
- Longer scan times: Operation above 150 ms and below 250 ms requires Revision G or later firmware and the 250 ms JP8 position.
- Arithmetic board: Scan times over 150 ms require the IC600CB524 ALU3 board; ALU1 and ALU2 do not support that configuration.
Expanded Channel 1 data connectivity
- Application: IC600BF940 connects conventional Series Six I/O where Expanded Channel 1 is required in an RPU system.
- Transfer path: Expanded-I/O data must be copied from the master CPU to the backup CPU with the Register Transfer function.
- Mapped data: Expanded-I/O input data is represented in register space within the redundant system image.
- Transmitter role: The module’s selectable status-byte behavior lets the I/O path coexist with the RPU register-transfer scheme.
Status-byte and CPU configuration checks
- Status-byte jumper: The circuit-board setting enables or disables transmitter status-byte generation.
- CPU-version check: The manufacturer directs technicians to read each CPU version from the Workmaster scratch-pad display.
- Compatibility test: With the RPU in HOLD, verify that both CPUs continue running to expose unsupported ALU combinations.
- System-image check: Confirm that the master-to-backup transfer includes the expanded-I/O data required by the application.
Register-conflict and timeout protection
- Reserved registers: R0254, R0255, and R0256 are used by RPU backup-to-master and register-transfer functions.
- Channel 1 conflict: The standard transmitter status byte occupies R256 and conflicts with the RPU register transfer.
- Corrective setting: IC600BF940 must be configured to disable status-byte generation when conventional I/O uses Expanded Channel 1.
- Timeout risk: Do not configure the 250 ms RPU mode with ALU1 or ALU2 CPUs, because a power or HOLD transition can cause CPU timeouts and I/O-chain reset.