Anyone with 03 -07 Dodge Cummins in FTC or NoCo

Discussion in 'The Rockies – It's all downhill from here...' started by clang, Jan 30, 2013.

  1. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    I have a 2004.5 Ram 2500, heavily modded. I have a Smarty programmer that is throwing a connection error - can't communicate with the ECM. Truck runs great, no issues or codes, the ECM tests out fine, the Smarty just won't communicate with the control module.

    I'm trying to figure out if it is my Smarty or something to do with all the mods on the truck. I would like to connect it to another truck to see if it can communicate with the ECM. That will at least tell me if the programmer has issues, or my truck is the issue.

    I would need a truck running the OEM program.

    Thanks :freaky

    9 Seven 0 three 72 one 33 one
    #1
  2. mtnbkrmatt

    mtnbkrmatt Adventurer

    Joined:
    Mar 23, 2010
    Oddometer:
    71
    Location:
    Gunnison, CO
    I've got an 03, but I'm in gunnison. Double check all your fuses.
    #2
  3. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    Thanks for the suggestion. I've been through the whole IPM, checked every fuse and relay, and cleaned every contact. Checked the wiring harnesses (did find two wires that had abraded areas and exposed copper, which helped fix an unrelated issue with the tranny).
    #3
  4. mtnbkrmatt

    mtnbkrmatt Adventurer

    Joined:
    Mar 23, 2010
    Oddometer:
    71
    Location:
    Gunnison, CO
    I figured you had, but thought I'd mention it. I worked on an 06 1500 once. It had blown a fuse, so the owner pulled the fuse labeled "spare" and stuck it where the blown one was. Then the radio wouldn't work. Turned out the radio ran through the spare fuse.
    #4
  5. jjustj

    jjustj cum petris et choris

    Joined:
    Jun 14, 2005
    Oddometer:
    6,082
    Location:
    9157 ft Dillon CO
    i get down to boulder and ft fun once a month or so what kind of time would that take?
    :ear
    #5
  6. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    About 10 minutes. I need to connect the Smarty to the OBD2 port and see if it will connect to the ECM. We don't need to change anything, just see if it will connect.
    #6
  7. SaharaJp99

    SaharaJp99 Been here awhile

    Joined:
    Feb 26, 2011
    Oddometer:
    695
    Location:
    Nunn
    Find a dealership with a used one and take it for a test drive!
    #7
  8. _cy_

    _cy_ Long timer

    Joined:
    Sep 25, 2011
    Oddometer:
    6,504
    Location:
    Tulsa, Oklahoma
    you need to speak to Smarty's customer service. there's a possibility, how ever small of screwing up another truck's electronics.
    #8
  9. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    It was the Smarty dealer that asked me to try it on another truck before sending it back to them.......
    #9
  10. _cy_

    _cy_ Long timer

    Joined:
    Sep 25, 2011
    Oddometer:
    6,504
    Location:
    Tulsa, Oklahoma
    talk to tech support at Smarty manufacturer .... not the dealer.
    #10
  11. thump_co

    thump_co ..ouch

    Joined:
    Feb 23, 2011
    Oddometer:
    2,502
    Location:
    8532'
    That would be a really nasty bug. A decent programmer should have to get an error code free connection before they'll even read settings, and then will only write after doing a backup of the OEM fw and multiple confirmation prompts and key cycling.
    #11
  12. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    This is the way the Smarty works. It first attempts to talk to the ECM on the truck. If it can, and it's not VIN locked to another vehicle it asks you what you want to do. It does nothing without many button presses and confirmations from the user.

    At this point it can't seem to talk to the ECM on my truck. It throws a comm error that Smarty is telling me indicates the unit either can't talk to the ECM, or other electronic signals are interrupting the communication (or the unit is bad). My ECM is good. I have had it tested, and like I said the truck runs like a champ, no codes and no warning lights.

    What I am wanting to do is just see if it can successfully communicate with the ECM on another truck. Mine is currently running the stock program, so the unit is not locked to my truck.

    These are great programmers, I have had a couple for various year trucks, but they are known to have trouble connecting to 2004.5 and 2005 trucks. It has something to do with the way the ABS system communicates with the ECM, and disrupts the communication to the programmer. Any mods to the truck, like aftermarket fuel pumps, transmission control modules etc can make the problem worse. My truck has all of these.

    If it works fine on another truck, I'm just going to wire a second minimal OBD2 port to the ECM specifically for the programmer.
    #12
  13. LostAussie

    LostAussie Growing Old, Not Up!

    Joined:
    Nov 17, 2007
    Oddometer:
    565
    Location:
    Johnstown, Colorado
    I have a stock 03 in Johnstown.
    #13
  14. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    Is there a time this weekend I could swing by and give this a test?

    You can call me any time.

    9 Seven 0 three 72 one 33 one

    Thanks :freaky
    #14
  15. eakins

    eakins Butler Maps

    Joined:
    May 29, 2002
    Oddometer:
    21,657
    Location:
    Fort Collins, Colorado
    so?
    #15
  16. Dozer Dillon

    Dozer Dillon Been here awhile

    Joined:
    Jun 2, 2009
    Oddometer:
    252
    Location:
    CO
    I have a 2004.5. Not sure if I'm any closer. I'm in Elizabeth. Have you tried Dodge Diesel Forum. I have found them to be very helpful.
    #16
  17. clang

    clang Not lost, Exploring!

    Joined:
    Sep 18, 2003
    Oddometer:
    2,805
    Location:
    Denver/Aspen
    LostAussie and I talked on the phone yesterday for a bit. Unfortunately I got tied up working on my other Ram getting it ready to sell, so I haven't had a chance yet to test the programmer.
    #17