[John Jensen]

PapaCap,
AlphaOBD has a Windows version for your computer. Or is it an Apple too?

I can understand why AlfaOBD isn't Apple compatible. With Apple, everything is sooo proprietory and it's their way or the hiway. I doubt that Apple would ever approve an app like AlfaOBD that can modify a system.

That said, they do make some great products, albeit all way overpriced.

 

[PapaCap]

I hear ya but still not happy. Once I went to the dark side (Apple) I haven’t looked back. Got tired of every manufacturer blaming the other for problems. With my iPhone, iMac, iPad, Apple TV, Time Capsule, and Apple Airport Express I just point out the problem and, viola, they solve it. While alfaOBD would be nice, and I’d buy it today if it connected to my iPhone, there is nothing it offers that is critical to my needs that would warrant getting an android device just to have alfaOBD.

 

[PapaCap]

I made an inquiry to alfaOBD about future opportunity for iPhone use and their response was “iOS version is in plans for some time already, maybe by mid of year.” Hopeful but no need to hold my breath.

 

[EcoD]

Heres a link of a guy swapping out display for a 7"

 

[EcoD]

More AlphaOBD Settings

AlfaOBD

Please Read!!! Supported years: 2013 to 2018 Make a backup of your original BCM configuration before making any changes. While we have a few BCM configs to compare with, there is nothing like comparing to your own pre-changes. Instructions: Uploading System ID (BCM) Information: Thank you...

www.ramforum.com

 

[golruss]

I have started this thread in hopes that we can build upon it and create our own FAQ and application help section that is specific to our 3.0L diesel engine.

AlfaOBD is a software for FCA group cars diagnostics. Fiat/Alfa Romeo/Lancia cars produced in 1994-2017, and Chrysler/Dodge/Ram/Jeep cars of model years 2005-2017 are supported. Although the software is primarily targeted for car owners, it provides many of the features of professional scanners.

Model years starting in 2018 are also fully supported currently with the aid of a bypass module. Personally I have a 2014 Ram Eco Diesel so I do not have a use for a bypass module. It would be great for those have supported vehicles in the model years starting in 2018 if they could also post about there experiences using a bypass module.

AlfaOBD natively supports Electronic control units installed in FCA group cars. Native support differs AlfaOBD from many other diagnostic applications providing OBD II generic support limited with engine and transmission modules. The application suite is powerful giving the user control of many of the same functions in the professional WiTech II tool that most Ram dealers use.

AlfaOBD is supported on Windows PC and Android devices. The official web site of Alfaobd is: AlfaOBD

I have a 2018 Ecodiesel and just did the DRL, enable fog light on high beam and change max speed limit. The hardest part was getting to the secure gateway module - its behind the radio. Had a check engine light for loss of communication to transfer case and something and of course you cannot clear the code using the conventional method. So I just drove around and start stop a couple of times and called it a night. This morning when I started the truck to go to work everything was back to normal. I probably should have taken some pictures while I was at it.

 

[PaulK]

Does anyone know if you can find odometer readings by date with code reader and or OBDalpha. I need it for taxes. Business truck. BTY I was able to program the VIN and injector codes into a ECM that I purchased. Thanks to all that worked to figure it out and posted instructions.

 

[Bravo2]

I have a 2018 Ecodiesel and want to read/clear a check engine light. So far in alfaOBD I:

• Connected to OBDLink MX
• Selected Dodge/Ram
• Ram 1500 (DS/DX)
• Engine
• Diesel Bosch EDC17C49

When I attempt to connect I get:
Interface Message CAN error connect failed. Verify the key is in MAR and check wiring.

My push button is in the ACC position. Any idea what I'm doing wrong?

 

[Crash68]

When I attempt to connect I get:
Interface Message CAN error connect failed. Verify the key is in MAR and check wiring.

My push button is in the ACC position. Any idea what I'm doing wrong?

Did you set he communication protocol to:
ISO 15765-4 (CAN 11bit/500k baud)

I'm not certain if you need the security gateway bypass to read the error codes but you'll need one to write any changes and probably clear codes also being that yours is an '18.
If you need the security bypass cable for an '18+: Home | KaodTech

 

[Bravo2]

Did you set he communication protocol to:
ISO 15765-4 (CAN 11bit/500k baud)

I'm not certain if you need the security gateway bypass to read the error codes but you'll need one to write any changes and probably clear codes also being that yours is an '18.
If you need the security bypass cable for an '18+: Home | KaodTech

Thanks!

I did not change anything with the communications protocol. Whereabouts would I do that in the settings?

And yes, I am using the security bypass cable from KaodTech.

 

[gtsav2006]

I have a 2018 Ecodiesel and want to read/clear a check engine light. So far in alfaOBD I:

• Connected to OBDLink MX
• Selected Dodge/Ram
• Ram 1500 (DS/DX)
• Engine
• Diesel Bosch EDC17C49

When I attempt to connect I get:
Interface Message CAN error connect failed. Verify the key is in MAR and check wiring.

My push button is in the ACC position. Any idea what I'm doing wrong?

ACC is the wrong position. One more notch to RUN, but don't crank the engine (if you are reading codes). If your's is push button, you have to push twice without the brake pedal pressed.

 

[Bravo2]

ACC is the wrong position. One more notch to RUN, but don't crank the engine (if you are reading codes). If your's is push button, you have to push twice without the brake pedal pressed.

Thanks, I eventually went back and tried it all again in the RUN position but still no luck with the connection. I think it has something to do with the communications protocol I'm using.

 

[Crash68]

I did not change anything with the communications protocol. Whereabouts would I do that in the settings?

I must ha e had something else on the brain when I posted, but in AlfaOBD under Preferences, is the Interface set to the correct type? Is the baud rate at the default 115200 and is the BLUE adapter not selected?
Just throwing some $0.02 ideas out there

 

[gtsav2006]

Are you getting the "Interface connected' confirmation before you select the ECM? I have a had time getting it to connect if I select the ECM before letting the interface get setup. In my experience, the OBD Link is kind of finicky about connecting as well. If its giving me a hard time it seems to help to press the button on the OBD Link adapter once. The bluetooth light should start blinking.

 

[Bravo2]

Are you getting the "Interface connected' confirmation before you select the ECM? I have a had time getting it to connect if I select the ECM before letting the interface get setup. In my experience, the OBD Link is kind of finicky about connecting as well. If its giving me a hard time it seems to help to press the button on the OBD Link adapter once. The bluetooth light should start blinking.

Thanks, I will make sure to check it's connected well before doing anything else.

is the Interface set to the correct type? Is the baud rate at the default 115200 and is the BLUE adapter not selected?

The interface was set to OBD Bluetooth, the Blue adapter option was unchecked, and the baudrate was the default 115200.

I will mess around with it some more when the weather gets warmer and things aren't so tense. Right now I'm afraid of bricking my truck and having to take it to the dealer.

 

[Bounty Hunter]

I've now reprogrammed my stock ECM using AlfaOBD, worked like a champ. The cheap VeePeak bluetooth OBD adapter worked flawlessly.

 

[TonyMM]

I've now reprogrammed my stock ECM using AlfaOBD, worked like a champ. The cheap VeePeak bluetooth OBD adapter worked flawlessly.

What do you mean by « reprogrammed »?

 

[John Jensen]

I've now reprogrammed my stock ECM using AlfaOBD, worked like a champ. The cheap VeePeak bluetooth OBD adapter worked flawlessly.

Bounty,
Congrats!
Glad to hear the VeePeak works so well. Your endorsement is appreciated. I see they are only 12.00 on Amazon. I'm ordering one for each vehicle. That way I don't have to move my MX between them and will have an OBD2 device in the vehicle when on the road.

 

[Kazimodo]

What do you mean by « reprogrammed »?

references :
Official Alfaobd thread
and
Programming new ECM to ED with AlphaOBD

post # 461 in second link has a PDF file in it , step-by-step instructions , you should read tge posts after #461
to make sure you get proper year ECM to match your truck.

 

[Bounty Hunter]

What do you mean by « reprogrammed »?

Adjusted the VIN and injector codes for the ECM to match the truck.

Bounty,
Congrats!
Glad to hear the VeePeak works so well. Your endorsement is appreciated. I see they are only 12.00 on Amazon. I'm ordering one for each vehicle. That way I don't have to move my MX between them and will have an OBD2 device in the vehicle when on the road.

Make sure it's the VeePeak BLE in order to have the bluetooth option. The cheaper VeePeak is wifi only and I wouldn't recommend it. The VeePeak BLE costs more than $12 from what I can see.

I recommend not leaving them plugged in when not using the vehicle. It will cycle the dash lights on and off, and who knows what else it repeatedly powers up.