|
Xoutpost server transfer and maintenance is occurring.... |
Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
|
LinkBack | Thread Tools | Display Modes |
#1
|
|||
|
|||
Persistent D907 fault
I have a persistent CAS K-CAN communication fault error D907. It always says it is "currently present". Besides that, every now and then I get a multitude of K CAN related errors in various modules (JBBF, FZD etc.). Today I had a strange happening - unlocked the car with the remote but it did not unlock, only mirrors unfolded and blinkers flashed. I saw on the dash the car on lift warning and unlocked the car with the key. It started OK but again, a bunch of errors were stored. Any idea what might have caused it? went to change the battery this morning, as I suspected it was bad but still, the D907 error persists. Sent from my SM-G998B using Tapatalk |
Sponsored Links | |
|
#2
|
|||
|
|||
So you changed the battery (with a fully charged battery) cleared the D907 and it is back? (Or never clears?)
I recall quite a few years ago some issues with an intermittent short to metal on bus wiring. Also. ONE bad module can pull down a buss and cause errors in other places. This can be troubleshoot by making educated guesses as to the offending one, disconnecting, then see if you got it... |
#3
|
|||
|
|||
The error actually clears when I wipe out the fault memory but comes back. I am yet not sure what makes it pop out - either locking/unlocking the car or else as a few times a tried to monitor when it will pop out (Android DeepOBD app can basically read fault codes in real time) but I was not able to pinpoint something specific.
If you have a knowledge in ISTA, do you know how can I interpret the wake up analysis tool? I checked it yesterday and it says that CAS/FRM woke up the car quite a lot but it also says that when the events are in series, they are probably caused by waking them up by simply locking/unlocking the car, opening doors etc. I am not sure how to tell which wakes up were not supposed to happen. |
#4
|
|||
|
|||
It is a wild guess but does the CAS communicate with the CID (CCC screen) somehow or even directly via K-CAN? Because I have Android unit and remember that one plug was left unhooked and recently I removed the unit to inspect the K-CAN wire behind it and it made me an impression that there is a K-CAN wire on that plug which was hooked to the old CCC screen but there was no place to hook it to the Android unit.
Still, as I remember I did not had the D907 fault when I first installed the Android, it started popping out later on. |
Bookmarks |
|
|
|