Pages: [1] 2
Author Topic: ME5.9.2 IMMO OFF. 24C02 is a little weird though  (Read 23647 times)
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« on: October 02, 2013, 06:03:49 PM »

Hey guys.
In the middle of a simple immo off here.
Hot aired the 24c02 off the board read it and hummm its a little weird here.
I was expecting A0 but I am seeing a F0 in the locations to be changed?

Does anything think if I just went ahead and made it 50 in the main and backup and corrected the checksum it would be ok?

Thanks for any advice.

oops forgot the file.. Smiley

BTW its out of a 2.0 Beetle 06A 906 018 AB if anyone needs a 24c02 file.
« Last Edit: October 02, 2013, 06:05:48 PM by f1torrents » Logged
eliotroyano
Hero Member
*****

Karma: +47/-8
Offline Offline

Posts: 807


« Reply #1 on: October 02, 2013, 07:27:01 PM »

Hey guys.
In the middle of a simple immo off here.
Hot aired the 24c02 off the board read it and hummm its a little weird here.
I was expecting A0 but I am seeing a F0 in the locations to be changed?
Does anything think if I just went ahead and made it 50 in the main and backup and corrected the checksum it would be ok?
Thanks for any advice.
oops forgot the file.. Smiley
BTW its out of a 2.0 Beetle 06A 906 018 AB if anyone needs a 24c02 file.

In fact it is a little weird dump. It seems to be more of a M38x ECU that a M592 one. Anyway it should be easily tested on bench. Also I remember that 24C02 from M592 ECUs, allows to be read and write with a clip without desolder the chip. Also short the crytal to be safe and avoid CPU startup. From my experience that trick wasn't helpful with M383 ECUs.
Then test and reply.
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #2 on: October 02, 2013, 07:34:37 PM »

It is 100% me5.9.2

I am thankful for the info. I tried to read it with my clip but couldn't get it to connect well.
Read first try once I took it off.
How would one test it on the bench to see it it was successful?
Logged
eliotroyano
Hero Member
*****

Karma: +47/-8
Offline Offline

Posts: 807


« Reply #3 on: October 02, 2013, 07:52:14 PM »

It is 100% me5.9.2
I am thankful for the info. I tried to read it with my clip but couldn't get it to connect well.
Read first try once I took it off.
How would one test it on the bench to see it it was successful?

During my tests, M383 & M592 send the engine blocked by immobilizer code testing it on bench and or the eeprom error code if exist some checksum error. If everything is OK neither of this codes should appear.
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #4 on: October 02, 2013, 07:59:53 PM »

Oh, yes of course.
I was misunderstanding what you originally wrote there.
I will finish it up and test it tomorrow.
Thanks for the input.
After some looking around I'm thinking this ECU might have a unitronics file on it.
I haven't even looked at the flash yet though.
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +639/-21
Offline Offline

Posts: 5640


« Reply #5 on: October 02, 2013, 08:10:58 PM »

I just have to be that guy.

M5.92

E=DBW
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655


« Reply #6 on: October 02, 2013, 08:41:31 PM »

I just have to be that guy.

M5.92

E=DBW

 Roll Eyes
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #7 on: October 03, 2013, 05:24:39 AM »

During my tests, M383 & M592 send the engine blocked by immobilizer code testing it on bench and or the eeprom error code if exist some checksum error. If everything is OK neither of this codes should appear.

May I ask why you changed
F0 -> A0 and not -> 50 ?

I was under the assumption
F0 = ?
A0 = Immo on
50 = Immo off

I had porepaired a file with 50 and then noticed you had posted up a file and it had A0.
Logged
eliotroyano
Hero Member
*****

Karma: +47/-8
Offline Offline

Posts: 807


« Reply #8 on: October 03, 2013, 05:47:12 AM »

May I ask why you changed
F0 -> A0 and not -> 50 ?
I was under the assumption
F0 = ?
A0 = Immo on
50 = Immo off
I had porepaired a file with 50 and then noticed you had posted up a file and it had A0.

F1Torrents basically you do not need to force hex 50 in that locations, please check out the attached pic, that I found here in Nefmoto forums....
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #9 on: October 03, 2013, 07:46:27 AM »

Yes, I a aware of that pic.
I was under the impression that it needed to be 50 but it seems you are saying it just needs to be reduced by 50.
Either way I will test and see what happens.
Just my test clip is horrible for reading on the board so I have to take the chip off every time I make a change.
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #10 on: October 06, 2013, 12:33:04 PM »

I ran some bench tests and without a car to test this in its hard to tell if the immo is on or off.

e2p removed- DTC for ROM ERROR
e2p stock file-No DTC for eeprom or immo
e2p with "A0" - No DTC for eeprom or immo
havent tested "50" yet

I checked the measuring blocks but don't see anything related to engine start permitted or not.

I guess my only question is.
Does the value just have to be reduced by "50" or does it have to be "50"
Is it just a coincidence that in a normal 24c02 immo off
A0 - 50 = 50  (that it just happends to = 50 )
Logged
eliotroyano
Hero Member
*****

Karma: +47/-8
Offline Offline

Posts: 807


« Reply #11 on: October 07, 2013, 05:39:08 AM »

I ran some bench tests and without a car to test this in its hard to tell if the immo is on or off.
e2p removed- DTC for ROM ERROR
e2p stock file-No DTC for eeprom or immo
e2p with "A0" - No DTC for eeprom or immo
havent tested "50" yet
I checked the measuring blocks but don't see anything related to engine start permitted or not.
I guess my only question is.
Does the value just have to be reduced by "50" or does it have to be "50"
Is it just a coincidence that in a normal 24c02 immo off
A0 - 50 = 50  (that it just happends to = 50 )

f1torrents from my tests DTCs was seen after at least two ignition on-off cycles. About the immo off procedure my understanding is that you need to substract 50 to the 000C & 006C fields and we need to check checksum adding 50 to the inverse alternate fields 000F 000E & 006F 006E, and going back inverse again. The main issue is that all eeprom dumps that I have have A0 with immo on.
Logged
MK2-VRT
Full Member
***

Karma: +2/-10
Offline Offline

Posts: 131


« Reply #12 on: October 07, 2013, 06:40:34 AM »

Change A0 to 50..

When you see A0 in 0x000 and 0x040, recalculated the checksums, when you see A0 in 0x000 and 0x060 / 0x070, then change A0 to 50 and not calc the sums, change it to 9E

Example :

0x000 - 0x040 ( Calc sums )

Original :
A0 FF 57 F4

Off
50 FF B4 F4

0x000 - 0x060

Original :
A0 FF 57 F4

Off :
50 FF 9E F4
Logged
f1torrents
Sr. Member
****

Karma: +17/-1
Offline Offline

Posts: 303


« Reply #13 on: October 07, 2013, 08:14:44 AM »

Thanks for the info there.
I am familiar on how to alter the IMMO and CS
The questions was about the problem with the file having a
F0 to start with instead of a A0

So would you change
F0 > A0
Or
F0 >50
Logged
eliotroyano
Hero Member
*****

Karma: +47/-8
Offline Offline

Posts: 807


« Reply #14 on: October 07, 2013, 11:46:46 AM »

Thanks for the info there.
I am familiar on how to alter the IMMO and CS
The questions was about the problem with the file having a
F0 to start with instead of a A0
So would you change
F0 > A0
Or
F0 > 50

I understand from MK2-VRT comment that you need to change F0 to 50 for Immo OFF. I can't verify that because all the immo dumps in my small database of M38x & M592 files are "A0" for Immo ON.
« Last Edit: October 07, 2013, 11:49:00 AM by eliotroyano » Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0s, 0q)