Ask our team:
  • Phone: +86 181 0690 9650
  • E-Mail sales1@apterpower.com
  • Lifecycle status

    Active / Available from OEM
    Apter Power can quote and source IC600BF940 and provide the applicable General Electric manufacturer documentation.

IC600BF940

/ 4.9
1001 reviews | Need a Specific Revision?
General Electric IC600BF940 is a Series Six local I/O transmitter module with selectable status-byte generation for RPU Channel 1 integration.
In Stock
Ships by Thursday, October 29
Fast Shipping Available
Get a quick price for IC600BF940
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for IC600BF940

  • Manufacturer:
    General Electric
  • Part Number:
    IC600BF940
  • Product Family:
    GE Series Six Plus
  • Product Type:
    Local I/O Transmitter Module
  • Stock:
    1
  • Module type:
    Local I/O transmitter module
  • System:
    GE Series Six
  • Manufacturer description:
    Second version of the I/O Transmitter Module
  • Configuration control:
    Circuit-board Status Byte jumper
  • Status Byte options:
    Enable or disable generation
  • Documented RPU use:
    Conventional Series Six I/O on Expanded Channel 1
  • Required Channel 1 RPU setting:
    Status Byte generation disabled
  • Conflict avoided:
    Transmitter Status Byte at R256
  • RPU reserved registers:
    R0254, R0255, and R0256
  • Protected transfer functions:
    Backup-to-master transfer and register transfer
  • Affected Channel 1 input range:
    I01 + 0977 through I01 + 1024
  • Tariff Code:
    8538900000
  • Country of origin:
    USA
  • Place of shipment:
    Xiamen,Fujian,China
By purchasing this item, you agree to the Terms & Conditions, ApterPower is not an authorized distributor for listed manufacturers or tradenames and therefore the manufacturer's warranty does not apply. All our products come with ApterPower's 1-year warranty.

More Information

Overview Manuals Compatibility Connectivity Monitor Protection

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.
Description
The General Electric IC600BF940 is a Series Six local I/O transmitter module identified in the original GE Redundant Processor Unit documentation as the second transmitter version.

In an RPU system, IC600BF940 supports conventional Series Six I/O on Expanded Channel 1, where transmitter status data would otherwise conflict with registers reserved for processor transfer functions.

A circuit-board jumper lets IC600BF940 enable or disable Status Byte generation. GE directs Channel 1 RPU applications to use this model with that generation disabled.

With the Status Byte suppressed, IC600BF940 avoids the R256 conflict associated with conventional Channel 1 I/O while the RPU retains R0254 through R0256 for backup-to-master and register transfers.
Alternative Names
IC600 BF940 IC600-BF940 IC-600-BF-940 GE IC600BF940 General Electric IC600BF940 Series Six IC600BF940 1C600BF940 IC6008F940
Technical notes
Before fitting IC600BF940 in an RPU Channel 1 path, document the status-byte jumper position and verify that the protected R0254–R0256 transfer registers remain unclaimed.
Exceptional Service

Our Mission

  • 100% Satisfaction

    We believe expertise is priceless. With over 20 years of experience, and top engineers on staff, we can help you solve or avoid problems that threaten your business.
  • Trust Guaranteed

    Not only do we have a vast inventory, our team makes sure every piece of equipment is in working condition. Your purchases are also backed by our Warranty.
  • Expertise

    Time is money, especially when your equipment is down. We work quickly to get your equipment on its way so you can get it back up and running.

FAQS

The following is a list of questions commonly asked by our customers. Please contact us if you have a question about our process that is not answered below.
Why is IC600BF940 specified instead of the earlier transmitter for RPU Channel 1?
IC600BF940 provides a jumper that can disable Status Byte generation, preventing the R256 conflict documented for conventional Series Six I/O on RPU Channel 1.
Which IC600BF940 setting is required for conventional I/O on RPU Channel 1?
IC600BF940 must have its Status Byte generation disabled when conventional Series Six I/O occupies Expanded Channel 1 in the documented RPU arrangement.
What can happen if IC600BF940 Status Byte generation remains enabled on RPU Channel 1?
IC600BF940 would use the R256 location that the RPU requires for transfer functions, creating a register-mapping conflict in that Channel 1 configuration.
Which RPU registers must be protected when configuring IC600BF940?
IC600BF940 planning should preserve R0254, R0255, and R0256 because the RPU uses those registers for backup-to-master and register transfer functions.
Which input-table range is affected by the IC600BF940 Channel 1 restriction?
IC600BF940 documentation identifies I01 + 0977 through I01 + 1024 as unavailable for other uses when the associated RPU transfer functions are required.
What should be recorded before replacing IC600BF940?
IC600BF940 replacement records should capture the physical slot, Expanded Channel 1 mapping, Status Byte jumper position, and whether RPU transfer functions use R0254 through R0256.
Can IC600BF940 be configured without reviewing the RPU map?
IC600BF940 should not be assigned a Status Byte setting from the part number alone; the actual channel allocation and reserved RPU registers determine the required jumper position.

Product Browsing History