When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
DFI and ECMDiscuss all aspects of DFI (Digital Fuel Injection), ECMs (Electronic Control Module), scanners, and diagnostic equipment. Fine tune your Third Gen computer system for top performance.
I'm using 165 ECM, Tunerpro RT, ALDL from BoostedNW, and Ostrich 2.0 to tune my SC, 350 motor.
Been working with an expert on the Corvette site, data logging and adjusting the bin.
It appears the data log freezes up from time to time, causing the engine to go into limp mode, then recovers.
At a certain point, this anomaly, will kill the engine.
The person I am working with proposed the possibility that the baud rate is switching back to 160 from 8192.
Has anyone had similar issues with the 165 ECM?
Could the Ostrich 2.0 have anything to do with this behavior? I changed the 3V battery so no potential of losing the bin.
I've ordered a rebuild 165 ECM but looking for any insight if its the ECM or something else. .
Note the discontinuities in the time and engine running time signals along with the IAC and rpm behavior just following the time periods (up to 10 seconds) of lost data . Spark advance relative to tdc, diagnostic switch in aldl position and desired idle speed also suggest that the ecm is temporarily reverting to 160 baud ALDL mode and then recovering again. This should not happen, but apparently is happening. Strange.
The ALDL idle speed and the ALDL spark advance adder have already been adjusted in subsequent bins in order to mitigate the issue if it should reoccur.
One possibility is that the user is disconnecting and reconnecting via TunerPro while recording data, or an issue with the instrumentation (usb/cable/laptop/tunerpro/adx) rather than the vehicle (aldl wiring/ecm/ostrich/bin).
$6E bins can force Mode 0 after loss of comm for only 5 seconds, so this may be what is happening here. I will try increasing the timer. Noteworthy: It is set to 30 seconds in $32 and $32B bins--big difference.
;---------------------------------------------
; If no Comm >= 5 Sec Force mode 0
; (TM'R VAL AT C70B)
;---------------------------------------------
CB23: LCB23 LDAA L0166 ; SERIAL DATA TIME TO FORCE MD 0
CB26: INCA
CB27: STAA L0166 ; NEW Ser DATA TIME VAL
CB2A: CMPA LC70B ; 5 SEC,
CB2D: BLS LCB32 ; BR TIME GT 5 SEC
; ... else
