xtremeDAN

just to start off some info.

about a month ago at the shop i work at we were working on a 2010 ram dsl, useing a titan remote starter and fortin evo chr. for what evere reasona t the time the guy doing the install said it wouldnt work and ripped it out and put in an idata ads al ca. after some testing thought that it was ok.

a week later the customer called and said that everyonce and a while the truck would not start on the first atemp. didnt think it was a big deal so he was in rush to come in for us to have a look at it.

a week after that i did a nother one and due to the issues i called fortin and ta that point they told us that the evo would not work yet. so that modual was out so i called idata and they said it should be fine so i installed it and was testing it and on the 3rd or fourth test the ign turned on and waited its 8 seconds for the glow plugs then the starter cranked shut down cranked again and repeatidly did this every half second.

i shut it down and tried again and it worked fine.

after that i left it for a while and tried again and watched the cluster to see if there was any warning signs or anything and there was a lightning bolt looking symbol on the dash and this time it did not even atemp to crank just shut down.

so i ripped out the ads and hard wired it all thinking maybe it was a data issue.

tested it again and this time it did the same thing as the other truck every once and a while it wouldnt crank on the first attemp. But the customer needed his truck so he left with it and would come back at a later date.

both trucks were from the same dealership and my shop foreman went there one day to try and fix both of them. there was a new firmware update for the ads witch fixed the 2500 but not the 3500 that i did.

the same day that he was there we did a nother install in a 3500 and found the same issues.

we had nothing to loose so we used a titan remote starter and the evo chr with the t harness and wired in 2 way data hooked up power ground parklights and hood pin and tested it. with the newest firmware 2.03 on the evo and it programmed for the factory alarm everything worked flawlessly for 2 days and since then there has been no complaints from the customer.

we called ads to see if they had heard of the issues we had seen and they said no but the next time we get a 3500 in they want us to call them and try and find whats going on.

has anyone else seen any weird issues like this?

Westec

iTrader: (1)

yes, the 180 ohm mux wire input (the start wire that is done by data inside the unit) does not rest at true ground...this is the issue. i am not yping it and out why...but you cam PM me and i will explain it via the phone.

xtremeDAN

Thanks for the info. no need to go any further with it on here like you have mentioned. just strange that i data would not know that if others have had the same issue. they usually have no issues.