Can anyone help me with AlfaOBD not able to connect to the Integrated Center Stack?

[2016 2500]

As the title says if anyone has any information, or could it be physically like wiring plug came loose? I have no idea where that plug might even be but I have had random things happen for example out of the blue engine code for service thottle soon, sensor circuit b voltage low. I clear it and it stays gone until it does not, then it stays for a while, then it goes away

 

[04fxdwgi]

I would think that the throttle related stuff would be related to the PCM, not the radio / hvac (center stack). Items not related to the PCM/TCM usually go thru the BCM (body control module).

The throttle pedal and it's electronics have been known to go south. There is a connector attached to it.

Do you have access to a scan tool to test the components? That would be my 1st goal.

I looked at my AlfaOBD program and don't see anything throttle related after a brief scan. It will test some functions, but not the likes of voltage levels and such. Usually used to mainly turn on / off or calibrate some features

 

[RamDiver]

As the title says if anyone has any information, or could it be physically like wiring plug came loose? I have no idea where that plug might even be but I have had random things happen for example out of the blue engine code for service thottle soon, sensor circuit b voltage low. I clear it and it stays gone until it does not, then it stays for a while, then it goes away

Before you start searching for anything related to AlfaOBD, as part of a full disclosure, you should make it clear you have been touring and tweaking without keeping any records.

And, if the specific issue you're trying to resolve only started after a tweaking fest, please state that without delay.

As I mentioned in your other thread, you could be searching for a lifetime, it's only reasonable to mention the above information immediately to another member trying to assist because they will likely change their approach.

AlfaOBD Troubles

2022 ram 1500 classic 5.7 I've just put new Alpha Rex headlights in and they started throwing a Parking Light Out code, went and bought an OBDmx+ and the AlfaOBD app, followed an online guide on how to enable LED park lamps, but it keeps saying this. Anyone know what's going on?

www.ramforum.com

.

 

[SitKneelBend]

As the title says if anyone has any information, or could it be physically like wiring plug came loose? I have no idea where that plug might even be but I have had random things happen for example out of the blue engine code for service thottle soon, sensor circuit b voltage low. I clear it and it stays gone until it does not, then it stays for a while, then it goes away

I wonder if it's referencing the electric pedal or the throttle body itself? Either way, my first step would be to pop each off, inspect and clean (maybe pack with dielectric grease) then reseat and clear codes to see if the issue returns. Maybe do one at a time to know which connector was the culprit if it works.

 

[2016 2500]

Thank you for the reply's, I mention the pcm issue because of how random it is, I have determined that the problem with that is a physical issue, I have tested a few things on that without much luck finding the root issue. I have found that water as in after heavy rain seems to affect that issue and it stays active for several days until things dry out. I do not think the issues are connected.

And as RamDiver has noted there is more to the issue I have To make a long story as short as possible, I bought the truck in 2022 it is a lower trim SLT here is the build sheet and window sticker and alfaobd logs that are recent. I bought the truck it did not have tow mirrors on it. I bought them from the dealer had them put in, flashed the computer to make the lights work. At that time I did not know about alfaobd when I did find out about it I didn't know much about it and I changed settings for led lights, installed those and then started making changes as I read about them on forums for example I tried to turn on the remote start, turns out without a new RF Hub that would not work, now during this time frame I had not learned about the backup option and so I made many changes without making a backup.

I was using elm327 obd and was able to connect to abs, airbags, bcm, climate control, evic and ICS I am sure it might have been more but I don't recall for sure. I didn't make that many changes in any of them, except the bcm However I did make at least one change I don't know what it was but I believe it had to be in the ICS I added HVAC icons to the top of the radio screen though if you notice the fan shows 7 position I later realized my fan is a 5 position. now I did all this in 2023 and at that time I didn't have any noticeable errors, I had the 3" EVIC and when using a standard code reader only the engine control was seen. Well a couple of weeks ago I found a 7" EVIC cheap and I knew I could reprogram it with alfaobd so I bought it I took pictures of the engine run time screen on my dash the day I replaced it and programed the mileage, the vin and the idle time and added up the 2 lines shown on the 3" evic to get total engine time and programmed that in, that actually had unexpected results so I had to modify those numbers to get what was close ok that all said.

At the time I put in the new evic I could not access the climate control nor the ICS they would just time out. I decided to buy the OBX MX + and try that, it easily accessed the climate control and gave me access to the door modules, which I had not had previously, but still would not connect to the ICS. I tried accessing everything in that menu, such as the amp, the radio navigator module central vision, well the only one that would connect is radio navigator that log is also attached. from that I got fault code UB8 lost communication with ICS

My guess is I changed something inthe body module and caused this, however I am open to the possibility this is a physical problem

 

[SitKneelBend]

Thank you for the reply's, I mention the pcm issue because of how random it is, I have determined that the problem with that is a physical issue, I have tested a few things on that without much luck finding the root issue. I have found that water as in after heavy rain seems to affect that issue and it stays active for several days until things dry out. I do not think the issues are connected.

And as RamDiver has noted there is more to the issue I have To make a long story as short as possible, I bought the truck in 2022 it is a lower trim SLT here is the build sheet and window sticker and alfaobd logs that are recent. I bought the truck it did not have tow mirrors on it. I bought them from the dealer had them put in, flashed the computer to make the lights work. At that time I did not know about alfaobd when I did find out about it I didn't know much about it and I changed settings for led lights, installed those and then started making changes as I read about them on forums for example I tried to turn on the remote start, turns out without a new RF Hub that would not work, now during this time frame I had not learned about the backup option and so I made many changes without making a backup.

I was using elm327 obd and was able to connect to abs, airbags, bcm, climate control, evic and ICS I am sure it might have been more but I don't recall for sure. I didn't make that many changes in any of them, except the bcm However I did make at least one change I don't know what it was but I believe it had to be in the ICS I added HVAC icons to the top of the radio screen though if you notice the fan shows 7 position I later realized my fan is a 5 position. now I did all this in 2023 and at that time I didn't have any noticeable errors, I had the 3" EVIC and when using a standard code reader only the engine control was seen. Well a couple of weeks ago I found a 7" EVIC cheap and I knew I could reprogram it with alfaobd so I bought it I took pictures of the engine run time screen on my dash the day I replaced it and programed the mileage, the vin and the idle time and added up the 2 lines shown on the 3" evic to get total engine time and programmed that in, that actually had unexpected results so I had to modify those numbers to get what was close ok that all said.

At the time I put in the new evic I could not access the climate control nor the ICS they would just time out. I decided to buy the OBX MX + and try that, it easily accessed the climate control and gave me access to the door modules, which I had not had previously, but still would not connect to the ICS. I tried accessing everything in that menu, such as the amp, the radio navigator module central vision, well the only one that would connect is radio navigator that log is also attached. from that I got fault code UB8 lost communication with ICS

My guess is I changed something inthe body module and caused this, however I am open to the possibility this is a physical problem

I'll say you probably didn't change anything in the ICS and instead made a change in the BCM. However, I wouldn't worry about that ICS code if everything is working properly. I'd clear it and see if it comes back. If you read the current status of the BCM and send that log file to me, I can compare it to mine to see if anything looks out of place.

 

[2016 2500]

I'll say you probably didn't change anything in the ICS and instead made a change in the BCM. However, I wouldn't worry about that ICS code if everything is working properly. I'd clear it and see if it comes back. If you read the current status of the BCM and send that log file to me, I can compare it to mine to see if anything looks out of place.

ok this is from 10 mins ago I believe your correct and it is in the BCM that the changes are what is stopping it, the UB8 code is persistent I have cleared it multiple times it comes right back. however I just watched a video, unrelated really, I was looking at the RA4 upgrade and came across a video about a Uconnect 5 install and alfaobd setting to make it work, long story short the guy disabled ICS and enabled DCSD Display Screen module and I recall looking at that in my alfaobd recently and it was enabled, maybe having it enabled is my problem, so I went out, made a backup in case lol, and changed that to disabled on my truck. Now I am letting the truck rest for a while then I will go back and check.

 

[RamDiver]

Keep in mind, that while some tweaks show immediate results, others take numerous ignition cycles or days to to produce an outcome.

.

 

[2016 2500]

good to know

 

[SitKneelBend]

ok this is from 10 mins ago I believe your correct and it is in the BCM that the changes are what is stopping it, the UB8 code is persistent I have cleared it multiple times it comes right back. however I just watched a video, unrelated really, I was looking at the RA4 upgrade and came across a video about a Uconnect 5 install and alfaobd setting to make it work, long story short the guy disabled ICS and enabled DCSD Display Screen module and I recall looking at that in my alfaobd recently and it was enabled, maybe having it enabled is my problem, so I went out, made a backup in case lol, and changed that to disabled on my truck. Now I am letting the truck rest for a while then I will go back and check.

That's exactly what I would have pointed you to.

 

[04fxdwgi]

As mine is a '16 Sport 5.7 with RA4 also, here is a copy of my BCM readout so you can compare

 

[2016 2500]

Thank you for that, however when I open that it seems to be hexidecimal code, which doesn't help me. is that the backup configuration file? or the log file?

 

[SitKneelBend]

Thank you for that, however when I open that it seems to be hexidecimal code, which doesn't help me. is that the backup configuration file? or the log file?

That's the backup config. I've never figured out how to read it either. When you backup your config, that file is the output. What I was looking from for you was the system status log for the BCM.

 

[RamDiver]

That's the backup config. I've never figured out how to read it either. When you backup your config, that file is the output. What I was looking from for you was the system status log for the BCM.

You know, I've often wondered what the heck you guys are talking about with the hex code.

04fxdwgi has posted a PDF file that shows the BCM config, it's not hex, it's a PDF.

I suspect that most crappy android things don't have sufficient brains to recognize a PDF file and just display crap.

Save the file to a PC and open it with your preferred PDF viewer .... and done.

I verified the above hex mystery file and it opens just fine on my laptop.

.

 

[2016 2500]

hmm thank you, I see it was trying to open it in text editor. opening with pdf view makes so much more sense out of it.

You know, I've often wondered what the heck you guys are talking about with the hex code.

04fxdwgi has posted a PDF file that shows the BCM config, it's not hex, it's a PDF.

I suspect that most crappy android things don't have sufficient brains to recognize a PDF file and just display crap.

Save the file to a PC and open it with your preferred PDF viewer .... and done.

I verified the above hex mystery file and it opens just fine on my laptop.

I apologize for my approach but I detest the android OS and think it's foolish to use it on your trucks even if most others do it. No offence intended.

.

 

[2016 2500]

Ok I am looking through the log and I find something I think is strange under cabin net Integrated Center Stack is enabled, however under Audio/Telemat Net ICS is not enabled? could it be as simple as that, it keeps getting confused on which net to search for the ICS, I have it enabled in both thinking it needed it in both.

 

[2016 2500]

So keeping in mind that some times things need time to adjust I went and did some playing around in alfaobd, I made a backup first lol specifically with the cabin net and audio/telmet net I disabled the ICS in cabin net and enabled it in audio net, I reset the body control module and went into the radio navigation module, I cleared the persistent code for lost communication with the ICS and it did not come back. I did lose the heat icons on the top of the radio you can see them in my first picture, I didn't lose any functionality that I could tell, touch screen worked sound was coming out of the speakers, my usb drive was playing music. I then enabled the amp in cabin net, reset the bcm and the radio and no sound out the speakers though you could still see it playing on the screen, all the buttons worked. so I disabled amp in cabin net again and reset both ecu's the sound was back. I checked the radio navigator and still no codes were showing. went back in to bcm and changed cabin net ICS TO enabled reset the ecu and the HVAC icons are back went into that module and got U11B8 Lost communication with ICS. so for some reason my ICS is not communicating I am really starting to think it has to be a plug or wire.

 

[2016 2500]

As mine is a '16 Sport 5.7 with RA4 also, here is a copy of my BCM readout so you can compare

Thanks to this I was able to verify I do have some settings different of course, different engine transmission and I don't have park sensors or auto bright/dim nor do I have rain sensors or any of that equipment, but the communications settings I made pretty much match except where I know different I don't suppose anyone with a more base model diesel would have bcm log, radio logs or any other logs?

 

[SitKneelBend]

You know, I've often wondered what the heck you guys are talking about with the hex code.

04fxdwgi has posted a PDF file that shows the BCM config, it's not hex, it's a PDF.

I suspect that most crappy android things don't have sufficient brains to recognize a PDF file and just display crap.

Save the file to a PC and open it with your preferred PDF viewer .... and done.

I verified the above hex mystery file and it opens just fine on my laptop.

.

You're right, I didn't open that file and assumed he was talking about the hex file. I'll post an example tomorrow.

 

[SitKneelBend]

Here's the Hex format being referred to...