I just redownloaded to make sure, but it comes up 8409. Unless that is an error in his file, that is still how it comes over for me, and that's how I have it.

 

Ok it's odd I get 8408.
But in MUT 12 I have 8409.
Anyway, good luck finding your problem

 

I have the same thing.
I just noticed my Closed Loop on/off value is 255. Also, what formula are you using?

 

So fireroasted should get new XML definitions to make sure that no adress is messed up.

 

So do you all have 255 as the value to turn the system on? I still can't figure out why mine is so irrational. at least my WB behaved as expected on my track without any issues but I flashed a zero in that value to turn the system off and all was fine the next morning.

 

I compared the .hex mrfred uploaded that we were supposed to copy and it had a 1 for the on/off value. I have no idea why mine is 255. It may have something to do with me running V7. I know it's working though my afrs were 14.7ish now they're around 16 per my maps. What formula are you using?

 

Did you possibly alter the range for the analog output on your LC-1? Is it possible that you hooked up the narrowband simulation wire and not the wideband analog output wire?

 

I have been using the MrFred log without USB cable mod for a long time now, and that has been working fine. So I know I didn't need to modify the voltage scaling or the formula into evoscan, and it was the brown wire for the LC1. It was straightforward when I did it a couple of years ago. I am assuming if my WB logging has and is working as expected then the hardware and its setup into the ECU is fine, and its something about this mod I still have wrong.

 

Is this the formula you're running in evoscan, 0.03137*x + 9.06? If it's not then your 1/ml and bL/mL will be off. Also, ecu flash wouldn't display more than "AC..." on my AFR low word. I had to copy mrfreds which gave a dec of 44237 then convert it to hex to see that it's ACCD then enter that hex (0xACCD).
We're gonna get this damn thing working one way or another!

 

Yup, I am using the 'default' formula and have the 31.9 and 289 values in the tables.

 

You had some bad settings even if you redownload the patched ROM...
I'd say that your xml isn't pointing the right adress in the ROM for one or many tables.

You could check them or start over the process (backup ROM and XML definitions before doing that )

delete old xmls
redownload xml definitions from tephra v7 thread
redownload mrfred's patched ROM
recopy over your fuel,ign, and all your tables from backed up ROM (leave the stock v7 definitions there)

There is no harm for trying that, except time waste if it doesn't work

 

I agree. Seems like everything you've done is right so it's got to be an issue with the XML.

 

Yikes, I don't think I am going to get into that, at least not now. I am not using V7, but rather a self patched ROM with many modifications. I am a little worried about recreating that correctly all over. Its likely the cause of my issue and I don't have the confidence that I will be able to repatch everything I need. Essentially, I could make things worse by breaking something else.

 

mmmm.. this is quite easy...

what have you patched for now? I'll help you with a step by step if you want.


or........ I'm feelling helpful: you could send me your rom and xml and i'll convert this to tephra v7, and I'll assure you that this will be a perfect match.

 

Guys,

Any advice on how to remove this patch correctly without breaking my existing LC1 AFR logging functionality. I was never able to get this to work, and I am chasing a very frustrating knock at cruise problem. At about 70 load I get about 7 or 8 counts. Not all the time, but its consistent enough.

I have tried old timing maps, Cams maps, LS, AFR, etc, everything that was in place when I didn't have this issue. (I have cruise logs from setting the injector scaling, and no cruise knock). One of the only modifications that I can't completely go back on is this mod. I have it turned off, I think, but I am desperate to solve this weird cruise knock.

Any ideas welcome. I am struggling, and have spent the last 2 days logging all different kinds of my old maps and attempts to make this knocking go away. It is not present over 120 load.