IC693PBM200 | IC693PBM200-EE

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


IC693PBM200 | IC693PBM200-EE

  • Availability: In StockShips Today!
  • Units in Stock: Immediate Availablity: 3 Units!
  • Call for best Pricing+ 1 919 680 1773
  • Manufacturer: GE-IP
  • Description: Siemens Profibus DP Master Module
  • Weight: 1 lbs :: ≈ 1 kgs
  • Warranty: 1 Years
  • Product Revisions Available:
  • Other Available Revisions of the IC693PBM200 : 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, -AA, -BC, -CC, -DD, -DE, -EE, -FE,

Product Manual Excerpt

GFK-2119F July 2011 IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: PROFIBUS DP Master for Series 90-30 PLCs IC693PBM200-EE with firmware version 1.34 This release of the Series 90-30 PROFIBUS Master module (IC693PBM200) firmware resolves the issues described on page 2. No new features were added. All previous firmware versions are replaced by this release. The new firmware is compatible with all previous firmware and hardware versions of the IC693PBM200. Hardware version –Ex reflects a label change. It does not affect features, performance or compatibility. Note: All users that issue COMMREQs to the PBM200 (PROFIBUS Master Module) must upgrade to firmware version 1.34. Upgrade Strategy This firmware release is available as field upgrade kit (part number 44A752220-G04). The field upgrade kit is available for download on the Support website, http://support.ge-ip.com/. Functional Compatibility Series 90-30 CPU374 Compatibility IC693PBM200 firmware version 1.16 or later is required to use this module with the IC693CPU374. HHP Support The Hand-Held Programmer (IC693PRG300) cannot be used to configure the IC693PBM200. Programmer Version Requirements The IC693PBM200 can be configured and programmed with Proficy™ Machine Edition Logic Developer PLC version 2.6 or later. No other programmers support configuration of this module. Network Configuration Limitations The number and type of slave devices and the amount of data they can exchange with the master is constrained by the various memory resources within the PLC. Three types of PLC memory resources may constrain network configuration: Total Hardware Configuration Size, Individual Module Configuration Size, and Data Transfer Size Per Module. Limitations on the Size of the Total Configuration The amount of memory available for the PROFIBUS configuration is affected by the CPU model being used, the version of the CPU firmware, the number and type of other modules in the configuration, the number and type of slave devices configured, and the amount and type of communication in progress with an external programmer or HMI devices. 2 Important Product Information GFK-2119F To check the current configuration size in Logic Developer PLC:  In Logic Developer-PLC, select ―Data View‖ for the hardware configuration (right click on hardware configuration and select Data View).  On the Summary Tab, add up the ―Data Size‖ fields of the components listed. Logic Developer-PLC will not allow hardware configurations to be created that exceed 65,535 bytes. The hardware configuration size is further limited by the size of the user hardware configuration space available in each CPU model as specified in the following table: User Memory Limitations CPU Model Maximum User Memory Available for Hardware Configuration (Bytes) 311/313 4,736 331 4,673 341 8,192 350 16,512 351 81,920* 352, 360, 363, 364, 374 245,760* *This memory must also contain the user program and the register, analog input, and analog output tables. Individual Module Configuration Limitations IC693 PLC CPU firmware releases 10.52 and earlier limit the size of the configuration for any one IC693PBM200 module due to internal system memory resources. Internal system memory is also used for communication and real-time update processes, so the amount available at any one time varies. If a configuration is stored to the PLC CPU that includes a configuration for an IC693PBM200 module that exceeds this limit and the module is physically present, a System Mismatch fault will be entered into the PLC fault table. No indication of the failure is given if the module is not physically present. Data Size Limitations The amount of data that can be exchanged between the PLC CPU and the IC693PBM200 module is limited to 3,972 bytes of input data (data going from the IC693PBM200 module to the PLC CPU) and 3,972 bytes of output data (data going from the PLC CPU to the IC693PBM200 module). Problems Resolved by this Revision of Product COMMREQ status word sometimes written to wrong location. In previous versions, the COMMREQ status word was sometimes written to the wrong location. In rare cases where COMMREQS were sent rapidly to the PBM200 module, the status word would be written to %R1—%R4, regardless of where the COMMREQ status word was programmed to be written. Firmware version 1.34 (IC693PBM200-DE) corrects this issue. All users that issue COMMREQs to the PROFIBUS Master Module must upgrade to 1.34 firmware. Important Product Information 3 GFK-2119F Operational Notes Rack/Slot Location Limitations The IC693PBM200 PROFIBUS Master Module may be operated only in the main rack of a Series 90-30 system; operation in expansion or remote racks is not supported. PLC Modes While the PLC is in either Run or Stop IOScan modes, the IC693PBM200 scans all configured slaves, sending outputs and reading inputs. When the PLC is not scanning I/O, the module continues to scan all I/O but enters Clear mode. In Clear mode, zeroed data is sent to all of the configured slaves. When the PLC again transitions to either Run or Stop IOScan mode, output transmission resumes using the most recentlysupplied output data. Network Scan Operation The Master module scans the PROFIBUS network as fast as possible, determined by the number of slaves and the amount of data per slave (and processing of COMMREQs, if any). The module’s scanning of the network is asynchronous with respect to the PLC’s logic sweep. PROFIBUS Identification Number Byte-Swapped in the Get Device Diagnostics COMMREQ The PROFIBUS Identification number for the device queried by the Get Device Diagnostics COMMREQ (command number 4) is byte-swapped. (The high-order byte is reported in the low-order byte of the specified PLC CPU memory location, and the low-order byte is reported in the high-order byte of the specified PLC CPU memory location.) Get Device Diagnostics COMMREQ Writes Non-zero Data to Extra Byte in PLC Memory if PROFIBUS Diagnostic Response has an Odd-byte Length If the diagnostic information returned from a PROFIBUS device by the Get Device Diagnostics COMMREQ (command number four) has an odd-byte length, and the response is written to word-oriented PLC CPU reference memory (%R, %AI, %AQ), there is always an extra byte left in the reference memory. This byte may contain non-zero data. ID of Faulted Slave not Reported in Slave Diagnostics Word if Fault Occurred while Master Turned Off, or Master/Slave Disconnected from Network If a slave encounters a new fault while the IC693PBM200 PROFIBUS Master is powered off or, while the master or slave is physically disconnected from the PROFIBUS network, the ID of that slave is not reported in the Slave Diagnostics Word after the master is powered on, or the master or slave is reconnected to the PROFIBUS network. A zero is reported instead. 4 Important Product Information GFK-2119F Migrating from the HE693PBM101 PROFIBUS Master Module The following issues should be considered when attempting to migrate applications that used the HE693PBM101 to the IC693PBM200:  The size of the slave status area for the IC693PBM200 is 128 points by default, compared to the 64 points used by the HE693PBM101. You may need to consider reducing the size of the slave status area to match the previous module’s usage.  When the PLC is not scanning its I/O, the IC693PBM200 enters Clear Mode. The HE693PBM101 does not.  In the HE693PBM101, the slave status bits are arranged by the order in which they appeared in the configuration. In the IC693PBM200, the slave status bits are arranged in order by bus address.  With the HE693PBM101, separate bits and data areas for each slave are used to detect and retrieve diagnostic data from the slaves. A word of optional input data in the IC693PBM200 informs the application program that a slave has diagnostic data. The data is then retrieved from the slave using a COMM_REQ function block. So the Diagnostic Flag area, the Diag_Data Slave Addr area, and the Diag Data area used by the HE693PBM101 are not present in the IC693PBM200.  The HE693PBM101 has one Module Revision input word. In the IC693PBM200, this input word has been combined with the new Slave Diag ID input word to form an optional 2-word input area.  The IC693PBM200 uses 16 fewer sync/freeze control bits and these bits have different semantics. The bits are now optional.  You may wish to disable fault reporting in the IC693PBM200 to match the behavior of the HE693PBM101. Installation in Hazardous Locations The following information is for products bearing the UL marking for Hazardous Locations:  WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS I, DIVISION 2.  WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE REPLACING OR WIRING MODULES.  WARNING - EXPLOSION HAZARD - DO NOT CONNECT OR DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS.  EQUIPMENT LABELED WITH REFERENCE TO CLASS I, GROUPS A, B, C & D, DIV. 2 HAZARDOUS LOCATIONS IS SUITABLE FOR USE IN CLASS I, DIVISION 2, GROUPS A, B, C, D OR NON-HAZARDOUS LOCATIONS ONLY.

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