I got my tactrix cable the other day from tuner tools, it got here so fast I think they have a teleporter. It was still smoking on my porch when it got here. Possibly from re-entry.

Props to them for being the cheapest place I found to get one. And props to Mellon for the link / discount link on his page.

Final thanks go to the EvoM community for the handy getting started how-to on ECU FLASH. It seriously helped, even tho I'm quasi familiar with the process from DSMlink.

Now that thats out of the way... lets get into the meat of this.

I just purchased the car about 2 weeks ago. Car was supposed to have a dyno tune & flash already. Supposedly safe as well. With no way to monitor knock, I'm not naive enough to just go "ok". I had to see.

Yeah...

Something tells me both High / Low octane fuel and timing maps shouldn't be the same. I understand for consistancy's sake it will make the car more predictable. But, doesn't that remove any ability of the car to not break itself?

2; The part throttle boost on the car is horrendous. IDK if its bov, or fuel related. I've tried adjusting the bov and it helped, but then went back to sucking horridly.
Thoughts?

3; Internal ID= 96940011
I'm assuming this is the rom ID everyone speaks of?
Car is a USDM 05 RS. Does this look right?

4; immobilizer tab brings up = "a 4 digit number" lol! (note to self, don't put code on intarwebb)
Is this the code? Or is this the hex address or something where it was located? Sorry new to this.

5; I would like to do the CEL knock patch. Where do I begin? I've read the thread, but some insight or tips on my first patching would be sooOOooo helpful! My laptop sucks and I had to buy a car adapter kit to limp it along, it won't run on battery power anymore and this limits my logging ability. I'd like to have a visual cue to back off it w/o having it connected. This way I can get started trying to tune a bit without fear of causing major damage as the weather goes thru its wildy varied fall changes.

6; Does anyone have a stock flash/map for this car ? Since it was already flashed I don't have the ability to "go back to stock" and start from scratch. Which really bothers me. IDK if I can ask for this, and I'm not trying to ruffle any feathers. So if something I posted is asking too much, or out of line I am sorry.


Any help would be greatly appreciated.

 

a few thoughts...

Unless I'm mistaken, publishing your immobilizer key on the web is kind of like giving away the PIN to your banking card...

As far as the CEL knock patch goes, its not particularly hard, all the instructions are here on evom. I'd recommend you backup your rom and xml files before attempting the patch. I'd also recommend you familiarize yourself with ecuflash before messing around with this.

If you are going to tune yourself, get a wideband.

You are correct, high/low fuel/timing maps should not be the same.

You can probably find the stock map at openecu.org.

good luck!

 

I have the Innovate WB & gauge. I haven't set it up to log yet with mitsulogger. Which, I'm having problems making any use of anyway... I'm used to graphed logs I can scroll across with a dashboard that gives raw values. (DSMLink) I can't get it to sample more than once or twice a second either. There has to be a better way to do this. Has to. Maybe I was just spoiled?

As far as the immobilizer code... I dunno? What can anyone do with it without my car? What is it even used for?

Thanks for the heads up on the code bud. I'll keep digging.

 

If you have an Innovate wideband, then use LogWorks. It's very similar to DSMLink with the graphical interface.

I, too, came from the DSMLink world, so I know how you feel. However, with all of the new developments and tools/loggers, etc, there are some aspects even better than DSMLink. I think you'll be happy once you get everything sorted out.


Eric

 

Doesn't it just log the WB tho? What about everything else?
knock? temps, rpm, etc...

This CSV file nonsense, combined with the slow sampling rate isn't really useful to me.

Does Evo Scan graph with values?
Something I can scroll across?

If it graphs its worth the $25.

Or am I just missing something?

 

Evoscan is well worth the money - people usually use a mix of applications thou

Evoscan .99 graphs are a little buggy and I haven't played with 1.0 yet. Just use it as an overview and then use excel to get into the nitty-gritty details.

 

good question

 

Not sure if anyone answered this, but the immobilizer is hex

 

logworks (can use) uses the same cable as ecuflash from which it gets a number of info channels.
so you are capable of logging eleven channels in total. if you have another innovate sensor readed (lma-3 or other) you could log more.

evoscan is worth the money too. his updates are free.

 

Yep. Logworks can log everything, just like the other loggers. It works a lot like DSMLink's interface. Download it and test it out.


Eric

 

When you talk about partial throttle boost are you talking about how the car feels or actual boost values? You probably know already but you can have your boost running perfect but the car still feels weak (because timing isn't right).

What are you using the log boost by the way? Or are you planning to log boost? I'd recommend the JDM MAP sensor. I'm using a GM MAP sensor, but the JDM MAP would be much easier to use in my opinion.

I don't know if logworks has scrollable graphs, but I know ECU+ does.

 

Evoscan does have graphing. I also use Data Log Lab which was originally recommended by MalibuJack. Data Log Lab allows you to load up your csv file and graph/compare any of your parameters. The newest version of Evoscan will also allow this.

Both EvoScan and Mitsulogger can log as fast as the ECU can send the data.

Like others have said, get a little familiar with Ecuflash and your Rom ID xml file before diving into the editing...but it's not that difficult.

 

EvoScan does have graphing capability, but it's not the greatest. I often get different O2 values when highlighting the WBO2 curve and others such as load ... one says 11.5 and the other 11.2 at the same RPM point. Also, the graph is based on time and not RPM which, IMHO, is more useful. Spikes and dips (which are common in LC-1 logs in EvoScan) cause the scaling of the graph to be WAY off and you can't see small changes in the curves.

I'd suggest messaging Mrfred and getting a copy of his Excel file that graphs your logs and calculated HP and TQ from your pulls. You can modify it to suit your needs easily. All you have to do is copy and paste your pull in to the 1st page and it generates the log graph and HP/TQ graphs for you. It's an awesome tool and I use it almost daily.

 

Please expand on this just a little bit. I have the LM1 WB & gauge. I skimmed thru the manual last night and it says you have to daisy chain devices and feed each an additional input. As in, INPUT sensors to the devices AKA run signal wire to device. LM1 only has one input carrying capability.

How do I get 11? If I could get 11 out of it I'd be giddy. That would cover all I need to tune with once I get the preliminary stuff down.

Also, which knock value do I need to watch in Mitsulogger? Knock sum? I think the low sampling rate is in essence the fact I left just about everything on. If I drop the requests down to the core values needed to tune, I think I will get a much higher sampling rate. But I am unsure of what I truely need; do to alot of the tuning in ecu flash being determined by load values/scale.

I am used to having to do far, far less... input global fuel correction, dead time, and adjusting rpm based fuel % sliders to articulate specifc fuel needs. DSMlink automatically smooths the curve. Same with timing. Part throttle/ light load is already in the base programming of DSMlink. Once your original bases are covered its done for you. The car retains its medley of airflow based maps. And applies your changes into them accordingly. You never have to tweak each. Just one.

So I'm sorry if I'm asking dumb questions. I just never had to think alot of this stuff out before.

About logging correct boost, I have a newer AVC-R. (Its still on the DSM, but I can pull it off) Can I use the 4 BAR map sensor to log boost somehow? Can the scale of the sensor be adjusted within one of these logging programs? I mean, if I have a japanese 4 BAR sensor... why would I pay $125 for a japanese 3 BAR map? I understand the ability of having it function both as ecu operated & logging capability. (JDM MAP) But I can mount this little thing anywhere... and just T'in. And leave the USDM MDP alone.

I already have a tandem harness wired to the sensor output, I could easily feed it manifold pressure, and rewire it into the mdp line too. (how it was on the DSM)
This might be more beneficial, as I see me attempting the SD/MAP flash at some point when I get a better grasp of this stuff. But can I use the 4 bar?

Touring B;
Is there a way to log airflow coverted into lb/min? If I can see lb/min I don't need hp/tq calculators. I'll know how parts changes effect where I'm at just from that.
That's all I want to see anyway. How much air am I flowing at what pressure? Do I have enough fuel to support it? What is my A/F ratio? Where is my timing, and am I knocking.

All I need.

 

you can read airflow from the stock MAF as a Hz value. If there is a conversion from Hz to Lb/min then you can run the conversion during or after the log.

You can know everything you've mentioned by logging:
AirFlowHz (look up the 2-byte mod to avoid the 1600 Hz clip)
Load (2-byte again. there is a conversion formula around for conversion to pressure. Or, you've got that 4-bar sensor)
IPW (you can calculate IDC% based on this. The formula is posted here or I can send to you)
WBO2 (your LC-1 of course)
Timing (easy enough)
Knock Sum (Yes, you really only need knock sum)

You can create custom calculations in EvoScan and Mitsulogger based on other logged values. This is helpful for the IDC% and the lb/min you're looking for. I'd be happy to help you set up the formulas if you can track down something for the lb/min.