Description
9662-610 Safety Instrumented System (SIS)
9662-610 Safety Instrumented System (SIS)
Module Clips Drive controller servo motor
Contact: Mr. Lai
Wechat:17750010683
Whats app:+86 17750010683
Skype:+86 17750010683
QQ: 3221366881
3221366881@qq.com
How to Build High Channel Density Digital IO Modules for the Next Generation Industrial Automation Controllers
With the rapid development of industrial automation, digital IO modules have become an indispensable part of industrial automation controllers. The digital IO module can connect the controller with external devices, such as sensors, actuators, etc., to achieve monitoring and control of industrial production processes. However, with the continuous development of industrial automation, digital IO modules need to have higher channel density and stronger functionality to meet the needs of new industrial automation controllers. Therefore, it is very important to build high channel density digital IO modules for the next generation of industrial automation controllers.
The digital IO module is one of the most fundamental modules in industrial automation controllers, and its main function is to connect the controller with external devices to achieve signal input and output. The digital IO module usually includes two parts: a digital input module and a digital output module. The digital input module can convert the digital signals of external devices into signals that the controller can read, while the digital output module can convert the digital signals output by the controller into signals that external devices can read. The channel density of a digital IO module refers to the number of digital input or digital output channels provided on the module, which is the input and output capacity of the module.
With the development of industrial automation, digital IO modules need to have higher channel density and stronger functions to meet the needs of new industrial automation controllers. The following are several aspects to consider when building a high channel density digital IO module for the next generation of industrial automation controllers:9662-610 Safety Instrumented System (SIS)
1. Choose the appropriate communication protocol
Digital IO modules typically communicate with controllers through communication protocols, so choosing a suitable communication protocol is crucial. Common communication protocols include Modbus, Profibus, CANopen, Ethernet, etc. Different communication protocols have different advantages and disadvantages, and selecting a suitable communication protocol requires considering the following factors:
(1) Communication speed: The faster the communication speed, the shorter the response time of the digital IO module, which can process input and output signals faster.
(2) Communication distance: The farther the communication distance, the wider the application range of digital IO modules.
(3) Reliability: The reliability of communication protocols determines the stability and reliability of digital IO modules.
(4) Cost: Different communication protocols have different costs, and suitable communication protocols need to be selected based on actual needs.
2. Choose the appropriate digital IO chip
The digital IO chip is the core component of the digital IO module, and its performance and function directly affect the channel density and function of the digital IO module. Choosing a suitable digital IO chip requires considering the following factors:
(1) Channel density: The channel density of digital IO chips determines the channel density of digital IO modules, and channel density needs to be selected based on actual needs.
(2) Input/output type: Digital IO chips usually support digital input and digital output, and some chips also support functions such as analog input and output, counters, etc.
(3) Speed: The speed of the digital IO chip determines the response speed of the digital IO module, and it is necessary to choose a chip with a faster speed.
(4) Accuracy: The accuracy of digital IO chips determines the signal accuracy of digital IO modules, and it is necessary to choose chips with higher accuracy.
(5) Cost: Different digital IO chips have different costs, and suitable chips need to be selected based on actual needs.
3. Optimize circuit design
The circuit design of digital IO modules has a significant impact on their performance and stability. In order to improve the channel density and functionality of digital IO modules, it is necessary to optimize circuit design, such as:
(1) Using high-speed digital IO chips: Using high-speed digital IO chips can improve the response speed and accuracy of the module.
(2) Adopting anti-interference design: In order to improve the stability of the digital IO module, it is necessary to adopt anti-interference design, such as using filters, isolators, etc.
(3) Using optimized PCB layout: Optimizing PCB layout can reduce noise and interference in digital IO modules, improve module performance and stability.
4. Choose the appropriate shell material and size
Digital IO modules typically need to be installed in cabinets or control cabinets, so choosing the appropriate housing material and size is crucial. The shell material should have good protective and heat dissipation properties to protect the circuits of the digital IO module from external environmental influences. The shell size should be able to adapt to different installation environments, such as cabinets, control cabinets, etc.
5. Optimize software design
The software design of the digital IO module determines its functionality and performance. In order to achieve high channel density and stronger functionality, it is necessary to optimize software design, such as:
(1) Supporting multiple input and output types: Supporting multiple input and output types can meet different application needs, such as digital input and output, analog input and output, counters, etc.
(2) Supporting multiple communication protocols: Supporting multiple communication protocols can adapt to different controllers and application environments.
(3) Support for online debugging and monitoring: Supporting online debugging and monitoring can facilitate user diagnosis and maintenance of modules.
(4) Support for expansion function: Supporting expansion function can increase the functionality and application range of the module while ensuring channel density.
In summary, building a high channel density digital IO module for the next generation of industrial automation controllers requires multiple considerations, including selecting suitable communication protocols, selecting suitable digital IO chips, optimizing circuit design, selecting suitable shell materials and sizes, and optimizing software design. Only by comprehensively considering these factors can a digital IO module with high channel density and stronger functionality be constructed to meet the needs of new industrial automation controllers.
How to assign IO devices to IO controllers?
PROFINET IO system
The PROFINET IO system consists of a PROFINET IO controller and its assigned PROFINET IO devices. After adding IO controllers and IO devices, it is necessary to assign IO controllers to the IO devices to form a basic PROFINET IO system.
Prerequisite requirements
● Already in the network view of STEP 7.
A CPU has been placed (e.g. CPU 1516-3 PN/DP).
● An IO device has been placed (e.g. IM 155-6 PN ST)
Operating Steps (Method 1)
To assign IO devices to IO controllers, follow these steps:
1. Move the mouse pointer over the interface of the IO device.
2. Hold down the left mouse button.
3. Drag the mouse pointer.
The pointer will now use the networking symbol to indicate the “networking” mode. At the same time, you can see a lock character appearing on the pointer
Number. The lock symbol only disappears when the pointer moves to a valid target position.
4. Now, move the pointer to the interface of the desired IO controller and release the left mouse button.
5. Now assign the IO device to the IO controller.
Operating Steps (Method 2)
To assign IO devices to IO controllers, follow these steps:
1. Move the mouse pointer over the word “Unassigned” in the bottom left corner of the IO device icon.
2. Click the left mouse button.
3. Select the IO controller interface to be connected from the available interfaces that appear.
4. Now assign the IO device to the IO controller.
What are the advantages of Ethernet remote IO modules that can be cascaded?
Advantages and specific application scenarios of Ethernet remote IO modules that can be cascaded
For scenarios where data collection control points are linearly distributed, such as streetlights, bridges, streetlights, digital factories, parking lot parking monitoring, smart parking lots, smart parking racks, and building automation control systems in smart parks, using cascading dual Ethernet remote IO modules saves more costs than using single Ethernet remote IO modules.
The Ethernet remote IO module that can be cascaded is a new type of Ethernet remote IO module that supports MAC layer data exchange and can achieve hand in hand connection. This not only saves switch interfaces, but also reduces a large amount of Ethernet cable costs, wiring space, and wiring costs.
Its advantages are as follows:9662-610 Safety Instrumented System (SIS)
1. No need for a large number of Ethernet switches or occupying Ethernet switch ports;
2. It can save a lot of Ethernet cables, cable space, and labor costs for installing cables;
3. The overall cost has significantly decreased;
4. Supports both Modbus RTU protocol, Modbus TCP protocol, and the Internet of Things protocol MQTT protocol;
5. Support TCP Server and TCP Client services;9662-610 Safety Instrumented System (SIS)
6. Can be connected to SCADA systems, PLC systems, or cloud platforms;
7. The series uses a MAC layer for data exchange, ensuring that network connectivity does not cause communication issues with subsequent devices due to device failures in the middle.
The comparison between cascaded Ethernet remote IO modules and traditional IO modules used in building automation systems is shown in the following figure:
1. Adopting a cascaded dual Ethernet remote IO module, data acquisition and control wiring for floors with a height of 70 meters only requires a 70 meter Ethernet cable;
2. Using a traditional single Ethernet remote IO module, the data acquisition and control system wiring for a 70 meter high floor requires a 280 meter Ethernet cable.
It can be seen that using cascaded dual Ethernet remote IO modules can save a lot of wiring costs compared to traditional single Ethernet remote IO modules.
Application of Ethernet Remote IO Module in Building Automation System
For building automation systems, each data acquisition control point is linearly distributed in each floor. Therefore, it is very suitable to use Ethernet remote IO modules that can be cascaded to achieve data acquisition and control.
The Ethernet remote IO module that can be cascaded supports MAC layer data exchange and can achieve a hand in hand connection method. This can not only save switch interfaces, but also reduce a large amount of Ethernet cable costs, wiring space, and wiring costs.
Its advantages are as follows:
1. No need for a large number of Ethernet switches or occupying Ethernet switch ports;
2. It can save a lot of Ethernet cables, cable space, and labor costs for installing cables;
3. The overall cost has significantly decreased;
4. The M160E supports both Modbus RTU protocol, Modbus TCP protocol, and the Internet of Things protocol MQTT protocol. In addition, it also supports TCP Server and TCP Client services; Can be connected to SCADA systems, PLC systems, or cloud platforms;
4. The M160E series uses a MAC layer for data exchange, ensuring that network connectivity does not cause communication issues with subsequent devices due to device failures in the middle.
Comparison between cascaded Ethernet remote IO modules and traditional IO modules for building automation systems:
1. Adopting a cascaded dual Ethernet remote IO module, data acquisition and control wiring for floors with a height of 70 meters only requires a 70 meter Ethernet cable;
2. Using a traditional single Ethernet remote IO module, the data acquisition and control system wiring for a 70 meter high floor requires a 280 meter Ethernet cable.
Therefore, we can conclude that for scenarios where data collection control points are linearly distributed, such as streetlights, bridges, streetlights, digital factories, parking lot parking monitoring, smart parking lots, smart parking racks, and building automation systems in smart parks, using cascading dual Ethernet remote IO modules saves more costs than using single Ethernet remote IO modules.
Modify the watchdog time of the PROFINET IO device under 16 STEP7
3.2 Check if the installation of PROFINET IO communication equipment meets the specifications
Most cases of PROFINET IO communication interference problems are caused by equipment installation that does not comply with the installation specifications for PROFINET IO communication, such as incomplete shielding, unreliable grounding, and being too close to interference sources. Installation that meets the specifications can avoid communication failures caused by electromagnetic interference. You can refer to the following brief installation requirements for PROFINET:
1. Wiring of PROFINET 9662-610 Safety Instrumented System (SIS)
In order to reduce the coupling of electric and magnetic fields, the larger the parallel distance between PROFINET and other power cable interference sources, the better. In accordance with IEC 61918, the minimum distance between PROFINET shielded cables and other cables can be referred to Table 1. PROFINET 9662-610 Safety Instrumented System (SIS) can be wired together with other data cables, network cables, and shielded analog cables. If it is an unshielded power cable, the minimum distance is 200mm.
Comprehensive analysis of the principle and application skills of microcontroller IO port
IO port operation is the most basic and important knowledge in microcontroller practice. This article takes a long time to introduce the principles of IO ports. I also consulted a lot of materials to ensure the accuracy of the content, and spent a long time writing it. The principle of IO ports originally required a lot of in-depth knowledge, but here it has been simplified as much as possible for easy understanding. This will be of great help in solving various IO port related problems in the future.
The IO port equivalent model is my original method, which can effectively reduce the difficulty of understanding the internal structure of the IO port. And after consulting and confirming, this model is basically consistent with the actual working principle.
I mentioned a lot earlier, and many people may already be eager to actually operate microcontrollers. The IO port, as the main means of communication between the microcontroller and the outside world, is the most basic and important knowledge for microcontroller learning. Previously, we programmed and implemented an experiment to light up the LED at the IO port. This article will continue to introduce the relevant knowledge of the IO port.
In order to better learn the operation of IO ports, it is necessary to understand the internal structure and related concepts of IO ports. These knowledge are very helpful for subsequent learning, with a focus on understanding and no need to memorize them intentionally. If you don”t remember, just come back and take a look. If you use it too much, you will naturally remember.
We have said that the most accurate and effective way to understand a chip is to refer to official chip manuals and other materials. But for beginners of microcontrollers, it may be difficult to understand the chip manual directly, especially when they see a bunch of English, unfamiliar circuits, and terminology. If it were me, I would definitely be crazy. But here I still provide a picture taken from Atmel”s official “Atmel 8051 Microcontrollers Hardware Manual”.
The purpose of giving this picture is not to dampen everyone”s enthusiasm for learning, but to help everyone understand how the various microcontroller materials we have seen come from and whether they are accurate. All of these can be clarified through official information, which will be helpful for everyone to further learn something in the future.
Introduction to the Second Function
The above figure is the authoritative 51 microcontroller IO port structure diagram provided by the official. It can be seen that the internal structure of the four sets of IO ports of the microcontroller is different, because some IO ports have a secondary function, as mentioned in the introductory section.
Do you remember this pin diagram? The second function name of the IO port is marked in parentheses. Except for P1, each interface has a second function. When introducing the microcontroller system module, I mentioned that the 51 microcontroller has an interface for reserved extended memory, which is the second function of P0 and P1 in the figure (while also using pins such as 29 and 30). Because it is not widely used and involves in-depth knowledge, no specific research will be conducted. By the way, the AD0~AD7 we see here are actually used for parallel ports. The second function of the P3 port, including serial port, will be introduced in detail later.
The drawbacks of network IO and the advantages of multiplexing IO
In order to talk about multiplexing, of course, we still need to follow the trend and adopt a whiplash approach. First, we will talk about the drawbacks of traditional network IO and use the pull and step method to grasp the advantages of multiplexing IO.
For the convenience of understanding, all the following code is pseudo code, and it is sufficient to know the meaning it expresses.
Blocking IO
The server wrote the following code to handle the data of client connections and requests.
Listenfd=socket()// Open a network communication port
Bind (listenfd)// binding
Listen (listenfd)// Listening while (1){
Connfd=accept (listenfd)// Blocking connection establishment
Int n=read (connfd, buf)// Blocking read data
DoSomeThing (buf)// What to do with the data you read
Close (connfd)// Close the connection and wait for the next connection in a loop
}
This code will be executed with stumbling blocks, just like this.
It can be seen that the thread on the server is blocked in two places, one is the accept function and the other is the read function.
If we expand on the details of the read function again, we will find that it is blocked in two stages.
This is traditional blocking IO.
The overall process is shown in the following figure.
So, if the client of this connection continues to not send data, the server thread will continue to block on the read function and not return, nor will it be able to accept other client connections.
This is definitely not feasible.
Non blocking IO
To solve the above problem, the key is to modify the read function.
A clever approach is to create a new process or thread every time, call the read function, and perform business processing.
While (1){
Connfd=accept (listenfd)// Blocking connection establishment
Pthread_ Create (doWork)// Create a new thread
}
Void doWork(){
Int n=read (connfd, buf)// Blocking read data
DoSomeThing (buf)// What to do with the data you read
Close (connfd)// Close the connection and wait for the next connection in a loop
}
In this way, once a connection is established for a client, it can immediately wait for a new client connection without blocking the read request from the original client.
However, this is not called non blocking IO, it just uses multithreading to prevent the main thread from getting stuck in the read function and not going down. The read function provided by the operating system is still blocked.
So true non blocking IO cannot be achieved through our user layer tricks, but rather by imploring the operating system to provide us with a non blocking read function.
The effect of this read function is to immediately return an error value (-1) when no data arrives (reaches the network card and is copied to the kernel buffer), rather than waiting for blocking.
The operating system provides this feature by simply setting the file descriptor to non blocking before calling read.
Fcntl (connfd, F_SETFL, O_NONBLOCK);
Int n=read (connfd, buffer)= SUCCESS;
In this way, the user thread needs to loop through the call to read until the return value is not -1, and then start processing the business.
We noticed a detail here.
Non blocking read refers to the stage where data is non blocking before it reaches the network card, or before it reaches the network card but has not been copied to the kernel buffer.
When the data has reached the kernel buffer, calling the read function is still blocked and requires waiting for the data to be copied from the kernel buffer to the user buffer before returning.
The overall process is shown in the following figure
IO multiplexing
Creating a thread for each client can easily deplete the thread resources on the server side.
Of course, there is also a clever solution. After accepting each client connection, we can put the file descriptor (connfd) into an array.
Fdlist. add (connfd);
Then create a new thread to continuously traverse the array and call the non blocking read method for each element.
While (1){
For (fd “- fdlist){
If (read (fd)!=- 1){
DoSomeThing();
}
}
}
In this way, we successfully processed multiple client connections with one thread.
Do you think this means some multiplexing?
But this is just like using multithreading to transform blocked IO into seemingly non blocking IO. This traversal method is just a small trick that our users have come up with, and every time we encounter a read that returns -1, it is still a system call that wastes resources.
Making system calls in a while loop is not cost-effective, just like making rpc requests while working on distributed projects.
So, we still need to plead with the operating system boss to provide us with a function that has such an effect. We will pass a batch of file descriptors to the kernel through a system call, and the kernel layer will traverse them to truly solve this problem.
PXI-2533
CROO-9104
CRLO-9012
CRKO-9104
CRJO-9042
CRJO-9022
CRIO-P048
CRIO-P004
CRIO-O104
CRIO-O022
cRIO-FRC
CRIO-9Q04
CRIO-9P33
CRIO-9O33
cRIO-9958
cRIO-9939
cRIO-9937
cRIO-9803
cRIO-9148
cRIO-9116
cRIO-9114
cRIO-9113
cRIO-9112
cRIO-9111
cRIO-9103
cRIO-9102
cRIO-9101
CRIO-90T8
CRIO-90E2
cRIO-9082
cRIO-9081
cRIO-9076
cRIO-9075
cRIO-9074
cRIO-9073
cRIO-9068
cRIO-9067
cRIO-9066
cRIO-9065
cRIO-9064
cRIO-9063
cRIO-9058
cRIO-9057
cRIO-9056
cRIO-9055
cRIO-9054
cRIO-9053
CRIO-904W
CRIO-904Q
cRIO-9049
cRIO-9048
cRIO-9047
cRIO-9046
cRIO-9045
cRIO-9043
cRIO-9042
cRIO-9041
cRIO-9040
cRIO-9039
cRIO-9038
cRIO-9037
cRIO-9036
cRIO-9035
cRIO-9034
cRIO-9033
cRIO-9032
cRIO-9031
cRIO-9030
cRIO-9025
cRIO-9024
cRIO-9023
cRIO-9022
cRIO-9014
cRIO-9012
CRIO-900R
cRIO-9004
cRIO-9002
CRII-9104
CRII-9004
cRI0-9118
cRI0-9116
cRI0-9113
cRI0-9112
cRI0-9104
cRI0-9103
cRI0-9025
CRAQ-9179
GPIB-140A 186135G-01
NI-9853
1.Has been engaged in industrial control industry for a long time, with a large number of inventories.
2.Industry leading, price advantage, quality assurance
3.Diversified models and products, and all kinds of rare and discontinued products
4.15 days free replacement for quality problems
ABB — AC 800M controller, Bailey, PM866 controller, IGCT silicon controlled 5SHY 3BHB01 3BHE00 3HNA00 DSQC series
BENTLY — 3500 system/proximitor, front and rear card, sensor, probe, cable 3500/20 3500/61 3500/05-01-02-00-001 3500/40M 176449-01 3500/22M 138607-01
Emerson — modbus card, power panel, controller, power supply, base, power module, switch 1C31,5X00, CE400, A6500-UM, SE3008,1B300,1X00,
EPRO — PR6423 PR6424 PR6425 PR6426 PR9376 PR9268 Data acquisition module, probe, speed sensor, vibration sensor
FOXBORO — FCP270 FCP280 FCM10EF FBM207 P0914TD CP40B FBI10E FBM02 FBM202 FBM207B P0400HE Thermal resistance input/output module, power module, communication module, cable, controller, switch
GE —- IS200/215/220/230/420 DS200/215 IC693/695/697/698 VMICPCI VMIVME 369-HI-R-M-0-0-E 469 module, air switch, I/O module, display, CPU module, power module, converter, CPU board, Ethernet module, integrated protection device, power module, gas turbine card
HIMA — F3 AIO 8/4 01 F3231 F8627X Z7116 F8621A 984862160 F3236 F6217 F7553 DI module, processor module, AI card, pulse encoder
Honeywell — Secure digital output card, program module, analog input card, CPU module, FIM card
MOOG — D136-001-007 Servo valve, controller, module
NI — SCXI-1100 PCI – PXIE – PCIE – SBRIO – CFP-AO-210 USB-6525 Information Acquisition Card, PXI Module, Card
Westinghouse — RTD thermal resistance input module, AI/AO/DI/DO module, power module, control module, base module
Woodward — 9907-164 5466-258 8200-1300 9907-149 9907-838 EASYGEN-3500-5/P2 8440-2145 Regulator, module, controller, governor
YOKOGAWA – Servo module, control cabinet node unit
Main products:
PLC, DCS, CPU module, communication module, input/output module (AI/AO/DI/DO), power module, silicon controlled module, terminal module, PXI module, servo drive, servo motor, industrial display screen, industrial keyboard, controller, encoder, regulator, sensor, I/O board, counting board, optical fiber interface board, acquisition card, gas turbine card, FIM card and other automatic spare parts