Product Name: Communications Module
Brand Name: Allen Bradley
Model Number:1203-GU6
Country of Origin:USA
Warranty: 12 Months
Whatsapp：+86 18159889985
Email：[email protected]
Brand Name: |
Allen Bradley |
Model Number: |
1203-GU6 |
Country of Origin: |
USA |
Packaging Details: |
Original new Factory Sealed |
Delivery Time: |
Delivery time in stock |
Payment Terms: |
T/T |
|
Sales Manager: |
Stella |
|
Send an email: |
|
|
Contact in Whatsapp: |
|
Parameter |
Value |
|
Catalog Number |
1203-GU6 |
|
Dimensions (H×W×D) |
76 × 45 × 123 mm (3.0 × 1.8 × 4.8 in) |
|
Weight |
179 g (6.3 oz) |
|
Operating Temperature |
0 to +55 °C (+32 to +131 °F) |
|
Storage Temperature |
-40 to +85 °C (-40 to +185 °F) |
|
Relative Humidity |
5–80% (operating), 5–95% (non-condensing) |
|
Power Consumption |
130 mA at 12V (from SCANport) + 60 mA at 24V (from DeviceNet) |
|
DeviceNet Baud Rates |
125 kbps, 250 kbps, 500 kbps, or Autobaud |
|
DeviceNet Node Address |
0-63 (default 63) |
|
Supported I/O Words |
2 to 20 words (polled, COS, cyclic) |
|
Datalinks |
Up to 4 (A, B, C, D), each 2 words in/out |
|
Serial Port |
RS-232 (DF1) for configuration & flash upgrade |
|
Mounting |
35 × 7.5 mm DIN rail (EN 50022) |
|
Approvals |
UL 508, cUL, CE |
The 1203‑GU6 Enhanced DeviceNet adapter acts as a gateway between a SCANport product (such as a 1336 PLUS, 1305, 1336 FORCE, or SMC Dialog Plus) and a DeviceNet network. It supports master‑slave (scanner) communications via polled, change‑of‑state (COS), or cyclic I/O, as well as peer‑to‑peer data exchange between multiple 1203‑GU6 modules. The adapter features a removable 5‑pin or 10‑pin Phoenix connector for DeviceNet, a standard SCANport 8‑pin mini‑DIN connector, and an RS‑232 serial port for local configuration using a terminal emulator (e.g., HyperTerminal) or for flash firmware upgrades. The 1203‑GU6 obtains its primary power from the connected SCANport device, while the DeviceNet transceiver requires a separate 24V DC supply. Configuration parameters (node address, data rate, I/O allocation, datalink enable, fault actions) are stored in non‑volatile memory and can be edited either over the DeviceNet network using DeviceNet Manager or via the serial port. The module also supports DeviceNet object classes including Identity, Message Router, DeviceNet, Connection, Register, Parameter, and SCANport pass‑through objects.
Integrate SCANport drives (1305, 1336 PLUS, 1336 FORCE, 1394, etc.) into a DeviceNet network with a PLC‑5 or SLC scanner (1771‑SDN or 1747‑SDN)
Replace hardwired I/O with network control for start/stop, speed reference, and status monitoring
Use change‑of‑state (COS) to reduce network traffic by sending only changed data
Implement peer‑to‑peer drive‑to‑drive communication without a controller (e.g., master drive broadcasting speed reference to follower drives)
Retrofit existing SCANport devices into DeviceNet‑based control systems
Flash upgradeable – Field firmware updates via RS‑232 serial port using Xmodem protocol
Multiple I/O modes – Supports polled, change‑of‑state (COS), cyclic, and combined allocations
Peer‑to‑peer I/O – Direct drive‑to‑drive data exchange without a scanner (2 or 4 words)
Datalink support – Up to four datalinks (A‑D) for continuous parameter access without messaging (no EEPROM wear)
Fault configurable outputs – Selectable action (fault, zero data, hold last, or fault config values) on idle or communication loss
Autobaud detection – Automatically matches network data rate; can also be fixed to 125/250/500 kbps
LED diagnostics – Three bi‑color LEDs (Network Status, Module Status, SCANport Status) for rapid troubleshooting
Serial configuration port – Local access for parameter editing, event queue viewing, and DF1 statistics
Protocol conversion – Translates DeviceNet explicit and I/O messages to SCANport commands and vice versa
Scheduled I/O mapping – Moves logic command/status, reference/feedback, and datalink data between scanner image table and SCANport device
Explicit messaging – Supports PCCC and emulated block transfers for parameter reads/writes, fault queue access, and NVS (EEPROM) save/recall/initialize
Change‑of‑state (COS) operation – Transmits data only when logic status bits or feedback value changes beyond a configurable threshold
Peer‑to‑peer communication – One adapter transmits output data (2 or 4 words) and others receive it as input, with configurable timeouts and fault actions
Fault handling – On controller idle or network loss, the adapter can fault the drive, zero outputs, hold last state, or apply pre‑set fault configurable values
Q1: How do I set the DeviceNet node address on the 1203‑GU6?
A: By default, the 1203‑GU6 ships with node address 63. Use a serial connection (1203‑SFC cable + HyperTerminal) or DeviceNet Manager to edit parameter 2 (DN Node Address) to a unique value between 0 and 62. After changing, set parameter 22 (Reset Adapter) to Enable, or power cycle the module.
Q2: Can the 1203‑GU6 use change‑of‑state (COS) instead of polling?
A: Yes. Configure the adapter for COS by setting the M‑S Output parameter (25) and enabling COS in the scanner’s I/O parameters. You must also set COS Status Mask (26) to define which logic status bits trigger a transmission, and COS Feedback Change (27) to set the feedback deadband. The adapter will then send data only when a specified bit changes or feedback deviates beyond the threshold.
Q3: What is the difference between the 1203-GU6 and the 1336-GM6?
A: The 1203‑GU6 is an external DIN‑rail module with its own enclosure, powered via SCANport plus an external 24V DC supply for DeviceNet. The 1336‑GM6 is an open‑style board that mounts directly inside a compatible drive (e.g., 1336 PLUS) and draws 5V from the drive control board. Both have identical DeviceNet functionality.
Q4: How many I/O words can the 1203‑GU6 transfer?
A: Up to 10 words in each direction (20 total). This includes 2 words for Logic Command/Status, 2 words for Reference/Feedback, and up to 8 words for four datalinks (each datalink uses 2 words in and out). The actual size is set in the scanner’s I/O parameters and must match the adapter’s M‑S Input/Output configuration.
Q5: Does the 1203‑GU6 require an EDS file for use with DeviceNet Manager?
A: Yes, but the 1203‑GU6 supports uploading its EDS file directly over the network. In DeviceNet Manager, double‑click the device icon (default generic), answer “Yes” to create an EDS file, then click “Load from Device” – the software will retrieve all parameter information automatically. No manual file creation is needed.
EN
