remote starter 2007 nissan quest

I am planning out the install of a remote starter only (no alarm) in my 2007 Nissan Quest. I plan to use a Python 4203P ("Responder One") and an XpressKit DBALL. So far everything is clear to me from the instruction manuals and my online research, but I have one question about the DBALL: The install guide for the DBALL for my car firmware says that to perform the "Feature Programming" I need to " Press the lock/arm or unlock/disarm button on aftermarket transmitter to change the option of the selected feature". However, the 4203 system is a one button remote starter. It has no lock/unlock button, only the one button to remote start. How do I change the options in the feature menu of the DBALL without a lock, arm, unlock or disarm button? Thank you

I haven't tried that combination, but I have an idea that might work. Are you doing the installation wire-to-wire or using the data-to-data cable? Regardless of which installation type you choose, try to get the DBALL at least temporarily in wire-to-wire mode. Then, take the lock and unlock wires from the DBALL, leave them long, and strip the ends. Go into the programming menu for the module, and when it asks you to press Lock or Unlock, instead just tap the associated wire to chassis ground in the car. After that, if you're using data-to-data, you'll want to get the module back into that mode and see if hopefully the settings stayed.

Thank you for your response. This worked. I was able to get the DBALL to recognize the unlock wire as long as I do this after resetting it, but before the Python 4203P sends any commands to it. I got everything installed and it works great, except for 2 annoyances: 1. I am unable to get any tach signal from the DBALL via D2D. The only way to make the starter work is in "virtual tach" mode. 2. The parking lights do not come on while the car is running on the remote starter. - The Python 4203P is able to get the DBALL to turn the parking lights on, because it flashes them once before starting the car, and it also will flash them 5 times if I use the "panic" feature on the Python 4203P remote. Any ideas?

FYI, in answer to part of my own question, in case someone else stumbles on this. I contacted XpressKit's tech support and received this reply: "The tach signal needs to be hardwired to the DB-ALL, the D2D communication for tach is not available on the 4203P." Connecting the DBALL tach out to the Python 4203P's tach in fixed the tach signal issue perfectly. I do wish they would document these things in the installation guides. I also wonder if this is why many professional installers always use W2W on everything, because there are so many little undocumented items that don't work on D2D. I am still looking for an answer to the parking lights issue.

In my experience the parking light flash while In remote start option is turned off in the menu by default hope it helps

Apparently the DB-ALL can only "flash" the parking lights, not turn them on steady. So it works when the Python 4203P tells it to flash them, but not to turn them on. XpressKit tech support suggested I put the Python 4203P into "flashing" mode for the parking lights, or connect the parking light output from the Python 4203P directly to the car. I am just leaving it as is. The system works well now, especially with the tach signal from the DBALL working. If anyone wants hints or direction on installing a remote starter in a 2007 Nissan Quest let me know. I did not make a "pictoral guide", but I collected a lot of documentation and made a lot of notes.