Problems encountered while debugging the PLC

Because the ground wire of the PLC and the zero line of the notebook power supply are connected, resulting in a short circuit in the PLC24V power supply, so it trips, you disconnect the PPI cable, the connection between them is disconnected, and it will not trip hungry, this situation is too rare. No way!!

I've had the conversion card failure you mentioned! In the past, I bought a serial converter for 20 yuan, and then connected to the PLC, I sometimes can't connect to the **program, can't **program! Later, I also heard from others that it was a converter failure, and suggested that I buy a comparator converter.

So I bought a $70 one. If there is really no more failure, why don't you try a good interface card!! It's best to buy it at a regular store!!

As for the problem of charging the laptop you mentioned, I don't know! I also connected to the socket of the device when I debugged, but I never had a problem.

Check whether the terminal block of the PLC is connected to the wrong wire. The input IM2M is connected to the positive pole, and the output is 1M

2m to the negative electrode, 1L

2L+ is connected to the positive electrode, if not, clear the program in the PLC and then go down, or choose to power on and reset.

It depends on how long your instinct lasts, if the persistence time is too short, then it is a problem with your laptop battery, which should have nothing to do with PLC communication.

Summary. Hello dear, happy to answer your <>

There may be several reasons why Siemens PLC has a debug mode error:1There is a syntax error in the PLC program that prevents the program from being launched.

2.The connection between the PLC and other devices is faulty, such as a damaged communication module or a faulty connection line. 3.

Debugging mode settings are incorrect, such as incorrect parameters or incorrectly configured <>

Siemens PLC debug mode is incorrect.

Hello dear, happy to answer your <>

There may be several reasons for the Shenna debugging mode error in Siemens PLC:1There is a syntax error in the PLC program that prevents the program from being launched.

2.The connection between the PLC and other devices is faulty, such as a damaged communication module or a faulty connection line. 3.

Debug mode settings are stuck with errors, such as incorrect parameters or incorrect configuration <>

Here are some <> related extensions that we hope you will find helpful

The steps to deal with the Siemens PLC debug mode error are as follows:1Check the PLC program to make sure it is free of syntax errors.

It can be checked using the compilation function of the Siemens PLC software. 2.Check the connection of the PLC to other equipment and equipment to ensure that the connection line and communication module are working properly.

It is possible to use the front line monitoring function in the scramble wheel to inspect the tung car. 3.Check the debug mode settings to make sure the parameters and configuration are correct.

It can be checked and modified using Siemens PLC software. 4.If the problem persists, try resetting the PLC's settings or reinstalling the PLC software.

The user program error indicator is installed on the base unit in the PLC and is marked as a user in the Q series indicator; The LEDs in the FX series are marked as PROG E.

This indicator is used to indicate the execution status of the PLC user program, when the PLC detects that there is an error in the user program during the start-up process or during operation, the indicator light User or PROG E will flash. The specific reasons for the error are:

Forgot to set a timer or a constant or ladder for a counter.

Error, abnormal drop in battery voltage, or conductivity due to abnormal noise.

The contents of the program's memory are changed due to the contamination of foreign objects, etc., and the LED flashes at this time. In this case, check the program again to see if there is any contamination of conductive foreign matter, whether there is any serious noise source, and whether the battery voltage is displayed.

In case of error, write one of the values of 8068 in the special data register D8004.

For example, if the written content is 8064, then if you look at the content of d8064, you can know that there is an error**. For the actual error content corresponding to the error**, please check the relevant materials or below.

What can be done if you make a mistake, that is, to correct the mistake.

Hope...