AlfaOBD Problem....Need some help

[planetbrian]

I'm having some issues with Alfaobd and my 2024 Power Wagon. I have the MX+, Kaodtech SGW bypass cable, and AlfaOBD software. I initially connected with my Windows Surface Pro tablet and also with my Android phone without any issues. I noticed an error code showing a daytime running light was out, so I did not do anything further until the dealership changed the light which they did. I brought my fixed truck home on Friday, and on Sunday I plugged in the MX+ to do some mods and I could not connect via bluetooth to either my tablet or phone. I spent a few hours trying to get it to connect....I even moved the pin connectors to different posts. I finally took out the bypass cable and connected MX+ to the factory obd connector for reading, and everything immediately connected and I noticed 3 error codes....U0011, U0232, U0184.

I tried to clear the codes with Alfaobd, but they keep coming back immediately. I then thought to unhook the battery for a while and while doing that, I noticed a good amount of corrosion on my negative battery post. I cleaned that up and left the negative cable off for 30 minutes, but the codes are still coming back. Interesting that I would think the mechanic would have noticed the corrosion on the post when replacing the light. Whatever the reason, I think i have a bad battery.

My questions are:

1) Why would I not be able to connect again via bluetooth using the bypass cable? Was it because the codes were already there?
2) Did the codes come up because of the connection problems?
3) Would the corrosion on the battery post cause this?
4) Would replacing the defective light assembly cause these codes?
5) Do I need the bypass cable to clear the codes?

Thank you for your help.

 

[planetbrian]

I'm having some issues with Alfaobd and my 2024 Power Wagon. I have the MX+, Kaodtech SGW bypass cable, and AlfaOBD software. I initially connected with my Windows Surface Pro tablet and also with my Android phone without any issues. I noticed an error code showing a daytime running light was out, so I did not do anything further until the dealership changed the light which they did. I brought my fixed truck home on Friday, and on Sunday I plugged in the MX+ to do some mods and I could not connect via bluetooth to either my tablet or phone. I spent a few hours trying to get it to connect....I even moved the pin connectors to different posts. I finally took out the bypass cable and connected MX+ to the factory obd connector for reading, and everything immediately connected and I noticed 3 error codes....U0011, U0232, U0184.

I tried to clear the codes with Alfaobd, but they keep coming back immediately. I then thought to unhook the battery for a while and while doing that, I noticed a good amount of corrosion on my negative battery post. I cleaned that up and left the negative cable off for 30 minutes, but the codes are still coming back. Interesting that I would think the mechanic would have noticed the corrosion on the post when replacing the light. Whatever the reason, I think i have a bad battery.

My questions are:

1) Why would I not be able to connect again via bluetooth using the bypass cable? Was it because the codes were already there?
2) Did the codes come up because of the connection problems?
3) Would the corrosion on the battery post cause this?
4) Would replacing the defective light assembly cause these codes?
5) Do I need the bypass cable to clear the codes?

Thank you for your help.

Update: So I installed the OBDMX+ Android software and that software shows no DTC error codes. The AlfaOBD software continues to show the same error codes even after I hit the clear codes button. AlfaOBD also says "No data received from ECU/Interface or data corrupted".

I was able to connect to the ALFAOBD software on my Windows tablet and the button to read faults is different than the Android version. Windows version shows "Read Present Faults" and that button shows no faults. Something is jacked up with Android version.....that button says "Read Confirmed Faults" and after clearing them they just show up again.

 

[John Jensen]

A thought - Alpha will not connect if you have the MX+ app open/connected.

 

[Brutal_HO]

A thought - Alpha will not connect if you have the MX+ app open/connected.

This holds true for pretty much any of the apps. Especially Torque which, unless set properly, won't drop the BT/BLE connection even exiting the app.

I finally just put in a Y-cable so I can have 2 readers connected. One is on the bypass side for AlfaOBD/JScan, one on the read only side for Torque where I run my tablet/gauges.

 

[John Jensen]

This holds true for pretty much any of the apps. Especially Torque which, unless set properly, won't drop the BT/BLE connection even exiting the app.

I finally just put in a Y-cable so I can have 2 readers connected. One is on the bypass side for AlfaOBD/JScan, one on the read only side for Torque where I run my tablet/gauges.

I also put in a Y-cable, my bypass side is for my SOTF tuning which I disconnect when I need that side for MX+ and alpha, the read only side has my Edge Insight CTS3

 

[planetbrian]

A thought - Alpha will not connect if you have the MX+ app open/connected.

I did not have both apps opened at the same time.

 

[planetbrian]

I fingered it out. With the KAODTECH cable, I mistakenly connected the 2 pin white connector to the white terminal block and the 2 pin black connector to the black terminal block. The directions say to do the opposite....Hmmm sounds odd, but it now works. White to black and black to white is the correct way. Those colors are for the Ram 2500. Different colors for different models.

 

[Brutal_HO]

I don't know why he does that (clip colors).

AlfaOBD

Has anyone played with AlfaOBD on their 2019 HD's yet? I'm curious if anything is accessible to "change" and if it just works. There is lots of different info out there on other forums, but i haven't found anything in regards to the 2019's. EDIT: AlfaOBD does work, here is the what is needed...

hdrams.com

White/Green wire to WHITE base connector (CANBUS-IHS)
Yellow/Blue wire to BLACK base connector (CANBUS-C)
https://hdrams.com/forum/index.php?...module-location-for-programmer.440/post-26099