bump

 

Hey guys. I am trying to learn more about the data logging and using ECU Flash and Evoscan. I was wondering if anyone has run these programs on a mac and if so what programs were nedded if any? I am having trouble running them on my macbook. Thanks in advance for any help.

 

Yep. Mine is still stuck like that but it works now. It reads com port 1 but it's reading off of com port 4.

I thought it was my program too so I loaded it I think a total of 5 times, but that didn't do anything. Not even the guys at limitless had an answer for me.

 

so now your evoscan works, but it still reads com1? ok, so that is out of the question. I'm unsure why evoscan 2.5 is not working for me. No settings have been changed. There are no differences besides the fact this is Vista and not xp.

 

BUMP

 

its similar.. What I'd do is copy an existing working line in the Mitsulogger XML, and update the portions that are different such as requestID and Eval.. Assuming that RequestID 12 is an ECU request, and not one that was repurposed by Evoscan.

Normally I don't do this but...


<Request LogReference="WIDEBAND" RequestID="12" Eval="0.0274*x + 9.0" Unit="wAFR" Logged="y" Response="2"/>


I actually realized the new version of Mitsulogger I'm working on, and the existing version you guys use, have some slight differences since I no longer use the Microsoft Script Control for evaluating the formulas, it was to address the fact that the ms script control has been deprecated and doesn't work in 64 bit versions of Vista.

 

Please forgive my ignorance my man. So basically I can just add the line you posted anywhere in the request.xml file for mitsulogger. Like I said I added that line I posted to my EVOSCAN XML file


Like I mentioned my wideband signal is pinned into my ECU where my rear o2 signal used to be.

Thanks for your help my tuner perfers the mitsulogger especially for setting up injectors

 

Yep thats basically all there is to it. If you want to use the logged data in a more complex formula, then you just have to make sure this item comes before future ones.. But for the most part, just place it in where you want it to show up.. If you want it to be the first thing in your list, put it before the first item..

 

OK so I added that line to the XML and can now select it from the list however, now my wideband entry and egrtemp have the same "12" request ID. Im assuming this cannot be?

 

Like I said, its whatever the ECU requestID is for what it is your trying to do.

But yes, if they both have the same requestID, their both reading the same "information" from the ECU.

If its Evoscan that is repurposing requestID's to use your wideband info, then obviously its an evoscan specific feature.. If your wideband is connected to the and actual ECU input, then its the same for Mitsulogger.

 

Does the new mitsulogger log boost past 25.5psi? I wasted $25 on evoscan that seems to be heavily bugged and gives wacho readings.

 

Its supposed to, if your sensor supports it.. However I found a bug in the zeitronix logger (the formula that calculates boost) that seems to foul up the reading over 25psi..

I've actually decided to dust off Mitsulogger as part of the Unilogger development, and have since updated it to fix some of the issues (not released yet) but the big problem with the current release of mitsulogger was its incompatibility with 64bit versions of Vista, I was using microsofts scripting component to calculate data and they did not bring it over to 64 bit versions of the OS's.

Innovate also had some issues as I had originally taken their engineers advice and used their activeX control to simplify reading the MTS serial data. Unfortunately this also made for a compatibility problem that I wouldn't have had if I had written the communications from scratch. Innovate really needs to provide .NET source code implementation of a way to read the serial stream directly to eliminate compatibility problems every time they update their software (and MTS.DLL)

It had taken some time to build a compatible and code-only evaluation tool to allow realtime calculations of formulas. In the process of doing this, I had stripped out the wideband loggers, so I decided to convert mitsulogger into a Unilogger plugin, and all of the existing wideband loggers will also become plugins. This means the applications share quite a bit of code, which makes things a little easier on development. The goal is that Mitsulogger can run standalone as a logger by itself, but if you plug it into Unilogger, you can also build a much more elaborate logging environment. Mitsulogger itself is getting overhauled to be easier to use (if that was possible) I'm leveraging the really powerful features of .NET objects to allow data to be passed between all of the components much more transparently.

The one thing I worked really hard with Mitsulogger is to make it an application that, if there is a glitch, it doesn't make the application completely unuseable, and I've kept all of the unecessary fluff to a minimum to make debugging easier.

 

^ Sounds good, when is it scheduled for release. I figured that mitsulogger stops w/ the zeitronix after 25.5(25.6psi=0 )so i add whatever figure is calculated from that point

 

when you guys connect, on the event log on the right, does it say ECU ID: 0000

Maybe that's my problem.

Edit: Ok i connected the 2.3beta(on windows XP) to my car and it DOES read ecu id:162C, so it seems the problem with the Vista's 2.5 is it is not reading my ECU correctly. more to dig with.

 

anyone who's been having a problem connecting w/ evoscan lately that has ecuflash version 1.38 ..download the newest version 1.39 and it will connect again. nvrmnd...it connected fine for a day and its not connecting again