What are the reasons for the CPU reporting system failure? Will it have any effect on normal work?
1. This product is used to
convert the car power supply of mobile phone chargers
2. This product has over-current
short-circuit overload protection
3. Insert this product into the
cigarette lighter socket of the car
4. Confirm whether the power
indicator light of this product is on
5. Insert the mobile phone
charger into the socket of this product
6. This product is used in mobile
phones, PHS, mobile phone line chargers, travel chargers, universal chargers,
etc.
150w Car Inverter, 150W Power Inverter, Car Charger Inverter with USB Shenzhen Jinziming Electronic Technology Co.,LTD , https://www.powerchargerusb.com
A: SF is a system failure, but the SF light is on, it may be:
1. The corresponding interrupt organization block OB is downloaded and there is no downtime.
2. It may be that the program has gone wrong, please check and compile it carefully.
3. May be a software failure, check the program structure, variable name, hardware configuration.
First reset the plc, first power-off reset, and then manually reset.
The manual reset method is as follows: S7-300 series CPU memory method: The operation mode switch is switched from the STOP position to the MRES position, and the STOP LED is lit and remains on for about 9 seconds. Release the switch to return it to the STOP position. Return the switch to MRES within 3 seconds. The STOPLED flashes at least 3s at 2Hz, indicating that it is resetting. Finally, the STOPLED is always on, and the mode switch can be loosened and completed.
If you still can't do the following for reference:
1. Connect the S7-300 CPU with the communication cable, and then open the project file with the SIMATICManager Manager. After the "Online" of the CPU, open the "ModuleInformation" window and check the "diagnosticBuffer" (ie the diagnostic buffer of the CPU) tab. history record. Then carefully analyze the cause of the error. It can be initially determined whether it is a hardware failure or a software failure.
2. Download the hardware configuration and program again to eliminate hardware configuration and software program problems.
3. Determining faults from a software programming perspective, such as downloading error handling organization blocks: OB81 (power failure), OB82 (diagnostic interrupt), OB83 (insertion/removal module interrupt), OB86 (rack failure or distributed I/O) Station failure), OB87 (communication error), OB121 (program error), OB122 (I/O access error), these organization blocks are sequentially downloaded to the CPU to cause an error to enter the STOP state.
4. Determine the fault from the hardware installation connection, such as: 1. Check whether the power supply is normal; 2. Check whether the backplane bus connection is normal, 3. Check whether the external connection of each module is abnormal; 4. Check whether each module is installed. Loose and vibrate around. 5. Is there any module damaged on the rack?