Emulation Anomalies with AutoProm

[84Elky]

Was able to procure another 7427 PCM this weekend and it seems to have solved the problem. I took it on a 20 min test drive with simultaneous data logging and emulation, 10k data points. It glitched one time at data point 129 and then didn’t do it again. Have driven it several times since - emulating but not data logging and it did not obviously do it those times either.

One glitch is one too many. By any chance, are you using a ZIF socket in the ECM to connect the cable from the AutoProm? If so, Moates does not support that method of connection. It will work, but can testify from experience that strange data can be provided for some but not all logged items, while everything else seems OK. This is due to a less than solid connection of one or more of the pins in the ZIF socket. With a solid connection, all OK but over time can change due to vibration, etc.

[Daveo91]

One glitch is one too many. By any chance, are you using a ZIF socket in the ECM to connect the cable from the AutoProm? If so, Moates does not support that method of connection. It will work, but can testify from experience that strange data can be provided for some but not all logged items, while everything else seems OK. This is due to a less than solid connection of one or more of the pins in the ZIF socket. With a solid connection, all OK but over time can change due to vibration, etc.

Yep, that was one of the first things Moates suggested. I was using the S4 Aries 28 pin (plastic locking lever) - I stopped using it as soon as they suggested I do so, but it didn't help. I have since purchased the much more durable S2 Aries (metal locking lever) and have been using that recently. Moates says that version is suitable for emulation. I was NOT using it, however, when I got that single glitch after I switched PCMs. I agree that one glitch is too many but I have driven it some more since I posted this, including a 13K datapoint log today - exported the log file and filtered for zeros in the RPM column - zero zeros, a good thing. The only thing I really have left to try is to shorten the ribbon cable but I think I'll only do that when/if the problem presents itself again. Thanks for the input!

[84Elky]

Yep, that was one of the first things Moates suggested. I was using the S4 Aries 28 pin (plastic locking lever) - I stopped using it as soon as they suggested I do so, but it didn't help. I have since purchased the much more durable S2 Aries (metal locking lever) and have been using that recently. Moates says that version is suitable for emulation. I was NOT using it, however, when I got that single glitch after I switched PCMs. I agree that one glitch is too many but I have driven it some more since I posted this, including a 13K datapoint log today - exported the log file and filtered for zeros in the RPM column - zero zeros, a good thing. The only thing I really have left to try is to shorten the ribbon cable but I think I'll only do that when/if the problem presents itself again. Thanks for the input!

Tks for update. I too have had cable issues, but replaced with a new one and all OK. Failing cable worked for years and all of a sudden started providing random data. Really weird. Had one pin with intermittent continuity when wiggling cable end while testing. Vice squeeze would not correct.