CTDan

Id love to be able to code PSE on all the time… please report back your findings.

MaxBlack

Typo, sorry 2013

Ken718B

When the car gets to the speed stated in the x value, the car will display the percentage of the value of the true speed stated in the value. Therefore, your codes indicate that from 0 to 250 kph, the car is displaying 100% of the true value, from 250 kph to 400 kph, the car is displaying 100% of the true value, and at 400 kph and beyond, the car is displaying 100% of the true value. Unless you are traveling more than 250 kph (155 mph), only the x1 and y1 codes are relevent. However, if you try adjusting these values and you decide that the adjustment should be different at different speeds, you can do that.

Attached is a picture from a PIWIS of the codes from a Canadian car. Note that the y values are greater than 100.

Valvefloat991

Thanks. That's very useful. Seems like I only need to correct the first two lines, as I don't spend much time above 400 kph (248 mph).

Ken718B

I agree. I was just saying that the codes give you more flexibility since you could reduce the x2 and x3 codes so that they are relevent. For example if you change the y1 value to 99 and that works well at low speeds but once you get over 100 kph it is too much correction, you could change the x2 value to 100 and the y2 value to 99.5 if that works better.

MaxBlack

So, I got the Thinkcar dongle, plugged it in to the OBD port, turned the key to accessory, and no blue light on the dongle as stated in the miniscule directions provided. Broken or doing something wrong???

Porsche_nuts

I got that the first time too. Make sure you push it in entirely and seated properly.

Valvefloat991

So you mean that you can not only change the correction factors, but also the speed break points for each zone. That makes more sense.

Ken718B

Correct. The x values are the speed at which the corresponding y value will be applied. This is all in my 718 coding guide just in case you don't have a copy.

Valvefloat991

Thanks very much. I did download your 718 coding guide, but haven't yet looked at it.

Meanwhile, I did modify the Speed Correction Factor as follows:

1 00.00 98.00
2 100.00 98.00
3 200.00 98.00

I've only had a chance to check one speed thus far, but with this 2 percent correction, 80 mph on my speedometer now matches the 80 mph show by Waze/GPS.

SUCCESS!

Ken718B

I thought it is a green light not blue light. Is the dongle going into the OBD port. Try pushing a little harder to make sure it goes in all of the way.

Ken718B

I will have to try that. Are you sure the Waze speed is accurate?


Based on our conversation, I will probably update the discussion in the guide.

If anyone has any coding that they have done that is not in the guide please provide it to me so I can include it in the next release of the guide. I plan on releasing the next version in the next week or two.

Valvefloat991

Who knows what's accurate? I have two GPS devices in my car. My Samsung Galaxy phone with its built-in GPS, which is what I assume that Waze uses. And my Escort Max 360c radar detector, which also has GPS.

After my recalibration of the speedometer, when the 911 digital display was showing 80, the Escort showed 81 and Waze showed 80.

I trust Waze more because the Escort typically reads about one mph higher than other GPS devices I've had. I suspect--but have no way of knowing--that the Escort is programmed to read one mph high in order to an attempt to reduce claims against the one-year ticket guarantee that comes with the detector.

At some point, I'll look for a measured mile and check the speed by measuring the time.

IXLR8

When doing coding, does it give you the option of saving the factory coding in case you want to revert back to it?

Valvefloat991

I don't know, but I've taken notes so that I can revert to the factory settings manually.