IC693BEM321 | IC693BEM321B

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


IC693BEM321 | IC693BEM321B

  • Availability: In StockShips Today!
  • Units in Stock: Immediate Availablity: 4 Units!
  • Call for best Pricing+ 1 919 680 1773
  • Manufacturer: GE-IP
  • Description: GE Fanuc Series 90-30 I/O Master Link IC693BEM
  • Weight: 1 lbs :: ≈ 1 kgs
  • Warranty: 1 Years
  • Product Revisions Available:
  • Other Available Revisions of the IC693BEM321 : 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,

Product Manual Excerpt

Important Product Information 3 GFK-2329C Problems Resolved by this Version The following problems are resolved in version 2.80 of the firmware. Subject Description Firmware Update Attempt Sent to Incorrect Module If an attempt to update Ethernet module firmware is inadvertently directed to a slot containing a different type of module (for example, an analog module) WinLoader will fail with the error Target is unable to enter boot mode. Serial comm error: Request timed out. After this error occurs, the CPU will be in an invalid state and should be power cycled. Service Request 24 results in different fault messages When Service Request 24 is used to reset a module in the RX3i system, a Reset of I/O Module fault appears in the PLC fault table. For RX7i systems, two faults appear: Reset of I/O Module and Loss of I/O Module. CPU Config Mismatch & Loss of Ethernet module Powering-up with a hardware configuration that has a CPU mismatch (e.g. a CPU is configured in a different slot than it occupies), will cause faults from and a loss of communication with all Ethernet modules in the system. In version 2.80, the configuration mismatch will no longer result in the loss of the Ethernet module (faults will still occur). CPU loses backplane comm RX3i CPU loses access to the backplane when an Ethernet module is configured for s slot that is occupied by the CPU. HCT Mem List feature will not work with PACSystems CPUs (with older versions of HCT) In previous releases of PACSystems CPU, the HCT Mem List feature does not work when using older versions of HCT. COMMREQs to DSMs The CPU goes STOP/HALT when it attempts to send certain COMMREQs to DSM modules. The COMMREQs that fail are COMMREQs that are supported only by the DSM module. Multiple DSMs may fail to receive Motion Programs If multiple DSMs are used in multiple expansion racks, all of them requiring motion programs, then very intermittently at power-up the PLC software watchdog may expire during the first few sweeps and/or some of the DSM modules may fail to receive their motion program files and consequently not function as programmed. The probability of this occurrence is increased with the number of DSMs and if some or all of them are in 90-30 remote racks. The following problem is resolved in Revision C of the Hardware. Subject Description At high temperatures, some CPUs don’t power up properly Some CPUs may not complete powering up when operating at high temp (above 52°C with hot neighbors, higher without hot neighbors). If the user leaves the CPU powered down for a few minutes, the CPU will cool and power up properly. Although the hardware fix to resolve this behavior was included in the last revision, it was not implemented in production. This revision bumps the hardware version (from B to C) to allow tracking of units that have been shipped without this fix. New CPU Features and Enhancements The RX3i CPU now provides support for two new modules:  Universal Analog Input Module (IC695ALG600)  Motion Controller Module (IC694DSM324) 4 Important Product Information GFK-2329C CPU Restrictions and Open Issues Subject Description Ethernet Disconnect During Word for Word Change If the Ethernet connection is broken during a word-for-word change, the programmer may not allow a subsequent word-for-word change after reconnecting due to the fact that it thinks another programmer is currently attached. If this occurs, you should go offline and then back online again. Simultaneous Clears, Loads and Stores Not Supported Currently, PACSystems CPUs do not support multiple programmers changing CPU contents at the same time. The programming software may generate an error during the operation. Simultaneous loads from a single PLC are allowed. Power Cycle During Online Edit If the user stores a folder to flash that is configured to power up from flash and then subsequently power is cycled in the middle of a Online Edit session, the programmer will still indicate that the Online Edit session is in progress after the power cycle. The user should cancel the Online Edit session to continue. Power Cycle During Write to Flash If the CPU is power cycled during the process of writing to flash, and is configured to power up from flash, a fault will be generated on power up. Hardware Configuration Not Equal After Changing Target Name If the user stores to flash a hardware configuration that indicates Logic/Config Power up Source is set to Always Flash or Conditional Flash and then subsequently changes the name of the target in the programming software, the hardware configuration will go Not Equal and will not Verify as equal. PLC and IO Fault Tables May Need to be Cleared Twice to Clear Faulted State Both PLC and IO fault tables may need to be cleared to take the CPU out of Stop/Fault mode. If one of the tables contains a recurring fault, the order in which the tables is cleared may be significant. If the CPU is still in Stop/Fault mode after both tables are cleared, try clearing the fault tables again. Setting Force On/Off by Storing Initial Value Once a force on or force off has been stored to the PLC, the user cannot switch from force on to force off or vice-versa directly by downloading initial values. The user can turn off the force by doing a download, and then change the force on or off by another download. Storing Large Numbers of Blocks to Flash Currently, storing logic with approximately 200 blocks or more to flash may fail, due to the programmer timing out. Number of Active Programs Returned as Zero The SNP request Return Controller Type and ID currently returns the number of active programs as zero. Serial I/O Failure at 115K During Heavy Interrupt Load Rare data corruption errors have been seen on serial communications when running at 115K under heavy interrupt load on the PLC. Under heavy load applications, users should restrict serial communications to 57K or lower. RAND_MAX and rand() function incompatible In the C Toolkit, the RAND_MAX system variable is defined as a 32-bit integer. However, the rand() function returns a 16-bit integer. By definition, rand() should return an integer between 0 and RAND_MAX. Incorrect COMMREQ Status For Invalid Program Name The program name for PACSystems is always LDPROG1. When another program name is used in a COMMREQ accessing %L memory, an Invalid Block Name (05D5) error is generated. SNP ID not always provided Unlike the Series 90-30, the RX3i CPU’s SNP ID will not appear in the Machine Edition programmer Show Status display. Service Request 11 will always return zeros. Second programmer can change logic while in Test & Edit mode While currently active in a Test and Edit session using Machine Edition on one PC, Machine Edition running on another PC is not prevented from storing new logic to the PLC. FANUC I/O Master and Slave operation Scan sets on the master do not work properly for the first operation of the scan set after entering RUN mode. They do work properly for subsequent scans. After downloading a new hardware configuration and logic, a power cycle may be required to resume FANUC I/O operation. Use PLCs of similar performance in FANUC I/O networks. If a master or slave is located in an RX3i system, the other PLCs should be RX3is or Series 90-30 CPU374s. Important Product Information 5 GFK-2329C Subject Description Must Have Logic If Powering- Up From Flash If the application will configure the CPU to retrieve the contents of flash memory at power-up, be sure to include logic along with hardware configuration when saving to flash memory. Avoid Ethernet module resets Resetting the Ethernet module, either by Service Request 24 or by the restart pushbutton, will cause some of the CPU’s internal memory to be consumed if EGD is configured. The problem becomes more pronounced with larger EGD configurations. Power-cycling the system will recover the internal memory. Configuration mismatch with unsupported module causes PLC sequence store failure If you attempt to store a hardware configuration to the CPU that has a module configured for a slot that physically contains an unsupported module, the store will fail with a sequence store failure. Two loss of module faults for Universal Analog Module Occasionally, the hot removal of the Universal Analog Input Module (IC695ALG600) results in two Loss of I/O Module faults instead of one. CPU logs incorrect fault for Overtemp When the CPU detects an overtemp condition, the overtemp fault causes the CPU to go to STOP/HALT instead of STOP/FAULT. Addition of Terminal Block fault sometimes missing or in wrong order If you hot insert the high-density terminal block after hot inserting the Universal Analog Input Module (IC695ALG600), sometimes the Addition of Terminal Bock fault is missing, or occurs before the Addition of Module fault in the fault table. 6 Important Product Information GFK-2329C CPU Operational Notes Subject Description Slot numbering, power supply placement, CPU placement and reference 1. The A/C Power-Supply (IC695PSA040) for the RX3i is a doublewide module whose connector is left justified as viewed when installed in a rack. It cannot be located in Slot 11 of a 12-slot rack nor Slot 15 of a 16-slot rack. No latch mechanism is provided for the last (right-most) slot in a rack, therefore it is not possible to place the power-supply in the second to last slot. 2. The RX3i CPU (IC695CPU310) is a doublewide module whose connector is right justified as viewed when installed in a rack. It is referenced for configuration and by user logic applications by the leftmost slot that it occupies. For example, if the RX3i CPU has its physical connector inserted in to slot 4, which means it occupies slots 3 and 4, the CPU is referenced as being located in slot 3. The referenced location of the CPU is not determined by what slot the physical connector is located in, but rather by the left most slot occupied by the entire module. 3. Due to item #2 above, the RX3i CPU may be located in Slot 0 of a rack (physical connector in Slot 1). In addition the CPU cannot be located in Slot 11 of a 12-slot rack nor Slot 15 of a 16-slot rack, since doing so would require the physical connector to be located in the slot reserved for an expansion module. 4. When migrating a Series 90-30 CPU system to a PACSystems RX3i CPU, be aware that to maintain the Slot 1 location of the CPU, only a singlewide power-supply may be used in Slot 0. Currently, the only available singlewide power-supply is a DC power-supply (IC695PSD040). Therefore, if the application using an existing Series 90-30 system must maintain a Slot 1 CPU and uses an AC power-supply, the RX3i system must have the RX3i AC power-supply located in a slot to the right of the RX3i CPU in Slot 1. 5. In deciding to place the CPU in slots other than Slot 1, the user should be aware of the possible application migration issues that could arise. The following lists the areas that could be affected when migrating an application from one CPU slot to another. Item Affected How Affected Service Request #15 (Read Last-Logged Fault Table Entry) Service Request #20 (Read Fault Tables) Location of CPU faults will not be the standard 0.1 location, but will reflect the slot the CPU is located in. User logic that decodes fault table entries retrieved by these service requests may need updating. User Logic Communications Request (COMMREQ) COMMREQs directed to the CPU (e.g. those directed to the serial ports of the CPU) will need to be updated with the correct CPU slot reference. H/W Configuration CPU Slot location Slot location of the CPU must be updated in the HW Configuration to reflect the CPU’s true location. Fault Tables Faults logged for the CPU The location of faults logged for the CPU in the fault table will not be the standard 0.1 (rack.slot) location, but will reflect the CPU’s actual slot. Series 90 PLCs Remote Series 90 PLCs that use SRTP Channels COMMREQs expect the CPU to be in slot 1. In order to support communications with Series 90 SRTP clients such as Series 90 PLCs using SRTP Channels, the RX3i internally redirects incoming SRTP requests destined for {rack 0, slot 1} to {rack 0, slot 2}, provided that the CPU is located in rack 0 slot 2 (and the remote client has not issued an SRTP Destination service on the connection to discover the rack and slot of the CPU). This special redirection permits Series 90-30 applications that expect the power supply to be located leftmost and the CPU to be located to the right of the power supply to function. Attempts to establish channels with CPUs in slots other than 1 or 2 will fail if initiated from Series 90 PLCs. HMI and External Communication Devices All external communication devices that interact with the CPU should be checked for compatibility with CPU slot locations other than slot 1. Problems may arise with, but are not limited to, initial connection sequences and fault reporting. Machine Edition View customers should select GE SRTP as their communications driver – it can communicate with a CPU in any slot. Host Communications Toolkit (HCT) External Devices Applications that utilize the Host Communications Toolkit may require updated drivers. Important Product Information 7 GFK-2329C Subject Description Important Installation Instructions for Battery A battery is shipped with the CPU unit behind the battery door on the faceplate but it is not connected. Do not connect the battery until the CPU is installed in the rack and the rack powered on. The battery may then be attached to either of the two terminals in the battery compartment. Once that is done, the CPU may be powered down and normal battery back up operation will begin. To save battery life, do not connect the battery for the first time until the CPU is powered up. LD-PLC Operations Machine Edition LD-PLC no longer supports a function that connects to the PLC, downloads, then disconnects from the PLC. The connect and download functions are now separate. To perform a download to the PLC, you must first connect to the PLC. Logic Executed in Row Major Instead of Column Major Logic execution in PACSystems RX3i is performed in row major order (similar to the Series 90-30). This is different from the Series 90-70, which executes in column major order. This means that some complicated rungs may execute slightly differently on PACSystems RX3i and Series 90-70. For specific examples, see the programming software on-line help. NaN Handled Differently Than in 90-30 The PACSystems RX3i CPU may return slightly different values for Not A Number as compared to Series 90-30 CPUs. In these exception cases (e.g., 0.0/0.0), power flow out of the function block is identical to Series 90-30 operation and the computed value is still Not A Number. PID Algorithm Improved The PID algorithm used in PACSystems has been improved and therefore PID will function slightly differently on PACSystems RX3i than on the Series 90-30. The differences are that the elapsed time is computed in 100 μS instead of 10 mS units. This smooths the output characteristic, eliminating periodic adjustments that occurred when the remainder accumulated to 10mS. Also, previous non-linear behavior when the integral gain is changed from some value to 1 repeat/second was eliminated. Some Service Requests different from 90-30 or no longer supported Service Requests 6, 15, and 23 have slightly different parameters. Refer to GFK-2222. PACSystems PLCs support Service Request 26/30 functionality via fault locating references. The first word of a Service Request command block is required to contain a zero. On the Series 90- 30, this value was ignored. Please note: the parameter to the service request must be the address of the location containing the zero.

Warning: include_once(/js/tracking.php): failed to open stream: No such file or directory in /var/www/series/revision.php on line 248 Warning: include_once(): Failed opening '/js/tracking.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/series/revision.php on line 248