IC695PNC001 RX3i PROFINET controller – GE

Description

IC695PNC001 PACSystems RX3i PROFINET Controller Module 10/100/1000, 4 Ports – 2 SFP connections, 2 Copper
IC200PNS001 VersaMax PROFINET Scanner, 10/100, 2 Ports, Copper
IC200PNS002 VersaMax PROFINET Scanner, 10/100, 2 Ports, Multimode Fiber
IC695SPC100** RX3i 10/100/1000base-TX (CAT5 100m) SFP
IC695SPF002** RX3i 100Base-FX (fiber 2 km) SFP

Use of the Media Redundancy Protocol (MRP) allows a user’s ring network to automatically heal itself in the event of a single break of the ring network. If a user’s application requires the PROFINET IO Devices to operate bumplessly through ring network recovery (no observed loss and subsequent addition of PROFINET IO Devices while the ring network recovers), the following network and application design guidelines must be observed:

1. If only one PNC is in the ring acting as the Media Redundancy Manager (MRM) and all of the Media Redundancy Clients (MRCs) are VersaMax PROFINET Scanners, customers can set minimum IO Update Rates as follows and expect PROFINET IO to operate bumplessly through ring network recovery:

▪ Using the fixed copper ring ports on the PNC, 1 ms IO Update Rate minimum

▪ Using SFPs on the PNC, 4 ms IO Update Rate minimum

2. If multiple PNCs are in the ring (one PNC acting as the MRM and other PNC(s) as MRC(s)) where VersaMax ROFINET Scanners are the only PROFINET IO Devices, customers can set minimum IO Update Rates as follows and expect IO to operate bumplessly through ring network recovery:

▪ 16 ms IO Update Rate minimum, regardless of ports utilized, and must set MRP Test Packet Interval to 10 ms and MRP Test Packet Count to 2.

3. If 3rd party MRCs are in use in the ring, customers can set a minimum IO update rate to the larger of the options that follow and expect IO to operate bumplessly through ring network recovery:

▪ Minimum IO Update Rate configurable in PME that is at least 1/3 the time of the worst-case ring recovery stated by 3rd party manufacturer, regardless of ports utilized. (i.e. if a manufacturer states their worst-case ring recovery is 90 ms, then the minimum IO update rate allowed would be 90/3 = 30 ms ~ 32ms.) or

▪ 16 ms IO Update Rate minimum, regardless of ports utilized, and must set MRP Test Packet Interval to 10 ms and MRP Test Packet Count to 2.

It has been nearly 30 years since the emergence of the old DCS, and during these 30 years, the development of computer technology and network technology can be said to be rapidly changing, with new products being launched on the market almost every day. For industrial control systems, regardless of the generation claimed, their system structure is relatively stable. A system can operate for at least 15 years.
Compared to the controller, network, and human-machine interface (mainly the operator station) of DCS, the damage rate of human-machine interface is higher. Because the hard drive of the operator station has moving parts, it is prone to malfunctions. For example, multiple operations by keyboards and operators can easily damage CRT24 hours of continuous operation. In addition, its electromagnetic characteristics determine its shorter lifespan. During the lifecycle of DCS, the operator station must be replaced once. If not replaced, keep the DCS that has been running for 7-8 years. There are too many operator station faults, and the purchase price of hard drives and CRTs is high, which is sometimes difficult to buy. Throwing it away as a whole and turning millions of investments into nothing feels too regrettable. Not only that, but with technological advancements, users also need to make operator station modifications.

Before the 1990s, DCS, whether it was the operator station, controller, or network hardware and software, were all developed by the DCS manufacturer themselves, which means they were all dedicated. The display software, database, and driver software of the operator station are not designed as modules, and the display and driver of the controller are intertwined. Due to the large number of tags that need to be controlled and displayed for certain controlled objects, a 300MW power plant can have over 8000 tags. The originally designed operator station host cannot meet the needs in terms of CPU computing speed and memory storage capacity. If you design the operator host yourself, you will invest too much. Secondly, after the design is completed, it may not necessarily meet the requirements. When the original label quantity was low, the host designed by oneself could work and was connected to the operator station using a serial port. Later on, the number of tags increased, and the serial connection no longer worked.

After the 1990s, some manufacturers began to use general-purpose computers for their DCS operator stations, such as SUN and DEC small computers. The connection between the DCS dedicated network interface and the operator station adopts the SCSI (small computer system interface) bus. The transmission speed from the interface to the operator station host has greatly increased.