Possible problems and countermeasures of engineering system integration

The steps in the integration of the engineering system are full of concerns about the details. Then what problems will happen during system integration? In terms of past engineering experience, there should not be any engineering director or engineering technician dare to take a vote and say that integration testing is done at one time because system integration is the key to the success of the entire project, and system integration is not simply to connect one or two systems. Together. Any negligence of small details can become a big problem. Therefore, besides the small details, we must face a bunch of problems that are most likely to occur during the system integration stage. These problems and solutions are as follows:

The power supply and consumption of the original system are sufficient for individual operation. However, after the system integration, voltage drop and current shortage occur. The initial system presents unstable solutions:

· Calculate the power demand power and type of category for all system integration before integration;

· Separate the same DC and AC power, and re-arrange the power bus junction and non-distribution no-fuse switch capacity and power control loop to integrate the UPS power interruption supply system load and use SWITCHING POWER to supply small-area DC power to stabilize the Pressure effect

· Put the system into full operation and use the ammeter to measure the maximum current value of each power supply switch one by one to ensure that it is within the safe load range, so that the power integration can be guaranteed.

When the system is running alone, everything is normal. After integration with the main system platform, it is found that some functions cannot be executed or are not affected by other subsystems.

· The subsystems are operated together and all project functions are executed, then the system is online, the functions cannot be performed on a record-by-item basis, and the unobtainable function subsystem and the system are separated from each other. Whether the single system is operating normally or not, and the database or background Find execution problems in the program;

• If the problems are merged with other systems, the subsystems are offline one by one to clarify the impact of the system from that subsystem, and then compare the problems in the system data one by one. Clear out the problem points or modify the protocol contents.

The operating modes of the various systems are different. After the linked operation mode is not synchronized, the owners do not know what basis they are based on:

·Compared to the same instruction background program DOS window send status column command and whether there is no response to each subsystem;

·Compared to the same command background program DOS window send status column command and whether it is garbled;

·Compared with the corresponding instruction of the background of each subsystem's same command DOS window's sending status column command, whether it matches the corresponding string;

· One by one to find problem instructions, modify the protocol, command string, and time parameters to correct the synchronization problem.

Subsystem software often occurs in a crash situation or automatically emits garbled instructions and receives instructions but does not respond to the solution:

· Check whether the connection status between the systems is correct;

Check whether the database field in the main integration system is correct;

• Check whether the subsystem encoding command and data sending time parameter setting are automatic manual error setting.

Non-overflow automatic cleanup of individual software databases in different systems generates Run Time Error scenarios Solution:

·Clear the backup database regularly;

· Set up automatic database coverage and automatic backup;

• Set to store only event data, system online data automatic timing clear function.

The command receiving and responding mode is different, which causes the continuous sending of the instruction to generate a system shutdown situation. Solution:

Check the string of the inter-system communication protocol;

• Check if the subsystem workstations are synchronized and correct.

The system switching mode is different, which makes the operation more troublesome solution:

· Through the network program connection method, the system will be turned on or off with the same operation screen, a single control command to turn on or off the integrated subsystem programs or hardware power;

• Use the Supervisory Control and Data Acquisition (SCARDA) approach to monitor and manage the power system.

The time of each system is not synchronized, or the format is mixed so that the instructions are issued in the wrong system.

· Unified all YY/MM/DD, Am/Pm, year, month, day, up, and afternoon time formats using PCs or workstations, including both Chinese and English display formats;

· Using system integration, implant a time synchronization timer so that the system automatically sends time correction commands at regular intervals to synchronize all system time.

The above problems and solutions are most encountered in the system integration stage. Engineers must carefully consider the possible causes of these problems and use the best solutions to simulate the tests in advance when the system is independently integrated. Integrate the test to solve these more difficult problems.