Strategies requiring brake status
Posted: Sat Aug 25, 2018 9:57 am
Hi All,
I am in the final stages of documenting all my pin outs, sensors etc and at present have a M880, CDL3, DBW4 and a couple of PDM15's.
I have 1 spare AV input on my M880 and have specced my front and rear brake pressure sensors to go to the CDL3 for logging purposes as it does not make sense from a maintenace / logic point of view to put one of them to the M880 and 1 to the CDL just so I can log the data.
Can anyone suggest a scenario / ECU strategy where it would be benificial for the ECU to know the status of the brakes? I have clutch pressure coming into the ECU which will allow for either pressure or binary input (via a table) into strategies like gear change blip etc but no strategy immediatly comes to mind where visibility of brake status would help - can anyone suggest any that would benifit from brake status and if so I will route front brakes to the ECU and leave rear on the CDL.
Cheers,
Ben
I am in the final stages of documenting all my pin outs, sensors etc and at present have a M880, CDL3, DBW4 and a couple of PDM15's.
I have 1 spare AV input on my M880 and have specced my front and rear brake pressure sensors to go to the CDL3 for logging purposes as it does not make sense from a maintenace / logic point of view to put one of them to the M880 and 1 to the CDL just so I can log the data.
Can anyone suggest a scenario / ECU strategy where it would be benificial for the ECU to know the status of the brakes? I have clutch pressure coming into the ECU which will allow for either pressure or binary input (via a table) into strategies like gear change blip etc but no strategy immediatly comes to mind where visibility of brake status would help - can anyone suggest any that would benifit from brake status and if so I will route front brakes to the ECU and leave rear on the CDL.
Cheers,
Ben