NefMoto

Me7.5, Audi TT QS... 018CA ecu... Car has intermittent N75 activity... mostly no duty cycle being applied to it and subsequent actuator only pressure.. During a drive for no apparent reason, n75 function will resume, and n75 duty cycle starts and its performing like it should.. However, no fault codes for anything for soft limp mode. IF when its woken up and n75 works, and you cycle the ign, you loose N75 again, and still no fault codes. New N75, works in output tests, plumbed correctly. ECU on vcds block 118 is not outputting any % duty cycle when the cars in its no n75 mode.. Request boost request is std QS levels (2000-2100mb). Read ecu files, and 95040 chip as backup. File is bog stock. Flashed a std bam 018H file into it and again, no N75 function.. Flashed immo defeat onto different ecu, std 018H file on it and it worked, N75 duty cycle worked. Flashed QS 018CA file onto another ecu, with its 95040 info and again no workie... Now, last test different ecu, modded 018H file for QS boost levels, immo defeated, first drive out, alls working.. Return and turn off, then restart again, no N75 again... wtf is occuring? I'm out of ideas here. Different ecu, different file, immo off.... same thing. No Fault codes at any time. Packet of biscuits to whoever can solve this puzzle! thx

Original immo off test file and readback after short drive and ign cycle resulting in no n75 again...
Can someone help describe whats changed and perhaps why?  No DTCs appearing at all on vcds
(http://badger-5.com/bin/immo-ttQS.JPG)

Logs.

I have logs which were showing 115,118vcds which I'll post up.

They dont show much tho... n75 working and not..

working then ign cycle not working
http://badger-5.com/bin/ttqs_stuff/018H-file-ok-ign-not-ok-LOG-01-001-115-118-ttqs-newecu-018h-immo-1.xls

not working
http://badger-5.com/bin/ttqs_stuff/018hfile-018ca-ecu-LOG-01-001-115-118-ttqs-17705-1.xls


Dan suggested this as he had some sort of thing on his TT, when using non vvt head with vvt/bam mapping..
Vvt not working properly, more than 3 degrees I think from set point will set 0 dc.. No error code either..

CDNWS set from 3 to 0 fixed his.. (he has no vvt fitted)

This car does have vvt... std QS TT

thx

Have you checked the wiring from the n75 plug to the ecu ?

Had a similar issue with a b1 s1 o2 ran new wires directly to ecu and issue was resolved.

unplugging n75 and ecu see's unplug and pops a faultcode
on output test n75 clicks on off fine wiggling all wiring near it doesnt effect it

if ign on, clear codes (no codes present) and start we have n75 working
then start car all works..
ign off and restart no n75, no fault codes, and if engine is still running clearing them does not bring n75 back top life..

this ones a doosey!
arghhhhhh

disco biscuits?  :-X

wired n75 direct to ecu..
same thing..

tried oe software on org ecu
tried another 225 018h software on org ecu
swapped ecu tried both oe software and 018h software

it will at best start from no % to n75 then spring to life for no apparent reason and work.. until you turn it off again, and it will not work again.

stumped

this has me stumped also...seems like it could only be hardware/wiring.

Could something else be shorting out and drawing the current away from the N75? like something you coded out but still have physically equipped?


you sure the address to the map you are changing is correct?

IDK..wierd issue you have there, please post the fix and actual problem after you figure it out.

No chance you're running a 2.0 ecu?

No, ecu oe one is 018CA TTQS
Tried other wideband box, 018H TT225 software, std, modified, mapped.... and seemingly every combination possible.. vvt disabled, enabled

Wired N75 direct to ecu output from 12v feed.. (did'nt cut off/isolate the factory output, just disconnected factory n75 plug and used my test lead direct.

Odd idle behaviour also... idle will raise to 1050rpm from 880rpm norm and sit high for ages, blip throttle and it will rev quick and clean and return to 880rpm..  if i blip throttle to 5krpm, revs take an age to drop sometimes, but not others.. Coincidence?  I dont know.  Swapped throttle body for a "was working when removed" one and it would fail basic settings..  Replaced throttle body a.n.other spare here and that worked ok, passed 060 tba fine.

Weridly.. again.. seems like there's a lot of this on this car, if I run the car on and off load (on my dyno) after key start, it will sit 0% N75 but come to life at some random point whilst I go on the gas on and off repeatedly..  Whe it does come to life, it stays alive until you next cycle ign then its gone again.  No codes being thrown at all during this.  IF I prod the throttle rapidly full on off on off on off, making the car jolt when taking up load on off (low rpms 1500-3500rpm) the N75% comes to life only after a short delay.  Car presently is wired back as std on factory wiring I should mention.

Never ever seen such a thing

Is there anything likely between the throttle revs on idle raising on their own (whilst 062 block on throttle remains 12.9% ) and the rev hangs which it randomly suffers?

Possibly  a bad ground had a MK5 a while back did some crazy things made a grounding kit all the weird problems went away.

hmmm.
At this point I will consider pretty much anything.. lol

I'll add/check some grounds.  TTQS has battery in boot as std after all... some distance for the voltage to travel I guess.. remote earthed vs motor..

wish me luck!

thx

Any reason why you can't get ME7L logs?

You should be able to see where/why it's happening by logging the right variables.

Is B_ldr being set?

Is LDRPID outputting 0%dc or is it getting cut down in LDTVMA?

Is it being triggered in DLDR?

If you're logging 0%dc then the cause is being registered in the ECU somewhere and the list isn't really that long.

thanks for posting phil
just got me7 logger going (I dont use it much, but it connected first time on this car :) )

N75 output duty cycle is sat at zero..
logged B_ldr is 0 until I prod acc pedal on off rapidly and it will come to life.

linked logged parameters.. and the read file from this std TTQS for ref.
>> ECU read>> http://www.badger-5.com/bin/ttqs_stuff/8n0906018ca-0261208086-1037375111-qs-read

>> csv logged just now whilst its sat on my dyno>> http://www.badger-5.com/bin/ttqs_stuff/8n0906018ca-0261208086-1037375111-qs-read_template_20140221_170847.csv

Please add pedal acceleration and throttle plate angle to your logs.

added throttle plate.. not sure which parameter acc pdl acceleration is..
you will see initiall full throttle nothing, then me rapid on and off pedal and it starts to work.

wped for pedal? just added and re-linked below


>>log>> http://www.badger-5.com/bin/ttqs_stuff/8n0906018ca-0261208086-1037375111-qs-read_template_20140221_180317.csv

thankyou for reading

Looks like you've narrowed down the problem to BBLDR.

WGDC is 0 because B_ldr is clear.

Do you have any RAM variables from BBLDR that you can log?

Your accell pedal position sensor is broken.

Thats where we've got to in poke and hope terms.. another pedal coming tomorrow.

What in the log makes you see accell pedal position sensor is broken nyet?

I see wped = 100 and plsol > 2000 mbar and b_ldr = 0

It would be easier to see what's going on with a real pull.

Op, are you just stabbing the pedal in the logs or is pedal position dropping out?

Uh seriously? ECUxPlot can't even run any of its filtering because your ped position and throttle plate are flapping like an autistic child's arms.

Also, in the future, try to get a full run with the pedal to the floor from 2.5k to redline.

Were you tap dancing on the pedal?

I was assuming so because of this

B_ldr looks fine in the area where ped is constant...

Hard to tell much from that log really.

There's no delay so the bit should set instantly when the desired PR is greater than one which it fails to do numerous times thoughout the log.

I am stabbing the pedal as said, as this for whatever reason brings it to life

nyet

You may have missed the bit where I say "only" when I stab at the pedal does the thing come to life. I could do full pulls pedal to floor and nothing happens at all.. Thats why I have'nt logged it, it shows N75 doing nothing..
I cant figure why stabbing the pedal always brings it to life, and thats why the pedal log last posted looks erratic as hell, its because I am stabbing it. (tap dancing on pedal :) )
Apply pedal down in normal driving, it does nothing... no n75%

weird huh?

yes..  I was. thats why its flapping..
smooth throttle nothing works.. only stabbing the pedal brings it to life..

N75 has been wired direct to ecu also to test, same fault continues.
when the car first came in it has 17705 fault code which I thought was the usual issue, but no codes have ever come up since, no matter what software I have flashed in, on different box, same box, etc.... the fault is constant.

If on real road test, or longer running up and down the box simulating road drive, sometimes, randomly the n75 will come to life.  Its coming to life remains until next ign cycle, and its dead again.

Only if I stab the acc pedal on off tap dancing stylee does it start up working again, pretty much on demand.

I've never ever seen anything behave like this..
If ecu's unhappy, and limp mode type event, no faults logging seems just weird.

Its behaving like the 17705 faultcode would do, but without throwing out that code.(or any for that matter)

Ah. I see that now as well.

Anyone able to think of a potential cause for this weird behaviour?

thanks

Can you post a clean 3rd gear pull?

It's not weird behavior, something is wrong.

Have you looked at BBLDR?

The answer is there.

Log any variables that you can in BBLDR to help narrow it down.

And this, with BBLDR variables if possible

Hi

There was no more time to do logs, customer wanted his car back.

However, the fix, unexplained as it is, was we swapped the accl pedal for another one and the problem went away.
Not a single fault code thrown during this whole episode

Weird huh?

Car now runs as it should.

Not too suprising; that is a common failure mode with resistor pots... they're fine when at a static position, but if you move them around a lot, the sweeper hits dead spots as it sweeps and the output drops in and out.

thanks for your help.

weird something like a dbw pedal unit would not fault out given its importance..

2 x pots in the pedal which should track each other (reverse direction to each other) and two more in the tbody also, all 4 of which should mirror each other, yet in this instance all looked ok, pedal sweep worked, yet n75 output remained disabled until stabbing the pedal.

most weird.

The lack of faults baffles me too! Like you said, that is the whole purpose to having 2 pots.. unintended acceleration and all that..

Just glad you got it sorted.