Multiecuscan

Hi!

I tried to do PROXI alignment on my car - FIAT Punto 1.2 8V, make year 2005. PROXI alignment was successful, but now my car won't start anymore. It removed Engine Control Node, so now even Check Engine light does not come ON when I put ignition ON. What can I do?

Reading CAN configuration data ...
CAN CONFIGURATION DATA:
00 00 00 2F 00 00 00 0D 00 00 00 0F 00 00 00 0E
00 00 00 2F 00 00 00 09 00 00 00 0D 00 00 00 09 00 00 00 09
35 31 37 31 30 37 33 39 20 20 20 50 50 45 41 43 45 45 45 53 49 20 03 03 10 2F 00 00 00 09 00 00 00 05 06 11 03 01 0C 15 01 00
CURRENTLY CONFIGURED CAN MODULES:
Body Computer Node (NBC)
Engine Control Node (NCM)
Electric Steering Node (NGE)
Dashboard Node (NQS)
Receiver Radio/Radio Navigator Node (NRR/RMN)
CURRENTLY AVAILABLE CAN MODULES:
Body Computer Node (NBC)
Electric Steering Node (NGE)
Dashboard Node (NQS)
REMOVED CAN MODULES:
Engine Control Node (NCM)
Receiver Radio/Radio Navigator Node (NRR/RMN)
CAN MODULES THAT REQUIRE EOL PROGRAMMING:
Body Computer Node (NBC)
Dashboard Node (NQS)
19.10.2012 12:24:31
CONNECTED TO:
FIAT PUNTO '03 1.2 8V
CAN Setup / PROXI Alignment Procedure
--------------------------------------------------------------

CURRENTLY CONFIGURED CAN MODULES::
Body Computer Node (NBC):
Engine Control Node (NCM):
Electric Steering Node (NGE):
Dashboard Node (NQS):
Receiver Radio/Radio Navigator Node (NRR/RMN):
:
CURRENTLY AVAILABLE CAN MODULES::
Body Computer Node (NBC):
Electric Steering Node (NGE):
Dashboard Node (NQS):
:
REMOVED CAN MODULES::
Engine Control Node (NCM):
Receiver Radio/Radio Navigator Node (NRR/RMN):
:
CAN MODULES THAT REQUIRE EOL PROGRAMMING::
Body Computer Node (NBC):
Dashboard Node (NQS):

EXECUTING ADJUSTMENT...
PROXI ALIGNMENT PROCEDURE
Writing CAN configuration data ...
Writing to module: Body Computer Node (NBC) SUCCESS!
Writing to module: Dashboard Node (NQS) SUCCESS!
COMPLETED

It seems that you have a problem with the wiring of the engine ECU.
If PROXI shows that there is no engine it means that the engine ECU cannot send/receive data on CAN network. Check all connectors that go to this ECU.

Just wanted to post an update to this thread.

Actually, the ELM327 interface is to blame. I removed resistor from it the enable CAN communication, which I then successfully established. However, the connection was very poor (unstable) and multiecuscan would not let me do PROXI alignment due to unstable CAN communication. So I installed two resistors (without capacitors) and as a result CAN communication stabilised and I could easily do PROXI alignment. However, by making this mod to my interface, the interface itself disabled CAN communication with Engine Control Unit ... so not even Check Engine Light comes on when I have interface plugged in OBD2 port ... but I can easily establish communication with any CAN-enabled controller unit (dashboard, BSI, power steering). To start the car, I have to remove the interface from OBD2 port to "release" CAN network for the Engine Control Unit ... strange.

I'm pleased you are getting to the bottom of this problem.

This is probably the worst example I have seen of poor quality ELM hardware causing issues. Normally duff Chinese/other clone ELM devices result in no connection issues. From a hardware and timing tolerance point of view it is certainly possible in border line conditions for some modules to connect and respond and others to fail to connect and respond. This appears to be what has happened in this case if I understand you correctly.

Since the early days Yani has built up an Authorised Supplier/Distributor list and for me (a Gendan customer/user even before Yani got them onboard) a recognised source of hardware & software is/has to be the only sensible avenue to decent and reliable diagnostics. Anything else is likely to be a Russian Roulette game with possible vehicle immobilisation being a possible outcome in the worst cases.

I can quite see and understand why MultiECUScan does not yet support key programming functions. It probably has nothing to do with the ability to support such functions in the code but is more concerned with broken/immobilised vehicles due to hardware/other issues.

Well, I'm a computer engineer and I work with vehicle diagnostics daily, but I don't have a lot of experience (or tools) for Fiat vehicles, but I did get to the bottom of the problem relatively quickly. I was kinda freaked out in the first place, because I thought I'd have to manually reprogram all CAN based modules directly (EEPROM/MCU), for which I did not have time.

However, it is really strange that this happens ... I will try to add 560 pF capacitors and try again. I won't bother if anything goes wrong on Punto, but I need to make sure my tool works correctly ... next week I need to do PROXI alignment on 2011 Bravo, which was crashed. A few of my professional diagnostic tools only support diagnostic itself, but not the alignment.

One more note:
Some ELM interfaces have this exact behaviour when they are connected only to the car but not to a computer.
I've seen a few of this type. So, when the interface is connected to USB and OBD everything works fine. If you disconnect it from OBD (without disconnecting USB) then everything works fine. However, if you disconnect the interface from USB (and it is still connected to OBD port) then the CAN lines are locked.... and you get various error messages on dashboard.

Well, mine is not of their kind. It interrupts CAN communication to the Engine Control Unit even if it is connected to the USB ... that's why the Multiecuscan removed the Engine Control Unit in PROXI alignment - because it could not establish communication with it.

Also, in my case, there are no error messages on the board, just the temperature needle drops down to 0, because instrument cluster does not receive CAN frames about the temperature anymore.