-
Hey Guest one of our sponsors Progressive Parts is running Black Friday and Cyber Monday offers - more details here
Bottax
Guest
Bottax
Guest
Yes, I have changed (the dealer change...) the ECU and fix my problem... but the HW number and SW number of my old ECU is the same of new ECU... so I have not remapped it, beacuse I want to know where is the problem first (the dealer will not change it anymore without take a lot of money 
).
Here in Italy i know same people that have remapped the FR 1.8 20VT (2004) from different tuners, but all get the errore 17704 P1296.
It seems that older versions of 20 VT (in Italy called TOP SPORT ) are not affected from this problem beacuse a lot of people have done an ECU tuning with great results.
).Here in Italy i know same people that have remapped the FR 1.8 20VT (2004) from different tuners, but all get the errore 17704 P1296.
It seems that older versions of 20 VT (in Italy called TOP SPORT ) are not affected from this problem beacuse a lot of people have done an ECU tuning with great results.
Last edited by a moderator:
Dam! Personally, I was afraid of this..!
We were also thinking that the fault is related to this series of HW & SW. Same series pop same error on Octavia RS.
Fact is, I think there are remapped FRs that work just fine. I asked about this problem at Upsolute in Austria and at REVO in UK. They did not encounter this problem.
What tuner remapped ur car?
Did you or some of ur friends try and upload another version of software..? Or the factory values?
We were also thinking that the fault is related to this series of HW & SW. Same series pop same error on Octavia RS.
Fact is, I think there are remapped FRs that work just fine. I asked about this problem at Upsolute in Austria and at REVO in UK. They did not encounter this problem.
What tuner remapped ur car?
Did you or some of ur friends try and upload another version of software..? Or the factory values?
Bottax
Guest
This is a dimsport issue!!!! yes? it's in the standard and tuned maps, so going back to stock error still occursCrize said:
sounds like they loaded the wrong software version when they remapped it.
see thread in JBS section re: jabba - different problems, similar reason.
see thread in JBS section re: jabba - different problems, similar reason.
No wrong Sw version... wouldn't work, I guess.
New content has different valid checksum!
For the checksum to be met, some bits are written in presumably empty or unread "areas" of the eprom. My gues is tuner was accidentally writing in an area that, at this version, was not empty.. or unread.
DimSport also updated comunication .dll of their software in the process of correction
Personally, I am pissed by the fact that it never crossed my mind to look for this error, specifically for our type of engine/implementation. I would have not find it... proving beyond any doubt that it is an ECU problem.
New content has different valid checksum!
For the checksum to be met, some bits are written in presumably empty or unread "areas" of the eprom. My gues is tuner was accidentally writing in an area that, at this version, was not empty.. or unread.
DimSport also updated comunication .dll of their software in the process of correction
Personally, I am pissed by the fact that it never crossed my mind to look for this error, specifically for our type of engine/implementation. I would have not find it... proving beyond any doubt that it is an ECU problem.
johneno
Guest
If the car has mapped cooling its usually the fault of the mapped cooling sensor that comes complete with the plastic water housing that fits on the side of the head! however you can get the same fault code on vehicles without the mapped cooling sensor, (oh yeah this sensor is not the temp sensor). This has been known to be a fault with the themostat housing and the fixture onto the engine!
Similar threads
