TephraMOD V5.8 - testing help required
#1
TephraMOD V5.8 - testing help required
Hi Guys,
I am about the release version 5.8 of my mods, however I need some guys to help test out the various features and fixes. Here is a rough CHANGELOG for V5.8 over V5:
V5.8
- fixed NLTS load threshold bug - untested
- fixed issue where autovalet is enabled but revlimit is disabled - untested
- fixed issue where altmap_by_adc0f wouldn't change to altmaps if toggle switch was already ON when car first flashed - untested
- tried to fix an issue where valet mode would sometimes kick in after a flash - untested
- added 2byte->1byte load mod - tested by me.
- added MAP averaging - tested by me.
- changed injector scaling to be part of ROM block with altmaps (for jcsbanks mod)
- simplified code + removed redundant code.
So what I need is some volunteers, please post your ROMID and later this week I will post up some pre-V5.8 ROM - if it all checks out I will release it.
please be aware that you will need to delete your old XML
also this is totally untested, so again follow the usual precautions when flashing this to your car
notes:
* avg map replaces the original variable - if you want to log the original please log 0xFFFF8417
* ditto for the rear 02, so log 0xFFFF8409 for the real variable
* 0xFFFF840B has the 2byte->1byte variable so log that and then in evoscan multiple the "x" by whatever factor, ie by default use Eval="1.2*x"
88590015 - V5.8 TEST
94170015 - V5.8 TEST
96420011 - V5.8 TEST
88580014 - V5.8 TEST
ps - Don't PM me your ROMID requests for V5.8 - do it in this thread
Cheers
D.
I am about the release version 5.8 of my mods, however I need some guys to help test out the various features and fixes. Here is a rough CHANGELOG for V5.8 over V5:
V5.8
- fixed NLTS load threshold bug - untested
- fixed issue where autovalet is enabled but revlimit is disabled - untested
- fixed issue where altmap_by_adc0f wouldn't change to altmaps if toggle switch was already ON when car first flashed - untested
- tried to fix an issue where valet mode would sometimes kick in after a flash - untested
- added 2byte->1byte load mod - tested by me.
- added MAP averaging - tested by me.
- changed injector scaling to be part of ROM block with altmaps (for jcsbanks mod)
- simplified code + removed redundant code.
So what I need is some volunteers, please post your ROMID and later this week I will post up some pre-V5.8 ROM - if it all checks out I will release it.
please be aware that you will need to delete your old XML
also this is totally untested, so again follow the usual precautions when flashing this to your car
notes:
* avg map replaces the original variable - if you want to log the original please log 0xFFFF8417
* ditto for the rear 02, so log 0xFFFF8409 for the real variable
* 0xFFFF840B has the 2byte->1byte variable so log that and then in evoscan multiple the "x" by whatever factor, ie by default use Eval="1.2*x"
88590015 - V5.8 TEST
94170015 - V5.8 TEST
96420011 - V5.8 TEST
88580014 - V5.8 TEST
ps - Don't PM me your ROMID requests for V5.8 - do it in this thread
Cheers
D.
Last edited by tephra; Jul 23, 2008 at 05:49 PM.
#6
yup. basically if you look at any map sensor there is a bit of error in every sample that gets returned. add that into the fact that the engine is naturally "inny/outty" you tend to get bumps in the MAP signal.
MAP averaging just takes the last 3 MAP samples and averages them and sticks that in the original MAP memory variable.
Its a rolling average, so the next MAP sample that comes in bumps the oldest off the average and a new average is calculated.
Basically its useful for ECU direct boost because it means the ECU is less likely to make a bad WGDC correction decision. If the pressure is consistently low OR high then it will average out so. Currently you could get into a situation where direct boost keeps hitting the troughs in the boost curve and keeps trying to add WGDC..
sorry for the long explanation - I hope it made sense!
MAP averaging just takes the last 3 MAP samples and averages them and sticks that in the original MAP memory variable.
Its a rolling average, so the next MAP sample that comes in bumps the oldest off the average and a new average is calculated.
Basically its useful for ECU direct boost because it means the ECU is less likely to make a bad WGDC correction decision. If the pressure is consistently low OR high then it will average out so. Currently you could get into a situation where direct boost keeps hitting the troughs in the boost curve and keeps trying to add WGDC..
sorry for the long explanation - I hope it made sense!