PDA

View Full Version : 2014 Nissan Rogue - Need help locating source of crash data



blackbird00
16th January, 2017, 07:38 PM
2323232323

ollync
16th January, 2017, 07:51 PM
I have a airbag module from a 2014 Nissan Rogue #98820-JM00C.


I have attempted to clear the crash data using a clean file from someone on this site. That was unsuccessful.
I physically replaced the EEPROM with a clean EEPROM from a new module. That was unsuccessful.


Even after replacing the EEPROM, I am still able to download crash data from the module. Which makes me think it must be stored somewhere else on the module......micro-controller perhaps?

Any thought/advice?

Thanks.

Why not replace old module with new one? Or try eeprom from old module in new one? Maybe it contains only coding data .



Sent from my iPhone using Tapatalk

blackbird00
16th January, 2017, 08:01 PM
232323232323

FxShaw
16th January, 2017, 09:19 PM
What is this mighty crash code that you cant get rid of? DTC?
This module only has one eprom that stores crash and its in a 93c76.

repairmymodule
16th January, 2017, 09:20 PM
What codes are you getting? Is the airbag light flashing or on steady?

With a decent programmer you can program the RL76 eeprom in circuit on these, no need to remove the chip. YOU may have corrupted your file, post your file here and I'll see if it's corrupt and if it is I'll send you a good file you can program to it to fix it

blackbird00
16th January, 2017, 09:47 PM
2323232323

blackbird00
16th January, 2017, 09:48 PM
2323232323

blackbird00
16th January, 2017, 09:57 PM
2323232323

blackbird00
18th January, 2017, 03:54 PM
2323232323

blackbird00
20th January, 2017, 02:06 AM
2323232323

repairmymodule
20th January, 2017, 11:13 AM
I can help you but I have to know, what DTCs you are getting? When you say it's not working, it is very broad description. There are 100 different things that could be wrong. A scan tool will narrow it down. Scan it and post codes.

The file you posted is clear of all crash data

mojomojo
21st January, 2017, 01:17 AM
I can help you but I have to know, what DTCs you are getting? When you say it's not working, it is very broad description. There are 100 different things that could be wrong. A scan tool will narrow it down. Scan it and post codes.

The file you posted is clear of all crash data

Seems like we have research and development going on here? What tool company do you work for Blackbird?:chuncky:

Just having fun

I gave on this module a while ago

blackbird00
23rd January, 2017, 04:02 PM
2323232323

satellitedream
23rd January, 2017, 05:01 PM
I am guessing you are using the bosch CDR system to retrieve this data from the module? Are you sure you swapped the eeproms from the new virigin module to the one with the crash data?

blackbird00
23rd January, 2017, 07:28 PM
2323232323

blackbird00
23rd January, 2017, 07:40 PM
2323232323

satellitedream
23rd January, 2017, 09:50 PM
It could be stored in a internal eeprom of a microcontroller, but i think thats unlikely if it has external eeprom. It could be possible that the crash data retriever is not reading any data or wrong data and thinks there is a crash but there really isn't because it is a new file. What does the CDR read from the new module with virgin eeprom?

blackbird00
23rd January, 2017, 10:05 PM
2323232323

blackbird00
13th March, 2017, 10:01 PM
2323232323

slick_dick
13th March, 2017, 10:10 PM
thanks that was an interesting read

iv found similar stories in other atmel based modules too

:stung:

blackbird00
13th March, 2017, 10:15 PM
2323232323

slick_dick
13th March, 2017, 10:17 PM
i like reading, pictures are good too

blackbird00
13th March, 2017, 10:21 PM
2323232323

slick_dick
13th March, 2017, 10:24 PM
:apologetic:

thats no good then, how about uploading it to an external source like dropbox perhaps?