lancerrally45

iTrader: (22)

Hey Guy,

My car is no where finished on the tuning however I ran into this the other day. My 1b load freaks out and my 2b load stays steady. Check out the pic and let me know what you think. My factor is 1.4 now, ive tried changing that however it does nothing. This is on my 2.4lr. Stock turbo for break in. Thoughts on the LOAD only. I dont feel like explaining myself on the rest. Thanks guys!

My thoughts: Is it as simple and making my maps larger? Since 2b is hitting over 350, and moving the scaling factor to 1.6?

ReaperX

iTrader: (5)

If your maps only go to 350 load, rescale and retest.

lancerrally45

iTrader: (22)

What the best way to rescale the map? I used the excel however it only goes to 350.

ReaperX

iTrader: (5)

You click on the load axis in the rom and just change it like you would if you were adjusting the timing or fuel at a given point in the map. I'd suggest going to 400 on your load scale.

Starting with the 210 load change as follows:
210 - 220
220 - 240
230 - 260
240 - 280
250 - 300

Then increment by 10 until the end of the axis.

lancerrally45

iTrader: (22)

Yeah I saw that, but then it messes up another table. Id have to go back and look. I was looking at a thread on max load people are running, and I see people have to ignore the IPW, because that limits the car to a certain load. 379-380 I believe. I understand that a 2.4 is going to move more air, but at the same time I wonder if I have a boost leak. Ive tested it a million times. I may have to give it another go. This is also on a stock maf unhacked.

ps(my tables already are at 350)

ReaperX

iTrader: (5)

Rescaling your load in the Tephra roms wont screw up another map. When you change the load axis on one it does it for all of them. Rescaling in the original mitsu rom would monkey with the EGR process, but not with tephra.

lancerrally45

iTrader: (22)

Gotcha, I was adding in more columns. Theres no way to add more in? You just have to rescale it and take away some lower in order to add some higher?

I have an idea, change column 350 to 370. It hits 360ish for 1 or 2 cells, then backs down lower. I wonder if this would work. Changing one will change all of maps to 370.

domyz

iTrader: (6)

Don't know about how you did it, but make sure you change the 1b factor in the rom AND in evoscan.

Nerdy note:
Max load factor is calculated like that
1byte=8bits,
in binary terms it's a "word" (00000000,00000001, 00000010, etc...)
so 256 possible values including zero
max value is 255


255*1.2=306 max load
255*1.4=357 max load
Goes like that.

ReaperX

iTrader: (5)

This too.

lancerrally45

iTrader: (22)

I already changed the conversion factor to 1.6 to fit the Correct load. I upped the last load of 350 to 370. It now logs fine however I'm breaking up still at lower loads. Must be plug gap.

lancerrally45

iTrader: (22)

Changed a bunch of things, Put in BR7ES plugs (may have been a step to cold at 8, it isnt breaking up at the top of 4th anymore). Changed the conversion to 1.6. Mess around with a few other things. (I forget I did it all at once). Went out and it started to read fine. Did a pull and now it will stop logging once I start a pull. So I downloaded evoscan and ecuflash again. Im just heading out to see if it worked.

I was getting an Error code :

Error: ML Write command error. (FT_Status: 4)

Causing it to stop logging when I did a pull. I can read/write using ecuflash, and it will start logging but as soon as I get on it, it shuts down. Like its getting overloaded... Weird.

domyz

iTrader: (6)

If it logs at steady speed, maybe it's related to a loose usb port or cable?
There is not more information uploading when you go WOT.

Boosted Tuning

iTrader: (12)

That logging issue just has to do with your 1Byte Load factor, in EVOscan and the ROM. It has nothing to do with rescaling your load axis on your maps, even though they shoudl be scaled properly for the amount of load your seeing.

lancerrally45

iTrader: (22)

You are correct on why it wouldnt read. However, now it wont log due to an error in evoscan.

I thought it may have been a loose connection so when I can log, i move the cable around everywhere, to see if I have a loose connection. It continues to log, so I know its not a loose connection. I was thinking it was the drivers, so I reinstalled evoscan and ecuflash. Ill go test now.

lancerrally45

iTrader: (22)

ANNNNNDDD Bingo, I can log a full pull now. Cars........ psh.