viper 5901 remote start, alarm conflict

Guys, I know there were many of those who brought up the remote starting question. I have non-obvious ones', so here there are:

1) Remote Start feature works only with disarmed vehicle.
When I try to RS on armed mode, it revs up and shutdowns immediately, and the alarm triggers right away. Says "trunk open" (also have a tilt sensor on that zone)

2) After RS'ing the vehicle I can lock the doors and "arm" it,
but in reality no sensors do work. But LCD still says "Armed"
So, the vehicle disarms but locks on RS.

3) With RS and engine running the ignition key can be inserted,
but can not be moved at all. Only when I disarm the vehicle once again, I can takeover the ignition/engine run with key, and turn off RS, vehicle will still operate normally. Problem is double-disarming.

Would you be so kind to tell me how these issues may be fixed?
Any help will be highly appreciated!

1) Does it try to r-start a second or third time by itself? Check the shut down diagnostic code. What if you disconnect whatever you've connected to the dark blue trunk pin wire to test? What if you disconnect tilt temporarily? Is it possible that the 5901 doesn't disarm OEM security at r-start?

2) That's normal. It bypasses all sensors during remote start and re-engages them 10 seconds after r-start shuts down. Trunk, door and hood pinswitches stay active though.

3) Is this a new Dodge key node? What make model year and what interface modules?

-------------
Prepare your future. It wasn't the lack of stones that killed the stone age.

Thanks for reply Big Dog!

1) No, it does not RS later on, just kicks in alarm stating that the trunk is open. Very strange though. Can't say for sure if the problem lays in tilt sensor.

2) I didn't know that. Wish I could somehow engage them on RS as well.

3) Yep, Mercedes style FOBIK, which is RKE + ignition in one.
But I have also a usual "classic" one, still same thing.
Would be much unhappy to see it won't moving at all, even though twice disarming is still seems odd.

The vehicle is Chrysler 2008 300 with DLPKKICH3 (CHWFR+RFLCHGM)

1) What if you disconnect whatever you've connected to the dark blue trunk pin wire to test? What if you disconnect tilt temporarily? Is it possible that the 5901 doesn't disarm OEM security at r-start? Are you connected D2D? Connect wire to wire and see if problem goes away.

2) It could lead to false alerts while the engine is running. What sensors do you want to work?

3) Damn I'm good! That was my first guess! I've never heard of a need for double disarming. Are you cutting the transmission release (yellow/blue)? Don't.   I suggest you download the latest install guide by following this link: DLPKKICH3 The install guide was re-written in the past week.

-------------
Prepare your future. It wasn't the lack of stones that killed the stone age.

Thanks for help man, everything works fine now - even though it was adjusted by tech who installed the system. Now, perhaps I will engage sensors even on RS later on.

by chance - do you know what changes the tech made? i'm running into the same problem -

i can't r/s with the 5901 armed - it'll flash the trunk error
if the system is disarmed, the r/s works fine - relocks the car, but the pager thinks the car is disarmed

Actually the R/S on my car worked around 2 month then went down.
It looks like that Chrysler 300 2008 and up models conflict with R/S at some point, maybe it's just Viper, don't know for sure.

The basics behind trunk flashing is that it was connected on that wire, as I remind, my tech reconnected the wire to another zone.

chiefwigms wrote:

---

by chance - do you know what changes the tech made? i'm running into the same problem -

i can't r/s with the 5901 armed - it'll flash the trunk error
if the system is disarmed, the r/s works fine - relocks the car, but the pager thinks the car is disarmed

---

Have you figured out what's causing the problem? I am running into the same issue and have not found any solution yet.

I found that that my 508D proximity sensor was causing problem. Not sure why but I am going to take a look this weekend.