Features:
- Provides two programmable serial interfaces for the Series Six CPU.
- Supports CCM communication over RS-232 and RS-422 links.
- Uses a 1024-byte quick-access buffer with expanded memory references.
IC600CB536 connects the controller with hosts, peer CCM devices, terminals, process systems, and operator interfaces.
Each port has its own physical and protocol context, making the saved configuration as important as the replacement board.
The Type 2 module is for CCM; RTU-dependent applications require the Type 3 option.
For General Electric IC600CB536 Type 2 Communications Control Module quotations and original manufacturer documentation support, contact Apter Power.
General Electric IC600CB536 Type 2 Communications Control Module Manuals, Datasheets, Links
Important Notice: Other accessories, manuals, cables, calibration data, software, etc. are not included with this equipment unless listed in the above stock item description. All prices are shown in USD.
Choose the interface from distance and topology
- Serial interface: IC600CB536 RS-232 serves short direct runs, while RS-422 supports the long-distance or multidrop arrangement.
- Cable path: Match each transmit and receive pair, shield, ground, and termination to the verified port wiring plan.
- Indicator meaning: A cable assembled by connector shape alone can cross the differential pairs.
- Modem signals: For modem service, preserve control-signal timing and the remote modem setup.
Keep both channels independently recorded
- Address map: Record electrical mode, rate, address, master or slave role, timeout, and attached device for each IC600CB536 port.
- Application path: Capture the CPU ID and any application request that moves data through the module.
- Functional proof: Test one port without changing the other.
- Message baseline: Retain a successful message trace as the commissioning baseline.
Verify the intended CPU data areas
- CPU data access: The module can exchange expanded I/O, override, register, and user-memory information under CCM rules.
- Program record: Map every host command to an authorized destination before testing writes.
- Program context: Use safe values and confirm the receiving program logic.
- Data direction: A successful link is incomplete until the correct data and update direction are proven.
Use the indicator sequence to separate setup faults
- Rack arrangement: Check IC600CB536 rack position, backplane switch state, CPU ID, and port configuration before power-up.
- LED evidence: An unexpected LED sequence should be recorded before cycling power.
- Fault isolation: Compare it with CPU communication and the matching fault sequence.
- Release criterion: Release the link to normal service only after both the hardware and application exchange are repeatable.