The first thing you do is get the harness connected to the engine and get it running. Then, and only then do you start debugging the system.
Keep it simple.... do one task at a time and get it done completely before you go on to the next task.
If you start burning chips, etc., you're going to get lost. The VSS, if it's needed by the donor system will fire a CODE 24 when you get the engine running. It will run without it. You'll need to get comfortable with the ALDL reporting system to recover codes.
Here's what that code means:
[ QUOTE ]
Trouble Code 24 indicates that the Vehicle Speed Sensor (VSS) is not sending the expected (based on other system parameters like LV8, TPS, RPM etc.) signal to the ECM.
Code 24 will be set if vehicle speed equals zero 0 mph when:
* VSS indicates less than 2mph.
* MAP is less than 30 kPa.
* Engine speed is between 2200 and 4400 RPM
* TPS is less than 2%.
* Not in Park or Neutral
* No Code 21, 22, 33, or 34.
* All conditions met for 3 seconds
If the code was logged when the vehicle was in motion, the following should be checked:
1) VSS circuit open, shorted to ground, shorted together
2) Faulty Connections
3) Defective VSS
4) Defective ECM
5) A faulty or mis-adjusted Park/Neutral (P/N) switch can result in false Code 24.
[/ QUOTE ]
Once you get the engine up and running you can start running code checks and see what more is needed.
Burning chips can be done by you, with the right equipment. You'll need a laptop, some chips,
cables, software and an EPROM burner. If you've got the laptop, there rest can be obtained for about the cost of having the chips burned... and you'll likely have three or four iterations before you end up with a great (not just good) fuel/RPM block map.
Download the
MegaSquirt software, or the
WINALDA software and get that laptop warmed up.