IC693PCM300 | IC693PCM300N

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

product-image

IC693PCM300 | IC693PCM300N

  • Availability: In StockShips Today!
  • Units in Stock: Immediate Availablity: 6 Units!
  • Call for best Pricing+ 1 919 680 1773
  • Manufacturer: GE-IP
  • Description: 160 KB
  • Weight: 1 lbs :: ≈ 1 kgs
  • Warranty: 1 Years
  • Product Revisions Available:
  • Other Available Revisions of the IC693PCM300 : 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

August 8, 1996 GFK-0494W IMPORTANT PRODUCT INFORMATION READ THIS INFORMATION FIRST Product: Programmable Coprocessor Module, Version 4.03 Catalog Number Hardware Identification EPROM Label Location IC693PCM300N PC3A1 388-020P4.03 388-021L4.03 U34 U35 IC693PCM301L PC3A2 395-020L4.03 U36 IC693PCM311M PC3C1 395-020L4.03 U39 This is release 4.03 of the Programmable Coprocessor Module, PCM. It corrects several minor software errors in CCM communication. The PCM supports application programming in the MegaBasic and C languages. The module also communicates using the Communications Control Module (CCM) protocol. Field Update Kit Catalog Number Update Kit Number IC693PCM300N 44A731200-G09 IC693PCM301L 44A731222-G07 IC693PCM311M 44A731222-G07 Functional Compatibility PCM firmware version 4.03 is compatible with release 1.00 or later of PCM support software (TERMF), IC641SWP063A and IC641SWP023A, and release 2.04 or later of PCM development software (PCOP), IC641SWP061B and IC641SWP021A. To develop MegaBasic applications, you must use either TERMF or PCOP. PCM firmware version 4.03 is compatible with release 1.03 of the Model 331 CPU, IC693CPU331C, or later. However, it is strongly recommended that all release 1.0x users upgrade to a later CPU release. This upgrade is available at no charge. See Additional Restrictions When Using a Release 1.0x CPU 331 later in this document for a list of restrictions which apply only when a PCM is used with a release 1.05 or earlier CPU. There are no changes to these PCM publications: MegaBasic Programming Language Reference Manual and PCM Development Software (PCOP) User’s Manual for this release. The Programmable Coprocessor Module and Support Software User’s Manual has revised for this release. 2 Important Product Information GFK-0494W Special Operational Notes 1. MegaBasic Defaults to Task Seven: When MegaBasic is started from an R (RUN) command in a PCMEXEC.BAT file, and the command does not specify a task number, the PCM operating system assigns MegaBasic to task number 7. This behavior applies to PCMEXEC.BAT files created by the PCM operating system as well as files created by users, and is consistent with PCM firmware version 2.51 and all earlier releases. In PCM release 3.00, MegaBasic defaults to task 15. 2. PCM Serial Ports Are not Isolated: The two PCM serial ports are not isolated from module ground in either RS-232C or RS-422/RS-485 mode. Common-mode input signals must be limited to 12 volts or less for RS-422/RS-485 mode. An external RS-232C/RS-485 converter with common-mode isolation is recommended for serial data paths longer than 50 feet. 3. Configuration Restriction: An IC693 Programmable Coprocessor Module (PCM) may reside only in the main PLC rack. 4. PROM Change: PCM RAM, including the RAM Disk (the RAM: device), is automatically cleared on the first power-up after the PCM PROM is changed. If RAM disk files must be preserved, they must be stored to an attached personal computer (PC), using TERMF or PCOP, before upgrading the PCM firmware, and loaded to the PCM after the upgrade. 5. Power-up Delay: The first COMMREQ sent to a PCM after a power cycle needs to be delayed until the PCM has finished power-up initialization. See the Programmable Coprocessor Module and Support Software User’s Manual for example PLC programs which delay before sending CCM and MegaBasic COMMREQs. New Features and Functionality 1. Disabling Time Of Day Clock Synchronization: By default, the PCM synchronizes its time of day clock with the PLC CPU. Some PCM applications do not require the time of day clock and are sensitive to the impact these messages have on PLC sweep time or backplane message rates. Synchronization messages can be disabled from PCM applications in firmware version 4.03 and later. 2. Masking Serial Port Errors: Parity, framing and overrun errors in characters received at PCM serial ports can be masked in PCM firmware version 4.03 and later. These error types may be masked individually or in any combination. Because serial port errors cause MegaBasic program termination unless the program explicitly handles them, some users may prefer to mask these errors. Problems Resolved by this Upgrade 1. Backplane Message Timeout: In previous releases, the PCM would time out when the PLC CPU did not respond to backplane messages within five seconds. However, certain versions of CPU firmware could delay up to eight seconds to respond when busy. The PCM backplane message timeout is now ten seconds. 2. VTOS Time Slice Task Rotation may Stop: Previously, PCMs running several time slice tasks plus a priority based task, with task synchronization controlled by event flags, would occasionally stop the time slice rotation. This has been corrected. Important Product Information 3 GFK-0494W Restrictions and Significant Open Problems 1. Invalid MegaBasic COMMREQ May Not Cause PLC Fault: When a MegaBasic COMMREQ message is sent to the PCM and MegaBasic is not executing, the expected fault message may occasionally not appear in the PLC fault table. 2. CCM Timeout On Large Requests: CCM requests for 3000 bytes or more of data may occasionally abort with a serial timeout error (Error code 0102H). 3. Redirection of MegaBasic STDIN: When MegaBasic is run with STDIN redirected from a file on an attached PC and execution of the MegaBasic program terminates for any reason, MegaBasic is unable to read input characters from the PC file. Redirecting STDIN from a PCM RAM disk file works correctly. 4. MegaBasic Serial Data Rate: When both PCM serial ports are configured for a data rate higher than 9600 bps and a MegaBasic program transmits and receives characters on both ports at the same time, the PCM watchdog timer may expire, halting operation and turning off the OK LED. 5. CCM Data Rate: Recoverable CCM communication errors, such as dropped characters, may occur when CCM initiates commands on both ports simultaneously at data rates above 9600 bps. It is recommended that the data rate on either CCM port not exceed 9600 bps when using both ports as initiators. 6. WAIT Mode COMMREQ: Programming the COMMREQ function block for WAIT mode will degrade PLC sweep time and may halt the PLC CPU, turning off its OK LED. Do not use WAIT mode COMMREQs unless you have a compelling reason. If WAIT mode is used, it is absolutely essential that no COMMREQs are sent until the PCM is ready to receive them, and that the sum of the worst-case PLC sweep time (without sending a COMMREQ) plus the longer of the two COMMREQ timeout values is less than the PLC CPU watchdog timer setting. If two or more WAIT mode COMMREQs can be sent during the same PLC sweep, the total of the timeouts for all the COMMREQs must be considered. See the Programmable Coprocessor Module and Support Software User’s Manual. 7. Extra Fault: When a WAIT mode COMMREQ which specifies an invalid PCM TASK ID is executed, two Bad task id faults are posted to the PLC fault table. 8. NOWAIT I/O and CTRL-C: If a MegaBasic program performs NOWAIT_READ and NOWAIT_WRITE operations simultaneously on the same serial port, and the program is aborted with CTRL-C or a MegaBasic STOP statement, the PCM may hang if the program is restarted before the I/O operations complete. Additional Restrictions When Using a Release 1.0x Model 331 CPU 1. Multiple PCMs and/or ADCs: When two or more PCMs and/or Access 90 Display Coprocessor modules (ADCs) which do not have identical catalog numbers are installed in a PLC system, the PCM/ADC modules may not function normally, particularly after a short power cycle (warm boot). Loss of module faults may be posted to the PLC fault table. 2. MegaBasic Data Length: If a MegaBasic program attempts to write more than 512 bytes of data to the PLC CPU in a single request, the CPU watchdog timer will expire, turning off the CPU OK LED. 3. Lost COMMREQ: When two or more PCMs are present, a COMMREQ to either PCM may never complete. If a ladder program attempts to send WAIT mode COMMREQs, the CPU OK LED may go out after several minutes. Ladder programs should always use NOWAIT mode COMMREQs. To ensure that transactions are completed, a time limit should be established for each COMMREQ using a PLC timer function block. When a COMMREQ fails to complete before its timer expires, the program can send it again. 4. PLC Configuration Change: When an I/O configuration is stored to the PLC, or a Hand Held Programmer operation (Autoconfig or clear PLC) results in a change to PCM configuration data, PCMs must be reset before the new configuration takes effect. 4 Important Product Information GFK-0494W When the PCM configuration is changed to correct a Configuration mismatch PLC fault, a PLC power cycle is required before the PCM will function normally. Loss of module PLC faults for the PCM will occur between the time the new configuration is stored and the power cycle. Changes and Additions to the User’s Manual none

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