2004 jeep grand cherokee xk09 issues

Hoping someone can help me out here. I installed a Viper 5901 Remote Start/Alarm in a 2004 Jeep Grand Cherokee using a XK09 flashed with the JDL firmware. The problem I'm having, is that while everything else seems to work fine, it will not remote start. When the remote start engages, the key idiot light in the dash flashes, the Jeep turns over and starts and immediately turns off. I have reset and reprogrammed the XK09 several times and it is still acting the same. Additionally, if I start the Jeep with the key, and then try to do a remote start take over to pull the key out, the starter grinds, as if the remote start didn't know that the Jeep was running in the first place.
I have the XK09 hooked up to the Viper using the D2D plug. When programming the remote start with it hooked up this way, should I have the Engine Sensing set to Tach or Virtual Tach? With it hooked up either way, the remote start won't let you program the tach, i.e. the led never flashes when you hold down the valet switch to program it.

If anybody has any insight as to what I'm missing here, I'd greatly appreciate it.

Thanks

I'm totally new to this, but maybe you have your starter output and ignition output reversed:

When you hit the start button the starter output gives current to the ignition circuit and the ignition output sends current to the starter. When the alarm senses that the engine is running, it shuts off the starter output and kills the ignition.

When you go to do the takeover, the ignition output sends current to your starter...

Dunno, did that make sense?

It seems to be a transponder bypass issue. If you put the key in the ignition (not turned on, just inserted into the ignition) and try the remote start, does it work ok? If it does, you may have a wiring issue with the XK09, If it still doesn't start properly, you may have another issue. But since the security light flashes on the dash during remote start, I'm pretty sure its an issue with the XK09. Also, check the LED on the XK09. If its not flashing its not working properly

blanx218 wrote:

---

It seems to be a transponder bypass issue. If you put the key in the ignition (not turned on, just inserted into the ignition) and try the remote start, does it work ok? If it does, you may have a wiring issue with the XK09, If it still doesn't start properly, you may have another issue. But since the security light flashes on the dash during remote start, I'm pretty sure its an issue with the XK09. Also, check the LED on the XK09. If its not flashing its not working properly

---

Based on everything I know, I agree with you. The LED on the XK09 does display everything that it should, it goes through the programming phase correctly, and the LED displays all the proper codes to lead me to believe that it should be working right, but it just does not. I did try remote starting it with the key in the cylinder, and it did not work that way either. Unfortunately for me, I bought the XK09 from the company I used to work for, that has gone out of business (Ultimate Electronics), so I can't return it and get a new one. Also, I'm doing the install at my house, and I don't have an XK Loader to re-flash it. I reset the XK09 again, and I'm leaving it unplugged all night tonight and I'm going to see if it will work when I try again tomorrow morning. If not, I'm going to take it to work with me (I work at Best Buy now), and re-flash it there, and then try again. If that doesn't work, I'll either see if we carry the XK09 at BBY and buy another one, or try a different module. Unfortunately, I have never had luck with these new modules. They seem super convenient, but I grew up doing installs in the days of the good old reliable 556U, and you NEVER had issues with those.......Oh memories. Thanks for the help.

kynetx wrote:

---

I'm totally new to this, but maybe you have your starter output and ignition output reversed:

When you hit the start button the starter output gives current to the ignition circuit and the ignition output sends current to the starter. When the alarm senses that the engine is running, it shuts off the starter output and kills the ignition.

When you go to do the takeover, the ignition output sends current to your starter...

Dunno, did that make sense?

---

Not a bad thought, I know what you are getting at, but I double checked these, and I do have the right connections.

Some updates for anybody who might have any ideas. I ran a real tach wire, which fixed my issues with the starter grinding if I tried to do a remote start take over.
As for my XK09 issues, I ran a brand new dedicated power and ground off of the 20 Pin harness on the XK09, and also dedicated the ground on the D2D connection instead of grounding it through the RS. I also re-soldered my connections at the immobilizer. This worked..... for a while. It started and ran normally through about 5 RS cycles, with no issues, until I buttoned everything back up and tried it again, only to have it start for a second and then turn right off flashing the Key light in the dash. I reset the module, AGAIN and it worked once, but when I tried a second time, it shut right off. Any ideas?

I'm going to re-flash the module tonight at work, and see if that helps, but I'm about out of ideas at this point. Everything else works perfectly.

what kind of time are you waiting in between RS cycles. I've seen Chrysler vehicles think your trying to program a key to the car if you activate then deactivate the RS too quickly. try it then let it sit for about 5 mins before trying it again and see what happens.

just a little personal experience, the XK09s SUCK!!! I always use idatalink ads-al-ca modules for Jeeps....FLAWLESS every time

blanx218 wrote:

---

what kind of time are you waiting in between RS cycles. I've seen Chrysler vehicles think your trying to program a key to the car if you activate then deactivate the RS too quickly. try it then let it sit for about 5 mins before trying it again and see what happens.

just a little personal experience, the XK09s SUCK!!! I always use idatalink ads-al-ca modules for Jeeps....FLAWLESS every time

---

That's an interesting thought. I hadn't considered that. I reflashed the module, and re-installed it, and so far (fingers crossed), it has been working. But the sentry key light still flashes on in the dash when it remote starts, and then comes on for a few seconds when you put the key in and hit the brake. I think I've reached the point where I'm going to just pick up either a PKCH1, and use it, or a 556U and get a key programmed. (if I go this route, I'll buy an uncut/unprogramed key from ebay, and program it but not cut it, that way I don't have a usable key in the vehicle). Depends on whichever is cheaper for me. I just kind of lost my faith in the XK09, even if it is working currently. But everything else the XK09 supports is awesome (parking lights, factory alarm integration, factory keyfobs control Viper alarm, memory seats, door triggers, etc etc), so I'll still leave it in for all of that.

So for anybody still interested, or anybody who might run into this in the future....I got it fixed. Long story short, the XK09 sucks. At least for the immobilizer. I re-flashed it, and it worked, for about a week, then stopped working again. I finally gave up, disconnected the XK09 from the immobilizer in the Jeep altogether, and bought a 556u at work. I ordered an uncut/unprogrammed sentry key on ebay for 25 bucks, and programmed the chip in this key using the instructions for the PKCH1 from Xpresskit.com. This way, the 556 bypasses my imobilizer in the Jeep perfectly, with 100% consistency (versus the 40% reliability of the XK09), and I don't have an actual cut working key in the Jeep in case somebody tries to steal it.
I will however say, that the XK09 is still very handy for all of it's other features. (Brake shutdown, parking lights, factory alarm AND factory keyfob integration, driver memory functions, etc).