Help! ALFAOBD mileage correction not working

[Policeboss]

Has anyone had an issue with AlfaObd mileage correction not working after upgrading their EVIC 7" cluster?

I have a 2014 3500 6.7L diesel SRW Tradesman and recently purchased a used 7" EVIC (diesel). I also purchased a MX+ and the AlfaOBD app to correct the mileage/Idle/Drive time. I was successful in changing the Idle/Drive Time but can not get the mileage to change. I'm using AlfaOBD Version 2.1.7.4

Any help would be greatly appreciated.

During correction AlfaOBD says Successful to let vehicle sleep, When I return mileage hasn't changed. Cluster also displays "Continental" While flashing,,

 

[1500ram12]

You're the second one today I've seen have this problem but only one with the mx device having the issue. I'd send Alexey a debug file and ask for a license number for a earlier known working version. The apk files can be found on post 1 of the alphaobd thread. The last file is a known working one.

In the mean time try disconnecting the battery maybe that will reset it. Also if you haven't update the mx. It can be done through the app that comes with it. @Bigdaddyshouse was having a similar issue when changing his, although his said it failed but changed the mileage.



2018 2500 6.4L Tradesman

 

[Policeboss]

You're the second one today I've seen have this problem but only one with the mx device having the issue. I'd send Alexey a debug file and ask for a license number for a earlier known working version. The apk files can be found on post 1 of the alphaobd thread. The last file is a known working one.

In the mean time try disconnecting the battery maybe that will reset it. Also if you haven't update the mx. It can be done through the app that comes with it. @Bigdaddyshouse was having a similar issue when changing his, although his said it failed but changed the mileage.



2018 2500 6.4L Tradesman

Thanks for the suggestions. I disconnected the battery and left it off last night and tried again this morning. I did update the MX+ firmware to the latest 5.0 and gave it a couple more tries. I've watched the Bigdaddyshouse videos, mine unlike his

You're the second one today I've seen have this problem but only one with the mx device having the issue. I'd send Alexey a debug file and ask for a license number for a earlier known working version. The apk files can be found on post 1 of the alphaobd thread. The last file is a known working one.

In the mean time try disconnecting the battery maybe that will reset it. Also if you haven't update the mx. It can be done through the app that comes with it. @Bigdaddyshouse was having a similar issue when changing his, although his said it failed but changed the mileage.



2018 2500 6.4L Tradesman

Thought you might have been on to something. I hadn't updated the MX+, so I did and gave it another few tries. Thanks for your assistance. I will be reaching out to Alexey again.

Mine unlike @bigdaddyshouse says "completed and to let vehicle sleep for a while" I'm not getting an error message.

 

[1500ram12]

Thanks for the suggestions. I disconnected the battery and left it off last night and tried again this morning. I did update the MX+ firmware to the latest 5.0 and gave it a couple more tries. I've watched the Bigdaddyshouse videos, mine unlike his



Thought you might have been on to something. I hadn't updated the MX+, so I did and gave it another few tries. Thanks for your assistance. I will be reaching out to Alexey again.

Mine unlike @bigdaddyshouse says "completed and to let vehicle sleep for a while" I'm not getting an error message.

Alexey is aware of the problem and has found the error. A few others are having issues also. It's odd tho that it doesn't appear to be a universal probably. Some people have had no issues changing mileage and hours.


2018 2500 6.4L Tradesman

 

[skyline090]

This guy didn't have any issues. I think the part that a lot of people aren't doing is the VIN write to the cluster so I would try that and see if you're still getting errors.


Video was uploaded only a few days ago. AlfaOBD walk through starts at 13:30

 

[1500ram12]

This guy didn't have any issues. I think the part that a lot of people aren't doing is the VIN write to the cluster so I would try that and see if you're still getting errors.


Video was uploaded only a few days ago. AlfaOBD walk through starts at 13:30

Hmmm I think this is the first time I've heard of anyone using vin write on a cluster


2018 2500 6.4L Tradesman

 

[Policeboss]

Alexey is aware of the problem and has found the error. A few others are having issues also. It's odd tho that it doesn't appear to be a universal probably. Some people have had no issues changing mileage and hours.


2018 2500 6.4L Tradesman

FIXED!!! Alexey sent me a link to a Windows Version. After activation the mileage corrected on the first try..



Thoughts were that the phone I was using may have been a problem it was a Galaxy using Lollipop.
I had also tried the VIN write, it took and was confirmed but that had not worked for me.




Thanks everyone for your assistance..

 

[SorySS]

Hi guys, having the same issue with the mileage change. Hours and idle worked perfect with Alfaobd, but mileage won’t change on my 7 inch evic. I have a 2019 classic and got the harness to pass the security.
I’m wondering if any of you can help me with this.
Thank you in advance!

 

[CLeng3940]

Alexey is aware of the problem and has found the error. A few others are having issues also. It's odd tho that it doesn't appear to be a universal probably. Some people have had no issues changing mileage and hours.


2018 2500 6.4L Tradesman

I have a 18 ram express, and just upgraded from the 3.5 to the 7 cluster. I have the bypass cable from kaodtech & mx+. I was able to get the splash screen to change and all my vehicle information seems correct, but whenever I try to write hours or mileage alfaobd says “no data received from ecu/interface or data corrupted.” Any help would be greatly appreciated.

 

[1500ram12]

I have a 18 ram express, and just upgraded from the 3.5 to the 7 cluster. I have the bypass cable from kaodtech & mx+. I was able to get the splash screen to change and all my vehicle information seems correct, but whenever I try to write hours or mileage alfaobd says “no data received from ecu/interface or data corrupted.” Any help would be greatly appreciated.

View attachment 230281

There's something with the baud or braud (whatever it's called) that might have to be changed under settings in alfaobd. If you haven't already update your mx+. Use the supplied app for the mx+ and update the firmware.


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

There's something with the baud or braud (whatever it's called) that might have to be changed under settings in alfaobd. If you haven't already update your mx+. Use the supplied app for the mx+ and update the firmware.


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

I updated the Mx+ firmware last night and tried changing the interface baudrate. Still getting the same error message. Not sure what other troubleshooting routes to take.

 

[1500ram12]

I updated the Mx+ firmware last night and tried changing the interface baudrate. Still getting the same error message. Not sure what other troubleshooting routes to take.

Can you screen shot each step you are taking


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

Can you screen shot each step you are taking


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

Can you screen shot each step you are taking


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

I can upload another video of the steps I’m taking for the mileage if needed.

 

[1500ram12]

I can upload another video of the steps I’m taking for the mileage if needed.

Interesting. Besides splash screen have you tried anything else?

Try setting low beams to led or any lighting feature to led to see if that works


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

Interesting. Besides splash screen have you tried anything else?

Try setting low beams to led or any lighting feature to led to see if that works


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

was successfully able to change tire size. I sent the debugging info to alfa and they’re currently looking into it. Hopefully they’ll have an answer for me. I’ll try setting fog lamps to stay on with high beams and let you know what happens. Thanks.

 

[1500ram12]

was successfully able to change tire size. I sent the debugging info to alfa and they’re currently looking into it. Hopefully they’ll have an answer for me. I’ll try setting fog lamps to stay on with high beams and let you know what happens. Thanks.

If you were able to change tire size then never mind. Was thinking it could have been something with the bypass cable or the mx+. Sounds like it could be a bug in alfaobd. Are you running the most current version? Looks like there was a update at the end of November


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

If you were able to change tire size then never mind. Was thinking it could have been something with the bypass cable or the mx+. Sounds like it could be a bug in alfaobd. Are you running the most current version? Looks like there was a update at the end of November


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

I just bought the app last night so I assumed the most recent version was installed. I will double check. Maybe try running an older version?

 

[1500ram12]

I just bought the app last night so I assumed the most recent version was installed. I will double check. Maybe try running an older version?

I would assume it would be the most current version. But couldn't hurt to check


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

 

[CLeng3940]

I would assume it would be the most current version. But couldn't hurt to check


2018 2500 6.4L Hemi Tradesman
1990 5.9L 12v Cummins W250

everything is up to date. I just went to reattempt total hours and it was changed correctly. Not sure what happened or how. The only thing I can think that I did differently is that I didn’t wait 30 sec like Alfa requests...just turned it off, waited for 5ish seconds and clicked it back to run. Just tried changing idle hours so we’ll see if that changes as well.