7 replies to this topic

[jamesmpi]

Has anyone had any problems with ecu scanners not being able to communicate and connect to their ecu?

The garage that is MOT my mpi has tried to connect their scanner but it won't connect. I don't know what make/type of scanner they ate using but was wondering if there are any possible reasons for this? I assumed and these type of scanners are plug and play

[charie t]

not always, are all the fuses all in good order?
those micro scan crap that snap on sell don't communicate, same with a few others

[jamesmpi]

Thats makes sense. The guy who runs the garage is a friend of mine and knows a lot about carb'd minis but not so much on mpis.

He said the scanner is too "new" for my car so cannot communicate with it.

[icklemini]

My scanner is new and that talks to them ;) - Does depend on the make/model... none of the rover minis are (E)OBD....

[Shifty]

Why are they trying to connect it?

[charie t]

Why are they trying to connect it?

Fault code reading
As icklemini said age is not the issue, different programming is though
some newer scanners are only programmed to read eobd better scanners will read both
Have a run over to dave (icklemini) and great chap and has the code reader that does the business
http://www.trackroad...es/default.aspx

Edited by charie t, 21 September 2012 - 02:59 PM.

[Shifty]

I guessed that, but is it part of the MOT or is there a fault that they are trying to find?

[jamesmpi]

trying to find a fault. my mpi wont pass the emissions so he tried to connect his ecu scanner to see if any fault codes were being flagged up, but wouldnt connect

my mpi is a 1380 with stage 3 head, sw5 cam and 1.5 rockers so i think its a combination of engine mods with my FSE boost vslve which im sure needs setting up again.

im going to try and refit the standard rockers to see if that makes any difference. if not then i maybe forced to look at reprogrammable ECUs