Multiecuscan

Firstly I had better tell you that I have a 2001 Alfa Romeo 147.

I decided to purchase FES to perform a Proxi Alignment, as the price of the software was the same as getting an independant diagnostics company to perform it. Anyway long story short the Proxi Alignment failed to execute, heres the log:

Reading CAN configuration data ...
CAN CONFIGURATION DATA:
00 00 05 4B 00 00 05 4B 00 00 00 03 00 00 00 01 00 00 00 00
00 00 05 4B 00 00 05 09 00 00 05 4B 00 00 05 09 00 00 05 01
34 36 37 39 33 39 32 34 20 20 20 44 54 53 49 45 45 50 44 45 20 20 00 07 11 4B 05 00 00 09 05 00 00 48 00 00 82 26 07
CURRENTLY CONFIGURED CAN MODULES:
Body Computer Node (NBC)
Engine Control Node (NCM)
Dashboard Node (NQS)
Brake System Node (NFR)
Driver Door Node (NPG)
Climate Control Node (NCL)
CURRENTLY AVAILABLE CAN MODULES:
Body Computer Node (NBC)
Engine Control Node (NCM)
Dashboard Node (NQS)
Brake System Node (NFR)
Driver Door Node (NPG)
Climate Control Node (NCL)
CAN MODULES THAT REQUIRE EOL PROGRAMMING:
Body Computer Node (NBC)
Dashboard Node (NQS)
Driver Door Node (NPG)
Climate Control Node (NCL)
5/8/2011 12:01:41 PM
CONNECTED TO:
ALFA 147 1.6 TS 16V 120CV
CAN Setup / PROXI Alignment Procedure
--------------------------------------------------------------

CURRENTLY CONFIGURED CAN MODULES::
Body Computer Node (NBC):
Engine Control Node (NCM):
Dashboard Node (NQS):
Brake System Node (NFR):
Driver Door Node (NPG):
Climate Control Node (NCL):
:
CURRENTLY AVAILABLE CAN MODULES::
Body Computer Node (NBC):
Engine Control Node (NCM):
Dashboard Node (NQS):
Brake System Node (NFR):
Driver Door Node (NPG):
Climate Control Node (NCL):
:
CAN MODULES THAT REQUIRE EOL PROGRAMMING::
Body Computer Node (NBC):
Dashboard Node (NQS):
Driver Door Node (NPG):
Climate Control Node (NCL):

EXECUTING ADJUSTMENT...
PROXI Alignment Procedure
Writing CAN configuration data ...
Writing to module: Body Computer Node (NBC)SUCCESS!
Writing to module: Dashboard Node (NQS)FAILED!
Timeout error
Writing to module: Driver Door Node (NPG)SUCCESS!
Writing to module: Climate Control Node (NCL)SUCCESS!
FAILED TO EXECUTE


I assume it's failing because of the timeout error when attempting to write to the Dashboard Node, (if that is the case why does it carry on and write to 2 more nodes?) however, assuming the Dashboard Node is the "clocks" then I have tried the procedure with 2 different sets and the outcome is the same with both. I understand there is problems with the procedure on some cars, the 147 included. Is this just something that needs to be ironed out with software updates? I can wait, I have put up with the flashing for a year now but its really starting to get on my nerves!

Thanks in advance

Hi,

As, of version 2.8 of multiecuscan there is no problem with the PROXI procedure on 147. If it fails then it could be caused by the interface.
You can send me a report so that I can see where the problem is. You have to click the red "Send Report" button after excuting the procedure and disconnecting from the car (you have to be connected to internet when sending report).
What is your interface? The PROXI function does not work well with Bluetooth interfaces.
Some of the drivers hav a setting for latency. It should be decreased to minimum.

Hi,
I replaced the dashboard of my car Fiat Bravo 1.9 MJT 150cv Sport 2007 model with a picture mounted on another car and the problem that I can not perform the alignment by proxy .... multiecuscan failed

snorky wrote:Hi,
I replaced the dashboard of my car Fiat Bravo 1.9 MJT 150cv Sport 2007 model with a picture mounted on another car and the problem that I can not perform the alignment by proxy .... multiecuscan failed

If the dashboard was on a 2009- vehicle, the proxy aligment is impossible, there are differences in electronics between the dashboards.

With the instrument panel was on a car of 2010 ....

yani wrote:Hi,

As, of version 2.8 of multiecuscan there is no problem with the PROXI procedure on 147. If it fails then it could be caused by the interface.
You can send me a report so that I can see where the problem is. You have to click the red "Send Report" button after excuting the procedure and disconnecting from the car (you have to be connected to internet when sending report).
What is your interface? The PROXI function does not work well with Bluetooth interfaces.
Some of the drivers hav a setting for latency. It should be decreased to minimum.

Sorry for the slow update, currently having laptop trouble. It will no longer boot the OS so I have sent an email to support@multiecuscan.net containing my hardware and license key and hopefully I will be able to get FES installed onto a new laptop and then I can send you the log Yani

I am using an ELM 327 1.3a interface, when I get up and running again I will try adjusting the latency.

Thanks, Shaun

Okay I have sent off the report and also I tried different latency settings. Still fails

Hi Yani, any news?

In the Faulty ELM Interfaces thread, a user has posted:

Shadeyman wrote:Hey Argo

Thanks very much. Removed the R04 resistor and BINGO, everything works!

Proxi-alignment & Service Reset both working perfectly.

Do you think its worth a try? I have no problems connecitng to any other ECU's so I'm unsure whether your method of modifying the interface will work for me, however I will have to investigate the pcb when I have time.

Thanks

Well I actually have a different board to the one in the original post and to the user who removed that resistor. Do you have any help for me Yani or should I just give up?

If you can connect to Body Computer, Instrument Cluster and other ECUs then you don't need to make modifications to the interface.
I can see in the report that there are still some latency problems. I don't know why this happens with some ELM 327 interfaces and does not happen with other interfaces. It could be a driver issue.
Anyway, I have improved the latency correction in next release both for VagCom/KKL and ELM interfaces. You can wait for it and try again...