Cant find bin for 16196397 BLZX anywhere! going crazy plz help!!

okay so ive been searching for days and i cant seem to find what i need anywhere. first things first i have 95 olds cutlass supreme 3.1 l82 with PCM # 16196397 BLZX. ive been having various driveability issues and i want to scan my codes and find out what is going on. i bought an aldl cable on ebay and im using tunerpro rt. as far as i can find out in the forums i should be using 1fa XDF and P66 V6 ADX files but i cant find the Bin anywhere. not even sure if i have the first two correct. i have gotten the cable to connect to the car and im able to pull data but it seems glitchy and has errors frequently. im still pretty lost as to how to use TPRT to view my codes and diagnose my problems. i (think) i was able to datalog a test trip but i have no idea on how to view the XDL file. im just about ready to go ballistic and start blowing things up. somebody please help me get this straightened out. thanks

You will need to unplug your ABS computer to get good datalogs. You need to use the P66 ADX, and P66 XDF. You will need to get a program that can write the flash, I personally use Tunercats Winflash, but now EEhack has branched out and will supposedly also flash the P66, however I've not used it yet.

http://www.gearhead-efi.com/Fuel-Inj...rmation-P66-V6

This is the ADX, XDF, and every bin file that we have collected so far for the P66 computer. I also have been working on a 2-bar MAP sensor compatible conversion that will allow turbocharging but without Robert or Charles development on this has fallen to just me and I'm a crap programmer.

flashhack should write that ecm for you, and you shouldn't need to touch the abs as far as i know. its bus connection logic is supposed to be really solid. just make sure you keep ignition power on if something goes wrong and you should be able to retry an infinite number of times, and try a read first.

i would appreciate you doing some testing with it as i don't have a lot of P66 users yet but i expect

kur4o has a hacked up version of eehack for the p66 that should work really well for datalogging. it's in a pretty recent thread around here but can't seem to find it right now

tunerpro's macro connection thing isn't really great at connecting to a busy ALDL bus and that's why sometimes you have to unplug a few modules to keep things quiet

eventually i plan to have flashhack pipe data to tunerpro, that way you'll get ultra reliable connections for any of the 8192 baud stuff, but can use all the tunerpro data tracing and graphing. it's a work in progress

Quote:

---

Originally Posted by steveo

flashhack should write that ecm for you, and you shouldn't need to touch the abs as far as i know. its bus connection logic is supposed to be really solid. just make sure you keep ignition power on if something goes wrong and you should be able to retry an infinite number of times, and try a read first.

i would appreciate you doing some testing with it as i don't have a lot of P66 users yet but i expect

kur4o has a hacked up version of eehack for the p66 that should work really well for datalogging. it's in a pretty recent thread around here but can't seem to find it right now

tunerpro's macro connection thing isn't really great at connecting to a busy ALDL bus and that's why sometimes you have to unplug a few modules to keep things quiet

eventually i plan to have flashhack pipe data to tunerpro, that way you'll get ultra reliable connections for any of the 8192 baud stuff, but can use all the tunerpro data tracing and graphing. it's a work in progress

---

I modified the .ADX to have a easier time dealing with the chatter from the P66. It involves a few changes to various macros (mostly repeating the Mode 8 command with 50 ms pauses in-between) and I believe I corrected one or more packet size values. Threw in my idea of a dashboard etc... and I was interested in adding the Mode 1 Message 3 commands but I don't understand where some of the .ads/.ds/.xdf hex values are supposed to go in the .ADX so I haven't attempted. However, I am able to read, log, and send various Mode 4 commands with the engine running successfully. I haven't had to disconnect ANY modules to get consistent data and I noticed that in TunerPro, the data connection speed must be around 4 to 7 hz. otherwise the data is wonky. Just unplug the serial connection, re-plug, press connect again and make sure the data connection speed is above 4-5ish hz. TunerPro is so stable that while recording a log, I can turn the engine off, and restart and TunerPro will continue to record even while the engine isn't running. Just make sure that the data connection speed is above that 5hz or so speed so the data stays accurate, if not, stop log, re-plug, verify data connection speed, continue recording. Data Tracing also works for me very well to watch the PCM operate in the VE table, and spark advance tables. If anyone would like to examine my .ADX, I have attached it to this post.