Yamaha FJR 1300

[evo1974]

please help me
eeprom read
soldering points

Thanks

[kumistheru]

please help me
eeprom read
soldering points

Thanks

Car type: Yamaha FJR-1300 - 93c56 - 2002 year
The mileage is stored in the next lines:
0060: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD
0070: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD
where the next bytes:
F6 02 09 FD - is a mileage

======================

For other information, read the following thread.

http://www.digital-kaos.co.uk/forums/f174/change-kms-mazda-422398/

[PremierD]

And out of curiosity mate ... just exactly do the maths work then ? .. its easy to quote Tachoshit or Nyo4 .. pretend they don't exist .. and then do the job :)

PS ... Poster asked for the solder points .. I thought that seeing as how you have done lots of dashes .. and don't remove eeps .. then you could tell him:)

[kumistheru]

And out of curiosity mate ... just exactly do the maths work then ? .. its easy to quote Tachoshit or Nyo4 .. pretend they don't exist .. and then do the job :)

PS ... Poster asked for the solder points .. I thought that seeing as how you have done lots of dashes .. and don't remove eeps .. then you could tell him:)

premierD, don't need to take up a fight. I know that you are not the fan of in-circuit programming. I only talked about my experience about doing eeps in in-circuit and never wanted to hurt your feelings about removing eeps to have a good read. As for the algos, I am not the best in maths, hence poor in cracking algo's but understand you are very good at. As for the posters solder points, I just use my clip to read it in-circuit as below digiprog manual pdf.263291

[evo1974]

Not good tachosoft
Km stored not 60-70 line
Stored 80 90 line
:-)

[captain crackers]

kumisthereu, don't post bad information. If you intend using Tachosoft, it is the same as a Yamaha Majesty 400 2005 but you probably will have to do a byte swap. Now that is 100% correct information. Arthur.

[PremierD]

premierD, don't need to take up a fight. I know that you are not the fan of in-circuit programming. I only talked about my experience about doing eeps in in-circuit and never wanted to hurt your feelings about removing eeps to have a good read. As for the algos, I am not the best in maths, hence poor in cracking algo's but understand you are very good at. As for the posters solder points, I just use my clip to read it in-circuit as below digiprog manual pdf.263291

Hold the bus mate .. you never hurt my feeling at all coz if you did you would not be able to read this .lol...
you do what you do .. and are happy that's all that matters , I agree that some eeproms CAN be read onboard .. but ALL of them can be read offboard .. so being an old fart I'll stick to removing them... at the end of the day its up to the individual how they **** a cluster ... :)

[PremierD]

Not good tachosoft
Km stored not 60-70 line
Stored 80 90 line
:-)

That's when being able to do the maths come in handy .. :) you just see it and edit it

[autodigitec]

That's when being able to do the maths come in handy .. :) you just see it and edit it

Calcing is fun, but a waste of time unless we are finding something that doesn't come in the usual softwares.



In this dump seems to be pretty easy (however not 100% correct as usual)
for example to read:(I dont have a dump, do I just took from tachosoft example)

0080: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD
0090: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD

mileage string = F6 02 09 FD
swap first 2 bytes = 02 F6
x16 or <<4 = 2f 60 (12128 km in decimal)

to write:

let's say 79230 km (01 35 7E in hex)
/16 or >>4 = 13 57
now swap the bytes = 57 13
then we XOR with FFFF = A8 EC
and we have the mileage string = 57 13 A8 EC

0080: 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC
0090: 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC

[kumistheru]

Calcing is fun, but a waste of time unless we are finding something that doesn't come in the usual softwares.



In this dump seems to be pretty easy (however not 100% correct as usual)
for example to read:(I dont have a dump, do I just took from tachosoft example)

0080: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD
0090: F6 02 09 FD F6 02 09 FD F6 02 09 FD F6 02 09 FD

mileage string = F6 02 09 FD
swap first 2 bytes = 02 F6
x16 or <<4 = 2f 60 (12128 km in decimal)

to write:

let's say 79230 km (01 35 7E in hex)
/16 or >>4 = 13 57
now swap the bytes = 57 13
then we XOR with FFFF = A8 EC
and we have the mileage string = 57 13 A8 EC

0080: 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC
0090: 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC 57 13 A8 EC

Thanks. Good explanation. So, the Tachosoft is not wrong in this sense except the location of the mileage. Arthur, the Captan Cracker have criticized me before saying that I was giving wrong information.

[kumistheru]

Hold the bus mate .. you never hurt my feeling at all coz if you did you would not be able to read this .lol...
you do what you do .. and are happy that's all that matters , I agree that some eeproms CAN be read onboard .. but ALL of them can be read offboard .. so being an old fart I'll stick to removing them... at the end of the day its up to the individual how they **** a cluster ... :)
Thanks PremierD. You are right. All eeps can be read off the boards without a problem. Can't argue about that.

[captain crackers]

kumistheru, You say "Tachosoft is not wrong in this sense except the location of the mileage". I can assure you that putting the mileage in an incorrect location can be very wrong. If you don't believe me, try it. I criticized you because all you did was copy and pasted Tachosoft information which you thought was correct but I knew it wasn't. How you do your work is up to you but giving out wrong information to others is not a good idea. One good thing though, you have now been shown how to calculate this type of algo.Arthur.