86 Camaro 305 8192 baud possible?

reddok · Post by **reddok** » Sun Dec 20, 2009 11:41 am

I'm new to TunerPro and I'm trying to read the data from the 8192 data stream. I can connect fine using the 1227165_160.ads file and read the 160 baud data but that file doesn't support the 8192 baud datastream. I've tried the 1227165_6E.ads file, but it doesn't connect. The ECU appears to switch modes (the lights on my serial adapter flash faster).

There doesn't appear to be an ALDL defination file that supports 8192 baud for the $32 mask. I've read 8192 data with a snap on scanner, so I know it should work. Is it just a matter of making my own .ads file for the 1986 prom?

Post by **robertisaar** » Sun Dec 20, 2009 12:19 pm

more or less, you did describe what is necessary for you to accomplish to read at 8192...

160 is tough to use due to how slow it actually is.

EDIT: an easier way to accimplish what you're trying to do may be to just switch to the 32B or preferably the 6E mask.

reddok · Post by **reddok** » Sun Dec 20, 2009 1:13 pm

So the mask file will affect the ability to read ALDL data? Would I need to use the 6E.xdf with the 1227165_6E.ads file? And would this work with my 86 prom?

Or do I have to put an 87 prom in it to be able to read the 8192 baud data?

Post by **robertisaar** » Sun Dec 20, 2009 1:24 pm

you would need a 87-88 or 89 BIN and then you could read and tune it using the 32B or 6E ADS/ADX and XDFs.

in the DS file for all of these masks, it states that 85 and 86 ECUs can only communicate in 160baud mode. i believe that for 85, but since the 86 is the same ECU through 1989, the only reason i can think of as to why it wouldn't be able to output a 8192 stream is that there is algorithm stating to do so. why GM would do that, i have no clue.

reddok · Post by **reddok** » Sun Dec 20, 2009 1:40 pm

I think its an issue with the .ads file. I can read the 8192 data with a snap on scanner. And the lights on my serial adapter seem to be flashing quite a bit faster when I request 8192 baud. Tuner pro just won't connect.

I'm wondering if just the proper .ads file for a 1986 would do? I could probably log the raw data and figure out what it's sending.

Post by **robertisaar** » Sun Dec 20, 2009 1:49 pm

in the DS file, it says to send a 160baud request, then send a 8192 request to connect at a 8192 rate. but thats for the 87-89 ECUs. it might apply to 86.