im thinking the condition where B_brems would interfere is not common at all.. which would be ONLY when doing a No-Lift-Shift above rpm threshold and above pedal threshold while simultaneously braking.
so yes, im sure you could put lots of variables in there, as long as them are not triggerd, and the function would still work under every other condition, but its written to use B_brems.
The PDF you produced is very good, but unless you can dissassemble the code it's quite hard to see where it's gone wrong if it doesn't work. Just working on changing the hex to make it work is a real labour of love! Actually seeing the function/routine in IDApro and seeing where the parts all fit together makes a lot easier..
yeah, dissassembling you own function after altering it, back and forth, as i once did, will help a lot.
i actually attached both assembled and dissasembled original function and pseudo-code to look at, in the PDF, but im not sure everybody noticed these attachments..?
it took me 3-4 days to figure out how to do this from scratch without notes and very little previous knowledge, so im sure people will figure it out.. and hopefully learn something in the process.
ive helped countless of people to implement this to their ecus, but i just havent got the time anymore.. an excel sheet is a good way to do it.. im sure a small Vbasic program could automate everything and sniff out the variables + patch any file.. if someone have the time to spare writing one.. i have some reviced functions coming up, so ill put my time into these instead.
