Yeah, that’s what I’m afraid of… getting to that thing is a b!%6h!
It doesn't even need to be there....if you do indeed have to swap it....you should move it under the seat or something. Just extend the CAN connector. All of the coax are already so long you can put it anywhere else in the cab. Maybe you can even use the CAN connector behind the glove box.
Pretty sure you can scan codes from CVPM. Check that first....then I'd check the connector in the passenger kick panel that connects the 8.4 to the cvpm. Knock out easy stuff before you take the damn back panel off again.
do you have a Tazer installed ? While rare it can cause this issue also. just something else to consider before you get too deep on troubleshooting, unpair the Tazer and see how it is.
Yeah, haven’t even considered the tazer. If I was to do this install again, I’d definitely put it behind the glovebox. There’s plenty of room back there. That back panel just isn’t worth it.
So it’s been a minute and I got locked out of my account with a password update, so wanted to give an update. So far all I’ve done is disconnect the rear cam, blow out the connectors, and reconnect. I recall reading somewhere the rear cam giving someone else issues. I’m very skeptical this was the issue, but it hasn’t had an episode since. It was happening every time I drove, but my logic was a single camera wouldn’t cause both to exhibit issues. ?‍
I’ll update if it returns or this was the fix.
So I was lurking on the JL forum and someone mentioned the last UConnect, update about a month ago, caused some “flakiness” with his cam. Then about a week ago, a second update came out. It’s very unusually for UConnect updates to come so close together. Usually a year or more apart.So it’s been a minute and I got locked out of my account with a password update, so wanted to give an update. So far all I’ve done is disconnect the rear cam, blow out the connectors, and reconnect. I recall reading somewhere the rear cam giving someone else issues. I’m very skeptical this was the issue, but it hasn’t had an episode since. It was happening every time I drove, but my logic was a single camera wouldn’t cause both to exhibit issues. ?‍
@Jimmy07 Thanks for the excellent write up (and the CVPM harness). I just finished my install and programmed via AlfaODB. I'm wondering if you can explain "takes several drive cycles and some time for all the settings changes to take effect"? I would think setting changes would be immediate, so this boggles my mind. And what's the definition of a drive cycle? Is there any way to accelerate this, as I want instant gratification for my weekend of work. ?Finally, you need to enable the system in the BCM to get it working. You’re going to have to use AlfaOBD to do this, as the sales code for the integrated trail cam system won’t be available for your VIN. Yes, I realize @bryanklay was able to get it added to his, but he got extremely lucky that they allowed it, and don’t expect this to be the case for everyone. In order to attempt to get a sales code added to your VIN build that is unavailable, you have to convince the dealer service advisor to contact the area FCA rep. HE has to convince the area rep to call FCA and in turn convince engineering to make the sales code available to add for your VIN, and they could easily say “NO, end of discussion”. EVEN AFTER they allowed it for Bryan, when they added the sales code and restored his vehicle configuration, it still didn’t work. It didn’t enable all the necessary BCM settings. So, rather than roll the dice with the dealer, and potentially wasting hourly rate money, just use AlfaOBD to get it done right the first time. Inevitably, people are going to wonder about their warranty with using AlfaOBD. First off, you’re already installing hardware onto your vehicle that isn’t going to be covered anyway if something goes wrong with that hardware. Second, AlfaOBD is changing the exact same bits in the BCM configuration that adding the sales code does, so technically speaking, it’s enabled the exact same way as factory. And last, the dealer can’t read the BCM configuration to see what changes have been made.
Software: AlfaOBD- Android app from google play store, or windows version download from http://www.alfaobd.com/download.html
Android will work, but windows is more powerful/preferred.
OBD interface so AlfaOBD can interface with vehicle modules- OBD Link MX+ is preferred, and will without a doubt make any change possible with no issue. People have had success using BAFX OBD Bluetooth, but it may come across some settings changes it’s not fast enough to make.
Security gateway module bypass (to allow the BCM settings changes to be made)- https://www.infotainment.com/products/fca-security-gateway-module-bypass?variant=8775773945892
To get started, unplug the security gateway module under the steering column, and plug in the bypass-
Plug the interface into the OBD port, and pair it to your Android device or windows computer. Open up AlfaOBD. For the Android version, connect to the interface. Choose your vehicle brand and model. Select body computer in the drop down, then select MY2020-2021 in the next drop down. Select connect, and once connected, *the first thing you want to do is save your current configuration so you have something to go by if you enable/disable some wrong settings by accident*. Select the faults and status tab. For Android, select the battery icon on the bottom right. Select read system ID, and let it fully populate. For windows, select view log, then “save as” anything or anywhere you want. For Android, once the system ID is read, it is automatically saved into a file in AlfaOBD. Once that’s done, click the active diagnostics tab. For the Android version, this is the little car in the bottom right. Drop down the menu and choose car configuration change towards the bottom. On the next drop down, find all the settings listed below and set each one how to what I have listed. For each setting, you will choose yes/no, or enable/disable. You’ll hit start, then next, then wait for procedure complete. Hit start one more time, and it will confirm the change by saying nothing else needs to be done. Move right on the the next setting change. No need to power off or wait between changes. These are all the settings changes that need to be made/confirmed:
VehConfig 1 rear view camera- NO
VehConfig 2 off road capable- YES
VehConfig 8 off road camera present- YES
ECUConfig 3 rear camera present- NO
CBC Features reversible washer pump enabled- YES
CBC Config I/O connector A pin 14- YES
CustSetMenu 1 Rear View Camera Gridlines CSM Present- NO
CustSetMenu 1 Rear Camera CSM Present- NO
CustSetMenu 3 Auto Launch Forward Facing Camera Off Road Plus CSM Present- NO
CustSetMenu 3 Auto Launch Off Road Plus CSM Present- YES
CustSetMenu 3 Forward Facing Camera Gridlines CSM Present- YES
CustSetMenu 3 Rear CVPM Camera Dynamic Gridlines CSM Present- YES
CustSetMenu 3 Rear CVPM Camera Static Gridlines CSM Present- YES
Cabin Net CVPM central vision processing- YES
Once these are changed, close the software. It will take several drive cycles and some time for all the settings changes to take effect. After that, you’re done, and will have the fully functioning integrated trail cam system.
Special thanks to @bryanklay. It’s been a pleasure helping him get this up and running. Very knowledgeable, and immediately picked up on, and understood everything I explained to him, and made remote troubleshooting and brainstorming a breeze! He’s going to get the new rear camera installed later this weekend, and we’re confident that will wrap up his full installation.
You can do battery disconnect cycles and other stuff to make it faster.
You're right, patience is a virtue. I'm an IT engineer, so I really do want to know the technical side of why you have to wait. That would satisfy my curiosity, if anyone knows...
![Brfertig [HACKED ACCOUNT]](https://cdn.jeepgladiatorforum.com/data/avatars/s/28/28791.jpg?1589454836){kind=avatar}
![O[][][][][][][]O](https://cdn.jeepgladiatorforum.com/data/avatars/s/36/36685.jpg?1609685303){kind=avatar}