As the thread title says, I had my Abarth remapped at the weekend and ever since, my OBDII code reader can't connect using the KWP2000 protocol like it did before the remap. I don't suppose anyone knows why that would happen? The car is running fine and a battery disconnect for 30mins hasn't fixed it...

The car is going back again on friday to have another remap (free of charge) as I've just changed my induction pipe for a GSR one so they're going to have a look at this issue as well to try and figure out what's up... just wondering if anyone had any ideas so that we have a starting point

Mabye the software they put on your ecu isnt EOBD compliant?

I know the standard stilo ecu is with the software it came with as i use one of these cheap elm 327 things on mine all the time its not been remapped at all though.

Never heard of that problem.

I can read mine OK (not OBD compliant anyway) and I know Bozzy could read his after AT remap

It's strange The remapper was really suprised as he's not come across this before. The remap apparently doesn't change the main ECU processor coding (his words, not mine ), only the fuel/injector/ignition map, so theoretically, shouldn't affect the OBDII code reader at all... weird, eh.

might be obvious, but you did remember to turn ignition on?

Did you bend or push in one of the connections in the OBD socket?

Did the tuner map your car through the OBD socket or did he have to remove it from the car? Some ECU's have to be powered on a bench to be written, might be something not connected back right?

Like your tuner said, the base software remains the same - they merely change parameters in the memory.

Wierd one...

OT: Hows the car running since the map, power wise?

It was an ECU out job, so as you say, maybe something isn't quite right now. I'll have to disconnect the ECU cables tomorrow and have a look to make sure all the pins are okay

Yup, the ignition was on as usual. When the OBDII reader tries to connect, I get a whine, which I assume is either the fuel pump priming or the Selespeed pump (something like that)... which usually only happens when you open the door or turn the ignition on. I even tried to connect while the engine was running and that caused the engine to misfire as it was trying to connect... tres strange

Greggers said:

It was an ECU out job, so as you say, maybe something isn't quite right now. I'll have to disconnect the ECU cables tomorrow and have a look to make sure all the pins are okay

Yup, the ignition was on as usual. When the OBDII reader tries to connect, I get a whine, which I assume is either the fuel pump priming or the Selespeed pump (something like that)... which usually only happens when you open the door or turn the ignition on. I even tried to connect while the engine was running and that caused the engine to misfire as it was trying to connect... tres strange

Click to expand...

I know with a lot of the alfa/fiat bosch ecu's they connect them on the bench, sometimes they can only be written to in boot mode which is acheived by bridging some pins.

Definately worth checking the connections. What are you using an elm or a hand held code reader?

Dan

It's a hand held U581 code reader. It's been brilliant so far, although I did have some trouble with it initially as it tries a number of different protocols before it gets to the KWP2000 one that the car uses. As it tried the other protocols, the car would through up loads of errors like ASR failure etc... I fixed it by making my own cable that only had the KWP2000 pins connected, eh voila, no more errors

I believe that the 2.4 uses the Bosch ME7.3.1 ECU... it's shared with some Alfas as well

It does use the 7.3.1 and the CFC-209 for gearbox. There are a couple of pins on the OBD port which can be used for practically whatever a manufacturer wants, I think fiat uses these for airbag/abs etc..

Sounds like somethings not wired up properly, ive had my car connected to an Elm for loads of reasons and never heard a pump prime on connction attempts, or it misfiring when running.

Did they touch any wiring at all?

Greggers said:

I'll have to disconnect the ECU cables tomorrow and have a look to make sure all the pins are okay

Click to expand...

i would wait till you take it back, because then there will be no dispute as to who has bent pins, if any are bent.
also if they are its better if they unbend them as then if one snaps off it will be their problem to sort and not yours

Nope, they disconnected the ECU cables, removed the ECU, remapped it and then put it back in. Everything has been running fine it's just that my OBDII reader now won't connect

When you say that it sounds like something not wired up correctly, whereabouts do you mean? I wonder if something isn't quite correct in my ECU connectors... hmmm... I'll give them a good examination tomorrow

dave said:

i would wait till you take it back, because then there will be no dispute as to who has bent pins, if any are bent.
also if they are its better if they unbend them as then if one snaps off it will be their problem to sort and not yours

Click to expand...

Good point Dave. I'll take your advice and wait until Friday. The car is runnig fine so there's no hurry...

Be still my tinkering fingers!

happed 2 times to me:
1)mixed up input cable (obd directly into serial well.. via the adaptor ) so i guess some wires got crossed.. or it sent voltage back via obd port causing all sorts of weird things to happen abs airbags etc included + doing that caused engine to stall if it was on)
2)generic code reader at a small independent (no idea how or why.. same as above)

check your pins and cable (or better still try another reader – perhaps one they use at the remap place) other then that - posts above answer your q ;-)

Well... this is weird but it appears to have fixed itself. I thought I'd see if it was still buggered and lo and behold, it worked straight away! Strange... bt I'm a happy bunny anyway

Might just not allow you to look at whats going on while its relearning mabye?

just a random guess though :yum:

I have to admit, that was my thinking as well... I'm just glad that it's working again