I hope it is not a problem with the long coding.
ABS could communicate with the ECU via UDS protocol. If it is the issue, there will be no solution.
I will work on it further.
I hope it is not a problem with the long coding.
ABS could communicate with the ECU via UDS protocol. If it is the issue, there will be no solution.
I will work on it further.
Will this tool be available in a future update ?
hi i can confirm that car dose not use the UDS protocol as to old ,also dose not use long coding . as it is 9N polo production from 2004 to 2009.
from the 2010 polo6 / 6R and 6C on-words use uds and in the polo 6r and 6c uses the long coding with the vin / immodata in the long coding
thats good news. I will investigate it further.
Iw would be much easier with the car as I woukd use some CAN tools.
Benrebuilds: Yes the tool for vag coding will be availabe in the next build.
Great stuff will be massively useful
Is there a way to get activation i waiting 2 weeks windows broke key
Sent from gaitnieks.lauris@gmail.com
hi any feedback ? . any new updates? .
new build is planned for Saturday
Dear Jadzwin,
I returned to V2 to check downshifting, and yes, Dq500 shifts down 2-3 gears(like stock ecu) when the pedal is pressed accelerator by 50-60 percent, this does not happen on V3. And another problem with upshifting on V3 mode S or M gears 1-2 7000, 2-3 6800, 3-4 6500, 4-5 5800, I checked on V2 and there 1-2 7300 and all the others are also higher. This Dq500 software on the Maxxecu control unit shifts all gears up to 7300-7400.
Next week I will have time to analyze the data.
What I need is a log from V2 and V3 as in the same condition when you upshifitng on S or M. I want to compare the TPS and torque.
I also need both base map you used for test to compare. The three important things are torque, losses and throttle position.
The changes in code were minor but I will compare and eventually, I prepare some different firmware for you to test.
Thank you. I tried different options with torque, nothing helped. I am now using V3 and the same software for Dq500 on V2 does not make upshifts, for comparison VC3 mode D all upshifts occur around 2000 engine revolutions, on V2 upshifts occur at 4000 revolutions.
It is very interresting. However as something works on V3 different than on V2 it should be quite easy to identify the problem.
I will make for you log on v2 with the same torque in dq map.
a few versions ago I noticed that I could start the car without pressing the brake pedal, but now it doesn’t work anymore. what’s the problem?
if you enabled Cruise cobtrol then the brake pedla is required.
For DSG is not required when gear lever is on P
oh, thank you. I will try to off CC and check start.
Hey,
This is more of a ‘just for fun’ request more than a need but would adding needle sweep for the tacho and speedometer output be something that could be added?
Not sure if there is a bug with the state of ‘F. IAT Correction’, it reports NO when it is actually active and working - in this case removing 2%, which can be seen in that log field and the Lambda Target is 0.02 less than from table:
This also highlighted something else - I export the Lambda Target From Table as a CAN message, as it is not in the standard stream:
Yet in my log file, at the same point as the above screen capture, the Lambda Target From Table is 0.01 less:
I have checked previous logs that use this CAN export and it appears to have a discrepency of 0.01 everywhere. Originally I thought this may be a rounding issue, but it is shown in EMU client at 0.xx precision, no higher:
could you please send a log ?