viper 4501v + dlpk gm 2004 silverado issu

I'm trying to install the basic Viper 4501V in my 2004 Silverado in order to get remote start abilities. I have a DLPK GM bypass module but it isn't programming. When I install the D2D connector while pressing on the program butting the LED lights up like it should but when I install connector 2 the light goes out and stays off. I got the DLPK to sort of work for a little while (would lock/unlock; however, remote start wouldn't stay on for more than a few seconds) but when I tried to program it again, it's not doing anything. The key FOB is also acting up. The remote start module used to click when I pressed a button but now it doesn't. I have the purple wire on the DLPK GM connected to the OBDII port and the pink wire to the ignition wiring as the .pdf below shows. Is there anything else I need to do? On another forum someone posted those were the only two wires connected other than the D2D and his worked great. http://www.xpresskit.com/DocumentDownload.aspx?documentid=6026&productid=125&firmwareid=1633 Any ideas would be greatly appreciated!

I just noticed that the remote start module will blink constantly when the lock button is pressed then nothing when unlock. The truck will also attempt to remote start if I hit the button but immediately shutdown. It appears the module is working... Just not making the clicking noise it use to when I pressed a key FOB input.

When the truck shuts down is the security light on the dash on or flashing? Have you learned the tach? Viper 4501V, is that correct?

catback wrote: When the truck shuts down is the security light on the dash on or flashing? Have you learned the tach? Viper 4501V, is that correct?

The security light is on. I did go through the virtual tach procedures the first time I programmed the DLPK GM but it didn't act like it worked... I also didn't think to check the security light then. I can't get it to program again to redo the virtual tach or try the manual route. I have the Viper 4105V remote start. I mistyped it earlier.

On connector 2 of the DLPKGM what do you have connected? Data, Ignition, Tach? Virtual tach won't learn the tach if the vehicle shuts off before the Viper shuts it off. The viper will start and stop the vehicle 3 times to learn the tach, then and only then has it learned the virtual tach. But considering how easy it is to hook up a real tach with the DLPKGM, it's better to use a real tach - it's more reliable which is great for cold climates that get snow and ice. The vehicle is shutting off because of the factory immobilizer, the security light is the tell-tale of this. Make sure your connections are correct and that connector 2 is not backwards/upside-down. During programming has it ever done different at step 4? and does or has it ever done step 6-11 properly as indicated in the instructions? Verifying D2D communication, unlock/lock, tach (must connect and learn tach), and parking light flash all work as they should? Where did you buy the DLPKGM? new or used? Things is try: Connect Viper to DLPKGM in W2W mode. I know your reluctant but this rules out D2D miscommunication problems. If it still doesn't work in W2W mode after reprogramming and checking all connections then the fault is with the DLPKGM in that it's not bypassing the Passkey system or learning the bypass. I ask some of the above questions because a few of these "no computer requiRED / ready to install" units are a one-time install deal where they will only learn a vehicle once.

I have the purple wire going to pin 2 of the OBDII and the pink wire connected to the ignition spliced in with the GM-12 T harness. I've been told there's a white wire coming from the back of the instrument cluster that's super easy to tie into for the Tach so I had planned on doing that once the lock/unlock started working again. I bought the DLPK GM new off of Amazon but I suppose it could have been a returned item. I may look into other bypass options and see if I can find one from a company that will preprogram my truck into it before they ship it. I'll try the W2W mode soon to see what that does.

catback wrote: During programming has it ever done different at step 4? and does or has it ever done step 6-11 properly as indicated in the instructions?

I forgot to address this. The first time I tried to program the DLPK GM all the steps worked correctly (although I now realize I didn't do the virtual tach learning process correctly so that's likely why it would run roughly 25 seconds then turn itself off). Now when I try to do the programming steps again, once I get to step 4 and plug in connector 2, the LED goes out. Pressing the Lock button as noted in step 5 doesn't give any indication visually or audible (remote start module used to click) and performing step 6 does not cause the LED to flash rapidly like it says it should in step 7.

lethl_ss wrote: I've been told there's a white wire coming from the back of the instrument cluster that's super easy to tie into for the Tach so I had planned on doing that once the lock/unlock started working again. I'll try the W2W mode soon to see what that does.

There's a tach wire on connector 2 of the DLPKGM tie that into the tach wire of the 4105v, it's even super easier that way. Yes, W2W is definitely worth a try.

lethl_ss wrote: when I try to do the programming steps again, once I get to step 4 and plug in connector 2, the LED goes out. Pressing the Lock button as noted in step 5 doesn't give any indication visually or audible (remote start module used to click) and performing step 6 does not cause the LED to flash rapidly like it says it should in step 7.

Likely, behavior of already being programmed. Give W2W a try, at the very least make the (-) while running (status) connection to the 4105v's blue or blue/white (status, 2nd status respectively) and test the remote start. See it works that way.

catback wrote: There's a tach wire on connector 2 of the DLPKGM tie that into the tach wire of the 4105v, it's even super easier that way.

Well I was able to get the DLPK programmed again. I had to leave in connector 2 the whole time then the rest of the procedures worked great. The truck will now lock and unlock perfectly again. I tied the tach wire from the speedometer to connector 2 (PURPLE / white) on the DLPK but that caused my trucks rpm gauge to fluctuate ~400 rpms in a pulsating manner. I set the remote start programming to accept Tach via Menu 2 table 1 option 4 but the truck immediately shutdown after start up. Moving the Menu 2 table 1 to option 2 (Voltage), it would run for roughly 25 seconds then turn off. Moving the menu to Virtual Tach caused it to run for 9 seconds and turn off. Cutting the tach wire caused the speedometer RPM to go back to normal but trying to program the virtual tach only gives 9 seconds before it shuts off and the parking lights never come on. The antitheft light does not illuminate in the cabin. If I move menu 2 table 1 back to the voltage option, it'll run for roughly 25 seconds again but again the parking lights never turn on.

The remote start shutdown diagnostic shows 3 flashes which means low/no RPM detected. It does this with or without the tach wire connected.