PDA

View Full Version : Suzuki Freewind mileage change



turist
26th September, 2009, 04:24 PM
Hello
I've got a Suzuki Freewind and I want to change the kilometers from about 74000-75000 to 28000.
I've got a programmer and I read the chip 93c46c.
How can I use the Tachosoft 18.1 to see which hex code is right and which hex code shoud I put?

Thank you!

sixpack
26th September, 2009, 04:37 PM
Hello
I've got a Suzuki Freewind and I want to change the kilometers from about 74000-75000 to 28000.
I've got a programmer and I read the chip 93c46c.
How can I use the Tachosoft 18.1 to see which hex code is right and which hex code shoud I put?

Thank you!
try this one and post results :

turist
26th September, 2009, 04:45 PM
Thank you sixpack very fast reply.
I was thinking to buy an other chip first and not to erase the original (for safety reasons).
By the way with witch programm did you calculate the km?

sixpack
26th September, 2009, 04:51 PM
Thank you sixpack very fast reply.
I was thinking to buy an other chip first and not to erase the original (for safety reasons).
By the way with witch programm did you calculate the km?


with Tachosoft 18.1, compare my file with yours and and see what i did.

info from thachosoft:


Car type: Suzuki FreeWind 650 - 93c46 - 2001 year
The mileage is stored in the next lines:
0020: 15 7B EA FF 15 7B EA FF 15 7B EA FF 15 7B EA FF
0030: 15 7B EA FF 15 7B EA FF 15 7B EA FF 15 7B EA FF
0040: 15 7B EA FF 15 7B EA FF 15 7B EA FF 15 7B EA FF
0050: 15 7B EA FF 15 7B EA FF 15 7B EA FF 15 7B EA FF
where the next bytes:
15 7B EA FF - is a mileage

turist
26th September, 2009, 07:33 PM
I saw that but i don't understand how did you find this code.

22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1

as the Tachosoft when I put 28000 at the odometer value saws this
17403km = FC8BFEFF
28000km = 9F92606D0000
28000km = CC006D60
28000ml = 002AB9809D
28000minutes = 606D00
28000km = 0400C045
28000km = 129A


I have no idea about programming so be patient.
Thank you for your time.

z786
26th September, 2009, 07:45 PM
I saw that but i don't understand how did you find this code.

22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1
22 2E DD D1 22 2E DD D1 22 2E DD D1 22 2E DD D1

as the Tachosoft when I put 28000 at the odometer value saws this
17403km = FC8BFEFF
28000km = 9F92606D0000
28000km = CC006D60
28000ml = 002AB9809D
28000minutes = 606D00
28000km = 0400C045
28000km = 129A


I have no idea about programming so be patient.
Thank you for your time.

what version tachosoft you using?
u mite be using the bugged version dat was crack recently, dats why ur gettin wrong data

regards

turist
26th September, 2009, 08:21 PM
I' m using Tachosoft 18.1

http://img2.imageshack.us/img2/681/tachosoft181.jpg (http://www.imagehosting.com/)

z786
26th September, 2009, 09:26 PM
is it cracked version? if yes it is most likely the messed up version, doesnt work properly as u can see!!!!!

just search the forum for tachosoft 18.1 FIXED, download dat 1, its much better

regards

turist
30th September, 2009, 05:46 PM
Thank you all for your help.
Sixpack the file is working with 28003km

thank you!

turist
21st November, 2009, 02:54 PM
sixpack there is a problem with the rom. The kph is worng I'm going with 50 and the tacho saws 200. Also the milage does not changing. I've done 50 km and th tach still saws 28003.
Whats going wrong? Help please

turist
22nd November, 2009, 10:30 AM
Could this happening because of the type of the chip? The original is 93c46cb6 and the other is 93c46w6.

ivanxxx
22nd November, 2009, 11:21 AM
Could this happening because of the type of the chip? The original is 93c46cb6 and the other is 93c46w6.


No its not the chip check for soldering erorors, take out the chip and check that he is well program then resolder. Suzukis stores milage in km and miles also! Write exact original mileage so we can check algoritam.

turist
22nd November, 2009, 11:48 AM
I found the problem and yes it wasn’t the chip. I was reading the chip in 16bit mode and I wrote it in 8bit because I couldn’t write it in 16bit. Now I read it in 8bit and wrote it in 8bit.