Description
MP3101 Invensys Triconex system
MP3101 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 MP3101 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 MP3101 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 exactly does embedded development do?
Embedded development is a technology similar to programming, but our understanding of the scope of programmers is to do computer software, web development, and also to do apps.
The majority of embedded development is intelligent electronic products, which are designed for hardware programming. This hardware can be understood as a circuit board, usually composed of a controller (processor) chip and different circuits.
The specific program and circuit are generally determined by the product function. For example, an electronic clock product is usually composed of a digital tube and a microcontroller (controller), and then written in C language to download it to the microcontroller to achieve clock display.MP3101 Invensys Triconex system
Of course, there are far more products that can be developed in embedded systems, including smartphones, wearable devices, drones, robots, mice and keyboards, and so on.
The knowledge system of embedded development and design is also very diverse, and different products require different learning contents.
So, if we want to enter embedded development, we must first understand several directions of embedded development, otherwise you will never find a starting point.
The general mainstream directions are microcontroller development, ARM+Linux development, and FPGA/DSP development.
I have been working on microcontroller development for the past 10 years of my career.
Microcontrollers can be said to be the foundation of all directions. If you have strong microcontroller development capabilities, then ARM+Linux, or FPGA/DSP are easy for you to get started.
The development of microcontrollers is also one of the directions with the lowest threshold for embedded systems. Initially, I was self-taught in electrical engineering and transferred there. It took me about four months from the beginning of my studies to finding a job.
However, at that time, the threshold was still very low, and you could basically find a job by working on a small project with a 51 microcontroller.
If it”s the current situation, you only know these things and have little competitiveness. Nowadays, the main focus of enterprises is on whether you have project experience, rather than what kind of microcontroller you know.
The project experience can be accumulated through practical projects with endless microcontroller programming, which can be said to be the closest to actual development at present.
At present, the salary of single-chip microcontrollers is not low, and it is normal for them to start at 8K in first tier cities, and they can reach 15K after working for 2-3 years.
There are many industries covered by embedded systems, and in the later stage, based on work, we will only focus on one direction. From a macro perspective, we will divide it into embedded software development and embedded hardware development. Software development is mainly based on application software development on systems (Linux, VxWorks, WinCE, etc.), and hardware development includes motherboard design, system porting, cutting, and writing low-level drivers
My personal experience started with microcontrollers. Firstly, I studied C and C++, digital and analog electronics, power electronics, circuit design, microcontroller principles, FreeRTOS, data structures, and computer operating systems. Later, due to work requirements, I relearned university automation control theory, signals and systems, complex functions, linear algebra, calculus, statistics, and compiler principles. These are all basics, and it is important to understand and thoroughly study them, This will bring help to the later research and development work, and there is also a need for more drawing board, drawing board, and practical operation. Without practicing optics, the efficiency is very low, and knowledge is repetitive. Only by repeatedly looking and using can we understand. We can buy some development boards to assist in learning. Now that the internet is developed, network resources can improve our learning efficiency.
Embedded development refers to developing under an embedded operating system, commonly used systems include WinCE, ucos, vxworks, Linux, Android, etc. In addition, develop using C, C++, or assembly; Using advanced processors such as arm7, arm9, arm11, powerpc, mips, mipsel, or operating systems also belongs to embedded development.
1. Basic knowledge:
Purpose: I can understand the working principles of hardware, but the focus is on embedded software, especially operating system level software, which will be my advantage.
Subjects: Digital Circuits, Principles of Computer Composition, and Embedded Microprocessor Architecture.
Assembly Language, C/C++, Compilation Principles, Discrete Mathematics.
Data structure and algorithms, operating systems, software engineering, networks, databases.
Method: Although there are many subjects, they are all relatively simple foundations and most of them have been mastered. Not all courses may be taught, but elective courses can be taken as needed.
Main books: The C++programming language (I haven”t had time to read it), Data Structure-C2.
2. Learning Linux:
Purpose: To gain a deeper understanding of the Linux system.
Method: Using Linux ->Linxu system programming development ->Driver development and analysis of the Linux kernel. Let”s take a closer look, then the main topic is principles. After reading it a few times, look at the scenario analysis and compare it deeply. The two books intersect, with depth being the outline and emotion being the purpose. Analysis is version 0.11, suitable for learning. Finally, delve into the code.
Main books: Complete Analysis of Linux Kernel, Advanced Programming in Unix Environment, Deep Understanding of Linux Kernel, Scenario Analysis, and Source Generation.
3. Learning embedded Linux:
Purpose: To master embedded processors and their systems.
Method: (1) Embedded microprocessor structure and application: Direct arm principle and assembly are sufficient, without repeating x86.
(2) Embedded operating system class: ucOS/II is simple, open source, and easy to get started. Then delve deeper into uClinux.
(3) Must have a development board (arm9 or above) and have the opportunity to participate in training (fast progress, able to meet some friends).
Main books: Mao Decao”s “Embedded Systems” and other arm9 manuals and arm assembly instructions.
What is the function of an IO chip
Io generally refers to input and output devices, where I is the input and O is the output. The input to the IO port of the chip is the external signal transmission to the chip, while the output is the internal signal transmission to other devices. The input and output are relative. In short, in a broad sense, the control of input and output interfaces is called an IO chip, and network cards are also considered IO or array cards.
The CPU must read and write data to external registers or ROMs on RAM or other hardware through IO commands (such as input/output commands). For example, reading a keyboard involves accessing external registers on the keyboard through the 60H port, and the chip on the keyboard scans the keyboard. Pressing or holding down a key for a long time will cause the chip to generate corresponding scan or break codes, which will be written to the external register of the 60H port, so that the CPU can achieve the purpose of controlling the keyboard. Therefore, I think IO chips should refer to a large category. The CPU already has powerful IO instructions and corresponding control buses.
51 microcontroller IO port input and output mode_ Four usage methods for IO ports
The traditional 51 microcontroller IO interface can only be used as a standard bidirectional IO interface. If it is used to drive LED, it can only be driven by injecting current or using a transistor external expansion drive circuit.
Current injection method: LED positive pole connected to VCC, negative pole connected to IO port. If the IO is at a high level, the two poles of the LED are at the same level, and there is no current, the LED will turn off; IO is at low power level, current flows from VCC to IO, and LED lights up. But when you connect the positive pole of the LED to the IO interface and the negative pole to GND, placing the IO interface at a high level will cause the LED to light up. However, due to the insufficient pull-up capability of the IO interface, the brightness is not ideal. The following method can be used to solve this problem.
Push-pull working mode: The positive and negative poles of the LED are connected to two IO ports, and then the positive IO interface is set as the push-pull output, while the negative IO interface is set as the standard bidirectional current input. The push pull method has strong pull-up ability and can achieve high-level LED driving.
Four usage methods for IO portsMP3101 Invensys Triconex system
From the perspective of the characteristics of the I/O port, the P0 port of Standard 51 is an open drain structure when used as an I/O port, and in practical applications, a pull-up resistor is usually added; P1, P2, and P3 are all quasi bidirectional I/Os with internal pull-up resistors, which can be used as both input and output. The I/O port characteristics of the LPC900 series microcontroller have certain differences, and they can be configured into four different working modes: quasi bidirectional I/O, push pull output, high resistance input, and open drain.
Compared with Standard 51, the quasi bidirectional I/O mode differs in internal structure but is similar in usage. For example, when used as an input, it must first write “1” to set it to high level before reading the level state of the pin.!!!!! Why is it like this? Please refer to the diagram below for analysis.
The characteristic of push-MP3101 Invensys Triconex systempull output is that it can drive a large current regardless of whether it outputs high or low levels. For example, when outputting high levels, it can directly light up the LED (by connecting several hundred ohm current limiting resistors in series), which is difficult to achieve in quasi bidirectional I/O mode.
The characteristic of high impedance input mode is that it can only be used as an input, but it can obtain relatively high input impedance, which is necessary in analog comparator and ADC applications.
The open drain mode is similar to the quasi bidirectional mode, but there is no internal pull-up resistance. The advantage of open drain mode is good electrical compatibility. If the external pull-up resistor is connected to a 3V power supply, it can interface with a 3V logic device. If the pull-up resistor is connected to a 5V power supply, it can also interface with a 5V logic device. In addition, the open drain mode can also conveniently implement the “line and” logic function.
For the explanation of the above question, there is this information:
High resistance state is a common term in digital circuits, referring to an output state of a circuit that is neither high nor low. If the high resistance state is input into the next level circuit, it has no impact on the lower level circuit, just like not connected. If measured with a multimeter, it may be high or low, depending on what is connected afterwards.
High resistance states can be understood as open circuits during circuit analysis. You can think of it as having a very high output (input) resistance. His limit can be considered suspended.
Typical applications of high resistance states:
1. On the bus connected structure. There are multiple devices hanging on the bus, and the devices are connected to the bus in a high impedance form. This automatically releases the bus when the device does not occupy it, making it easier for other devices to gain access to the bus.
2. Most microcontroller I/O can be set to high impedance input when used, such as Lingyang, AVR, and so on. High resistance input can be considered as having infinite input resistance, indicating that I/O has minimal impact on the preceding stage and does not generate current (without attenuation), and to some extent, it also increases the chip”s resistance to voltage surges.
Definition of IO Link Protocol and Its Interface
IO Link is a peer-to-peer, serial digital communication protocol designed for periodic data exchange between sensors/actuators and controllers (PLCs). The IO Link protocol was first proposed by Siemens and has now become an international standard IEC 61131-9. With the advancement of Industry 4.0, the use of IO Link is becoming increasingly widespread. Today”s article will introduce the definition of the IO Link protocol and its interfaces.
Factory automation can be divided into execution layer, on-site layer, on-site control layer, workshop control layer, and management layer according to functional division. As shown in the following figure:
The execution layer includes various execution mechanisms (valves, pumps, motors, etc.) and sensors, which are the muscles and peripheral nerves of factory automation. They receive commands from the upper layer and complete specified actions.
The on-MP3101 Invensys Triconex system site layer includes various distributed IOMP3101 Invensys Triconex system systems, which are the central nervous system of factory automation. It conveys control instructions from the upper layer to the execution layer; And feedback the signals from the execution layer to the control layer, serving as the information center;
The on-site control layer includes various PLC systems, which are the brains of factory automation. It issues corresponding instructions and commands the execution layer to complete corresponding actions based on internal program requirements and signal feedback from the execution layer;
The workshop control layer (MES) and management layer communicate with various PLC systems at the management level to complete management tasks at the workshop and factory levels.
The IO Link protocol to be introduced in this article is a protocol that transfers data between the execution layer and the field layer. An IO Link system consists of the following components:
1) IO Link Master;
2) IO Link Device;
3) Non shielded 3-5 core standard cable;
4) Tools for configuring IO Link parameters;
The IO Link Master transfers data between the IO Link device and the PLC. It is usually a distributed IO module with IO Link connection channels on the module. The IO Link Device is connected to the channel of the IO Link Master through a cable, and the IO Link Master exchanges data with the PLC through a bus. As shown in the following figure:
Every IO Link device needs to be connected to a channel of the IO Link supervisor, so IO Link is a peer-to-peer communication protocol, not a bus protocol.
IO Link devices are divided into two types: sensors and actuators: sensors are usually the four pin interface of M12, and actuators are usually the five pin interface of M12.
According to IEC 60974-5-2, the definition of IO Link Device pins follows the following regulations:
1) Pin 1 (PIN1): 24V power supply positive pole;
2) Pin 3 (PIN3): 0V
3) Pin 4 (PIN4): IO Link communication or standard IO output;
The pin definition of the IO Link device is shown in the following figure:
Which types of equipment should PLC module manufacturers develop first?
We know that PLC, also known as programmable logic controller, collects variable data through various IOs to achieve the purpose of automated control. Therefore, developing PLC is largely about developing IO. However, with so many types of IO, which PLC module manufacturers should develop first? Let me share my opinion:
1. Digital input IO, including PNP and NPN digital input IO, counter input IO, etc.
2. Digital output IO, including PNP and NPN digital output IO, PWM pulse output IO, relay output IO, and so on.
3. Analog input IO, including current acquisition input IO, voltage acquisition input IO, temperature acquisition input IO, and so on. The current input IO can collect currents ranging from 0 to 20 milliamperes, while the voltage input IO can collect voltages ranging from negative 10V to positive 10V. Temperature acquisition IO includes thermocouples and thermal resistors.
4. The style of analog output IO is similar to that of analog input IO, but does not include temperature analog, mainly voltage and current type.
What IO combinations can a mini PLC combine with to achieve automated control?
At present, there are two main design modes for controllers like PLC, one is integrated design and the other is modular design. From the name, we can feel that there are two different PLCs, one that cannot be disassembled and the other that can be disassembled. Due to the fact that the main control module and IO module of the modular PLC can be spliced as needed, its volume and weight are usually very small, and we cannot call it a mini PLC too much. So, what IO combinations can such a small gadget combine with to achieve automation control? Let”s take a brief inventory:MP3101 Invensys Triconex system
1. Firstly, there is the digital quantity acquisition IO module, which is used to collect digital quantity information. Typical examples include counter IO, PNP type digital quantity acquisition IO, NPN type digital quantity acquisition IO, etc.
2. Then there is the digital output IO module, which is used to send digital instructions. The most typical example is PWM output IO, which can output pulse signals to control servo motors or stepper motors for operation.
3. After talking about digital IO, let”s talk about analog IO. Analog signal acquisition type IO includes voltage signal acquisition, current signal acquisition, and temperature signal acquisition. The IO for collecting temperature signals includes PT100, PT1000, and various thermocouple temperature acquisition modules.
4. Finally, there are analog output IO, as well as output current signals and voltage signals.
In addition to the above IO modules, our modular PLC also supports extended communication interfaces, further enhancing the equipment”s scalability.
Module Input/Output (I/O) KnowledgeMP3101 Invensys Triconex system
Module Input/Output (I/O) Knowledge
I think it”s necessary to talk about the sorting of the input and output ports of the module. Generally, we can divide it into IO functional division and IO specifications.
The purpose of the former is mainly to convert all functions into actual division into MCU IO ports, while the purpose of the latter is to determine the specifications of all IO ports. Of course, you can completely skip these tasks, and it”s also possible. Depending on the company”s requirements, I think individuals still consider them as a work habit.
The following examples are all created for my blog post. If there are any duplicate names, please do not contact me.
Looking at the above figure, first determine all input and output functions and power input, as well as communication.
Then separate the power distribution with different lines, and start organizing each power supply line and processing process. The final purpose of the entire diagram is to clearly allocate the input and output sequence.
The IO specification is to provide a detailed description of all interfaces, crystal oscillators, and other information to the MCU.
1. Enter the number of low effective interfaces and how much pull-up resistance (switch wet current) is required (how much current does the microcontroller need to absorb, which may be injected into the microcontroller after pull-up).
2. Enter the number of highly effective interfaces, how many pull-down resistors are required (switch wet current), (how much current does the microcontroller need to absorb, and it is possible to inject the microcontroller after the switch is effective)
3. Number of analog input interfaces, evaluate whether the analog ports of the microcontroller are sufficient, and confirm the required analog conversion accuracy. Evaluate whether the A/D conversion reference voltage needs to be replaced (to meet accuracy requirements). Consider how many power supplies need to be tested and how many analog input ports are configured.
4. Evaluate the requirements for crystal oscillator accuracy and whether a phase-locked loop is required.
The above requirements are mainly aimed at module design and need to be confirmed during the early development of the module. All requirements can be organized using an Excel table and displayed in the diagram.
Distributed dual Ethernet IO module
The distributed dual Ethernet IO module adopts an industrial grade design, which meets the demanding industrial application scenarios. It is equipped with a dedicated high-performance Ethernet chip, which can quickly achieve cascade networking between IO modules without the need for repeated wiring, saving on-site wiring costs.
The distributed dual Ethernet IO module comes with switch input, switch output, relay output, analog input, analog input, thermal resistance input, etc. It supports high-speed pulse input counting and high-speed pulse output, and is designed specifically for industrial field data collection, measurement, and control. The distributed dual Ethernet IO module supports Modbus TCP protocol and Modbus RTU protocol for uplink, which can quickly connect to existing DCS, SCADA, PLC, HMI and other systems. The distributed dual Ethernet IO module supports one RS485 interface and supports Modbus RTU Master function. It can expand the IO module, read and write intelligent instrument data, or connect to HMI, DCS, PLC and other devices as a Modbus Slave.
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
