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 can test 88840017 for EDM folks, even if I'm still waiting the harness for altmap. But IMHO there are more common IDs...

 

good stuff Dave,
as the stationary rev limiter in V5 was disabled with the valet mode mod.
90550001

 

hey baz - was stat_revlimit lost in the upgrade to 90550001 or the V5 mod?

ie did I cause it :P I will look into it when I get around to 90550001

 

Can you explain MAP averaging?

 

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!

 

Willing to test 90550001 too! Hopefully with v5.8 mod with Map sensor

 

That makes perfect sense. I somewhat assumed that is what it was I just wanted to make sure i wasn't off base. Good stuff.

 

Willing to test 88590015 w/ JDM MAP

 

Willing to test 94170015

 

I'm here and ready tephra!

96530006

or 96940011, if you can magic up some space in it

 

Me too! I'm using my JDM MAP sensor to log boost and and control direct-boost control via GM BCS.

 

Even though I just set up my v5, I'd be happy to help test 88590015 w/ JDM MAP and direct boost control. I can test the NLTS bug too and the toggle switch ... I just need the MUT change and the EvoScan code to log the flag.

 

yeah Dave I think it got lost when we went to v5
anyway no hassle whenever ya can stat rev limit dont cause any major issues but would be nice to have it back

 

Another 94170015 volunteer here.