Ic 695 Cpe 310
Ic 695 Cpe 310
Ic 695 Cpe 310
http://www.pdfsupply.com/automation/ge-fanuc/rx3i-pacsystem/IC695CPE310
Rx3i PacSystem
919-535-3180
[email protected]
PACSystems RX3i
IC695CPE310
GFK-2713B Central Processing Unit
April 2012
*
The PACSystems RX3i CPE310 can be used to perform
real time control of machines, processes, and material CPU OK I/O FORCE
handling systems. The CPU communicates with the RUN STATUS
programmer via the internal Ethernet port or a serial port. OUTPUTS ENABLED SYS FLT
It communicates with I/O and Intelligent Option modules COM 1 RDSD /
COM2
over a dual PCI/serial backplane.
RESET
NIU001+
Features
■ Contains 10 Mbytes of user memory and 10 Mbytes
of non-volatile flash user memory.
■ Battery-less retention of user memory.
■ Optional Energy Pack on system power loss powers COM 1
CPU long enough to write user memory to non-
volatile storage (NVS).
■ Configurable data and program memory.
■ Programming in Ladder Diagram, Structured Text,
Function Block Diagram, and C.
■ Supports auto-located Symbolic Variables that can
use any amount of user memory.
■ Reference table sizes include 32Kbits for discrete %I
ETHERNET
and %Q and up to 32Kwords each for analog %AI
USB-A RDSD !
and %AQ.
COM 2
■ Supports most Series 90-30 modules and expansion
racks. For supported I/O, Communications, Motion,
and Intelligent modules, see the PACSystems RX3i
Hardware and Installation Manual, GFK-2314.
■ Supports up to 512 program blocks. Maximum size for
a block is 128KB.
■ Two serial ports: RS-485 and RS-232.
■ Embedded Ethernet interface supports a maximum of Ordering Information
two programmer connections. Description Catalog Number
■ The rack-based Ethernet Interface module
RX3i 1.1 GHz CPU IC695CPE310
(IC695ETM001) supports a complete set of Ethernet
Standard Pwr Supplies
functionality. For details, see TCP/IP Ethernet
120/240VAC, 125VDC IC695PSA040
Communications, GFK-2224. IC695PSD040
24VDC
■ Time synchronization to SNTP Time Server on
Multifunctional Pwr Supplies
Ethernet network when used with a rack-based 120/240 VAC, 125 VDC
Ethernet module (IC695ETM001) version 5.0 or later. 24 VDC IC695PSA140
■ Ability to display serial number and date code in IC695PSD140
programmer Device Information Details. Rx3i Universal Backplane
■ Ability to transfer applications to and from USB 2.0 7 Slot IC695CHS007
12 Slot IC695CHS012
A-type compatible RDSDs (removable data storage
16 Slot IC695CHS016
devices).
Real Time Clock Battery IC690ACC001
■ Compliant with EU RoHS Directive 2002/95/EC
RX3i CPU Energy Pack IC695ACC400
using the following exemptions identified in the
Annex: 7(a), 7(c)-I and III, and 15. Energy Pack Cable IC695CBL001
Note: For Conformal Coat option, please consult the
factory for price and availability.
*
indicates a trademark of GE Intelligent Platforms, Inc. and/or
its affiliates. All other trademarks are the property of their
respective owners. All rights reserved.
2 IC695CPE310
GFK-2713B
Specifications
Memory retention The non-volatile storage (NVS) can retain data indefinitely without
loss of data integrity. When CPU power is restored, data stored in
NVS is transferred back to user memory and the NVS is cleared.
An optional IC695ACC400 Energy Pack powers the CPU long
enough to write its user memory contents to non-volatile storage
during a system power loss. For details on the Energy Pack, refer to
publication GFK-2724.
Program storage 10 Mbytes of non-volatile flash user memory.
Quick Start
For initial start-up and configuration of the CPE310, complete the following steps. For details on CPE310 operation, refer to
PACSystems CPU Reference Manual, GFK-2222R or later. If you are swapping a CPE310 with a CPU310 in an
existing system, also refer to “Migrating RX3i CPU310 Applications to a CPE310” on page 4.
1. Remove the pull-tab from the Real Time Clock (RTC) battery, located on the back of the CPE310.
2. Remove power from the RX3i rack and install the CPE310. The CPE310 can be installed in any pair of slots in the RX3i
Main rack, except the two highest-numbered slots.
3. Mount the Energy Pack on the left side of the module in slot 0 of the rack. Use cable IC695CBL001 to connect the Energy
Pack to the connector on the bottom of the CPE310.
4. Apply power to the rack.
Note: When the Energy Pack is powered up for the first time, or is in a system that has been powered down long
enough to completely discharge the Energy Pack, it may require a few seconds for it charge to its operating
level. The CPU’s STATUS LED will blink green during this time.
5. Connect the CPE310 to the Ethernet network.
6. Using Proficy Machine Edition (PME) software, configure a CPE310 in an RX3i target and assign a new IP address to the
embedded Ethernet interface.
The CPE310 has the same configuration parameters as the CPU310, with the following exceptions.
Universal Serial Bus: The RDSD (USB) port is enabled by default in the Controller and in the Proficy Machine
Edition hardware configuration.
If a configuration with Universal Serial Bus set to Disabled is stored to the CPE310, USB port operation can be
restored by storing a configuration with the port enabled or by performing a Clear All operation (power cycling the
CPU with the Energy Pack disconnected).
Note: The USB port is for transfer of application data only. It is not intended for permanent connection.
Modbus Address Space Mapping is not supported.
Ethernet configuration: The embedded Ethernet interface must be initially configured by downloading a CPE310
configuration to the RX3i from Machine Edition.
To configure the embedded Ethernet interface in Machine Edition, expand the CPU slot to display the Ethernet
daughterboard. The Settings tab for the embedded Ethernet module contains IP Address, Subnet Mask and
Gateway IP Address. Consult your network administrator for the proper values for these parameters.
Note: This release does not support the alternate methods of setting a temporary IP address: the Set Temporary IP
Address tool in PME, BOOTP, or the Station Manager CHSOSW command.
7. Go online with the target and download the configuration. You can use one of the following methods for the initial
connection to the CPE310:
Through the Ethernet port, using the factory-loaded IP address, 192.168.0.100. This address is intended only for
initial connection in order to complete the configuration and must be changed before connecting to the Ethernet
network. When you store a hardware configuration with a different IP address, the temporary IP address is lost; it is
not restored by a Clear operation.
Through the RS-232 COM1 serial port - This is a DCE (data communications equipment) port that allows a simple
straight-through cable to connect with a standard nine-pin AT-style RS-232 port.
Through the RS-485 COM2 serial port – Use SNP programming cable IC690ACC901
Through the Ethernet connection of an ETM001 in the same rack with a known IP address configuration
4 IC695CPE310
GFK-2713B
Release History
Catalog Number FW Version Comments
IC695CPE310-ABAC 7.13 Corrects issues with Logic Write to Flash (Service Request 57).
IC695CPE310-ABAB 7.11 Resolves the issues detailed in GFK-2713A.
IC695CPE310-AAAA 7.10 Initial release.
IC695CPE310 5
GFK-2713B
Upgrades
CPE310 can be upgraded to release 7.13 in the field by using the upgrade kit 82A1804-MS10-000-A2, which can be
downloaded from http://www.ge-ip.com/support.
Subject Description
Second programmer can While currently active in a Test and Edit session using Machine Edition on one PC,
change logic while in Test & Machine Edition running on another PC is not prevented from storing new logic to
Edit mode the RX3i.
Must have logic if powering-up If the application will configure the CPU to retrieve the contents of flash memory at
from flash power-up, be sure to include logic along with hardware configuration when saving to
flash memory.
Two loss of module faults for Occasionally, the hot removal of the Universal Analog Input Module (IC695ALG600)
Universal Analog Module results in two “Loss of I/O Module” faults instead of one.
Power up of Series 90-30 HSC As power is applied to a 90-30 High-Speed Counter, the "module ready" bit in the
module may take as long as 20 status bits returned each sweep from the module may not be set for as long as 20
seconds seconds after the first PLC sweep, even though there is no "loss of module"
indication. I/O data exchanged with the module is not meaningful until this bit is set
by the module. Refer to pages 4-3 to 4-5 of GFK-0293.
Informational fault at power up Intermittently during power-up, an Informational non-critical CPU software fault may
be generated with fault extra data of 01 91 01 D6. This fault will have no effect on
the normal operation of the RX3i. But, if the hardware watchdog timer expires after
this fault and before power has been cycled again, then the outputs of I/O modules
may hold their last state, rather than defaulting to zero.
Extended memory types for IO %R, %W and %M cannot be used as IO triggers.
triggers
SNP Update Datagram message If an Update Datagram message requests 6 or less bits or bytes of data, the RX3i
will return a Completion Ack without Text Buffer. The protocol specifies that the
returned data will be in the Completion Ack message, but it may not be present.
GBC30 may not resume In rare instances, a GBC30 in an expansion rack may not resume normal operation
operation after power cycle after a power cycle of either the expansion rack or the main rack.
Configuration of third-party Do not specify a length of 0 in the configuration of a third-party module. The module
modules will not work properly in the system.
Power supply status after CPU The RX3i will report a “Loss of or missing option module” fault for the IC695PSD140
firmware update power supply following an update of CPU firmware. Also, the slot will appear empty
in the programmer’s online status detail view. The power supply continues to
operate normally. Power cycle to restore normal status reporting.
Power supply status after Rarely, turning a power supply on or off may not result in an add or loss fault. Also,
power cycling the slot will appear empty in the programmer’s online status detail view. The power
supply continues to operate normally. To restore normal status reporting, cycle the
power.
Don’t use multiple targets In a system in which the hardware configuration is stored from one target and logic
is stored from a different target, powering-up from flash will not work. The observed
behavior is that, following a power up from flash, PME reports hardware
configuration and logic "not equal".
Missing “Loss of terminal The IC695ALG600/608/616 analog input modules do not produce a “Loss of terminal
block” fault block” fault when hardware configuration is stored or the module is hot-inserted, and
the terminal block is not locked into place.
Sequence Store Failure When downloading projects with very large hardware configuration or which use
large amounts of user memory, it is possible to encounter a “PLC Sequence Store
Failure” error when writing the project to flash. To avoid this error, either or both of
the following actions may be helpful:
1. Perform an explicit clear of flash prior to performing the write.
2. Increase the operation timeout used by ME prior to performing the write. This is
done by expanding the Additional Configuration in the Inspector window for the
target controller, and adjusting Request Timeout. The timeout may need to be
increased to as much as 60000 msec, depending on the amount of memory
used and the condition of the flash memory.
IC694MDL754: must configure Always configure 16 bits of module status when using this module. Configuring 0 bits
module status bits of module status will result in invalid data in the module’s ESCP status bits.
8 IC695CPE310
GFK-2713B
Subject Description
IC695ALG600 Lead Resistance A configuration store operation will fail if a channel is configured for 3-wire RTD and
Compensation setting Lead Resistance Compensation is set to Disabled. A Loss of Module fault will be
logged in the I/O Fault table at the end of the store operation. To recover the lost
module, the configuration must be changed to enable Lead Resistance
Compensation and module must be power cycled.
WinLoader may stop operating On computers running Windows 2000 and using some versions of Symantec
Antivirus protection, WinLoader will lock up if used in Advanced mode. To recover,
cycle the computer's power.
Logic and HWC not equal after If the Hardware Config from Target 1, with Logic/Configuration Power-up Source and
power cycle Data Source both set to “Always from Flash,” is stored in Flash, then Logic and
Hardware Config from Target 2, with Logic/Configuration Power-up Source both set
to “Always from RAM,” are stored to RAM and there is a good battery, then when
power is cycled the programmer may show that Logic and Hardware Config are not
equal. The remedy is to clear Flash and re-store the Logic and Hardware Config
from Target 2.
WinLoader does not detect PC WinLoader does not detect whether a PC's COM port is in use when attempting to
COM port in use when connect to a PACSystems CPU to perform a firmware upgrade. If the port is already
upgrading PACSystems CPU in use it displays the status "trying to connect" followed by "waiting for target." To
proceed with the upgrade, press the "abort" button and disconnect the other
application that is using the COM port.
WinLoader does not display WinLoader does not display an error message if it cannot connect to a PACSystems
error when it cannot connect CPU to perform a firmware upgrade. This occurs if the cable is physically not
serially with PACSystems CPU connected to the CPU or if the CPU's serial port is not configured for the same baud
as WinLoader. In this case Winloader displays the status "trying to connect" followed
by "waiting for target." To proceed with the upgrade, press the "abort" button and
correct the cable or baud rate setting.
SRTP connections remain open The Ethernet Interface does not terminate all open SRTP connections before
after IP address changed changing its IP address. Thus, once the local IP address has changed, the privileged
connection may not be available until the TCP keep-alive timeout has expired.
If quicker recovery of the SRTP connection is needed, modify the “wkal_idle”
Advanced User Parameter to reduce the TCP keep alive timer down to the desired
maximum time for holding open the broken connection. Refer to TCP/IP Ethernet
Communications for PACSystems, GFK-2224, for details.
REPP does not save results of The station manager REPP command does not retain the results of a PING that is
aborted PING aborted due to error. The PING results are reported when the PING is aborted, but
subsequent REPP commands give the results of the last successfully terminated
PING.
Multiple log events The Ethernet Interface sometimes generates multiple exception log events and
Controller Fault Table entries when a single error condition occurs. Under repetitive
error conditions, the exception log and/or Controller Fault Table can be completely
filled with repetitive error messages.
Clear of large hardware A Log event 08/20 may occur when very large hardware configurations are cleared
configurations may cause log and transfers are active on other Server connections. This log event can be safely
event 08/20 ignored.
PLC response timeout errors Under extremely heavy SRTP traffic conditions, the Ethernet Interface may log an
(8/08) in Ethernet exception log event in the Ethernet exception log (Event 8, Entry 2 = 08H) indicating an overload
under extremely heavy SRTP condition. This error terminates the SRTP connection. If this event appears, either
traffic the traffic load should be reduced, or the application should use an alternate
communications method to verify that critical data transfers were not lost due to the
overload.
SRTP channel transfers may When SRTP communications are interrupted by a power cycle, the Ethernet
take up to 20 seconds after interface may require up to 20 seconds to re-establish TCP connection used for
power cycle SRTP communications.
TCP connection may timeout If the TCP connection timeout is set higher than 10 minutes, the connection may
early if the timeout is set above time out before the configured value. The connection timeout is derived from three
10 minutes AUP parameters:
wkal_idle + (wkal_cnt + 1) * wkal_intvl
IC695CPE310 9
GFK-2713B
Subject Description
Station Manager PARM Although the parm v Station Manager command works correctly, the v subsystem
command help text is wrong code (SRTP server) is not shown as supported by the online help.
Blink code upon powerup In rare occasions a blink code of 9-1-1-15 may be reported upon power up.
To resume operation the unit must be power cycled again with the Energy Pack
disconnected.
All CPE LEDs blinking in unison In very rare occasions a CPE310 may power up erroneously indicating an over
at powerup temperature condition (all CPU status lights blinking on and off in unison) and fail to
go into run mode.
To resume operation the unit must be power cycled again (with or without the
Energy Pack connected.)
Subject Description
Undefined Symbols in In Release 5.00 or later, if an attempt is made to download a C block containing
C Blocks undefined symbols, the download will fail. Machine Edition will display the following
message in the Feedback Zone: Error 8097: Controller Error – Controller aborted the
request [0x05][0xFF]
Prior to Release 5.00, C blocks containing undefined symbols could be successfully
downloaded, but if they were executed the CPU would transition to Stop/Halt mode.
Length of serial I/O (Release 5.70 or later) The "Set Up Input Buffer Function" will always allocate a buffer
buffer containing 2097 bytes. This is one byte more than previous PACSystems releases.
LD-PLC operations Machine Edition LD-PLC no longer supports a function that connects to the PLC,
downloads, and 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.
IC695CPE310 11
GFK-2713B
Subject Description
Slot numbering, power 1. The A/C Power-Supply (IC695PSA040) for the RX3i is a doublewide module whose
supply placement, CPU connector is left justified as viewed when installed in a rack. It cannot be located in
placement and reference 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 doublewide RX3i CPUs are modules whose connector is right justified as viewed
when installed in a rack. They are referenced for configuration and by user logic
applications by the leftmost slot that it occupies. For example, if one of these
modules 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, a doublewide 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. Either DC power supply can be used (IC695PSD040 or
IC695PSD140). 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
User Logic Service Request #15 Location of CPU faults will not be the
(Read Last-Logged standard 0.1 location, but will reflect the slot
Fault Table Entry) the CPU is located in. User logic that
decodes fault table entries retrieved by
Service Request #20
these service requests may need updating.
(Read Fault Tables)
Communications COMM_REQs directed to the CPU (e.g.
Request those directed to the serial ports of the CPU)
(COMM_REQ) will need to be updated with the correct CPU
slot reference.
H/W CPU Slot location Slot location of the CPU must be updated in
Configurati the HW Configuration to reflect the CPU’s
on true location.
Fault Faults logged for the The location of faults logged for the CPU in
Tables CPU the fault table will not be the standard 0.1
(rack.slot) location, but will reflect the CPU’s
actual slot.
External Note: CPEs only provide the ability to communicate with a
Devices programmer. Additional protocols and communication with other
devices are not supported.
Duplicate station The default serial protocol for the RX3i is Modbus RTU. The default Station Address is 1.
address for Modbus will If the PLC is added to a multi-drop network, care must be taken that the PLC is configured
conflict with other with a unique Station Address. Nodes with duplicate Station Addresses on the same
nodes network will not work correctly.
12 IC695CPE310
GFK-2713B
Subject Description
Timer operation Care should be taken when timers (ONDTR, TMR, and OFDTR) are used in program
blocks that are NOT called every sweep. The timers accumulate time across calls to the
sub-block unless they are reset. This means that they function like timers operating in a
program with a much slower sweep than the timers in the main program block. For
program blocks that are inactive for large periods of time, the timers should be
programmed in such a manner as to account for this catch up feature.
Related to this are timers that are skipped because of the use of the JUMP instruction.
Timers that are skipped will NOT catch up and will therefore not accumulate time in the
same manner as if they were executed every sweep.
Constant sweep Constant Sweep time, when used, should be set at least 10 milliseconds greater than the
normal sweep time to avoid any over-sweep conditions when monitoring or performing on-
line changes with the programmer. Window completion faults will occur if the constant
sweep setting is not high enough.
Large number of A large number of COMM_REQs (typically greater than 8) sent to a given module in the
COMM_REQs sent to same sweep may cause Module Software faults to be logged in the Controller fault table.
module in one sweep The fault group is MOD_OTHR_SOFTWR (16t, 10h) and the error code is
causes faults COMMREQ_MB_FULL_START (2). When this occurs, the “FT” output of the function
block will also be set. To prevent this situation, COMM_REQs issued to a given module
should be spread across multiple sweeps so that only a limited number (typically 8 or less)
of COMM_REQs are sent to a given module in each sweep. In addition, the FT output
parameter should be checked for errors. If the FT output is set (meaning an error has
been detected), the COMM_REQ could be re-issued by the application logic.
C Block standard math In C Blocks, standard math functions (e.g. sqrt, pow, asin, acos) do not set errno to the
functions do not set errno correct value and do not return the correct value if an invalid input is provided.
Upgrading firmware Upgrading the CPU firmware with the WinLoader utility may fail when multiple IO
modules are in the main rack, due to the time it takes to power cycle the rack system.
If the upgrade process fails, move the CPU to a rack without IO modules and restart
the upgrade process.
Winloader initial connect baud rate is fixed at 19200 baud. Note that the firmware
download will occur at 115.2K baud by default.
Note that if you have hyperterm open on a port, and then try to use Winloader on the
same port, Winloader will often say “Waiting for Target” until the hyperterm session is
closed.
Hot swap Hot swap of CPUs is not supported in this release.
Serial port configuration With the following combination of circumstances, it is possible to render serial
COMM_REQs communications with the CPU impossible:
User configuration disables the Run/Stop switch
User configures the power up mode to Run or Last
Logic is stored in FLASH and user configures CPU to load from FLASH on power up
User application issues COMMREQs that set the protocol on both of the serial ports
to something that does not permit communications to the PME programmer.
Run Mode Store of EGD Rx3i rack-based Ethernet modules (IC695ETM001) must be running firmware version
6.00 or greater to utilize the Run Mode Store of EGD feature.
LAN must be tree, not ring The hub or switch connections in an Ethernet network must form a tree and not a ring;
otherwise duplication of packets and network overload may result. In this situation, the
RX3i Ethernet modules will continually reset.
Reporting of duplicate The PACSystems RX3i does not log an exception or a fault in the Controller Fault Table
IP address when it detects a duplicate IP address on the network.
SRTP connections remain The Ethernet Interface does not terminate all open SRTP connections before changing its
open after IP address IP address. Once the local IP address has changed, any existing open TCP connections
changed are unable to normally terminate. This can leave SRTP connections open until their
underlying TCP connections time out. If quicker recovery of the SRTP connection is
needed, modify the “wkal_idle” Advanced User Parameter to reduce the TCP keep alive
timer down to the desired maximum time for holding open the broken connection. Refer to
TCP/IP Ethernet Communications for PACSystems, GFK-2224, for details.
IC695CPE310 13
GFK-2713B
Subject Description
Lengthy CPE backplane Some exceptionally lengthy CPE backplane operations, such as MC_CamTableSelect,
operations Data Log, and Read Event Queue functions, will take longer to complete compared to
other RX3i CPU models, and may delay backplane operations to IC695 modules.
For example, when an MC_CamTableSelect function block is executed on the PMM335
module, the CPU’s acknowledgement of the PMM355 module interrupt may be delayed. In
this situation, you may see the following fault in the I/O Fault Table, even when the
interrupt has not been dropped: Error initiating an interrupt to the CPU.
Incorrect COMM_REQ The program name for PACSystems is always "LDPROG1". When another program name
status for invalid program is used in a COMM_REQ accessing %L memory, an Invalid Block Name (05D5) error is
name generated.
FANUC I/O Master and Scan sets on the master do not work properly for the first operation of the scan set after
Slave operation 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 RX3i CPUs or Series 90-30 CPU374s.
Repeated power up/down cycles of an expansion rack containing FANUC I/O slaves may
result in failure of the slaves’ operation, with the RDY LED off.
Lost count at power up for The serial IO Processor (IC693APU305) will lose the first count after every power up or
Serial IO Processor every time the module receives a configuration.
COMM_REQ status words In previous releases, the CPU allowed configuration of COMMREQ Status Words in bit
declared in bit memory memory types on a non-byte-aligned boundary. Even though the given reference was not
types must be byte-aligned byte-aligned, the firmware would adjust it the next-lowest byte boundary before updating
status bits, overwriting the bits between the alignment boundary and specified location. To
ensure that the application operates as expected, release 3.50 requires configuration of
COMMREQ Status Words in bit memory types to be byte-aligned. For example if the user
specified status bit location of %I3, the CPU aligns the status bit location at %I1. Release
3.50 firmware requires the user to specify the appropriate aligned address (%I1) to ensure
that the utilized location is appropriate for their application. Note that the actual reference
location utilized is not changed, but now is explicitly stated for the user.
STOP and RUN mode The PACSystems CPU receives requests to change between stop and run mode from
transition priority many different sources. These include (but are not limited to) Proficy Machine Edition,
HMIs, the user application, and the RUN/STOP switch. Since there are many potential
sources for a mode change request, it is possible to receive a new mode change request
while another is already in progress. When this occurs, the CPU evaluates the priority of
the new mode change request with the mode change that is in progress. If the new mode
change request has an equal or higher priority than the one already in progress, the CPU
transitions to the new mode instead of the one in progress. If, however, the new mode
change request has a lower priority than the one in progress, the new mode request is
discarded and the CPU completes the mode change that is in progress. The sweep mode
priorities are (listed from highest to lowest priority) STOP HALT, STOP FAULT, STOP,
and RUN. (Note: The IO ENABLED/DISABLED state is not part of the mode priority
evaluation.)
For example, a CPU is in RUN IO ENABLED mode and a SVC_REQ 13 function block is
executed to place the CPU into STOP IO DISABLED mode. Before the transition to STOP
IO DISABLED is completed, the RUN/STOP switch is changed from RUN IO ENABLED to
RUN IO DISABLED. In this case, the CPU ignores the new request from the RUN/STOP
switch to go to RUN IO DISABLED mode because it is already processing a request to go
to STOP IO DISABLED mode and STOP mode has a higher priority than RUN mode.
Nuisance faults sometimes If a power supply is missing or has some fault that makes it appear to be missing, the
logged for missing power CPU may improperly report (upon download of configuration) more than one fault. Such
supply additional faults may be safely ignored and will not occur in a properly configured rack
(with no mismatches or missing modules),
Uploaded controller Controller supplemental files uploaded from the CPU are time stamped as 8/1/1980
supplemental files lose 12:08AM regardless of PC or PLC time.
date and time
14 IC695CPE310
GFK-2713B
Subject Description
AUP parameter restrictions The Advanced User Parameter “wsnd_buf” should not be changed by the user.
Changing the value of this parameter may cause the Ethernet Interface to drop
its connection and the LAN LED to turn off.
When explicitly configuring speed or duplex mode for a PACSystems RX3i port
using Advanced User Parameters (AUP), do not request a store to flash as a
part of the download when communicating over the CPE's embedded Ethernet
port. In this situation you first must store to the RX3i and then initiate a separate
request to write to flash.
Changing IP address of Storing a hardware configuration with a new IP address to the RX3i while connected
Ethernet interface while via Ethernet will succeed, then immediately disconnect because the RX3i is now
connected using a different IP address than the Programmer. You must enter a new IP address
in the Target Properties in the Machine Edition Inspector window before
reconnecting.
Proper IP addressing is always The PACSystems Ethernet Interface must be configured with the correct IP Address
essential for proper operation in a TCP/IP Ethernet network. Use of incorrect IP addresses
can disrupt network operation for the PACSystems and other nodes on the network.
Refer to TCP/IP Ethernet Communications for PACSystems, GFK-2224 for
important information on IP addressing. When storing a new HW configuration to the
RX3i, be sure that the HW configuration contains the proper Ethernet addressing
data (IP Address, Subnet Mask, and Gateway IP Address) for the RX3i.
Note: Machine Edition programming software maintains the target IP address
(used to connect the programmer to the target) independent of the contents
of the HW Configuration for that target). The target IP address is set in the
Target Properties in the Machine Edition Inspector window. Storing a HW
Configuration whose Ethernet addressing data contains an IP Address that
is different from the RX3i target IP address will change the IP address used
by the target RX3i as soon as the Store operation is completed; this will
break the Programmer connection. Before attempting to reconnect the
Programmer, you must change the target IP address in the Target
Properties in the Machine Edition Inspector window to use the new IP
address. To regain communication at the former IP address, use the
manual corrective action described above.
Storing a HW Configuration containing incorrect Ethernet addressing data to the
PACSystems RX3i will result in loss of the Programmer connection and will require
manual corrective action as described above.
16 IC695CPE310
GFK-2713B
Subject Description
10Base-T / 100Base-TX auto- The PACSystems RX3i CPU with embedded Ethernet provides a direct connection
negotiating full-duplex Ethernet to one 10Base-T /100Base-TX CAT5 (twisted pair) Ethernet LAN cable from one
ports network port. By comparison, Rx3i peripheral Ethernet modules (IC695ETM001)
provide direct connection to one or two 10Base-T /100Base-TX CAT5 (twisted pair)
Ethernet LAN cables from two network ports. In either case, the Ethernet-enabled
device has only one IP address that may be used by one or two ports. Cables may
be shielded or unshielded.
Caution
The hub or switch connections in an Ethernet network must form a tree and
not a ring; otherwise duplication of packets and network overload may result.
Caution
The IEEE 802.3 standard strongly discourages the manual configuration of
duplex mode for a port (as would be possible using Advanced User
Parameters). Before manually configuring duplex mode for a PACSystems
RX3i port using Advanced User Parameters (AUP), be sure that you know the
characteristics of the link partner and are aware of the consequences of your
selection. Setting both the speed and duplex AUPs on a PACSystems RX3i
port will disable the port’s auto-negotiation function. If its link partner is not
similarly manually configured, this can result in the link partner concluding an
incorrect duplex mode. In the words of the IEEE standard: “Connecting
incompatible DTE/MAU combinations such as full duplex mode DTE to a half-
duplex mode MAU, or a full-duplex station (DTE or MAU) to a repeater or other
half duplex network, can lead to severe network performance degradation,
increased collisions, late collisions, CRC errors, and undetected data
corruption.”
Use AUPs to specify End-users can utilize an AUP file to set their own non-default password for Station
non-default Station Manager Manager operations. GE Intelligent Platforms recommends that our customers use
password this functionality in their applications.
IC695CPE310 17
GFK-2713B
Power up characteristics
The Conditional Power-up From Flash feature works the same as in previous Rx3i CPUs: that is if the configuration is
configured for “Conditional – Flash” and the Energy Pack is disconnected or has failed, the contents of flash will be loaded into
RAM at power up. The CPU’s logic and configuration source and operating mode at power-up are in accordance with the
tables on pages 4-14 and 4-15 of GFK-2222, where “memory not preserved” means that the Energy Pack is not connected or
not working. The contents of those tables apply as follows:
All entries in the “Logic/Configuration Source and CPU Operating Mode at power-up” table which address
“Logic/Configuration Power-up Source in User Memory” apply to Logic/Configuration as if there were a battery.
The condition of “Memory not preserved (i.e., no battery or memory corrupted)” is created on a CPE310 by power
cycle with the Energy Pack removed.
The condition of “No configuration in User Memory, memory preserved” is created on a CPE310 by clearing
configuration (or never downloading configuration), and then cycling power with the Energy Pack connected.
The conditions for Logic/Configuration source of “Always Flash,” “Conditional Flash” and “Always RAM” are created
by setting the appropriate configuration setting in the CPE310 and cycling power with the Energy Pack connected.
User memory is preserved only if the Energy Pack is connected (and charged) at power-down. Similarly, user
memory is preserved only if the Energy Pack is present at power-up.
The user memory is preserved on a CPE310 by an Energy Pack connection at the instant of power-down and the
instant of power-up. Removing or reconnecting the Energy Pack while the CPE310 is not powered has no effect on
the preservation of user memory.
WARNING - EXPLOSION HAZARD - USB PORT IS ONLY FOR USE IN NONHAZARDOUS LOCATIONS, DO NOT
USE UNLESS AREA IS KNOWN TO BE NON-HAZARDOUS.