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

 

Well, if that guy's right and it's a violation of the OBD 2 standards, perhaps you should take it up with mitsu to see if they could fix that and some of the other ecu bugs while they're at it,like the "ASC service needed bug."

 

I'd rather not let mitsu know that I'm interfacing with the ECU.. I'll let tuning shops like TTP and AMS that have relationships with Mitsu explain that.

 

If you're just datalogging and not flashing then there's not any risk of them voiding your warranty, but maybe you're right and telling AMS or someone who has a relationship with mitsubishi ight be a better way to go.

 

What bug is that? The only time I have seen an ASC Service light is:
1. When the traction control kicks in and asc is fully on
2. When the combination of parts / tuning causes the ecu to see load values outside of the range defined in the rom.

#1 is not a bug, it is how the system alerts you to low traction condition
#2 is not a bug, it is a check condition put into the ecu and it must be addressed (table values modified) when tuning.

Is there something else you are referring too that i missed? If so pm me a thread so I can have a look.

To the OP, this is nothing new, product manufacturers (esp in the computer security world) often do not follow RFC to the letter and third parties that make products that interface with the manufacturers device (anti spam / mail firewall boxes) are often quick to point out the flaws in the manufacturers interpretation of RFC's....

While it's good to have the information, the chances the the manufacturer will make any changes are slim and none.

 

THIS IS NOT A THREAD ABOUT ASC...EVERYONE LET THAT GO PLEASE.

This was simply to notify the EVO X community that CANbus 6x data samples may not work due to a bug found by Dynoscan service.

Can anyone verify this doesn't wotk with PCMscan?