CRP 12X Premium FAQ

Here we list some frequently asked questions and answers relating to Launch CRP129 Premium （crp123 premium）.
Question: System halts when reading data stream. What is the reason?
Answer: It may be caused by a slackened connector. Please turn off the CRP12X Premium, firmly connect the connector, and switch it on again.

Question: Screen of main unit flashes at engine ignition start.
Answer: Caused by electromagnetic disturbing, and this is normal phenomenon.

Question: There is no response when communicating with on-board computer.
Answer: Please confirm the proper voltage of power supply and check if the throttle has been closed, the CRP 129P is in the neutral position,and the water is in proper temperature.

Question: Why are there so many fault codes?
Answer: Usually, it’s caused by poor connection or fault circuit grounding.

Warranty
THIS WARRANTY IS EXPRESSLY LIMITED TO PERSONS WHO PURCHASE LAUNCH PRODUCTS FOR PURPOSES OF RESALE OR USE IN THE ORDINARY COURSE OF THE BUYER’S BUSINESS.

LAUNCH electronic product is warranted against defects in materials and workmanship for one year (12 months) from date of delivery to the user.This warranty does not cover any part that has been abused, altered, used for a purpose other than for which it was intended, or used in a manner inconsistent with instructions regarding use. The exclusive remedy for any automotive meter found to be defective is repair or replacement, and LAUNCH shall not be liable for any consequential or incidental damages.

Final determination of defects shall be made by LAUNCH in accordance with procedures established by LAUNCH. No agent, employee, or representative of LAUNCH has any authority to bind LAUNCH to any affirmation, representation, or warranty concerning LAUNCH automotive meters, except as stated herein.

http://obd2lily.mihanblog.com/post/134

Make Key for Fiat grande punto 2007, VVDI2 or FVDI?

Intention:

Make key for Fiat grande punto 2007

Prepare job:

Read BCM eeprom 93c86 data with Xhrose VVDI Prog programmer.

First attempt:

VVDI2:

read bcm EEPROM 93c86 with vvdiprog, uploaded to vvdi2? key programmer the file and give me “unknown version”. Read again as microchip and same problem. I think vvdi2 has bugs on this car.

FVDI commander (FVDI2)

Then get FVDI2, go to Fiat program, key maker, select car, uploaded file and give pin and position to make key. Made transponder and programmed key correctly with it. Key worked like a charm.

Hope it helps!

http://hmilycar.blog.fc2blog.us/blog-entry-75.html

What Causes TPMS to Fail?

TPMS Direct explains some of the causes of TPMS failure

Sensors fail primarily due to battery failure or improper service procedures. Initially there will be a learning curve for installing and checking the Tire Pressure Monitoring System (TPMS Tool), but most service technicians quickly learn how to identify and service the system efficiently.

●   Sensor batteries can become discharged and fail – the internal lithium battery is not serviceable, and it has a life expectancy of approximately 5-7 years.
●    Installing the incorrect valve core will cause failure – TPMS sensors require a special nickel-plated valve core instead of the regular copper or brass valve core
●    Normal tire changing procedures can damage a TPMS sensor – this includes flat repairs, new tire replacement, snow tire change or a wheel upgrade
●    Pulling a typical looking rubber valve stem out of the wheel will lead to a broken sensor. TPMS systems now use either metal or rubber valves
●    Over tightening a new sensor valve will result in a broken sensor
●    Typical road hazards – collisions, potholes, curbs – can damage the TPMS system
●    TPMS sensors contain delicate electronics that are subject to failure over time

Like most things, TPMS are not invincible. Such as ATEQ VT55 OBDII TPMS Diagnostic Tool. Curbs, potholes, and just streets in general pose hazardous conditions to our aftermarket wheel and TPMS Sensors. Unfortunately we cannot control that but we can save you from the dealership! Our sensors are 100% OEM replacement, they are the same exact sensors that are in there right now. We buy in large quantities direct from manufactures to ensure that we always have availability, and that we provide the best prices anywhere.

http://blog.qooza.hk/obd2tools?eid=29127536

How to SD connect C4 LAN & WiFi Configuration

Topic: How to configure SD connect C4 LAN & WiFi to solve DAS fault (1.1)-1.501.9500.

Tool: a clone SD Connect C4

Software: 2011/3 Xentry

Status: I’ve started up SDNC to see if the connection is okay, and it turns green when I connect the multiplexer via LAN, but when I try the wifi it stays red. It can also read out some data from the multiplexer so I am assuming the the multiplexer is working fine too

Error: If I connect it to a car, DAS keeps popping up the (1.1)-1.501.9500 error (as I understand that must be some kind of communication problem). The car’s wiring is fine as KTS 520 can communicate with it.

Photos:

See the ceaser test post results

see the error message DAS gives

SDConnect toolkit says that my mux is available, but when I click on the button in the middle I get an error message, with an error code 750. That button is supposed to be for searching for multiplexers. This kind of gives me the impression that something isn’t quite working right :S
In the toolkit admin, it displays a serial number, says the mux is available. See in the attachments.

Solution:

It’s working!!! (At least it’s working via LAN, have not tried WLAN yet.)

I can’t believe it :O

Changed value in cal.ini to PART_W (to be exact, didn’t need to change it, it was PART_W, just left it that way :P).

As for the rest of the instructions, I haven’t been able to follow them exactly. I also got a vid with instructions and it’s a little bit different (I’ll post it here if anyone needs though). For example the LAN IP address is 172.29.127.112, but it seems to be working that way. Also I haven’t been able to configure the “road WLAN”, because it doesn’t matter what I enter into the “key” field, it keeps saying that the key cannot be divided by 2 and therefore it is not hexadecimal

Hope this isn’t going to hinder my chances of using WLAN…

But I’m going to find out in a few anyway.

EDIT: Also tried with LAN IP: 172.29.127.119, it doesn’t make a difference. MB SD Connect Compact 4 works with both IP-s.

Damn….I clicked on the “Delivery condition” button in the SDconnect toolkit, and now I cannot turn on the WLAN on SDconnect. I think it wrote something into the MUX’s software :S

The LAN connection still works though, so the MUX is not blocked yet luckily….

Look here: Mercedes Star Diagnostic SD Connect Compact 4 LAN & WIFI configuration

SD connect C4 LAN configuration

SD connect C4 WIFI configuration

http://obd2lily.mee.nu/why_choose_real_mb_star_c5_with_engineer_software

ATEQ VT55 Replaces TMPS Sensor Tool

Just so you know, we're no longer supporting the TPMS Sensor Tool (T/N AKS06200060); we've replaced it with the ATEQ VT55 OBDII TPMS. The old TPMS sensor tool won’t work with the Accord Crosstour, and the VT55 is just a better tool all around.

Like the TPMS sensor tool, the VT55 works with the HDS to learn new tire pressure sensor IDs or to find a tire pressure sensor location. Youll see these procedures listed in the HDS as Sensor ID Learning and Sensor Position Check, respectively.

Unlike the TPMS sensor tool, though, the VT55  at Obd2tool.com can also work solo as a quick means to check tire pressure sensor operation. Its large LCD screen lets you see if a tire pressure sensor is actually transmitting and exactly what it transmits.

For more info on the VT55, check out “Meet the New TPMS Sensor Tool!” in the December :08 issue of ServiceNews. And if videos are your thing, be sure to look up “Meet the VT55” in Tech2Tech. '

The ATEQ VT55 is a TPMS diagnostic tool. It is compatible with all currently known TPMS sensors including OE, Universal, Programmable and Aftermarket Sensors.

Supported Languages: English, French, Spainsh, Polska, German,Cestin,Italian

Read and diagnose sensors, OBD2 ECU reset and transfer data to ECU

Note: With most vehicles, if the vehicle is in “learn mode” the vehicle will also confirm that the TPM sensor has communicated to the ECM with a series of horn beeps.

ATEQ’s VT55 OBDII reprograms Asian or European vehicles (including Toyota, Honda, Nissan, Hyundai, Kia, Mitsubishi, etc) which do not feature a TPMS self reprogramming software

https://www.gamerlaunch.com/community/users/blog/4750493/1891782/tool-q%26amp%3Ba%3A-ready-to-tackle-tpms-service-