Description
4000056-002 Invensys Triconex system
4000056-002 Invensys Triconex system
Module Clips Drive controller servo motor
Contact: Mr. Lai
Wechat:17750010683
Whats app：+86 17750010683
Skype：+86 17750010683
QQ: 3221366881
3221366881@qq.com
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 4000056-002 Invensys Triconex system
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 4000056-002 Invensys Triconex system 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.
What are the characteristics of a demonstration system based on IO Link slave stations
IO Link is an industrial communication interface that is independent of any fieldbus and suitable for simple sensors and actuators at the lowest level of industrial control. The IO Link system includes IO Link devices (such as sensors and actuators), IO Link master stations, and cables for standard sensors. The system structure is shown in Figure 1. For example, when a remote IO module compatible with EtherNet/IP serves as the master station, in addition to standard I/O signals, the module sends and receives configuration data, diagnostic data, or enhanced process data through a pulse modulation process, which is then packaged into EtherNet/IP data packets and finally transmitted to the network master station, usually a PLC. In the above applications, the connection between remote I/O and IO Link devices remains the same as that of traditional discrete devices. The advantage of IO Link mainly lies in its greater information exchange capability, which was previously impossible to achieve with standard I/O devices. Another advantage of IO Link is that it does not rely on any fieldbus, and through any I/O module that complies with the IO Link protocol (including local I/O and remote I/O), IO Link sensors or actuators can be integrated into any fieldbus system.
In order to further study the architecture, communication mechanism, and development application of the IO Link system, an IO Link slave toolkit can be designed and developed, including a universal development module for IO Link, an IO Link analysis tool, and an IO Link slave protocol stack. The IO Link universal development module is the foundation for this work and also serves as a bridge between the IO Link master station and equipment signals. The IO Link analysis tool can help developers and testers analyze communication details to identify and solve problems. The IO Link slave protocol stack is a firmware library that provides a hardware abstraction layer and application program interface, allowing developers to easily and quickly develop IO Link slave products on various microprocessor platforms. The IO Link slave station studied in this article only focuses on digital (button) signal input and digital signal output (indicator light). The design of the IO Link universal development module only needs to be expanded on this basis to have the ability to process analog signals.
The IO Link Master module used in this article, USB IO Link Master, can connect IO Link devices to a PC, which can be configured and tested through the IO Link Device Tool software or demonstrated device functionality. IO Link devices must be described through a device description file (IODD file), which includes a set of XML text files and PNG graphic files, which contain information about device identification, communication characteristics, parameters, process data, and diagnostic data. The portion within the elliptical dashed line in Figure 2 is an IO Link three wire cable, with L+/I – being a 24 V DC power supply and C/Q being a signal line used to transmit process data, diagnostic data, configuration data, etc. The IO Link universal development module is mainly composed of data transceivers and microprocessors. It can process input signals from sensors and transmit information to the IO Link master station. It can also receive and process data information from the master station and transmit it to the actuator. The IO Link analysis tool can help developers view, record, analyze data, and understand communication details. This part of the design is not discussed in this article.
Introduction to IO Link Communication Mode4000056-002 Invensys Triconex system
IO Link devices can operate in SIO mode (standard I/O mode) or IO Link mode (communication mode). After power on, the device always operates in SIO mode. The port of the main station has different configuration methods. If configured in SIO mode, the main station considers the port as a standard digital input. If configured in communication mode, the main station will automatically identify the communicable devices for communication.
2.1 Data Types4000056-002 Invensys Triconex system
The three basic data types for IO Link communication are periodic data (or process data PD), non periodic data (or service data SD), and event.
The process data (PD) of the device is transmitted periodically in the form of a data frame, while service data (SD) is only exchanged after the master station issues a request. Figure 3 shows a typical IO Link message structure. When an event occurs, the “event flag” of the device is set, and the main station reads the reported event (service data cannot be exchanged during the reading process) upon detecting the setting. Therefore, events such as pollution, overheating, short circuits, or device status can be transmitted to the PLC or visualization software through the main station
2.2 Parameter data exchange
Since service data (SD) must be transmitted through PLC requests, SPDU (Service Protocol Data Unit) is defined. In the main station, requests for read and write services are written to SPDU and transmitted to devices through the IO Link interface.
The general structure of SPDU is shown in Figure 4, and its arrangement order is consistent with the transmission order. The elements in SPDU can take different forms depending on the type of service. SPDU allows access to data objects that are intended for transmission, while Index is used to specify the address of the requested data object on the remote IO Link device. In IO Link, there is a term called direct parameter page, which stores parameter information such as minimum cycle time, supplier ID, and master station commands. The data objects accessible in the direct parameter page can be selectively provided through SPDU.
HMT7742 is an IO Link slave transceiver chip that serves as a bridge between the MCU of external sensors or actuators and the 24V signal line that supports IO Link communication. When the IO Link device is connected to the master station, the master station initializes communication and exchanges data with the MCU. HMT7742 serves as the physical layer for communication.
Due to the fact that the three indicator lights (rated voltage 24 V) controlled by the output port of the MCU are powered by the IO Link power cord, it is necessary to monitor the current on the power cord in order to trigger appropriate corrective measures when the current exceeds a set threshold, such as removing the indicator lights from the IO Link power cord. The current monitoring module uses an INA194 current detection amplifier. As a high detection current detector, INA194 is directly connected to the power supply and can detect all downstream faults. It has a very high common mode rejection ratio, as well as a large bandwidth and response speed. It can amplify the voltage on the induction resistor 5O times and output it to the forward input terminal AIN0 of the MCU internal voltage comparator. When the voltage value of AIN0 exceeds the threshold set at the reverse input terminal, By controlling the low level output of PB0, the indicator LAMP can be cut off from the IO Link power line to achieve overcurrent protection function. This part of the circuit is shown in Figure 6.
What are the types of integrated IO modules4000056-002 Invensys Triconex system
For a programmable logic controller, IO fulfills the responsibilities of data acquisition and instruction output. What control objectives can a PLC achieve, and the quantity and type of IO are crucial. For general integrated PLCs, the number and types of IO interfaces are constant. Some friends may ask, what if you encounter a complex control project with insufficient IO ports in the PLC? Don”t worry, nowadays PLCs have communication interfaces that can be connected to other IO couplers to achieve IO expansion. So, what are the types of IO modules that we can integrate in our daily lives? Actually, it can be mainly divided into four categories, namely:
1. Digital signal acquisition IO can achieve discontinuous signal acquisition, and a typical IO type is a counter input IO module.
Technology Oasis • Source: Guangcheng CAN Bus • Author: Guangcheng CAN Bus • 2022-05-09 09:52 • 1740 readings
For a programmable logic controller, IO fulfills the responsibilities of data acquisition and instruction output. What control objectives can a PLC achieve, and the quantity and type of IO are crucial. For general integrated PLCs, the number and types of IO interfaces are constant. Some friends may ask, what if you encounter a complex control project with insufficient IO ports in the PLC? Don”t worry, nowadays PLCs have communication interfaces that can be connected to other IO couplers to achieve IO expansion. So, what are the types of IO modules that we can integrate in our daily lives? Actually, it can be mainly divided into four categories, namely:
1. Digital signal acquisition IO can achieve discontinuous signal acquisition, and a typical IO type is a counter input IO module.
2. Digital output IO, which can send out command signals of digital quantities to control actuators, such as PWM IO, can send pulse signals to control servo motors and stepper motors. In addition to PWM IO, we often use relay output type IO.
3. After discussing digital IO, let”s talk about analog IO. Firstly, analog input IO includes voltage analog input IO, current analog input IO, temperature analog input IO, etc. They collect continuous signals.
4. Finally, there is the output type IO of analog quantity, mainly including voltage analog quantity output type IO and current analog quantity output type IO. Some friends may ask why there is no temperature this time, but there are relatively few applications, mainly based on voltage and current types.4000056-002 Invensys Triconex system
Industrial automation solutions, starting with remote IO modules!
The remote IO module is mainly used for collecting analog and digital signals on industrial sites, and can also output analog and digital signals to control equipment. It is possible to expand the input and output ports of data processing equipment such as PLCs and collection instruments. For example, a PLC only has 10 analog input interfaces, but if 30 analog quantities need to be collected on site, remote IO expansion needs to be added.
Furthermore, due to the distance between the equipment and the main control PLC or industrial computer, RS-485 bus is usually used for transmission. There are also some factories with high levels of automation that use industrial Ethernet to control remote IO modules. In the past, when laying lines between equipment and cabinets, people had to connect them one by one, which greatly increased the cost of cables and construction time. Moreover, if the distance was relatively long, they also faced problems such as voltage attenuation. And with the remote IO module, it effectively solves this problem. If your cabinet is 200 meters away from the site and you do not use remote IO, then you need to lay out each signal line for 200 meters. Installing the remote IO module on site can save you a lot of cable costs and reduce the complexity of construction from a cost perspective.
Simply put, sometimes some IO is set up in the on-site device cluster, which can be connected to the PLC through a communication cable to send the signal to any place where it is needed, saving wiring and PLC”s own IO points. Sometimes, the logical “remote” is because the allowed number of “local IO” cannot meet the actual needs, and it needs to be connected to the “remote IO template”, depending on the actual situation.
In addition, the general cabinet room is located on the device site. But some control signals, such as emergency stop and bypass, are implemented in the control room, so remote IO modules need to be used to send these signals to the control system in the cabinet room.
Why use remote I/O?
1. Because in some industrial applications, it is impossible to install PLCs with local I/O modules near on-site equipment due to harsh environments.
2. When you want to place the I/O module near the field device to eliminate long multi-core cables, you can receive signals from distant sensors and send remote control signals to control valves, motors, and other final actuators. The signal can be transmitted at any distance using various transmission protocols such as Ethernet and Profibus through high-speed media such as twisted pair and fiber optic.
3. Multiple transmission protocols such as Ethernet and Profibus can be used to send signals at any distance on high-speed media such as twisted pair and fiber optic.
The barium rhenium technology MXXT remote IO module uses industrial grade components with a wide working voltage of DC9-36V, which can operate normally within the range of -20~70 ℃. It supports RS485/232 communication mode, and the communication protocol adopts standard Modbus TCP protocol, Modbus RTU over TCP protocol, and MQTT protocol. We strive to fully meet the needs of our customers with an electrical and mechanical system that is anti-interference, resistant to harsh environments, and compatible with general use. It has stable performance, reliable quality, short delivery time, and fast response.
Advantages of Barium Rhenium Remote I/O Module
1. It can be controlled by remote commands.
2. Save the cost of using industrial control computers and IO cards, and Ethernet I/O modules can be directly connected to the upper computer system;
3. Replacing 4-20mA signal transmission with 10/100MHz Ethernet transmission has improved transmission speed;
4. Replacing various instrument controller signal lines with an Ethernet cable reduces the attenuation of remote signal transmission;
5. The signal cable of the instrument controller only needs to be connected to the Ethernet I/O module, greatly reducing cable costs and wiring workload.
6. Convenient installation method. Rail installation, high reliability, strong anti-interference ability, and more convenient on-site installation.
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
