PROBLEM WITH N20 TMAP SENSOR

[cupra]

I have the n20 Tmap sensor (7843531-01) with plug & play bms, and the start i always get the error code 2ABD.


Right now I'm using jb4 G5 iso and the AFR1500= 1 to work properly, with firmware 19.hex


Anyone else have the same problem?


My car is a 2007 6MT (never been updated the DME).


Any solution other than removing the TMAP sensor?

[bigdnno98]

Did you email Terry? I was running the same exact setup and it worked fine.

@Terry@BMS

I have the n20 Tmap sensor (7843531-01) with plug & play bms, and the start i always get the error code 2ABD.


Right now I'm using jb4 G5 iso and the AFR1500= 1 to work properly, with firmware 19.hex


Anyone else have the same problem?


My car is a 2007 6MT (never been updated the DME).


Any solution other than removing the TMAP sensor?

[Terry@BMS]

No known problems. Perhaps a wire is loose or your sensor has failed. Either way swapping back to the stock sensor would be the next move. Unless you have a single turbo or VT3 turbos there is no need for a 3.5bar sensor anyway. I would not run more than 20psi on the RB setups.

[cupra]

with TMAP sensor of stock 2.5 no problems, only when using the TMAP 3.5 I get this error (2ABD).


The wires are well (adaptar bms n20 Plug & Play)...... and i must fix this because will be a problem for VTT.

[ChuckD05]

maybe a failed sensor like T said... and a failed caps lock key?

[cupra]

I installed and removed several times the TMAP and always the same error.
The sensor is new, unusual for this broken.
It may be for the cobb flash bms?

[Terry@BMS]

It could be something on the JB4 side but then again if it works with the factory sensor that rules out the hardware, and since many others are running ISO19 on the N20 sensor without issue (myself included) that rules out the software. I've written up ISO20 that has a bunch of 3.5 bar sensor software changes so if you want to try that out of desperation you're welcome to.

[cupra]

terry, gladly i try the firmware 20 to see if this can solve the problem.


I Publish data with the results

[Terry@BMS]

Just email me then. You need a different interface also to use it.

[cupra]

I guess you're out or busy. Because I sent several emails and have not received a response from the emails sent to you yesterday and today.

[Terry@BMS]

Yes, have a full box of emails to deal with before I can delve in to helping you. Patience is a virtue.

[cupra]

Thanks T.
I'll try and hope it is resolved and i may post a good news

[cupra]

No has been fixed the error 2ABD.
He started the car and the error goes in immediate.
The case that the car runs right, but not good to drive so

[Terry@BMS]

The only other possible cause might be some very old DME software that is checking for sensor plausibility with the engine off. With the engine off the JB4 is off and the sensor will show an out of range value.

[cupra]

I think the same. .. i will update the dme and try to see if I have luck.

Will post results for if anyone happens the same problem

[cupra]

We have updated the dme and now everything works perfectly.


I hope it will help somebody, if has the same problem.


Thank you all for the comments.

[tomsti]

We have updated the dme and now everything works perfectly.


I hope it will help somebody, if has the same problem.


Thank you all for the comments.

Hi.
I have jb4 g5 and when I install the tmap n20 with its adapter, the car starts fatally and stops. I put the original tmap again and register it in jb4 with 0 and it is perfect. I have tried 2 tmaps of 3.5 bars new and the adapter is fine ... I do the process and I frame 1 when I install the tmap n20. I have tried to see if it gives a fault but does not give any maybe because it stops soon. I do not know where the problem may be, so I ask for help.
greetings.
The car is BMW n54 2007 from Spain with jb4 g5 iso,mhd flash,mmp turbos,PI precision ,stage 4 pump precision..

[Terry@BMS]

Make sure TMAP is set to 1 in the JB4 interface and that NOTHING has been setup in the BEF for a 3.5bar.

[tomsti]

Thanks Terry for your interest, I've tried everything and it's the same.
I put 2 new tmaps, 2 adapters, by jb4 doing the process correctly, by mhd with its equal process, I have made a backup of the dme ... and there is no way I put the tmap n20 and it always goes fatal.
In other n54 this process takes 2 minutes and in this car is very rare ... I would be removing jb4 physically and the controller split controller of the port injection ...
This car carries a lot of material and still because of this you can not blow hard ...
What else could it be? Will it be the DMD itself?
It is a BMW 335i N54 I8AOS and is at sea level, hear similar problems in cars at high altitude.

greetings!

[tomsti]

After doing many tests, I found the culprit of not letting me put the tmap n20.
Disconnect the split second controller for PI, and finally the tmap n20 works well ... I mention it for someone to help in the future ... I went crazy trying everything.
Greetings.

[shushikiary]

I'm currently having similar issues but disconnecting my AIC6 didnt solve the issue.

I read a proper 0.94 volts off the sensor when at idle (I'm at 5280 ft altitude) which is exactly 12.03 PSI, stock TMAP reports 1.64 volts in same situation, which again is exactly 12.03 PSI. So I know the TMAP is working right, yet the second its plugged in I get 2ABC and 3100. I checked continuity of the harness as well to be sure. IAT reports properly as well.

I think the DME is just unhappy with the voltage being so low that is being reported by the TMAP, because 0.94 volts on the stock TMAP is like 6.4 PSI, way to low for the ECU to ever see so I think the DME thinks the TMAP is bad because of the altitude.

[Dean@RFP]

What you need is to lower Map Min voltage in XDF or have your tuner do it. I usually set it to 0.70 or 0.50 volts. That way it don't trip out when car turns on. Common issue. Also I read somewhere that older firmware ECUs don't like 3.5bar tmaps and it causes plausability issue (2abc)