HALDEX can support

[phoenix3d]

Hi Andrey and the Guys..

Best of the season to you all.

Was wondering about the HALDEX (4motion) control systems from VAG, and if or when possible support could be looked at?

There are 5 Generations of Controllers
Gen 1 uses a Stepper
Gen 2 and Up uses a more simple Pump and Valve control

We are looking to simply (For now) communicate with the HALDEX Controller attached to the Rear Axle via the CANBUS.

As we have at least 5 Vehicles Waiting eagerly for this. AUDI S3 Quattro in specific. (This will be with the DSG wishlist as well)..

I Will attach a few documents with this message, But details required would basicaly be as follows.

HALDEX Controller requires the following CAN info.
The below list is in the following format.

Controller -> Data required -> HALDEX Controller (bear with me and shout if my explaination sucks)

ECU
-> Engine Speed -> canbus
-> Throttle Position -> canbus

ABS Controller
-> Wheel Speed -> canbus
-> Brake Light Switch -> canbus

PArking Brake Controller
-> Lateral Acceleration -> ABS Controller -> canbus
-> Longitudinal Acceleration -> ABS Controller -> canbus
-> YAW Rate -> ABS Controller -> canbus

Steering Angle Sensor
-> Steering Angle -> canbus

Databus Onboard Diagnostic Controller
<-> Probably Diagnostic Data

So In a nut shell, if all other OEM controller are still in place for now, we would purely require the Engine Speed and Throttle Position Data transmited via CANbus. Just to get it up and Running for now.

Would there be a way of "Mapping the Output for Rear wheel output bias via either Curves or a MAP for the following control modes?

1.) Off Mode = Basically disable the Haldex completely (ie any rpm value of below 400rpm Haldex goes offline)
2.) Locked Mode = Lock Output Bias to specific values in say 10% increments (from 0% - 100%)
3.) Throttle Mode = Output bias mapped on a Curve TPS / Output bias %
4.) Speed Mode = Output bias mapped on a Curve Speed / Output bias %
5.) Boost Mode = Output bias mapped on a Curve Boost(Load) / Output bias %
6.) Passthrough = Unmodified data signals passed directly through to Haldex controller for OEM specification
7.) Brake Signal = Active High Brake signal (0% Output and Pre-chrage pump active)
8.) Handbrake Signal = HALDEX Offline (Burnout Mode)

9.) 3D Map = HALDEX output % mappable on a 3D Map Example: Throttle/Speed/Output%
10.) 3D Map = HALDEX output % mappable on a 3D Map Example: Boost/Speed/Output%

See herewith Info.

as well here is a link to an External controller unit as example..
https://www.haldexcontroller.com/en/products/haldex-controller/haldex-controller-overview
https://www.haldexcontroller.com/en/products/haldex-controller/haldex-controller-manual/itemlist/category/28-haldex-controller
https://www.haldexcontroller.com/en/products/haldex-controller/haldex-controller-manual

Kindest Regards
Phoenix3D

[AndreyB]

https://github.com/rusefi/rusefi/wiki/Lua-Scripting and https://github.com/rusefi/rusefi/tree/master/firmware/controllers/lua/examples are your friends

You need a junior software developer to spend 2 hours to learn Lua syntax and then implement it based on the specs.