GFK-2942H_IC695CPE330

GFK-2942H_IC695CPE330
Important Product Information
PACSystems* RX3i
IC695CPE330-ABAJ
IC695CPE330CA-ABAJ
1GHz 64MB CPU w/Ethernet
GFK-2942H
July 2016
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
RX3i 1GHz 64MB CPU w/Ethernet
The PACSystems* RX3i RX3i CPE330 is a richly
featured programmable controller CPU equipped
with a 1GHz dual-core microprocessor, 64Mbytes of
built-in program memory and two independent
high-speed Ethernet interfaces. It is ideally suited
for multi-tier communications and for
synchronizing large amounts of data. Its metal
housing provides superior noise immunity.
The CPE330 is programmed and configured over
Ethernet via GE’s Proficy™ Machine Edition (PME)
software. It resides in the RX3i main rack and
supports all RX3i I/O and Intelligent Option modules,
up to 32K I/O points.
CPU Features:
 RX3i Hot Standby Redundancy CPU with support
for PROFINET I/O using IC695PNC001 PROFINET
Controllers.
 RX3i Hot Standby Redundancy with Ethernet
(EGD) & Genius I/O
 Simplex PROFINET I/O Controller with support for
up to 32 I/O devices and update rates of 1 –
512ms. I/O device update rates of 8ms and faster
are possible with 16 or fewer devices. When there
are more than 16 devices configured, update
rates of 16ms and higher are available.
 Supports two independent 10/100/1000 Ethernet
LANs. LAN1 attaches via the dedicated (upper) RJ45 connector shown in Error! Reference source
not found.. LAN2 attaches via the lower pair of
internally-switched RJ-45 connectors.
 Achilles Level 2 Communications Certification 1
 The embedded Ethernet interface is supported by a dedicated microprocessor core. This dedicated processing
capability permits the CPU to support these two LANs with:
o up to 48 simultaneous SRTP Server connections,
o up to 16 simultaneous Modbus®/TCP Server connections.
o 32 clients are permitted; each may be SRTP or Modbus/SRTP.
o OPC UA Server with support for up to 5 concurrent sessions with up to 10 concurrent variable subscriptions and
up to 12,500 variables;
o up to 255 simultaneous Class 1 Ethernet Global Data (EGD) exchanges;
o two independent Redundant IP addresses, one for each of the embedded Ethernet LANs.
 Optional Energy Pack, IC695ACC402, allows CPE330 to instantly save user memory to non-volatile storage in the
event of loss of power.
 Ability to transfer user programs and/or data to and from USB 2.0 A type Removable Data Storage Devices (RDSDs)
Indicates a trademark of General Electric Company and/or its subsidiaries. All other trademarks are the property of their respective
owners. Copyright © 2015 - 2016 General Electric Company. All Rights Reserved.
1 Achilles Level 2 Communication Certification available in CPE330 R8.80.
*
2
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
 HART Pass Through allows the CPE330 to communicate HART asset management data between HART-capable I/O
modules and PC-based asset management tools. (Requires additional HART-compatible products.)
 Supports the Remote Get HART Device Information COMMREQ, which allows the user application to read information
from a HART device connected to an RX3i Analog module in an IC695PNS001 RX3i PROFINET Scanner. A UDFB that
automates the COMMREQ control logic is available for download from the GE support website. (Refer to New Features
and Enhancements for additional information.)
 User may program in Ladder Diagram, Structured Text, Function Block Diagram, or C. Refer to PACSystems RX7i &
RX3i CPU Programmer's Reference Manual, GFK-2950.
 Contains 64Mbytes of configurable data and program memory.
 Supports auto-located Symbolic Variables that can use any amount of user memory.
 Reference table sizes include 32k bits for discrete %I and %Q and up to 32k words each for analog %AI and %AQ.
Bulk memory (%W), up to max user memory, is also supported for data exchanges.
 Supports up to 512 program blocks. Maximum size for a block is 128KB.
 For supported I/O, Communications, Motion, and Intelligent modules, refer to the PACSystems RX3i System Manual,
GFK-2314.
 Ability to display serial number and date code in PME Device Information Details.
 Operating temperature range 0C to 60C (32 F to 140 F).
Current Release Information
Firmware Version (Build Number)
Catalog
Number
Date
IC695CPE330ABAJ
IC695CPE330
CA-ABAJ
July
2016
Upgrade Strategy:
Field Upgradeable
Comment
Not Field Upgradeable
Primary
OS
Loader
BOC
FPGA
Primary
µController
Primary
ACC402
EP Base
µController
Boot
BIOS
8.95
(E6FJ)
1.02
(E4OC)
1.19
(43A1)
1.241
(20A4)
1.10
(n/a)
2.20
(n/a)
1.2
(n/a)
0ACEE007
19-Mar-15
Feature
Enhancements
Firmware version 8.95 is released to manufacturing for full production and as a web upgrade kit.
Firmware version 8.95 adds Remote Get HART Device Information COMMREQ functionality.
When upgrading for the Remote Get HART Device Information COMMREQ functionality, additional
HART-compatible hardware and firmware is required. See the Remote Get HART Device
Information COMMREQ entry in the Functional Compatibility section below for more details.
All versions of the CPE330 are field upgradeable to this firmware release using the upgrade kit
listed below. The upgrade is available via download from the GE support website
http://geautomation.com/support. Product Article ID is 000004140.
The firmware upgrade process may take up to four minutes to complete depending on the
contents of the update. During the update, the RUN and OUTPUTS ENABLED LEDs blink GREEN
and the CPE330 may automatically reset one or more times. All LEDs will be off during the
automatic resets. The IC695ACC402 Energy Pack (if present) may also be updated. The energy
pack blinks all LEDs GREEN and performs an automatic reset following its update.
Do not manually power cycle the CPE330 or remove the Cap Pack from the Energy Pack base
(if present) during the updates as this may place the CPU in an unrecoverable and unusable
state.
Upgrade Kit:
41G2016-FW01-000-A8
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
3
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Release History
Firmware Version (Build Number)
Catalog Number
Bundled
w/ACC402
Energy Pack
IC695CPE330ABAH
IC695CPE330CAABAH
IC695CPE330AAAG
IC695CPE330CAAAAG
IC695CPE330AAAF
IC695CPE330AAAE
IC695CPE330AAAD
IC695CPE330AAAC
IC695CPE330AAAB
IC695CPE330AAAA
IC695CPK330
Field Upgradeable
Date
Not Field Upgradeable
Primary
OS
Loader
BOC
FPGA
Primary
µController
Primary
ACC402
EP Base
µController
Boot
BIOS
May
2016
8.90
(E6AO)
1.02
(E4OC)
1.19
(43A1)
1.241
(20A4)
1.10
(n/a)
2.20
(n/a)
1.2
(n/a)
0ACEE007
19-Mar-15
Feb
2016
8.80
(E5RM)
1.02
(E4OC)
1.19
(43A1)
1.229
(38A8)
1.10
(n/a)
2.20
(n/a)
1.2
(n/a)
0ACEE007
19-Mar-15
Dec
2015
Nov
2015
Aug
2015
June
2015
May
2015
Mar
2015
8.75
(B5O1)
8.70
(E5KG)
8.60
(E55G)
8.55
(E4YL)
8.50
(E4V9)
8.45
(E4P6)
1.02
(E4OC)
1.19
(43A1)
1.229
(38A8)
1.19
(43A1)
1.19
(43A1)
1.19
(43A1)
1.19
(43A1)
1.19
(43A1)
1.171
(16A14)
1.171
(16A14)
1.171
(16A14)
1.171
(16A14)
1.110
(11A12)
2.20
(n/a)
2.20
(n/a)
2.20
(n/a)
2.20
(n/a)
2.20
(n/a)
2.19
(n/a)
1.2
(n/a)
1.2
(n/a)
1.2
(n/a)
1.2
(n/a)
1.2
(n/a)
1.2
(n/a)
0ACEE007
19-Mar-15
1.02
(E4OC)
1.02
(E4OC)
1.02
(E4OC)
1.02
(E4OC)
1.02
(E4OC)
1.10
(n/a)
1.6
(n/a)
1.6
(n/a)
1.6
(n/a)
1.6
(n/a)
1.5
(n/a)
0ACEE007
19-Mar-15
0ACEE007
19-Mar-15
0ACEE007
19-Mar-15
0ACEE007
19-Mar-15
0ACEE007
19-Mar-15
Functional Compatibility
Subject
Description
Feature
Programmer Version
Requirements
Minimum Version of PME Required
CPE330 Embedded Simplex
PROFINET I/O Controller
Proficy Machine Edition Logic Developer PLC 8.60 SIM 13 or 9.00 SIM 4 or
later are required for configuration of PROFINET on the CPE330.
CPE330 Hot Standby
Redundancy with
PROFINET I/O & Extended
PROFINET Device Subslot
Configuration
Proficy Machine Edition Logic Developer PLC 8.60 SIM 8 or later is
required for native configuration support of the CPE330 and its
embedded Ethernet ports as a RX3i Hot Standby Redundancy
CPU with PROFINET I/O using IC695PNC001 PROFINET Controllers.
PME 8.60 SIM 8 or later is also required for Extended PROFINET
Device Subslot Configuration
CPE330 EGD
Configuration – LAN2
Advanced Ethernet
Configuration Parameters
– LAN1 & LAN2
Proficy Machine Edition Logic Developer PLC 8.60 SIM 5 or later is
required for configuration of EGD on CPE330 LAN2. This version is
also required for advanced Ethernet configuration parameter
support on both LAN1 and LAN2.
CPE330 EGD
Configuration – LAN1
Proficy Machine Edition Logic Developer PLC 8.60 or later is
required for configuration of EGD on CPE330 LAN1. This version
(without SIM5) does not support EGD on CPE330 LAN2 or
advanced Ethernet configuration parameters for EGD.
CPE330 Configuration
Proficy Machine Edition Logic Developer PLC 8.60 or later is
required for native configuration support of the CPE330 and its
embedded Ethernet ports.
4
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
Description
CPU315, CPU320, &
CRU320 Compatible
Configuration
If the embedded Ethernet ports are not needed, older versions of
Proficy Machine Edition may be used to download a CPU315,
CPU320, or CRU320 configuration to the CPE330.
CPU315 configurations must first be migrated to CPU320, then
downloaded to CPE330.
Refer to “CPU315, CPU320, & CRU320 Configuration Compatibility”
below.
Feature
PROFINET IO
Compatibility
RX3i I/O Module
Firmware Upgrade
HART® Pass Through
Embedded PROFINET
Controller HART Pass
Through Support
Minimum Version of
PNC Controller
Required
Remote Get HART Device Information COMMREQ
2.26
Extended PROFINET Subslot Numbers
255 PROFINET Redundant IO Devices
2.25
2.10
Minimum Version of
3iPNS Required
2.41
Redundantly controlled PROFINET IO
2.00
Simplex (non-redundantly controlled) PROFINET IO
2.00
File Name
Module
Version Notes
41G1485-MS10-000-A2.zip
ALG222
1.60 The CPE330 I/O Module Firmware Upgrade
41G1485-MS10-002-A1.zip
ALG223
1.60 procedure is transacted over Ethernet using a
41G1485-MS10-001-A2.zip
ALG232
1.60 web browser and contains enhanced security
41G1485-MS10-003-A1.zip
ALG233
1.60 features. Instructions for this procedure are
82A1190-MS10-000-A2.zip
ALG306
1.02
included in the CPE330 upgrade kit
82A1191-MS10-000-A2.zip
ALG312
1.02
41G1289-MS10-000-A2.zip
ALG392
1.61 documentation.
82A1726-MS10-000-A1.zip
ALG412
1.02
41G1486-MS10-000-A2.zip
ALG442
1.61 The upgrade files listed here contain the
41G1486-MS10-001-A2.zip
ALG542
1.61 necessary security features to allow them to
44A753049-G03.zip
ALG600
1.14 work with the new enhanced security
44A753281-G01.zip
ALG704
1.08 procedure.
44A753282-G01.zip
ALG708
1.08
44A753283-G01.zip
ALG728
1.01
Older versions may not contain the necessary
41G1606-MS10-000-A2.zip
APU300
1.10
44A753277-G06.zip
CMM002
1.34 security features to allow them to work with the
44A753278-G06.zip
CMM004
1.34 new enhanced security procedure. Should you
82A1512-MS10-000-A4.zip
CMX128
1.07 need to use an older version upgrade kit which
82A1844-MS10-000-A0.zip
CMX128
2.00 is incompatible, contact GE for assistance at
41G1836-MS10-001-A0.zip
ECM850
1.00 http://geautomation.com/support.
41G2060-MS10-000-A1.zip
EDS001
6.30
41G2076-MS10-000-A1.zip
EIS001
6.30 All future I/O module firmware upgrade kits will
44A753032-G15.zip
ETM001
6.21 be compatible with the new security feature.
44A753032-G16.zip
ETM001
6.30
44A753029-G01.zip
MDL660
1.10
41G1522-MS10-000-A0.zip
MDL664
1.00
41G1522-MS10-000-A1.zip
MDL664
1.01
44A753028-G02.zip
MDL754
1.20
41G1520-MS10-000-A0.zip
MDL765
1.00
41G1520-MS10-000-A1.zip
MDL765
1.01
44A73033-G02.zip
PBM300
1.04
41G1444-MS10-000-A6.zip
PMM335
1.61
82A1790-MS10-000-A9.zip
PNC001
2.11
82A1790-MS10-000-B0.zip
PNC001
2.20
82A1729-MS10-000-A1.zip
PRS015
1.04
82A1558-MS10-000-A4.zip
RMX128
1.07
82A1845-MS10-000-A0.zip
RMX128
2.00
41G1930-MS10-000-A0.zip
RMX228
2.00
HART Pass Through entails usage of PC-based applications, RX3i Analog modules with HART
functionality and (optionally) supporting PROFINET products. HART Pass Through operation is
described in the PACSystems HART Pass Through User Manual, GFK-2929.
HART Pass Through is available on the CPE330 using a stand-alone IC695PNC001 PROFINET
I/O Controller module. The PACSystems Field Device Tool (FDT), HART Device Type Managers
(DTMs), and the PACSystems HART Multiplexer do not support the CPE330’s Embedded
PROFINET Controller.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
5
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
Remote Get HART
Device Information
COMMREQ
USB
CFast
RX3i Backplane
Hardware Revision
Compatibility
Series 90-30 Module
Compatibility
IC694 (blue) Module
Compatibility
IC695 (PCI) Module
Compatibility
GFK-2942H
Description
The Remote Get HART Device Information COMMREQ is supported by these products:
 RX3i CPUs with version 8.95 or later
 IC695PNC001 RX3i PROFINET Controller version 2.26 or later
 IC695PNS001 RX3i PROFINET Scanner version 2.41 or later
 IC695PNS001 RX3i PROFINET Scanner GSDML-V2.3-GEIP-RX3iPNS-20160602.xml2
CPE330 is compatible with USB 1.1 and USB 2.0 devices.
Cfast slot is not enabled in this release.
The following backplane hardware revisions MUST be used:
IC695CHS012-BAMP
IC695CHS016-BAMP
IC695CHS012CA-BAMP
IC695CHS016CA-BAMP
or
IC695CHS007-AA (or later)
IC695CHS012-CA (or later)
IC695CHS016-CA (or later)
IC695CHS012CA-CA (or later)
IC695CHS016CA-CA (or later)
The following Series 90-30 modules are supported by the PACSystems RX3i:
Discrete Input Modules:
IC693ACC300,
IC693MDL230/231/240/241/250/260/632/634/635/645
/646/648/654/655/6603
Discrete Output Modules:
IC693MDL310/330/340/350/390/730/731/732/733
/734/740/741/742/748/752/753/754/758
/760/916/930/931/940
Discrete Combinational:
IC693MAR590, IC693MDR390
Analog I/O Modules:
IC693ALG220/221/222/223/390/391/392/442
High Speed Counter:
IC693APU300
FANUC I/O Link:
IC693BEM320, IC693BEM321
Motion Control:
IC693DSM314, IC693DSM324
GENIUS:
IC693BEM331
Device Net Master:
IC693DNM200
Serial IO Processor:
IC693APU305
Temperature Control:
IC693TCM302, IC693TCM303
Power Transducer:
IC693PTM100, IC693PTM101
No other Series 90-30 modules are supported.
CPE330 supports all IC694* modules.3,4
CPE330 supports all IC695* modules.
Series 90-30 Main
Rack Compatibility
Series 90-30 Main Racks cannot be used in a PACSystems RX3i system.
Series 90-30 CPUs do not operate in PACSystems RX3i Racks.
Isolated 24Vdc
power
In applications that use the IC69xALG220/221/222, consult PACSystems RX3i System Manual,
GFK-2314 for details of wiring the 24Vdc power.
IC695PNS001 RX3i PROFINET Scanner GSDML-V2.3-GEIP-RX3iPNS-20160602.xml is required to enable HART Pass Through Service
Options settings in PME. Refer to the PACSystems RX3i System Manual, GFK-2314M or later, for more information.
3 IC693MDL660/IC694MDL660 firmware must be updated to version 1.10
4 IC694MDL754 firmware must be updated to version 1.10
2
6
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
Subject
Recommended
IC200ALG240
revision
Configuration of
IC694MDL754
IC695CPE330
AC Power Supply
Compatibility
CPU315, CPU320, &
CRU320
Configuration
Compatibility
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
When a VersaMax™ system Genius* Network Interface Unit (IC200GBI001) interoperates with
a Genius Bus Controller located in a PACSystems PLC, and the VersaMax system contains an
IC200ALG240 Analog Input Module, it is recommended that the IC200ALG240 firmware be
updated to Revision 1.20 or later. Use firmware update kit 44A752313-G02, available in Article
ID 000004438: https://ge-ip.force.com/communities/en_US/Download/IC200ALG240VersaMax-Analog-Input-Module-16-Bit-8-Isolated-Inputs-DN16-enUS.
Always configure sixteen bits of module status when using this module. Configuring zero bits
of module status will result in invalid data in the ESCP status bits of the module.
For new installations using AC power supplies, the CPE330 requires an IC695PSA040H or
IC695PSA140D (or higher) revision power supply to ensure compatibility.
For retrofit installations using AC power supplies, the CPE330 may require an IC695PSA040H or
IC695PSA140D (or higher) revision power supply depending on the total current load in the
backplane. If the total current load exceeds the minimum current threshold of the existing
power supply, no power supply change is required.
The CPE330 may be interchanged with a corresponding CPU320 or CRU320 with no upgrade
to Proficy Machine Edition (PME) software. Logic and configuration equality in PME are
maintained when storing the same project to either a CPU320/CRU320 or a CPE330.
The CPE330 ships from the factory configured for Normal (CPU320) compatibility mode. The
compatibility mode must be switched to CRU320 mode prior to downloading a CRU320
application. (Refer to PACSystems RX3i 1GHz 64 MB CPU w/Ethernet IC695CPE330 Quick Start
Guide, GFK-2941D or later for instructions on changing the compatibility mode.) Changing the
compatibility mode is not necessary if a CPU320/CRU320 application is changed to a CPE330
application with a version of PME that has native CPE330 support.
Migration of CPU315 applications to the CPE330 is possible with no upgrade to PME by
converting them to a CPU320 application and storing the project to the CPE330. Versions of
PME with native CPE330 support allow either a CPU320/CRU320 or a CPE330 configuration to
be stored to the CPE330. When a CPE330 is configured as a CPU320 or CRU320, Ethernet
properties cannot be configured however, the embedded Ethernet ports may be used with the
default IP Addresses.
Migration of CPU315,
CPU320, & CRU320
Serial Applications to
CPE330
Applications using the embedded serial ports of the CPU315, CPU320, & CRU320 should move
serial functionality to the IC695CMM002 or IC695CMM004 Serial Communication Modules
when migrating to the CPE330 since it does not have embedded serial ports.
Ethernet AUP File
Support
The CPE330 does not support Advanced User Parameter (AUP) files for its Embedded Ethernet
interfaces. AUP files are supported for external IC695ETM001 Ethernet modules.
Service Request 56 &
57 Logic Driven
Read/Write to Flash
Support
Supported Browsers
for CPE330 Firmware
Update
The IC695ACC402 Energy Pack automatically saves all user memory to flash when the CPE330
is powered off, and restores it to RAM when the CPE330 is powered on. Consequently, the
CPE330 does not support Service Requests 56 & 57 Logic Driven Read/Write to Flash. The ENO
output of the function block returns no power flow if these service requests are executed.
When migrating a CPU320 application that uses Service Requests 56 & 57 to a CPE330, the
IC695ACC402 Energy Pack needs to be attached.
The CPE330 supports secure firmware update over Ethernet using a web browser. Supported
browsers are listed below along with the minimum required version:
 Firefox: 41.0.2 (or later)
 Chrome: 46.0.2490.80 m (or later)
 Internet Explorer: 11.0.9600.18059IS (or later)
 Opera: 32.0.1948.44 (or later)
 Safari: 9.0 (10601.1.56.2) (or later)
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
7
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
CIMPLICITY
OPC UA Client
CPE330 vs CPU320
Power Requirements
GFK-2942H
Description
PACSystems OPC UA servers support up to five concurrent sessions with up to ten concurrent
variable subscriptions and up to 12,500 variables. The subscription limit is shared across all
available sessions.
When using CIMPLICITY OPC UA Client, ensure the total number of subscriptions does not
exceed the maximum. CIMPLICITY OPC UA Client is configured to create one subscription for
every 500 items by default. If, for example, a project contains 1000 monitored items,
CIMPLICITY creates two subscriptions. The number of items per subscription may be modified
from the Device Configuration Panel / OPC UA DA Configuration / Subscriptions / Max. Number
of Monitored Items.
When migrating a CPU320 application to a CPE330, the power consumption must be
recalculated to ensure adequate power is available in the new system. The maximum power
consumption of a CPE330 is 18W whereas the maximum consumption a CPU320 is 9.3W.
Depending on the total power available in the CPU320 system, it is possible that additional
RX3i power supplies will be required. Users may view the combined power consumption of an
RX3i rack in PME by right-clicking the power supply whose icon has a power usage indicator
and selecting properties.
CPE330 Power Requirements
CPU320 Power Requirements
+3.3 Vdc:
0.0 A
1.0 A
+5.0 Vdc:
0.0 A
1.2 A
+24 Vdc Relay:
0.625 A without Energy Pack
0.0 A
0.750 A with IC695ACC402 Energy Pack
+24only
Vdcenergy
Isolated:
A
0.0 A
The
pack 0.0
compatible
with the IC695CPE330 is the IC695ACC402.
PACSystems Energy
Pack Compatibility
The CPE330 is not compatible with the ICRXIACCEPK01 RXi Controller Energy Pack or the
IC695ACC400 CPE305/310 Energy Pack.
 It is not physically possible to connect the CPE330 and the IC695ACC400 CPE305/310
Energy Pack together.
 However, it is possible to connect the CPE330 and the ICRXIACCEPK01 RXi Controller
Energy Pack. Connecting the CPE330 to the RXi Energy Pack is not harmful. However, if
power is applied, the CPE330 will continuously reset and not power up. Should this
occur, turn the CPE330 off and disconnect the RXi Energy Pack.
 It is possible to connect the ICRXIACCCPK01A RXi Capacitor Pack to the IC695ACC402
Energy Pack Base. If this occurs, the capacitor pack may take longer to charge and a
battery fault may be logged. Do not use the CPK01A RXi Capacitor Pack with the ACC402
Energy Pack Base.
 It is also physically possible to connect the IC695ACC402 CPE330 Energy Pack and
IC695ACC412 Capacitor Pack to an ICRXICTL000 controller. If this occurs no errors are
logged. However the capacitors will reach their end-of-life threshold faster than the RXi
Capacitor Pack ICRXIACCCPK01. Do not use the CPE330 Energy Pack or Capacitor Pack
with the RXi Controller.
Ethernet Station
Manager
Compatibility
Ethernet Station Manager utility Version 1.3 Build 2 or later is recommended for use with the
CPE330. Earlier versions are compatible; however they may not display all CPE330 Ethernet
parameters after issuing a parm all command. Should this issue occur, pressing enter, or
issuing another command will cause the station manager to display the remaining
parameters.
Redundant IP
Support
Redundant IP is supported by the SRTP Server, Modbus TCP Server, and EGD protocols. It is not
possible to use Redundant IP with the OPC UA Server and the Ethernet firmware update web
page.
Hot Standby
Redundancy I/O
Support
The CPE330 supports Hot Standby Redundancy with PROFINET IO using IC695PNC001
PROFINET controller modules and Hot Standby Redundancy with Ethernet (EGD) or Genius IO.
Ethernet (EGD) and Genius IO may be used simultaneously. However, they may not be mixed
with PROFINET IO in a single redundancy system.
8
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
Subject
PNC001 Version for
Extended PROFINET
Subslot Numbers
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
IC695PNC001 PROFINET Controller firmware version 2.25 or later is required to configure
PROFINET devices using extended subslot numbers.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
9
GFK-2942H
Problems Resolved by this Revision
Subject
ID code
CPE330 Does not
Produce
Multicast EGD
DE3400
Scan Failed Error
Using Explore
PROFINET Networks
with CPE330
Embedded PNC
DE3449
Cyber Security
Updates
DE3187
Description
In rare cases, multicast EGD production may not start after downloading a
configuration containing multicast EGD exchanges on both LAN 1 and
LAN 2. When this occurs, the CPE330’s embedded ETM contains this event in
the log:
28H 1H 0034H 0000H 0000H 0005H 017fH a8ae0033H
PROFICY Machine Edition’s Explore PROFINET Networks feature returns a
Scan Failed error when attempting to browse devices in a network
connected to the CPE330’s Embedded PROFINET Controller. This issue
occurs when the Embedded PROFINET Controller’s IP address doesn't
change after powering up or downloading configuration from PME.
Explore PROFINET Networks works as expected (until the next power cycle)
after downloading a configuration that changes the Embedded PROFINET
Controller’s IP address.
Security enhancements were made to the IC695CPE330 to harden the
product against an attacker.
New Features and Enhancements

Remote Get HART Device Information COMMREQ: Information from a HART device connected to an RX3i Analog
Module in an IC695PNS001 RX3i PROFINET Scanner may be read into the user application using the Remote Get
HART Device Information COMMREQ. This COMMREQ is supported by both the IC695CPE330’s Embedded PROFINET
I/O Controller and the IC695PNC001 PROFINET I/O Controller module.
Remote Get HART Device Information COMMREQ operation is described in GFK-2314 PACSystems RX3i System
Manual.
A UDFB that automates the COMMREQ control logic is available for download from the GE support website. (Article
ID: 000017816) https://ge-ip.force.com/communities/en_US/Download/Remote-Get-HART-Device-InformationCOMMREQ-UDFB
10
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Restrictions and Open Issues
CPE330 CPU & Embedded Ethernet:
Subject
ID code
Description
Firmware Update Login
Timeout
DE196
DE205
DE2626
The CPE330 enforces a two minute login activity timeout on the Firmware
Update web page. Selecting an update package on the Firmware Update
page and pressing the Upload File button after the timer expires initiates a
firmware update. However, instead of displaying the firmware update
status, one of these scenarios may occur:

Another login page is presented. After entering the user name and
password the update status is displayed.
 The web browser loses connection with the CPE330 and is unable to
display update status because the CPU is automatically resetting
while applying the firmware update. After the reset completes,
pressing the refresh button in the browser shows the installed
firmware version.
 An error message is displayed indicating the firmware update was not
successful however, returning to the firmware update home page
shows that the new firmware version was installed.
These timeout issues may be avoided by having the firmware file ready so
that the firmware update can be initiated immediately after logging in.
Running applications with
fatal faults from flash
DE86
If an application that generates a fatal fault (such as a watchdog timeout)
is stored to flash, the controller is configured to power-up from flash and
go to RUN, and the RUN/STOP switch is disabled, the application may
become stuck in an endless loop. (Power-up from flash, go to RUN,
watchdog timeout, repeat.) Return the CPE330 to the factory if this
condition is encountered. It is recommended that users thoroughly test
their application before writing it to flash.
Clear All clears PLC_BAT
and masks Energy Pack
failures
DE715
A Clear All operation clears the values of all %S bits. After this operation
the PLC_BAT status bit value may not reflect the actual status of the
Energy Pack. For example, an Energy Pack in a failed state prior to the
Clear All operation will remain in the failed state after the Clear All.
Nonetheless, the PLC_BAT bit will indicate a good state as a result of the
Clear All operation. Remove the Cap Pack and reinstall it in order to
reassert the PLC_BAT status bit.
Using OEM Passwords with
Enhanced Security
Disabled
DE755
Single character OEM passwords are not supported when enhanced
security is disabled.
PME cannot display
reference tables with
Enhanced Security Enabled
and OEM Locked
DE781
When Enhanced Security is enabled and OEM protection is engaged, only
reference areas specified within the Access Control List can be viewed by
a programmer, or HMI, regardless of privilege level. For example, if viewing
%R memory from words 1 to 400 then the Access Control List must include
read access to %R words 1 to 400. A custom reference view table with
smaller reference sizes may also be used.
Controller Communication
Window Timer settings
below 10 ms are ignored
DE845
Normal sweep allows the configuration of the Controller Communications
Window Timer for Limited operation and a time range from 0 to 255 ms
(default 10 ms). However, the system is currently ignoring settings in the
0 to 9 ms range which results in an effective window time of 10 ms for this
configuration range. This means a sweep impact of up to 10 ms may
occur for some complex Controller Communication Window operations. If
this operation is undesired then it is recommended to use a different
sweep mode such as Constant Sweep or Constant Window.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
ID code
11
GFK-2942H
Description
Selecting Variable Publish
State = Internal causes
variable to be published in
Address Space
DE1330
PME allows users to select a Variables Publish State to Internal. In some
cases, this will cause the variable to be published to the OPC-UA address
space. The manual states users should select External Read/Write or
External Read-Only to publish to the address space. This is the
recommended approach.
OPC-UA Server Restart
Fails to complete
DE1326
The OPC-UA server may fail to restart after a large number (~200) of
restart sequences are attempted without an intervening power cycle. A
restart sequence will occur with the following operations: Run Mode or
Stop Mode Store when published variables change and OPCUA server is
running. Whenever this occurs, the server restart bit will stay on
indefinitely. The issue is contained to OPC-UA server operation only. Power
cycling the controller is the only way to address the issue.
Abrupt Power-down Fault
DE2256
An Abrupt power-down detected at power-up fault is recorded in the
CPE330 PLC Fault Table if both the Logic/Configuration Power-up Source
and Data Power-up Source in the hardware configuration are set to
Always Flash or Conditional Flash and the CPE330 is turned off without an
energy pack connected. This fault indicates that user memory was not
preserved across the power cycle and does not interfere with normal
operation because the application is already configured to power up from
flash if there is no energy pack connected.
Power Supply Loss of
Module Fault After
Configuration Download
DE2257
CR-6257
A Loss of, or missing option module fault may appear for any RX3i power
supply configured in the main rack whenever a hardware configuration
download is performed after a BOC update occurs. (A BOC update occurs
during a firmware update when switching between different CPU models
in a single backlpane and also the first time a particular CPU model is
placed in a backplane. BOC updates are indicated by the RUN and Output
Enabled LEDs blinking in unison briefly during power up.)
This issue does not affect normal operation and may be cleared by power
cycling the CPU.
Missing Addition of IOC
event, when ECM850
module restarts due to
reason like reset pushbutton and SVC_REQ 24
DE1248
When ECM850 module RESET is triggered using SVC_REQ 24 or via Reset
pushbutton, PLC CPU do not report Addition of IOC fault message in
Controller fault table, after successful reset of module.
Blink Code 1-2-1-8 After
Power On
DE2017
Rarely, after powering on, the CPE330 may display blink code 1-2-1-8 on
its LEDs. If this occurs, cycle power to the CPU to clear the condition.
Loss of I/O Modules in
Expansion Rack
DE2336
Rarely, I/O modules in an expansion rack may fail to reconfigure if the
expansion rack is turned off and back on while the main rack remains
powered on. If this occurs, turn the expansion rack off and back on again
or, download hardware configuration using PME.
ALG616, ALG626, & ALG628
Terminal Block Present
Status Bit
DE2422
IC695ALG616-Fx, IC695ALG626-Fx, and IC695ALG628-Fx (and later
hardware revision) analog modules may not set the terminal block present
status bit in their module status after a CPE330 firmware update
completes, even if the terminal block is installed. Normal operation of the
terminal block present status bit may be restored by performing one of the
following operations: removing and reinstalling the terminal block,
resetting the analog module using Service Request #24, or power cycling
the rack.
12
GFK-2942H
Subject
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
ID code
Description
Unable to Use <Enter Key> to
Login to CPE330 Firmware
Update Web Page
DE2965
After entering the firmware update user name and password, the mouse must be
used to click the login button. Pressing the <Enter> key on the keyboard does not
submit the login credentials.
Microsoft® Edge Browser not
Supported for CPE330
Firmware Update
DE3011
The Firmware Update Home page displays correctly using the Microsoft Edge
browser however, if a firmware update is performed the firmware is updated
successfully but status is not reported.
CPE330 Logs Loss of IOC Fault
for PNC001 on Power Down
DE3029
The CPE330 may log a “Loss of IOC” Fault for a configured IC695PNC001 PROFINET
controller when the CPE330 is powered off.
CPE330 Logs Redundant Link
Communication Failure on
Power Down
DE3030
The CPE330 may log a “Redundant Link Communication Failure” Fault for a
configured IC695RMX128 or IC695RMX228 Memory Xchange Module when the
CPE330 is powered off.
Unable to Place CPE330
into Run Mode Using PME
DE3098
Rarely, when the CPE330’s Run/Stop switch is set to Run I/O, an attempt to
change its mode from Stop No I/O to Run I/O Enabled using Proficy
Machine Edition (PME) fails and displays this error message in the
Feedback Zone:
Error 8533: Unable to start runtime. Controller Error - Invalid sweep mode
[0x05][0xF6] [0x803D0022]
This error message is expected when attempting to place the CPE330 into
RUN I/O Enabled mode and the Run/Stop switch is set to Stop however, it
is not expected when the Run/Stop switch is set to Run I/O.
If this issue occurs, the CPE330’s mode may be set by first power cycling
the CPU and then using PME to change the mode.
Ethernet COMMREQs not
always delivered on the
first logic sweep
ISS183540
In certain instances where User Logic is of sufficient size and a COMMREQ
is issued on first logic sweep, a race condition existing between
determination of the CPU Run/Stop state and logic-driven issuance of a
COMRREQ which may cause the COMMREQ to be aborted before its
transmission is attempted. To the user, it would appear as if the COMMREQ
was never issued. The condition is much more observable on COMMREQs
issued from the CPU’s embedded Ethernet port. To avoid the possibility of
encountering this condition, users should avoid issuing COMMREQs on first
logic sweep.
PMM335 loss is
occasionally detected on
power down of the
CPU. (Module is not lost on
power up.)
ISS182714
The PMM335 monitors power loss, independently of the CPU. The CPE305,
CPE310, CPU315, CPU320, CRU320, and CPE330 are fast enough that they
can occasionally detect and log the loss of the PMM335 just before the
CPU itself powers down.
No corrective action is required; This situation can be verified in two ways:
(1) by inspecting the timestamp in the loss-of-module report one can
correlate it with the power-down event, and (2) by performing a PME Show
Status Details report one can see that the PMM335 is present after power
up.
Hot Swapping some Analog
modules slowly result in
modules not being
recognized
CR-7365
Occasionally during a hot insertion (hot swap) of IC695 Non-Isolated
Analog Input Modules, input channels may take up to 2 seconds to reflect
actual input values after the module ok bit is enabled in the module status
word. This has only been seen when the hot insertion has been done
slowly (i.e. approximately 1.5 seconds to insert the module).
Ethernet Disconnect
During Word for Word
Change
CR-2234
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. To correct the issue, go offline and then back online
again.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
ID code
13
GFK-2942H
Description
Simultaneous Clears,
Loads and Stores Not
Supported
CR-3118
CR-3300
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.
Hardware Configuration
Not Equal After Changing
Target Name
CR-3181
If the user stores a hardware configuration to flash that sets Logic/Config
Power up Source 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
CR-3191
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 are 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
CR-3317
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 Force Off by another download.
Second programmer can
change logic while in Test
& Edit mode
CR-4223
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.
Must Have Logic If
Powering-Up From Flash
CR-4633
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.
Two loss of module faults
for Universal Analog
Module
CR-5462
Occasionally, the hot removal of the Universal Analog Input Module
(IC695ALG600) results in two Loss of I/O Module faults instead of one.
Power up of Series 90-30
HSC module may take as
long as 20 seconds
CR-5666
As power is applied to a 90-30 High-Speed Counter, the module ready bit
in the status bits returned each sweep from the module may not be set for
as long as 20 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
High Speed Counter Modules for PACSystems RX3i and Series 90*-30 User’s
Manual, GFK-0293D.
Informational fault at
power-up
CR-5850
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 PLC. 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 Triggers
CR-5952
CR-6319
%R, %W and %M cannot be used as IO triggers.
Possible PME inability to
connect
CR-6067
Infrequently, an attempt to connect a programmer to a PLC via Ethernet
will be unsuccessful. The normal connection retry dialog will not be
displayed. Rebooting the computer that is running the programmer will
resolve the behavior.
14
GFK-2942H
Subject
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
ID code
Description
GBC30 may not resume
operation after power
cycle
CR-6167
In rare instances, a GBC30 in an expansion rack may not resume normal
operation after a power cycle of either the expansion rack or the main
rack.
Configuration of 3rd Party
Modules
CR-6207
When configuring a 3rd Party Module in PME, a non-zero reference length
must be assigned to at least one reference type. For example, assign eight
bits of %I. Do not specify a length of zero for all reference types since this
will cause the module to not function properly in the system.
Power supply status after
power cycling
CR-6294
Rarely, turning a power supply on or off may not result in an add or loss
fault. 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.
Don’t use multiple targets
CR-6450
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
block fault
CR-6526
The IC695ALG600/608/616 analog input modules do not produce a Loss of
terminal 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
CR-6586
ISS176888
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 work
around 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 PME prior to performing the
write. This is done by expanding the Additional Configuration in the
Inspector window for the target controller, and adjusting the Request
Timeout. The timeout may need to be increased to as much as
60000 ms, depending on the amount of memory used and the
condition of the flash memory.
IC695ALG600 Lead
Resistance Compensation
setting
CR-6689
A configuration store operation will fail if a channel is configured for 3-wire
RTD and 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.
C Toolkit PlcMemCopy
Documentation Incorrect
CR-7082
This routine does allow the destination and source pointers to be outside
of reference memory. If the destination points to discrete reference
memory, overrides and transitions will be honored. Note that the header
for PlcMemCopy has been updated in Release 3.50 of the C toolkit.
Logic and HWC not equal
after power cycle
ISS168431
If the Hardware Config from Target 1, with Logic/Configuration Power-up
Source and 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.
Multiple Log Events
CR-2014
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.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
ID code
15
GFK-2942H
Description
Spurious Ethernet Fault
CR-4104
In rare instances, after power cycle, the Ethernet Interface may log the
following fault, Event = 28H, Entry 2 = 000eH. This fault can be safely
ignored.
Clear of large hardware
configurations may cause
log event 08/20
CR-6577
A Log event 08/20 may occur when very large hardware configurations
are cleared and transfers are active on other Server connections. This log
event can be safely ignored.
PLC response timeout
errors (8/08) in Ethernet
exception log under
extremely heavy SRTP
traffic
ISS010006
Under extremely heavy SRTP traffic conditions, the Ethernet Interface may
log an event in the Ethernet exception log (Event 8, Entry 2 = 08H)
indicating an overload condition. This error terminates the SRTP
connection. If this event appears, either 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 take up to 20 seconds
after power cycle
ISS155214
When SRTP communications are interrupted by a power cycle, the
Ethernet interface may require up to 20 seconds to reestablish TCP
connection used for SRTP communications.
Intermittent Ethernet log
event 8H/15H after power
cycle
ISS163056
When starting after a power cycle, the Ethernet Interface may
intermittently log an exception (entry 8H, Entry 2 = 15H, Entry 3 = 0000H,
Entry 4 = 00aaH). This exception is benign and may be ignored.
Station Manager “PARM”
command help text is
wrong
ISS181788
Although the “parm v” Station Manager command works correctly, the “v”
subsystem code (SRTP server) is not shown as supported by the online
help.
RDSD upload / unintended
OEM protection lock
ISS182099
When an OEM key is set in a controller, and the controller is unlocked, if an
RDSD upload is performed, in rare occasions OEM protection will be
unintentionally locked after the upload completes. To recover, enter OEM
password to unlock the project, then clear the user memory and flash
memory.
16
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
CPE330 Embedded PROFINET Restrictions & Open Issues:
Subject
IP Address
Changes To
Embedded PNC
May Cause Loss
Of
Communication
s With PNS &
GCG
ID code
DE3423
DE1461
Description
Downloading a new hardware configuration with a different IP Address for the
embedded PROFINET interface in the CPE330 to an already configured CPE330
may cause configured PNSs and GCGs to disconnect from the embedded
PROFINET interface. This issue is observed when using both PME 8.6 SIM 12/13 and
PME 9.0 SIM 4.
If this issue occurs, disconnect PME from the CPU, remove the Energy Pack if one is
attached to the CPU, and cycle power to the main rack. Then reconnect PME and
download the hardware configuration again.
There are 2 scenarios that can cause the Embedded PNC to indicate that an MRP
Ring is closed when in fact it is still open. The scenarios are:
1.
Embedded PNC
indicates
premature MRP
Ring closure and
logs extra Ring
Closed/Ring
Open faults
when network
cable
reconnected
2.
DE1711
Store of HWC
may result in 3
IOC Software
Faults.
STXPNS001
Firmware
revision is not
displayed
correctly when
viewed using
PME PROFINET
Explorer
Loss of IOC and
Backplane
Communication
s Faults after
Clearing CPE330
Hardware
Configuration
with
Mismatched
STXPNS001
Configuration
DE568
ISS18284
3
DE569
ISS18229
3
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
When either an RX3i PNS or PNC that participate in the MRP ring as an
MRP Client communicating via Copper or Fiber SFPs is powered-up in the
MRP ring, extra Ring Closed/Ring Open faults are logged in the I/O fault
table. A Ring Closed fault occurs during the initial stage of the PNS/PNC
power-up, followed by a Ring Open fault in the middle of the PNS/PNC
power-up sequence, and finally a Ring Closed fault occurs when the
PNS/PNC completes power-up (OK LED on).
When the first of two MRP ring breaks is restored, extra Ring Closed/Ring
Open faults are logged in the I/O fault table. Upon restoration of the first
ring break, a Ring Closed fault occurs, followed by a Ring Open fault. Then
upon restoration of the second ring break, a final Ring Closed fault occurs.
The duration between faults is a function of the PNC’s configured MRP
Default Test Interval and Test Monitoring Count.
When either of the two scenarios is invoked, the user sees extra Ring Closed/Ring
Open faults in the IO Fault Table. The extra Ring Closed/Ring Open fault may be
ignored.
On very rare occasions, storing a very large PROFINET hardware configuration may
result in 3 IOC Software faults. The faults tend to occur after a large number of
changes are made to the hardware configuration or the current hardware
configuration in the system is cleared prior to storing a new configuration.
If the controller is Faulted, clear the I/O Fault Table to recover. Otherwise, no
additional steps need be taken and the faults may be ignored.
Firmware revision information for the STXPNS001 does not display correctly using
PROFICY Machine Edition. The correct firmware revision information can be viewed
on the module using HyperTerminal.
Clearing the CPE330’s hardware configuration after downloading a mismatched
RSTi STXPNS001 PROFINET Network Adapter configuration causes a Loss of IOC
and a Backplane communications with Controller fault; lost request fault to be
recorded in the fault table. Communication with Proficy Machine Edition is also lost.
If this issue occurs, power cycle both the CPE330 and STXPNS001. (When power
cycling the CPE330, disconnect its energy pack if one is connected.) Then, correct
the STXPNS001 hardware configuration in PME so that it matches the physical
hardware in the IO node and download the updated hardware configuration to the
CPE330.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
17
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
ID code
Description
Loss of IO
DE579
In very rare cases, hot insertion of a mismatched VersaMax I/O module (i.e.,
Device
MDL650 in a slot configured for an MDL640) into the VersaMax PNS can cause a
following hot
loss of connection between the PNS and the Embedded PNC.
insertion of
mismatched
No user action is required. When this behavior is seen, the Embedded PNC will
VersaMax I/O
automatically re-connect to the VersaMax PNS.
module
IOC SW Fault
DE838
When storing a PROFINET configuration that is close to the upper limit of the
with large
CPE330’s user memory the store may fail with an IOC Software Fault logged in the
configurations
I/O Fault Table.
Breaking &
reconnecting an
MRP ring by
pulling either of
the 2 MRM ports
causes extra
ring open/close
faults
Unintended
operation of
PNIO DEV COMM
function block
DE1140
ISS18137
9
Clearing the PLC’s existing Hardware Configuration (and I/O Fault Table if the
controller is Faulted) before attempting the store should allow the store to succeed.
In some cases, if the network is broken and repaired at either of the two ring ports
of a CPE330 configured to be the MRM, extra “I/O Bus Fault-Redundant Ethernet
network ring broken (open)” and “I/O Bus Fault-Redundant Ethernet network ring
okay (closed)” faults are logged in both the I/O Fault Table and the PNC Local Log
when the ring is repaired.
These additional faults may safely be ignored as long as the last fault to be logged
is “I/O Bus Fault-Redundant Ethernet network ring okay (closed)”.
The power flow output of the PNIO_DEV_COMM function block provides validation
of the input parameters and confirms that the Embedded PNC has locally
processed the configuration of the specified I/O Device. As currently implemented,
the power flow output will not turn ON until after the Embedded PNC has made its
first attempt to connect to the specified I/O Device. Therefore, we recommend the
user not rely on power flow output for parameter validation.
18
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Operational Notes
CPE330 CPU & Embedded Ethernet:
Subject
Description
Default IP Addresses
for CPE330 Embedded
Ethernet
Connecting to CPE330
Embedded Ethernet
when IP Addresses
are not Known
Initial Ethernet communication with the CPE330 may be accomplished using the default IP
Addresses programmed at the factory:
LAN1 (Top Ethernet Port)
LAN2 (Bottom Two Ethernet Ports)
IP Address:
192.168.0.100
10.10.0.100
Subnet Mask:
255.255.255.0
255.255.255.0
Gateway:
0.0.0.0
0.0.0.0
If the IP Addresses of the CPE330 embedded LAN1 and LAN2 Ethernet interfaces are not
known, communication may be established using these methods to set new IP Addresses:


Set Temporary IP
Address Utility
Limitations
Set a temporary IP Address using the Set Temporary IP Address utility in Proficy Machine
Edition. (PME) After setting the temporary address, connect to the CPE330 using PME and
download a new hardware configuration with the desired permanent IP Addresses. (The
IP Address set by the Set Temporary IP Address utility is temporary and is reset to match
the stored configuration after a power cycle. After using the utility, a permanent IP
Address must be set by storing a hardware configuration.)
Connect to the CPE330 with PME using an IC695ETM001 module with a known IP Address.
Download a new hardware configuration with the desired IP Addresses for the CPE330
embedded Ethernet interfaces.
These limitations apply when using the Set Temporary IP Address utility in Proficy Machine
Edition (PME) with the CPE330. Refer to PME’s help for a complete list of limitations:





The Set IP utility supports communication through network switches and hubs.
Communication through routers is not supported.
The current user logged on the development computer must have full administrator
privileges and PME must be run as an administrator.
The target controller must be located on the development computer’s local subnet, as
specified by the computer’s subnet mask and the IP address of the computer and
controller.
The Set IP utility does not always work on Windows® 7 SP1. Refer to PME’s help for
possible work-arounds.
The Set IP utility is not compatible with USB to Ethernet adapters.
Ethernet Event Log
Not Preserved Across
Power Cycle
The CPE330 Ethernet event log for its embedded Ethernet interfaces is not maintained across
a power-cycle. Ethernet log events will be reported in the PLC Fault Table as with other RX3i
CPUs. The PLC Fault Table entries will be preserved if an energy pack is attached.
Station Manager
Commands
The embedded Ethernet interfaces of the CPE330 support a subset of Station Manager
Commands (monitor only commands). Refer to PACSystems TCP/IP Ethernet Communications
Station Manager Manual, GFK-2225, for details.
Programmer Display
of Module
Information
The functionality to display module status in Proficy Machine Edition Logic Developer will
show 5CPE330A when the CPE330 is configured as a CPU320.
RDSD / Programmer
Interaction
When using RDSD, all Proficy Machine Edition Logic Developer PLC connections must be in the
Offline state for the RDSD to function properly.
RDSD OEM /
Password Protection
of Former Uploads
Incorrectly
Maintained
When deleting an OEM key from a project, you must remove the Energy Pack and cycle power
before writing to the RDSD. If this procedure is not followed there are rare occasions where
the OEM key that had been deleted may be restored on the RDSD device and therefore could
be unexpectedly downloaded to the CPU on a subsequent RDSD download.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Subject
Description
19
GFK-2942H
Extra Option Module
Fault after
Downloading CPU320
Configuration to
CPE330
An Extra Option Module fault is logged in the Controller Fault Table after downloading a
CPU320 configuration to a CPE330. This indicates that the Embedded Ethernet interface did
not receive a configuration. This fault is expected and does not interfere with normal
controller operation.
CPE330 Power-up
Time
The CPE330 requires more time to power up than the CPU320:


When an IC695ACC402 Energy Pack is not connected, the CPE330 requires approximately
30 seconds to complete power-up. The CPU OK, RUN, and OUT EN LEDs remain off for up
to 30 seconds after power is applied.
When an energy pack is connected, the CPE330 requires up to 90 seconds to complete
power up. The power up sequence of the CPE330 begins after the energy pack is fully
charged. Charging may require up to 60 seconds depending on the capacitor pack’s
initial charge. (The energy pack’s STAT LED blinks green while it is charging and turns solid
green when charging is complete.)
Hot swap of Cap Pack
during firmware
update results in RXi
controller fatal
indication (i.e., blink
code)
Insertion or removal of the Energy Pack Cap Pack during an Energy Pack firmware update will
cause the CPE330 to become non-responsive. In order to recover from this condition user
must cycle power to the CPE330. The CPE330 controller will enter a fatal blink trap with code
0x2825.
Insertion of Cap Pack
during controller
power-up could
cause failed battery
fault
If the Energy Pack is powered on without a Cap Pack and a Cap Pack is then inserted during
power-up of the CPE330, the CPE330 could log a failed battery fault. The CPE330 expects the
Energy Pack to report fully charged within a certain amount of time. This time limit may not be
met if the Cap Pack is absent at power up.
Avoid Overlapping IP
Subnets when
Configuring CPE330
IP Address and
Subnet Mask
The CPE330 contains two LAN interfaces, each one supporting a unique IP Address. Care must
be taken when assigning IP Addresses and subnet masks to each LAN so that an overlapping
IP subnet is not created. Intermittent or no Ethernet communication may result if an
overlapping IP subnet is created and the two interfaces are NOT connected (cabled) to the
same physical network.
By default PME prohibits configuring both LAN interfaces on an overlapping IP subnet. (This
may be changed by going to Controller General Options and changing the CPE330 – LAN1,
LAN2 On Same Subnet to Show as Warning.)
Avoid Overlapping
Remote IP Networks
when Configuring
CPE330 IP Address
and Subnet Mask
The CPE330 network interface behaves like a single ETM001 with two LANs / IP Addresses. (It is
a multi-homed device.) Care must be taken when assigning IP Addresses and subnet masks to
each LAN so that each network does not overlap any remote subnets in the network
infrastructure. Intermittent or no Ethernet communication may result if the local networks on
the CPE330 overlap a remote subnet.
CPE330 Ethernet
Gateway Operation
The CPE330 allows configuration of an Ethernet gateway on both LAN1 and LAN2. Since the
CPE330 contains two LAN interfaces, each one supporting a unique IP Address, only one
gateway is active at a time:
 If a gateway is configured on only one of the two LAN interfaces and the other is not
configured (0.0.0.0) then, the single gateway is shared by both interfaces.
 If a gateway is configured on both LAN interfaces, then the LAN1 gateway is given priority
over the LAN2 gateway as long as LAN1 is functional. If, for example, the LAN1 cable is
disconnected then the CPE330 will use the LAN2 gateway as a backup.
LAN1 and LAN2 LED
Network Speed
Indicators
The LAN1 and LAN2 network speed indication LEDs embedded in the RJ-45 Ethernet ports of
the CPE330 use different colors to indicate 1 Gbps data rate. The LAN1 LED is Amber to
indicate a data rate of 1 Gbps; the LAN2 LED is Green.
20
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
Subject
Description
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
CPE330 Embedded
Ethernet Protocols &
Performance
The CPE330 has two independent Ethernet LANs with three auto-negotiating, full-duplex
10/100/1000 Ethernet Ports which allow support of two IP Addresses and the following
protocols:

OPC UA Server with support for up to 5 concurrent sessions with up to 10 concurrent
variable subscriptions and up to 12,500 variables
 SRTP Server with support for up to 48 simultaneous connections
 Modbus/TCP Server with support for up to 16 simultaneous server connections
 SRTP and Modbus/TCP Client with support for up to 32 clients; each may be SRTP or
Modbus/TCP
 Ethernet Global Data (EGD) Class 1
Embedded Ethernet communication is managed by a dedicated processor core. Applications
using Ethernet communication should be validated to ensure adequate throughput is
available to meet the needs of the application. Additional IC695ETM001 Ethernet modules
may be added to the system if additional throughput is required.
CPE330 Multicast EGD
Exchange Operation:
Double Consumption
Possibility
In the event that LAN1 and LAN2 are physically connected to the same Ethernet network, then
any multicast EGD consumer exchanges may be consumed twice if both CPE330 LAN
interfaces use the same multicast IP addresses.
This double consumption occurs because the CPE330 has two LAN interfaces and it is
possible for the CPU to receive duplicate multicast packets (one from each interface) and
consume both. If this occurs, issuing a stat g station manager command shows that the
multicast consumer exchange updates twice as fast as the producer sends it.
CPE330 / CRU320
Mixed-model
Redundancy
Operation
To avoid this issue, connect the LAN1 and LAN2 to physically separate Ethernet networks
(i.e. no Ethernet switches in common).
During power-up, when a CPE330 is configured as a secondary redundancy CPU, it waits up
to 70 seconds to detect the primary unit. (All other redundancy CPUs wait 30 seconds.) If the
primary unit is not detected within this wait time, the secondary unit assumes the primary unit
is not present. In this case, if the secondary unit is configured to transition to Run on powerup, it becomes an active unit without a backup unit.
Because a CPE330 supports a CRU320 compatibility mode which allows a CRU320
configuration download to a CPE330, a mixed-model redundancy system can be created. It is
not recommended to design a system with mixed-models; however, this setup may be used
to replace a failed redundant CPU until a matched replacement is available.
CPE330 / CRU320
Mixed-model Dual
Synchronization
When a CPE330 and CRU320 are operating in a mixed-model redundancy system, Dual
Synchronization at power-up cannot be guaranteed because of the power up time
differences of the two CPUs.
STOP to RUN
Transition in CPE330
Redundancy System
with PROFINET I/O
A Primary CPE330 waits a maximum of 20 seconds during power-up for PROFINET device
connections when there is no redundant link with the secondary unit. As soon as one
PROFINET device connection is established (and no secondary PROFINET device connection
exists) the Primary CPU can power-up in RUN mode. Otherwise, the Primary CPU powers-up
in STOP mode. If a PROFINET connection is established after the timeout period expires, the
standalone Primary CPU must be manually switched from STOP to RUN mode.
In comparison, the CRU320 waits 3 seconds during power-up before attempting to go to RUN,
which is not enough time to establish connections to its PROFINET devices. This means that a
standalone Primary CRU320 always powers up in STOP mode.
When running an OPC UA Server with a Limited Communications Window, the Server can
process enough requests to use the entire window which will add that time to your PLC Logic
sweep. For example, a 100 ms Limited Backplane Communications Window could add the full
100 ms to your PLC Logic Sweep. Caution should be taken to ensure the Communication
Window is configured within the tolerances of the system.
Secondary CPE330
Redundancy CPU
Power-up Wait Time
Using OPC UA Server
with Limited
Communications
Window
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
21
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
Description
When both CPE330s in a redundant system are powered on at the same time and perform a
Redundant Link
dual synchronization, it is possible for the secondary unit to log Redundant Link
Communication
Communication Failure faults if it completes power up before the primary unit. In this scenario,
Failure Fault During
these faults occur because the primary unit is not yet online and do not indicate a redundant
dual Synchronization
link failure. As soon as the primary unit completes power up it takes control and normal
system operation begins with the primary controlling I/O and the secondary in standby mode.
All RX3i CPUs
The following apply generically to any RX3i CPU:
SRTP or Modbus
Channel COMMREQ
Error Response with
Gateway
SRTP & Modbus TCP Channel commands on RX3i CPUs with embedded Ethernet
(IC695CPE3xx) and the IC695ETM001 RX3i Ethernet module provide different COMMREQ error
codes whenever a request is sent to an unreachable server. When an Ethernet gateway is
configured, the COMMREQ returns error code 0290H; when a gateway is not configured, the
COMMREQ returns error code AA90H.
Cannot Clear
Controller Passwords
Loaded in Flash
WARNING: Passwords loaded to Flash (including OEM Password) cannot be cleared using
clear Flash or by downloading new firmware. Users MUST document the password as it is not
possible for the user to restore a unit to the default, no passwords condition (NULL).
OEM Protection not
enforced on powerup from User Flash
unless engaged
before power cycle.
The OEM Protection Lock must be explicitly set before power down in order to ensure the OEM
lock will be set on power-up regardless of the type of security being used.
When passwords are
set with Enhanced
Security, connecting
with PME or
establishing SRTP
connections can
cause a temporary
increase in sweep
times.
Due to the complex math involved with Enhanced Security authentication, creating SRTP
connections and changing privilege levels will take additional sweep time (several
milliseconds) not required when passwords are set with legacy security. If consistent sweep
time is important to the application, then it is recommended to configure the sweep mode for
Constant Sweep. Alternately, Constant Window or a Normal Sweep with both Limited
Backplane Window and Limited Controller Comm Windows can be configured. These sweep
modes will limit the sweep impact of Enhanced Security authentication and result in
authentication processing across multiple sweeps.
C Toolkit Application
Compatibility
Beginning with Rel 7.00 of the C Toolkit, writes to %S memory will now fail to compile where in
previous releases a compilation warning was issued. This affects use of the GE-supplied
C Toolkit macros Sw(), Si(), and Sd().
For firmware version 6.70 and later, the RUN LED for remote/expansion racks will reflect the
current IO enable/disable state (even when there are no output modules in the expansion
rack).
RUN LED for remote/expansion rack with input modules only will work as follows for All
versions prior to version 6.70:
When a remote or expansion baseplate is used with the RX3i, the RUN LED on the Series 9030 power supply for that baseplate is illuminated when the system is in Run mode only if the
rack contains at least one output module. If the rack contains input modules only, the RUN
LED is not illuminated. This is due to the way input modules are managed in the PACSystems
design and does not indicate an error.
RUN LED is not
illuminated on the
Series 90-30 power
supply for an RX3i
remote/expansion
rack with input
modules only
Undefined Symbols in
C Blocks
In Release 5.00 or later, if an attempt is made to download a C block containing 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.
22
GFK-2942H
Subject
Slot numbering,
power supply
placement, CPU
placement and
reference
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
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 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.
User Logic
H/W
Configuratio
n
Fault Tables
External
Devices
Item Affected
Service Request #15
(Read Last-Logged
Fault Table Entry)
Service Request #20
(Read Fault Tables)
Communications
Request (COMMREQ)
CPU Slot location
Faults logged for the
CPU
How Affected
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.
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.
Slot location of the CPU must be updated in the HW
Configuration to reflect the CPU’s true location.
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)
Applications that utilize the Host Communications Toolkit may require updated drivers.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
23
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
Description
Machine Edition LD-PLC no longer supports a function that connects to the PLC, downloads,
LD-PLC operations
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.
Logic Executed in
Row Major instead of
Column Major
Logic execution in PACSystems RX3i is performed in row major order (similar to the Series 9030). This is different from the Series 90-70 that 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
S90-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 smoothes 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.
 Service Requests 6, 15, and 23 have slightly different parameters. Refer to PACSystems
RX7i & RX3i CPU Programmer's Reference Manual, GFK-2950.
 PACSystems PLCs support Service Request 26/30 functionality via fault locating
references.
 Service Request 13 requires a valid value in the input parameter block (Refer to
PACSystems RX7i & RX3i CPU Programmer's Reference Manual, GFK-2950 for details). On
the Series 90-30 and Series 90-70 the parameter block value was ignored.
 Service Requests 48 and 49 are no longer supported (there is no auto-restart) because
most faults can be configured to be not fatal.
IL and SFC are not available.
Some Service
Requests different
from 90-30 or no
longer supported
IL and SFC
DO I/O Instruction
The Series 90-30 Enhanced DO I/O instruction is converted to a standard DO I/O instruction
(the ALT parameter is discarded and ignored.)
END Instruction
The Series 90-30 END instruction is not supported. Alternate programming techniques should
be used.
Non-nested JUMP,
LABEL, MCR, &
ENDMCR
Instructions
Non-nested JUMPs, LABELs, MCRs, & ENDMCRs are translated to the corresponding nested
JUMPs, LABELs, MCRs, & ENDMCRs when converting from Series 90-30 to PACSystems RX3i.
Changing IP Address
of Ethernet Interface
while Connected
Storing a hardware configuration with a new IP Address to the RX3i while connected via
Ethernet will succeed, then immediately disconnect because the RX3i is now 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.
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.
24
GFK-2942H
Subject
Constant Sweep
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
Constant Sweep time, when used, should be set at least 10 ms 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
COMMREQs sent to
Module in one sweep
Causes Faults
A large number of COMMREQs (typically greater than 8) sent to a given board in the same
sweep may cause Module Software faults to be logged in the PLC fault table. The fault group is
MOD_OTHR_SOFTWR (16t, 10h) and the error code is COMMREQ_MB_FULL_START (2). When
this occurs, the FT output of the function block will also be set. To prevent this situation,
COMMREQs issued to a given board should be spread across multiple sweeps so that only a
limited number (typically 8 or less) of COMMREQs are sent to a given board 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 COMMREQ could be re-issued by the application logic.
C Block Standard
Math Functions Do
Not Set errno
In C Blocks, standard math functions (e.g. sqrt, pow, asin, acos) do not set errno to the correct
value and do not return the correct value if an invalid input is provided.
Hot Swap
Hot Swap of power supplies or CPUs is not supported
Run Mode Store of
EGD
RX3i peripheral Ethernet modules (IC695ETM001) must be running firmware version 6.00 or
greater to utilize the Run Mode Store of EGD feature.
Proper IP Addressing
is Always Essential
The PACSystems Ethernet Interface must be configured with the correct IP Address 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 PACSystems RX7i &
RX3i TCP/IP Ethernet Communications User Manual, 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 an 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.
Network
Architecture and
Overload
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.
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
The PACSystems RX3i does not log an exception or a fault in the PLC Fault Table when it
detects a duplicate IP Address on the network.
Reporting of
Duplicate IP Address
SRTP Connections
Remain Open after IP
Address Changed
The Ethernet Interface does not terminate all open SRTP connections before changing its
IP Address. Once the local IP Address has changed, any existing open TCP connections are
unable to normally terminate. This can leave SRTP connections open until their underlying TCP
connections time out.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
25
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
Description
Send Information
Send Information Report COMMREQ requests, with a minimum interval between host accesses
Report (COMMREQ
of 200 ms or less, may fail if issued from the CPU’s embedded Ethernet port. A COMMREQ
2010) requests may
Status Word value of 0290H, Period expired before transfer completed; still waiting on transfer
fail at minimum
indicates this condition occurred. To work around this issue, the user can set the minimum
intervals less than
interval between host accesses to a value greater than 200 ms if issuing a Send Information
200 ms from
Report COMMREQ from the embedded Ethernet port of the CPU.
embedded Ethernet
port.
Modbus/TCP Client
On CPUs with embedded Ethernet ports, a delay of at least 10 ms must occur between logicChannels require at
driven attempts to close sixteen Modbus/TCP Channels simultaneously and then re-open
least a 10 ms delay
sixteen Modbus/TCP Channels. This delay is necessary to provide external Modbus/TCP
between bulk
Servers sufficient time to close all channels before the Client issues channel open requests.
channel close and
bulk channel open
processing
Lengthy CPE
Some exceptionally lengthy CPE backplane operations, such as MC_CamTableSelect, Data Log,
Backplane
and Read Event Queue functions, will take longer to complete compared to other RX3i CPU
Operations
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 COMMREQ
The program name for PACSystems is always LDPROG1. When another program name is used
Status for Invalid
in a COMMREQ accessing %L memory, an Invalid Block Name (05D5) error is generated.
Program Name
Scansets on the master do not work properly for the first operation of the scanset after
FANUC I/O Master
entering RUN mode. They do work properly for subsequent scans.
and Slave operation
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.
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.
The Serial IO Processor (IC693APU305) will lose the first count after every power up or every
Lost count at power
time the module receives a config
up for Serial IO
Processor
COMMREQ Status
Words Declared in
Bit Memory Types
must be ByteAligned
In previous releases, the CPU allowed configuration of COMMREQ Status Words in bit memory
types on a non-byte-aligned boundary. Even though the given reference was not 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.
26
GFK-2942H
Subject
STOP and RUN Mode
Transition Priority
Suspend IO Function
Block does not
Suspend EGD
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
The PACSystems CPU receives requests to change between stop and run mode from 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 scenario 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 Service request 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.
In a S90-70 the SUSPEND_IO function block suspends EGD in addition to IO Scan.
In PACSystems controllers the SUSPEND IO only suspends IO Scan.
Nuisance Faults
Sometimes Logged
for Missing Power
Supply
If a power supply is missing or has some fault that makes it appear to be missing, the CPU may
improperly report (upon download of configuration) more than one fault. Such additional
faults may be safely ignored and will not occur in a properly configured rack (with no
mismatches or missing modules),
Uploaded Controller
Supplemental Files
lose date and time
Controller Supplemental Files uploaded from the CPU are time stamped as 8/1/1980 12:08AM
regardless of PC or PLC time.
CPU Parameters
Reset to Default
Values After
Replacing CPU
Module in PME
OPC UA Sessions,
Subscriptions, &
Variables
When replacing CPU modules in Proficy Machine Edition, some parameters may be reset to
default values. After replacing a CPU module, it is recommended that all parameters are
evaluated for application compatibility including the Controller Communication Window Mode,
Controller Communications Window Timer, Backplane Communication Window Mode, and
Backplane Communications Window Timer.
PACSystems OPC UA servers support up to five concurrent sessions with up to ten concurrent
variable subscriptions and up to 12,500 variables. The subscription limit is shared across all
available sessions.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
27
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
CPE330 Embedded PROFINET Controller:
Subject
Description
Embedded PNC Loading
To prevent overloading of the Embedded PNC, the maximum number of I/O Devices
Limits
that can be
configured is limited to the equivalent of two devices with update rates of 1 ms.
Devices configured with longer update periods present smaller data loads to the
Embedded PNC. For example, a device with an update rate of 2 ms is an equivalent
load as 2 devices at 4 ms.
The maximum number of devices allowed (up to 32) is determined by their update rates
as shown in the following calculation:
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝐷𝑒𝑣𝑖𝑐𝑒𝑠 𝑎𝑡 𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
𝑆𝑈𝑀 (
) ≤ 2 𝑑𝑒𝑣𝑖𝑐𝑒𝑠/𝑚𝑠
𝑈𝑝𝑑𝑎𝑡𝑒 𝑅𝑎𝑡𝑒 𝑥
Maximum Configuration at Each Update Rate
Update Rate (ms)
Total Number of Devices
1
2
2
4
4
8
8
16
16 – 512
32
If the configuration exceeds the equivalent of two devices with 1ms update rates,
Proficy Machine Edition will not store the configuration.
Minimum IO Update Rates
for Bumpless Operation in
a Ring Topology
If your application requires the PROFINET IO to operate bumplessly (no Loss of Device
faults and no defaulting of IO) through a break in the ring, then the IO Update Rates of
all of the devices in that ring must be no smaller than the Minimum IO Update Rate
described below.
When no third party items participate in the ring:
LAN 2 Ring
Ports
Both Ports
Operating at
100Mbps
Either Port
Operating at
1000Mbps
IO-Devices in the
ring
No RX3i PROFINET
Scanners
An RX3i PROFINET
Scanner using Ports 1
and 2 for the ring
Minimum IO
Update Rate
8ms
Additional Media Redundancy
Manager requirements
None
8ms
None
16ms
Set Default Test Interval to
10ms.
Set Test Monitoring Count to 2.
If any third party items participate in the ring, the minimum IO Update Rate is the
smallest IO Update Rate selectable within PME that is more than 1/3 of the largest
worst-case ring recovery time among the third party items. For example, if the
manufacturer states that the worst-case ring recovery time is 96ms, the rate needs to
be more than 96ms divided by 3, which is 32ms. The next available rate after 32ms is
64ms.
28
GFK-2942H
Subject
Maximum Number of
Nodes per Network Based
on Topology
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
For a network using MRP ring topology and an Embedded PNC as the MRP Ring
Manager, the maximum number of nodes is 32. (1 MRP Manager and 31 MRP clients)
For a network using star, line topology, or MRP Ring (Where the Embedded PNC is not
the MRP Ring Manager) the maximum number of nodes of the system is 264.
(Consisting of up to eight IC695PNC001 PROFINET Controllers and one CPE330
Embedded PNC plus up to 255 I/O-Devices)
Third-party MRP Manager
Use with PNC as
MRP Client
NOTE: A third-Party MRP Ring Manager may have limitations as to the number of MRP
Clients that it supports.
When using a third-party MRP Manager, it is recommended to set the MRP Manager
Test Monitoring Interval and Count to 10ms and 2 respectively and/or connect the PNC
client directly to a device that provides fast link down detection.
Not following these recommendations may result in degraded MRP Ring update
performance for bumpless operation due to the speed at which ring breaks are
detected. Use the table below as a guide when choosing not to follow the
recommendations.
Bumpless Operation Using Third-party MRP Manager Without Recommended Test
Monitoring Interval/Count
Ring Port Connection
Minimum Recommended I/O Update Rate
100Mbps
8ms
1000Mbps
64ms
Configuring Ethernet &
Embedded PROFINET
Controller Operation with
CPE330 LAN 2 Mode
Copying PROFINET
Configuration with PME
Default IC695PNC001
SFP Cage 3 & SFP Cage 4
Setting After Copying
PROFINET Configuration
The CPE330’s LAN 2 Ethernet ports may be configured for Ethernet or PROFINET
controller operation using the LAN 2 Mode parameter on the CPE330 hardware
configuration Settings tab in PME.
When LAN 2 is configured for Ethernet, these ports support SRTP Client/Server,
Modbus TCP Client/Server, OPC UA Server, and EGD. All PROFINET controller services
(Including Explore PROFINET Networks) are disabled when LAN 2 is configured for
Ethernet. Configuring LAN 2 for PROFINET retains standard Ethernet operation and
enables PROFINET controller services.
Proficy Machine Edition provides a PROFINET configuration cut / copy / paste function to
facilitate application portability between rack-based IC695PNC001 PROFINET
Controllers and the CPE330’s Embedded PROFINET Controller. Configuration may be
copied from a PNC001 to the CPE330 and from the CPE330 to a PNC001. This function is
available in PME by right clicking an IC695PNC001 or CPE330 PROFINET Controller node
in the Navigator and selecting cut / copy / paste.
The IC695PNC001 PROFINET Controller’s SFP Cage 3 and SFP Cage 4 settings may not
be restored to their default No SFP Device Configured value after copying a PROFINET
configuration from a CPE330 Embedded PROFINET Controller to the PNC001 using
Proficy Machine Edition. If this occurs, simply change the configuration value to the
desired setting.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
29
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
Description
Embedded PROFINET
The CPE330’s Embedded PROFINET Controller is able to detect that a network device
Controller Duplicate
has the same IP address as its own. When a duplicate IP address is detected, the
IP Address
Embedded PROFINET Controller behaves as follows.
IC695GCG001 Genius
Communication Gateway
COMMREQs
In each case, the system has an active PROFINET network with a PROFINET Controller
connected to at least one PROFINET Device:
1. If a second PROFINET Controller with an identical IP address to the active
PROFINET Controller is added to the network, the second controller will not
enter the network and will log a Duplicate IP Detected fault. The first Controller
will maintain all device connections.
2. If a device with an identical IP address to an active PROFINET Controller is
added to the network, the Controller will log a Duplicate IP Detected fault and
maintain all device connections.
3. If a device with an identical IP address to an active PROFINET Device is added
to the network, the Controller will log a Duplicate IP Detected fault and maintain
all device connections.
Both the CPE330’s Embedded PNC and the rack-based IC695PNC001 are able to send
Communication Requests (COMMREQs) to the IC695GCG001 RX3i Genius
Communication Gateway. When sending requests to the GCG001, the COMMREQ
function block inputs must be set as follows:
COMMREQ
Input
(enable)
IN
SYSID
Description
Permissive logic that controls power flow to the COMMREQ function block.
The memory location of the Command Block containing the specific
COMMREQ command information. The Command Block may be located in
any word–oriented area of memory (%P, %L, %R, %AI, %AQ, or %W).
A two-byte hex value that gives the rack and slot location of the controlling
PROFINET Controller. The rack number must be zero and occupies the
more significant byte; the slot number in which the IC695PNC001 or
IC695CPE330 PROFINET Controller is located occupies the less significant
byte. Example:
Rack#
0
TASK
PROFINET Command Line
Interface
Slot#
4
Resulting SysID Hex Word Value
0004h
The task is always “00084h” (hexadecimal) for the IC695PNC001
The task is always “20084h” (hexadecimal) for the IC695CPE330
The CPE330 Embedded PROFINET Controller does not support the Command Line
Interface. (CLI)
30
GFK-2942H
Subject
MRP Ring Ethernet Traffic
Storm Prevention
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Description
The CPE330’s LAN 2 Ethernet ports may be used as an MRP Ring Manager. (MRM) Since
LAN 2 defaults to be an Ethernet switch, it is required that the physical ring must not be
connected until a MRM configuration is stored to any Ethernet node on the ring
including the CPE330.
Failure to have an active MRM configured in an Ethernet ring will result in an Ethernet
traffic storm caused by the ring’s network loop topology. The Ethernet traffic storm will
prevent communication to all Ethernet nodes connected to the ring until the ring is
broken or an MRM is configured.
Storing Updated Media
Redundancy Protocol
(MRP) Configurations to
Large Operating MRP Ring
Networks with Fast IO
Update Rates Configured
Can Result in PROFINET IO
Device Loss/Add Faults
PROFINET IO Device
Loss/Add Faults for 3rd
Party IO Devices May
Occur on Hardware
Configuration Store in
Some Large Network
Configurations
PROFINET DCP – Direct
Connection indicates that
“no valid Ethernet
adapters are available for
PROFINET DCP discovery
(must run PME as
Administrator to use this
feature)”
The CPE330 maintains its MRM status after a hardware configuration clear until it is
power-cycled. After clearing the hardware configuration, and before power-cycling a
CPE330 that was configured as an MRM in a ring topology, it is recommended that
either:
a) The ring be broken by physically disconnecting an Ethernet port on any
network node in the ring, or
b) Any other network node in the ring be configured as a MRM.
When storing Media Redundancy Protocol (MRP) configuration updates to an operating
MRP ring network, users may infrequently observe one or more pairs of “Loss of
Device” and subsequent ”Addition of Device” faults regarding PROFINET IO Device
faults on the network. This is expected behavior and is more likely to occur on ring
networks with a large number of PROFINET IO Devices acting as Media Redundancy
Clients (MRC) with very fast IO Update Rates configured.
Because changing MRP configuration settings requires each MRC to break and
reconnect its own connections to the ring network, IP packets on the network may be
lost as this flurry of connection breaks/ reconnects occur on the network. Since a
PROFINET IO Device is considered lost if it misses 3 consecutive IO data transactions, if
3 consecutive IO data packets from a particular PROFINET IO Device are lost due to
network reconfiguration, the device will appear to be lost to the PNC and a Loss of IO
Device is logged. When the network stabilizes, the PNC will be able to reestablish
connection with the lost IO Device and an Addition of IO Device fault will be logged.
When storing hardware configurations with more than 64 PROFINET IO devices that
include multiple PROFINET controllers and 3rd Party PROFINET IO devices on a single
network, occasional Loss/Addition of IO Device faults may be logged for some 3rd Party
PROFINET IO Devices. The devices should operate normally after being reacquired by
their controlling PROFINET controller and the Loss/Addition faults can be disregarded.
The PME PROFINET DCP tool requires elevation to administrator privilege to run when it
is launched by right-clicking on a PNC. Since the PME installation does not setup PME or
any of its internal tools to run at the administrator privilege level, you will have to inform
Windows that you want it to run PME as an administrator. There are two ways do this:
1. Right click on the PME icon (and any other shortcuts associated with PME) and
select properties. Then select the Compatibility tab and check the checkbox for
“Run this program as an administrator.”
2. Right click on the PME icon and select properties. Then select the Advanced
button and check the checkbox “Run as administrator.” This method shows
“Run as administrator” in bold when you right click on the icon in the future.
You may also launch the PROFINET DCP tool from the Utilities tab menu in PME.
However, this launch method does not provide full functionality of the tool. That is, it
does not compare I/O devices found to any configuration in the PME Project. Also, if
PME was not launched as an administrator, this method of launching the DCP tool
requests the user’s permission to elevate access to administrator privilege.
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
31
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
GFK-2942H
Subject
Description
PNIO_DEV_COMM
The PNIO_DEV_COMM function block may require multiple logic scans to return the
Function Block Usage
status of an I/O device. It must continue to receive power flow until:
a)
b)
The ENO output turns on indicating that the function block’s parameters are
successfully validated and the PNC completed its first attempt to connect to
the specified I/O device or;
The OK output turns on indicating the PNC is successfully communicating with
the I/O device
32
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
GFK-2942H
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Product Documentation
PACSystems RX3i 1GHz 64MB CPU w/Ethernet IC695CPE330 Quick Start Guide
PACSystems RX7i & RX3i CPU Reference Manual
PACSystems RX7i & RX3i CPU Programmer's Reference Manual
PACSystems RX3i System Manual
PACSystems RX3i PROFINET IO Controller User Manual
PACSystems RXi, RX3i, and RX7i Controller Secure Deployment Guide
PACSystems RX7i & RX3i TCP/IP Ethernet Communications User Manual
PACSystems TCP/IP Ethernet Communications Station Manager Manual
PROFINET I/O Devices Secure Deployment Guide
PACSystems HART Pass Through User Manual
PACSystems Hot Standby CPU Redundancy User Manual
PACSystems Memory Xchange Modules User’s Manual
† Redundancy and PROFINET Updates Pending.
GFK-2941E
GFK-2222W†
GFK-2950
GFK-2314M†
GFK-2571E†
GFK-2830K
GFK-2224P
GFK-2225M
GFK-2904B
GFK-2929
GFK-2308K†
GFK-2300E†
User manuals, product updates and other information sources are available on the GE support website,
http://geautomation.com/support.
If you purchased this product through an Authorized Channel Partner, please contact the seller directly.
General Contact Information
Online technical support and GlobalCare
Additional information
Solution Provider
http://support.ge-ip.com
http://www.geautomation.com/
solutionprovider.ipatge.com
Technical Support
If you have technical problems that cannot be resolved with the information in this manual, please contact us by
telephone or email, or on the web at http://support.ge-ip.com
Americas
Online Technical Support
Phone
International Americas Direct Dial
Technical Support Email
Customer Care Email
Primary language of support
Europe, the Middle East, and Africa
Online Technical Support
Phone
EMEA Direct Dial
Technical Support Email
Customer Care Email
Primary languages of support
http://support.ge-ip.com
1-800-433-2682
1-780-420-2010 (if toll free 800 option is unavailable)
support.ipatge.com
customercare.ipatge.com
English
http://support.ge-ip.com
+800-1-433-2682
+420 239015850 (if toll free 800 option is unavailable or if
dialing from a mobile telephone)
support.emea.ipatge.com
customercare.emea.ipatge.com
English, French, German, Italian, Czech, Spanish
PACSystems* RX3i 1GHz 64MB CPU w/Ethernet
IC695CPE330-ABAJ, IC695CPE330CA-ABAJ
Asia Pacific
Online Technical Support
Phone
Technical Support Email
Customer Care Email
33
GFK-2942H
http://support.ge-ip.com
+86-400-820-8208
+86-21-3877-7006 (India, Indonesia, and Pakistan)
support.cn.ipatge.com (China)
support.jp.ipatge.com (Japan)
support.in.ipatge.com (remaining Asia customers)
customercare.apo.ipatge.com
customercare.cn.ipatge.com (China)
www.geautomation.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement