Alfa GT PROXI Align Failed - Flashing Odo
Posted: 05 Jun 2017, 15:16
Hi MultiECUScan forum.
Recently got an Alfa GT 3.2 with a flashing odo, it was reading incorrect much lower KMs compared to the number of KMs listed on the Engine ECU.
Using MultiECUScan I can copy the number of KMs listed on Engine ECU and write to the instrument cluster so they can match. The instrument cluster continues to count from this number within normal discrepancy as mentioned in the sidebar notes when you check the odometer reading on the Engine ECU.
When I try to do a Proxi Allignment i get this error
Writing to module: Dashboard Node (NQS)FAILED
When I connect to the instrument cluster using MultiECUScan 2.8 and an ELM327 Cable, Windows 8 tablet I can see the build date on the instrument cluster reads 2005, yet the vehicle is a 2004 model.
I'm guessing the instrument cluster is not original since when I got it the KMs it was reading was much lower and it was flashing.
Any easy way to correct this?
Have tried Proxi Alignment several times, same error.
Recently got an Alfa GT 3.2 with a flashing odo, it was reading incorrect much lower KMs compared to the number of KMs listed on the Engine ECU.
Using MultiECUScan I can copy the number of KMs listed on Engine ECU and write to the instrument cluster so they can match. The instrument cluster continues to count from this number within normal discrepancy as mentioned in the sidebar notes when you check the odometer reading on the Engine ECU.
When I try to do a Proxi Allignment i get this error
Writing to module: Dashboard Node (NQS)FAILED
When I connect to the instrument cluster using MultiECUScan 2.8 and an ELM327 Cable, Windows 8 tablet I can see the build date on the instrument cluster reads 2005, yet the vehicle is a 2004 model.
I'm guessing the instrument cluster is not original since when I got it the KMs it was reading was much lower and it was flashing.
Any easy way to correct this?
Have tried Proxi Alignment several times, same error.