Originally posted by alex_96GL:
I understand that aftermarket deals mostly w/ the data sections, but I wonder how they debug the actual code at Ford. In Windows kernel for example one can connect through serial port and debug from a remote machine, so your debugee machine sits and does literally nothing untill you press F10. But that's not possible w/ the engine running, so they must have an emulator of some kind... Last time I thought about it, this seemed to be the most interesting field because once you've got an emulator you can actually run the code in the debugger and see exactly what it's doing and when. But even this is not easy to approach, because from what I know Ford code is no longer 8086 assembly...



Test bench. You can run LED's as the injectors and another for the crank trigger to watch spark pulses and see what you are changing as you change them. That's the DIY way...

I know Tuner Pro has their software along with Moates' hardware that can emulate GM ECU's right now and they're working on the "big 3" platforms (Tuner Pro used to be GMECMEdit until they decided to go multi-platform). It's not going to be long now...

Originally posted by DemonSVT:
Originally posted by morbid:
hehe maybe that guy could figure out the throttle hang code and get rid of it.


You can turn that off "so-to-speak" in the code. I've done it.



What does TwEECer call those fields? Tuner Pro has DFCO (Deceleration Fuel Cut Off) and IAC steps vs Throttle position table (in GM OBD-I anyway). How about a screen shot of TwEECer in action. I'm just more curious than anything...


http://www.bnmotorsports.com "And I will strike down upon thee with great vengeance and furious anger those who attempt to poison and destroy my CEG brothers. And you will know I am the Moderator when I lay my vengeance upon you."