Joined: 06 May 2007
|Posted: Mon Jul 25, 2011 2:07 pm Post subject:
|I'm going to comment on one video at a time, so if I say something responding to o9ne video, then change something later on, just ask for clarification, if something doesn't make sense. Great idea making videos BTW.
|Glenno wrote: |
|If you can view these videos I made maybe you can better see what Iím trying to do. Sorry they are torturous!
Ok, the little blip heard at 0:47 is the sound that I was speaking about. That confirms connection. There are other sounds, similar to or the same as that one that tells you if the upload was successful. I think that was the upload sound that was heard there.
You don't have an XDF loaded, so emulating will do nothing for you. You need the XDF loaded to Tuner Pro. This is basically a road map of what is in the bin file, and shown in terms we can understand and manipulate. The XDF will populate "All these things that are empty" at 0:27.
You don't have a bin file selected, so again Emulating really won't do anything for you, and anything that you have uploaded would not be a bin file that the PCM will understand.
To load a Bin file you need to click on either "file>Open" or the yellow open folder to the very left side of the tool bar. This will open a menu that will allow you to browse to where you have saved any bin files. Initially it should open to some bins that are loaded with Tuner Pro RT, I don't recall if there are any bin files that will work for you in there.
The ALDL Not connected, has to do more with the ALDL Xtreme cable. This will require an ADS (Tuner Pro V4 uses an ADS, Tuner Pro V5 uses an ADX, there is a way to import an ADS to an ADX, but that won't apply to you right now). To set this up, you need to go Tools>ALDL/Datalogging>Set-up. Using the F4 key will also get you there. Once you open this window you will be able to set the com port for the cable (there is a handy little test button to verify that it is the correct port) and the ADS file to be used. The ADS file is again, basically a road map to decipher the data stream that is coming from the PCM, and displayed in terms that humans can understand.
Also check to make sure your ZIF socket and is seated right into the DIP socket in the adapter and that the ribbon cable is seated into the ZIF socket correctly. It looks like it is not installed correctly in the video.
The ribbon cable is oriented correctly. The Red stripe is at the correct end.
Yes, at 0:45 you mentioned the "V2 dot dot dot," that is exactly what I was refering to. This verifies that the Ostrich is recognized by TPRT, this is good, we can leave that part and work on the other things that are missing.
The single flash tells me it is trying to read something from the Ostrich, but it's likely not something that is use-able by the PCM.
The bin is loaded to Tuner Pro in this video. One step closer.
Try uploading the bin to the Ostrich again. I have found sometimes, that even if I get a good tone, the upload sometimes isn't complete, a second press seems to resolve that.
The PCM is reading the bin from the Ostrich, and is recognized as a valid program.
The fuel pump running for an extended period is from settings in the bin that instructs it to hold the pump on that long.
Going back to the ALDL, that has to do with there being no ALDL Extreme cable connected to the ALDL port, and no ADS loaded to Tuner Pro.
The reason the CEL didn't flash that second time was because you didn't leave the key off long enough. IIRC the key has to be off for about 8 to 10 seconds for the PCM to fully power down and go through the start sequence again that will show the flash, then solid CEL.
This also basically verifies that the ribbin cable and ZIF socket are seated properly, must just be the optics on the camera playing tricks.
You're getting there, one step at a time.
I'm not entirely sure about this one.
I have had this problem when I have moved a file, and then try to open from the "recent bins/xdf/ADX" drop down menus. So if you moved the file between loading it to Tuner Pro and trying that recent bins selection that would definitely cause it.
Just to make sure, you downloaded the file to your PC and then loaded it to Tuner Pro RT from your PC, correct?
To sum it all up, we now know that the PCM appears to be wired correctly, due to the way it reacts, being CEL and fuel pump prime, it's reading the bin file from the Ostrich, so you are getting close now.
Next thing to do is to get the ADS loaded to Tuner Pro, so that you can connect to the ALDL and get some data from the PCM.
On Moates.net there look to be a couple $0D datastream definitions, both that I can see quickly look to be in .zip folders, which as long as you have an extractor, like Winzip (IIRC a free download if you don't), then down load one or both, and load one to Tuner Pro, set the com port for the cable, make sure when you test the cable for function via Tuner Pro, that the ALDL cable is not connected to the car at all. Once this is all set up you can then again, go back to a key on state, watch for that CEL flash, press connect on Tuner Pro RT, and you should get a connected message.
Once you get the connected message you can open the dash, which is found in the tool bar and is a large "D." The "V" is for a "values" list, that has more things than what you will see in the dash, "F" is for "flags," meaning that it will show the simple on/off values that are in the data stream such as closed loop, or TCC control, etc. The "M" is for "monitors," we won't bother with that until you are comfortable with the rest of the program first lol.
You also need to get an XDF loaded so that you can see the values in the bin file. $0D.xdf that is at moates.net should be a good one to start with.