kess v2 wake up error solution

How to Solve KESS V2 Wake up error?


If you encounter "Wake up error" when running Kess v2 as the following picture shows:

Possible reasons for wake up error:
Kess v2 fails to read out TF card program or the program in the TF card is not working properly.
2 reasons for Kess v2 fails to read out TF card program.
1) The four pins of chip are not soldered firmly on the main board.
2) The chip is loose for a long time of use.

Try to do as following instruction:
1) Solder the chip once more to make it tightly connected to the main board.
2) Clean up the shrapnel on the card slot with a brush.
3) Lift up the shrapnel a little bit to make sure it can well communicate
with the TF card, if the card slot shrapnel is not flexible enough.
4) Clean the TF card and then put it back to the card slot.

If the wake up error stays, format the card and then copy the software back to the card.
It is easy 3 basic steps, pay attention to the important note.
1. Format TF card
2. Ask us to send you the software in the TF card
3.
decompress the file, choose them all, copy and paste to TF card.
(IMPORTANT NOTE: Don’t directly copy the compressed file to TF card;
don’t create a new folder in TF card and copy decompressed file into
it.)

(1. Decompress file: kessv2 up)

(2. Copy the 4 files and paste to TF card)
Note: Following is Wrong operation:

If
the two methods above do not work out wake up error, reflash the CPU
program, and then copy and paste the software to the TF card again. The
procedure to reflash CPU is as the same as that to solve token
limitation as the following link shows:

How to Use Engine Diagnostic Machines

In 1996, by order of the Environmental Protection Carprog Agency, engine diagnostics became standardized for vehicles sold in the United States. As a result, diagnostic coding is the same in a Ford as it is in a Chevrolet or a Chrysler. The process of accessing a vehicle's second generation on-board diagnostic system is the same, as well. A handheld computer is needed. The functionality this type of device covers a broad spectrum. Cheaper, simpler diagnostic machines are simple OBD-II code readers, while the more sophisticated scanner can do much more.
1. Insert your diagnostic machine into the your vehicle's data link connector. For most vehicles, this 16 pin-receiving outlet can be found in the leg space on the driver's side of the vehicle. It will either be under the steering column or to the left or right of the steering column.
2. Switch the diagnostic machine on. Some of the higher end scanners have a self-activating feature, whereas some of the more simpler code readers may need to have the power button pushed.
3. Turn your vehicle's electrical system on. Doing this depends on the brand and type of OBD-II scanner. Some will need to have the engine running.
4. Issue a retrieval command. How to do this also depends on the specific device you own. Button locations do vary and some scanners use a manu system. Also, some scanners are preset to automatically pull codes from a vehicle's computer, once a data stream is sensed. For the exact instructions on how to do this, consult the manual of the device you own.
5. Look at the codes on the device's screen. Often, they will be differentiated by their status in the vehicle's computer. Some codes will be labeled as "faults" or "trouble." This means the codes have happened quite frequently, and the system has activated you vehicles service engine soon light. Other codes will be labeled as "pending." These are still recorded malfunction, but they have occurred a little less frequently than fault or trouble codes. Pending codes do not active a vehicle's service engine soon light.
6. Look at the first character in the OBD scanner on the screen. This letter will tell you where to look for the problems. "P" stands for "powertrain," and the codes correspond with problems in the engine. "C" stands for "Chassis" and the codes correspond with issues in the electrical system. "B" stands for "Body" and correspond with mechanical issues not associated with the engine. "U" stands for network communication
7. Look on your device for something akin to "live data." Simpler code readers may not have this function. You can shift out of code reading mode and obtain readings from your vehicle's many sensors. This way, you can find outoil pressure and engine revolutions per minute. If your scanner has this feature, it quickens the troubleshooting process. Many of the OBD-II codes correspond with specific engine sensors. If you have only a simpler code reader, you will have to check these sensors independently, usually with a continuity tester and a volt meter. Maxidas ds708