5cyl rabbit
- 60-2 primtrig
- but sectrig is special
Attached are 3 files.
- "Bad RPM Reading...." is a log of the engine running poorly with the bad RPM reading
- "Running Normally..." is a log of the engine running normally with the 1.2.12 fw
- "TPTC Triggerlog" is a trigger log of the 1.2.30 fw taken after the "Bad RPM " datalog.
special setup, with secignore
- hints: ...
Normally after a few years, SD-erase is a good idea (2GB SD capacity used a few years ago was limited to a few thousand hours, even 8GB used nowadays is not infinite).
Updated a car from 1.2.12 fw to 1.2.30, and now I have a triggering/RPM reading issue.
The reason I changed fw, is because the car with the 1.2.12 is having problems with the SD Card logging -
It always took longer on this car, but lately it started not being able to access the log list at all. (SD-erase didn't fix or wasn't attempted ??
I noticed starting with 1.2.24 fw there is improved SD log support
BUT I could not find a download link for 1.2.24 fw, so I went to the next released/stable fw of 1.2.30
Anyway, with the 1.2.30 fw, the RPM reading is dropping 50% of value over and over again constantly, and the engine struggles to run.
I'm going to re-install 1.2.12 fw today, and try to access the SD Logs with the newer VEMSTune to see if that improves, and we need to see if the RPM reading issue goes away.
Any advice you have about the 1.2.30 fw, or if you have a better recommendation, I'd appreciate it!
Thanks,
Kevin Black