that's what i was thinking.. however, when i zeroed out the right side BEC table in order to find a good WGDC curve... it still does it.... pretty sure the correction interval wouldn't be a factor then.... when i was running a MBC and WGDC of 100% across every value.. it sounded fine..

the correction right now is 1. I will make the changes re-flash and test tomorrow... a friend of mine @ 1320ms told me to check the 3 port first.. make sure that return line to the intake.. (which apparently is optional to connect) was disconnected first.. he said it would dtertmine if the EBC is the issue.... he said if the EBC uses a stepper motor.. it would cut on intermittent and make that sound...

capped the intake port... and vented to atmosphere that connection on the EBCS and it worked for the first pull.. but not the second and third...

 

im having nearly the same problem as corey121389 had but slightly different.

i did everything exactly how he has done, copied the tephra v7 xml pack into the rommetadata folder for the evo, downloaded the 94170715 rom, and even tried renaming it like he did but all i keep getting is unknown rom image error message. what am i doing wrong?

last time i tried doing this i effed my ecuflash program up for like 3 weeks before i could get it to work again and open a regular rom. PLEASE HELP!!!!

 

donation sent....for 90550001 v7

 

Hello

i had my stock ecu retuned by Big Al of DynoFlash.....however the Stationary Rev Limit was not set......

i would like to have it set.....any ideas?

by the way i'm from Guyana south america

 

Hello,
I have me current BIN professionally tuned and works very well.. Nevertheless I am missing several superior features in V7 mod. Can you give me an advice how migrates current MAPS value to V7? I have used big map translator but it does not work well for me. The Fuel map has different scale then source part in Excel sheet. The boost control is also driven different way.
I will very appreciate any recommendations or experience.
Regards
J.

 

Couldn't find it, for AFR safety boost drop feature,

What pin at the ECU does the WBO2 analog out 2 go?

Already have the analog 1 going to the ECU, just need to know the pin to send the 0 - 5VDC signal from my LC1 so I can use the AFR safety feature (before I blow up the engine)

 

Ok I have asked in other threads and have pmed a couple people with no response. I have V7 rom 9653076. I recently hooked up a GM iat sensor and wired it to pin 77 blue and white wire. I go to log it with evoscan request 09 and I get 195F as a reading with eng off. Actual air temp is 65F. V7 already incorporates the mat patch but looking at the scaling table it reads all the same. What do I need to do to get this to read properly?

 

Anyone else having 1-byte load not reflect actual timing in the map? I have tried 2 v7 roms and they both do it. My 1-byte load can say for example 260 load /6K rpm and 12 degrees timing advance. However in the table that should be 8 degrees advance. 12 degrees is down around 230-240 load at 6K.

Im logging timing at request 06. I thought this was the timing after compensation.

Is the problem my load logging or timing logging?

 

Request 06 is correct. Must be the load. I assume that your load factors are the same in Ecuflash and Evoscan?

From my observations at least, timing values can be interpolated between cells in the table too.

 

Well, I'm figgering the safety feature runs off the WBO2 signal from the O2 sensor itself, unfortunately this is not really a 0..5VDC circuit as the wiki page states. If it was, I would just use my LC1 analog 2 (0..5VDC output). Since my ecu is not using its signal from my existing LC1 analog 1, which is wired to ECU, I'll just set up LMPro to output 1.00 volts at say 12.99 AFR, ECUFlash at 1.00 volts, flash it, shut off my both primary and backup methanol pumps, and see what happens. No wiring needed

 

Yeah same load factor, both 1.3x.

Its not just a little bit out either as with between cell interpolation, its way off, like 4-5*

Say the timing map says at 260 load 6K rpm = 8 degrees. My logs say at 260 load 6K rpm = 12 or 13 degrees. So its adding 4-5 degrees over what my timing map says which is BS. I thought it had to be load logging related but its done it in 2 different v7 roms now, 9626 and 9055.

Whats niggling at me though is that around 230-240 load at 6K the timing is 12-13 degrees, and 260/1.3 x 1.2 = 240........but both the rom and evoscan have 1.3x as the load factor.

 

there might be an inconsistency between your loggers response of load rpm and timing, with timing being the slowest to respond . If you visually shift the timing fwd .3 or so sec and looks correct that might be the case Otherwise it might be overcompensated as error somewhere . my timing does the same, but only1-2* on the low side of things

 

Yeah thats possible but it'd be almost unique to me which would be odd. The load I'm hitting at given boost levels is about right so it seems legit, just really strange.

Your issue may be air temp timing compensation? If its 1-2* lower than the table.

 

Can't help but to emphasize on my New Year Resolution for 2012 once again

V7 for 88570008!

 

Just curious if the 1byte load log is obtained prior to MAF scaling. The load value I log is consistently 20% lower than the actual load being used. This is confirmed from logged AFR_MAP and timing which is hitting higher than the load log. My MAF scaling is 1-2 units higher in this area.