Syvecs Forums

I've used Enable A on the S8 before, generic 0-5v input.

I used a 10ms validation time so the ecu can kill engine prior to the cartek doing it's full ground disconnect at 500ms

log all the sevsrc parameters and it will tell what reduction is active.

Again, no idea how their coding works for the box, but that should identify why any torque reductions are happening

without knowing what the slave inputs are used for, they'd mean nothing to me.

As stated multiple times, log the reasons for the torque reductions..

ie.

first you said upshifts are harsh, and then downshifts ?

For most part for downshifts, it'll either not open the throttle enough, or open it too much. Start somewhere and work one direction only to see how it feels.

Does logging look like the blips are starting at a correct time ?

I never said gear cut.

I stated you need to, log the reasons for the torque reductions.

Yeh the upshifts are fine, maybe a bit agressive but fine. I dont think there is any cut actually happening for the upshifts? Gaz at GR showed me one of his logs and he gets signal back to request a blip so iv now got to figure out why im not getting this, it could be a CAL issue or it could be the...

there are some fuel reductions and ign retards around what look like upshifts. But you aren't logging the reason for these reductions. Just that there are reductions. No idea what's happening around the shifts though or what is instigating them You'd assume there should be some sort of marker that i...

blip is assigned ? but cut not ?

the paddles should initiate these things yes, well normally for a sequential etc.

Haven't a clue what order of events etc are needed for the DSG, especially as it could also have a fully auto mode too I assume ? So it will still shift, without the user actually requesting anything.

What are your blips and DBW target etc doing during the shift ?

Is there a blip request ? is it active ? Does DBW target change to reflect any request ?