IMPORTANT PRODUCT INFORMATION

Transcription

1 Restarts for autonumbers that do not restart in each chapter. figure bi level 1, reset table_big level 1, reset chap_big level 1, reset app_big level 1, reset figure_ap level 1, reset table_ap level 1, reset figure level 1, reset table level 1, reset these restarts must be in the header frame of chapter 1. a:ebx, l 1 reseta a:obx:l 1, reseta a:bigbx level 1 reseta a:ftr level 1 reseta c:ebx, l 1 reset1 c:obx:l 1, reset1 c:bigbx level 1 reset1 c:ftr level 1 reset1 Reminders for autonumbers that need to be restarted manually (first instance will always be 4) let_in level 1: A. B. C. letter level 1:A.B.C. num level 1: num_in level 1: rom_in level 1: I. II. III. roman level 1: I. II. III. steps level 1: IMPORTANT PRODUCT INFORMATION Compatibility Product: READ THIS INFORMATION FIRST Factory LAN TCP/IP Ethernet Interface IC693CMM321-AC IC693CMM321-BC* IC693CMM321-CC* This IPI describes the TCP/IP Ethernet Interfaces, IC693CMM321-AC, IC693CMM321-BC and IC693CMM321-CC. These catalog numbers refer to the Ethernet Interfaces, IC693CMM321-AA, IC693CMM321-BA and IC693CMM321-CB that have been upgraded to version 1.11 using the Field Upgrade kit 44A G02. These modules provide network communications using the SRTP (Service Request Transfer Protocol) over TCP/IP (Transmission Control Protocol and Internet Protocol) on an Ethernet Local Area Network (LAN). The Interface supports communication between IC693 PLCs and/or IC697 PLCs (equipped with Ethernet Interface, IC697CMM741, and TCP/IP software, IC697ENS042). Also, the Interface now supports communication to IC641 TCP/IP Ethernet programming software. The Ethernet Interface can respond to applications that communicate via the TCP/IP Host Communications software. See later sections for restrictions. The IC693 Ethernet Interface is compatible with the following products: IC693 PLC CPU firmware version 5.03 or later (version 6.03 or later for Model 351 CPU). IC641 programming software version 6.01 or later (required to configure the Ethernet Interface). IC641 TCP/IP Ethernet programming software version 6.50 or later. (required for TCP/IP Ethernet communications to the TCP/IP Ethernet Interface). Host Communications Toolkit software products, listed below. Note that applications built using previous releases of Toolkit products can successfully communicate only to IC697 Ethernet Interfaces. Applications must be relinked using the proper Toolkit release in order to communicate with the IC693 Ethernet Interface. (Once rebuilt, such applications may communicate interchangeably with both IC697 and IC 693 PLCs.) Refer to Host Communications Toolkit Important Product Information document (GFK-0871) for further details, including component version numbers. Toolkit for Microsoft Windows C/C++ Applications (IC641SWP052D or later) Toolkit for Windows NT C/C++ Applications (IC641SWP058B or later) Toolkit for HP-UX C Applications (IC641SWP054B or later) Toolkit for DEC VAX/VMS C Applications (IC641SWP053B or later) Toolkit for DEC Alpha AXP/VMS C/C++ Application (IC641SWP057B or later) Host Communication Drivers for Windows (qty.1: IC641SWP050D; qty.10 - IC641SWP051D) * This catalog number has CE Mark approval. Microsoft and Windows are registered trademarks of Microsoft Corporation. DEC, VAX, Alpha AXP, and VMS are trademarks of Digital Equipment Corporation.

2 2 Important Product Information: Factory LAN TCP/IP Ethernet Interface Product Documentation Operational Notes TCP/IP Ethernet Communications for the IC693 PLC User s Manual, GFK TCP/IP Ethernet Communications for the IC693 PLC Station Manager Manual, GFK System Prerequisites The Ethernet Interface requires Release 5.03 or later of the IC693 CPU (6.03 or later for the Model 351 CPU) and Release 6.01 or later of the IC641 programming software. For full operation including support for the TCP/IP Ethernet programming software, up to 16 server connections, and the ability to install the TCP/IP Ethernet Interface in expansion and remote racks, IC693 CPU version 6.5 is required. Power Supply Requirements The Ethernet Interface requires PLC Power Supply IC693PWR321 (Rev. K or later) or IC693PWR322. Power consumption of the Ethernet Interface module is +5VDC, plus power required by the AAUI transceiver. When calculating the total power consumption of the PLC rack, be sure to include the +5VDC required by the AAUI transceiver (typically 50 to 350mA) used with each Ethernet Interface; consult the transceiver documentation to obtain its power requirements. If used, also include the +5VDC power required by the RS-485-to-RS-232 Converter (typically 100mA). Configuration Through Serial Port Required Before Using IC641 TCP/IP Ethernet Programming Software Version 6.01 or later of the IC641 programming software (serial connection only) or version 6.50 or later of IC641 TCP/IP Ethernet programming software must be used to configure the Ethernet Interface prior to use. The Ethernet Interface cannot operate on the network until a valid IP address is configured. Two methods are available: 1. Perform the intial configuration using IC641 programming software through the PLC CPU serial port. 2. Connect a serial terminal to the station manager port (port1) of the Ethernet Interface. Then use the CHSOSW command to enter a temporary IP address. The interface can then be reached by the IC641 TCP/IP Ethernet programming software. Refer to TCP/IP Ethernet Communications Station Manager Manual, GFK-1186, for details. Note: This method of assigning an IP address is not recommended when the PLC CPU firmware is older than version 6.50 because an unconfigured Ethernet Interface is unable to operate for two minutes after the PLC is powered on.

3 Important Product Information: Factory LAN TCP/IP Ethernet Interface 3 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 addressing can disrupt network operation. Refer to TCP/IP Ethernet Communications User s Manual, GFK-1084 for important information on IP addressing. AAUI Cable Attachment Power to the PLC must be turned off whenever the transceiver cable (AAUI cable) is connected or disconnected at the Interface or at the transceiver. SQE Enable The Ethernet Interface requires that the SQE test signal be enabled on the transceiver connecting it to the Ethernet LAN. 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 via the HHP. Such attempts may result in erroneous Loss-of-Module faults in the PLC Fault Table or other unexpected behavior. Serial Load/Store of Register Table Causes the IC641 TCP/IP Ethernet Programmer To Lose Communication A load or store of the PLC Register (%R) table from the IC641 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 CPU 341 or CPU 351 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 and/or 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.

4 4 Important Product Information: Factory LAN TCP/IP Ethernet Interface IC641 TCP/IP Ethernet Programmer Briefly Loses Communication When Configuration Cleared or Stored Clearing or storing the PLC configuration causes the IC641 TCP/IP Ethernet programming software to display a flashing NO COMMUNICATIONS message for one or two seconds. PLC faults similar to those listed under the section, Serial Load/Store of Register Table Causes Ethernet Programmers To Lose Communication, above occur, and 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 IC641 TCP/IP Ethernet programming software, the communications loss occurs immediately after successful completion of the store. Attempts to store a configuration plus logic and/or reference tables in one operation can fail. However, storing a configuration separately from logic or reference tables will always succeed. 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 the IC641 TCP/IP Ethernet software 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 the section, 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 API 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/IO SCAN 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. Lost Ethernet Packets No Longer Cause PLC Faults Lost Ethernet packets do not cause either PLC faults with the text LAN data memory exhausted - check parms; resuming, or the corresponding log event (code = c, entry 2 = 103) in this release. They continue to increment MisdPack in TALLY L. However, this PLC fault is reported by this release when a buffer chaining error occurs while the interface is attempting to receive an excessively long, invalid Ethernet frame.

5 Important Product Information: Factory LAN TCP/IP Ethernet Interface 5 New Features Default System Parameter Change This version changes the Ethernet Interface s default system heap allocation parameters to minimize out-of-memory PLC faults. If a version 1.00 user has changed any of these parameters (balloc1, balloc2, balloc3, or balloc4) with the station manager CHPARM command, and the new defaults are different from the user values, a Module software corrupted, requesting reload fault will appear in the PLC fault table immediately after the Interface firmware is updated. This fault text is misleading; the actual meaning is that advanced user parameters have been changed. The Ethernet Interface does not request a reload. Note that loading firmware version 1.00 after updating to version 1.10 or later will set all system parameters back to version 1.00 defaults. The Module software corrupted, requesting reload fault will appear in the PLC fault table every time the Ethernet Interface is restarted. You can stop the fault from occurring only by changing the slot configuration data for the Ethernet Interface and then storing the new configuration to the PLC. Up To Sixteen Server Connections When the PLC CPU contains version 6.50 or later firmware, the Ethernet Interface provides up to sixteen simultaneous SRTP server connections for remote clients. Any combination of SRTP server and Channels API connections that totals sixteen or fewer is supported. Operation With Internal Backup Configuration When the PLC CPU contains version 6.50 or later firmware, clearing the slot configuration of the Ethernet Interface causes the interface to do the following: Close all established TCP connections, including IC641 TCP/IP Ethernet programming software. Disable the Channels API. Turn off the STAT LED. Post a LAN system software fault; resuming PLC fault with fault-specific data starting with Print the message Module config has been deleted; switching to internal backup to the local station manager port. When the Ethernet Interface operates in this state, the SRTP server is available, but the Channels API is disabled. The Ethernet Interface slot configuration is cleared when the IC641 programming software 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. Quick Restart With Duplicate Configuration This version performs a quick restart when a user stores a PLC configuration while the Ethernet Interface is operating with an internal backup that is identical to the new

6 6 Important Product Information: Factory LAN TCP/IP Ethernet Interface configuration data. See Operation With Internal Backup Configuration, above. This feature requires CPU version 6.50 or later firmware. The Ethernet Interface: Logs a restart event (event code = 1, entry 2 = 0, entry 3 = 0f). Turns the STAT LED on. Attempts to go on the network if it was previously off line. Enables the Channels API. Prints the message Module has been configured; switching to PLC configuration to the local station manager port. Then the Interface continues to operate. There is no interruption of communication with SRTP clients during this process. If the PLC CPU firmware is older than version 6.50, the Ethernet Interface always performs a full restart whenever a PLC configuration is stored while the interface is using an internal backup configuration. Station Manager PROG Command The new Station Manager PROG command displays the PLC program name.

7 Important Product Information: Factory LAN TCP/IP Ethernet Interface 7 Problems Fixed In This Release ID Code Á Description ÁÁ In the previous version, the Ethernet Interface could detect that it was using a duplicate IP ÁÁ Address only when another device sent an ARP message containing the interface s own ÁÁ address (usually within a few minutes of startup). In this version, the interface immediately validates its IP address upon startup. ÁÁ Á In the previous version, a blown AAUI fuse would generate an incorrect exception log event and would not properly set AAUI Fuse Blown (Status Bit 8) in the LAN Interface ÁÁ Status Word (LISW) bits. This has been corrected. ÁÁ Á In the previous version, a blown Serial Port #2 fuse would not be noted in either the Ethernet Interface exception log or the PLC Fault Table, and the Serial Port #2 Fuse Blown (Status Bit 7) in the LAN Interface Status Word (LISW) bits would not be set. This has been ÁÁ ÁÁ corrected , Á In the previous version, the PLC CPU would not communicate with an Ethernet Interface 29954, Á until the interface was configured by storing a PLC configuration from the IC642 programming software. This has been corrected , Á 29991, CPU firmware version 6.50 or later is required for correct operation Á ÁÁ 29750, In the previous version, the PLC CPU would not establish communication with, nor deliver configuration data to, an Ethernet Interface while the PLC was in the STOP/FAULT Á ÁÁ state. This has been corrected. ÁÁ CPU firmware version 6.50 or later is required for correct operation. ÁÁ The PLC CPU previously delayed up to two minutes to complete power up if the Ethernet ÁÁ Interface was in the Software Load state. This has been corrected. ÁÁ CPU firmware version 6.50 ot later is required for correct operation. ÁÁ In the previous version, valid IP addresses having values of the most significant octet in the Á range 208 through 223, inclusive, were erroneously rejected when specified as destination ÁÁ addresses in COMMREQs or the Station Manager PING command. This has been corrected. ÁÁ ÁÁ

8 8 Important Product Information: Factory LAN TCP/IP Ethernet Interface Restrictions and Significant Open Problems - IC693 Ethernet Interface ID Code ÁÁ Description ÁÁÁ 31220* When the software loader function of the Ethernet Interface is activated and the PC Loader program is used to change the serial port baud rates at both the PC and the interface, the Ethernet ÁÁÁ ÁÁÁ Interface does not return to the default baud rate when the user aborts the operation at the PC. To return to the default baud rate, it is necessary to restart the Ethernet Interface. See 31221, ÁÁÁ below. ÁÁ 31221* When the software loader function of the Ethernet Interface is active, pressing the restart button ÁÁÁ for any length of time has the same effect. If the software load progressed far enough to erase ÁÁÁ flash memory, a restart will always activate the software loader until software is loaded successfully. Otherwise, a restart will always return the Ethernet interface to operational state. ÁÁÁ To restart from the loader and then re-enter the software loader, it is necessary to press the restart button a second time and hold it down five seconds or longer. ÁÁÁ ÁÁÁ ÁÁ 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. ÁÁÁ ÁÁ The Hand-Held Programmer (HHP) cannot display or change the Ethernet Interface configuration. Attempting to read the Ethernet Interface configuration with the HHP, either before ÁÁÁ or after configuration by Logicmaster 90-30, can corrupt the PLC configuration already in the ÁÁÁ CPU. To recover, the PLC must be cleared and the PLC configuration stored again. ÁÁÁ ÁÁ When all 16 TCP connections are in use, attempting to issue a Read/Write Channel command that specifies a previously established channel number will fail unless the remote IP address ÁÁÁ in the new command is the same IP address previously assigned to that channel. The failure will return error code 9790 hexadecimal in the COMMREQ status word. When this ÁÁÁ error code is detected, an Abort Channel must be issued before the Read/Write Channel ÁÁÁ command can succeed. ÁÁÁ If PLC program size is more important than the speed of establishing new connections, an ÁÁÁ Abort Channel command should always be issued when a channel is no longer needed. ÁÁÁ This avoids the program logic needed to test the COMMREQ status word for error code ÁÁÁ ÁÁ 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. ÁÁÁ * New item for this release.

9 Important Product Information: Factory LAN TCP/IP Ethernet Interface 9 Restrictions and Significant Open Problems - IC693 Ethernet Interface (Continued) ÁÁ ÁÁ ÁÁÁÁÁ ID Code ÁÁÁÁÁ ÁÁ ÁÁ Description Á The Ethernet Interface may intermittently miss input characters at the Station Manager serial port when the module is very busy. Missed input characters are not echoed to the ÁÁ user. Under this condition, the user should enter characters slowly, waiting for each character to be echoed before entering the next. ÁÁ Á When all 16 TCP connections are in use (by any combination of SRTP server connections ÁÁ and client channels), the Ethernet Interface SRTP server cannot handle rapid reuse of an existing TCP connection. The remote client should close an existing connection before ÁÁ attempting to establish a new one. For example, Channels API clients should issue an ÁÁ Abort Channel command before the next Read/Write Channel command. ÁÁ To prevent resource exhaustion in the Ethernet Interface, it is required that no more than ÁÁ one COMM_REQ be active at a time for each channel. The PLC program should wait for completion (or timeout) of the previous COMMREQ before issuing a new COMMREQ for ÁÁ the same channel. ÁÁ Á The Ethernet Interface can behave unpredictably when all internal memory resources are exhausted. The interface will restart itself in this circumstance to prevent improper operation. ÁÁ ÁÁ 30386, There is no precise PLC Fault Table entry when the Ethernet Interface automatically restarts due to fatal system software error (such as Event 2, Entry 2 = 387) or due to a watch- ÁÁ ÁÁ dog timer expiration. The I/O Fault Table will record the unexpected loss and subsequent restart of the Ethernet Interface. ÁÁ Restrictions and Significant Open Problems - IC693 PLC CPU with Ethernet Interface ID Code Á Description ÁÁ The PLC CPU does not set the FT output of a COMM_REQ block when a non-existent ÁÁ PLC address is specified for the COMM_REQ Status (CRS) word. However, the Ethernet ÁÁ interface posts a Bad local application request; discarded request PLC fault. Always use a valid CRS address, since the PLC cannot detect this error condition. ÁÁ

10 10 Important Product Information: Factory LAN TCP/IP Ethernet Interface Restrictions and Significant Open Problems Software Loader Load Reason Zero After Software Load Aborted Aborting a software load with the restart button zeros the load reason (entry 5) in the station manager restart log event. Additional Restrictions With CPU Firmware Earlier Than Version 6.50 IC641 TCP/IP Ethernet Programming Software Not Supported IC641 TCP/IP Ethernet programming software requires both IC693 CPU version 6.5 and Ethernet Interface version 1.10 or later. The programming software may appear to connect with a PLC using older CPU firmware, but essential functions will not work correctly. Caution Do not attempt to use IC641 TCP/IP Ethernet programming software with CPU firmware earlier than version Unpredictable operation of both the PLC CPU and the programming software will occur. Single Incoming Network Connection to CPU PLC CPU firmware versions earlier than 6.50 can support only one incoming network connection through the Ethernet Interface at a time. The Ethernet Interface consequently supports only one incoming connection at a time when used with this CPU firmware. No Operation in Expansion or Remote Rack With CPU firmware versions earlier than 6.50, locate the Ethernet Interface in the main PLC rack only. The Ethernet Interface is not supported by this CPU firmware in an expansion or remote PLC rack. Incoming Network Connection May Be Refused After Restart After any restart, including power up, the Ethernet Interface is unable to accept incoming network connections for approximately 2.5 seconds after the LAN Interface OK bit of the LAN Interface Status Word is set. This occurs only with CPU firmware earlier than version Unconfigured Ethernet Interface Inoperative for Two Minutes After Restart With CPU firmware versions earlier than 6.50, an unconfigured Ethernet Interface waits for two minutes after each restart to receive valid configuration data from the PLC CPU.

11 Important Product Information: Factory LAN TCP/IP Ethernet Interface 11 The interface slowly flashes its Module OK LED and is not operational during this time. This behavior occurs when a new interface is powered on for the first time. It also occurs when the IC641 programming software clears the PLC configuration, or stores a new configuration with an empty slot or different module type at the location where the Ethernet Interface is installed. Changes and Additions to the User s Manual (GFK-1084) TCP/IPEthernet Communications for the IC693 PLC User s Manual, GFK-1084A, includes numerous corrections and additions. This new version was still in preparation at the time of product release. GFK-1084A will replace GFK-1084 as soon as it is available. Changes and Additions to the Station Manager Manual (GFK-1186) TCP/IPEthernet Communications for the IC693 PLC Station Manager Manual, GFK-1186A, includes numerous corrections and additions. This new version was still in preparation at the time of product release. GFK-1186A will replace GFK-1186 as soon as it is available. The information included below will be added to appendix B. Table B-2. Exception Log Event Codes - Continued Log Event ÁÁÁÁÁ Possible Cause and Resolution Code Event 12 This event is logged by the TCP layer. TCP events ÁÁÁÁÁ Entry 1 will always be zero. Entry 2 identifies the type of error: 1 through 12: no change from GFK LAN system - software fault; resuming Internal error: An attempt to bind a remote TCP/IP endpoint to a TCP connection failed because a connection was already open to that endpoint. Entry 3 is the endpoint identifier. 14 LAN PROM/software mismatch; running soft Sw util Internal error: A memory allocation error occurred while attempting to open a server connection requested by a remote node. Entry 3 is the endpoint identifier for the remote requester. 15 LAN PROM/software mismatch; running soft Sw util Internal error: An error occurred while attempting to send a reply when a server connection was requested by a remote node. Entry 3 is the endpoint identifier for the remote requester. Entry 4 is the TCP error code.

12 12 Important Product Information: Factory LAN TCP/IP Ethernet Interface Table B-2. Exception Log Event Codes - Continued Log Event ÁÁÁÁÁ Possible Cause and Resolution Code ÁÁÁÁÁ Event LAN PROM/software mismatch; running soft Sw util TCP events ÁÁÁÁÁ Internal error: The software attempted to deallocate data for a TCP (Continued) ÁÁÁÁÁ connection before the connection was closed. Entry 3 is the remote endpoint identifier for the connection. Entry 4 is the TCP state of the connection: 1 = CLOSED 2 = LISTEN 3 = SYN-SENT 4 = SYN-RECEIVED 5 = ESTABLISHED 6 = FIN-WAIT-1 7 = FIN-WAIT-2 8 = CLOSE-WAIT 9 = LAST-ACK 10 = CLOSING 11 = TIME-WAIT 17 Connection to remote node failed; resuming A packet was received with an inappropriate field value for the current state of the TCP connection. RST was sent to the remote endpoint. Entry 3 is the remote endpoint identifier. Entry 4 is the connec- tion state (See error code 16 above.). Entry 5 is the offending field value. 18 Connection to remote node failed; resuming A SYN packet was received when an ACK was expected. RST was sent to the remote endpoint. Entry 3 is the remote endpoint identifier. Entry 4 is the connection state (See error code 16 above.). Entry 5 is the offending field value. 19 Connection to remote node failed; resuming A remote node attempted to establish a new TCP connection when all 16 connections were already in use. RST was sent to the remote endpoint. Entry 3 is the remote endpoint identifier. Entry 4 is the connec- tion state and contains 2 (LISTEN).