VAT removed from 12587603 bin, still no start from 5.3 engine

[twad1206]

I used Tunerpro to edit 12587603 bin file. Disabled VATS and uploaded the bin to my ECM (Hardware# 12589162). Bin 12587603 was not my original operating system for my ECM. I attempted to start my engine and the engine would not start and run. I then installed my ECM inside a friends 2004 silverado. The truck's security light came on and went off as the engine started and ran perfectly. I removed my ECM from my friends truck and installed on my engine again. My engine still does not start. I am using the original harness and engine from my donor 2005 silverado truck. When the ECM is powered on with "key" power, I do not get power to the fuel pump from the ECM. I can manually supply power to the fuel pump and still no start for the engine. The engine acts as if VATS is "enabled". I checked the VATS settings with Tunerpro once again and observe VATS to be disabled. I have extra ground cables attached to the engine.

Any ideas as to what I am doing wrong to get the engine to start?

The bin file I uploaded to my ECM is attached to this thread.

[ralmo94]

Universal Patcher says that one of the options for the VATS or as its labeled in UP VTD, is out of range, set at 2 on a range of 0 or 1.18443

Also the checksums are modded from stock but ok18444

[ralmo94]

I have attached the same file with the only mod from what you posted as putting said parameter in range, set at no vats

[ralmo94]

Also, is there any specific reason you changed OS? Do you have a copy of the original bin? If it was just for supported XDF, I'll bet UP would support it.

I was going to see what all you changed in the bin, but on the 2004 bin page, there are several different 12587603 bins

[twad1206]

I attempted to use Universal Patcher and found the program difficult to navigate. I used TunerPro and found the program easy to use, especially since all I needed was to disable VATS. I downloaded the 7603 bin file and a compatible XDF file.

[twad1206]

I changed OS because I could not find a compatible XDF for it. UP seems above my knowledge level. I may take another look and see if I can use the program. However, does anyone see a problem with the file I uploaded? Is VATS disabled in the BIN file and if it is, then I should be looking at some other reason for my engine not starting.

[twad1206]

I will down load and try the file you provided.
I have five more ECM's. All with different hardware numbers and OS.
If the current ECM does not respond with the bin you provided I will go to one of the five available and try using UP on its original OS.

[twad1206]

One other thing. Why would my ECM work perfectly in my friends 2004 Silverado and not on my engine?
Same engine, trans, etc. My donor vehicle was 2005 silverado.

[ralmo94]

Are you aware that there are internal differences between DBW and DBC pcms?
I don't really know why, different hardware number could be, I don't really know.
Also you never said what file you used whether dbc or dbw, or what engine you have. The more information you can provide, the more people will be able to help you withoust asking for more information. You are always better to provide more info than not enough, there is no such thing as TMI. That's my honest opinion

[kur4o]

One other thing. Why would my ECM work perfectly in my friends 2004 Silverado and not on my engine?
Same engine, trans, etc. My donor vehicle was 2005 silverado.

2004 OS is not compatible with 2005+ TAC module and pedal. Maybe that is your issue. Or some wiring issue too.

[twad1206]

I have DRW, 5.3engine, 4l60e trans

[ralmo94]

4x4 or 2wd, what original OS, can you post original file?

[twad1206]

2004 vs 2005 may be the issue.

Wiring: used original engine harness and fuse box.
Connected engine harness to port C2 of fuse box. Connected positive power cable to battery and other end to the fuse box, as original from truck. Negative cable to battery and to engine block.
Port C1, wire A9 of fuse box has constant power, Port C3, wire F1 has 12 v power.

[twad1206]

2wd vehicle . Original bin attached

[ralmo94]

Have you tried the 05 Chevy 1500 4x4 os 12592618.bin file from the 2005 section? It shows as all stock in universal patcher. I understand UP looking intimidating, but if you learn to use the search function it can be easy to navigate. It can also be used to create an XDF for tunerpro

[ralmo94]

A quick google search produced an XDF from pcmhacking.net
Here is a link to it
https://pcmhacking.net/forums/download/file.php?id=28812&sid=5f84877083f82c9916ad2fdcc7d53f7b
It was posted aug of this year, with no reports of anyone using it, but it may be helpful to compare with UP for sanity checks
Hope that helps

[ric]

hi i am working on a 1993 c1500

[ralmo94]

hi i am working on a 1993 c1500

I seen your other post,
Have you disabled VATs?
Is the file on your p59 a match for engine and transmission?
Have to be careful if p59 was drive by wire, DBW pcm's from what I have read do not have an IAC driver, and if you flash a DBC bin to one it can brick it.

Best to use the file in your pcm to avoid bricking, safest anyway. You can do segment swaps if you need different engine or transmission.
Here is a video I made of how to disable vats with universal patcher.
Universal Patcher is available here
http://www.gearhead-efi.com/Fuel-Injection/showthread.php?9616-New-LS1-Tuning-Tool-Universal-Patcher

https://youtu.be/mfVzxEDEXF4

[ric]

THANKS I have changed what was on the video and will try to start it today

[Pulse_GTO]

The file you posted is not from a 2005, but from a 2006 truck. It has OS 12587811, I'm attaching an XDF for it, just remember to copy the GM-P01-P59-checksum-plugin.dll file to your "Plugins" folder in the Tunerpro directory.

It's a good thing that you are going drive by wire as the 12589162 PCM does not have the IAC driver installed and would not be able to work in a drive by cable application. There is a write up on how o add the driver, but with how cheap these PCMs are I would rather pick up one that already has it.

[In-Tech]

Sorry, off topic a bit,
Didn't I read somewhere that 12587811 has some anomaly that puts it in power reduction mode and kills the throttle? I don't remember the details but would like to play with it on the bench. I could be wrong on which OS it was, but was a DBW p59 '06 or '07 I think.