I kinda screwed up when I patched the B14 and accidentally turned off part of a routine. I'm not sure what it did. I'll redo it with the routine turned back on.
Can you test something for me btw? Add these to your XDF (both constants & you may already have the first)-
E065 - Closed Loop Speed Trigger, size is byte, conversion is 2*X (just like a speed limiter)
E066 - Closed Loop Speed Additive, size is byte, conversion is just X
and to Flags/Switches add-
E036 - Closed Loop Speed Trigger Enable, bit 5
Open whatever bin your working with, set the E036 flag, and set the speed trigger to something low like 5kph, and the additive to something small like 1 or 2, and see what happens.
Here's how it works-
The speed trigger is straight forward, above that value and it stays in closed loop. The enable/disable flag turns this function on/off (off by default for the FWD SR ECU). The 'additive' is weird, but I think its really a 'disable above a certain speed' function, but its hard to implement in TP. How it works is it takes the current speed, adds it with the additive value, then if the result is higher than 0xFF it sets it to 0xFF. Whatever the result is is what it compares to the speed trigger. Weird, but I think its intention is to act as a disable function if above a certain speed. I guess you could implement it in TP as
510 - (2*X)
Anywho, let me know what it does.