First of all, this is not hardware related, at least it shouldn't be. These issues did not exist when I plugged the car in. Somewhere along the way, I must have programmatically F-ed something up or a module decided to leave the chat. Hardware wise, nothing has changed since the last time all the modules talked to each other.
I have several issues going on in my car right now (window switches don't work, convertible top wont move, etc. however, I can trigger these modules via ISTA-D and they do work, so it's not a hardware fault, the vehicle network is at fault. Check this fault output:
I think the issue stems around either the FRM or CAS systems. Doing some digging and I believe the issue has something to do with them not being in sync with each other or they are in some way not configured correctly to talk to each other? It seems weird. I ran the UID in INPA and cross referenced it with a backup I did back in 2017 and the ZB number match up with what's in the car now. Unfortunately, I didn't have the forethought to backup the FSW files for the CAS and FRM modules back then but I do have backups from last week when the car did work. However, using those backups to create MAN files and pushing them to the modules via NCS Expert didn't help. I did try to have ISTA-P do a full reprogram of the car but it keeps hanging on this idea the FZD module was replaced and I cannot seem to get ISTA-P to ignore that module so ISTA-P is pretty much useless right now. Oddly enough, I was able to push a new ZB flash to it via WinKFP just fine.
For reference, here is the readout from INPA from 2017 and then from yesterday. Just note, some modules are missing because I did the TEL/MULF -> Combox retrofit years ago although maybe I didn't do that very well either as the Combox still reads as TEL/MULF even though it's the Combox ZB number. It works correctly in the car so I never really worried about it.
I'm running out of ideas here and could use some insight/help. I think my next step will be to push a new ZB file to CAS but what else can I do? My next thought was maybe the Footwell module itself kicked the bucket? I was going to try my luck at a scavenge yard to grab an FRM and CAS module off one of the E9x's they have in the yard but I am pretty sure this is not a hardware issue but just some stupid programming issue.
I have several issues going on in my car right now (window switches don't work, convertible top wont move, etc. however, I can trigger these modules via ISTA-D and they do work, so it's not a hardware fault, the vehicle network is at fault. Check this fault output:
I think the issue stems around either the FRM or CAS systems. Doing some digging and I believe the issue has something to do with them not being in sync with each other or they are in some way not configured correctly to talk to each other? It seems weird. I ran the UID in INPA and cross referenced it with a backup I did back in 2017 and the ZB number match up with what's in the car now. Unfortunately, I didn't have the forethought to backup the FSW files for the CAS and FRM modules back then but I do have backups from last week when the car did work. However, using those backups to create MAN files and pushing them to the modules via NCS Expert didn't help. I did try to have ISTA-P do a full reprogram of the car but it keeps hanging on this idea the FZD module was replaced and I cannot seem to get ISTA-P to ignore that module so ISTA-P is pretty much useless right now. Oddly enough, I was able to push a new ZB flash to it via WinKFP just fine.
For reference, here is the readout from INPA from 2017 and then from yesterday. Just note, some modules are missing because I did the TEL/MULF -> Combox retrofit years ago although maybe I didn't do that very well either as the Combox still reads as TEL/MULF even though it's the Combox ZB number. It works correctly in the car so I never really worried about it.
I'm running out of ideas here and could use some insight/help. I think my next step will be to push a new ZB file to CAS but what else can I do? My next thought was maybe the Footwell module itself kicked the bucket? I was going to try my luck at a scavenge yard to grab an FRM and CAS module off one of the E9x's they have in the yard but I am pretty sure this is not a hardware issue but just some stupid programming issue.
