xHP Flashtool: Official Beta Results Thread for 6HP21

[trebila]

I noticed 2 issues in 3rd-> 2nd downshift in D mode stage 3 v1_0 :

- coming to a stop slowly, I can hear and feel a "clunk" in the transmission, when the AT downshift from 3rd to 2nd (low rpm, around 1000 rpm). I think it occurs during the ongoing clutch phase. not smooth, and certainly not healthy for the clutch.

-coming to a stop rapidly, the trans downshift from 3rd to 2nd too soon, I can hit 2500 rpm when going in 2nd, not smooth at all, then it upshift immediately after in 3rd when I release the brake pedal and slightly accelerate. It should stay in 3rd the whole time.

 

[doublespaces]

Here is a fix by @RayBan for the coding issue:

Concerning the "Retrieve vehicle details" issue:

This should be already fixed in the meantime, as it is related to the backend, not the app itself!

The coding bug:

This happens a lot since release, as many cars have being flashed in the past with WinkFP, but haven't been properly coded with NCSExpert afterwards. On newer cars this is obvious, because of the paddles not working, on older cars, this is not noticeable for the driver. Only if you retrieve the fault codes, you will have a "coding missing" error.

This prevents reading of the coding, which we do at the end of the backup. So that's the reason, why guys were sitting 30 minutes before their tablets and then got the error. We now changed that, so that this pops up immediately on start of backup. So that does not safe one, from coding his unit properly before applying xHP, but at least it is visible instant and get's messaged accordingly.

This issue never popped up the last 1.5 months, as it is very specific to 335i drivers using the Alpina flash.

For all those, who have NCS Expert, here's the way to code your TCU:

- Copy the file attached in your C:\NCSEXPER\PFL folder
- Start NCS
- Load Profile  Expertmode FSW PSW Manipulate ohne MAN
- Hit F2 (Chassis), Select E89
- Hit F1 VIN/ZCS/FA
- Hit F3 ZCS/FA f. ECU, select CAS
- Hit F6 (Back)
- Hit F4 (Process ECU), select EGS
- Hit F3 (Execute Job)
- Done

Please make sure that the text matches the functions on your F-keys in NCS!
if the text appears at another F-Key, use this one!

For all those, who don't have NCS, but payed someone to flash Alpina on to their car: Call them and tell them to properly code your EGS. That means, tell them to finish their Job.

 

[08_335i]

Tell them to finish there job, HAHAHA! Love it. Luckily I had NCS expert and was able to go in and do it myself. Flashing the backup as we speak now that it's fixed.

 

[trebila]

worked on another AT today, with Pure stage 2 turbos on straight race fuel (102 RON), with stage 3 xHP flash,

reported torque is maxing out at 1000nm up top.

 

[trebila]

I noticed 2 issues in 3rd-> 2nd downshift in D mode stage 3 v1_0 :

- coming to a stop slowly, I can hear and feel a "clunk" in the transmission, when the AT downshift from 3rd to 2nd (low rpm, around 1000 rpm). I think it occurs during the ongoing clutch phase. not smooth, and certainly not healthy for the clutch.

-coming to a stop rapidly, the trans downshift from 3rd to 2nd too soon, I can hit 2500 rpm when going in 2nd, not smooth at all, then it upshift immediately after in 3rd when I release the brake pedal and slightly accelerate. It should stay in 3rd the whole time.

@RayBan

Any update planed to fix this really annoying issue ?

 

[bradsm87]

I have not changed any torque limiter in the DME flash.
I don't need to.
As soon as you target an high load -> high boost target, and if actual boost reach boost target , you'll report an high torque without hitting a torque limiter.

So what were you doing wrong when you were getting torque limit active with xHP TCU flash? You said you made changes in the DME flash to fix it.

 

[bahn]

Torque limiters are not completely removed in the stage 3 flash for xdrive vehicles at least. Going above 552nm results in hitting a limiter. Torque act. is flatlined at 552nm with throttle closures and timing cuts. http://www.datazap.me/u/bellium/xhp?log=2&data=2-5-16-18-19-20&solo=2-18-20

 

[trebila]

Torque limiters are not completely removed in the stage 3 flash for xdrive vehicles at least. Going above 552nm results in hitting a limiter. Torque act. is flatlined at 552nm with throttle closures and timing cuts. http://www.datazap.me/u/bellium/xhp?log=2&data=2-5-16-18-19-20&solo=2-18-20

So what were you doing wrong when you were getting torque limit active with xHP TCU flash? You said you made changes in the DME flash to fix it.

The same thing than above : blindly raising L2T , because load is too low.
Again, it's a DME flash issue.

 

[trebila]

Could we move on about torque limiters, guys, and report wrong transmission behaviour, to help Rayban building a better trans flash?

If you get torque limiters, you're DME tuning is wrong.
So ask your tuner to fix it for you.

 

[bradsm87]

Torque limiters are not completely removed in the stage 3 flash for xdrive vehicles at least. Going above 552nm results in hitting a limiter. Torque act. is flatlined at 552nm with throttle closures and timing cuts. http://www.datazap.me/u/bellium/xhp?log=2&data=2-5-16-18-19-20&solo=2-18-20

There is a DME table in the XDF called "Torque Limit (Customer Specific) that some suspect is a 335xi-only table. Lower it lots and see if you get super early torque limit. If you do, contact Martial at MHD and he'll sort out a workaround.

 

[bradsm87]

Could we move on about torque limiters, guys, and report wrong transmission behaviour, to help Rayban building a better trans flash?

If you get torque limiters, you're DME tuning is wrong.
So ask your tuner to fix it for you.

Updating DME tuning knowledge with the new found TCU limit increases is all part of the process. My car is having diff repairs so I can't test but it's good to share some experiences and info so everyone knows how to deal with torque limits. I'm going to use stock load to torque and torque eff divisor, so I hope I don't have an issue, but it's always good to share some info.

 

[trebila]

Read carefully my previous posts, Brad, everything is explained.

 

[bradsm87]

Read carefully my previous posts, Brad, everything is explained.

Yes I know and I'm across the requirements. Are we sure 335xi owners don't have other limits though like the guy that posted earlier?

 

[trebila]

Who knows ?
If there is something specific for xi, I'd say it's in the DME, not the TCU.

 

[bahn]

The same thing than above : blindly raising L2T , because load is too low.
Again, it's a DME flash issue.

What are you even on about? Low load? This isn't a JB4... load was 220. The xHP guys just confirmed there's additional torque limiters in the transfer cases control unit. They need to add that into their documentation if that's the case.

 

[trebila]

lol, you target load 220 in the flash, but actual load is 160 up top, and as actual torque is based on actual load...

 

[trebila]

What are you even on about? Low load? This isn't a JB4... load was 220. The xHP guys just confirmed there's additional torque limiters in the transfer cases control unit. They need to add that into their documentation if that's the case.

I was not reffering to you, didn't noticed you had an xi.

 

[natedog7700]

Tell them to finish there job, HAHAHA! Love it. Luckily I had NCS expert and was able to go in and do it myself. Flashing the backup as we speak now that it's fixed.

How did you do it? I have NCS expert too. I tried following RBT's instructions but i got lost almost right away.

 

[Jeffman]

How did you do it? I have NCS expert too. I tried following RBT's instructions but i got lost almost right away.

I got Alpina flashed remotely by some guy in Europe years ago and I've never used NCS expert...I suspect I'll have the same problem. It would be great if there were some kind of Android app or add-on module for xHP to handle the coding.

 

[Cheezy]

Guys, visually double check and confirm your vin before you vinlock to a demo vehicle in Europe.