What are the standard interfaces for automation control systems?

There are too many standard interfaces, and there are a few pins of aviation connectors.

Find a supplier and ask for information.

Introduction to OPCserver, an industry-standard communication interface.

ForeverCredit OPC Server Server Software, referred to as OPCserver, is a standard OPC interface independently developed by Beijing Huahengxin Yuanzheng for various DCS, PLC, configuration software, power integrated automation and other control systems, measurement systems, and other auxiliary production equipment and software systems involved in the production process of the enterprise, and provides industry standard communication interfaces for third-party application systems. MIS, ERP and other systems provide data.

I've used a network cable, rs485.

The interface is the connection port between the control system and the input and output equipment, and is the transfer station where the system exchanges information with the outside world. For example, CRT interface with display, shared protocol communication interface, etc.

The "interface" in the design of the automation control system is simply put: the conversion and docking of analog and digital quantities.

No matter how simple and popular it is: the relationship between the kilogram "unit" and the number "number", and the adjective "size" and "how much".

1. Advantages of tool testing: easier to get started, high efficiency to achieve coding implementation Disadvantages: Programming foundation is required, function self-implementation, low efficiency 2. Disadvantages of tool testing:

The test data structure is single, the scalability is poor, and the coding implementation is advantageous: The test data is more diverse, the scalability is more flexible, and the free elementary courses on the official website of the Chuanzhi Podcast are taught, and they are all systematic tutorials, so you can have nothing to do with me.

After understanding what interface testing is, how do you do it? The process of interface testing is similar to that of functional testing: interface test plan - interface test case - interface test execution - interface test report.

The dependencies of test case design are mainly requirements specifications and interface documents.

Because the interface test is not for ordinary users, but for another system component, it cannot be tested directly, and it needs to be tested with tools, such as server-side HTTP interface test, commonly used tools such as jmeter, postman, httpclient, etc. Test with tools, so the goal is to prepare the test data test script and execute it directly, when writing the test execution, there are the following principles:

1.Different interface parameters cover different business scenarios;

2.Construct appropriate data in the background to meet the test cases of the interface;

3.Based on the return value of the interface, assert whether it returns the desired result or not, and look at the database validation;

4.If the test case involves multiple steps, all the steps involved should be verified;

5.Remove the results from the testing process to ensure a clean environment before each use case is executed.