My LCD screen project, boost, WBO2, Knock, etc

[CoopKill]

Ok, so all are aware the mirage cable is not compatible with this unit.

I have tried the null adapter with the cable, and no luck. Due to the gender of the parts available here is what I had to run. Mirage cable to null modem adapter to a gender changer to the box. The mirage cable is a male, and Radio Shack did not have a female/female null adapter. The mirage cable must be wired different than the norm...

It is entirely possible I am just a re__rd...

Will be getting Blacks cable...

[RealMcCoy]

Ok, so all are aware the mirage cable is not compatible with this unit.

I have tried the null adapter with the cable, and no luck. Due to the gender of the parts available here is what I had to run. Mirage cable to null modem adapter to a gender changer to the box. The mirage cable is a male, and Radio Shack did not have a female/female null adapter. The mirage cable must be wired different than the norm...

It is entirely possible I am just a re__rd...

Will be getting Blacks cable...

I'm betting the correct null modem adapter will fix it... I ordered extra the last time, I have a spare. You're only a day or so away from me by mail. I could send you one.

Or you could try a real computer store...

[CoopKill]

I will be in Willsonville tomorrow, so I'll hit Fry's. Not confident that a different one will be the cure, but will try...

[Simace]

Has anyone tried to datalog using EvoScan (v2.8 here)?

Reason I ask is that I recently got my FTDI USB-Serial cable and gave it a go. I setup the device (Datalog=passthru, etc) as per the Gen 2 manual along with adding the two new ID's to EvoScan (08 and 09). Connection is successful, but the logs look as follows;



Here's the EvoScan setup;


It appears only WB02 and Boost are properly logged, the rest is missing. If I take EvoScan as it's setup and use the Tantrix 1.3U cable directly to the ODBII port, it logs correctly (minus the WB02 and Boost obviously.)

Forgot to mention that I'm running version 2.14 on the LCD/Boost Controller.

[RealMcCoy]

Got nothing on that one.... I've been using 2.8 to log mine without issue.

[Jimvr4]

Has anyone tried to datalog using EvoScan (v2.8 here)?

Reason I ask is that I recently got my FTDI USB-Serial cable and gave it a go. I setup the device (Datalog=passthru, etc) as per the Gen 2 manual along with adding the two new ID's to EvoScan (08 and 09). Connection is successful

Here's the EvoScan setup;


It appears only WB02 and Boost are properly logged, the rest is missing. If I take EvoScan as it's setup and use the Tantrix 1.3U cable directly to the ODBII port, it logs correctly (minus the WB02 and Boost obviously.)

Forgot to mention that I'm running version 2.14 on the LCD/Boost Controller.

Since connection is successful this may not apply but I believe the protocol should be Mitsubishi MUT III, not MMC.

[RealMcCoy]

Since connection is successful this may not apply but I believe the protocol should be Mitsubishi MUT III, not MMC.

I this case that's not necessary... Mine works just fine just as his is configured

[Simace]

RealMcCoy, you think you can post up your XML file for EvoScan? I'd like to compare yours with what I have...maybe it's corrupted on my end? Do you think maybe the '99 ECU is the reason?

FWIW: later this evening, I'll try the MUTIII vs MMC and post what I get.

[RealMcCoy]

RealMcCoy, you think you can post up your XML file for EvoScan? I'd like to compare yours with what I have...maybe it's corrupted on my end? Do you think maybe the '99 ECU is the reason?

FWIW: later this evening, I'll try the MUTIII vs MMC and post what I get.

I'd be happy to, but I just got the program last week... I'm not that familiar. I don't know where the XML is, or how to extract it. I'll have to educate myself on the proccess.

[Simace]

Got it working. It was the ODBII connection - intermittent, wasn't seated properly. Now it's time to tune

FWIW: the xml files for EvoScan exist either within the Application directory (under Program Files) OR within your [My] Documents, depending on how you installed it.

3rd Gear Pull


VirtualDyno


Notes on what I see;
- Looks good, but maybe a bit too rich....maybe...
- Between 4500-5000 I should add 1% dutycycle...
- Between 5000-5500 I should add 2.5% dutycycle...
- Between 5500-6000 I should add .5% dutycycle...
- Would really be nice to have 2byte working