Technical Trying to connect 1.2S 2014 to multiscan

[pitbullharry]

I am using the ELM327 USB with the yellow adapter and trying to connect to the Engine module to read a possible fault code. Whatever module I choose I cannot connect to any of them. How do I know which of the control modules I have to select. I have tried them all and each one fails to connect. I know the lead can connect to the car as if it scans via F11 it will find modules on the car.

I am sure that the yellow module is the one I need as according to the multiscan site I need the ELM327 module and the A3 adapter which it says is the yellow one.

 

[Baglady1990]

Don’t use an adapter for the engine

 

[chris3234]

Don’t use an adapter for the engine

This for the engine ECU and abs I think you don't need a adapter

 

[puntodeltathema]

As others have said, you just connect the ELM without coloured adapter for reading the engine ECU. MES will generally always tell you if you need an adapter - if it doesn't prompt, don't use one.

Also - your car is on the change point from Euro5 (what MES calls CF5) and Euro 6 (CF6), so try both.

 

[forzaf1]

What error are you getting when you try to connect?

 

[pitbullharry]

It seems I need the registered version as the engine managment options were in Red not Blue. So will sort this out and try again without the adapter. The website seemed to indicate that you could read codes with the free version but alas not.

So I just try all of the engine management options until one works?

 

[forzaf1]

You will need to pay in order to access your car and fix any errors. Free version is just a teaser.

For engine, you just need the standard black cable. It will read it just fine when you have paid over and registered.

 

[pitbullharry]

Well registered and can now connect but as expected no fault codes left!

The car had a timing belt change and I had similar issue with a Fiat Panda 1.2 that had the timing belt changed and gave the exact same issues but despite the usual Fiat procedure of "eeny meeny miney mo change this part and it might go" the problem was never fixed and kept coming back. That car was sold as it was turning into a dangerous money pit.
Same 1.2 eengine in this car and behaving exactly the same. Girlfriend was scared both times the issue happened so need to fix it or Fiat will be got rid of.

 

[chris3234]

Well registered and can now connect but as expected no fault codes left!

The car had a timing belt change and I had similar issue with a Fiat Panda 1.2 that had the timing belt changed and gave the exact same issues but despite the usual Fiat procedure of "eeny meeny miney mo change this part and it might go" the problem was never fixed and kept coming back. That car was sold as it was turning into a dangerous money pit.
Same 1.2 eengine in this car and behaving exactly the same. Girlfriend was scared both times the issue happened so need to fix it or Fiat will be got rid of.

Does the car misbehave in anyway or just get the EML light comming up?



As the EML and usually a misfire code comming up at motorway speeds is a common issues caused by a phonic wheel relearn not being carried out after a timing belt change