OK, bummer...maybe I will try with the OBD patches first. I would like to run those.

I agree with the harness. Mine consists of a push button spst switch and two wires. One goes to pin 42 of the ECU and the other goes to the 5V source I have on my SSi4.

Hopefully, I can test tomorrow. Regarding the P0505, from what I read, I thought that adjusting your BISS while holding the ISC steady with Evoscan solved it? That and maybe the 96940011 stepper values?

The logging and ECU resets don't make me feel to happy, but I'll let you know what I find. If I can't get it done tomorrow, then this weekend on Sunday is the next chance I have.

 

P505 - ADJUST YOUR BISS.

search for a thread by ME with P0505 (or maybe just 505) in the title. some of the last pages show you how to fix p505 with biss adjustment

 

OK, finally got around to flashing this in place of my 96940011.

First I made sure my map switching was working, so I logged MUT 83 and it registers 253-254 with the switch activated, so that was good.

Then, I flashed the 96530006 ROM with Acamus' OBD II patch in place and fired up the car first try. I let it idle for a bit, switched to alt maps, brougth up LiveMap, and started messing around.

The map tracing of the ignition is pretty nice, so I started changing the idle timing realtime to see if it would take and it did just fine. I changed it back and it changed back without issue.

However, I did manage to either corrupt the RAM maps or mess up something in LiveMap. I did the read ign, write ign several times and kept clicking read ign and read fuel to make sure that the RAM maps were OK. One time, though, the RAM maps and fuel maps had all messed up numbers, like 38 where it used to be 5. I also read the fuel RAM map and that was all screwy too. The car started running crappy at that time, too, but I'm not 100% positive it was due to that or the normal 'idle issue' when converting to this ROM. Anyway, I shut the car down, restarted the car and LiveMap and the read ign and read fuel were fine again. So, John, does that mean it was fine all along and the app just went screwy or are the ram maps rewritten or something at startup? Come to think of it, it may have been after I was testing my switch to go back to normal ROM maps and alt RAM maps and then reading ignition again. But, I forgot now. Maybe leaving LiveMap running while I switched back and forth messed something up?

By the way, I used EvoScan to set the Biss, but once the ISC was allowed to recontrol the idle, the idle wouldn't come down from about 1500. Looking at the ISC steps, it was around low 20's and it wouldn't adjust lower to try to get to the idle speed target. So, I'm not sure if I just didn't mess around enough or if one of the ISCV tables need to be adjusted as well. I adjusted the BISS to a happy medium somewhere in between where the idle seemed fine.

Unfortunately, that's all the time I have to test it today. I will leave the 96530006 ROM in the ECU and run on the alt maps tomorrow to go to the gym, etc, and see if anything different happens.

On a side note, I noticed today (before testing this) that all three of my ACD lights were on going to the gym. The only thing I did yesterday was hook up my switch. After a restart it's back to normal, until I start driving for a few seconds, then all three illuminate. So, I have to look into what I messed up there.

John, if you read this, let me know what you think about the messed up values in the ignition and fuel RAM maps.


Eric

 

Eric,
Just a note, when you converted to the new ROM did you put 0011 values for idle stepper tables and such into the 0006 ROM? If so, revert those back to the original 0006 values and then adjust your BISS. SHould help.

 

Eric - you were running 1500 because the ECU had LEARNED the OLD ISCV values required to keep your idle correct.

after about 10 mins of idle it would have come down to 850 automatically.

go redo it hehe

ps - dont change your idle stepper table until you have a real problem

 

Nope, didn't change my ISCV values...left the 96530006 values in there.

Tephra, makes sense...I just thought it would have started adjusting sooner.

Just researched the ACD issue as well and looks like I just need to bleed the ACD system or top off the fluid. About to go check that now. It's about time for me to replace all the fluid anyway, so maybe it got a bit low and it's reminding me not to be a lazy ***.

 

Messed up values with sections of map moved could happen if a read is short or long, and then the remains of the buffer affect the next read/write. I will look into tidying up the buffers to stop this happening, but it should still be usable if you don't repeatedly press the read/write buttons. You can switch maps whilst logging no problem theough.

 

OK, just dropping in to give an update. Have been running on the RAM maps for the last few days and put at least a few hundred miles on and several startups and have had no issues to speak of.

So, other than the buffer issue that I saw the first day I tested, everything else has been running perfectly in RAM without any issue. Also, I have no CELs using 96530006 in place of 96940011, although I do have the acamus OBD patch(es) in place.

Now I have to learn how to put additional maps in RAM, what maps to choose, and possibly learn VB to make new tabs and enhance the app without bothering John every other day.

Although, John, that does lead me to ask whether or not you are going to implement this on a tephra v7 ROM (96530006) and if/when you will release a new Evo LiveMap with your enhanced features, such as the charting, etc? The reason I ask for a v7 tephrarom is because of the mass airflow mod that mrfred created and tephra added to his v6 and later roms. I ported that patch over to 96940011 and liked it a lot, and I guess I can give it a shot for 96530006, but if it's already done, may as well use the latest tephrarom.

Again, a tremendous thanks for the great work. Now I have to convince mrfred or you to implement SD for this ROM.


Eric

 

Wait, you have no DMA stream drop and ECU reset? Hmm, that makes me think it may be from the SES p505 code I keep getting. It seems to happen right before or right after the SES light goes on.

As soon as the rain stops, I'll adjust the BISS screw and hopefully fix that P505 error. Then I guess we'll see if I still get the issue I'm having.

I still think we should look at the 2k ram block and make sure nothing is getting clobbered.

 

Eric, I'm glad it is working. I'm not entirely happy that you can trigger buffer problems though, when the 9 is so bomb proof. I have been sulking about DMA on the 8 because the 96260009 has been such a PITA with check engine lights and stalling even when not logging and when running normal maps! I've not seen a thread on Tephra V7 yet, I'll go looking, but happy to update where there is demand. I will also add the charting etc.

Joe R, I have tested a version with a verify button that will compare the RAM contents with the ROM shadow area in an Ecuflash file. It can't test the Tephra 0xDEAD variable which I think is the problem on 96260009 because as soon as that gets overwritten everything it is fixed before you can log it.

 

John, tephra's released a first test of a 96530006 V7 near the end of the V6 thread, if you want a quick pointer to it.

 

http://banks.myzen.co.uk/9653chart.zip

Above is a version which has charting (hard coded scalings and items), live display of variables, verify button.

I have redone the logging table, and the order has to match what I've put for the charting and live display to work. I have not done all the work for you though...

So you need to create a new "MUT table" in ROM or RAM (you could put it near the end of the shadow ROM area) with these items (look then up from your original MUT table), and put its ROM or RAM address into the "logging address"live map application.

 

Any updates for SD for 96530006? Sorry if thats off topic

 

I think I was using the program wrong or something but when I pressed read from RAM the map that shows up is a stock map but it does trace properly. It's just that all the values in both tables are from a stock map and don't look anything like my map.

Just wondering if I missed something?

 

The RAM maps are your alt maps. Did you alter those? If not, then they are just the stock maps.