03 silverado diesel/avital 4103/dball

The problem is NOT tach related if: 1 - You have the unit set for tach sensing and it will take over when originally started with the key 2 - If tach sensing was shut off and it still starts for a moment then dies. Usually a tach issue allows the truck to run for a few minutes and dies OR may just crank and crank for a minute then shut off. This is either an issue with the DBALL learning the code of the immobilizer system OR more likely is the avital is NOT triggering the DBALL when it's about to attempt a remote start. I'm also leaning on this one since everything else is working via the DBALL (locks, etc). What is the LED doing on the DBALL when you try remote starting? Is it lit? Flashing? Solid? Since you have connected W2W, what wire is connected to the DBALL's Blue/White GWR Input (pin 10 of the 10-pin connector)?

         Times 2 with Frank.

Soldering is fun!

I have the dball pin 10 blue/white wire connected to the avital 4 pin harness blue 200mA status output. I checked for connectivity and its a good connection. The dball is flashing green continuously while attempting a remote start. I believe that means the gear is active and normal.

I should also mention when programming the dball, everything went as it should. I connected the 10 pin, (but not the 12 as I have nothing connected to that harness). I held the programming button, then connected the 14 pin. LED turns on orange, I release button and it turns red. Then start the vehicle with key, LED turns green, turn vehicle off and remove key.

Yep that sounds exactly like what it should it do. I'll be honest, I don't use DBALLs anymore due to inconsistent and very frustrating problems with them. I primarily use iDatalink modules. I have installed on many Silverados including an '06 just this weekend and worked perfectly (i know that doesn't help you). But they are very straightforward installs. You have 2 ignition wires, 2 Accessory wires, 1 Starter wire and 2 Power wires. Otherwise, it's the data connection at the OBD II port, pin 2 (violet). And of course ground, brake, parking lights, horn, etc.

When I run the shutdown diagnostics of the remote start, I get error 3, low or no rpm. Doesn't that point to the tach being an issue? I will return this remote start module for another that actually has the tach jumper like described in the install manual. (Easier said then done when ordering on amazon).

If the Passlock is preventing start, the remote starter will give you an RPM error since it's being prevented from starting. The Avital has no way of telling that it's the anti-theft stopping it so it thinks it's lack of RPM. Earlier you mentioned you set the Avital to No Tach Sensing and it still won't start. It's not a tach issue if it won't stay on even with tach sensing off. I don't think it's an issue with the Avital. I've been wrong before but I have installed tons of Avital 4103s and they are good basic starters. I think the problem is with the DBALL honestly.

I hear ya... Just for troubleshooting, if the dball is the problem, shouldn't the remote start work with the key in the ignition? Or would I have to unplug the dball to test that?

This truck uses passlock II which is a resistance-based system via 2 wires. The DBALL and other modules interact with the BCM directly via the data wire. The key itself isn't a chipped key, so therefore inserting the key in the ignition switch will do nothing for testing the remote starter. Only on transponder based systems will that work, but the passlock system is actually built into the ignition switch not the key. Hope that made sense.

Understood. I think I am going to return the dball and purchase a idatalink ads-tb. It's only $35 with free shipping from amazon and it looks like I don't have to install different firmware after I receive it ( is that correct?). Hoping to keep it simple!