What should I do if there is a warning when I start the Schneider PLC program? Thank you for your he

Start menu Run, enter "regedit" to run the registry, and then follow the steps below.

Find in the registry: Hkey Local Machine Software Schneider Electric Common ObjectStoreParam"addressingspacesize"="0x28000000" "cachesize1stappli"="0x1800000"will"addressingspacesize"="0x28000000"Changed to"addressingspacesize"="0x18000000"Can.

Close other larger programs, such as antivirus software

Find in the registry: Hkey Local Machine Software Schneider Electric Common ObjectStoreParam"addressingspacesize"="0x28000000" "cachesize1stappli"="0x1800000"will"addressingspacesize"="0x28000000"Changed to"addressingspacesize"="0x18000000"Can.

Generally, this indication is on the output leakage lead module, which means that the external power supply of the module is not connected, and the common terminal is not connected.

Connect to an external power supply with a short circuit.

CP can be used for networking, such as large DCS, because some modules have their own DP ports, CP modules can be used. An inverter can be connected.

The IM module is used to connect the expansion rack, for example, 10 IO modules are needed, but the No. 0 rack can only be installed with 8, and the remaining two will be installed on the No. 1, and the IM module will be installed on the two racks.

The communication between the PLC and the host computer is faulty. Check whether the communication interfaces are well linked.

1. After powering on, the error light flashes, and the RUN light does not light up. run to the running state. Or flashing can see if there is a problem with the next Cheng jujube Ming order, if the program is fine. That is, there is a problem with the IO module.

2. There are generally many reasons why the error light is on, such as IO card damage, communication failure, data overflow, stool macro to zero, and so on. The IM module is installed on the two racks, and the two racks do not belong to the network, but are just an extension of the No. 0 rack, so it is different from the CP module.

Dear Hello, I am happy to answer for you, the following is the answer for your query, I hope Chang Zhaoheng will be helpful to you There may be many reasons for Schneider PLC to report fault, and the common reasons include: 1Power failure:

The unstable power supply of the PLC power supply or the failure of the power supply will cause the PLC to report communication failures: the communication between the PLC and other equipment fails, such as communication line failures, communication protocol mismatch, etc. 3.

Program error: There is an error in the PLC program, such as a program logic error, instruction error, etc. 4.

Module failure: The input and output modules of the PLC are faulty, such as module damage, poor connection, etc. Solution:

1.Check whether the PLC power supply is stable, if not, you need to replace the power supply. 2.

Check that the communication lines and protocols between the PLC and other equipment are correct, if not, you need to adjust them. 3.Check whether the PLC program is correct, if there is an error, you need to modify it.

4.Check whether the input and output modules of the chain town PLC are normal, if there is a fault, the module needs to be replaced or reconnected. If the above methods do not solve the problem, it is recommended to contact Schneider PLC's after-sales service center for repair or replacement.

Summary. For different causes of failure, the solutions will be different:1

Hardware failure: Generally, the faulty hardware device needs to be replaced; 2.Program Error:

The program logic needs to be re-analyzed, debugged, and modified; 3.Communication failure: Check whether the communication line is normal, whether the communication parameter settings are correct, and debug and repair it. 4.

External interference: It is necessary to do a good job of grounding the ground to avoid the interference of external interference signals.

Dear, it's a pleasure to meet your <>

There are many reasons for Schneider PLC to report a fault, including but not limited to the following:

1.Hardware failures: such as power failures, CPU failures, memory failures, etc.; 2.

Program errors: For example, the program logic has a dead Li Nian loop, unlimited recursion, etc., resulting in insufficient CPU processing power and failure; 3.Communication Failure:

For example, the communication line is interrupted, the communication parameter is set incorrectly, etc.; 4.External interference: such as electromagnetic interference, electrostatic disturbance, etc.

For different causes of failure, the solutions will be different:1Hardware failure:

Generally, it is necessary to replace faulty hardware equipment; 2.Program error: The program logic needs to be re-analyzed, debugged, and modified. 3.

Communication faults: Check whether the communication line is normal, whether the communication parameters are set correctly, and debug and repair them. 4.External interference:

It is necessary to do a good job of ground grounding, and fan training to avoid the interference of the interference signal of the outer lead car.

When solving the problem, it is necessary to determine the type of fault, guess the cause of the fault, and then solve the problem in a targeted manner, and at the same time pay attention to the protection of the PLC equipment and the connection with its sensitive equipment.

Dear <> hello Ha Yun I have the following answers, please be patient and look at Ha <> 2Power failure: The PLC needs a stable power code, and the fault will be triggered when the voltage is too high or too low.

The solution is to check the power supply and restore the normal voltage. 2.CPU Failure:

The CPU is the control core of the PLC, and its failure will cause the system to fail and report a fault. CPU overhaul or replacement is required. 3.

Sensor failure: The PLC needs to collect the signal of the sensor for operation and control, and when a sensor fails, the signal will be lost and the fault will be reported. Faulty sensors need to be serviced or replaced.

4.Module failure: A failure of the extension module to connect to the host can also cause a fault.

When there is an error in the programming of the PLC's control program, a fault will also be triggered during operation. The PLC program needs to be checked and modified. 6.

Input/output faults: Faults can also occur when the input/output terminals of the PLC or the module base connected to the peripherals fail. You need to check the I/O lines and external device connections.

7.High humidity: The PLC also has certain requirements for ambient humidity, and too high humidity may affect the normal operation of the PLC and report faults.

The ambient humidity needs to be checked and adjusted.