AlfaOBD

[theblet]

I'm going to ask a NEWB question, so please be easy. Also, I DID spend over an hour looking for this information...............so again, please be easy.

I have a 2024 1500 Laramie and am trying to get Alfa hooked up. I have the bypass cable with the two smaller plugs and the OBD. I know where to plug the smaller plugs in. I know to remove the "stock" OBD and put the other end of my bypass cable where that used to be. First question, is that correct?

Second question, assuming the "stock" OBD plug is now my bypass cable..............what do I do with the "stock" OBD plug? Just tie it up out of the way?

I was planning on leaving the bypass cable in and my MC+ plugged in while I make several changes. Thank for any help.

I leave the bypass cable in place, but not the MC+. It looks like it stays on when the trucks off. It may drain the battery

 

[kapinallinen2]

I remove my SGW bypass cable and leave my MX+ plugged in.
It has an operating current of 62 mA and in battery saver mode it draws 2mA.

 

[Csjumper2003]

Does anyone know how to turn down the audible press sounds? Seems they're set at same level as stereo but I would prefer them at half that volume...

Sent from my SM-S918U1 using Tapatalk

I was thinking the same. I turned it off bc it is so loud

 

[Lature1984]

You have Uconnect 5. Entirely different than the 2019-2021 radios, so basically none of their info applies to you. Your issue is most like a radio software issue, which UC5 is riddled with at the moment. You are one version behind though, I can send you the newest update that you can load via usb.

I'd like this too if you could send it please

 

[Kenobe]

I used AlphaODB to activate the rain sensor I installed for my wipers. First start of the truck - works great. Second start of the truck - I get a 'service power steering" light. I tried all kinds of backing out the change, d/c the battery and nothing made that error go away. Note the power steering worked just fine.
A week later I went to the dealer for something else and asked them to look at that error. They brought the truck back out later and said "the error light is gone, no idea why it was on"
So, how the heck did AlphaODB make that error come on, and how the heck did the dealer make it go away? Note there were NO error codes in the system.

I'm scared to try anything else with Alpha ODB now.

 

[HSKR R/T]

I used AlphaODB to activate the rain sensor I installed for my wipers. First start of the truck - works great. Second start of the truck - I get a 'service power steering" light. I tried all kinds of backing out the change, d/c the battery and nothing made that error go away. Note the power steering worked just fine.
A week later I went to the dealer for something else and asked them to look at that error. They brought the truck back out later and said "the error light is gone, no idea why it was on"
So, how the heck did AlphaODB make that error come on, and how the heck did the dealer make it go away? Note there were NO error codes in the system.

I'm scared to try anything else with Alpha ODB now.

Did you try clearing the code yourself? Might have just been a fluke

 

[Kenobe]

Did you try clearing the code yourself? Might have just been a fluke

No code in the system, even the dealer said so

 

[Brutal_HO]

@Kenobe BACKUP THE CONFIG before you touch anything,

 

[Darksteel165]

@Kenobe BACKUP THE CONFIG before you touch anything,

I feel like someone should say this on every single page of these threads lol.
Not only backup the config, verify you can restore, or at a minimum get the file to look at the clear text of what was changed.
For a while restores would not work for me, I just manually changed settings back but not everything has a settable state.

 

[1923bob]

I used AlphaODB to activate the rain sensor I installed for my wipers. First start of the truck - works great. Second start of the truck - I get a 'service power steering" light. I tried all kinds of backing out the change, d/c the battery and nothing made that error go away. Note the power steering worked just fine.
A week later I went to the dealer for something else and asked them to look at that error. They brought the truck back out later and said "the error light is gone, no idea why it was on"
So, how the heck did AlphaODB make that error come on, and how the heck did the dealer make it go away? Note there were NO error codes in the system.

I'm scared to try anything else with Alpha ODB now.

Go with the Tazer

 

[Darksteel165]

Go with the Tazer

This has nothing to do with anything an TazerDT can do...

 

[combat grunt]

Anyone have a writeup on how to change the Fuel tank Size just upgraded to a 55gal S&B on the mega cab I though I had it bookmarked but I don't and my cell phone google fu is not on it today its a 2022 Ram 2500 if it needs to be specific.

 

[Dballard17]

I'm just about to start my adventure into Alphaobd with my 2019 1500(DT). When accessing the body computer there are 4 variants to choose from. Is there any way to tell which one I need to choose? They all start with "DT MY2019 PowerNet" followed by a variation number. Sorry if this is a dumb question. Just don't want to go messing things up somehow.

 

[combat grunt]

I was able to go the body module and then vehicle config to change the tank size. It didn’t work at first just stated “low” on the DTE. Went back home hooked it up again reset it to factory then back to 208liters then it worked.

 

[Aidan]

I programmed the off road and performance pages this morning. I have a ‘22 Big Horn Level 2, night edition with 8” screen. Nothing came up in the screen but I did get the pages in the driving cluster, which for me actually makes more sense. It funny because my uncle came over to watch/help me install the MOPAR Ram Airflow CAI right after I programmed it. It was cool to take it for a drive with the CAI and then have the performance pages as well. Made it feel like I was driving a muscle car, LOL.

The performance options had lap times, drag race times, g-forces, etc.

The off-road options had the two angle bubbles and suspension diagram.

It was all controlled with the steering wheel buttons. This made the whole purchase of the OBD reader, bypass cable, alfaOBD and android tablet purchase worth it!

View attachment 144634View attachment 144635View attachment 144636View attachment 144637View attachment 144638View attachment 144639View attachment 144640View attachment 144641View attachment 144642View attachment 144643

Would you mind sharing how you did this? I tried and it shows on infotainment but not the cluster.

 

[combat grunt]

Hello,
I installed a S&B 55Gal Tank on my 2022 Ram 2500. I was able to get the fuel tank size reset but the fuel gauge is not working or the DTE as is should. For example it shows I have 1,000miles remaining I have already went 400 I do average 18-20mpg (HWY) most of my driving so the math still don't add up. Has anyone adjusted any other setting to show the gauge correctly? I figure every 13ish Gallons I should move a QTR Tank on the gauge. At this point I'm still showing over full and have the setting for fuel tank size set at 50gallons in size or 189L (DTE did adjust up), I tried adjusting it to 208 DTE moved up but did a test gauge only moved off full just barely at 500miles.

 

[HSKR R/T]

Hello,
I installed a S&B 55Gal Tank on my 2022 Ram 2500. I was able to get the fuel tank size reset but the fuel gauge is not working or the DTE as is should. For example it shows I have 1,000miles remaining I have already went 400 I do average 18-20mpg (HWY) most of my driving so the math still don't add up. Has anyone adjusted any other setting to show the gauge correctly? I figure every 13ish Gallons I should move a QTR Tank on the gauge. At this point I'm still showing over full and have the setting for fuel tank size set at 50gallons in size or 189L (DTE did adjust up), I tried adjusting it to 208 DTE moved up but did a test gauge only moved off full just barely at 500miles.

This is a 1500 forum. Try getting help from HDRams.com

 

[MxChris]

Hello all,​

My 2020 Tradesman is pretty basic for options so I upgraded my radio from the 5" to the 8.4" Uconnect 5 recently. This week I put in a 7" digital cluster from a wrecked 2020 1500, screen is great and simple install but obviously the mileage isn't correct. Trying to input the correct mileage and hours and I keep hitting a brick wall. I first tried the vLinker MC with AlfaOBD via Bluetooth, I'd make the change I want, it would say it was successful and to let the car sit for several minutes. Come back an hour later and no changes were made. On one of my tries with the vLinker MC it made a change to the mileage but incorrectly, 10k miles off what I input. Same combo but this time on Windows, same results. Bought the OBDLink EX because it's USB, Windows again and am getting exactly the same results.​

• I have the AlfaOBD software running on a Microsoft Surface running Windows 10.
• OBDLink EX and vLinker MC
• Basic security gateway cable from Amazon.
• I've tried the vLinker MC with the Android and also Windows versions of AlfaOBD. Changes seem successful but do not take on either version of the software.
• I've tried OBDLink EX with Windows. Changes seem successful but do not take.
• I have input the mileage as xxxxx and xxxxx.x, same results
• At this point in my troubleshooting, the only constant is the security gateway bypass. Is there a performance difference in these cables?

 

[Jimmy07]

Hello all,​

My 2020 Tradesman is pretty basic for options so I upgraded my radio from the 5" to the 8.4" Uconnect 5 recently. This week I put in a 7" digital cluster from a wrecked 2020 1500, screen is great and simple install but obviously the mileage isn't correct. Trying to input the correct mileage and hours and I keep hitting a brick wall. I first tried the vLinker MC with AlfaOBD via Bluetooth, I'd make the change I want, it would say it was successful and to let the car sit for several minutes. Come back an hour later and no changes were made. On one of my tries with the vLinker MC it made a change to the mileage but incorrectly, 10k miles off what I input. Same combo but this time on Windows, same results. Bought the OBDLink EX because it's USB, Windows again and am getting exactly the same results.​

• I have the AlfaOBD software running on a Microsoft Surface running Windows 10.
• OBDLink EX and vLinker MC
• Basic security gateway cable from Amazon.
• I've tried the vLinker MC with the Android and also Windows versions of AlfaOBD. Changes seem successful but do not take on either version of the software.
• I've tried OBDLink EX with Windows. Changes seem successful but do not take.
• I have input the mileage as xxxxx and xxxxx.x, same results
• At this point in my troubleshooting, the only constant is the security gateway bypass. Is there a performance difference in these cables?

Use the vLinker MC and the windows version. You need to enter the kilometer value that is equivalent to the miles that you want displayed.
Alfaobd can’t change the hours on the 5th gen rams.

 

[MxChris]

Use the vLinker MC and the windows version. You need to enter the kilometer value that is equivalent to the miles that you want displayed.
Alfaobd can’t change the hours on the 5th gen rams.

Thanks, this worked. Hopefully the hours will be able to be changed in the future, I've noted those to fix it if so.
The OBDLink EX is on the officially supported list so I thought it would be better to have that?