TCC info

[rr]

For reading code it is a matter of following the source (anht_hac.pdf)
and seeing how the instructions interact. What variable is being loaded
and tested against what constant. Then see how the code branches.
The code is what causes the ECM to do things. It reads the sensors and
changes the outputs (timing, egr, div, bpw, . . . ).

Test bench. Slap an ECM down on the bench, hook LEDS up to the
outputs and various 555's, variable resistors and switches to the inputs.
Hang a scanner on it, power it up and you can pretend it's a car.

There is one in the members projects on the web site. Real handy
to both test code changes and discover how GM code operates.

BobR.


Barry C. Forrest wrote:

> rr wrote:
> >
> > It is a matter of going through the code and figuring
> > out what it does. When it doesn't make sense I fire up
> > the test bench. This lets me watch what it is doing.
>
> I here all this talk about "test benches" and read code but I' just a
> bit too new to this to get the idea.
>
> I've been extracting BIN's with a pocket programmer and checking them
> out in Turbo cat.
> I did a few changes to my PROM on my F-body and it has been working so
> at least I get the basic of Prog 101.
> What's next? How do I read code and us a test bench?
>
> The only test bench I have is my ride.
>
> thanks
>
> Barry C. Forrest
> ----------------------------------------------------------------------------

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org