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.
It runs. But I've got what is probably some coolant sensor issues, car won't run when it hits operating temp, etc.... no codes. I need to do some logging if possible.
I'm having data logging issues. I know it's an $88 mask because I opened it up, disabled VATS, AIR, and burned the chip myself. I've tried 2 ECM's.
I've tried four different $88 .adx files that I got from various sites including gearhead efi, forum posts here, etc.
Im logging with an Autoprom. It connects, I show ~20 Hz data, good connection, but the data is garbage.
I scoped the serial data line terminal on the ALDL and it's definitely pushing data:
It sure seems like the adx files have all the wrong offsets because none of the 4 I've tried work.
Any help or suggestions appreciated.
GD
Last edited by GeneralDisorder; 08-17-2017 at 11:59 PM.
Looks like a packet of chatter. The $88 mask sends chatter, need to tell the ECM to stop them by requesting data packets. Need the timing between receiving a chatter packet and the sending of a data packet request to be done properly.
So you think it may be a timing issue with the $88 adx file setup? Maybe the adx isnt resonding fast enough? This is an AZTY bin which Ive read is the most up to date.....Is it possible a different $88 bin would have different timing?
I'll get another scope reading today and zoom out to get the time between these chatter packets.
I'm also going to scope it after I "connect" with the Autoprom and see if there's any change. I figured this was some kind of handshake being put out by the ECM and awaiting a response from the scan tool.
So you think it may be a timing issue with the $88 adx file setup? Maybe the adx isnt resonding fast enough? This is an AZTY bin which Ive read is the most up to date.....Is it possible a different $88 bin would have different timing?
I'll get another scope reading today and zoom out to get the time between these chatter packets.
I'm also going to scope it after I "connect" with the Autoprom and see if there's any change. I figured this was some kind of handshake being put out by the ECM and awaiting a response from the scan tool.
Thanks!
GD
I really don't know if it is an ADX issue or not. I've never needed to log using TunerPro. AZTY is the latest 3.1l auto BIN.
Does anyone know if there is an older BIN I could use that is known to work with the $88 adx's? I could flash to that for diagnostics and then put the AZTY back on after I have run my logs.
Took more readings. The "chatter" packets are 200ms apart and always identical:
Once I get connected I get more frequent and more varied packets. TunerPro says connected and data coming in at 20Hz. I'm assuming this means communication is established. That's about right I'm seeing packets every 50ms or so. Here's one of the data stream packets:
But the data stream is garbage. So that pretty much means the $88 adx files are not a match for the AZTY BIN.
Does anyone know of a hac for the AZTY BIN or offsets for the datastream?
I'm going to try an older 3.1 Auto BIN and see if I can get any of the $88 adx files to work with one of those.
GD
Last edited by GeneralDisorder; 08-19-2017 at 03:06 PM.
> TunerPro says connected and data coming in at 20Hz.
Can't be, the fastest data packet rate is about 11 Hz. The ECM is likely sending some other type of packet. As there are several different ones that can be requested.
The data packet length is 63 bytes of data along with the header and checksum at the end.
If you are using a Moates autoprom, call them with the car, computer, and wifi handy. I was having the same problem, and while he couldn't figure out how to datalog and emulate, he was able to get the autoprom to log in pass-through mode.
He took a bunch of debug logs and said they will look into why it won't read the $88.
Thanks for the confirmation that it's not just me. I was able to get the AZTY prom, disable the VATS, and burn a chip to get the car started. And old fashioned troubleshooting found a bad CTS so it stays running now. I believe it needs injectors but they are not so easy to ohm when hot like the V8 TPI setup, and without any BLM data I'm limited in what I can easily (reasonably) do for the guy.
08-17-2017, 11:14 PM
