IC695PNS001 PROFINET scanner module hot swappable


Series model:

Category: SKU: IC695PNS001 Tag:
Whatsapp:+86 15359293870
WeChat:+86 18106937731
Contacts:kelly CHEN


The PACSystems* RX3i PROFINET Scanner (PNS) module, IC695PNS001, connects a remote universal RX3i I/O rack of Series 90-30 or RX3i modules to a PROFINET I/O Controller. The PROFINET Scanner scans the modules in its rack, retrieving input data and providing output data, and exchanges that data on the PROFINET I/O LAN at the configured production rate.

The PNS manages PROFINET communication and module configuration between an I/O Controller and modules in the remote rack. If network communications are lost, the PNS manages I/O states according to the individual module configurations.

The PNS supports 10/100/1000 Mbps Copper, 100/1000 Mbps Multi-mode Fiber, and 100/1000 Mbps Single-mode Fiber. PROFINET communications on the network require 100 or 1000 Mbps link speed. Although 10 Mbps cannot be used for PROFINET communications, 10 Mbps can be used for other types of Ethernet traffic such as PING.

Features of the RX3i PNS include:

▪ Programming and configuration services for all supported Series 90-30 and RX3i I/O Modules using Proficy Machine Edition. For a list of currently supported I/O modules, refer to “Supported Modules, Power Supplies and Backplanes,” on pages 9-12.

▪ Support for daisy-chain/line, star, or ring (PROFINET Media Redundancy Protocol (MRP)) topologies.

▪ Four switched Ethernet ports – two 8-conductor RJ-45 shielded twisted pair 10/100/1000 Mbps copper interfaces and two Small Form-factor Pluggable (SFP) cages for user-supplied SFP devices.

▪ The network can include media interfaces of more than one type.

▪ Support for transfer of I/O Device Name to another PNS module using an SD card. This eliminates the need to connect a configuration tool, such as Proficy Machine Edition when replacing a module.

▪ A USB port for field updates of firmware using WinLoader.

Note: The USB port is for firmware upgrades only. It is not intended for permanent connection.

Ordering Information:

IC695PNS001 PACSystems RX3i PROFINET Scanner Module 10/100/1000 with four Ports (two SFP connections, two Copper) Includes a blank SD card, two mounting screws and a USB port cover.
IC695SPC100 RX3i 10/100/1000Base-T copper SFP
IC695SPF002 RX3i 100Base-FX (fiber 2 km) SFP (Multi-mode fiber – MMF)
IC695SPF550 RX3i 1000Base-SX (fiber 550 m) SFP (MMF)
IC695SPF010 RX3i 1000Base-LX (fiber 10 km) SFP (Single-mode fiber – SMF)


The technical characteristics and mutual penetration of DCS and PLC:
Different conceptual foundations and development paths result in DCS and PLC having their own unique technical characteristics, and the development of technology is not closed, and mutual learning and infiltration always run through the development process.

Control processing capability:
We know that a PLC controller can often handle thousands of I/O points (up to over 8000 I/Os). The controller of DCS can generally only handle hundreds of I/O points (no more than 500 I/Os). Is it because the technical level of DCS developers is too poor? I’m afraid not. From the requirements of a distributed system, it is not allowed to have centralized control. Controllers with too many points are useless in practical applications. DCS developers do not need to drive controllers with many I/O points, and their main focus is on providing the system with reliability and flexibility. PLC, on the other hand, is different. As an independent flexible control device, the stronger the point capability, the higher its technical level. As for the application level of the entire control system, this is mainly a matter for engineering companies and users, rather than the core goal of PLC manufacturers.

Another indicator of control processing ability, the calculation speed, is also much faster in people’s impression than DCS. From a certain perspective, the situation is indeed the same. The efficiency of PLC executing logic operations is very high, with less than 1 millisecond of executing 1K logic programs. Its control cycle (taking DI input directly sending DO output as an example) can be controlled within 50ms; DCS, on the other hand, uses the same method for handling logical and analog operations, with a control cycle often exceeding 100ms. When we use the PID algorithm to compare, we can find that the PLC performs a PID operation in a few milliseconds, and the T2550 controller of NETWORK 6000+DCS also takes 1 millisecond to solve a PID. This indicates that the computing power of PLC and DCS is equivalent to the actual operation, and a certain type of DCS controller is even stronger. The difference in control cycle is mainly related to the scheduling design of the controller. Large PLCs often use auxiliary CPUs to complete analog operations, while the main CPU completes switch operations at high speed. Therefore, even if the analog operation speed is average, the speed performance in switch control is still very excellent. However, when DCS processes switching and analog operations at the same speed, the control cycle index is indeed not ideal. The new DCS controller has learned the design of large PLCs and achieved significant improvement in control cycle performance. Taking the T2550 controller of NETWORK 6000+DCS as an example. The controller can set four tasks with different priorities, and the minimum calculation cycle can be set to 10ms. With high-speed I/O cards, the control cycle can reach 15-20ms. And analog operations are set in other tasks with longer cycles.