You use the same Tactrix cable to log the ECU values, just like Mitsulogger. You don't have to use the LM-1s serial connection for anything other than the O2. I haven't done this personally because I log with EvoScan, but I know a few others use LogWorks and love it. It just takes a little time to set up all of the values to log from the ECU.

 

OK, a little about LogWorks:

There are a few logging programs out there. The most commonly used ones are EvoScan, Mitsulogger, and LogWorks. All three of them log the requests and variables from the ECU, just like your DSMLink did.

Since you have and Innovate LM-1, though, you can use LogWorks. I have an LC-1 wideband and their SSi4, but I am assuming that the LM-1 is similar. There should be a serial output from the LM-1 to go to your laptop. That way your LM-1 wideband readings would be in your log with all of your other values, like knock sum, RPM, etc.

Since you are coming from DSMLink, I recommend LogWorks. It is the most similar to DSMLink, in the fact that your realtime logs are presented in graphical format and you review your logs this way. The LogWorks app is pretty nice.

As far as a couple of your other questions:

Log knock sum. This is the same knocksum that you had in DSMLink. Except DSMLink also let you choose knock retard, which was the amount of timing being pulled due to the knock sum. Basically, it's 1* of timing for each 3 knock counts...the same as with your DSMLink and DSM. So, a knock sum of 9 would be a knock retard value of 3 that you are used to with DSMLink.

About your lb/min logging question...you can search for a thread that I did on this. I forgot the title and don't have the link. I made some caculations to get you close based on your MAF Hz, intake temp, and baro. No one that I know of at this time has found the true mass airflow loggable variable. I think Bez may have, but I never saw this logged yet. I would just wait until someone finds the right variable so that you can log it.


Eric

 

you may have missed the point, you have to download the package from innovate, it includes logworks and the openport 1.3 that allows data from the ecu to be logged with your lm1 data. so you have the ecuflash cable attached to the car from which you get some data(up to ten inputs with the current LW2) and the serial cable from your lm-1. You can choose which data from openport that you wish, from about twenty points.
its a lot easier to do it than explain it.

one last point, boost pressure is interesting but not necessary, 2 byte load is all you need in that direction.

http://www.innovatemotorsports.com/products/tactrix.php

openport comes in the logworks download

 

I have the logworks 2.0 CD. I have logworks loaded. If there is an add on then yes, I missed that part. I will have to go back and do some more research.

You guys have been seriously helpful. I really appreciate it. I know noone likes going thru the motions for the 10 millionth time for "another newb". But its helping me alot.

I went thru Tephra's CEL patch thread today. I know, no big deal, but I have never patched anything or even seen XML. It took me a while to figure it all out but I got the stuff to populate in ECU Flash and set it up using the rom he provided. (I've yet to flash it to the car, I want to get the maps closer to where they are now and start from there.)

I brought up all the fuel tables from my current tune, (timing and fuel tables are the same low/high octane )

And from the "stock" patched rom tephra provides. (timing, fuel, hi/lo) To compare. At first these tables seemed very foreign to me. But from driving the car with a close eye on the WB lately, I'm seeing whats in the table on the gauge. Well, pretty close. And I think in my mind from comparing and some logs I could really pull some of the problem area's out of it. (Its stupid rich, bad transitions under load, RICH LEAN RICH LEAN RICH in adjacent cells following the load/rpm path) Most of the fuel tune makes me scratch my head, but basically from the look of it, they fattened it up and and added tons of timing. Little else. Looks pretty much like a shelf tune.

With the CEL light knock warning I think I can tweak it by a** without depending on alot of logging. Which is good because my laptop sucks. It overheats and shuts down randomly.

Some good info in some of these posts. Keep it coming. I'm starting to get a better grasp on this stuff.

 

openport 1.3 may be on your computer already then. just open it BEFORE you click logworks. hit the start log, nothing will happen, that's ok, ...open logworks , start realtime log and voila!

 

It wasn't. I had 2.01, not 2.04. I hit the update check button and it told me it was "up to date". Even tho it wasn't. Removed it, went to Innovates site and dowloaded 2.04. Now it comes up under the tab. My laptop may be sh**y but its only USB. Can I use a keyspan serial to USB adapter for the WB output to the laptop?

Thanks for the heads up on the openport thing.

I'm off tomorrow so I'm going to play a bit more with various logging / tuning to try and get better at this.

After the struggle I had trying to get the CEL flash patch working... I don't know if I'm proficient enough to do an actual rom patch to get 2 byte load etc. It took me quite a few tries to get the simple xml addition to ecu flash to work. (I've NEVER even seen XML before, so please don't laugh at me too much)

I'm just a car geek. Anything I know computer wise is simply because I had to learn it for my car habit. So this stuff is hard for me.

I wanna learn tho. After trudging my way thru it today, I want to go the rest of the way. (trying to learn enough to run the map setup Bez put out eventually.)

 

The 2-byte load mod is very easy...much easier than doing the CEL patch.

There is a specific thread for your ROM, 96940011. The address for the MUT table is in there. Just make sure you add that to your 96940011.xml file. Then all you have to do is add the 899a and 899b in place of the first two variables in your MUT table. Then just log requests 00 and 01. Go through that thread and it should explain it all....let us know if you have any questions.

As far as XML, just edit the files with Notepad or Wordpad. Don't let it scare you....just think of it as a simple text file.


Eric

 

I used XML notepad. (Which I downloaded)
It came up in the "table" view, with the clicky folders.
Add element, parameter, etc. Con-fu**ing-fusing I tell you! I guess there's an easier way to do it then? It took me a while but I got it to work.

 

I opened the openport 1.3 thing in logworks today. Set what I wanted to log, clicked log and it wanted a serial port it said. I'm assuming I have to plug the cable for the WB in as well if I want to log at all then? (I know, why wouldn't you want the wb) I just, tried it instead of mitsulogger kinda on the fly.

I loaded the cars current tune into the CEL patched rom today too. Set my immobilizer, CEL settings, and flashed it to the car. It f**king worked! I held it at part throttle on the highway in 5th gear up hill. I knew it would knock there if it was going to at all. It did! 6 counts. (I have the light set for 3 knock sum) or 1* of ignition retard. (thanks to the informative post I got here) My lady was manning the laptop watching the log and was making sure it went off. It works good! (I have it set for 1000ms) So its just a quick flash per knock sum of 3. It flashed twice in rapid succession. And I let up.

I have a feeling if I would have held it there it would have kept knocking... until it melted. As there is no low octane map. :gay:

I'm going to scale down the timing and fueling in direct comparison to the current flash. And load it into the low octane tables so it can pull as needed to save itself. Unless you think it would be better for me to start from stock maps.
?

Personally I would have went the other way. Leaned it out and only added a little timing. Probably ended up with the same power. And 5 more mpg. And embers not flying out the tail pipe burning holes in my paint.

I'm just too green to get ballsy enough to do it yet.

I gotta get this logworks running. I think I'll go out and screw with it now.

 

You could always get a cheap mail in flash from Jestr or TTP and then tune yourself from there. You'd know it would be safe then.

 

DONT use an XML editor - just use a straight text editor.

and XML editor will be tempted to change stuff that doesn't NEED changing. Text editor gives you much more control+safety

Cheers
Dave

 

"I opened the openport 1.3 thing in logworks today. Set what I wanted to log, clicked log and it wanted a serial port it said. I'm assuming I have to plug the cable for the WB in as well if I want to log at all then? (I know, why wouldn't you want the wb) I just, tried it instead of mitsulogger kinda on the fly."

yup, you need the lm-1 serial cable attached to get logworks to fire up. and you will need to open logworks to get openport to log.

 

Speaking of safety. The log I did make showed the car knocking and timing NOT being pulled... I noticed this a couple times as I drove tonight too. I'd get a triple flash on the cel light. Which in my case means 9 counts or higher. Not good.
I was lugging it hard in 4th & 5th from low rpm tho.

I think I have a boost leak too. Not at idle/air leak kind. But at so much boost it seems like its bleeding out. A/F is in the 9's where it was in the 11's prior. Sounds more hissy, and not as fast. Gauge reads the same. But that means nothing.

I'm going to make sure I didn't miss anything from the previous flash that was on the car. I triple checked it. But who knows. I say boost leak.

Thanks again tephra. That patch is giving me a constant heads up I otherwise wouldn't have had. When I get some extra cash I will donate since you did the hard work I am benefitting from. What program do you recommend for XML editing? (I downloaded XML notepad) And it did seem overly complicated. I had to paste each line into a table from your add on text. It wouldn't let me cut and paste it all at once. Of course, I could just be an idiot.

 

start -> run -> notepad

 

For the XML files, just use notepad or wordpad. They should already be part of your Windows.

As far as timing being pulled due to you knock, I can almost guarantee that timing indeed was being pulled. If you look at your load and RPM at the moment you were knocking, take that load and RPM and look at your timing map. It should be getting pulled 1* for every 3 knock counts.

The only way to know for sure is to log 2-byte load and RPM along with knock and check your maps.