I didn't go looking deep into this but from my shallow searching it appears as if people thought the $32B was only slow 160baud. Well I just used the USB Autoprom with the verticle switch "up" for ALDL mode and connected to a 165 ABUN (87 5.0 fed auto w/2.73) at 8192 baud! From the looks of things, the 6E ads file is having no address issues, MAF is MAF, TPS, flags appear to be spot on.
Is this a "new find" or is this completely stock appearing memcal NOT really an ABUN?
I'm going back tonight to run some more tests, just thought I'd post that up incase some people are moving to the #6E code JUST for the faster baud... apparently no difference.

I talked with Mangus awhile back, and $32B and $6E use the same aldl stream format, with the exception of like one bit. I forget exactly, but it was something not used anyway.

So yes, $32B and $6E can use the $6E ads file. And both can do 8192 Baud datastreams.

this question did come up about tunerpro, and that made me take a look at both to verify. I always thought 86-89 would work with high speed data, and in looking around scan tools and so forth, everything usually broke out the scan-ability (if thats a word), to 86-89 then 90-92.

https://www.thirdgen.org/techbb2/sho...hreadid=288471
https://www.thirdgen.org/techbb2/sho...hreadid=276064
https://www.thirdgen.org/techbb2/sho...hreadid=276084
Those are the 3 threads that stuck out in my mind.

$32 wont send at 8192, at least never when I recorded data from it.

$32B, I have tons of 8192 data.