So I went to use my Predator for the first time today and couldn't get it to work. It came with r18 on it. First thing I did out of the box was get the DSDownloader and update the Predator with r20. Plug into car - it boots and I see the 6.1L Hemi screen for about 1/2 second and it goes to Performance Tune. Followed the instructions (manual is a bit old?). Got to where I selected the tune (CAI 91 oct.) and it told me it was unable to identify the vehicle and to turn on the key. Turn on key and proceed When it gets to backing up the Original Backup it fails very quickly. Few seconds? Proceed and it makes the second attemp and fails. Says one reason might be there is already a performance tune installed. I've never had anything other than the dealer TSBs... Maybe that's the problem? I need to look for the latest stock tune from Diablo? Thought it might be the calibration thing. Followed the instructions for that and the extra calibration tab didn't showup on the DSDownloader. [Edit] Tried turning the key on before selecting the tune and same result. Ends with "can't tune due to backup" Also forgot to mention it's a '06 Magnum SRT8. Here is what it showed from the "Predator Information" In the mean time I think I'll run out to the car and try turning the key to on after the initial screen and before selecting performance tune... Next I'll come back and hunt around the Diablo site for the "latest" pcm? Hopefully I'll be saved by then.
Yes R20 is only for the the newer vehicles, and seems to have difficulties linking with the 06. If you have an 06 the earlier versions work the best. I believe I am running R17 and have no reason to update it....R16, R17 and R18 are all the revisions I would suggest....
8r18 is not going to help likely, something else is going on here. Go to options/troubleshooting/show calibration ID and see if it can read the calid and also see if it will read the VIN from the same menu. Thanks Mike
good thread .. thanks for the information curtis .. i know i have had a problem with this personally ..
I haven't... Spent all day at Talon's place. Had to drive up there and back stock tuned LOL. Just got back. Will try Mike's suggestion (see if that works) in the next half hour or so. By the way, the AFE is really quiet compared to the Mopar. Most of the time you can't hear it at all. It's all exhaust now (I got the Mopar cat backs). From the cabin I think the Mopar CAI is just as loud as the exhaust. Even at WOT it's loud. Never noticed this since I got the CAI first and then the cat back. The Mopar CAI makes that brrrraaaAAAAAck sound :scare:. Off to try the Predator...
Hi Mike, Tried that. It sees to work fine retrieved CALID and VIN (and I verfied the VIN is indeed correct). Can I post that stuff? I pm'd you anyway. thanks, Dave
It's the same Mike. I tried again after reading the calid and vin and still no joy. Tried unplugging the predator, key cycles, starting the car, then starting over and no effect. It tries to read the Original Backup, displays the hour glass, the nav unit shuts off completely (I had it "off" with the button but it displays the clock even when off) then back on and then the Predator displays "Original Backup NOT SAVED", we go through the second attempt which fails and it finally says something to the effect of "Not tuning due to backup" and we get back to the initial Performance menu.
Mike, would it be easier if I give someone a call? or take it over to the DiabloSport support forum? I can report back here for everyone else after we get it sorted out.
Ok guys, we seem to have resolved this :clap:. Thanks Mike for the responses and everybody else who offered (especially Curtis -- future heavy breathing calls are NOT from me :bigwink Pulling the fuse on the power to my Clifford 5.50x alarm resolved the problem... This is really perplexing to me. I was very particular having it installed and specifically did it to be as least invasive as possible. No remote start. No automatic windows. No automatic door locks. I was under the impression that the alarm was a completely independent system with only the power connection directly off the battery. Main unit is powered directly from the battery and add-on sensors are powered by the main unit. I assume the starter kill switch is inserted in the power to the starter. Could it be the (fluctuating?) power draw from the sensors that is doing it? I know that the sensors are powered even when the alarm is deactivated. So, for example, the periphery sensor would still be functioning but the main unit would ignore the input. Heh, the good news is I remembered to turn off the cut-power auxilary siren before pulling the fuse on the alarm power... The bad news is that I forgot to disable the battery disconnect notification on the web site for the GPS unit... 15 min. and 8 txt messages out of my allotment. On the upside, I never tested that feature. Mike, I'm kind of hoping DiabloSport characterizes this 'cause I'm really curious to know what's going on here.
Glad we got this sorted out. It seems that there may be a way to wire up the starter kill circuit so it does not get in the way, but i would have to really look into this to try to figure it out. Easy answer is to be sure any and all aftermarket electronics are disabled before attempting to use the Predator to flash the vehicle. Thanks Mike
True. But it can be an easier answer than customer practice. Maybe a medium priority useability issue? It's going to be real common for the same people who are tuning their cars to have some or a lot of aftermarket stuff as well. Although a good idea, I don't think everybody is going to implement easy disconnect for their systems. I understand, since you're working with reading and writing eprom, the problem may not be fixable from your end. If it is practical to do so that would be nice. Thanks again for your attention in getting me going.
