View Single Post
      05-02-2019, 08:28 PM   #21
RSL
Captain
647
Rep
779
Posts

Drives: E92 ///M3 (Retired) / 335is
Join Date: Mar 2012
Location: USA

iTrader: (6)

Quote:
Originally Posted by vtl View Post
If its a 2048 limiter then should the shift bog fix make it never occur? Because the I8A0S car I tested it on had the shift bog fix enabled in MHD.

Why do you say it wont be able to be zeroed out on Auto/DCT? Do you mean it'll be jerky or cause problems with the TCU? Auto/DCT already have these throttle correction tables a lot lower than MT. If you have to preserve a non linear throttle on DCT/AT and zero out the throttle correction tables then yes it could indeed be hard to drive smoothly (although AT has a torque converter which dampens things out anyway)

I think an adjustable slider in MHD would probably be the best idea for people who find it a bit too jerky, I found I have adjusted my driving to have more finesse on the throttle.

If anyone associated with N54 development needs the XDF for I8A0S just PM me and ill send it across
Yes, sorry, jerky/too responsive, at least in 1st on DCT. In INA0S, they actually added damping to it for DCT. AT is already low, probably because the converter does suck up a lot, so might be OK, but shifts are a potential consideration. RPM range, rev gradient, crank vs. input shaft speed diff, throttle/request, etc. are all involved. It might make shifts better, worse or no different, really not sure and we may not know until someone tries. It MAY be possible to 0 out the base and add to speed to at least get by most of 1st gear on DCT reasonably, but that may not be safe (any other gear below 30-35mph would be dead weight by comparison).

1st on DCT is already a bit of a party from a stop at 50% of the stock INA0S base values, stock speed corr, 1M torque request (way less than stock 335is) and not a lot of throttle. It will come together, but will take some finessing. If anyone does haul off and just 0 out the base corr on a DCT, PLEASE vid the first drive

No idea on the 2048 fix, that's an MT issue I've paid little attention to. Not sure what conditions the 2D59 tripped on that car, but if it hit a limp mode with it, my experience is that it would be a 2048. I could pop them all day long at PT with too much request and not enough monitor space, that code never showed up without a 2048 or vice versa.

There are PV monitors, but not sure if they are only for cruise control, plausibility or are in play here at all, but it would be simple to verify if it's a 2048 or not by logging. Use a stock request table, stock max diff and A/B monitors or however he was hitting them with ease before, let it trip and see what the log says.

Slider would be a good idea and probably necessary Glad to know I'm not the only one that spends nights going cross-eyed staring at it, nice job!

INA0S DCT tables:
Attached Images
 
Appreciate 1
vtl1494.50