Injection angle has huge impact for engine throttle response, so it is strange that it doesn’t help.
For Acc enrichment I add another 3D table with user define Axes.
RPM, dTPS, TPS and MAP
So user will be able to create own correction.
2 Likes
Thanks!
Will wait for the new table and experiment with it a little more, regarding the throttle response being strange that’s why I posted the other thread to check the firing order settings but I am sure they are correct.
Hopefully the new table will help.
Hi there,
I have a question regarding the rev limiter with the V3 software:
- If I set values (exp. 8000rpm) at Rev Limiter 1, will the Fuel Cut rev limiter have affect here, or the rev limiter set in CLT Limit?
- What is the preffered way on setting the rev limiter with the V3 software?
Thank you
Liridon
always revlimiter with the lowest rpm limit will be activated at the time.
hi, auto tune still dont work. it gives met 130 value when current is 75 and error is 0,08lambda
Do you use version 3.032c ?
Yes
Best regards Hermans Pieter
Technical director KCPerformance
could you please send me the log ?
Hi @Jadzwin_ECUMASTER how long till new software release to fix ACC?
Thanks
Middle of next week. There will be many improvements and bug fixes.
8 Likes
Any news for DSG USD Logging ( Clutch Pressure, Temperature, Slipping…) ?
For 99 percent it wont be implemented in Black.
Probably only in PRO
1 Like
HI evening so i found some kind of a bug from 3.031 to 3.032b
i found that the knock sensors and triggering false readings on 3.032b when i go back to 3.031 and 3.030 don’t have this issues
20240817_0835 v3.030 all OK .no knock error.emublog3 (5.2 MB)
current v3.032 knock issues bug.emub3 (60.4 KB)
attached is 2 logs
let me know if you need more information
I’ve noticed the knock sensitivity as well. From 3.31 to 3.32 the instances of knock in the logs is way more than the previous. I was going to log both versions today but perhaps the logs provided above will help.
I can do some logging If needed as well. Let me know
1 Like
I will analyze that.
1 Like
Do you have the project from 3.031 ?
There were no modifiaction to knock support in 3.032 so probably the problem is different.
about the knock sensing. on v2 a knock always looks like a real spike. on v3 its all way smoother. is that done on purpose or just a setting problem? i am on integrator 180. so normaly its a really rough graph.
here a log from v2 and v3. both with the same settings. i also needed to pull in .20gain to get to the almost same engine noise on v3. v2 i needed way more quiet. knock in v2 is the lowest graph in the picture. the spikey one
hi sorry for the delay .
I have used this file between the versions of firmware
current v3.032 knock issuse bug.emub3 (60.4 KB)
this is the file use for the logs
I’m experiencing a misfire issue when I load v3. The issue isn’t there on v2. I have a log where the misfire is present intermittently at idle and sometimes in low RPMs. Any advice would be great. This is on a 3rz-fe supercharged engine.
it is reallt hard to say without the log