GE-IP | 9030 | GE Fanuc 90-30 GE-IP PLC

IC693CMM321 Image


  • Availability: In Stock Ships Today!
  • Units in Stock: Immediate Availablity: 5 Units!
  • Call for best Pricing+ 1 919 680 1773
  • Manufacturer: GE-IP
  • Description: GE Fanuc Series 90-30 Modbus EGD Ethernet Interface TCP/IP Module
  • Weight: 1 lbs :: ≈ 1 kgs
  • Warranty: 1 Years
  • Product Revisions Available:
  • Other Available Revisions of the IC693CMM321 : A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, -KN, -KM, -KL, -JL, -JK, -HJ, -GH, -FG, -EF, -EE, -DD, -CD, -CC, -BA,

Product Manual Excerpt

Product: Factory LAN TCP/IP Ethernet Interface Module for IC693 PLC IC693CMM321-GJ with Firmware Release 3.11 This document contains information about this product that is not available in any other publication; therefore, we suggest you read it, then save it with your other PLC documentation. General Description This release consists of a firmware update for the IC693CMM321 Ethernet Interface Module. Release 3.11 resolves two issues in previous versions. For details, see Problems Resolved by this Release on page 6. Note that firmware releases numbered 3.00 and greater apply only to hardware revision -Fx modules or later. This firmware cannot be loaded into a IC693CMM321-Ax, -Bx, -Cx, -Dx, or -Ex. Users of the IC693CMM321-EF and earlier modules can update by replacing their older Ethernet Interface module with an IC693CMM321-Fx or -Gx module. CAUTION The release 3.11 field upgrade kit replaces both the TCP/IP software and software loader of the IC693CMM321. A power interruption during the approximately three seconds required to re-program flash memory with the new software loader will cause the module to become completely inoperative. See Operational Notes on page 3 for more information. DO NOT attempt to upgrade your IC693CMM321 to release 3.11 unless your Series 90-30 PLC has a reliable power source. DO NOT turn power off during the upgrade process. This module provides MODBUS/TCP Master and Slave functionality. It provides network communications using the SRTP (Service Request Transfer Protocol) over standard TCP/IP (Transmission Control Protocol / Internet Protocol) on an Ethernet Local Area Network (LAN). The Ethernet Interface supports communication between IC693 PLCs, IC697 PLCs, IC698 PLCs, and/or IC200 PLCs equipped with TCP/IP Ethernet Interfaces. It can communicate with the various Windows-based PLC software products and the TCP/IP version of the DOS-based software. Hardware Identification: EM3A2-44A751166-G01 R02 Software Identification: IC693CMM321-GJ Software Loader: Version 3.01 TCP/IP: Version 3.11 Replaces Module Versions: IC693CMM321-GH Firmware Field Upgrade Kit 44A751570-G02 Note that this hardware requires the use of a Station Manager cable (IC693CBL316) to update firmware. MODBUS is a registered trademark of Schneider Automation, Inc. 2 Important Product Information GFK-1085R Upgrade Strategy ■ Firmware version 3.11 is incompatible with module versions IC693CMM321-EF and earlier. ■ Module versions -FG and -FH may be upgraded to -FJ using the kit specified below. ■ Module version -GH may be upgraded to -GJ using the kit specified below. ■ Module hardware version -F may be upgraded to hardware version -G by returning modules to the factory. See Problems Resolved by Hardware Version G on page 6 for details. Functional Compatibility Release 3.11 of the IC693CMM321 is compatible with these products: ■ IC693 PLC CPU firmware version 6.50 or later; restricted operation with CPU firmware 5.03 (6.03 for Model 351 CPU). See Additional Restrictions with CPU Firmware Earlier than Version 6.50 on page 8. ■ PLC Logic Developer version 2.11 or later. ■ VersaPro version 1.01 or later. Version 2.02 or later is required to store hardware configurations that contain module initialization files larger than 32,768 bytes. ■ Windows -based programming software, version 2.01 or later. ■ The MS-DOS-based programming software IC693 version 6.01 or later. ■ The MS-DOS-based programming software IC693 TCP/IP Ethernet version 7.01 or later. Hardware Compatibility EM3A2-44A751166-G01 R00 or later versions Documentation For changes and additions to user documentation, see page 9. TCP/IP Ethernet Communications User s Manual, version B or later TCP/IP Ethernet Communications Station Manager Manual, version G or later  MS-DOS, Windows, and Microsoft are registered trademarks of Microsoft, Incorporated. Important Product Information 3 GFK-1085R Operational Notes Power Loss During Field Upgrade to Release 3.11 or Newer May Leave Ethernet Module Inoperative The field upgrade kit for release 3.11 or newer (including ZIP files downloaded from the GE Fanuc PLC Technical Support Web site) replaces the software loader of the IC693CMM321 as well as the TCP/IP software. A power interruption during the approximately three seconds required to reprogram flash memory with the new software loader will cause the module to become completely inoperative. To recover from this condition, the module must be returned to the factory. CAUTION DO NOT attempt to upgrade your IC693CMM321 to release 3.11 unless your Series 90-30 PLC has a reliable power source. DO NOT turn power off during the upgrade process. This Firmware Release is Incompatible with Version IC693CMM321-EF or Older Hardware You should not attempt to use this firmware with older versions of this module. If this firmware version were to be loaded to an IC693CMM321-EF or older version of this module, the module will not function as expected, and the following symptoms will be observed: 1. The interface is unable to go online. 2. The STAT and SER LEDs blink alternately at a -second rate. 3. The LAN Interface OK and LAN OK bits in the LAN Interface Status Word remain off. 4. A PLC fault with text \"LAN system-software fault; resuming\" occurs. 5. A System log event (Event 2, entry 2 = 0401H) occurs in the Station Manager event log. 6. The following incompatible hardware message is printed to the Station Manager display from the NODE and STAT L commands: This firmware version requires IC693CMM321-F or later hardware. Your hardware version is incompatible, and the network interface is unable to go online. To recover, please use the firmware loader to reload firmware version 2.20. It is available from the PLC Technical Support web page. See the TCP/IP Ethernet Communications User\'s Manual for details. To restore correct operation, update the module firmware to version 2.20. If you do not have the version 2.20 field update kit, part number 44A737842-G05, download the file cmm321-r220.zip from the PLC Technical Support web page, unzip the file, and then follow the instructions in cmm321update.doc (included in the ZIP file). System Requirements This version of Ethernet Interface firmware requires IC693 CPU firmware version 6.50 or later for full operation. Restricted operation is available with CPU firmware version 5.03 or later (6.03 for the Model 351 CPU). However, Ethernet Interface users are strongly urged to update their CPU firmware. See Additional Restrictions with CPU Firmware Earlier than Version 6.50 on page 8. Connecting to PLC programming software via Ethernet requires both IC693 CPU version 6.50 (or later version) and Ethernet Interface version 1.10 or higher. 4 Important Product Information GFK-1085R Power Supply Requirements ■ The Ethernet Interface requires PLC Power Supply IC693PWR321 (Rev. K or later), IC693PWR322, or IC693PWR330. ■ Power consumption of the Ethernet Interface module is 700mA @ +5VDC, plus power required by the optional AAUI transceiver. ■ This version of IC693CMM321 hardware does not require an AAUI transceiver for operation on 10Base-T networks. If an AAUI transceiver is used (for example, on an optical fiber Ethernet network), be sure to include the +5VDC power required by the transceiver (typically 50 to 350mA) when calculating the total power consumption of the PLC rack. Consult the transceiver documentation to obtain its power requirements. Configuration Through Serial Port Required Before Using Ethernet Communications The Ethernet Interface cannot operate on the network until a valid IP address is configured. The necessary Ethernet addressing information must be configured prior to actual network operation. Two methods are available: 1. Perform the initial configuration using a PLC Programmer through the PLC CPU serial port. 2. Connect a serial terminal to the Station Manager port (port 1) of the Ethernet Interface module. Then use the CHSOSW command to enter a temporary IP address. The interface can then be reached by a PLC programmer via Ethernet. See TCP/IP Ethernet Communications for the PLC Station Manager Manual for details. Proper IP Addressing is Always Essential The Ethernet Interface must be configured with the correct IP Address for proper operation in a TCP/IP Ethernet network. Use of incorrect IP addresses can disrupt network operation. Refer to TCP/IP Ethernet Communications User s Manual for important information on IP addressing. AAUI Cable Attachment Power to the PLC must be turned off whenever the transceiver (AAUI) cable is connected or disconnected at the Ethernet Interface or at the transceiver. Sudden changes in power supply loading caused by connecting or disconnecting the transceiver with power on may result in unexpected operation of the Ethernet Interface, PLC CPU or other modules. Connecting the transceiver with power on may also blow the protective fuse. A blown fuse cannot be replaced in the field; the Ethernet Interface must be returned for repair. SQE Enable If you use an external AAUI transceiver, the Ethernet Interface requires the SQE test signal to be enabled on the transceiver. Make sure your transceiver has SQE enabled. No HHP Support The Hand Held Programmer (IC693PRG300) may not be used to configure the Ethernet Interface. Do not attempt to configure the Ethernet Interface or to read its configuration with the HHP. Such attempts may result in erroneous Loss-of-Module faults in the PLC Fault Table or other unexpected behavior. Important Product Information 5 GFK-1085R Serial Load/Store of Register Table Causes Ethernet Programmers to Lose Communication A load or store of the PLC Register (%R) table by a PLC Programmer connected through the CPU serial port can cause Ethernet applications that use the PLC programmer communication window to lose communication. This condition occurs when the load/store operation requires more than 10 seconds to complete. For example, transferring the %R table of a CPU341 or CPU351 at 19,200 baud or less will cause the timeout. The Ethernet Interface posts two or more PLC faults with the text LAN system-software fault; resuming , and fault-specific data starting with 080008 and/or 080042. In addition, faults with text Bad remote application request; discarded request (1B0021) and Local request to send rejected; discarded request (110005) may occur. The STAT LED on the Ethernet Interface goes out. IC693 MS-DOS TCP/IP Software Briefly Loses Communication When Configuration Cleared or Stored Clearing or storing the PLC configuration causes the MS-DOS Ethernet programming software to display a flashing NO COMMUNICATIONS message for one or two seconds. PLC faults similar to those listed under Serial Load/Store of Register Table Causes Ethernet Programmers to Lose Communication above occur; the STAT LED on the Ethernet Interface goes out. In some cases, a ten second delay occurs before loss of communication is detected. When the PLC configuration is stored from the MS-DOS Ethernet programming software, the communications loss occurs immediately after successful completion of the store. Attempts to store configuration plus logic and/or reference tables in one operation can fail. However, storing configuration separately from logic or reference tables will always succeed. See Restrictions and Open Problems on page 7 for a description of operational behavior when configuration is cleared or stored using VersaPro. Clearing Slot Configuration Closes TCP Connections When the PLC CPU contains version 6.50 or later firmware, clearing the slot configuration of the Ethernet Interface causes the interface to close all of its TCP connections immediately. The Ethernet Interface slot configuration is cleared when a PLC Programmer connected via Ethernet clears the PLC configuration, or stores a new configuration with an empty slot or different module type at the location where the interface is installed. PLC faults similar to those listed under Serial Load/Store of Register Table Causes Ethernet Programmers to Lose Communication above occur; the STAT LED on the Ethernet Interface goes out. Applications that use the Ethernet Interface s SRTP server, such as Host Communications Toolkit client applications, must be aware that the connection has closed and take action to establish a new connection. Extra Channels Data Transfer Entering STOP/IOSCAN Mode Use caution when configuring the PLC CPU to scan I/O in STOP mode. There is a small time delay between a RUN to STOP/IOSCAN mode transition in the PLC CPU and the time when the Ethernet Interface deactivates repeating channels. The length of this delay varies with the PLC hardware configuration and the application program. In some cases, the time delay will be long enough that one data transfer by a repeating channel will occur after the CPU mode transition. After a RUN to STOP/NO IO mode transition, the Ethernet Interface aborts repeating channels immediately. 6 Important Product Information GFK-1085R RUN Mode Program Store A store of a folder containing large (greater than 14kb) program blocks using a PLC Programmer via Ethernet may fail and result in momentary loss of communication. This condition has been observed only when attempting to store a large program to a PLC which is in RUN mode, and which is configured to use a limited communication window. These conditions cause the store operation to take the maximum possible period to complete. The failure may occur if this period exceeds 10 seconds for an individual program block. If this problem does occur, one of the following options may be used to complete the store operation successfully: 1. Change the PLC configuration to use Run-to-Completion mode instead of a Limited Communication Window for the store operation. 2. Change the PLC from RUN to STOP mode to complete the store. 3. Structure the folder being stored to eliminate large program blocks or subroutine blocks. This will minimize the chance that any single block will take longer than the maximum 10-second period allowed for storage of that block. Problems Resolved by this Release Module Hardware Faults in CMM311 and PCM3xx Modules An IC693CMM321-FG or -GH module (version 3.00 or 3.10) installed anywhere in the same rack with one or more IC693CMM311, IC693PCM300, IC693PCM301 and/or IC693PCM311 modules will cause all of the latter modules to post a non-fatal module hardware fault (error code 1009) to the PLC fault table each time the rack is powered on. This issue is resolved in version 3.11. Reset while Running Modbus/TCP IC693CMM321-GH (firmware version 3.10) may reset itself after running Modbus/TCP for a period of time, depending on the application. This issue is resolved in version 3.11. Problems Resolved by Hardware Version -G An IC693CMM321-Fx Ethernet module will occasionally cease transmission on the network. This can cause timeouts of SRTP Channels, timeouts of SRTP Server operations (programmer connection, HMI, etc.), failure to reply to PING requests, etc. The module s exception log may contain c/10b and 11/5 entries. The module will spontaneously resume transmission after a brief period (usually a few seconds). This issue is resolved in hardware version -G. IC693CMM321-FG through -FJ modules may be upgraded to IC693CMM321-GJ by returning them to the factory. The hardware is NOT fieldupgradeable. Important Product Information 7 GFK-1085R Restrictions and Open Problems ■ The Ethernet Interface sometimes generates multiple exception log events and PLC Fault Table entries when a single error condition occurs. Under repetitive error conditions, the exception log and/or PLC Fault Table can be completely filled with repetitive error messages. ■ Initialization errors that generate any of the following exception log events should also restart the Ethernet Interface into Maintenance state: event 1b, entry 2 = 0003h; event 1c, entry 2 = 25h, or event 1c, entry 2 = 26h. The Ethernet Interface does not restart in these conditions. ■ Use of the same IP Address by this Ethernet Interface and by another device on the same network results in the PLC Fault Table message Bad remote application request; discarded request. This condition should be identified more precisely. ■ When the client or server PLC scan time exceeds 100 ms, channels may fail with error codes 2411, 0B11, 9B90, 3F11, or 9590. The error codes may be viewed by doing a Stat H command. ■ While a local Station Manager TRACE LZ troubleshooting command is in effect at an Ethernet Interface, do not issue Station Manager REM TEST commands to it from a remote Interface. Doing so can cause errant behavior, including Interface lockup and loss-of-module in the PLC fault table. ■ After performing a firmware update to an Ethernet Interface in which one or more Advanced User Parameters have been set to non-default values, the PLC Fault Table does not contain the message it should ( LAN IF can t init-check parms; running soft Sw Utl ); rather, no fault table entry appears. There is no indication in the fault table that the Ethernet Interface has entered Maintenance state to permit resetting of the user parameter(s). The Ethernet Interface does generate an entry in its exception log. ■ The TCP tallies CurEstab and EstabRes do not always report the correct value. ■ An Information Report channel may remain in the AWAIT_DRSP or AWAIT_CRSP state indefinitely if the remote host fails to send a response. ■ When using VersaPro via Ethernet through this Ethernet Interface, a Clear operation that does not include clear of Software Configuration causes VersaPro to crash . This behavior is not observed using the other Ethernet programmers or if VersaPro is connected to the PLC via the Ethernet Interface within an IC693CPU364. Rebooting the PC is often required to re-establish communication with the PLC. 8