12/17 Updates Released

[breeves002]

Yeah I’m just concerned because the ABS module is listed under CSP 21P22 which I’m going in for in 2 weeks. I just don’t want a bad version getting pushed to the car.

Probably different software. It’s possible it’s the same but older vehicles don’t have the eye tracking camera enabled yet so shouldn’t be an issue. It seems to be that’s what the issue is with.

Sponsored

 

[ProximusAl]

I’m only getting offered the 2 APIMs again. You can see in the black bubble regarding the cable. Fast boot flash is something I’ve seen with android but not sync.

 

[DevSecOps]

Yeah so the abs update broke Bluecruise and lane centering it seems….but no codes in anything. Just BC not available.

There was a second ABS update released yesterday. I ran that and BC is still broken. Going to try a 12v disconnect and reconnect to hopefully get it back. Otherwise it’s back to UCDS and the VBF loader to flash the old software back…

I updated all the modules today. I noticed that the TCU and IPC modules wouldn't go through until after the GWM update and a restart of my laptop. They originally failed in the comms stage.

The ABS update took along with the TCU and IPC but they are bugged along with the PCM and show pending. Looking at the logs however show that the TCU and IPC updated successfully. The ABS update didn't log anything which I find strange, but it said successful when it was done

Bluecruise is gone for me as well. I never use is so I'm not too worried about it. The eye tracking system is not working either. Regular cruise previously required it with BC enabled and I can cover the sensors and it doesn't care.

Spoiler: IPC Update Log

***** DEBUG LOG RESULTS *****
Instrument Cluster Module
Based on template version: FNV2_ver1.1
Application type - Software Update
Opening up comms channels and checking module communications.
Comms ok with module
Config data source is MODIFIED_CONFIG, number of DIDs =    11
Number of Config DIDs from GIVIS = 11
GIVIS DE0x Ok
Using GIVIS DExx Data.
Opening up comms channels and checking module communications.
Comms ok with module
shi BEGIN-- GetFilesFromGivisProcess
File Mode = MR parser Used
shi FESN From CDL = 1PF114BP, FESN Read From Module = 1PF114BP
shi BEGIN-- GetProgrammingNetworkInterface
shi Asy software list count = 2, Part number from GetPartNumberV2Type = LJ8T-14C026-MS
shi Part number from GetAssemblySoftwarePartNumber = LJ8T-14C026-LS
shi Part number from GetAssemblySoftwarePartNumber = LJ8T-14C026-MS
shi Found matching Software part number in assembly
shi out_strProgrammingNetworkInterface = USB
shi PNI =  USB- Part number =LJ8T-14C026-MS
shi END-- GetProgrammingNetworkInterface
shi BEGIN-- GetProgrammingNetworkInterface
shi Asy software list count = 2, Part number from GetPartNumberV2Type = LJ8T-14C026-LS
shi Part number from GetAssemblySoftwarePartNumber = LJ8T-14C026-LS
shi Found matching Software part number in assembly
shi out_strProgrammingNetworkInterface = CAN
shi PNI =  CAN- Part number =LJ8T-14C026-LS
shi Part number from GetAssemblySoftwarePartNumber = LJ8T-14C026-MS
shi END-- GetProgrammingNetworkInterface
shi END-- GetFilesFromGivisProcess
shi BEGIN-- MainUpdateProcess
shi END-- MainUpdateProcess
Restoring configuration data to module.

DA01 = DSLJ8T-1A292-AL
GGDS004 L3 SEED = 2461D14D836D610D1E6FCEB7E9FFB321
GGDS004 L3 KEY = DC3E4D1055D35914CC982AFBDFD24EEC

Opening up comms channels and checking module communications.
Comms ok with module
Reading DTCs to check for Unconfigured DTC U2100
Procedure completed or was aborted---SUCCESS
Exit - Ok

 

[louibluey]

I’m only getting offered the 2 APIMs again. You can see in the black bubble regarding the cable. Fast boot flash is something I’ve seen with android but not sync.

I was not careful enough to see the hover over, I get the same message. I will be more careful in the future read those hover over messages, and to look for "only if directed". Too bad, I thought everything on our custom VIN page was already tailored to our VIN.

I wonder if "recover the Sync image software" should be under tools, not SW Updates? I bet all of this was a Friday snafu and that it will get fixed by mid week.

 

[DevSecOps]

Finally, IPC cannot communicate through Mongoose for some reason, and as soon as the update begins, FDRS says ignition off, which terminates the update. Ignoring that instruction, and letting it run does nothing either, it just keeps trying to establish communications.

I had the same issue, but installing the GWM first allowed me to install the TCU and IPC after a reboot of the computer as well. But as I mentioned even though they took, they are bugged out and reporting that they are still available. BC is also dead for me.

 

[generaltso]

Finally, IPC cannot communicate through Mongoose for some reason, and as soon as the update begins, FDRS says ignition off, which terminates the update. Ignoring that instruction, and letting it run does nothing either, it just keeps trying to establish communications.

That‘s the exact same issue I had when trying to install the door control module updates.

 

[breeves002]

I'm glad I'm not alone at least. I'm going to try using UCDS to update the IPC tomorrow. Yesterday when I tried it it worked through mongoose but didn't do any update. Just did what it does for the bugged PCM. I have literally had a VCM on order since March I have no idea why I haven't gotten it yet. Today when I tried the IPC it did the 'cant connect to VCM'. I have a buddy locally with a VCM if I really need one for that update. Just a near hour drive out to him.

@DevSecOps do you have an IPC code for invalid data received from VDM and a VDM code for invalid data received from ECM/PCM B? Also do you now have a traction control option on the touchscreen that doesn't work?

What's extra weird is if you run the ABS update again it physically re-writes the software onto the ABS module. The same software it did before.

Hopefully they fix it this week. I use blue cruise and lane centering all the time so would like to have it back. Just gotta drive the old fashioned way for now. We'll see what happens.

I did a configuration on the CMR just to see if the eye tracking module wanted to be reconfigured. It decided to run a software update on the CMR which took forever and then promptly failed after finishing... So don't do that.

This is what I get for wanting to be on the bleeding edge

 

[DevSecOps]

@DevSecOps do you have an IPC code for invalid data received from VDM and a VDM code for invalid data received from ECM/PCM B? Also do you now have a traction control option on the touchscreen that doesn't work?

Yes Sir:

What's extra weird is if you run the ABS update again it physically re-writes the software onto the ABS module. The same software it did before.

Exact same over here. Normally it would read, verify the version is correct and just attempt to send to the mothership. With this one is acts like it was never done.

 

[breeves002]

Yes Sir:

Yup exactly the same as me.

I wonder if we can get the IPC update to run if it will fix everything. You think they'd force you to do both of them or release a service bulletin on it. Maybe one is coming.

Do you have the traction control switch in the APIM driver assist section now that doesn't work?

Also...You say your TCU updated. Did it do the normal update where it takes the busses offline and shows you the block progress? Mine wouldn't do that. It just acts the same way like I'm doing the PCM update.

 

[DevSecOps]

Yup exactly the same as me.

I wonder if we can get the IPC update to run if it will fix everything. You think they'd force you to do both of them or release a service bulletin on it. Maybe one is coming.

Do you have the traction control switch in the APIM driver assist section now that doesn't work?

Also...You say your TCU updated. Did it do the normal update where it takes the busses offline and shows you the block progress? Mine wouldn't do that. It just acts the same way like I'm doing the PCM update.

Well maybe my IPC and TCU didn't take then. I had experienced the same error where it refused to communicate at the comms stage as others noted, then I did the GWM and rebooted and it let me "do" the IPC and TCU. They went through their paces and said complete, but they didn't disappear so by what you are saying they might not have completed. But I ran the modules against another GTPE that I have a VIN for and some of my TCU and IPC codes are different, so I'm not sure. You know more about this than I do.

As for the Traction Control, no I don't have it in the GUI, but I don't know if I ever did since the GTs came with the physical button to the left of the steering column.

 

[ProximusAl]

Trying to update my APIM but getting a message saying cannot download binary. Trying again

 

[ProximusAl]

Next one…getting there..24 mins so far

 

[ProximusAl]

This one keeps flicking between obtaining software and this

 

[ProximusAl]

 

[ProximusAl]

Sponsored