fixem2,

I actually have those tables, but those are for boost control.

I'm talking about the patch for boost logging and it's patch tables and instructions. Maybe they are related and I'm not reading into it enough since I don't use boost control via the ECU.

 

Sorry about that, for the 96530006 ROM there is no patch needed. The ECu logs that address perfectly. Use Evoscan to log the output from the ECU and you will be golden.

 

In my case, I will need to know what pin to wire my gm 3.3 bar into (I can find that easily).

Just so I don't have to look it up, what address are you logging?

 

I will have to get you the address tonight, I do not have my evoscan xml on this pc. Why are you wiring the sensor to the pin? The 05 Evo 8 has a MAP sensor already? DOes the GM not connect the same? Just curious.

 

I have something called an SSi-4 from Innovate, which allows me to log an additional 4 0-5V sensors. So, this is where my GM 3.3 bar and GM AIT sensor wired into right now.

 

First: I can confirm gear_head's success; logging this morning worked like a champ. I haven't made any live map adjustments yet, although I don't suspect there will be a problem.

Second: Your code compiles just fine with VB.NET Express 2008. I've resized most of the interface elements down to fit an 800x600 screen, so I'll give the live mapping stuff a test at lunch.

Third: think I speak for everyone here when I say "thank you".

(Eric: for the JDM MAP sensor, I'm logging request ID 0x38. I have to ask though, why are you logging both a JDM MAP and the GM 3.3-bar?)

 

All the "big beasts" of the Evo world are right into this ECU

 

logic,

I don't have a JDM 3-bar map sensor. I have been logging boost from my GM 3.3bar for years...before we had the boost logging patches and address for the JDM 3 bar.

 

Hmm. What about the EGR code needed a tweak? The immobilizer is trivial, but would an EGR problem have actually prevented the car from firing? I'm definitely willing to give this ROM another go, if it looks like there might be a simple fix.

Maybe I'll just ask over there.

 

The EGR/MAP sensor stuff stopped 88590015 from firing up my car (JDM IX with 88570008) - until I applied the 88590015 changes for a JDM 3 bar MAP sensor.

 

Ah crap, I completely forgot about that; I was just trying to get a ROM that fired, and didn't bother setting that up. I feel like an idiot; that would definitely be causing problems.

Looking at mrfred's original threads, I don't see locations listed for 96260009; have you (or anyone else reading this) worked out the JDM MAP sensor and direct boost control adjustments for that ROM yet? The voltage addresses listed there for the 9642xxxx ROMs look right, but the EGR MAP check tables are incorrect.

(I'm less concerned about direct boost control, but my car is a bad test subject for this without JDM MAP support. I was spoiled by 96530006, since that was already taken care of for me. It's interesting to me that a JDM ROM doesn't support a "JDM MAP sensor" out of the box...)

 

96260009 doesn't have EGR, and doesn't make any MAP sensor checks as it doesn't have one, but I believe you just wire in a MAP sensor and have to make no changes to the ECU. Only the JDM 9 has a JDM 3 bar MAP sensor.

So perhaps this doesn't help after all?

 

so does that mean us 05 USDM retards shouldn't switch over to 96260009?

or are you saying that we will be able to log MAP since you added the code into it?

 

Ah, so it's the same as the 96530006 ROM then (as far as MAP logging goes), if I'm understanding correctly. Then I think you're right, that's probably not it. I suspect the problem exists between keyboard and chair at this point.

On the other hand, your changes to 96530006 work like a champ. Logging (nice sample rate!) and live updating appear to work as expected. The live tracking of timing position was a nice touch. What baud rate are you currently running? (And if you increased it, did you find it worthwhile?)

kaymin: 96260009 hasn't worked for me yet, but that doesn't mean someone smarter than me shouldn't try it out. The MAP sensor should work just like it does with 96530006; that is to say, since there's no MAP sensor natively, there's no code to mess with. Just plug it in and go.

 

I don't exactly have an IAT sensor wired up yet and I don't really wanna try it on the MAF yet cuz my MAP is still a one bar so it's all pointless at this point. lol?

What IAT sensor is everyone buying to weld into the UICP?