Help Support Ram Forum by donating:


  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Alphaobd Mileage Correction Notes

Discussion in '4th Gen DIY' started by 1500ram12, Jan 16, 2020.

  1. 1500ram12

    1500ram12 Senior Member

    Posts:
    5,300
    Likes Received:
    2,103
    Joined:
    Jan 23, 2012
    Ram Year:
    2018
    Engine:
    6.4L Hemi
    Since there is a lot of "issue" with alphaobd and mileage/Hour's correction I thought if we can compare what version worked with what year truck and what year cluster maybe we can find a pattern.

    Version 2.1.7.3
    2018 2500 Tradesman 6.4L
    2017 7" sport Cluster
    Scantool Obdlink MX +
    2017 kindle fire 7
    Samsung galaxy note 5
    Hour's worked first try
    Only issue couldn't set exact mileage. Was off .3 miles


    2018 Ram 2500 6.4L Hemi Tradesman
     
    Last edited: Jan 16, 2020
    likes2build and Noneck like this.
  2. 1500ram12

    1500ram12 Senior Member

    Posts:
    5,300
    Likes Received:
    2,103
    Joined:
    Jan 23, 2012
    Ram Year:
    2018
    Engine:
    6.4L Hemi
    Saved


    2018 Ram 2500 6.4L Hemi Tradesman
     
  3. 1500ram12

    1500ram12 Senior Member

    Posts:
    5,300
    Likes Received:
    2,103
    Joined:
    Jan 23, 2012
    Ram Year:
    2018
    Engine:
    6.4L Hemi
    Saved


    2018 Ram 2500 6.4L Hemi Tradesman
     
  4. chri5k

    chri5k Senior Member Supporting Member

    Posts:
    1,054
    Likes Received:
    1,400
    Joined:
    May 24, 2019
    Location:
    USA
    Ram Year:
    2016
    Engine:
    Diesel
    Truck: 2016 2500 6.7 Cummins
    Trim: SLT
    Original Radio: 2016 RA2 - 5"
    Current radio: 2018 UAQ
    Cluster: 2016 3500 6.7 Cummins
    Dongle: Scantool MX
    Phone: Galaxy S7
    AlphaOBD: 2.1.7.3
    Milaeage: Worked first time. Off by 0.3
    Hours: Worked first time. Dead on.
    Nav in Cluster: Working with graphics present.
     
    Last edited: Jan 16, 2020
  5. Jimmy07

    Jimmy07 Senior Member

    Posts:
    2,791
    Likes Received:
    2,255
    Joined:
    Feb 23, 2017
    Ram Year:
    2017
    Engine:
    6.4 Hemi
    Android ver. 2.1.7.7
    MX Bluetooth
    Truck: 2017 ram 2500 tradesman 6.4
    2015 regular 7” cluster
    2016 longhorn cluster
    2017 (currently) limited cluster
    Truck: 2015 ram 2500 tradesman CTD
    Original 3.5” cluster
    2016 regular 7” cluster
    2016 longhorn cluster (from above)
    All of the above worked the first try for mileage and hours. The whole mileage number is always correct, with the tenths varying between .3-.8 off.
     
  6. chri5k

    chri5k Senior Member Supporting Member

    Posts:
    1,054
    Likes Received:
    1,400
    Joined:
    May 24, 2019
    Location:
    USA
    Ram Year:
    2016
    Engine:
    Diesel
    Man you are like the 7" diesel clustermeister. I had a really hard time finding one diesel cluster. I guess you had the market cornered on them. ;-)
     
  7. Jimmy07

    Jimmy07 Senior Member

    Posts:
    2,791
    Likes Received:
    2,255
    Joined:
    Feb 23, 2017
    Ram Year:
    2017
    Engine:
    6.4 Hemi
    The only one that was actually a diesel cluster was the longhorn. I ran it in my gasser first, then sold it to a coworker who has the 6.7 CTD.
    I tend to get bored after looking at the same thing for a while. They’re easy to find and get your money back on the old one.
     
  8. SeaRefractor

    SeaRefractor Junior Member

    Age:
    52
    Posts:
    22
    Likes Received:
    9
    Joined:
    Jan 23, 2018
    Location:
    Normandy Park, WA
    Ram Year:
    2016
    Engine:
    Hemi 5.7
    Truck: 2016 1500 5.7 V8 Hemi
    Trim: Tradesman
    Original Radio: 2016 RA1
    Current radio: 2016 RA1
    Cluster: 2016 1500 Laramie 5.7 V8 Hemi
    Dongle: Obdlink MX +
    Phone: OnePlus 7 Pro
    AlphaOBD: 2.1.7.7
    Milaeage: Worked first time. On targe
    Hours: Gave error. Set correct.

    Worked great! Did get a failure on setting engine total hours and idle hours, but restarting the truck the hours show correctly.
     
    1500ram12 likes this.
  9. Mordechai

    Mordechai Member

    Age:
    28
    Posts:
    60
    Likes Received:
    24
    Joined:
    Mar 30, 2019
    Location:
    St. Pete, Florida
    Ram Year:
    2016
    Engine:
    5.7 Hemi
    Truck: 2016 1500 5.7
    Trim: SLT
    Original Radio: 2016 RA2
    Current radio: 2016 RA2
    Cluster: 2017(maybe 2018 truck date is 12-17) 1500 Big Horn 5.7
    Dongle: Generic ELM327
    Phone: OnePlus 6t
    AlphaOBD: 2.1.7.7
    Mileage: No error, completed successfully, did not change mileage.
    Hours: No error, completed successfully, did not change hours.

    Will try again tomorrow with a OBDlink MX. Can't seem to get it to work with cheap OBD reader. Have not had problems with alfa until now.
     
    1500ram12 likes this.
  10. Mordechai

    Mordechai Member

    Age:
    28
    Posts:
    60
    Likes Received:
    24
    Joined:
    Mar 30, 2019
    Location:
    St. Pete, Florida
    Ram Year:
    2016
    Engine:
    5.7 Hemi
    Tried this again today with OBDlink MX. While it is 6x the price of the scanner i had, you get what you pay for. Worked great! Here are some notes:

    I pulled the build sheet for the donor truck, it was actually a 2018 3.6 Big Horn/SLT. P/N 68340663AB.
    Both the Mileage, and hours gave me a "procedure failed" message, but took right away(After the flash cycle). Hours appear spot on, and mileage is almost perfect.

    Cluster had: 21060.3, I wrote 92,135.6. Odometer now displays 92,135.3

    OnPlus 6t is on the latest version of Android 10(10.0.31), Kept the same alfaOBD version.
     
    dracman and 1500ram12 like this.

Share This Page