dball/dball2 constant red flashing

I have a 2006 GMC Sierra CCLB w/Diesel I have a Viper 5901 system install and have both an DBALL and DBALL2 which are not syncing with the vehicle. When I program the DBALL via XKLOADER2 it appears that the programming works successfully. When I try to program it to the truck in D2D mode the initiation sequence works (push button, plug d2d wire, orange light, release, red light) The problem is when I turn the key and start the truck the red light stays lit for about 3-5 seconds and then starts flashing at a constant rate. There is no orange or green pattern happening. It's constantly flashing red. When I programmed the DBALL I unchecked everything except the Door Lock/Unlock and OEM Lock/Unlock The interesting thing is that I have not had any problems with this when I first installed and setup the DBALL to work with the system. Everything programmed correctly and synced up correctly. Had been working great for about 18 months... Anyone else have this error code? I've not see anything on the net explaining what this could be. I've double checked my wire connections for the D2D wire into the alarm box and also checked the single data wire that connects to the vehicles databus system and everything seems to be OK. Any thoughts on trashing the DBALLs and going with idatalink...read these are significantly better. thanks! Ben

Triple check your SWC (Data) wire...could be a bad/loose connection, could be a break in the wire, the issue could be on the vehicle end. If it is an issue with the data wire on the vehicle end another, different brand, module alone won't fix things.

I'll take a 3rd check on the data wire from module to vehicle data line. I've never had any issues with obtaining data using a diagnostic code reader or my Tech II, but i'll try using them again since this problem just started as well to see if i have problems accessing the vehicle through the factory wires. Thanks for the thoughts and encouragement...

a continuity check on the SWC wire concluded that it is good. I hooked up my diagnostic device and was able to view engine data, so i'm pretty confident that it is not a bad data/bus wire. Is is possible that my Viper 5704 D2D is messed up? Any way to test with a multimeter the condition of this?

This is one of my typical out of left field comments but:- Is there somewhere else on that vehicle you could pick up the data? Have you used that data wire for anything else? You could be overloading the clock speed or its read ability (with thanks to Kreg).

rodrigue10 wrote: Is is possible that my Viper 5704 D2D is messed up? Any way to test with a multimeter the condition of this?

Disconnect the D2D connection, and power the DBALL directly in W2W mode and try to program the vehicle that way.

X2 with Catback it won't be the Viper, they are independent entities. It's possible but extremely unlikely that you aren't getting 12V+ and ground from the Viper, you can test this easily enough.

Thanks all for the tips and thoughts. I finally got it to work after banging my head against the wall for a couple weeks! Just have to put all my wiring back together nicely again since i pretty much went through all my remote start/security wires again. Per your advise i tried the W2W mode since it was only a few wires to hook up and everything was exposed. I was still getting the same constant red flashing light. I don't have anything attached to the diagnostic port at this time of trying to program, but I have hooked up an EDGE Insight CTS to monitor engine data. Maybe this made things unhappy...but even with it hooked up i didn't have any problems with the DBALL interface working. And didn't see any immediate problems after removing the device. I determined ultimately that there had to be something going on with the vehicle's can/bus system since my remote start still worked without the module, just no doors/alarm disarm. There were no apparent shorts and since i could use my Tech II to do anything diagnostically with the truck i figured a faulty data line was not the likely culprit. After doing some long and hard thinking i realized that i recently flashed my truck's ECM with an EFI Live custom OS. (about 2 months ago) After flashing this custom OS i didn't have any problem's with the dball and remote start doing what they were intended to do, but thought that i would try re-flashing back to my OEM Flash and see what happens. After getting it flashed back to more of an OEM state i proceeded to start the programming procedure...first in W2W mode since i was already setup for it. The module programmed with out any problems almost instantly. It was like magic! Then i decided to give the D2D mode a try so i reprogrammed the module via the web applet and made sure my D2D options were checked. Then i proceeded to program it in D2D mode in the truck and that worked as well... So to sum up if anyone else has a DBALL or DBALL2 that constantly flashes red there is something likely not happy with ECM... Now to talk with my EFI Live vendor to see what their thoughts on the matter are...would like to get my custom OS installed again... Might try to reflash my custom OS again and see if this happens again. Hope this helps anyone else out there in the future! -Ben