Old post but here you go - the data. Disengagement on cruise is part of the stock setup so no issue there, it just continues. Not sure on the engagement on deaccel - will need to do some logging there.
I don't believe that the "increased traction" mod does a thing or at least folks have on clue what this does. It's just speculation and butt dyno. I did a bunch of logging of the Haldex activity and got no variation no matter which of the three settings I used (standard/increased traction/reduced noises) on a course I have but I digress...
Per United, the stock setup can transfer a max of 50% of the available torque. Stock on my Sportwagen was 199 lb-ft so theoretically 50% can be transferred for ~100 lb-ft. The tune is supposed to remove that limit and allow 50% of whatever power you are making so for me on the IS38/Unitronic, that's around 325 per Uni's dyno sheet so I should now be able to get 50% of that for 162 lb-ft. I was getting a max of roughly 30% of the available before the tune.
The Graph shows a standing launch pre- and post-tune logging within the brake control unit (3) the awd channel "nM". This is clearly not the actual torque but some proxy/measurement that the ECU uses and matches roughly what United's graph on their site looks like so figured this was the way to do it. I didn't take the post-tune run up to the same speed as the pre-tune run so that's why the post-tune line drops off out on the right. OBDEleven sucks big-time for logging and doesn't always use the same interval for data points - I did the best I could normalizing them and some of the slight differences in the 2 graphs' trend matching each other are most likely related to that but it's close enough.
Datazap file:
https://datazap.me/.../pre-vs-post-haldex-tune-launch...
View attachment 212266