Allen Bradley 1336-GM5 Serial Communication Module

The Allen Bradley 1336-GM5, also cataloged as the 1336GM5 Communication module, operates as a dedicated hardware component for DeviceNet adapter communication within 1336 Impact / Plus / Plus II / Force / Spider drive platforms.

Hardware Specifications

Profinet / EtherNet/IP Deterministic Networks and Bus Communication

The 1336-GM5 establishes robust data exchange across adjustable drive networks through a dedicated SCANport-to-DeviceNet adapter architecture. Hardware-level parameter adjustments are executed via onboard DIP switch configuration, ensuring precise network addressing and data rate alignment. Backplane communication velocities and register mappings maintain deterministic response cycles across compatible 1336 Impact, Plus, Plus II, Force, and Spider drive series without introducing latency into the primary motor control loops.

Frequently Asked Questions

Q: What communication protocols does the 1336-GM5 support?

A: The module functions as a DeviceNet adapter, converting SCANport communications to DeviceNet network protocols.

Q: How are configuration settings managed on this communication card?

A: Configuration is handled via onboard DIP switches to establish hardware-level parameters before drive operation.

Q: Is the manufacturer warranty applicable to the 1336-GM5?

A: No. The factory warranty does not apply as the unit is discontinued by the manufacturer, but it includes a Radwell 2-year warranty.

Field Installation Guidelines

1. Ensure the host drive is completely de-energized, locked out, and fully discharged of internal capacitor voltages prior to handling.
2. Observe standard electrostatic discharge (ESD) precautions by wearing a grounded wrist strap while handling the PC board add-on card.
3. Set the onboard DIP switches to match the required DeviceNet network address and communication parameters prior to mounting.
4. Mount the communication module securely onto the designated SCANport interface within the compatible 1336 drive enclosure, ensuring proper pin engagement.
5. Connect the DeviceNet network cabling to the adapter terminal, verify shield continuity, and re-energize the host drive to test communication links.