(((Mitsubishi MUT-II/MUT-III Datalogger)))

[Dj4play]

Originally Posted by maddux317

I see where you are coming from on this. With just over 1,000 97-99 VR-4's that were produced, there can't be all that many of them still running the roads today and even less that are being modded. Still though, there are those of us that would like to be able to reprogram our 97-99 ECU's. This is more than likely going to have to be an open source kind of thing if it is pursued. I know I am definitely going to delve deeper into this subject....... Maybe the EVO guys can provide us with a little help.

i have the source code for the evo and can flash tune them. they are not 100% the same as the 3s however and will require work, and almost any amount of work for this platform is a waste of time for an actual buisness because the amount of profit that is made is not enough to keep a legit buisness' doors open. This fact is sad but true. I hate to break it down like that, but its very sad. 85% of the 3s cars we recieve through our doors need to be scrapped not built.

[tfw a-ok]

Originally Posted by Dj4play

i have the source code for the evo and can flash tune them. they are not 100% the same as the 3s however and will require work, and almost any amount of work for this platform is a waste of time for an actual buisness because the amount of profit that is made is not enough to keep a legit buisness' doors open. This fact is sad but true. I hate to break it down like that, but its very sad. 85% of the 3s cars we recieve through our doors need to be scrapped not built.

I'm sure there are some people struggling to maintain these cars but there is still a legitimate force out there of viable serviceable cars. It's unfortunate that you only see the worst of them.

[maddux317]

Originally Posted by Dj4play

i have the source code for the evo and can flash tune them. they are not 100% the same as the 3s however and will require work, and almost any amount of work for this platform is a waste of time for an actual buisness because the amount of profit that is made is not enough to keep a legit buisness' doors open. This fact is sad but true. I hate to break it down like that, but its very sad. 85% of the 3s cars we recieve through our doors need to be scrapped not built.

I agree with you on the business end, these cars are getting older and more rare every day. This is going to have to be something that is done by an individual who is not looking for profit. I'm very interested in the idea myself, but it is going to take a lot of research as I have never messed with anything like this before...

[linchpinjoe]

Originally Posted by Dj4play

i have the source code for the evo and can flash tune them. they are not 100% the same as the 3s however and will require work, and almost any amount of work for this platform is a waste of time for an actual buisness because the amount of profit that is made is not enough to keep a legit buisness' doors open. This fact is sad but true. I hate to break it down like that, but its very sad. 85% of the 3s cars we recieve through our doors need to be scrapped not built.

lovely

[simace]

Alright, now I'm concerned on the accuracy of EvoScan - specifically, its' ability to pull err codes from ECU.

This past Saturday, I gutted both front/rear pre-cats on my '99. On Monday, I got the dreded CEL.

Using EvoScan (latest ver), I get the following DTCs;
-Barometric Pressure Sensor
-Speed Sensor

Moreover, everytime I click the button to get the DTCs, it returns different sensors (but almost always the Barometric Pressure Sensor). Because of this, I decided to use the ole'Palm datalogger.

Using the old palm data logger (which has ODBII OBDGauge) and got;
-P04xxxx the one associated with the non-existing pre-cat (what I would expect after gutting them)

Retreiving DTCs with the palm repeatedly always kept coming back with the exact same error.

Seems that EvoScan is way off.....or is it?

[tfw a-ok]

Originally Posted by simace

Alright, now I'm concerned on the accuracy of EvoScan - specifically, its' ability to pull err codes from ECU.

This past Saturday, I gutted both front/rear pre-cats on my '99. On Monday, I got the dreded CEL.

Using EvoScan (latest ver), I get the following DTCs;
-Barometric Pressure Sensor
-Speed Sensor

Moreover, everytime I click the button to get the DTCs, it returns different sensors (but almost always the Barometric Pressure Sensor). Because of this, I decided to use the ole'Palm datalogger.

Using the old palm data logger (which has ODBII OBDGauge) and got;
-P04xxxx the one associated with the non-existing pre-cat (what I would expect after gutting them)

Retreiving DTCs with the palm repeatedly always kept coming back with the exact same error.

Seems that EvoScan is way off.....or is it?

This is not a shrink wrap product........ as far as I know, trouble code diagnostics is still under development and is expected in the next release.

Please read the site so you know what you've purchased.

[simace]

Originally Posted by tfw a-ok

This is not a shrink wrap product........ as far as I know, trouble code diagnostics is still under development and is expected in the next release.

Please read the site so you know what you've purchased.

Link?

[tfw a-ok]

Originally Posted by simace

Link?

http://www.limitless.co.nz/

[ver fer]

Has anyone with a Innovate LC-1 tested it to see if it work with this logger?

[Agent|99VR4]

Yes I've heard the Check engine codes diagnostics are being worked on for the next release. Thats when Im buying!