Forscan datalog of an AWD spin

[4DRHTRD]

This is the 4x4 module, what I see is a quick peak in FWD ABS sensors and then you see it catch. I originally thought it would be good to replicate the front ABS sensors to the rear but now that I think about it that quick peak probably sets off the nannies. I'm now thinking that for a awd launch controller replicating rear ABS to front would stop the nannies along with forcing the car into AWD at 50/50.

Take a look and see what you guys think.

 

[breeves002]

I still don't understand why it wouldn't be easier to disable the abs computer completely for launch?


Sent from my iPhone using Tapatalk 2

 

[4DRHTRD]

I still don't understand why it wouldn't be easier to disable the abs computer completely for launch?


Sent from my iPhone using Tapatalk 2

Disable it how?
Also the reaction would be to shut off AWD, part of the diagnostics contain making sure that you're getting ABS signals from all 4 wheels.

 

[breeves002]

Ahh so turning it off completely makes it 100% FWD? Have you pulled the fuse to confirm?

That makes sense though. It doesn't know if the front wheels are slipping.

I think it is going to be a lot harder to trick the abs computer than you think. I need to think about this one.

Someone over on tcca managed to defeat the advancetrac completely by flashing a different abs programming.


Sent from my iPhone using Tapatalk 2

 

[4DRHTRD]

I think it might be easier to do than we think based off this thread:
http://www.mazdaspeedforums.org/forum/f434/introducing-canbus-triple-150523/

I'm already talking to him.

 

[breeves002]

I guess my question is this: will the bad computer become confused if the data is replicated exactly? I guess there is only one way to find out...

The best option is to figure out how to reprogram the abs computer. That's easier said than done though.


Sent from my iPhone using Tapatalk 2