Jon,
Seems like we need a Lab view interface to the PCM. Just Tap into the PCMs
harness, and watch the bouncing lines... you could generate trending data
to correlate with the trucks "state" to determine whats up! Since all we're
really after (for basic mods) is crank sensor, Injector pulse width, rev
limit and speed limit it shouldnt be too hard to either build a
microprocessor that "takes over" in these areas... It could "reject"
anomalous commands and let the stock PCM do its thing (alright its starting
to sound like a lot of coding would be required...) reflashing seems too
"proprietary" but after seeing what JET is doing I get the feeling its not
that hard to do better...
.02
BKB
snip" You could probably run the custom computer
in tandem with the PCM, with the custom computer intercepting all signals
to and from the PCM. Anything that hasn't been implemented by the custom
unit could be "passed through" so the PCM won't generate an error code
for a sensor it doesn't see... One problem with this method is the OBD-II
tests. The PCM will sometimes purposely run the engine lean or rich to
test the O2 sensors, so if the PCM sprays extra fuel and the engine
doesn't go rich, it'll probably cry "foul".
This archive was generated by hypermail 2b29 : Fri Jun 20 2003 - 12:12:43 EDT