IC695CPE310-ACAT Network Communication and Ethernet Site Manager


IC695CPE310-ACAT firmware version 8.96 has added support for remote access to COMMREQ for HART device information.

Category: SKU: IC695CPE310-ACAT Tag:
Whatsapp:+86 15359293870
WeChat:+86 18106937731
Contacts:kelly CHEN


The internal FLASH drive that holds the firmware and backs up user data updated to a new vendor. This change address an issue in which a very small percentage of IC695CPE310 units may not properly power up after a power cycle.

In terms of time scheduling, PLC programs generally cannot run according to predetermined cycle times. The PLC program is executed from beginning to end and then from scratch. (Some new PLCs have been improved, but there are still limitations on the number of task cycles.) DCS can set task cycles. For example, fast tasks, etc. Similarly, for sensor sampling, the change time of the pressure sensor is very short. We can use a task cycle of 200ms for sampling, while the lag time of the temperature sensor is large. We can use a task cycle of 2s for sampling. In this way, DCS can reasonably schedule the resources of the controller.

From the perspective of network structure: Generally speaking, DCS commonly uses a two-layer network structure, with one layer being a process level network. Most DCS uses their own bus protocols, such as Yokogawa’s Modbus, Siemens and ABB’s Profibus, ABB’s CAN bus, etc. These protocols are all based on standard serial transmission protocols RS232 or RS485. The on-site IO module, especially the sampling data of analog quantities (machine code, 213/scan cycle), is very large, and there are many on-site interference factors. Therefore, network standards with high data throughput and strong anti-interference ability should be adopted. The bus structure based on RS485 serial port asynchronous communication mode meets the requirements of on-site communication. The sampling data of IO is converted by the CPU into shaped or real data, which is transmitted on the operation level network (second layer network). Therefore, the operation level network can adopt network standards with moderate data throughput, fast transmission speed, and convenient connection. At the same time, as the operation level network is generally arranged in the control room, the requirements for anti-interference are relatively low. Therefore, using standard Ethernet is the best choice. TCP/IP protocol is a standard Ethernet protocol that typically uses a communication speed of 100Mbit/s. The working task of a PLC system is relatively simple, so the amount of data that needs to be transmitted is generally not too large, so a common PLC system is a one layer network structure. The process level network and operation level network can either be merged together, or the process level network can be simplified into internal connections between modules. PLC does not or rarely uses Ethernet.

In terms of the scale of the application object, PLC is generally used in small automatic control places, such as equipment control or a small amount of analog control and interlocking, while large-scale applications are generally DCS. Of course, this concept is not very accurate, but it is very intuitive. Traditionally, we refer to systems larger than 600 points as DCS, and systems smaller than this scale as PLCs. Our control system for heat pumps, QCS, and horizontal products is generally referred to as PLC. Having said so much about the differences between PLC and DCS, we should realize that with the development of PLC and DCS to this day, they are actually moving closer to each other. Strictly speaking, nowadays, PLC and DCS can no longer be cut in one go, and the concept between them is often blurred. Now, let’s discuss the similarities (similarities) between each other.


IC695CPE310-ABAR 8.65 Firmware release 8.65 resolves security and OPC UA issues.
IC695CPE310-ABAP 8.50 Support for RX3i HART Pass Through feature.
IC695CPE310-ABAN 8.30 Adds support for EGD Class 1 on Embedded Ethernet Interface.
IC695CPE310-ABAM 8.20 Adds support for OPC UA.
IC695CPE310-ABAL 8.15 Adds support for IC695RMX228 (128 MB Reflective Memory Module with Single Mode Transceiver.)
Adds ability to read reflective memory status bits for IC695CMX128, IC695RMX128, and IC695RMX228 (reflective memory modules).
Adds enhanced Ethernet diagnostics capabilities.
IC695CPE310-ABAK 8.05 Adds support for the new IC695ECM850 (IEC 61850 Ethernet Communication Module), which operates as an IEC 61850 Client and provides connectivity to IEC 61850 Server devices.
Resolves three issues detailed in PACSystems RX3i CPU IC695CPE310-ABAK IPI, GFK-2713K.
IC695CPE310-ABAJ 7.80 Resolves the following issues:
 Unable to enter existing CPU password after Enhanced Security enabled.
 The PNC0001 fails to reconnect after remote IO power loss.
 The PBM300 stops responding after SUS_IO instruction executed.
IC695CPE310-ABAH 7.75 Corrects issues with the OEM lock functionality and with Ethernet communications. Adds support for RX3i CMX/RMX modules version –CG (hardware version Cx with firmware version 2.00 and later).
For details, see PACSystems RX3i CPU IC695CPE310-ABAH IPI, GFK-2713H.
IC695CPE310-ABAG 7.70 Adds support for the following new modules: IC694MDL758, IC695CNM001 and
IC694PSM001. Refer to PACSystems RX3i CPU IC695CPE310-ABAG IPI, GFK-2713G for issues resolved.
IC695CPE310-ABAF 7.30 Adds support for Modbus/TCP Server, Modbus/TCP Client, SRTP Server, and SRTP Channels from the embedded Ethernet port. For details, refer to PACSystems RX7i & RX3i TCP/IP Ethernet Communications User Manual, GFK-2224L or later.