ECU CANbus - bug found

[tsitalon1]

Hey guys,

I contacted Dynoscan support to find out why the 6x Can logging (much faster sampling rate) wasn't working with my Evo. Here is the email back after they examined all logs.

Keep in mind that "EVO3" is the normal sampling rate.

Hi,

The EVO3 file shows a sample rate of about 94mS per data sample. With 5 data parameters being monitored, each sensor value is updated about every 468mS. The data in the file looks fine and the scan tool is working properly.

The comlog shows that the vehicle does not support CAN 6x mode. The vehicle is not sending all the messages back as it should, which is a violation of the OBD II standards. In short, your vehicle ECU has a CAN 6x mode bug.

Many vehicle have software bugs, just like any other piece of software. We've seen many vehicle with different bugs over the years. Just keep the CAN 6x option turned off with this vehicle and it will work fine.

Dave

--------------------------------------
Auterra Support
__________________
Alex

[Stellar24]

So this is an issue on Mitsubishi's end? That sucks that you cant get a faster sample rate than .5 seconds per channel. :mad:

[tsitalon1]

So this is an issue on Mitsubishi's end? That sucks that you cant get a faster sample rate than .5 seconds per channel. :mad:

Well, if I log less sensor's at a time I can. Also I am hoping that mitsu uses some non-standard communication that maybe the ECUSCAN/FLASH guys can figure out.

Are the PCMscan guys getting better than 94ms samples?

[Stellar24]

Also, does anyone know if Evoscan is available or will work for the Evo X? It might work a little better since it is Mitsubishi specific.

[TTP Engineering]

There is no evoscan available for Evo X at this time.